Skip to main content

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.
Redo finds the Sellercloud order by the Shopify order name, with and without the #, 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
The return timeline notes a skipped RMA.

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.
The first check looks back 24 hours. Each later check starts 5 minutes before the previous one began. If the Sellercloud request fails, the next check starts from the same point. If Redo can’t process one RMA, it logs the error, continues with the others, and does not retry that RMA unless Sellercloud updates it again. Contact Redo support if a closed RMA did not process.

How to set it up

Redo support sets up Sellercloud. There is no self-serve connect button. To connect Sellercloud to your Redo account, email Redo support with the connection details below (not the password) and mention which Redo team the integration is for.

Prerequisites

You need a Sellercloud account and an API user (username and password) for Redo to use.
The API user needs permission to read orders, read and create RMAs, update RMA tracking numbers, and read return reasons. It also needs a company assignment in Sellercloud. Without RMA-creation permission, Redo reports that the API user is not allowed to create RMAs.
The address of your Sellercloud REST API, the one that serves /api/token and /api/Rma.
Your Shopify orders must reach Sellercloud with the Shopify order name as the order’s source order ID, so Redo can find the original order.

Configuration steps

1

Send the connection details

Email support@getredo.com with your Sellercloud API base URL and API username. Ask support for a secure way to share the API password, and do not send it by email.
2

Choose what to turn on

Both settings are on by default. Tell Redo support if you want either one off:
  • Create RMAs: Redo creates an RMA in Sellercloud for each approved return.
  • Process returns: Redo processes returns when their RMA is closed in Sellercloud.
3

Test the integration

Create a test return in Redo for an order that is in Sellercloud, then:
  1. Approve the return and confirm that the return timeline shows the Sellercloud RMA ID.
  2. In Sellercloud, open the RMA and check the items, reasons, and tracking number.
  3. Close the RMA in Sellercloud.
  4. Within the next hourly check, confirm that Redo processes the return.
Redo asks Sellercloud for an access token with your username and password, and requests a new token 5 minutes before the current one expires. Redo does not run a credential test at setup. A wrong URL, username, or password shows as an error on the first 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 refused the token request.Solution:
  • 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 has a source order ID equal to the Shopify order name.Solution:
  • 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
When none of the returned SKUs equals a product ID on the Sellercloud order, Redo creates no RMA and the return shows the generic Sellercloud API error. Redo support can see the cause.Solution:
  • 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
Sellercloud blocked the request.Solution:
  • Grant the API user RMA-creation permission and a company assignment in Sellercloud
Sellercloud accepted the request but returned no RMA ID.Solution:
  • Check Sellercloud for an RMA on the order before retrying. If Redo finds it on retry, it records it instead of creating another.
Sellercloud returned an error or an unexpected response.Solution:
  • Retry from the return’s actions menu
  • Contact Redo support with the return ID if it keeps failing

FAQ

Each Redo team has one Sellercloud connection. To switch accounts, contact Redo support.
Close an RMA when the whole return is received. A closed RMA processes every unprocessed item on the return.
Redo looks up the order by the Shopify order name and checks the first 50 matching orders. The Shopify order name must be the source order ID in Sellercloud.
Redo leaves the RMA in Sellercloud. Cancel it in Sellercloud.
Redo creates the RMA. It does not receive items, set a resolution, or add notes, and it does not read received quantities.

Support

For issues with the Redo integration configuration, return processing, or data synchronization, contact support@getredo.com. For issues with Sellercloud access, API credentials, or warehouse operations, contact your Sellercloud account manager or support team.