Business Central Dsco integration
OpusNext connects Dynamics 365 Business Central to Dsco so your inventory stays fresh across every retailer and marketplace, orders drop straight into BC as sales orders, and shipment and invoice data goes back automatically. Typical go-live is 2 to 6 weeks.
What syncs between Dynamics 365 BC and Dsco
| Data | Direction | What it means |
|---|---|---|
| Frequent inventory updates | BC → Dsco | Stock refreshed often enough to avoid overselling |
| Orders | Dsco → BC | Created as BC sales orders in seconds |
| Item & SKU onboarding | BC → Dsco | New items published without spreadsheets |
| Shipments & tracking | BC → Dsco | Carrier and tracking from the real shipment |
| Invoices & cancellations | two-way | Financial flows stay inside BC |
Where Dsco projects usually go wrong
The parts that decide whether this integration ages well - and how we handle them.
Dropship marketplaces punish stale inventory harder than anything else. If your availability is hours old, you oversell, cancel, and your scorecard - and your placement - suffers.
Inventory is pushed on change rather than on a nightly clock, at the frequency each trading partner expects, so what the marketplace shows is what your BC location can actually ship today.
Onboarding items is where the weeks disappear. Every partner wants its own identifiers and attribute set, and teams end up rebuilding the same catalogue in spreadsheets over and over.
Items are published from the BC master with per-partner identifier and attribute mapping held in the integration, so adding a partner is a mapping exercise rather than another catalogue rebuild.
Shipment and invoice data has to be exact and on time. Missing tracking, a wrong carrier code or a late invoice turns into a deduction, and nobody notices until the remittance arrives.
Shipment, carrier and tracking data is taken from the actual BC shipment and sent automatically, with cancellations and partials written back as documents so nothing is settled by email.
Before you choose a Dsco connector
Five questions worth asking any vendor - and our answers for Dynamics 365 BC.
OpusNext: Yes. Extension fields are read and mapped, including the ones you use for partner-specific identifiers.
OpusNext: Partner-specific cost and identifiers are mapped per channel against one BC item master.
OpusNext: Event-driven for orders and shipments; inventory pushes on change at each partner frequency.
OpusNext: No. We connect directly to Business Central through its official APIs - nothing extra to license or host.
OpusNext: Official APIs on the BC side, and the mapping re-checks itself when your BC schema or version changes.
Dsco and Microsoft Dynamics 365 Business Central - common questions
How often is inventory updated in Dsco?+
On change, at the frequency each trading partner expects, rather than on a single nightly schedule for everyone.
Do orders create sales orders in Business Central?+
Yes, within seconds, as proper customers and sales orders, so fulfilment and finance work from the ERP.
Can one Business Central serve several retailers and marketplaces?+
Yes. Each partner is a channel with its own identifiers, attributes and cost mapping against a single BC item master.
Is tracking data sent back automatically?+
Yes. Carrier and tracking come from the actual BC shipment, so partners get accurate data without anyone typing it twice.
What happens with cancellations and partial shipments?+
They are written back into Business Central as real documents, so exceptions are visible in the ERP rather than settled over email.