Shopify Business Central Integration: Connector, APIs, and Limits

Dynamics 365 Business Central is a common next step for US and international merchants who outgrow QuickBooks, and it has an unusual advantage: Microsoft builds the Shopify integration itself. That changes the usual question from “which connector?” to “how far does the built-in connector go, and what do we do about the rest?” As on every page, documented marks statements from Microsoft or Shopify documentation, and recommendation marks our guidance.

Start with the built-in Shopify Connector

Documented: Microsoft’s Shopify Connector for Business Central synchronizes products, inventory, customers, orders, fulfillments, transactions, and payouts. Each shop has its own setup, a company can connect more than one Shopify store, and recurring synchronizations can run through the job queue. Orders are imported into Business Central sales documents, and shipments are synced back to Shopify, which marks the order fulfilled.

Documented: for inventory, Business Central is the source of truth. You enable inventory sync per Shopify location and choose a stock calculation method — Microsoft lists Projected Available Balance at Today and Free Inventory (not reserved) as the standard methods.

Documented: payouts are synced with a dedicated action, and Shopify payment gateways are mapped to Business Central payment methods (the mapping record is created automatically when orders are imported).

Recommendation: run the connector’s setup in a sandbox with a Shopify development store first, then decide what’s missing. Most gaps can be closed by extending the connector in AL (Business Central’s language) rather than replacing it, which keeps you on Microsoft’s upgrade path.

When a custom integration makes sense

Recommendation: consider custom code — either an extension to the connector or a separate service on the API — when you have:

• a 3PL or WMS between Shopify and Business Central that must own fulfillment,
• multiple ERPs or companies fed from one Shopify store with intercompany rules,
• complex bundles or configurable products that the connector’s item model can’t represent,
• B2B flows (pricing agreements, credit checks, approval steps) beyond what the connector maps.

Compare trade-offs in custom integration vs. off-the-shelf connectors.

The Business Central API for custom work

Documented: Business Central exposes a REST API (API v2.0, OData v4) under https://api.businesscentral.dynamics.com/v2.0/{tenant}/{environment}/api/v2.0/, scoped to a company — for example companies({id})/salesOrders. Authentication uses Microsoft Entra ID OAuth 2.0; unattended integrations use service-to-service authentication with the OAuth client credentials flow, after the Entra application is registered in Business Central and granted permissions.

Recommendation: create a dedicated Entra application per integration with the narrowest permission set that works, and prefer certificate credentials to client secrets for production. A separate identity per integration also makes the per-user API limits below work in your favor.

POST https://api.businesscentral.dynamics.com/v2.0/{tenant}/Production/api/v2.0/companies({companyId})/salesOrders
Authorization: Bearer {entra_access_token}
Content-Type: application/json

{
  "externalDocumentNumber": "SHOP-US-5551234",
  "customerNumber": "WEB-US",
  "orderDate": "2026-10-27"
}

Illustrative only. Add lines through the salesOrderLines navigation, and confirm field names against the API reference for your version and any extensions installed.

Avoiding duplicate orders

Documented (Shopify): Shopify webhooks can be delivered more than once.

Recommendation: Business Central’s standard API has no built-in “upsert by external key” for sales orders, so idempotency is your job:

1. Put the Shopify order ID in a stable reference such as externalDocumentNumber (with a per-store prefix).
2. Keep your own table of processed Shopify events and created Business Central IDs; check it before every create.
3. After a timeout, query sales orders filtered on that reference before retrying.
4. Use the record’s ETag (If-Match) for updates so you never overwrite a newer change.

The general technique is in preventing duplicate orders.

Webhooks from Business Central

Documented: external systems subscribe to entity changes through the api/v2.0/subscriptions endpoint. When a subscription is created, Business Central calls the notificationUrl with a validationToken query parameter, and your endpoint must return the token in the response body with status 200. Subscriptions expire after three days unless renewed with a PATCH, and each renewal repeats the handshake. Business Central waits 30 seconds after the first change to an entity before notifying, so several quick changes produce one notification; if more than 1,000 records change in that window, it sends a single collection notification that you resolve by querying with a modified-since filter.

Recommendation: run a scheduled job that renews every subscription well before expirationDateTime and alerts when a renewal fails. Treat notifications as “something changed” signals: fetch the current record, don’t trust a stale payload. Keep a reconciliation query as a safety net. See webhooks and webhooks vs. polling.

API limits

Documented: Microsoft documents per-user OData limits for Business Central online:

Limit	Value	When exceeded
Concurrent requests	5	Further requests wait in a queue
Request queue size	95	HTTP 429
Simultaneous connections	100	HTTP 429
Rate	6,000 requests per 5-minute sliding window	HTTP 429
Time waiting in queue	8 minutes	HTTP 503

Recommendation: limit your worker to a handful of parallel calls per identity, retry 429s with exponential backoff, and schedule large backfills off-hours. Because the limits are per user, a separate identity per integration keeps a catalog backfill from throttling order imports.

Inventory, fulfillment, and money

Recommendation:

• Inventory: publish available-to-sell per location; map each Shopify location to a Business Central location explicitly. Reconcile daily.
• Fulfillment: post the warehouse shipment in Business Central, then send fulfillment and tracking (UPS, FedEx, USPS) to Shopify so the customer is notified.
• Sales tax: let Shopify or your tax engine calculate tax at checkout and post the calculated amounts, rather than recalculating in Business Central — confirm the approach with your tax advisor for each state where you have nexus. See sales tax in ERP integrations.
• Payouts: reconcile Shopify Payments payouts as net deposits with fees, refunds, and adjustments booked separately. The connector’s payout sync is the starting point; see how we approach payouts in the QuickBooks Online page.

Common pitfalls

• Rebuilding what the connector already does instead of extending it.
• Expired webhook subscriptions after three days with nobody noticing.
• Duplicate sales orders because there’s no upsert and no idempotency layer.
• One shared identity for every integration, so one job’s backlog throttles all the others.
• Testing in a sandbox against production Shopify and assuming outbound syncs work — they’re blocked there.