Sign In
Book a Demo

CommerceHub DSCO Integration for Dropship Suppliers

Rithum DSCO, formerly CommerceHub DSCO, is how retailers send dropship orders to their suppliers. Pipe17 pulls your retailers’ DSCO orders, routes them to your warehouses and 3PLs, and posts tracking and stock back to DSCO.
Book a demo
Pipe17 Rithum Integration and Connector Icon Tile

The Solution for DSCO Integration & Order Management

DSCO Carries the Retailer's Orders. Pipe17 Decides Where Each One Ships.

For a brand on an iPaaS and a legacy OMS, a retailer’s DSCO program means another feed to build and more rules holding its orders apart from DTC. Pipe17’s Order Operations Platform does both jobs. Each DSCO retailer becomes an order source Pipe17 routes with your storefront and marketplaces, against the stock they already sell.
iPaaS & Custom Builds Legacy OMS Pipe17
Native API-First Connectivity ✅ ❌ ✅
Pre-Configured Commerce Connectors ❌ ❌ ✅
Custom Integration Mappings ✅ ❌ ✅
Advanced Order Orchestration ❌ ✅ ✅
Exception Management & Alerts ❌ ❌ ✅
Unified Inventory Management ❌ ✅ ✅
Rapid to Implement & Go-Live ❌ ❌ ✅
Easy to Add / Swap Channels & Flows ❌ ❌ ✅
Low Total Cost of Ownership (TCO) ❌ ❌ ✅

Leading Brands and Fulfillment Providers are Powered By Pipe17

Olly logo horizontal black svg
Follett Higher Education logo horizontal svg black
Mary Ruths horizontal svg logo black
CGK Linens Horizontal SVG Logo
Ryder horizontal svg black logo
AS Beauty logo horizontal svg black
Dude Wipes horizontal logo black svg
FedEx horizontal svg logo black
Wyze horizontal svg logo black
Melin horizontal svg logo black
Barrett Distribution Centers horizontal svg logo
Sacheu Beauty horizontal svg logo black
Made In Cookware horizontal svg logo black
Azalea Wang logo horizontal black svg
Radial fulfillment horizontal svg logo black
Black Rifle Coffee Company logo horizontal black svg

Retailer Dropship Shares Your DTC Stock, Routing, and Reporting

Two-tone icon of a computer dashboard with charts controls and gears symbolizing visibility and system control.

One Stock Count for Retailers and DTC

DSCO retailers sell from the same available count as your storefront and marketplaces, and Pipe17's per-channel buffer holds back the units you reserve for DTC.

Sealed package with checkmark, representing completed or shipped order

Retailer Orders Route Like DTC

Pipe17 routes each DSCO order by the rules your other channels use, and splits a multi-line order across locations when one cannot ship it all.

Box with checkmark overlaid, representing a verified, completed or fulfilled order

Retailer Updates Without the Portal

Pipe17 posts acknowledgments, tracking numbers, line cancellations, and invoices to DSCO for each order your warehouses work. Nobody keys them into a retailer portal.

Automated DSCO Data Flows and Controls

Pipe17 syncs every DSCO dropship program you sell through continuously, taking in orders, cancellations, and retailer labels and sending back acknowledgments, tracking, invoices, and stock.
  • Pull Orders from DSCO. Each retailer’s dropship orders arrive with the purchase order (PO) number, ship-by and cancel-after dates, requested carrier and service, gift message, ship and pack instructions, and the customer’s addresses. Filters limit the pull to the warehouses you fulfill from, a status, or a start date.
  • Acknowledge Orders in DSCO. Pipe17 confirms each order in DSCO once it goes to fulfillment, with an optional pending-shipment status. The retailer sees acceptance as its own step, ahead of tracking.
  • Pull Retailer Shipping Labels from DSCO. When a retailer provides its own shipping label, Pipe17 retrieves it from DSCO for the location packing the order.
  • Push Fulfillments to DSCO. Every shipment posts back with its tracking number, carrier, service, ship and estimated delivery dates, shipping cost, weight, and the SKUs and quantities in the box. An order shipped in several packages sends a tracking number for each.
  • Push Invoices to DSCO. Pipe17 sends DSCO an invoice for each order your locations ship, ready for the retailer to pay from DSCO.
  • Push Cancellations to DSCO. Pipe17 cancels a whole order or only the lines you cannot fill, and DSCO shows the retailer the change while the rest of the order keeps moving.
  • Pull Retailer Cancellations from DSCO. A retailer’s cancellation in DSCO closes the matching order in Pipe17.
  • Push Inventory to DSCO. Pipe17 sends each SKU’s available quantity to DSCO per warehouse, or totals all locations into one DSCO warehouse. Limit the feed to a SKU list when a retailer carries part of your range.
  • Pull Inventory from DSCO. Where DSCO already holds a stock figure for a SKU, Pipe17 reads it in beside your own count.
  • Pull Products from DSCO. Items in DSCO come into Pipe17 by SKU and match the products your channels and warehouses already use. Pull the whole catalog or only chosen SKU patterns.
  • Push Product Updates to DSCO. Pipe17 keeps the items already in DSCO current, from title, brand, description, and cost to country of origin, dimensions, weight, images, and UPC. It also updates the manufacturer’s suggested retail price (MSRP) and the dropship, marketplace, and wholesale prices.
  • Pull DSCO Warehouses as Locations. Pipe17 creates a location for each DSCO warehouse. Orders the retailer assigns there go to the 3PL or facility that ships them, and Pipe17 reports that location’s stock back to DSCO.
  • Match SKUs the Way Each Retailer Sends Them. Pipe17 matches SKUs regardless of case and falls back to the UPC when a SKU is unknown. An order still finds the right product when the casing differs or only a barcode arrives.
  • Run One Connection per Retailer. Each of your retailers’ DSCO programs is its own connection, with separate statuses, SKU filters, and warehouse mapping, even when several retailers share one DSCO account.
  • Turn Unroutable Orders into Exceptions. When no warehouse can fill a DSCO order, Pipe17 raises an exception that names the reason, and your team reroutes it or cancels the short lines while the retailer’s ship-by date is still ahead.

