Loading…
Open-Policy Exchange
~4 min to deploy
Commerce & Retail Ops Pack
Over-selling, margin-floor, and coupon-stacking gates for orders and fulfillment — the three that leak the most money.
For: Shopify Plus, BigCommerce, high-volume retail
SOC 2 CC8.1ISO 27001 A.8.34Checkout evidence trail
What it enforces
Over-Selling Gate
Blocks fulfilling an order for stock oversold across channels.
Margin Floor Guard
Blocks any order that would breach the encoded margin floor.
Coupon-Stacking Gate
Stops unauthorized or cascading discount stacking at checkout.
commerce-retail-ops-pack.yaml
# Commerce & Retail Ops Pack
# Fork: the three gates from the commerce starter pack, with your thresholds.
apiVersion: decionis.dev/v1
kind: PolicyPack
metadata:
name: commerce-retail-ops-pack
surface: bigcommerce
policy_pack_id: commerce
standards: [SOC2-CC8.1, ISO27001-A.8.34]
defaults:
mode: shadow
emit_dossier: true
margin_floor_pct: 12
rules:
- name: over_selling_gate
when: "action == 'order.fulfill'"
decision: |
BLOCK IF units_ordered > units_available
ALLOW OTHERWISE
reason_code: oversold_inventory
- name: margin_floor_guard
when: "action == 'checkout.commit'"
decision: |
BLOCK IF order.net_margin_pct < margin_floor_pct
ALLOW OTHERWISE
reason_code: below_margin_floor
- name: coupon_stacking_gate
when: "action == 'checkout.apply_discount'"
decision: |
BLOCK IF combined_discount_pct >= 50
ESCALATE IF coupons.count > 1
ALLOW OTHERWISE
reason_code: unauthorized_coupon_stacking
Fork it, change the thresholds to match your environment, and deploy in shadow mode first — it defaults to listen-only so nothing in your live pipeline changes.
How to install it
Follow the install path for this surface, then paste the forked YAML as your policy config.
What to do next
This recipe is one step in a path. The same five steps apply to every recipe in the exchange.
- Simulate this recipe
Run the policy against a realistic action in the browser. Push it past what the rules allow and watch the verdict come back. No account.
- View the signed Decision Dossier
See exactly what was decided and why: the rule that fired, the evidence it read, the policy version in force, and an Ed25519 signature you can verify yourself.
- Deploy in shadow mode
Measure what the policy would have caught on your own traffic without touching the live path. Every recipe defaults to shadow, so the first deployment carries no execution risk.
- Connect a real workflow
Point the same policy at the system where the action actually originates — a checkout, an ERP posting, a Zap, an agent's tool call.
- Share the verified result
Publish the proof: a public verification link, an embeddable badge, a PR comment, or an anonymized shadow-mode finding. This is how the next person discovers Decionis.