Folds the Walmart Marketplace referral fee into the margin gate before an order is acknowledged.
For: Walmart Marketplace sellers acknowledging orders automatically
Blocks acknowledging an order whose post-referral-fee margin falls under the encoded floor.
Escalates an order combining a rollback price with a further promotion.
Restrains acknowledgement when the inventory feed is older than the freshness window.
# Walmart Referral-Fee Margin Gate
# Fork: referral rates vary by category — set yours here.
apiVersion: decionis.dev/v1
kind: PolicyPack
metadata:
name: walmart-referral-fee-margin-gate
surface: walmart
workflow_key: order_acknowledgement
standards: [SOC2-CC8.1, ISO27001-A.8.34]
defaults:
mode: shadow
emit_dossier: true
margin_floor_pct: 8
referral_fee_pct: 12
rules:
- name: referral_fee_margin_check
when: "action == 'order.acknowledge'"
decision: |
BLOCK IF (order.total * (1 - referral_fee_pct / 100) - order.cost_basis) / order.total < margin_floor_pct / 100
ALLOW OTHERWISE
reason_code: post_referral_margin_below_floor
- name: promo_stacking_ceiling
when: "action == 'order.acknowledge'"
decision: |
ESCALATE IF price.is_rollback == true AND promotions.count > 0
ALLOW OTHERWISE
reason_code: rollback_and_promotion_stacked
- name: inventory_sync_restraint
when: "action == 'order.acknowledge'"
decision: |
RESTRAIN IF inventory.feed_age_minutes > 60
ALLOW OTHERWISE
reason_code: stale_inventory_feed
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.
Follow the install path for this surface, then paste the forked YAML as your policy config.
This recipe is one step in a path. The same five steps apply to every recipe in the exchange.
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.
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.
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.
Point the same policy at the system where the action actually originates — a checkout, an ERP posting, a Zap, an agent's tool call.
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.