As eCommerce businesses grow, managing orders, inventory, customers and financial data across separate systems becomes increasingly difficult.
Shopify manages the online buying experience, while Microsoft Dynamics 365 Business Central manages inventory, purchasing, warehousing, fulfilment and financial operations. Without a reliable connection between the two platforms, teams can become dependent on spreadsheets, manual data entry and disconnected operational processes.
Integrating Shopify with Microsoft Dynamics 365 Business Central can automate the movement of data between eCommerce and the ERP. However, the success of the integration depends on more than simply installing a connector.
Retailers need to determine which system owns each type of data, how frequently information should synchronise, how exceptions will be managed and whether the standard integration supports their B2C and B2B requirements.
This guide explains the key considerations when integrating Shopify with Microsoft Dynamics 365 Business Central.
What is Microsoft Dynamics 365 Business Central?
Microsoft Dynamics 365 Business Central is an enterprise resource planning platform designed to help small and mid-sized organisations manage core business operations.
It can support areas including:
- Financial management
- Purchasing and procurement
- Inventory management
- Warehousing
- Order management
- Manufacturing
- Supply planning
- Customer management
- Reporting and business intelligence
For an eCommerce retailer, Business Central will commonly act as the operational and financial system of record.
Shopify, by comparison, manages the customer-facing commerce experience. This includes product discovery, merchandising, checkout, promotions, customer accounts and online order capture.
When the two platforms are integrated effectively, Shopify can provide the commerce experience while Business Central manages many of the operational processes required to fulfil and account for each sale.
Can Shopify integrate with Microsoft Dynamics 365 Business Central?
Microsoft provides an official Shopify Connector for Dynamics 365 Business Central.
The connector is designed to synchronise data such as products, inventory, customers, sales orders, transactions and payouts between Shopify and Business Central. Microsoft describes the integration as a way to connect Shopify commerce activity with Business Central’s finance, sales and operational capabilities.
The connector can provide a strong starting point, particularly for businesses with relatively standard data and fulfilment requirements.
However, the availability of an official connector does not necessarily mean that every implementation will be straightforward.
Complexity can increase when a retailer has:
- Multiple Shopify stores
- Multiple Business Central companies
- Several warehouses or fulfilment locations
- Complex product variants
- Bundles, kits or bills of materials
- Customer-specific pricing
- Shopify B2B requirements
- Multiple currencies or regions
- Existing middleware or third-party systems
- Custom fulfilment processes
- Advanced returns or refund workflows
- High order volumes
- Legacy or inconsistent ERP data
The right integration approach should therefore be selected according to the retailer’s operational model, rather than simply choosing the fastest connector to install.
Why integrate Shopify with Business Central?
A successful Shopify and Business Central integration can reduce manual administration while creating a more reliable flow of information across the business.
Automate order processing
Shopify orders can be transferred into Business Central without requiring staff to manually re-enter customer, product and payment information.
Once created in Business Central, the order can move through the retailer’s normal operational processes, including inventory allocation, picking, packing, fulfilment, invoicing and financial reporting.
Fulfilment and tracking information can then be returned to Shopify so the customer can monitor their delivery.
Improve inventory accuracy
Business Central will often be the source of truth for available inventory.
Inventory levels can be synchronised with Shopify to reduce the risk of customers purchasing products that are not available.
This becomes particularly important when inventory is shared across:
- Online stores
- Physical stores
- Wholesale channels
- Marketplaces
- Sales teams
- Multiple warehouses
The integration must define how available-to-sell inventory is calculated. Simply sending the total quantity on hand may not be appropriate if some stock has already been allocated, reserved or quarantined.
Reduce duplicate data entry
Without integration, teams may need to manually maintain products, customers, orders and inventory across both platforms.
This increases operational cost and creates opportunities for errors.
Integration allows approved information to move between the systems automatically, reducing duplication and helping employees focus on higher-value work.
Improve financial visibility
By transferring Shopify orders, transactions and payout information into Business Central, finance teams can gain a clearer view of revenue, tax, payment fees, refunds and reconciliation.
The Microsoft connector includes support for synchronising transactions and payouts, although the required accounting configuration should still be reviewed carefully for each implementation.
Support scalable growth
Manual processes that are manageable at 50 orders per day can become unsustainable at 500 or 5,000 orders per day.
A properly designed integration allows an organisation to grow transaction volumes without increasing administration at the same rate.
What data should be synchronised?
One of the first integration decisions is determining which data needs to move between Shopify and Business Central.
Not every field needs to be synchronised, and not all data needs to move in both directions.
| Data type | Common source of truth | Typical integration flow |
|---|---|---|
| Products | Business Central, PIM or Shopify | ERP or PIM to Shopify |
| Product content | Shopify or PIM | PIM to Shopify |
| Product images | Shopify, PIM or Business Central | Usually to Shopify |
| Inventory | Business Central | Business Central to Shopify |
| Base pricing | Business Central | Business Central to Shopify |
| Promotional pricing | Shopify or Business Central | Depends on business rules |
| B2B pricing | Business Central | Business Central to Shopify |
| Customers | Shopify or Business Central | Often bidirectional |
| B2B companies | Business Central or Shopify | Often bidirectional |
| Orders | Shopify | Shopify to Business Central |
| Fulfilments | Business Central or warehouse system | Business Central to Shopify |
| Tracking numbers | Business Central, WMS or carrier | Operational system to Shopify |
| Refunds | Shopify or Business Central | Depends on process |
| Payouts | Shopify | Shopify to Business Central |
The correct ownership model depends on the organisation.
For example, Business Central may own commercial product data such as SKUs, cost prices and inventory. Shopify may own SEO titles, merchandising content, collection assignments and online media.
Trying to make Business Central the source of every field simply because it is the ERP can create unnecessary restrictions for the eCommerce team.
Product and inventory integration
Microsoft’s Shopify Connector can synchronise Business Central items with Shopify products and variants. It can also synchronise product pricing, images and inventory-related information.
Before enabling product synchronisation, the business should establish clear rules for:
- SKU structure
- Product and variant identifiers
- Units of measure
- Barcodes
- Product status
- Product descriptions
- Images
- Pricing
- Tax configuration
- Inventory locations
- Discontinued products
Matching products by name is unreliable. A stable identifier, generally a SKU or ERP item number, should be used across both systems.
The integration also needs to determine what happens when a product is:
- Added in Business Central
- Updated in Shopify
- Discontinued in the ERP
- Out of stock
- Replaced by another item
- Sold as part of a bundle
- Available online but not through other channels
These rules should be established during discovery rather than decided after synchronisation issues begin appearing.
Shopify order integration
Shopify orders will generally flow into Business Central so they can be processed alongside orders from other channels.
The integration may need to map:
- Shopify order number
- Customer details
- Billing and shipping addresses
- Product lines
- Discounts
- Gift cards
- Shipping charges
- Taxes
- Payment method
- Payment status
- Fulfilment status
- Shopify store or market
- Sales channel
- B2B company
- Purchase order number
- Payment terms
Microsoft’s connector can import orders created through several Shopify sales channels, including online stores, Shopify POS and B2B.
However, the organisation still needs to decide when an order should enter Business Central.
Potential triggers include:
- When the order is created
- When payment is authorised
- When payment is captured
- When the order is marked as paid
- After fraud checks are completed
- After an internal approval process
- At scheduled intervals
For most retailers, sending every newly created order immediately may not be the safest approach. Orders may still be edited, cancelled, flagged as fraudulent or awaiting payment.
Customer integration
Customer integration is often more complicated than order integration.
A direct-to-consumer Shopify store may contain thousands of customers who have placed only one order. Creating a separate ERP customer record for every shopper can make Business Central difficult to manage.
Depending on the requirements, consumer orders may be assigned to:
- Individual Business Central customer records
- A generic Shopify customer account
- Customer records created only after certain criteria are met
Shopify B2B requires a different model.
In Shopify, an individual customer can be associated with a company and one or more company locations. Business Central uses customer records differently, so the mapping between Shopify customers, companies and Business Central customers must be carefully considered. Microsoft’s documentation specifically notes this difference in data structure.
Integrating Shopify B2B with Business Central
Shopify B2B can be integrated with ERP and CRM systems to synchronise company accounts, orders, inventory, catalogues, pricing and customer data. Shopify’s native B2B functionality is available on Shopify Plus.
A Shopify B2B and Business Central integration may need to support:
- Company accounts
- Multiple company locations
- Approved buyers
- Customer-specific catalogues
- Contract pricing
- Quantity breaks
- Payment terms
- Tax identifiers
- Purchase order numbers
- Credit limits
- Sales representatives
- Order approvals
- Invoice payments
- Account-level shipping rules
Microsoft has progressively expanded the connector’s support for Shopify B2B, including company locations, payment terms, tax identifiers and customer-specific catalogue pricing.
Even with this support, the data model should be validated against the business’s real B2B requirements.
For example, one Business Central customer may have multiple delivery addresses, buyers, price lists and account rules. These relationships need to map correctly to Shopify companies and company locations.
Native connector, middleware or custom integration?
There are three main approaches to integrating Shopify with Microsoft Dynamics 365 Business Central.
1. Microsoft’s Shopify Connector
The official connector may be appropriate when:
- The business uses relatively standard Business Central processes
- Product and order structures are straightforward
- Limited transformation of data is required
- The connector supports the required B2C or B2B workflows
- The business is comfortable operating within its configuration model
The native connector can reduce implementation effort and provides a Microsoft-supported foundation.
However, it should still be tested against real products, customers, orders, fulfilments, refunds and exception scenarios.
2. Integration middleware
Middleware provides an intermediate layer between Shopify and Business Central.
This can be appropriate when:
- Multiple systems are involved
- Data needs to be transformed
- Several Shopify stores connect to one ERP
- One Shopify store connects to multiple ERP companies
- Integration monitoring is required
- Complex routing or workflow rules apply
- The business expects to add more sales channels
Middleware can centralise integration logic instead of placing it entirely within Shopify or Business Central.
It can also provide queues, retry mechanisms and monitoring tools that help operational teams identify failed transactions.
3. Custom integration
A custom integration may be appropriate when the retailer has specialised requirements that are not well supported by an existing connector.
Examples include:
- Complex B2B pricing
- Custom product configuration
- Advanced order splitting
- Bespoke warehouse routing
- Multiple ERP companies
- Custom credit processes
- Non-standard returns
- Special inventory calculations
- High-volume event-driven processing
Custom does not necessarily mean building every component from scratch.
Microsoft allows developers to extend the Shopify Connector and supports hybrid approaches where additional functionality is built around its existing capabilities.
This can allow a business to retain supported connector functionality while adding specific logic where required.
Common Shopify and Business Central integration mistakes
Failing to define the source of truth
Every important data field should have a clearly defined owner.
Without this, one system may continually overwrite changes made in another.
Synchronising too much data
More synchronisation is not always better.
Only information required by the receiving system should be transferred. Unnecessary bidirectional synchronisation increases complexity and the risk of conflicts.
Ignoring exception handling
Integrations will eventually encounter invalid addresses, missing SKUs, unavailable products, API interruptions or unexpected order data.
The important question is not whether an exception will happen. It is whether the business can identify and resolve it quickly.
Using total inventory instead of available inventory
Inventory sent to Shopify should usually represent what is available to sell, not simply the physical quantity recorded in a warehouse.
The calculation may need to account for reservations, open orders, safety stock and inventory allocated to other channels.
Underestimating B2B complexity
B2B integration is not simply B2C integration with different prices.
Company hierarchies, buyers, locations, payment terms, customer catalogues, tax settings and approval workflows all need to be considered.
Treating the connector as the complete solution
Installing a connector does not define the business rules, clean the data or test operational edge cases.
The connector is one component of the overall solution.
How should integration errors be managed?
Integration monitoring should be included from the beginning of the project.
A robust integration should provide:
- Transaction logging
- Clear error messages
- Automatic retry processes
- Alerts for repeated failures
- A queue of unresolved transactions
- Visibility for operational users
- Correlation between Shopify and ERP records
- Protection against duplicate processing
Errors should not remain hidden inside a scheduled integration process.
For example, if an order cannot enter Business Central because its SKU is missing, the relevant team should be alerted before the order misses its fulfilment target.
Operational visibility is especially important during peak sales periods when order volumes and customer expectations are highest.
How often should Shopify and Business Central synchronise?
Different data types may require different synchronisation frequencies.
Inventory might need to update every few minutes, while product descriptions may only need to update several times per day.
Orders may be transferred:
- In near real time
- Every few minutes
- On a scheduled batch
- After reaching a defined status
The correct frequency depends on:
- Order volume
- Inventory availability
- API limits
- Operational urgency
- Warehouse processes
- Customer expectations
- The number of connected systems
Near-real-time integration is valuable when the business needs rapid inventory and order updates. However, it also requires strong exception handling and monitoring.
Shopify and Business Central integration checklist
Before implementation begins, the retailer should be able to answer the following questions:
- Which system owns products, inventory, pricing and customer data?
- What identifiers will connect records across the platforms?
- Which Shopify stores and Business Central companies are involved?
- How will multiple warehouses and Shopify locations be mapped?
- How should available-to-sell inventory be calculated?
- When should Shopify orders enter Business Central?
- How will cancellations, edits, refunds and returns be handled?
- How will consumer customer records be created?
- Are Shopify B2B companies and company locations required?
- How will contract pricing and payment terms synchronise?
- Which system creates fulfilments and tracking details?
- How will transactions and payouts be reconciled?
- What happens when synchronisation fails?
- Who is responsible for investigating integration errors?
- How will the integration be tested before launch?
Is the native Shopify Connector enough?
For some businesses, the standard Microsoft connector may provide most or all of the required functionality.
For others, it may be better used as a foundation that is extended with middleware or custom logic.
The decision should be based on a detailed review of:
- Data structures
- Order workflows
- Inventory rules
- B2B requirements
- Finance processes
- Fulfilment operations
- Integration volumes
- Exception scenarios
A proof of concept using real business data can help confirm whether the connector supports the required operating model before the full implementation begins.
Planning asuccessful Shopify and Business Central integration
A successful integration project should begin with discovery and data mapping, not development.
The discovery process should document:
- Current systems
- Future-state architecture
- Data ownership
- Integration flows
- Field mappings
- Business rules
- Timing requirements
- Failure scenarios
- Security requirements
- Testing criteria
The integration should then be tested using realistic scenarios, including:
- New and existing customers
- Guest orders
- B2B orders
- Discounted orders
- Partial fulfilments
- Split shipments
- Order cancellations
- Refunds
- Out-of-stock products
- Invalid product mappings
- Failed payments
- Duplicate messages
This reduces the risk of discovering critical operational gaps after launch.
Shopify and Microsoft Dynamics 365 integration services
Shopify and Microsoft Dynamics 365 Business Central can provide a strong platform combination for growing retailers, wholesalers and manufacturers.
Shopify delivers the customer-facing commerce experience, while Business Central manages operational and financial processes behind the transaction.
The greatest value comes when the integration reflects the way the business actually operates.
OSE designs and develops Shopify and Shopify Plus solutions integrated with ERP, inventory, warehouse, finance and customer systems. Our approach includes integration discovery, solution architecture, data mapping, development, testing, deployment and ongoing support.
Whether the right solution uses Microsoft’s native Shopify Connector, integration middleware, custom development or a hybrid architecture, the objective is the same: create a reliable flow of data that supports the business as it grows.
