If you run Dynamics 365 Business Central and sell on Shopify, you don't need to buy an integration to get started. Microsoft ships a Shopify connector inside Business Central online at no extra cost, it's open source, and the 2026 releases closed several of the gaps we used to fill by hand. This is our field guide as of September 2026: what it does well, the deadline most teams don't know about, what's arriving in October, and the point at which a custom layer still earns its keep.
What it covers out of the box
The connector synchronizes the core loop of an online store with the ERP:
- Products and variants — items in Business Central become Shopify products (or the reverse), with prices, images per variant, custom collections, and product options generated from item attributes. Metafields sync both ways through a public façade, which is how structured product facts reach your storefront and any AI shopping agent reading it.
- Inventory — stock per Business Central location pushed to one or more Shopify locations, with a choice of calculation methods. Since April the connector uses Shopify's current inventory mutation, treats Business Central as the source of truth, retries on concurrency errors, and logs anything it had to skip.
- Orders — Shopify orders from the online store, POS and B2B imported as sales documents, with payments, fulfillments, payouts (now carrying an external trace ID for reconciliation) and refunds flowing back. Sales documents can be created in the checkout currency.
- Customers and companies — mapped or created on import. As of July 8, 2026, B2B company sync works on every Shopify plan, not just Plus.
It's built on Shopify's GraphQL Admin API, it lives in Microsoft's BCApps repository, and it exposes integration events plus stable public façade codeunits (orders, metafields, products) so partners can extend it without forking it. That last point matters: most “the connector can't do X” problems are a small extension, not a replacement.
The deadline: December 31, 2026
This is the one that bites quiet, well-run stores. Shopify releases a new API version every quarter and supports each for twelve months. The connector pins a version and adopts the next one only in Business Central major releases. Fall behind on Business Central updates and the pinned version eventually reaches end of support — calls get blocked and synchronization simply stops.
Where that stands today: the connector in Business Central 2026 release wave 1 (April 2026) uses Shopify API 2026-01, which Shopify supports until December 31, 2026. To stay connected into January you must be on 2026 release wave 2, which reaches general availability in the first week of October. The previous cliff was July 1, 2026, and we still meet environments that discovered it the hard way. If your BC admin has been deferring updates, check the connector's API version on the Shopify Shop Card today; it's item one on our Microsoft integration audits.
One more reason not to wait: Shopify is moving apps to expiring offline access tokens. The October connector supports them (tokens refresh automatically, refresh tokens last up to 90 days, and an admin reconnects the shop if that window lapses). Older connectors don't.
What's arriving in October
The 2026 release wave 2 connector has been in public preview since early September and goes live in the first week of October. The changes worth knowing about:
- B2B catalogs and pricing, natively. Company sync, B2B order processing and market catalogs are available on all Shopify plans (up to three active market catalog assignments on Basic, Grow and Advanced; unlimited on Plus). Direct company catalogs and staff-member mapping need Advanced or Plus. Company tax IDs map to the right registration fields, and the connector now stops you from syncing the same catalog's prices twice.
- A Tax Matching Agent for US stores. Imported Shopify tax lines get matched to Business Central tax jurisdictions with a confidence level and a review page. It suggests and maps; it does not calculate tax or decide liability, and Microsoft is explicit that you remain responsible for approving the result.
- Exchanges handled properly. A return with a replacement item lands on one credit memo or return order, and you can split the replacement onto its own document. You also choose whether refunds become credit memos or sales return orders — the latter is what warehouse teams needed.
- Your Shopify order number as the BC document number, plus a review step for the sell-to, ship-to and bill-to contacts before a sales document is created.
- Tariff numbers and country of origin synced, which matters now that duty rules are changing in several markets.
- Operational cues. Skipped Records and API Errors tiles on the activities page, a filtered errors view in the log, and syncs that skip a bad unit-of-measure combination instead of halting the whole run.
Note that Microsoft stopped publishing release plans in September 2026; new capabilities now appear on the AI at Work roadmap. Whoever owns your connector should know where to look.
Where teams still get stuck
- Which stock number is the truth. The connector can push different stock calculations. Pick one deliberately — projected available versus free inventory — because pushing the wrong number is how you oversell during a sale. And note a Shopify-side change from August 5: inventory held by draft orders and transfers moved from the “reserved” state to “committed”. If a report or app on your side was reading “reserved”, its numbers dropped without anything being wrong.
- Multiple stores. The connector supports several Shopify shops per environment, but pricing, customer mapping and location routing per shop need to be designed, not defaulted.
- Negotiated pricing that moves. Native B2B catalogs cover a lot now. What they don't cover is a rate card that changes mid-contract, tiers that depend on year-to-date volume, or a distributor who must see two price lists at once. That's still a small extension plus disciplined catalog setup.
- Returns versus refunds. Refunds and exchanges are handled; Shopify's return objects themselves are still not processed by the connector. If your returns flow starts in Shopify, plan the hand-off.
- Ownership. Somebody has to watch the job queue, the error cues and the quarterly API calendar. Connectors don't fail loudly; they fail as “why is that order not in BC?” three days later.
When custom is warranted
Go beyond the connector when the business rule doesn't fit its model, not because someone says “the native thing is basic”. Real examples from our work: configure-to-order products where the bill of materials is only known at checkout; three-way flows where Salesforce owns the account, Business Central owns the invoice and Shopify owns the cart; and Shopify changes that ripple into accounting — since September 9, an app updating an unfulfilled order's shipping address triggers a tax recalculation, so amended totals have to be reconciled, not assumed. In each case we keep the connector for what it does well and add an event-driven layer for the rest.
The connector doesn't cover the other Dynamics 365 apps — Sales, Supply Chain Management, Finance and Operations. If your ERP is F&O rather than Business Central, this article isn't your path; that's an integration project from day one.
One more reason to treat the October update as a project rather than a click: the same release removes the ability to publish Microsoft's standard pages as SOAP web services. If a custom Shopify bridge was built years ago against the Customer or Item card over SOAP, it stops working with update 29, and the fix is moving it to API pages or OData. We find one of these in more environments than you would expect, usually where "the connector" turned out to be a consultant's script.
Our short checklist
- Confirm the connector's pinned Shopify API version and book the 2026 release wave 2 update before December 31.
- Decide the single stock calculation you'll trust, and check whether anything on your side still reads Shopify's “reserved” quantity.
- Choose how refunds should land — credit memo or sales return order — with the warehouse team in the room.
- Map customers, companies and tax IDs deliberately, especially for B2B and POS.
- Name an owner for the job queue, the error cues and the API calendar.
- Inventory any older integration that reaches Business Central over SOAP against standard pages; update 29 removes that path.
- List the rules that don't fit — and only then scope custom work.
We're a Microsoft Partner and we build on both sides of this connector. If you'd like us to review your setup before the December deadline, start with our Microsoft services or integrations, or book a free consultation. If your business is B2B or industrial, the B2B & industrial page covers the quote-to-cash side.