Introduction
Many growing companies sell through more than one door. Consumers order on a Shopify storefront, while retailers and wholesale buyers send purchase orders through Electronic Data Interchange (EDI). When these channels run in separate systems, teams re-key data, stock numbers drift, and invoices go out late. The fix is a single order flow, with Microsoft Dynamics 365 Business Central at the centre, so every order, whether it arrives from a Shopify checkout or an EDI message, ends up in one ledger with one set of inventory, pricing, and customer records. Here is how to design that flow.
This blog will cover the following points
- Why Shopify and EDI orders belong in one flow
- How Business Central handles Shopify orders
- Where EDI fits and what the E-Documents framework offers
- A simple three-layer architecture
- The data that must stay in sync
- Planning for Japan and how Sysamic can help
Why One Order Flow
Shopify and EDI solve different problems. Shopify captures online orders from consumers and increasingly from B2B buyers. EDI lets retailers and distributors exchange standard documents, such as purchase orders, advance ship notices, and invoices, without anyone typing. The risk comes when each channel keeps its own stock, prices, and customer data. A multichannel seller is safer when Business Central owns stock, pricing, credit, and financials, while Shopify and the EDI platform act as channels that feed it and read from it.
Shopify Orders in Business Central
The native Shopify connector already covers the consumer side. Orders are imported from Shopify, customers are matched by email, phone, or bill-to details, and paid orders automatically create sales orders or invoices in Business Central. Shipments post back with tracking numbers so customers are notified in Shopify. Behind the scenes, Shopify is moving its integration toward GraphQL, and the connector keeps pace with each Business Central release. Refunds, gift cards, and multi-rate taxes land in the ledger, which keeps finance aligned with the storefront.
Where EDI Fits
For trading partners who require EDI, the typical document set is familiar: an 850 purchase order arrives, an 856 advance ship notice follows shipment, an 810 invoice closes the transaction, and an 846 inventory advice may share stock levels. Business Central’s E-Documents framework supports sales and purchase invoices, purchase orders, and receipts in both directions, with status tracking, logs, and external endpoint connectors. It is built to be extended for local or industry-specific requirements. Note that Microsoft’s E-Documents localizations currently list countries such as Germany, Denmark, Norway, and Australia, but not Japan, so Japan-specific formats usually need a Marketplace app or a custom connector.
A Simple Three-Layer Architecture
Most successful designs use three layers. The channel layer includes Shopify for online orders and the retailer systems that send EDI. The integration layer is an EDI or integration platform that translates formats, enforces partner rules, and moves documents using protocols such as AS2 or SFTP. The ERP layer is Business Central, which creates sales orders, reserves stock, posts shipments and invoices, and records everything in the ledger. Keeping Business Central as the single system of record means a Shopify order and an EDI order follow the same fulfilment and invoicing path.
What Must Stay in Sync
Four data sets cause most problems when they drift. Item master data, including SKUs, descriptions, barcodes, and price tiers, should originate in Business Central. Inventory should flow from Business Central locations to Shopify locations and to EDI partners. Customer and company mapping must be consistent so repeat buyers are not duplicated. Finally, payments, credit memos, and taxes should post to the same accounts regardless of channel.
Planning for Japan
Companies selling into or from Japan face extra questions. Do your Japanese trading partners use their own EDI formats or portals? Does each invoice meet qualified invoice requirements and consumption tax rules? Are Japanese product names, addresses, and furigana handled correctly? Answer these before choosing connectors, and test with a pilot customer first.
Conclusion
One order flow turns Shopify and EDI from competing channels into a single, controlled process. With Business Central as the system of record, teams spend less time re-keying data and more time serving customers.
Sysamic K.K. is a Tokyo-based Microsoft Dynamics 365 Business Central partner with more than 20 years of experience helping international companies run compliant, well-configured ERP operations in Japan. We design Shopify and EDI integrations, configure the connector and E-Documents setup, map inventory and customer data, and align everything with Japan’s tax and invoicing rules. If you want to bring your online and wholesale orders into one flow, we would be glad to help. Email us at info@sysamic.com or fill out our contact form here to get in touch.