Three ways to connect Shopify and Business Central, and where each one stops
There are three ways to connect Shopify and Business Central: Microsoft’s native connector, your Business Central partner, and an integration firm. They are not rivals. Each covers more of the route than the one before it, and the right choice is the first one that covers your whole route.
The three options at a glance
| Native connector | Your BC partner | Integration firm | |
|---|---|---|---|
| Covers | Shopify to Business Central: products, stock, orders, refunds, payouts imported | The connector, configured and extended inside Business Central | The whole route: storefronts, ERP, 3PL, payment providers, bank |
| Stops at | Posting payouts, edited orders, the 3PL, multi-currency rounding, the API deadline | Systems outside Business Central, incidents that cross systems | The native connector stays where it fits |
| Who supports it | Your team, with Microsoft’s documentation | The partner’s service desk, within the ERP’s scope | A care plan with response times in writing, across every system on the route |
| Best fit | One or more shops, standard flows, finance comfortable with the reconciliation journal | Gaps that live in BC: posting setup, journals, mappings | Multi-brand, a 3PL or WMS, orders paid two ways, B2B paid outside checkout |
Option 1: Microsoft’s native Shopify connector
Microsoft ships the Shopify connector with Business Central online and updates it with every major release. It is the right starting point for any Shopify business on Business Central, and it covers more than most people expect.
It supports more than one Shopify shop. Each shop gets its own setup, with its own products, locations and price lists, inside the same Business Central company. A group with three storefronts and one ERP can connect all three. What else it covers today:
- Products and variants in both directions, with images, barcodes, tags and metafields.
- Stock levels sent to one or many Shopify locations.
- Orders from the online store, Shopify POS and B2B, with shipping costs, gift cards, tips, fraud risk and refund information.
- Fulfilment back to Shopify, including item tracking.
- Customers and B2B companies, matched by email, phone or tax number.
- Payouts from Shopify Payments, imported for review.
The October 2026 update (Business Central update 29.0, 2026 release wave 2) added five Shopify items:
- Control over which sales documents orders and returns create. A refund can now arrive as a return order, so the warehouse receives the goods.
- Detection of order changes, with exchanges and refunds on one document.
- B2B companies, catalogs and pricing.
- Tariff numbers and country of origin.
- Automatic renewal of the shop connection.
If that list covers your process, use it. Ask your BC partner to switch it on and walk through an ordinary order, a refund and an order paid two ways, with examples from your business.
Where the native connector stops
The limits below come from Microsoft’s own documentation. They are not flaws. They are the edge of the connector’s remit, and each one is a job somebody has to own.
1. The payout is imported, not posted. Payouts “are for information purposes only and don’t affect the General Ledger or Bank Ledger”. Finance still closes the gap between a lump-sum payout, the fees inside it and the invoices and credit memos it covers. Microsoft’s guidance names the difficulties: many invoices against one payout, and amounts that differ by the commission. There is also one payment method code per sales order, so an order paid with a gift card and a card is handled by hand.
2. An order edited after the sales document exists. The connector detects the change and marks the order, but the change is not carried into Business Central. Someone updates the documents to match, or deletes them, unlinks the order and syncs it again. A reduced quantity arrives as a zero-amount refund that cannot become a credit memo.
3. The route ends at Business Central. The connector’s remit is Shopify and Business Central. Getting a despatch request to a 3PL or warehouse system, and the confirmation and stock position back, is a separate integration. For a business that fulfils through a 3PL, that is the leg where the re-keying lives.
4. Currency differences. Orders and transactions import in the shop currency. A store selling in several currencies produces small differences between the sale and the payment transaction; Microsoft’s example is 409.53 against 409.48 DKK. Each one is a reconciliation line.
5. A version clock. Every connector release is pinned to a Shopify API version. The connector in 2026 release wave 1 uses API 2026-01, which Shopify supports until 31 December 2026; update 29.0 moves to 2026-07.
Business Central’s own update window for 29.0 runs to February 2027, so a Shopify merchant who takes the full window loses synchronisation in January. Someone has to own that date. The connector is also available for Business Central online only, not on-premises.
Option 2: your Business Central partner
Your ERP partner knows your chart of accounts, your posting setup and your locations, and should be part of the conversation. For gaps that live inside Business Central, they are often the right people to close them.
The connector is open source and built to be extended. Partners can subscribe to events for orders, products, customers, inventory, shipping and refunds, use the public façade codeunits for common operations, and replace stock calculation, customer mapping or return processing through interfaces. A partner can build a payout journal that separates fees, a rule for orders paid two ways, or a stock calculation that respects your reservations. Limits 1 and 4 above are the kind of work that belongs here.
Where it stops. The work outside Business Central: the 3PL’s API, the carrier, a retailer’s EDI channel, a second payment provider that settles on its own schedule. An extension also has to be tested against each major release, because the connector adopts a new Shopify API version every six months. And ask who owns an incident that crosses Shopify, Business Central and the warehouse, and whether the partner’s service desk carries integration support with response times, or on a best-effort basis.
Implementation partners deliver the ERP; we deliver the integrations around it, with that boundary in writing. Your partner keeps the ERP relationship and the connector configuration. Integration adds to that work; it does not replace it.
Option 3: an integration firm
When the route runs through more than two systems, or the exceptions are the business, the work is integration, not configuration. The signs:
- Multi-brand groups on one ERP.
- A 3PL or warehouse system in the middle.
- Orders paid two ways.
- B2B orders paid outside checkout.
- A finance lead who needs the payout to land in the ledger as a posting, not a list.
An integration firm is responsible for the whole route: each handover, each exception path, the reconciliation design with finance, and the operation after go-live. Ask any firm, including us, what it will own, which accounts the work runs in, what the price includes, who supports it afterwards and what another provider would need to take it over.
At Inite, the answers are the terms we work on. Delivery is fixed-price, agreed before work starts. One working channel is shared by the customer, Inite and the customer’s other vendors, including the BC partner and the 3PL. A question about a missing despatch is answered by whoever can see the despatch.
Kori, our AI Integration Support Engineer, monitors continuously and carries first-line investigation, with findings reported in the open. Every design is reviewed by a second architect. Code and platform accounts are owned by the customer, documentation is maintained as part of the work, and care plans carry response times in writing.
The native connector stays where it fits. We build around it, not over it.
How an integration firm connects Shopify and Business Central
The map below is the route we build for a Shopify business on Business Central with a 3PL. Grey is what the native connector carries. Orange is what integration adds.
- Walk one order end to end. From checkout to bank deposit, with the people who handle it today: the person re-keying, the warehouse, finance. The output is a map of every handover and where each fact lives.
- Give each fact one home. Stock on hand lives in the warehouse system or in Business Central, never both. Prices live in Business Central. Fulfilment status lives with the 3PL. Everything else is derived from the system that owns it.
- Keep the native connector where it fits. Products, stock levels and standard orders often stay native. Integration carries the rest: the 3PL leg, orders paid two ways, edited orders and the payout posting.
- Design the exceptions first. Edited and cancelled orders, partial refunds, exchanges, gift-card splits, an order the 3PL cannot fulfil. These cost finance the most time, so they are built and tested before the standard path is called done.
- Design reconciliation with finance. The payout, less fees, matched to the invoices and credit memos it covers and to the bank deposit, so the month-end match is a report, not a job.
- Test with your own orders. A standard sale, a partial refund, an order paid half by gift card, a delayed warehouse update, in a sandbox against your data, signed off by the people who do the work today.
- Go live with monitoring and ownership. Code in the customer's accounts, documentation current, continuous monitoring from the first day, and a care plan that starts when the first integration goes live.
Choosing
Before comparing proposals, choose a few examples to work through with every option. A standard sale, a partial refund, an order paid partly by gift card, a delayed warehouse update and the payout that covers them. Include what finance needs to see when the money lands, and bring the person who does the re-keying today. They know which exceptions occur.
That makes the comparison about your working day, not whose feature list is longest. Start with the native connector, name the gaps, and choose the first option that covers all of them. Our Shopify and Business Central page describes how we approach the pair.
The next step
If you want to talk those examples through, our free assessment is a one-hour conversation about your systems and future integration plans. The useful outcome is a clearer next step, whether that is the native connector, your partner or us.
