+1 480 485 7373
Microsoft Teams
Start with the business process, not the connector
The first question is never which tool to buy. It is which process crosses the boundary between systems: an order placed online, a deal marked won in the CRM, a payroll run, a bank deposit. Write down who starts it, which system should hold each piece of data, and what a person should do when the two sides disagree.
Once that is on paper, the method usually picks itself. A common process with a maintained app on AppSource rarely justifies custom code. A process that touches three or four systems often suits an integration platform. An unusual rule that only your business has is where a custom API integration earns its cost.
Four ways to connect Business Central, compared
Questions to answer before any build starts
- ✓Which system is the master for each field, not just each record
- ✓Does data move in real time, on a schedule, or once a day
- ✓What happens to a record that fails, and who sees the error
- ✓Which volumes and peaks the link must handle, such as holiday orders
- ✓How tax, discounts, shipping and fees post to the general ledger
- ✓Whether a manual export would honestly be good enough for now
Business Central integration guides
Business Central + Shopify →
Integration design for Shopify and Business Central beyond the standard app: multiple stores, B2B, marketplaces, custom data and payout reconciliation.
Business Central + Amazon →
Connecting Amazon Seller Central to Business Central: FBA and FBM inventory, order import, settlement reports and fee reconciliation.
Business Central + BigCommerce →
Connecting BigCommerce to Business Central: catalog, price lists, B2B Edition accounts, orders, inventory and customers.
Questions about connecting Business Central
Does Business Central have an API?
Yes, Business Central Online exposes REST APIs based on OData for customers, vendors, items, sales and purchase documents, journals and more. Developers can also publish custom API pages through an AL extension when a standard endpoint does not cover a table. That is what most connectors, integration platforms and custom builds use under the hood.
Should we buy a connector or have one built?
Buy first when a maintained connector covers your process, because someone else absorbs the upkeep when either system changes. Build when your rules are genuinely unusual or no connector exists. We usually test a connector against your real edge cases before recommending either path.
Who fixes an integration when it breaks?
Someone named in writing before go-live, and that is part of the design, not an afterthought. Every integration we set up has an error log a person checks, an alert for failures, and a documented way to resend a failed record. Ongoing monitoring can sit with your team or with our support service.
Can one integration project connect several systems at once?
Yes, but we normally phase it so each link is proven before the next one starts. Orders and inventory usually come first because they touch revenue every day. Reporting and document links tend to follow once the transactional data is reliable.
Talk to us about your project.
Tell us what you run today and what has to change. A senior consultant replies with a written next step.