On Dsco, yes. Product sync is available, so Commercium creates and updates Dsco item records directly from your Shopify catalogue, identifiers, titles, images, categories, costs and each retailer’s required attributes, validated before submission.

On OrderStream, no. Commercium does not currently support product creation for OrderStream; item setup follows each retailer’s own process. Once your items exist, Commercium runs inventory, orders, acknowledgements, shipments, invoices and packing slips from Shopify.

Yes. Products, variants, images, inventory levels and metafields can be created and updated in Shopify from your ERP, PIM or another connected channel, so Shopify can be either the source of truth or the destination.

Yes. Dsco and OrderStream orders can be transformed and sent to supported ERP, ecommerce, OMS, WMS, accounting or fulfilment systems, with acknowledgement, shipment, tracking and, for OrderStream, invoice data flowing back to the retailer.

Yes. Shopify orders can be transformed and sent to supported ERP, ecommerce, OMS, WMS, accounting or fulfilment systems, and fulfilment, tracking and refunds flow back into Shopify.

Yes. Commercium works with businesses during onboarding to prepare product data, connect systems, configure mappings and establish operational workflows, including confirming whether your retailer uses Dsco or OrderStream and setting up the per-retailer mapping or document profile.

Yes, you can add as many Dsco and OrderStream seller accounts as you want while remaining on your same plan. You only upgrade when you cross your plan’s order limits.

Yes, you can add as many Shopify stores as you want while remaining on your same plan, useful for multi-brand or multi-country setups. You only upgrade when you cross your plan’s order limits.

First, book a demo with Commercium and tell us which retailers invited you, whether they trade on Dsco, OrderStream or both, and how your Shopify store is set up.

Second, get your credentials ready, your Dsco account API key; your OrderStream account and exchange credentials, facility IDs and each retailer’s document set; and your Shopify credentials or our app from the Shopify App Store.

Third, meet your integration engineer, who connects Shopify once and maps SKUs, locations, carriers and fields per retailer. Onboarding takes 1–2 hours once the details are provided.

Fourth, test every flow, through Dsco’s onboarding interface and the OrderStream sandbox. Fifth, go live: we switch each connection on, contacting Dsco support where required, and Commercium monitors the workflows.

CommerceHub merged with ChannelAdvisor and now operates as Rithum. Rithum owns two dropship platforms: Dsco, an API-first retailer–supplier network, and OrderStream, a document-driven platform where each retailer sets its own document set. Commercium connects Shopify to both.

The retailer’s onboarding invitation will name the platform. If you’re unsure, send it to us, we’ll confirm which platform the programme runs on and which documents it requires before your first call.

Yes. One Shopify connection feeds both platforms, from the same stock pool, on the same plan. Each retailer gets its own mapping or document profile, whichever platform it uses.

Product, inventory, order, order acknowledgement, shipment and tracking, and packing-slip sync, over the Dsco REST API, for every trading partner on your account.

Order sync, order acknowledgement sync, invoice upload, inventory sync (including the daily full upload), shipment confirmation and automatic packing-slip generation. Which of those run is set per retailer.

You choose which Shopify locations contribute to dropship availability. Those levels are pooled, buffered per retailer and pushed to Dsco and OrderStream in near real time. When an order lands anywhere, every retailer on both platforms is updated.

OrderStream policy mandates a full inventory upload once a day. Commercium performs it to maintain compliance and runs real-time updates alongside it, so availability never goes stale between files.

They can be. Retailer orders are created as Shopify orders tagged by retailer and platform, with customer notifications suppressed, the correct location assigned and dropship cost on the lines.

Orders are downloaded on a schedule, checked against live pooled Shopify stock and acknowledged automatically under your rules, accepting, backordering or cancelling lines. Orders approaching a retailer’s window are escalated before the deadline passes.

For Dsco, the retailer’s slip is retrieved per order. For OrderStream, the slip is generated automatically in the retailer’s layout. Either way it is routed with the pick list to the Shopify location or 3PL packing the order.

Carrier codes and service levels are per retailer on both platforms. Each retailer gets its own carrier mapping, so tracking captured from Shopify fulfilments or your 3PL is accepted.

Yes, on both. Dsco provides an onboarding interface for initial order, acknowledgement and shipping tests, and OrderStream provides a sandbox. We test every flow with your team before anything goes live.

Barcodes are optional in Shopify but expected by most retailers. Commercium audits barcode completeness and format before go-live and flags gaps, with metafield fallbacks where a retailer accepts another identifier.

You can install our app from the Shopify App Store, or connect through Shopify’s Admin API with scoped permissions you approve. No theme changes are required, and access can be revoked at any time.

Yes. You choose which locations contribute to dropship availability, and routing rules decide which Shopify location or 3PL fulfils each retailer order.

Yes. Split and partial shipments are confirmed per package or line, and backorder and cancellation rules are set once per retailer on each platform.

Yes. Once Shopify and your CommerceHub accounts are connected, a new retailer is a new profile over the same Shopify data. A Dsco trading partner we haven’t worked with before can usually be added within a day.