Marketplace order statuses — mapping in both directions

Statuses travel in both directions, and each direction has its own pitfalls.

Step by step — map statuses for a new channel

1. Go to Integrations → Integrations → My integrations and open the connection.
2. Open the Orders stage and expand Status mapping.
3. Get the channel’s list of statuses. With an empty table, you can choose between two buttons:
   • Fetch statuses downloads the marketplace catalog. This works only for some connectors; the others respond “This integration does not provide a status list—add statuses manually.”
   • Add external status lets you enter a status yourself. In the window, enter the Status key (marketplace), the raw value, such as 21 or CANCELLED, and the Display name. Click Add. This opens a drawer from the right; it is not a modal window.
4. Once external statuses exist, click Add mapping.
5. In the Add status mapping window, choose an External status (from the marketplace) and an Internal status (yours). Both fields are required.
6. Save. The system asks for a code in the 2FA verification required window (2FA confirmation when changing permissions).
7. Repeat for each status. Start with those that change how the order is handled: canceled, return, shipped.
8. Review the list for the Push disabled: ambiguous mapping badge. It means two external statuses point to the same internal status, so pushing it is disabled. Remove the extra mapping.
9. Return to this table after the channel has been operating for a few days and map statuses the system added in the meantime. Once external statuses exist, the fetch button is called Refresh statuses.

Delete a mapping using the trash icon in its row. The system asks “Are you sure you want to delete this status mapping?” and you confirm with Delete.

Inbound: marketplace status → internal status

The marketplace sends its status key. The system looks it up in the mapping table and substitutes your status.

What happens to a key that is not in the table:

The system creates it automatically and maps it to the status named default. The import is not interrupted, and no one is notified.

This makes sense because a new marketplace status will not stop sales. But there is a side effect to know about: a new channel’s “canceled” status will fall back to default, like everything else, until someone maps it.

In practice, after connecting a new channel, return to the mapping table after a few days and map the statuses the system added.

If your internal status is deleted, the mapping does not fail outright. Orders fall back to default, and a warning appears in the log.

Outbound: internal status → marketplace status

Pushing status changes is stricter:

• no mapping → nothing is sent; a warning appears in the log;
• more than one mapping for the same internal status → the push is skipped entirely, with an error in the log.

The second case is easy to miss: adding a “second alternative just in case” does not expand the mapping; it disables pushing for that status.

The internal status is updated only after a successful push. If the marketplace refuses the change, the order is not falsely marked as successfully sent.

Fetch the marketplace status list

A button retrieves the status catalog directly from the channel. It works only for some connectors. The others report that they do not support this operation; enter their statuses manually.

This operation is safe: it does not delete anything, only adds missing entries.

Where to find it

Only in Status mapping under the connection configuration’s Orders stage. There is no separate menu screen. Saving requires 2FA confirmation (2FA confirmation when changing permissions).

These are not shipment statuses

Carrier statuses use a completely separate mechanism and their own dictionaries (Status dictionaries — external, internal, and mapping). Do not confuse the two tables.