DSCO is a drop-ship management platform operated by CommerceHub. The app connects to your DSCO account to automate the movement of orders, inventory, products, and fulfillment data between your retail trading partners and your fulfillment operations.
Key capabilities:
- Pull drop-ship orders from DSCO into Pipe17 for routing to fulfillment
- Pull or push your product catalog between DSCO and Pipe17
- Pull or push inventory updates between DSCO and a connected 3PL or IMS
- Push fulfillment and tracking information back to DSCO
Setup
Prerequisites
- An active CommerceHub DSCO account. Note: OrderStream accounts are not compatible with this integration. DSCO accounts cover drop-ship orders placed by your retail partners only.
- If you are a new DSCO subscriber, you must complete the onboarding process with your DSCO representative before connecting to Pipe17.
- A CommerceHub DSCO account with OAuth authorization enabled. You will be redirected to CommerceHub to authorize the connection during setup — no credentials need to be entered manually in Pipe17.
- Review the Pipe17 Quick Start Guide before going live to confirm all required setup steps are complete.
Steps
- Log in to your Pipe17 account.
- Log in to your CommerceHub DSCO account in a separate tab.
- In Pipe17, navigate to Integrations → Add Integration and search for CommerceHub DSCO.
- Click Add. The Flow Settings screen appears. Leave all flow toggles disabled for now and click Next.
- Select the CommerceHub environment you want to connect. If you have a staging environment, select it from the dropdown.
- Click Connect. A new tab opens and redirects you to CommerceHub to authorize the connection. Complete the authorization in that tab. Once authorized, the connection is established automatically and you are returned to Pipe17.
- Confirm the connection is successful. A green Connected status appears on the main Integrations page. If you see Not Configured or Error, contact the Pipe17 support team.
Settings
Flow settings
| Setting | Description |
|---|---|
| Pull orders from CommerceHub | Enables Pipe17 to pull drop-ship orders from DSCO. |
| Pull locations from CommerceHub | Enables Pipe17 to pull DSCO warehouse locations. Enable this setting before using warehouse-based order routing. Disabled by default. |
| Products: Disabled | No product data is synced between DSCO and Pipe17. |
| Pull product catalog from CommerceHub | Pipe17 pulls your product catalog from DSCO. |
| Push product catalog to CommerceHub | Pipe17 pushes a catalog from another connected source (for example, Shopify) into DSCO. |
| Inventory: Disabled | No inventory data is synced between DSCO and Pipe17. |
| Pull inventory updates from CommerceHub | Pipe17 pulls inventory data from DSCO, visible in the Inventory tab. |
| Push inventory updates to CommerceHub | Pipe17 pushes inventory from a connected 3PL or IMS to DSCO. |
| Push fulfillments to CommerceHub | Pipe17 pushes tracking and fulfillment information from your 3PL to DSCO for the corresponding orders. |
Order settings
| Setting | Description |
|---|---|
| Exclude orders created before this date/time | Pipe17 pulls only orders created after the date and time you enter. |
| Pull only orders with specific order IDs | Restricts order pulls to the specified order IDs. All others are ignored. |
| Pull orders when assigned the following statuses in CommerceHub | Pipe17 pulls orders matching the selected DSCO statuses. Default: Pending shipment and Canceled. |
| Allow pulling previously acknowledged orders | When enabled, Pipe17 pulls orders that were acknowledged before the DSCO connection was established. |
| Pull only orders allocated to warehouses tied with fulfillment locations in Pipe17 | Enabled by default. Pipe17 pulls orders assigned to DSCO warehouses that are linked to a fulfillment location in Pipe17. Disable this setting to pull orders regardless of warehouse assignment. Requires Pull locations from CommerceHub to be enabled. |
| Force fulfillment via Pipe17 for following CommerceHub order types | Specify DSCO order types that should always route through Pipe17 for fulfillment. |
| Acknowledge CommerceHub order when sent to fulfillment in Pipe17 | When enabled, the app automatically acknowledges the order in DSCO as soon as it is routed to fulfillment in Pipe17. |
| Mark CommerceHub order as shipment_pending when sent to fulfillment in Pipe17 | When enabled, the app updates the order status in DSCO to shipment_pending when it is routed to fulfillment. |
| Cancel CommerceHub order when canceled in Pipe17 | When enabled, canceling an order in Pipe17 pushes a cancellation to DSCO. |
| Cancel Pipe17 order when canceled in CommerceHub | When enabled, canceling an order in DSCO also cancels it in Pipe17. Confirm with your fulfillment partner that they have also canceled the order on their end before relying on this setting. |
Product settings
| Setting | Description |
|---|---|
| Process only products with specific product SKUs patterns | Restricts product sync to the SKU patterns you specify. |
| Force product catalog resync | Forces a full resync of the product catalog from DSCO. Use this when products are missing or out of sync. Disable after the resync completes. |
Inventory settings
| Setting | Description |
|---|---|
| Report inventory totals from Pipe17 to dedicated CommerceHub location | Aggregates all inventory in Pipe17 and reports it to the selected DSCO location. |
| Process only inventory with specific product SKUs patterns | Restricts inventory updates to the SKU patterns you specify. |
| Force inventory resync | Forces a full resync of inventory from DSCO. Use this when inventory levels appear stale or incorrect. Disable after the resync completes. |
Flows
| Flow | Direction | Notes |
|---|---|---|
| Orders | DSCO → Pipe17 | Pipe17 pulls orders in Pending shipment and Canceled statuses by default. |
| Product catalog | Bidirectional | Pull from DSCO or push from a connected source such as Shopify. |
| Inventory updates | Bidirectional | Pull from DSCO or push from a connected 3PL or IMS. |
| Fulfillments and tracking | Pipe17 → DSCO | Pushes tracking information originating from your 3PL back to DSCO. |
Channel SKU mapping: This connector supports SKU mapping between Pipe17 and DSCO. If your DSCO product identifiers differ from those used in your other channels, configure Channel SKU values in Channel Options to ensure accurate product matching across flows.
Troubleshooting
-
Orders are not appearing in Pipe17 after connecting
The most common cause is that the order does not have a shipment created in DSCO. Open the order in DSCO and click SHIP in the top-right corner to create a shipment, then wait for Pipe17 to pull the order on the next sync cycle. -
Orders assigned to a DSCO warehouse are not pulling into Pipe17
Warehouse-based order routing requires Pull locations from CommerceHub to be enabled so the app can see your DSCO warehouse locations. Once locations are pulled, confirm the relevant warehouse is linked to a fulfillment location in Pipe17. Alternatively, disable Pull only orders allocated to warehouses tied with fulfillment locations in Pipe17 to pull all orders regardless of warehouse assignment. -
Authorization does not complete or the CommerceHub tab closes without connecting
This typically occurs if the authorization window is closed before the process completes, or if your CommerceHub session has expired. Return to the Integrations page in Pipe17, locate the CommerceHub DSCO connector, and click Connect again to restart the OAuth flow. Ensure you are logged in to your CommerceHub account before attempting to authorize. -
Products or inventory appear missing or out of sync
Use the Force product catalog resync or Force inventory resync toggles in the connector settings to trigger a full resync from DSCO. Disable these toggles again after the resync completes. -
Account is active in DSCO but orders are not being routed
If you see a yellow banner at the top of your DSCO account, your onboarding process is not complete. Pipe17 cannot pull orders from an account that has not completed DSCO onboarding. Contact your DSCO representative to complete this process. -
Connector shows "Not Configured" or "Error" status after connecting
Return to Integrations, locate the CommerceHub DSCO connector, and click Connect to restart the OAuth authorization flow. If the error persists after a successful authorization, contact the Pipe17 support team.
Need Help?
If you need additional assistance:
- Use Ask Pippen, our AI agent, located at the top of the app page.
- Submit a support request with as much relevant detail as possible. Learn how to submit a request.
- For urgent issues, email us directly at support@pipe17.com.
We're here to help you succeed with your operations.
Comments
0 comments