Tell Us What You’re Connecting
Provide the systems, workflow and business requirements.
Storefront · ERP
Connect Microsoft Business Central + BigCommerce
Automate storefront order, customer record, catalog and product attributes, availability / inventory, pricing (including customer-specific where in scope) between Microsoft Business Central and BigCommerce — with monitoring and managed support from APIWORX.
APIWORX connects the systems your business already uses and takes responsibility for the agreed integration workflows after go-live. The exact objects, direction and cadence are fixed in writing during scoping.
ERP + eCommerce Specialists
Managed & Monitored Integrations
Expert Integration Team
APIWORX Provides the Service
Yes. APIWORX connects Microsoft Business Central and BigCommerce.
But connecting the applications is only the beginning. The work that costs you time sits in the process running between them.
APIWORX automates that process end to end — the objects moving between Microsoft Business Central and BigCommerce, the ownership rules that decide which system wins, the exceptions when a record will not post, and the monitoring that tells someone before your team finds out from a customer.
How it works
From requirements to a managed integration
We Design the Integration
APIWORX recommends the integration architecture, mappings and implementation approach.
We Build, Monitor & Support It
APIWORX implements the integration and provides ongoing monitoring and support as applicable.
Who this is for
This page is for eCommerce and operations teams running BigCommerce with Dynamics 365 Business Central as the ERP.
What needs to be in place
- BigCommerce with API credentials scoped to orders, products, customers and inventory as required.
- Business Central (cloud, or on-premises with a connection path agreed in scoping).
- A Business Central service account permitted to create sales documents and read availability.
- A decision on which system owns catalog data, pricing and stock.
When you may not need this
A small store with static stock may not need managed integration. It becomes worthwhile when availability moves fast, when catalog changes are frequent, or when B2B customers expect their own pricing to be honoured on the storefront.
What is out of scope
- We do not design or maintain your BigCommerce theme or apps.
- Tax determination stays with your advisors.
- B2B pricing behaviour on the storefront depends on your BigCommerce configuration, confirmed in scoping.
What actually moves, and who owns it
A representative BigCommerce-to-Business Central scope, agreed object by object before build.
Microsoft Business CentralAPIWORX (mapping, retries, exception queue)BigCommerce
| Object | From | To | System of record | Trigger | If it fails | Owner |
|---|---|---|---|---|---|---|
| Storefront order | BigCommerce | Business Central | BigCommerce (capture) / BC (fulfilment) | Order reaches an agreed status | Held in exception queue with the mapping error | APIWORX |
| Customer record | BigCommerce | Business Central | Per agreed rule | At order creation | Order held rather than creating a duplicate customer | APIWORX (mapping) / you (master data) |
| Catalog and product attributes | Business Central or agreed source | BigCommerce | Agreed in scoping | On change, on an agreed cadence | Change held; previous values stay live | APIWORX (delivery) / you (data ownership) |
| Availability / inventory | Business Central | BigCommerce | Business Central | Scheduled publish on an agreed cadence | Last good feed remains in force; failure alerted | APIWORX |
| Pricing (including customer-specific where in scope) | Business Central | BigCommerce | Business Central | On change | Held; existing prices remain live | APIWORX (delivery) / you (pricing policy) |
| Shipment and tracking | Business Central / WMS | BigCommerce | Business Central | Shipment posted | Retried, then queued for review | APIWORX |
| Refund / credit | BigCommerce | Business Central | BigCommerce | Refund recorded | Queued for finance review | APIWORX |
Three decisions that make or break this integration
Catalog and availability direction
The first thing to settle is direction: which system is the source for each product field, and how availability reaches the storefront. Direction decided once, in writing, prevents the slow drift that makes people stop trusting the storefront.
- Field-level ownership for descriptions, pricing, weights and tax classes.
- Availability published from Business Central with location filters and optional buffers.
- Merchandising fields left in BigCommerce deliberately where marketing must own them.
- New items introduced through an agreed path rather than created on the fly.
B2B customers and customer-specific pricing
Many BigCommerce merchants sell to both consumers and trade accounts. Where trade pricing lives in Business Central, the storefront has to honour it without turning into a second pricing engine.
- Customer price groups mapped from Business Central where B2B pricing is in scope.
- Trade accounts matched to existing Business Central customers rather than duplicated.
- Payment-terms and on-account behaviour scoped explicitly, including credit checks.
- What the storefront can display is confirmed against your BigCommerce configuration.
Order flow and fulfilment status
Orders become Business Central sales documents with the references and dimensions your team already uses, and shipment status returns to the storefront so customers and support see the same picture.
- Order and payment references written to nominated Business Central fields.
- Shipping method mapped to shipping agent and service codes.
- Shipment confirmation and tracking written back to the BigCommerce order.
- Duplicate prevention keyed on the BigCommerce order ID.
Reliability and ownership
The operating rules that apply to this workflow after go-live.
- Every run is logged with the source record reference so an order or document can be traced end to end.
- Failed messages are retried on a defined schedule; anything that still fails lands in an exception queue rather than being dropped silently.
- Duplicate prevention keys on the source system's own identifier (order number, PO number, document ID).
- Exceptions are worked by the APIWORX team and escalated to your named operations contacts when a business decision is needed.
- Mapping changes — new SKUs, new locations, new partner requirements — are part of the ongoing engagement.
- Support windows and response commitments live in your agreement; this page does not state an SLA.
How an order is traced
Illustrative — not customer data
An illustrative reference trace between BigCommerce and Business Central.
| BigCommerce order ID | Business Central sales document reference |
|---|---|
| BigCommerce product SKU | Business Central item number (mapped) |
| Business Central posted shipment | BigCommerce shipment with tracking |
| BigCommerce refund | Business Central credit document |
Scope and questions
- Can Business Central drive B2B pricing on the storefront?
- Where customer price groups exist in Business Central they can be published, subject to what your BigCommerce configuration supports. This is confirmed in scoping rather than assumed.
- Do you support multiple storefronts?
- Yes. Each storefront is mapped to the locations, dimensions and pricing rules you agree.
- Is inventory published as a single number?
- That depends on your location setup and what you want customers to see. Location filters and buffers are agreed before build.
- Does this work with on-premises Business Central?
- It can, with a connection path agreed during scoping. We confirm feasibility for your environment rather than promising it upfront.
Your integration plan
Get My Integration Plan
Tell us what systems you need connected. We’ll recommend the architecture, implementation approach, timeline and estimated price range.
Ready to map your integration?
Tell us what systems you need connected. We’ll recommend the architecture, implementation approach, timeline and estimated price range.
Next step
Scope your BigCommerce + Business Central integration
Tell us your systems and documents. A specialist confirms scope by email.