| Flow | DSCO Order ID | PO / Retailer | SS Order # | Status | Tracking | Received | Updated | Error |
|---|---|---|---|---|---|---|---|---|
Loading… | ||||||||
Loading…
How often the middleware checks DSCO for new orders and ShipStation for shipped/cancelled orders. Minimum 15 minutes. Takes effect on next poll cycle — no restart needed.
Every N hours (set in Settings → Poll interval), the middleware calls the DSCO API and fetches orders with lifecycle received — meaning they've arrived at the supplier but haven't been acknowledged yet. Only orders created within the lookback window are returned.
Each new DSCO order is immediately created in ShipStation using the configured Store ID. The DSCO order ID becomes the ShipStation order number — this is the link used to match shipments later. The order lands in ShipStation with status Awaiting Shipment.
Right after the order is created in ShipStation, the middleware calls DSCO's acknowledge endpoint. This moves the order's lifecycle from received → acknowledged, so it won't be fetched again on the next poll. If acknowledgment fails, the order stays in ShipStation but is flagged in the logs.
On each poll cycle, the middleware also checks ShipStation for orders that have moved to Shipped status since the last poll. It only looks at the configured store, so other stores in your account are not affected.
For each shipped ShipStation order that originated from DSCO, the middleware submits the tracking number and carrier back to DSCO using the singleShipment endpoint. DSCO then notifies the retailer. The order is marked Shipped in the middleware dashboard.
If an order is cancelled in DSCO, the middleware cancels the matching order in ShipStation on the next poll. Conversely, if an order is cancelled in ShipStation, the middleware calls DSCO's cancel endpoint. Either way, the order is marked Cancelled in the dashboard.
| Status | Meaning |
|---|---|
| Received | Order pulled from DSCO. Not yet sent to ShipStation. |
| Sent to SS | Order created in ShipStation and acknowledged in DSCO. Waiting to be shipped. |
| Shipped | Shipped in ShipStation. Tracking number pushed back to DSCO successfully. |
| Cancelled | Cancelled in either DSCO or ShipStation. Propagated to the other platform. |
| Error | Something failed — see the error column in the Dashboard or check the Logs tab for details. The middleware will not retry automatically; manual intervention may be needed. |
| Setting | What it does |
|---|---|
DSCO Client ID |
OAuth2 client ID from the DSCO / Rithium portal. Used to obtain access tokens. |
DSCO Client Secret |
OAuth2 client secret. Kept encrypted at rest — never exposed after saving. |
SS API Key / Secret |
ShipStation API credentials from Account → API Settings. Used for Basic Auth. |
SS Store ID |
The numeric ShipStation store ID where DSCO orders will be created. Orders from other stores are ignored. |
Poll Interval (hours) |
How often the sync runs. Minimum 0.25 (15 min). Takes effect after the current cycle finishes — no restart needed. |