Business Central 29 brings an interesting change to the way we should think about ERP integration. For years, companies have treated integrations as something that gets built once and then quietly runs in the background:
But modern commerce does not work that way anymore.
Shopify changes its APIs. Retailers change their EDI requirements. 3PLs introduce new interfaces. ERP platforms evolve their integration frameworks. And suddenly, an integration that worked perfectly two years ago becomes a maintenance problem.
Business Central 29 makes this particularly interesting because two critical areas are moving forward at the same time:
- Business Central is expanding its E-Documents framework to support standardized EDI document exchange.
- The Business Central Shopify Connector is moving alongside Shopify's rapidly evolving GraphQL API platform.
For businesses already running Shopify and Dynamics 365 Business Central together, this is worth paying close attention to.
Business Central Already Had Electronic Data Exchange
It is important to clarify one thing first: EDI is not suddenly appearing in Business Central with version 29.
Business Central has supported electronic data exchange for years through capabilities such as the Data Exchange Framework, extensions, and external EDI provider services.
For example, a distributor could receive an electronic purchase order from a retailer:
Retailer → EDI Provider / Middleware → Business Central
The EDI provider or middleware could translate the retailer's document into a format Business Central could process. The same could happen in the opposite direction:
Business Central Invoice → EDI Provider → Retailer
So companies could absolutely run EDI integrations with Business Central before BC 29. The difference is that Microsoft is continuing to bring electronic document scenarios into a more standardized E-Documents framework.
What BC 29 Changes
Business Central 29 explicitly adds the ability to exchange EDI documents through E-Documents using the Peppol BIS 3 EDI standard.
That means EDI is becoming more directly connected to the E-Documents architecture rather than being treated purely as an external integration problem.
This is an important evolution, but it should not be confused with Business Central becoming a complete replacement for an enterprise EDI platform.
Business Central still connects to external access points and service providers for electronic document exchange. Microsoft currently documents integrations with certified providers including Pagero, Avalara, Logiq, SignUp, and B2BRouter.
The better way to understand the change is:
Before BC 29
Retailer │ │ EDI ▼ EDI Provider / Middleware │ │ Transformation ▼ Business Central
With BC 29 E-Documents
Retailer / Business Partner
│
│ EDI / Electronic Document
▼
External Access Point
│
▼
Business Central E-Documents
│
▼
Sales / Purchase / Payment Documents
The external access point does not disappear. Instead, Business Central has a more standardized framework for managing the electronic-document side of the ERP process. That is a meaningful architectural improvement.
Consider a Real Retail Example
Imagine a manufacturer selling through a national retail chain. The retailer sends an electronic purchase order:
- EDI 850 — Purchase Order: Business Central receives the order and creates the corresponding sales document.
- EDI 855 — Purchase Order Acknowledgement: The manufacturer validates inventory commitments and confirms line items.
- EDI 856 — Advance Ship Notice (ASN): When goods ship, logistics dispatch data is sent with UCC-128 barcode details.
- EDI 810 — Invoice: Post-shipment financial settlement sent directly into the retailer's accounts payable engine.
Historically, much of the complexity around these exchanges had to sit in an external EDI platform, custom integration, or middleware layer. With the expanding E-Documents capabilities in Business Central, more of the document lifecycle can be represented within Microsoft's standardized electronic-document architecture.
That does not eliminate the need for integration engineering. It changes where the integration boundary sits — and that distinction is important.
Now Add Shopify to the Picture
This becomes even more interesting for companies running Shopify + Business Central because Shopify is also changing the integration layer underneath the commerce platform.
Shopify has moved its Admin API strategy decisively toward GraphQL, with the REST Admin API classified as legacy since October 1, 2024. Shopify recommends that new integrations use the GraphQL Admin API.
Shopify also versions its APIs aggressively. A Shopify API version is supported for a limited period, meaning an integration cannot simply be written once and forgotten. Shopify's documentation states that API versions are released every three months and supported for 12 months.
That has a direct consequence for Business Central customers.
What Happens to a Shopify + Business Central Integration?
Suppose a company originally implemented:
Shopify → Business Central Shopify Connector → Business Central
The company may think: "The integration is finished." Technically, it isn't.
Shopify continues evolving its API. Business Central therefore has to keep its Shopify Connector aligned with Shopify's supported API versions. Microsoft's Shopify Connector documentation says the connector primarily uses Shopify's GraphQL Admin API, adopting newer Shopify API versions through Business Central major releases.
Microsoft has specifically highlighted this in the Business Central 29 release: the Shopify integration is updated to use Shopify's July 2026 API, along with secure access tokens and improved synchronization diagnostics.
That means BC 29 is particularly relevant to companies whose Shopify store is connected to Business Central.
Why This Matters to Existing Shopify + Business Central Customers
Consider a company running an older Business Central release. Its architecture might look perfectly healthy today:
Shopify │ ▼ Shopify Connector │ ▼ Business Central ├── Inventory ├── Sales Orders ├── Customers └── Fulfillment
Nothing appears broken on the surface. But the Shopify API underneath the connector continues to move forward.
Microsoft explicitly warns that if an older connector remains tied to an API version after Shopify's support window ends, synchronization can eventually stop working.
So the problem isn't necessarily: "Our Shopify integration is broken."
It may eventually become: "Our ERP connector is running against an API version that Shopify no longer supports."
That is a very different kind of integration problem — and one that requires proactive architectural governance.
BC 29 Also Brings More Shopify Capabilities
The Shopify changes in BC 29 are not limited to API compatibility. Microsoft's BC 29 release notes include capabilities around:
- Shopify B2B Companies: Native mapping for multi-location B2B accounts and ordering rules.
- Catalogs and Pricing: Multi-tiered customer pricing and specialized B2B catalog synchronization.
- Tax Matching: Improved automated tax reconciliation across state and regional jurisdictions.
- Order Changes: Dynamic processing for modified orders, line cancellations, and checkout updates.
- Exchanges and Refunds: Direct reconciliation of credit memos and returns in Business Central.
- Tariff Numbers & Country/Region of Origin: Cross-border compliance fields mapped to customs data.
- Improved Synchronization Diagnostics: Granular error logging and self-healing sync retries.
- The Updated Shopify API Version: Support for the latest GraphQL specifications.
This is important because Shopify is increasingly becoming more than a storefront. For many businesses, Shopify is becoming part of the commercial operating system, while Business Central remains the operational and financial system of record.
The integration between them therefore becomes strategically important, often warranting dedicated ERP support and optimization.
The Bigger Architecture: Modern Omnichannel Commerce
Now consider a modern commerce company with multiple sales and logistics channels:
┌── Shopify Plus
│
├── Amazon
│
├── Retailers / EDI
│
├── 3PL / WMS
│
└── CRM
│
▼
Integration Layer
│
┌──────┴──────┐
│ │
Business Central F&O
│ │
└──────┬──────┘
│
▼
Data / Fabric
│
▼
Power BI / AI
This is where integration architecture becomes more important than any individual connector.
Shopify can change its APIs. Retailers can change their EDI requirements. A 3PL can change its interface. An ERP can change its APIs.
A good integration architecture creates enough separation between these systems that one platform's change does not become everyone's emergency.
This Is Where Enterprise iPaaS Becomes Relevant
This is also why modern integration platforms and Azure Integration Services become interesting.
Instead of building dozens of fragile point-to-point connections:
3PL ———————————————— Business Central
EDI ———————————————— Business Central
CRM ———————————————— Business Central
Legacy DB ———————————— Business Central
You can introduce a resilient enterprise integration layer:
Shopify
│
EDI / 3PL
│
CRM
│
Legacy Systems
│
▼
┌───────────────────────┐
│ Enterprise Integration│
│ Layer │
│ │
│ APIs / Events / Queues│
│ Transformation / EDI │
│ Monitoring / Security │
└───────────┬───────────┘
│
┌─────┴─────┐
▼ ▼
Business Central F&O
│ │
└─────┬─────┘
▼
Fabric
That layer can use different technologies depending on the requirement, including APIs, Logic Apps, Service Bus, Functions, API Management, and external EDI services.
The point isn't to introduce technology for its own sake. The point is to decouple business systems from each other's changes.
So What Should Businesses Using Shopify + Business Central Do?
The answer is not necessarily: "Upgrade to BC 29 immediately."
The right question is: "Which version of the Shopify API is our connector using, when does that API version reach end of support, and what capabilities do we need from the newer connector?"
Microsoft's documentation explicitly recommends keeping the Shopify Connector current because Shopify's API versions evolve and older versions eventually lose support. For an existing implementation, an integration review should therefore look at:
- Shopify API version: Which Shopify API version is the current connector using?
- Business Central version: Is the Business Central release still aligned with the supported Shopify Connector?
- Authentication: Are the Shopify credentials and access-token model current?
- Synchronization: Are inventory, products, customers, and orders synchronizing correctly?
- B2B requirements: Are Shopify B2B catalogs, pricing, and customer/company structures being synchronized correctly?
- Returns and order changes: Does the current integration correctly handle exchanges, refunds, and modified orders?
- EDI: Does the business need retailer or 3PL EDI? If so, should EDI be handled directly through the newer Business Central E-Documents capabilities, an external provider, or a broader integration layer?
- Architecture: What happens when Shopify changes its API again?
That last question is perhaps the most important one.
The Real Lesson From BC 29
Business Central 29 is not simply giving businesses "EDI." And it is not simply giving them "a new Shopify connector." It demonstrates something much bigger:
Enterprise integrations are becoming living systems.
ERP platforms evolve. Commerce platforms evolve. EDI standards evolve. APIs evolve. The integration architecture has to evolve with them.
For a company running Shopify and Business Central, BC 29 is therefore worth looking at not merely as an ERP upgrade, but as an integration architecture checkpoint.
The question shouldn't only be: "Does our integration work today?"
It should be: "Is our integration architecture designed to keep working when Shopify, Business Central, our EDI network, or our downstream systems change tomorrow?"
That is the difference between an integration that merely connects two systems and an integration architecture built for the enterprise.
Final Thought
Business Central is increasingly becoming better equipped to participate directly in modern electronic-document workflows, while Shopify is simultaneously moving toward a more aggressively versioned GraphQL-based API ecosystem.
For businesses using both platforms, that convergence makes integration architecture increasingly important.
The ERP is no longer an isolated system. The commerce platform is no longer an isolated storefront. And the integration between them is no longer just plumbing — it is part of the business architecture.