CommerceHub - Configure for Automated Fulfillment

Documentation Team · Updated May 31, 2026 19:42

DropStream connects your CommerceHub drop-ship feed to a warehouse management system so orders flow automatically from retailer to shipment, and stock levels stay in sync without manual intervention.

What this integration does

Imports orders from your CommerceHub retailer feed into DropStream.
Forwards orders to your warehouse management system, with line items mapped by SKU.
Posts fulfillment status back to CommerceHub when the warehouse ships, including tracking numbers and carrier information.
Pushes inventory updates from the warehouse to CommerceHub.

What you’ll need

A CommerceHub account, with access to the CommerceHub setups portal.
Your CommerceHub FTP Username, FTP Password, Hub Retailer ID, and Hub Partner ID.
A DropStream account. If you don’t have one yet, contact your DropStream administrator or fulfillment provider.

Setup at a glance

The setup involves work on two sides — CommerceHub, then DropStream — and the recommended order is:

Partner Setup (in CommerceHub) — confirm you can sign in to the CommerceHub setups portal, and gather your login.
Get your API credentials (in CommerceHub) — collect your FTP credentials and Hub Retailer/Partner IDs from your CommerceHub representative.
Enable API access (in DropStream) — add the store through the Add Connection wizard and enter your CommerceHub credentials.

Who does what

If you manage your own DropStream account, you’ll do every step yourself — switching between CommerceHub and DropStream as the article order suggests.
If a third-party fulfillment provider is configuring DropStream for you, you only need Get your API credentials. Send the resulting credentials to your provider; they handle the rest.

Notes and limitations

CommerceHub feeds require provisioning — they aren’t fully self-serve. Request credentials from your CommerceHub representative and let DropStream Support know you’re adding a CommerceHub store.
The integration runs over CommerceHub’s FTP/EDI feed; there’s no OAuth or API token to manage on the DropStream side beyond the FTP credentials and Hub IDs.