Escalates quote discounts past the encoded band when the contract-value evidence is missing.
For: Deal desk and pricing teams approving quotes in Salesforce
Escalates discounts above 20% when contract-value evidence is missing.
Blocks a quote whose net price falls under the encoded margin floor.
Restrains a quote combining a discount with extra concessions beyond the authorized ceiling.
# Salesforce Discount Approval Gate
# Fork: this is the saas_ops "Discount Logic Gate" expressed for CPQ quotes.
apiVersion: decionis.dev/v1
kind: PolicyPack
metadata:
name: salesforce-discount-approval-gate
surface: salesforce
workflow_key: quote_discount_approval
standards: [SOC2-CC8.1, ISO27001-A.5.15]
defaults:
mode: shadow
emit_dossier: true
rules:
- name: discount_band_escalation
when: "action == 'quote.submit'"
decision: |
ESCALATE IF discount_pct > 20 AND contract_value_usd < 50000
ALLOW OTHERWISE
reason_code: discount_evidence_missing
- name: floor_breach_block
when: "action == 'quote.submit'"
decision: |
BLOCK IF net_margin_pct < margin_floor_pct
ALLOW OTHERWISE
reason_code: below_margin_floor
- name: stacked_concession_restraint
when: "action == 'quote.submit'"
decision: |
RESTRAIN IF concessions.count > 1 AND discount_pct > 15
ALLOW OTHERWISE
reason_code: stacked_concessions_over_ceiling
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.