Business Central CommerceHub integration
OpusNext connects Dynamics 365 Business Central to CommerceHub so retailer purchase orders become BC sales orders automatically, inventory feeds go out on the schedule each retailer expects, and shipment confirmations and invoices flow back without anyone re-keying them in a portal. Typical go-live is 2 to 6 weeks.
What syncs between Dynamics 365 BC and CommerceHub
| Data | Direction | What it means |
|---|---|---|
| Inventory & availability feed | BC → CommerceHub | Retailers see stock you can actually ship |
| Retailer purchase orders | CommerceHub → BC | Become BC sales orders automatically |
| Order acknowledgement | BC → CommerceHub | Acknowledged inside the retailer window |
| Shipment confirmation & tracking | BC → CommerceHub | ASN data sent from the real shipment |
| Invoices & cancellations | two-way | Exceptions handled as documents, not emails |
Where CommerceHub projects usually go wrong
The parts that decide whether this integration ages well - and how we handle them.
Dropship is a deadline business. Every retailer has its own acknowledgement and ship windows, and missing them turns into chargebacks - not warnings. A nightly batch simply cannot hit a same-day window.
Orders are picked up and acknowledged on the event, and inventory feeds are scheduled per retailer to match the window each one expects, so compliance stops depending on somebody watching a portal.
Each retailer wants your catalogue in its own language - their SKU, their cost, their attributes - while Business Central has exactly one item master. Teams end up maintaining spreadsheets per retailer, and the spreadsheets drift.
BC stays the master. The retailer-specific SKU, cost and attribute mapping lives in the integration, per channel, so you onboard a new retailer by mapping it rather than by cloning your item list.
The money is lost in the exceptions: partial shipments, backorders, cancellations and returns. These are the flows generic connectors skip, and they are exactly the ones retailers score you on.
We model the exceptions explicitly back into BC documents, so a partial ship, a cancel or a return is a real transaction in your ERP rather than a note somebody forgot to pass on.
Before you choose a CommerceHub connector
Five questions worth asking any vendor - and our answers for Dynamics 365 BC.
OpusNext: Yes. Fields added by AL extensions are read and mapped, including the ones you use for channel-specific data.
OpusNext: Retailer cost and price are held per channel against a single BC item master, so nothing is duplicated or re-keyed.
OpusNext: Event-driven for orders and acknowledgements; inventory feeds are scheduled to each retailer window.
OpusNext: No. We connect directly to Business Central through its official APIs - no separate middleware to license or host.
OpusNext: We use the official APIs on the BC side, and the mapping re-checks itself when your BC schema or version changes.
CommerceHub and Microsoft Dynamics 365 Business Central - common questions
Can we sell to several retailers through CommerceHub from one Business Central?+
Yes. Each retailer is a channel with its own SKU, cost and attribute mapping against a single BC item master.
How do you help avoid chargebacks?+
Orders are acknowledged on the event and inventory feeds are scheduled to each retailer window, so the deadlines that drive chargebacks are met by the system rather than by hand.
Are partial shipments, cancellations and returns supported?+
Yes. They are written back into Business Central as real documents rather than being handled outside the ERP.
Do we still need to work in the portal?+
The routine flows - orders in, acknowledgement, shipment and invoice out - run automatically, so portal work becomes the exception rather than the daily job.
How often is inventory sent?+
As frequently as the retailer expects. Feed frequency is configured per channel rather than one nightly job for everyone.
Other Dynamics 365 BC integrations
Connect CommerceHub to your Dynamics 365 BC.
Book a demo - we will map your data live.
احجز عرضًا تجريبيًا