Dynamics 365 Business Central · Beta
Commerce Gate's Business Central extension checks sales-document release and posting against your margin floor and an agent's spend budget, and allows or blocks the document before it moves. Its source is available for review; signing, a clean sandbox check and a Marketplace preview come before general release. One company-wide setting decides what happens if Commerce Gate is unavailable; documents go through unless you change it.
Illustrative example, not a customer result
Sales order release · Automation
Business Central · Margin and agent-spend policy
The installed Business Central extension checks release and posting. The separate Dynamics 365 MCP guard checks a transaction without writing to your ERP.
Release advances a Business Central document before posting. This platform documentation does not certify a third-party extension.
What it catches
Your ERP, repricer and agents keep doing the work. Commerce Gate decides, action by action, whether what they are about to do on Dynamics 365 Business Central fits the policy you publish.
Not yet. It is in Beta, and certification and distribution are still pending. A source package version does not prove a signed package, a clean sandbox check or a public Marketplace listing. The readiness guide lists what remains.
No. It checks the complete transaction against your policy and the agent's budget and answers allow or block, without writing to your ERP. The Business Central extension and this MCP guard are separate.
The extension asks Commerce Gate at sales-document release and posting; no marketplace credentials are stored in your ERP. Before general release the package still needs signing, a clean sandbox check and a Partner Center preview. An AppSource listing is Planned after Microsoft certification.
Release and posting events, with lines, prices, cost basis and the agent that raised them.
Line quantity, unit price and unit cost.
Your margin and agent-spend rules, applied to the whole transaction.
Pick one setting for the whole company: release and posting either continue or stop until the check is back. Unless you change it, they continue.
Test with the signed package in a sandbox before you roll out. You choose the company-wide setting for when Commerce Gate is unavailable, and you turn on enforcement yourself after testing.
Once the signed preview package is available, add your Commerce Gate connection details, region and API key in a Business Central sandbox.
Run one sales document and check the decision, its reason code and how long it took. Business Central has no look-back at past orders.
Choose whether release and posting continue or stop when Commerce Gate is unavailable, then turn on enforcement once the test behaves as you expect.
The same rules on every platform you connect, and one Decision Ledger for the decisions each records.
Hold the Walmart order you can't ship. Catch the price that's under cost after the fee.
Walmart Marketplace controlsNo Shopify checkout below your margin floor. No discount code that stacks under it.
Shopify controlsCatch the cart price rule that sells below cost before the order is placed.
Adobe Commerce controlsInstall the extension, connect it to your workspace, choose what happens if Commerce Gate is unavailable, and test one sales document. There is no look-back at past Business Central orders.
