What is Sellercloud?
Sellercloud is a commerce operations platform that manages orders, inventory, and warehouse fulfillment across sales channels. Redo’s Sellercloud integration creates an RMA in Sellercloud for each approved return and processes the return in Redo once the RMA is closed in Sellercloud.What the integration does
From Redo to Sellercloud
When a return is approved in Redo, the integration finds the original order in Sellercloud and creates an RMA against it. The RMA has:- Return items only, matched to the Sellercloud order lines by SKU (the order line’s
ProductID). Items the customer keeps (green returns) are left off, and two Redo lines with the same SKU are combined into one. Items with no SKU, or a SKU not on the Sellercloud order, are left off the RMA without a notice on the return. If the order has two lines with the same SKU, Redo uses the first. - Return reason, matched to a Sellercloud return reason with the same name, ignoring case and punctuation. When none matches, Redo uses the reason named Other. If Sellercloud has no reason named Other, or Redo can’t read your reasons, the RMA is created without a reason.
- Item description
Redo return {returnId}: {reason}, which Redo uses to recognize its own RMAs. - Tracking number, when the return has one at approval or when you retry. Redo reads the RMA after creating it and sets the tracking number only when it differs. A tracking number added later is not sent.
#, matched exactly against the order’s source order ID.
Before creating an RMA, Redo lists the RMAs already on the Sellercloud order and looks for one whose item description is Redo return {returnId} or starts with Redo return {returnId}:. If it finds one, Redo records that RMA instead of creating a second. If several match, Redo records the oldest. If the lookup fails, Redo stops with an error instead of creating an RMA, so a retry never books a duplicate.
Redo does not create an RMA when:
- the return ships to a Redo warehouse (a returns center)
- every item is a green return
- the customer chose a drop-off return
- the return is an in-store (POS) return
- RMA creation is turned off for your store
From Sellercloud to Redo
Sellercloud does not send webhooks. Redo checks Sellercloud every hour, on the hour, for RMAs that were updated since the last successful check and are closed. For each closed RMA, Redo finds the return by the stored RMA ID:- Return still open: Redo processes every item not yet processed. Restocking follows your Redo inventory restock setting; items from green returns are not restocked.
- Return already closed in Redo: Redo adds a timeline note and changes nothing.
- No Redo return for the RMA: Redo skips it.
How to set it up
Prerequisites
Active Sellercloud account with API access
Active Sellercloud account with API access
API user permissions
API user permissions
Sellercloud API base URL
Sellercloud API base URL
/api/token and /api/Rma.Orders flow through Shopify
Orders flow through Shopify
Configuration steps
Send the connection details
Choose what to turn on
- Create RMAs: Redo creates an RMA in Sellercloud for each approved return.
- Process returns: Redo processes returns when their RMA is closed in Sellercloud.
Test the integration
- Approve the return and confirm that the return timeline shows the Sellercloud RMA ID.
- In Sellercloud, open the RMA and check the items, reasons, and tracking number.
- Close the RMA in Sellercloud.
- Within the next hourly check, confirm that Redo processes the return.
Troubleshooting
When Redo can’t create the RMA, the return gets the RMA creation failed tag and a timeline entry. Retry from the return’s actions menu after you fix the cause.Sellercloud rejected the stored credentials
Sellercloud rejected the stored credentials
- Confirm the API base URL and username with Redo support, and ask for a secure way to re-share the password if it changed
- Confirm the API user is active in Sellercloud
No Sellercloud order was found for this Shopify order
No Sellercloud order was found for this Shopify order
- Confirm the order exists in Sellercloud and wait for order import if it is new
- Create the RMA manually in Sellercloud if the order can’t be matched
The Sellercloud API returned an error: no items matched
The Sellercloud API returned an error: no items matched
- Check that the SKU in Shopify matches the product ID on the Sellercloud order exactly
- Check that no SKU changed after the order was placed
The Sellercloud API user is not allowed to create RMAs
The Sellercloud API user is not allowed to create RMAs
- Grant the API user RMA-creation permission and a company assignment in Sellercloud
Sellercloud did not return an RMA ID after creation
Sellercloud did not return an RMA ID after creation
- Check Sellercloud for an RMA on the order before retrying. If Redo finds it on retry, it records it instead of creating another.
The Sellercloud API returned an error
The Sellercloud API returned an error
- Retry from the return’s actions menu
- Contact Redo support with the return ID if it keeps failing
FAQ
Can I connect more than one Sellercloud account?
Can I connect more than one Sellercloud account?
When should I close an RMA?
When should I close an RMA?
How does Redo find the Sellercloud order?
How does Redo find the Sellercloud order?
What happens when a return is reset or rejected in Redo?
What happens when a return is reset or rejected in Redo?
What does Redo write to the RMA?
What does Redo write to the RMA?