Loading…
Open-Policy Exchange
~6 min to deploy
Amazon Oversell & Fee Gate
Blocks fulfilling an order for stock oversold across channels, and checks referral plus fulfillment fees against the margin floor.
For: Amazon sellers running multi-channel inventory
SOC 2 CC8.1ISO 27001 A.8.34Fulfillment evidence trail
What it enforces
Over-selling gate
Blocks fulfilling an order that would ship more units than the system of record holds.
Fee-adjusted margin floor
Blocks an order whose margin, after referral and fulfillment fees, falls under the floor.
Cross-channel reservation restraint
Restrains a fulfillment when the same units are already reserved on another channel.
amazon-oversell-and-fee-gate.yaml
# Amazon Oversell & Fee Gate
# Fork: set your own fee assumptions and floor per category.
apiVersion: decionis.dev/v1
kind: PolicyPack
metadata:
name: amazon-oversell-and-fee-gate
surface: amazon
workflow_key: order_fulfillment
standards: [SOC2-CC8.1, ISO27001-A.8.34]
defaults:
mode: shadow
emit_dossier: true
margin_floor_pct: 8
rules:
- name: over_selling_gate
when: "action == 'order.fulfill'"
decision: |
BLOCK IF units_ordered > units_available
ALLOW OTHERWISE
reason_code: oversold_inventory
- name: fee_adjusted_margin_floor
when: "action == 'order.fulfill'"
decision: |
BLOCK IF (order.total - order.cost_basis - fees.referral - fees.fulfillment) / order.total < margin_floor_pct / 100
ALLOW OTHERWISE
reason_code: fee_adjusted_margin_below_floor
- name: cross_channel_reservation_restraint
when: "action == 'order.fulfill'"
decision: |
RESTRAIN IF inventory.reserved_on_other_channel == true
ALLOW OTHERWISE
reason_code: units_reserved_elsewhere
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.