Product
Oversell, margin and refund controls, one policy, one signed ledger.
Commerce Gate has three guards: Inventory Guard flags orders that would promise stock you don't have, Price Guard flags price changes that fall under your margin floor once marketplace fees are counted, and Order Guard gates acknowledgments, cancellations and refunds. Every check, from a Walmart order to an AI agent's proposed price, uses the same proceed / hold / escalate vocabulary and lands in one signed Decision Ledger. What each platform can enforce, and what stays evaluation-only, is stated on its platform page. Commerce Gate is not a payment gateway: it never processes a payment, holds funds or moves money.
Inventory Guard
Check a stock change against your inventory floor before it is published.
Your ERP, feed or AI agent tells Commerce Gate the quantity it is about to publish for a SKU, from the current value to the new one, optionally per location. Commerce Gate answers whether that crosses your inventory floor. Whether the platform can then stop the write depends on what that platform's connector enforces; the answer is always recorded either way.
- Current-to-new quantity check before the write
- SKU and optional location
- Inventory-floor policy
- Verdict recorded; the platform connector decides what it can enforce
Price Guard
Catch the price that's under cost after fees before it reaches the marketplace.
Your repricer or AI agent tells Commerce Gate the price it is about to push for a SKU. Commerce Gate checks it against your policy and, when you also send the landed cost, works out the net margin after marketplace fees and compares it with your floor.
- Current-to-new price check before the push
- Landed cost in, net margin out
- Margin floor with marketplace fees counted
- Approval thresholds you set
Order Guard
Hold the risky order, gate the refund, before anything is sent.
On Walmart, an order acknowledgment that breaks policy is held. Ship, cancel and refund are checked for a valid order state, and a refund is also checked against your refund policy: rejected above what is left to refund, escalated to a named approver above your unattended limit, and held for review when the line was already refunded. Every refund check produces a signed dossier; ship and cancel run when an operator confirms them and are logged without one. An AI agent can ask Commerce Gate about a fulfillment step, refund or return before acting, and Commerce Gate never performs it.
- Walmart order acknowledgment held on a policy breach
- Refund rejected above the refundable balance, escalated above your unattended limit, held when the line was already refunded
- Operator confirmation before anything is sent to the marketplace
- Signed dossier on every refund check and policy decision; ship and cancel are logged without one
Decision Ledger
Recorded policy evaluations show what was decided, when, under which policy version, and by which actor. Policy decisions carry a signed dossier; operator-confirmed Walmart ship, cancel and refund actions are logged without one.
- Decision → Evidence → Policy → Outcome → Timestamp
- Ed25519-signed Decision Dossier with evidence fingerprint
- One ledger for supported recorded evaluations
Ledger entry
Price update · DC-AFR-55
- Decision
- HOLD
- Policy
- Margin Floor v2
- Source
- ERP automation
Commerce Evaluator
Commerce Gate shows what it would have held before you enforce anything. Connecting Walmart or Adobe Commerce starts a 90-day order evaluation automatically; order scenarios you type in use the same evaluation logic.
- Orders reviewed, order value reviewed, policy coverage
- Within policy · Review recommended · Would hold
- Orders missing cost data are never counted as covered
90-day Commerce Evaluation
Walmart Marketplace review
- Orders reviewed
- 1,284
- Order value reviewed
- $186,420
- Would hold
- 27
Start with the starter policy. Tune it when you've seen the evidence.
Margin floor, low-inventory, and stacked-promotion rules are published for you on first sign-in. Every edit becomes a new immutable version.