Use Shadow Mode to understand the policy and inputs
Shadow Mode shows you which actions would have been stopped, why, and on what data, before you turn anything on. Walmart and Adobe Commerce begin with a 90-day order evaluation; Shopify looks back 14 days. Business Central checks one transaction at a time and has no look-back.
A look-back does not prove a past loss was prevented or that the same orders will recur. Read it as what happened in that period, and keep reviewed order value apart from actual savings. Missing costs or incomplete history can change the result.
Enforcement requires a real commitment point
Enforcement matters where something can actually stop the action before it commits. On Walmart, that is holding the order acknowledgment; on Shopify, the checkout rule inside Shopify Functions; on Adobe Commerce, the checkout validation response. The Business Central extension, in Beta, checks release and posting.
Shopify documents its server-side checkout validation, and Commerce Gate’s capability matrix states how it uses it. A platform offering an API does not mean every Commerce Gate action is built, permitted or turned on there.
Shopify: native cart and checkout validation. The platform validation surface supports the checkout context; Commerce Gate’s own matrix defines its integration scope.
Move to enforcement only for a verified path
Before you turn on enforcement, review typical results, fix your cost and policy inputs, know what sends the final action and test the outcomes outside production. Check permissions and settings. A go-ahead answer is not your authorization to act.
Test what happens when Commerce Gate is unavailable, too. Walmart order acknowledgments and Adobe Commerce checkout go through. Shopify checkout rules keep protecting you by default, and you can let individual rules through. Business Central has one company-wide choice, and an agent that gets no answer must wait.
What Commerce Gate covers today
Walmart order acknowledgment: enforces when enabled
An order acknowledgment that breaks policy is withheld.
MCP price proposals: evaluates only
Shadow Mode answer with net margin after landed cost and marketplace fees, with dossier evidence where supported.
Before you choose, see what happens on each platform during an outage and how we check integration status. Signed Decision Dossiers come where the platform supports them; some outage fallbacks and operator-confirmed actions are recorded without one.
How to choose
Stay in Shadow Mode while you are validating the policy
Stay in Shadow Mode while you check your data, understand what would be held and decide which controls to turn on. It is free with no time limit where offered, and never billed as governed decisions.
Enable enforcement for the tested action and platform
Turn on enforcement once you accept the policy, the workflow and what happens during an outage. Check your plan and the capability matrix first; a plan or mode change does not turn a check into a block.