Connect CommerceHub OrderStream to Odoo
Run your retailer dropship program out of Odoo instead of the OrderStream web portal and a spreadsheet.
First, which OrderStream are we talking about
CommerceHub OrderStream is the platform big-box retailers assign to their dropship suppliers. If you sell through Home Depot, Lowe's, Costco, Best Buy, or a similar program, OrderStream is likely how they hand you orders and how you confirm shipments back.
Two things confuse people searching for this. First, CommerceHub merged with ChannelAdvisor and the combined company rebranded as Rithum in 2023, so you will see all three names used for the same ecosystem. Second, OrderStream and Dsco are siblings, not competitors: OrderStream is the older EDI-based system, Dsco is the newer API-first platform. Which one you are on determines how the integration gets built.
On Dsco rather than OrderStream? The buyer is the same and the business problem is the same, but the build differs. See our Odoo Dsco integration page.
How the connection actually works
OrderStream is an EDI platform. Connections run over SFTP with XML payloads, and you will need a set of identifiers from CommerceHub and your retailer before anything can be built: the SFTP host and credentials, your Partner ID, the retailer's Partner ID, your Vendor ID, and your Warehouse or Facility ID.
The documents that move between you and the retailer are standard EDI transaction sets:
| Document | Direction | What it carries |
|---|---|---|
| 850 | Retailer to you | Purchase order. Becomes a sales order in Odoo. |
| 855 / 997 | You to retailer | Acknowledgement. Confirms you received and accepted the order. |
| 856 | You to retailer | Advance ship notice with tracking. The one that causes the most trouble. |
| 810 | You to retailer | Invoice. Has to reconcile against the original 850. |
| 846 | You to retailer | Inventory advice. Keeps the retailer from selling what you do not have. |
Worth knowing up front: Odoo has no native ANSI X12 EDI support. Anyone who tells you this is a configuration exercise is selling you something. The work is a connector module, middleware, or a purpose-built integration against Odoo's API, and which of those is right depends on your volume and how many retailers you serve.
Common OrderStream integration issues
These are the problems that cost dropship suppliers real money. Most are cheap to prevent during scoping and expensive to fix after go-live.
Late or missing shipment confirmations (856)
This is the single largest source of retailer deductions. The physical package can go out perfectly on time, but if the ASN is late, missing, or does not match what shipped, the chargeback is automatic. Drop-ship compliance windows are measured in hours, not days, so a confirmation that waits for someone to run a batch at end of day is already too slow.
Inventory feeds (846) that go stale
Retailers generally expect an inventory advice at least once per business day, and more often for fast-moving SKUs. A feed that runs nightly while your warehouse sells all day means you accept orders you cannot fill. Cancellations follow, and cancellation rate is exactly what retailers score you on.
Partial acknowledgements falling back to manual work
Automated acknowledgement handling commonly covers full acknowledgements only. The moment you need to accept part of an order and reject the rest, someone has to go into the CommerceHub web portal and do it by hand. Teams discover this in week one of go-live rather than during scoping.
Invoice (810) and purchase order (850) mismatches
If the invoice does not reconcile to the original PO on quantity, price, or line detail, payment stalls and your accounts receivable team starts chasing. This is usually a mapping problem rather than a data problem, and it is much cheaper to fix before go-live.
SKU and UPC data that is not ready
OrderStream is explicitly not plug-and-play on product data. SKUs and identifiers have to be correct on both sides before the connection is activated. In practice this is where most projects lose time, because it surfaces catalog problems that predate the integration.
Warehouse and facility ID mapping
Your Warehouse or Facility ID has to land in the right field, and it is not always where you would expect. Get it wrong and orders route to the wrong location or fail validation outright.
Every retailer is a little different
You are not integrating with OrderStream once. You are integrating with Home Depot's rules, then Lowe's, then Costco. Each retailer can require a different document subset, different lead times, different labeling. Budgeting for one integration and getting three is a common surprise.
Packing slips are not part of the sync
Branded packing slips generally have to be pulled or generated separately rather than arriving with the order data. Worth deciding early how that fits your pick and pack process rather than bolting it on later.
Dropship only, not B2B
These connections carry dropship orders. If you also sell into the same retailer on a bulk purchase order basis, that is a separate flow, and assuming one covers both leads to an unpleasant discovery.
Test to production cutover
OrderStream separates test and production by hostname. The change itself is trivial, but the credentials are worth saving carefully, since they are not always reissued readily when you onboard your next retailer.
Industry estimates put EDI-related retailer chargebacks at roughly 1 to 5 percent of gross invoice value. On $2 million of annual dropship revenue that is $20,000 to $100,000 a year, which is usually more than the integration costs.
How we approach it
- Confirm the platform and the retailers. OrderStream or Dsco, and which retailer programs. This changes the scope more than anything else.
- Audit the product data. SKUs and identifiers have to be right before a connection is activated. We would rather find the problems here than during go-live.
- Map the documents to Odoo. The 850 becomes a sales order, the 856 fires off the delivery, the 810 follows the invoice, the 846 reports real availability.
- Build with failure in mind. Every sync logs what it did and alerts a human when something breaks. A silent failure on an 856 is a chargeback nobody noticed until the deduction appeared.
- Test against the test environment, then cut over. Credentials saved properly, so onboarding your next retailer is cheaper than the first.
Our team is in Mukwonago, Wisconsin. The people scoping your integration are the people building it, and nothing goes offshore.
What it costs
Any firm quoting an EDI integration without looking at your retailer requirements and your product data is guessing. We start with a paid 4-hour Discovery at $260, where we review your retailer documentation, your catalog, and your order volume. You leave with a real scope and a real number whether or not you continue with us.
A single-retailer OrderStream connection typically lands between our Essentials pack (25 hours, $1,550) and Core pack (50 hours, $2,900). Additional retailers on the same connection cost meaningfully less, because the Odoo side is already built. Hours run $65 down to $50 as the packs get larger.
Connecting something else? We integrate Odoo with marketplaces, carriers, payment processors, and accounting systems.
All Odoo integrationsTalk through your OrderStream setup
Bring your retailer list, your order volume, and your current process. We will tell you what the integration should cost and whether it is worth building.
Schedule a Consultation