DSCO Integration FAQs: API dropship, whichever retailer requires it

DSCO (also written Dsco) is an API-first platform that orchestrates dropship and marketplace order flow between retailers and their suppliers, handling real-time order ingestion, structured product catalogs, live inventory checks, and automated tracking. It began as a CommerceHub product and is now part of Rithum.

Not exactly — DSCO, ChannelAdvisor, and Cadeera are all products under the Rithum umbrella (formed when CommerceHub acquired ChannelAdvisor and rebranded as Rithum in December 2023), but DSCO specifically is the API-based dropship engine, distinct from ChannelAdvisor's marketplace listing and retail media tools. See the ChannelAdvisor hub for that side of Rithum.

The retailer decides. Major retailers including Nordstrom, Nordstrom Rack, Kohl's, and Saks use DSCO for some or all of their dropship programs; as a supplier, you connect to DSCO because that's the platform your retail partner requires, not because you selected it independently.

Many retailers still run dropship over traditional EDI (850 purchase orders, 856 ASNs, 810 invoices); DSCO is API-first, built for real-time order ingestion and structured catalogs rather than batch EDI transactions. Some retailers use DSCO for some programs and traditional EDI for others.

Each retailer relationship is typically its own connection within DSCO's platform, even though the underlying technology is shared; InfiPlex connects each retailer's DSCO-powered program independently while sharing the same inventory pool.

The InfiPlex DSCO integration connects a retailer's DSCO-powered dropship program to the InfiPlex Inventory & Order Management System. Orders pull in automatically, inventory syncs in real time across every channel you sell on, and shipments route through your warehouse or a 3PL with tracking confirmed back through DSCO's API.

Yes — access to a retailer's DSCO program requires that retailer's approval as a supplier first; DSCO itself doesn't operate an independent vendor application separate from the retailer relationship.

Our USA-based team configures the API connection with you during onboarding, mapping product catalog data, order fields, and shipment confirmation requirements to DSCO's specification for your specific retailer.

Your OMS site is provisioned within 1–2 business days, and API-based connections like DSCO often complete faster than traditional EDI certification, though the exact timeline depends on your specific retailer's onboarding requirements.

Yes — our team maps your product data to DSCO's catalog structure during onboarding; ongoing catalog updates can flow through InfiPlex's standard inventory and product data tools.

InfiPlex pulls orders from the connected DSCO program in real time (DSCO is built for fast order ingestion), landing in the same queue as your other retailer and marketplace orders.

Yes — once an order ships, InfiPlex sends the shipment confirmation and tracking data back through DSCO's API automatically, which DSCO then forwards to the retailer and, in many cases, the end customer.

Yes — the OMS routes DSCO orders to a connected 3PL or WMS via the 3PL Connector, with confirmations sent back automatically once the 3PL ships.

Yes — that's the core of the product: DSCO-powered dropship orders join the same order queue as traditional EDI retailers, marketplaces, and 130+ other integrations, all processed from one screen.

Order status updates flow through the OMS between DSCO and your systems, and our team maps your specific cancellation and return workflow during onboarding so records stay accurate on both sides.

InfiPlex maintains one master inventory pool, and every sale on any channel — the DSCO-connected retailer, another retail partner, or your own webstore — updates available quantities everywhere in real time.

DSCO's platform is built around live inventory checks as part of its real-time order flow; InfiPlex's inventory pool is what feeds that check, so keeping InfiPlex's numbers accurate is what keeps DSCO's availability checks accurate.

Yes — per-channel buffers hold back a safety quantity for that retailer relationship, configured independently from your other channels.

Use the built-in Inventory Tool for direct edits, the Inventory Upload tool for spreadsheet-based changes, scheduled FTP feeds, or automated pulls from supplier systems. One update propagates to DSCO and every other connected channel.

Yes — the OMS tracks stock across multiple warehouses and 3PLs and routes orders to the right source based on your rules.

DSCO connects on every InfiPlex plan as a standard trading-partner connection. Basic Starter is $49.99/month with up to 2,000 SKUs at $0.50 per order; Growth Starter is $499.99/month with 10,000 SKUs and 1,000 orders included ($0.10 per additional order); Growth Pro is $999.99/month with 100,000 SKUs and 10,000 orders included ($0.05 per additional order). Full details are on the Pricing page.

DSCO/Rithum may have its own platform fees depending on the retailer relationship and your agreement with them; InfiPlex's plan and per-order pricing are separate and cover the OMS connection, not any DSCO or retailer-side fees.

Vendors managing several retail trading partners — some via DSCO, some via traditional EDI — often fit well on Growth Starter or Growth Pro, both of which include ERP connections like NetSuite on Growth Pro.

Growth packages carry a 3-month minimum commitment and Partner packages a 12-month term; Basic Starter is month-to-month. Schedule a demo and we'll scope the right plan against your retail trading-partner mix.

The goal here is factual, useful context — DSCO is a real, widely used dropship platform for major retailers, and this hub simply explains how InfiPlex connects to it once your retailer requires it, without disparaging either product.

InfiPlex's connection is scoped to whatever platform your retailer currently uses; if a retailer migrates to a different dropship technology, our team reconfigures the connection accordingly during that transition.