Business Central and Shopify Integration: Connector Scope, Sync Design and Pitfalls
A technical reference for ecommerce businesses on Business Central: what Microsoft's Shopify Connector synchronizes, who should own each data set, where AL extensions are needed, the failure points in variants, tax, refunds, stock and B2B pricing, and how other webshops connect through the Business Central APIs.
Microsoft's standard Shopify Connector, preinstalled in Business Central online, synchronizes products and variants, customers and B2B companies, orders with their payments, refunds and returns, fulfilments, inventory levels and Shopify Payments payouts. Stock always flows from Business Central to Shopify, while products can be mastered in either system. AL extensions come in where the standard mapping stops: products with a matrix of two or more variant options, item attributes as structured data, custom stock calculations, B2B pricing beyond catalogs and price groups, and order rules a storefront app adds. The usual failure points are variant and SKU mapping, tax recalculated in Business Central, refunds, multi-location stock and B2B pricing. Solzet delivers this remotely from Yerevan.
What does the standard Shopify Connector synchronize with Business Central?
The Shopify Connector is Microsoft's own app for Business Central online, and it connects one or more Shopify stores, each with its own settings on a Shopify Shop Card. Microsoft's Shopify Connector overview lists the scope: products, inventory, customers, orders, fulfilments, transactions and payouts. The table summarises the direction of each flow as documented on Microsoft Learn, so you can see what is configuration and what is left for an extension or a process.
| Data | Direction | What the connector does |
|---|---|---|
| Items, products and variants | Either way, set by the Sync Item field | Exports or imports items with variants, images, barcodes, tags and metafields. Item attributes, extended text and marketing text are exported into the Shopify description (items). |
| Prices | Business Central to Shopify | Calculates the storefront price from the unit price, a customer price group, a customer discount group and the currency, and supports catalogs for B2B companies and markets. |
| Inventory | Business Central to Shopify | Sends calculated availability per Shopify location, using Projected Available Balance at Today or Free Inventory (not reserved), filtered by Business Central location (inventory). |
| Customers and B2B companies | Either way | Maps customers by email and phone and B2B companies by tax or registration number, with templates per country or region for new customers. |
| Orders | Shopify to Business Central | Imports online store, Shopify POS and B2B orders with shipping costs, gift cards, payment terms and transactions, then creates a sales order, or a sales invoice for orders already fulfilled (orders). |
| Returns and refunds | Shopify to Business Central | Blank, Import Only, or Auto Create Sales Document, which creates a sales credit memo or a sales return order. |
| Fulfilments | Business Central to Shopify | Marks the Shopify order as fulfilled from the posted shipment, with shipping agent and tracking details. |
| Transactions and payouts | Shopify to Business Central | Imports order transactions and Shopify Payments payout information for reconciliation (transactions and payouts). |
| Posted sales invoices | Business Central to Shopify | Exports posted invoices so buyers see them in their Shopify account. |
Which system should own products, prices, customers and stock?
Decide the system of record for each data set before anything is switched on, because the connector will faithfully copy whatever the setup tells it to. Microsoft's own advice on the items page is the starting point: if names, descriptions and prices are managed in Business Central, choose To Shopify; if the merchandising team maintains product content in Shopify and Business Central only needs items for order processing, choose From Shopify. Inventory is different. Microsoft describes Business Central as the system of record for stock, and the connector only sends availability to Shopify.
We write the ownership down as a short table in the design: products and content, prices and discounts, customers, B2B companies and their locations, stock, orders, refunds, payments and invoices, with the owning system and the sync schedule for each. That table is what the job queue entries, the SKU mapping and the extensions are then built from.
- Products: usually Business Central for distributors and manufacturers, Shopify for brands whose merchandising team lives in Shopify.
- Prices: Business Central when price groups, discount groups or B2B catalogs drive the storefront.
- Stock: Business Central, always, calculated per location filter.
- Customers: imported with orders, or a default customer for anonymous web sales, decided per shop.
- Orders, refunds and payouts: Shopify is the source, Business Central is where they are posted.
Where do you need AL extensions on top of the Shopify Connector?
The connector is extensible by design, and Microsoft documents extension points for stock calculation, metafield mapping and order processing. We add AL extensions only where the standard behaviour does not match the business, and we build them so they survive both Business Central updates and new connector versions. The Business Central AL development page explains how we build and test extensions in general; the list below is what typically drives them on a Shopify project.
- Variant matrices: Business Central has no option matrix, so the connector uses the variant code as the only option and cannot create a variant for a Shopify product that combines two or more options, such as colour and size. Catalogues built that way need a mapping extension or a different product design.
- Item attributes as data: the connector exports attributes as a table inside the description. Filters, size charts and specification fields in the storefront need attributes mapped to Shopify metafields through the extensibility model.
- Custom stock calculation: the two standard methods do not cover safety stock per channel, stock held for B2B or availability across a component bundle. A custom stock calculation is added as an extension.
- B2B pricing: customer price groups, discount groups and catalogs cover standard cases. Contract prices per company location, quantity breaks or prices from a separate pricing engine need an extension.
- Order rules: order attributes, tags or storefront app data that should drive the location, dimensions, the salesperson or a hold on the order.
- Bundles: products from bundle apps that block inventory updates through the API, usually mapped to non-inventory items with the components handled in Business Central.
What usually goes wrong in a Business Central and Shopify integration?
Almost every problem we see on a Shopify integration is a setup decision taken too late rather than a defect in the connector. The table lists the failure points we test for before go-live, with the behaviour Microsoft documents and the fix we design in.
| Failure point | What happens | What we do about it |
|---|---|---|
| Variants and SKU mapping | With SKU Mapping set to Item No., each Shopify variant becomes a separate item; with the wrong separator or empty SKUs, imports create duplicates or fail to map. | Choose Item No. + Variant Code or Barcode deliberately, clean SKUs in Shopify first, and test a full catalogue import in a sandbox. |
| Item attributes | Attributes arrive in Shopify as a table in the description, not as filterable fields. | Decide which attributes the storefront needs as metafields and map them in an extension. |
| Tax and VAT | Taxes on imported orders are recalculated when the sales document is created, so wrong VAT posting setup or tax areas give totals that differ from Shopify. Prices Including VAT follows the Shopify order. | Align VAT business and product posting groups, set Tax area priority, and reconcile order totals against Shopify on test orders for every tax case. |
| Refunds and returns | A credit memo or return order is only created if the original order was already processed into a Business Central document; order edits can import zero-amount refunds that cannot become credit memos. | Process orders before refunds arrive, choose Process Returns as per shop, set the refund G/L accounts and the return location priority, and test partial refunds and restocking. |
| Multi-location stock | A new Shopify location has no inventory records for existing products, and a Shopify line split across two locations becomes one Business Central line with one location. | Assign inventory to new locations in Shopify, decide between Shopify locations and the Business Central Fulfillment Service, and design how split shipments are posted. |
| Units of measure | With UoM as Variant, availability is shared across the unit variants and can be briefly wrong in Shopify between syncs. | Use it only where the business accepts the timing, and schedule inventory sync on the job queue. |
| B2B pricing and companies | B2B orders map through the company and its locations, with optional sell-to and bill-to customer numbers; a missing mapping stops the sales document. | Map every B2B company and location before go-live, and decide where contract prices are mastered. |
How do non-Shopify webshops integrate with Business Central?
There is no Microsoft connector for most other webshop platforms, so the integration runs through the Business Central API v2.0: standard endpoints for customers, items, sales orders, sales invoices and more, with OAuth through Microsoft Entra ID. Where the standard endpoints do not expose what the shop needs, we add custom API pages in an AL extension, and we use webhook subscriptions so the shop learns about changes instead of polling for them.
The design questions are the same as for Shopify: who owns products, prices and stock, which documents an order becomes, how refunds and returns are posted, and how failed messages are retried and reconciled. For a platform with an established Marketplace (AppSource) connector, we assess that app against your processes before building anything. If the webshop also feeds a CRM, our CRM and ERP integration page covers how customer and order data flows between Business Central and Dynamics 365 Customer Engagement or a custom CRM.
How does Solzet run a Business Central and Shopify integration project?
A Shopify integration is usually part of a Business Central implementation or added to a live Business Central, and the Dynamics 365 Business Central page explains how we implement the wider system. The integration itself follows a fixed sequence, with every decision written down so it can be reviewed by your finance and ecommerce teams.
- Assessment: shops, markets and currencies, catalogue and variant structure, locations and fulfilment, tax cases, payment providers, B2B customers and the apps installed in Shopify.
- Design: the ownership table, SKU mapping, stock calculation and location filters, order, refund and return settings, G/L accounts and the job queue schedule.
- Build: connector configuration per shop, and AL extensions for variants, metafields, stock, pricing or order rules where the design calls for them.
- Test: a sandbox connected to a Shopify development store, with test orders for every tax case, partial fulfilment, split locations, partial and full refunds, returns, gift cards and B2B orders.
- Go live: catalogue sync, opening stock, a cutover window for open orders, and monitoring of Shopify log entries and the job queue in the first weeks.
- Support: connector version changes, new shops or markets, and extension updates as Business Central and Shopify release changes.
Do you need a UK-based partner for Business Central and Shopify?
No local presence is needed for the work itself. Business Central online runs in the Microsoft cloud and Shopify is a hosted platform, so the whole integration is designed, built and tested remotely. Solzet is headquartered in Yerevan, Armenia, and delivers remotely: we have no UK office. Our working day overlaps with the UK and continental Europe, so workshops, testing and go-live support happen in your business hours, and the same senior consultants and developers who design the integration build the extensions and stay through support.
We recommend the right solution: Dynamics 365 (Customer Engagement, Business Central or Finance and Operations), Power Platform, or a custom-built CRM. One team for CRM, ERP and the integration between them.
What do people ask us?
What does the Business Central Shopify Connector synchronize?
Products and variants with images, barcodes and metafields, prices, inventory levels per location, customers and B2B companies, orders from the online store, Shopify POS and B2B, returns and refunds, fulfilments, transactions and Shopify Payments payouts, and posted sales invoices. Stock flows from Business Central to Shopify; products and customers can sync either way.
Is the Shopify Connector included with Business Central?
It is a Microsoft app for Business Central online and Microsoft states that it is preinstalled for new sign-ups and trials. Each Shopify store is connected on its own Shopify Shop Card with its own settings. Licensing for Business Central and Shopify is separate and set by each vendor.
When do you need AL extensions for a Shopify integration?
When products combine two or more variant options, when item attributes must become filterable metafields, when stock needs a custom calculation, when B2B prices go beyond price groups and catalogs, or when order data from storefront apps must drive posting. Standard cases are configuration only.
Why do order totals differ between Shopify and Business Central?
Because taxes are recalculated when the connector creates the Business Central sales document. If VAT posting groups, tax areas or the Prices Including VAT behaviour do not match how the Shopify store is set up, the totals differ. Align the tax setup and test an order for every tax case before go-live.
How are Shopify refunds and returns handled in Business Central?
Per shop you choose not to import them, to import them only, or to create sales documents automatically, either a credit memo or a sales return order. Automatic creation needs the original order to have been processed into a Business Central document first, and refund amounts not tied to items post to G/L accounts you set.
Can Business Central integrate with WooCommerce, Magento or a custom webshop?
Yes, through the Business Central API v2.0, custom API pages built in AL and webhook subscriptions, or through a Marketplace (AppSource) connector where a suitable one exists. The design questions match Shopify: data ownership, order documents, refunds and error handling.
Does Solzet have a UK office for Shopify and Business Central projects?
No. Solzet delivers remotely from Yerevan, Armenia, with a working day that overlaps the UK and continental Europe. Business Central online and Shopify are both cloud services, so the integration is designed, built, tested and supported remotely by the same senior team.
Where should you go next?
Business Central AL development
AL extensions, integrations, APIs and Marketplace apps, built to survive updates.
Dynamics 365 Business Central
Business Central online implementation, integrations and support, delivered by Solzet.
CRM and ERP integration
Customer, order and invoice flows between Business Central and Dynamics 365 or a custom CRM.
Distribution and wholesale
How Solzet approaches CRM and ERP for distributors and wholesalers.
Business Central for food distribution
Lots, expiry, FEFO picking, recalls and warehousing in Business Central.
Which solution is right for your business?
Tell us what you need. A senior consultant replies within one business day with a recommendation (Customer Engagement, Business Central, Finance and Operations, Power Platform or a custom-built CRM), not a sales script.