Connect With Your DSCO API Client ID and Secret

Enter the client ID and secret Rithum issues for your DSCO supplier account, then switch on the flows you run. Pipe17 owns the CommerceHub DSCO connector and maintains it as the DSCO API changes.

Ship Every Retailer's Dropship Orders From One Inventory Pool

Watch a DSCO order route to the warehouse holding the stock and post tracking back to the retailer. Your storefront’s available count drops by the same units.
Book a demo
Rithum logo horizontal svg black

is better with

Pipe17 horizontal svg logo black

CommerceHub DSCO Integration FAQs

DSCO is Rithum's dropship platform, which retailers use to send dropship orders to the brands that supply them. Pipe17 connects to DSCO as the supplier through its CommerceHub DSCO integration. Pipe17 pulls each retailer's orders over the DSCO API and routes each one to the location that ships it: a warehouse, 3PL, or store. Pipe17 posts acknowledgments, tracking, invoices, cancellations, inventory, and product updates back to DSCO.

DSCO is a dropship platform, not a company. CommerceHub bought it in 2020, and CommerceHub became Rithum in 2023 after combining with ChannelAdvisor, which is why the same platform now appears as Rithum DSCO. Pipe17's CommerceHub integration, listed as CommerceHub DSCO, serves retailer dropship programs, and a separate Rithum (formerly ChannelAdvisor) integration serves marketplace listings and orders, each with its own setup and data flows.

Nordstrom runs its dropship supplier program on DSCO, and DSW runs its dropship network on the same Rithum platform. A brand selling to a retailer on DSCO connects over the DSCO API, with no EDI mapping for that program. Retailers that run CommerceHub OrderStream, or keep a legacy EDI program, connect through Pipe17's managed EDI instead.

DSCO connects to Shopify, NetSuite, or a 3PL through connectors Pipe17 maintains, with no point-to-point build. Orders pulled from DSCO route to a 3PL such as Radial or ShipBob, or to your own warehouse. The same orders post to NetSuite or another ERP with their fulfillments, and they draw on the inventory your Shopify store or other storefront sells.

Yes, a 3PL on Pipe17 sets up each client's DSCO program as a connection inside that brand's own Pipe17 organization, and the dropship orders route to the 3PL's warehouse like the brand's DTC orders. Tracking posts back to DSCO from the warehouse's shipments, and the brand's inventory at the 3PL feeds the retailer. The 3PL runs one process for retailer dropship and DTC.

Pipe17 allocates inventory to a DSCO retailer from one available count per SKU across your warehouses, 3PLs, and stores, minus the buffer you set for that channel, sent to DSCO per warehouse or as one total. Inventory Buffers, a per-SKU reserve per channel, hold back units you keep for DTC, so a retailer sells only what you can ship. Every order from any channel lowers the count DSCO sees next.

Cancel the line in Pipe17, the cancellation posts to DSCO, and the other lines ship as planned. DSCO scopes whole-order cancellation to the retailer and line cancellation to the supplier, and Pipe17 works within that, canceling line by line from your supplier account, and every line at once when nothing can ship. When the retailer cancels first in DSCO, Pipe17 closes the matching order.

Yes, Pipe17 sends DSCO an invoice for each dropship order your warehouses and 3PLs ship, alongside the acknowledgment and tracking it already posts for that order. Most retailers on DSCO pay their suppliers through its Invoice Workflow, and the invoice reaches the retailer there with the order it covers, whichever location filled it.

Pipe17 is an order management system (OMS) that treats each DSCO retailer as one more order source beside your storefront, marketplaces, and EDI retailers, with a single stock count and the same routing rules behind all of them. Dropship orders post to your ERP with their fulfillments, beside every other channel's orders.