For manufacturers running Dynamics 365 Business Central
Business Central already holds the production orders, BOMs, routings, work centers and costing. Getting that into the report, app, workflow or outside system you actually need is the part that keeps turning into another fragile workaround. That is the part we build.
We do not replace Business Central. We build on the REST API stack Microsoft recommends, and everything runs in your tenant.
The gap
The same six symptoms show up in nearly every Business Central shop we walk into.
Planners export Business Central data to build the shortage list or the production schedule they actually work from. The ERP has the demand and the supply; the decision happens in a spreadsheet on one person’s laptop.
The plan everyone follows is the one nobody can audit
Order, shipment, quality or production information goes into Business Central and then into another system. Sometimes it goes the other way. Either way somebody is re-keying, and sometimes the two disagree.
Two systems, two numbers, one argument
A customization or integration written against Dynamics NAV still works, so it stays. Microsoft has deprecated SOAP endpoints and points new development at OData V4 and API pages, which makes that old integration a release blocker waiting to happen.
Working today, undocumented, and on a clock
What we do
Pick the one that hurts most. Most manufacturers start with reporting and one integration.
Production, shortage, late-order, WIP, purchasing and margin views built from Business Central data, without asking anyone to stitch exports together first.
In practice
A live shortage view that joins production demand, on-hand inventory and purchase supply, so a planner sees what will stop a job before the job stops. Reads come through supported endpoints, not a scrape of the client.
A focused interface for the slice of ERP data and workflow one team actually needs. Planners, operators, customer service, field service.
In practice
A customer-service screen that shows order status, promise dates and shipment history straight from Business Central, so the person on the phone never opens a full ERP role centre or consumes a full licence to read one field.
Business Central connected to CRM, quality, e-commerce, warehouse, shipping, suppliers and internal applications, through API pages and OData rather than the side door.
In practice
An outside application creates and updates records through Business Central APIs, so posting routines, dimensions and validation all run exactly as they do when a user presses the button.
An inventory of what the old integrations touch, what depends on them, and what has to move before a deprecation forces the issue.
In practice
We map each legacy endpoint, its schedule and every downstream consumer, then move the parts that need it onto OData V4 or purpose-built API pages. You get the map whether or not we do the migration.
Chatbots and assistants grounded in Business Central data and your own documents, so answers come from your records instead of a general-purpose guess.
In practice
Someone asks which jobs are short material this week. The assistant reads live Business Central data through a scoped, logged endpoint and answers with the order numbers, not a paragraph of hedging.
One place where Business Central data, spreadsheets and other operational databases resolve into the same shapes, so cross-system reporting stops being a manual reconciliation.
In practice
Reporting reads come off that layer rather than live operational screens, which keeps a heavy month-end query away from the people trying to post transactions.
Not sure which of these matters most for your company? That is what the first call is for.
Under the hood
Through the interfaces Microsoft ships and recommends. The choice depends on your version and hosting model, so we confirm it before we design anything.
30 minutes
to walk your systems before anyone proposes a build
0
direct table writes, everything posts through supported APIs
Your tenant
is where everything we build is deployed and owned
Questions
Yes, and that is the only way we do it. Microsoft recommends its REST API stack for integrations, and custom API pages and queries can expose business-specific data and operations when the standard endpoints do not cover what you need.
The integration options available to you depend on version and architecture, so the first thing we do is map what is already in place. On-premises and older NAV environments usually have more moving parts and more legacy integration, not fewer options.
Yes. Business Central supports OData V4, though Microsoft recommends REST APIs for new application integrations. Worth saying plainly: an endpoint being available does not make it a good analytics model. Most reporting problems we get called about are data-model problems, not connection problems.
Yes. Microsoft has deprecated SOAP endpoints and recommends OData V4 or API pages and queries instead. A legacy integration inventory is the sensible first step, because the risk is rarely in the integration you remember and usually in the one nobody documented.
No. Business Central stays your system of record. We build the layer on top: reporting, custom apps, integrations and automation. If somebody has told you the fix is a new ERP, get a second opinion before you sign anything.
Usually briefly, to confirm licensing and access. We are not competing with your partner for the ERP work itself. We take the projects that sit outside what a partner typically builds.
Let's talk
Thirty minutes. You walk us through how Business Central is set up and which reports people quietly gave up on. We tell you straight what we would build first, and what it would take.
Read next
Other systems we build on
SAP Business One
Production visibility, reporting and custom workflows built on SAP Business One’s Service Layer and SDK. Business One stays the system of record.
Oracle NetSuite
Manufacturing analytics, custom workflow apps and integrations built on SuiteTalk REST and SuiteAnalytics. NetSuite stays the system of record.
Infor CloudSuite Industrial (SyteLine)
IDO integrations, operational reporting and custom apps around Infor CloudSuite Industrial. Built so the next requirement does not become another Mongoose form.
SYSPRO ERP
MCP servers, custom apps, AI chatbots, and live dashboards built on SYSPRO e.net and OData. We keep SYSPRO as your system of record.
All ERP work