When re-keying orders and untangling payments starts taking too much of the week, you have five common options for connecting Shopify and Business Central. The right choice depends on the work your business needs done, who will support it and what you want to own.
We are an integration firm, so one of those options is us. Our starting point is still check what the native connector already covers. You should not pay someone to rebuild a connection that already fits.
These options can overlap. Your BC partner might configure the native connector, an integration firm might connect the warehouse, and an internal team might own day-to-day support.
Option 1: the native Microsoft Shopify connector
Microsoft’s Shopify connector supports more than one Shopify shop, product and stock synchronisation, orders and fulfilment information. It also handles gift-card and refund information and imports Shopify Payments payout information. Multiple storefronts alone are not a reason to rule it out.
The useful test is whether it supports your complete process, in the Business Central version and setup you run. Ask your BC partner to walk through an ordinary order, a refund, a split payment and the eventual bank deposit, using examples from your business.
For example, Microsoft distinguishes between importing payout information and reconciling it. Imported payout records do not themselves post to the general or bank ledger. The connector also provides payment-transaction tools; you still need to check how fees, refunds and settlements fit your accounting process.
If the native connector meets the Shopify-to-BC need, use it. A separate warehouse connection or a specific business rule can be addressed without replacing everything that already works.
Option 2: an integration platform (iPaaS)
An integration platform as a service, or iPaaS, provides tools and connectors for moving information between systems. It can suit a business that wants to build around an existing platform and its supported connections. Some providers also bring specialist retailer EDI capabilities, the electronic document exchanges suppliers need.
Compare the service as well as the connector list. Who builds and maintains the flows? Does the subscription include support for a failed order, or only access to the platform? How does pricing change with volume, and what can you take with you if you leave?
A platform and an integration firm can work together. One can carry the retailer connection while the other handles how those documents reach the ERP. The important part is that responsibilities meet without a gap.
Option 3: hire a developer
Hiring can make sense when integration is a sustained stream of work and you want that capability inside the business. An internal developer can build up detailed knowledge of your operations and work closely with the people using the systems.
Budget for the whole responsibility: development, testing, documentation, maintenance and cover when someone is away. A hire is not, by itself, a support model. Whoever builds the integration, another person needs enough access and knowledge to pick it up.
This option is easier to justify when the ongoing workload supports the role, not just when the first project looks expensive.
Option 4: your BC partner
Your ERP partner knows your Business Central setup and should be part of the conversation. They may be well placed to configure the native connector, handle work within BC or deliver the wider integration themselves.
Ask about the whole route from checkout to fulfilment, not just the BC end. Who owns a problem that crosses Shopify, the ERP and a 3PL? Who coordinates the investigation when each system shows a different status?
This is not an either-or choice. We work alongside implementation partners by design, never take on the ERP implementation and put that boundary in writing. Your existing partner can stay at the table.
Option 5: an integration firm
An integration firm focuses on the connections between systems and the work needed to keep them running. It can be a good fit when your requirements cross several vendors or go beyond the standard paths.
Ask any firm, including us:
- What will we own, and which accounts will it run in?
- What is included in the price, and how are changes to scope agreed?
- Who supports it after go-live, and what response times are in writing?
- What documentation and access would another provider need to take over?
- Can you show relevant experience with our systems and business rules?
At Inite, that means code and platform accounts you own, fixed-price packages and a shared conversation with your team and other vendors. Kori helps investigate issues, with people responsible for the work that needs human judgement. The Care Plan scope and response commitments are in writing.
Choosing
Before comparing proposals, choose a few examples for every provider to work through: a standard sale, a partial refund, an order paid partly by gift card and a delayed warehouse update. Include what finance needs to see when the payout lands.
That makes the comparison about your working day, rather than whose feature list is longest. Start with the native connector, identify the gaps and choose who should own each one. Our Shopify and Business Central page explains how we approach the pair.
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 involves us or the tools and partners you already have.
