Business Central & NAV / Business Central integrations
Business Central integrations built around how your business works.
Your business does not stop at the edge of Microsoft Dynamics 365 Business Central. We design and build integrations that connect BC with external applications, trading partners, and operational systems, using the architecture that fits the requirements rather than forcing every problem into the same connector or tool.
Engagement types
What we connect to Business Central
These are categories of integration work, not a claim to a packaged connector for every named platform.
Ecommerce & marketplaces
Orders, customers, inventory availability, and fulfillment status between storefronts or marketplaces such as Amazon, Shopify, and TikTok and BC.
EDI & trading-partner transactions
Purchase orders, acknowledgments, ship notices, and invoices with retail and supply-chain partners.
Warehouse & fulfillment systems
Pick, pack, ship, and inventory movements exchanged with WMS and 3PL platforms.
Payments & transaction reconciliation
Payment capture, settlement data, and the application and reconciliation of those payments in BC.
Customer & operator portals
Web applications that surface live BC data — orders, invoices, shipments, documents — without ERP licenses for every user.
Custom applications
Line-of-business applications that need to read from or post into BC reliably.
Legacy-system connections
Older systems that still run part of the business and need a maintained bridge to BC.
Approach
Standard connectors when they fit. Custom engineering when they don't.
For integrations that need more control over data mapping, business rules, exception handling, or processing, we use .NET middleware and SQL-based data processing alongside Business Central APIs and targeted AL extensions. Where a standard connector or Power Platform flow adequately solves the problem, there is no reason to add unnecessary custom software.
The middleware runs outside Business Central. SQL is used where it belongs: extracting from source systems, staging and transforming data outside BC, and reconciling results. Anything written into Business Central goes through its supported APIs and the application logic that validates and posts it. Targeted AL extensions cover BC-side APIs, validation, and behavior the standard surface does not expose.
An integration isn't finished when the API returns success. It's finished when the business transaction is correct.
Design requirements
What a dependable integration has to do
Requirements we design for in each engagement, sized to what the integration actually needs — not a universal prebuilt platform.
Visible failures
Errors surface where someone will see them, not in a silent queue.
Controlled retries
Transient failures retry deliberately; permanent ones stop and report.
Duplicate prevention
A replayed message does not become a second order or a double posting.
Traceable transactions
Every record in BC can be traced back to what arrived, when, and from where.
Maintainable mappings
Field mappings and business rules live where they can be read and changed.
Verified business results
The check is whether the order, payment, or posting is correct — not whether the call succeeded.
How it runs
An integration engagement, step by step
Understand the systems and the transaction flow
What moves, in which direction, triggered by what, and what it has to become in BC.
Agree mappings, scope, and acceptance criteria
Which fields, which rules, which exceptions — and how we'll know it's right.
Build and test the connection
Middleware, API work, and any BC extension, tested against realistic data.
Validate the business outcome
Postings, balances, and documents checked in BC, not just message counts.
Agree deployment, documentation, and support
Who runs it, who is called when it fails, and what is handed over. You own the code and documentation we produce.
Questions
Common questions.
We already work with a Microsoft partner. Can you work alongside them?+
Yes. The integration can be a defined workstream next to your existing team, with responsibilities and acceptance criteria agreed up front. We don't need to replace anyone to do the integration work well.
How do you decide between a standard connector and custom middleware?+
By the requirements: how much control the mapping, business rules, exception handling, and processing need. If a standard connector or Power Platform flow handles it adequately, that's my recommendation. If it doesn't, .NET middleware with supported BC APIs and targeted AL is usually the right shape.
Can you improve an existing integration rather than replace it?+
Often, yes. The starting point is understanding what it does today, where it fails, and what the business needs it to do. Where a targeted repair or extension gets there, that is usually better than starting over.
What about ongoing support?+
Support responsibilities are agreed as part of the engagement — who monitors, who responds, and how changes are handled. We don't publish a blanket SLA; the arrangement is defined for the integration in question.
Related work
Evidence from consulting engagements and in-house roles.
Consulting engagement (current)
NAV-to-Business Central upgrade with EDI and marketplace integrations
International CPG manufacturer and distributor
Upgrading from Dynamics NAV to Business Central, with customer EDI through TrueCommerce, custom AS2 for vendors, and Amazon, Shopify, and TikTok store integrations built on .NET APIs and AL extensions.
Consulting engagement
Business Central customer portal with document integration
Built a full-stack customer-facing portal surfacing live Business Central data through the BC API, with SharePoint document integration via the Microsoft Graph API.
→ Customers self-serve on live ERP data with zero ERP licenses issued to customers.
In-house role · Consulting engagement
Amazon Seller and EDI order processing into NAV
Built an end-to-end order processing pipeline from Amazon Seller Central and EDI transaction sets into NAV — automating order intake, inventory updates, and fulfillment acknowledgment.
→ Multi-partner orders processed automatically into NAV without manual re-entry.
Already working with a Microsoft partner or MSP? We can take on an agreed integration, EDI, migration, or remediation workstream alongside your existing team.
Start the conversation
Tell me what needs to connect, migrate, or work better.
Describe the systems involved and what you're trying to accomplish. I review every inquiry personally and will tell you directly whether the project is a fit.
Discuss an integration