Integrate
Commerce Gate lets your repricer, ERP, workflow or AI agent check a proposed action before sending it. Your integration sends the facts your policy needs, gets a decision and honors it before going on. The API and the published MCP never carry out the proposed action. Treat an error or an unreadable response as a hold.
Recipe 1
One request per proposed action, sent before the tool writes to the marketplace. The operation is evaluateCommerceDecision in the published contract at /.well-known/openapi.json.
POST https://api.decionis.com/v1/protocol/evaluate-decisionAuthorization: Bearer <workspace API key> and Idempotency-Key, stable for retries of the same proposed action.channel is repricer, erp, workflow or api; source is your tool's name. Both are recorded on the dossier.SHADOW. The answer is the same one enforcement would give; your tool enforces it by honoring the answer.A price change from a repricer, with the signals the starter policy reads:
{
"org_id": "your-workspace-id",
"decision_type": "PRICE_CHANGE",
"transaction_type": "price_change",
"workflow_key": "commerce_price_change",
"amount": 89,
"channel": "repricer",
"source": "acme-repricer",
"mode": "SHADOW",
"idempotency_key": "sku:DC-AFR-55:price:89.00:2026-09-10T12:00:00Z",
"context": {
"action_type": "PRICE_CHANGE",
"actor_type": "REPRICER",
"actor_id": "acme-repricer",
"platform": "walmart-marketplace",
"signals": {
"sku": "DC-AFR-55",
"from_price": 129,
"to_price": 89,
"currency": "USD",
"estimated_cost": 81.79,
"net_margin_percent": 8.1
}
}
}The answer, trimmed to what the tool acts on:
{
"outcome": "REVIEW",
"policy_version": "commerce-policy-v2",
"dossier_id": "9d8b4c1e-2f0a-4b6e-9c3d-1e2f3a4b5c6d",
"reason_codes": [
"MARGIN_BELOW_FLOOR"
],
"mode": "SHADOW"
}| Contract says | Operators read | Your tool does |
|---|---|---|
APPROVE | PROCEED | Go ahead. This is a policy result, not consent from a person. |
REVIEW | HOLD | Stop. Leave the marketplace as it is and put the action in front of an operator. |
ESCALATE | ESCALATE | Stop. A named approver decides before you ask again. |
REJECT | BLOCK | Stop. Outside policy; do not retry the same action. |
An error, a timeout or an answer you cannot read means hold. Keep the dossier_id with your own record of the push, so finance can open it in the Decision Ledger months later.
Rules read context.signals. The starter policy every workspace begins with reads these; a rule you add on the Policies page reads whatever field you name.
| Rule | Reads | Fires when | Send it with | How |
|---|---|---|---|---|
| Protect minimum margin | signals.net_margin_percent | LT 12 → require review | PRICE_CHANGE, ORDER_ACCEPTANCE | Percentage points: (net revenue minus landed cost) divided by net revenue, times 100. Landed cost is your unit cost plus the marketplace referral fee and shipping you bear. Send it as a number, so 8.1 means 8.1%. |
| Protect low inventory | signals.available_inventory | LT 10 → require review | INVENTORY_MUTATION, ORDER_ACCEPTANCE | Units left after the change or the order, at the location it applies to, from your source of truth. |
| Review stacked promotions | signals.discount_count | GT 1 → require review | ORDER_ACCEPTANCE, PROMOTION_CHANGE | How many discount sources combine on the order or would combine under the promotion. |
| Reject refunds above the refundable balance | signals.refund_exceeds_refundable | EQ true → auto reject | REFUND_REQUEST | true when the refund amount is more than the order line still has left to refund; send remaining_refundable beside it. |
| Escalate refunds above the unattended limit | signals.refund_amount | GT 1000 → escalate | REFUND_REQUEST | The refund amount in the order currency; send currency and reason_code beside it. |
| A held order is released only by an approver | signals.workflow_key | EQ commerce_order_release → escalate | ORDER_RELEASE | Send workflow_key: commerce_order_release at the top level of the request, not under signals, when a system wants to release an order the gate held. The policy escalates it to a named approver through Presence; Commerce Gate never picks the approver. |
| Review a second refund on the same line | signals.prior_refund_count | GT 0 → require review | REFUND_REQUEST | How many refunds the same order line already carries; 0 for the first. |
Without a landed cost, a margin rule cannot fire, and Commerce Gate lets the action through rather than guess a cost. Send estimated_cost and the margin it produces, or price and order checks will go ahead.
Recipe 2
The MCP does the normalization above for the agent: it takes the plain facts (SKU, prices, cost, quantities, refund amounts), derives the signals, and sends the same request in Shadow Mode. Install it with npx -y @decionis/commerce@0.2.0.
commercegate_describe_capabilitiescommercegate_validate_erp_transactioncommercegate_evaluate_actioncommercegate_get_dossiercommercegate_get_proof_packetcommercegate_list_shadow_reportscommercegate_summarize_shadow_reportscommercegate_evaluate_marketplace_offer_submissionRecipe 3
A repricer that never asks can still be watched. On Walmart Marketplace, the listing sweep reads the price of every published listing through the Items API, lands the cost with your referral-fee schedule, and checks each listing against the margin floor in Shadow Mode. Listings below the floor get a signed decision and appear on the Price Guard page; nothing on Walmart is written.
The sweep waits for Walmart to grant the Items read scope on your connection; the Price Guard page shows “Waiting for Walmart” until then, and the switch unlocks when it is granted. Until that day, recipe 1 is how a repricer is governed.
Send the proposed action and the facts your policy needs, such as SKU, proposed price, landed cost, quantity or order amount. Use the published contract and a stable idempotency key. Keep credentials in secure configuration and send only the data the check needs.
Only through the controls you turn on: it can withhold a Walmart acknowledgment, apply Shopify checkout rules, or check Business Central release and posting. On Walmart, ship, cancel and refund wait for your operator to confirm. Your repricer or ERP sends price and stock changes. The MCP checks and reads evidence and never writes to a marketplace or ERP. Approving a policy is not consent to act.
Where your platform records a Decision Dossier, it explains the decision and links to signed evidence, and a proof packet helps you review it. Some observations, outage fallbacks and operator-confirmed actions have no dossier. A record that a check ran does not prove the price changed, the order shipped or the refund completed.