Shopify + Business Central: Build a Working Shop in 45 Minutes
- 25 kwi
- 6 minut(y) czytania
A practical walkthrough of connecting Shopify to Microsoft Dynamics 365 Business Central — from empty item list to live order — and the pitfalls that trip up every first-time implementation.
If you've ever sat through an e-commerce integration project, you know the pattern: three months of planning, two months of configuration, and one month of everyone arguing about why the inventory numbers don't match. It doesn't have to be that way. Business Central's native Shopify connector has matured to the point where a competent consultant can build a functional shop in under an hour — provided they know which switches to flip and, more importantly, which traps to avoid.
This article walks through the whole round trip: setting up a Shopify store, connecting it to Business Central, getting products and orders flowing in both directions, and sidestepping the nine mistakes that cause 90% of the support tickets.
Why Shopify in the first place
Shopify is an all-in-one e-commerce platform for creating, managing, and growing an online store without needing advanced technical skills. For a Business Central customer evaluating it, the pitch comes down to six things:
Easy to start — you can have a storefront online the same day you sign up
Built-in payments and checkout — no separate payment gateway project
Everything in one place — products, orders, customers, marketing
Scales with your business — the same platform serves hobby shops and nine-figure retailers
Apps and integrations — a vast ecosystem, including the first-party BC connector
Built for selling — it's opinionated in ways that reduce decision fatigue
What Shopify gives you is a website to sell from, a catalog to list physical or digital products in, a checkout that accepts payments, and tools to manage orders, inventory, and customers. What Business Central gives you is the financial and operational system of record behind all of that. Connecting the two lets each do what it does best.
The 45-minute blueprint
Here's the workflow, in the order you should actually do it:
Prepare the product list in Business Central
Create the Shopify store
Connect the two
Push products from BC to Shopify
Place a test order
Watch it flow back
Each step is small. The trick is doing them in the right order.
Step 1 — Build the product list in Business Central
Start where your inventory actually lives. Create the items in BC first, with the attributes that matter for the storefront — category, color, size, brand, whatever is relevant to your catalog. Item attributes are what Shopify will consume as product options and filters later, so the time you spend here directly shapes how browsable the shop feels.
For any reasonable catalog, don't do this by hand. Use a configuration package to bulk-load the item list from Excel. A configuration package is the boring, reliable way to get dozens or hundreds of items into BC consistently — with the correct unit of measure, base price, item category, and attributes in every row. This is the single biggest time-saver in the whole setup.
Step 2 — Create the Shopify store
On the Shopify side, the setup is almost too easy. Sign up, pick a theme, and you have a storefront. For integration work specifically, there's a detail worth knowing: use shopify.dev to skip the payments configuration while you're still discovering the platform. Development stores give you everything you need to test the integration without having to register a real payment processor or enter tax information.
Once the store exists, the real work is on the BC side — setting up the Shopify connector, creating a Shopify Shop record, and entering the credentials that let BC talk to the store's API.
Step 3 — Push products from BC to Shopify
With both sides ready, Business Central can create the Shopify products directly from the item list. The Add Items action in the Shopify Shop page is the one to use — it takes the BC items you've prepared and pushes them into Shopify, complete with attributes mapped to variants, prices, and inventory levels.
This is where most implementations go wrong for the first time, which is why the pitfall list below is worth reading before you click the button.
Step 4 — Place a test order
With products live in Shopify, buy something. Place a real order through the storefront (dev stores let you use test card numbers), and watch Business Central pick it up as a sales order through the sync. This is the moment of truth — if products, prices, customer, and quantity all flow correctly, you have a working integration. If any of them don't, one of the pitfalls below is the reason.
The nine common pitfalls
These are the issues that show up in real projects over and over. None of them are hard to fix — but all of them are easy to miss until something goes wrong in production.
1. Inventory location mismatch
Business Central and Shopify each have their own concept of "where stock lives." If the locations aren't aligned — or if you haven't mapped the BC location to a Shopify location at all — inventory counts will look right in one system and wrong in the other. Fix this before you sync a single item.
2. Not enabling "Track Quantity" in Shopify
If Shopify isn't tracking quantity for a product, the inventory field in BC might as well not exist for that item. The storefront will happily sell 200 of something you have 3 of. Enable Track Quantity on every item that has physical stock.
3. Variants not mapped correctly
Item attributes in BC become variants in Shopify — but only if the mapping is set up cleanly. A shirt with three colors and four sizes should be one Shopify product with twelve variants, not twelve separate products. Get this wrong and your catalog becomes a mess nobody wants to clean up later.
4. Multiple locations in BC without rules
If your BC tenant uses several warehouses and you haven't told the connector which location Shopify orders should draw from, the system will guess — and it will guess wrong at least some of the time. Configure a default location (or explicit rules) before orders start flowing.
5. Posting shipment before Shopify sync
Posting a shipment in BC before the order has fully synced to Shopify breaks the link between the two records. Shopify ends up thinking the order is still open; BC thinks it's shipped. Let the sync complete first.
6. Editing orders in Shopify after sync
Once a Shopify order has come into BC, treat the BC record as the source of truth. Editing the order back in Shopify — changing quantities, swapping line items, adjusting prices — creates mismatches that are painful to reconcile. If a change is needed after sync, make it in BC.
7. Prices controlled in two places
Either Business Central owns prices or Shopify does. Pick one. If a merchandiser changes a price in Shopify and a pricing engine in BC recalculates it a minute later, you get a tug-of-war nobody wins. Usually BC is the right master, but the important thing is making a decision and sticking to it.
8. Missing Shopify item mapping
Every item that should be sellable online needs an explicit mapping between its BC record and its Shopify product. Items without a mapping are invisible to the sync — they'll silently fail to update and nobody will notice until a customer complaint.
9. Returns created in wrong system
Returns are the mirror image of the posting-shipment problem. If a return is opened in Shopify but processed in BC (or vice versa) without a clear policy, financial records and inventory records drift apart. Decide where returns live, document it, and train the team accordingly.
Best practices for the integration itself
Two habits make a real difference when you're implementing or troubleshooting:
Use shopify.dev development stores to skip payments. Real payment configuration is a distraction during discovery. Development stores let you test the full flow — product sync, order sync, inventory updates, fulfillment — without ever entering a credit card number.
For demos and troubleshooting, temporarily disable background synchronization and enable full logging mode. The background sync is great for production because it's invisible. That's exactly what makes it hard to debug. Turning it off during a demo means events happen when you trigger them, in an order you control. Turning on full logging means that when something does break, you have the trail to figure out why. Together, they turn "it works on my machine" into "here's exactly what happened, step by step."
Key takeaways
Start in BC, not Shopify. Build the item list with attributes first, ideally through a configuration package. Everything downstream is cleaner when the master data is clean.
The connector is genuinely good. For standard scenarios — physical goods, one warehouse, prices mastered in BC — you can be live in under an hour.
Most problems are configuration, not code. Eight of the nine pitfalls above are single settings or process rules. Get those right and the integration mostly runs itself.
Pick one master for everything. Locations, prices, order edits, returns — each needs a designated owner. Ambiguity here is the root cause of almost every data quality issue in Shopify + BC implementations.
Forty-five minutes is a real number when you know the path. The reason it takes some teams forty-five days is that they're discovering the pitfalls live, in production, with real customers watching. A little preparation changes the math considerably.
Komentarze