Execution pattern
Refuse the order that ships below your true cost.
An order reaches checkout carrying stacked discounts or a drifted automated price.
Native discount rules reason about price, not margin. Stacked codes and a repricer that moved overnight combine into an order that is profitable on the listing and loss-making on the invoice.
The signals available at the moment of the action, and the rule that judges them.
Refuse the order when net margin against verified cost falls below the floor, evaluated inline before the checkout token is issued.
Checkout completes above the floor.
A borderline order waits on a merchandiser.
Checkout is refused; the dossier records the margin computation.
Fork one and change the thresholds. Available today on 9 platforms.
Never discount below margin. Holds the checkout before the payment token is issued when the cart would breach the floor.
shopify
Never discount below margin. Holds a WooCommerce checkout whose net margin would breach the encoded floor.
woocommerce
Folds eBay final-value fees and promoted-listing rates into the margin check before a listing or price change goes live.
ebay
Escalates quote discounts past the encoded band when the contract-value evidence is missing.
salesforce
Catches a pricing feed or AI engine publishing a price far off the last-known-good value before shoppers see it.
adobe commerce
Over-selling, margin-floor, and coupon-stacking gates for orders and fulfillment — the three that leak the most money.
bigcommerce
Cloud spend, discount, and entitlement gates — stop runaway burn, margin leakage, and unsupported entitlement changes.
sdk
Velocity, discount, and market-eligibility gates for Shopify checkout, B2B, and POS — with audit evidence for every exception.
shopify
This pattern is one answer to each of these.
The same five steps for every pattern in the library.
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.