Connect CommerceHub DSCO to Pipe17

DSCO is a drop-ship management platform operated by CommerceHub (Rithum). The CommerceHub (DSCO) connector links your DSCO account to the app so that orders, inventory, products, and fulfillment data move between your retail trading partners and your fulfillment operations.

With this connector, you can:

  • Pull drop-ship orders from DSCO into the app for routing to fulfillment.
  • Pull your product catalog from DSCO, or push it to DSCO from another connected source.
  • Pull inventory from DSCO, or push inventory from a connected 3PL or IMS to DSCO.
  • Push fulfillment and tracking information to DSCO.
  • Pull your DSCO warehouses into the app as locations, and sync order cancellations in both directions.

Setup

Before you begin, make sure you have:

  • An active CommerceHub DSCO account. OrderStream accounts aren't compatible with this integration. DSCO accounts cover only drop-ship orders placed by your retail partners.
  • A completed DSCO onboarding process, if you're a new DSCO subscriber. Work with your DSCO representative to complete it.
  • A Client ID and Client Secret for the CommerceHub (Rithum) API. To create them, see the Rithum article Creating new API credentials.
  • A review of the Pipe17 Quick Start Guide, to confirm that all required setup steps are complete before you go live.

Connect CommerceHub DSCO pop-up

To connect CommerceHub DSCO:

  1. Navigate to Integrations in the app.
  2. Click Add Integration, and then select CommerceHub (DSCO).
  3. In Select CommerceHub environment, select CommerceHub (https://api.dsco.io) or CommerceHub staging (https://staging-api.dsco.io).
  4. Enter your Client ID and Client Secret.
  5. Click Connect.
  6. Check that the integration shows Connected on the Integrations page.
  7. In the integration settings, set up the flows you want to use: Pull locations from CommerceHub, Pull orders from CommerceHub, Process product catalog information, Process inventory, and Push fulfillments to CommerceHub.

Settings

Setting Description Options/Default
Exclude orders created before this date Under Orders. The app pulls only orders created after this date. After syncing starts, the app processes orders as they're updated, so to pull an older order after you move this date back, you need to modify the order in DSCO. Optional. Default: integration creation date
Pull only orders with specific order IDs Pulls only orders with these IDs and ignores all others. Optional
Pull orders when assigned following statuses in CommerceHub Pulls orders that have one of the selected DSCO statuses. Created, Pending shipment, Shipped, Canceled. Default: Pending shipment, Canceled
Allow pulling previously acknowledged orders Pulls orders that were already acknowledged in DSCO. On/Off. Default: Off
Pull only orders allocated to warehouses tied with fulfillment locations in Pipe17 Pulls only orders assigned to DSCO warehouses that are linked to a fulfillment location in the app. Requires Pull locations from CommerceHub. Turn it off to pull orders regardless of warehouse. On/Off. Default: On
Force fulfillment via Pipe17 for following CommerceHub order types DSCO order types that always route through the app for fulfillment. Optional
Acknowledge CommerceHub order when sent to fulfillment in Pipe17 Acknowledges the order in DSCO when the app routes it to fulfillment. On/Off. Default: Off
Mark CommerceHub order as shipment_pending when sent to fulfillment in Pipe17 Changes the DSCO order status to shipment_pending when the app routes it to fulfillment. On/Off. Default: Off
Cancel CommerceHub order when canceled in Pipe17 Sends a cancellation to DSCO when you cancel the order in the app. On/Off. Default: Off
Cancel Pipe17 order when canceled in CommerceHub Cancels the order in the app when it's canceled in DSCO. Before you rely on this setting, confirm that your fulfillment partner also cancels the order. On/Off. Default: Off
Enable case-insensitive SKU matching Under SKU Matching. Matches incoming SKUs to your catalog regardless of case. For example, BGA-6481 BEIGE matches BGA-6481 Beige. If two products differ only by case, the app uses the first match. On/Off. Default: Off
Enable UPC fallback when SKU is not found If an incoming SKU doesn't match a product, the app tries to match by UPC. Requires a UPC on incoming line items. On/Off. Default: Off
Process only products with specific product SKUs patterns Under Products. Pulls or pushes products only for these SKUs. Enter an exact SKU (not case-sensitive) or a regular expression wrapped in slashes, for example /^ABC*/. Optional
Force product catalog resync Forces a full product catalog resync. Use it when products are missing or out of sync. Turn it off after the resync completes. On/Off. Default: Off
Report inventory totals from Pipe17 to dedicated CommerceHub location Under Inventory. Sends inventory from all active locations in the app to this single DSCO location. The location must exist in DSCO. Optional
Process only inventory with specific product SKUs patterns Pulls or pushes inventory only for these SKUs. Enter an exact SKU or a regular expression wrapped in slashes. Optional
Force inventory resync Forces a full inventory resync. Use it when inventory levels look stale or wrong. Turn it off after the resync completes. On/Off. Default: Off

Flows

Flow Direction Notes
Locations DSCO → Pipe17 Runs every 5 minutes when Pull locations from CommerceHub is on. Turn it on before you use warehouse-based order routing.
Orders DSCO → Pipe17 Runs every 5 minutes when Pull orders from CommerceHub is on. Pulls orders in Pending shipment and Canceled statuses by default. Cancellations sync in both directions when the cancel settings are on.
Products DSCO → Pipe17 or Pipe17 → DSCO Runs every 5 minutes. In Process product catalog information, choose Pull product catalog from CommerceHub or Push product catalog to CommerceHub. Pushing sends a catalog from another connected source, such as Shopify.
Inventory DSCO → Pipe17 or Pipe17 → DSCO Runs every 5 minutes. In Process inventory, choose Pull inventory updates from CommerceHub or Push inventory updates to CommerceHub. Pushing sends inventory from a connected 3PL or IMS.
Fulfillments Pipe17 → DSCO Runs every 5 minutes when Push fulfillments to CommerceHub is on. Sends tracking information from your 3PL to DSCO.

Channel SKU mapping: This connector supports SKU mapping. If your DSCO product identifiers differ from the ones in your other channels, set Channel SKU values in Channel Options so that products match across flows.


Integration actions

Action What it does
Pull products by SKUs Pulls products with the SKUs you enter.
Pull orders by external order ID Pulls the DSCO orders with the IDs you enter.
Pull orders by date Pulls orders created after a date, within a time interval from 1 to 48 hours. Default: 1 hour.
Pull inventory by SKUs Pulls inventory for the SKUs you enter.

Troubleshooting

  • Orders don't appear in the app after you connect
    The order usually has no shipment in DSCO. Open the order in DSCO, click SHIP in the upper-right corner to create a shipment, and wait for the next sync.
  • Orders assigned to a DSCO warehouse don't pull into the app
    Turn on Pull locations from CommerceHub, and link the warehouse to a fulfillment location in the app. Or turn off Pull only orders allocated to warehouses tied with fulfillment locations in Pipe17 to pull all orders.
  • The connection fails or shows Not Configured or Error
    The Client ID or Client Secret is wrong, or you selected the wrong environment. Check the credentials in Rithum, update them in the connection settings, and then click Connect again.
  • Products or inventory are missing or out of sync
    Turn on Force product catalog resync or Force inventory resync, and turn it off again after the resync completes. Also check the SKU pattern settings.
  • Your DSCO account is active, but orders aren't routed
    A yellow banner at the top of your DSCO account means your onboarding isn't complete, and the app can't pull orders until it is. Contact your DSCO representative to finish onboarding.

Need Help?

If you need additional assistance:

  • Use Ask Pippen, our AI agent, located at the top of the platform page.
  • Submit a support request with as much relevant detail as possible. Learn how to submit a request.

We’re here to help you succeed with your operations.

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.

Have more questions?
Submit a request
Share it, if you like it.