Published on ZapierAug 4, 2026
Shopify
Create Decionis decision dossiers for new paid Shopify orders
Every paid Shopify order produces verifiable decision evidence.
For Commerce operations, margin controls, refunds, and order governance.
Execution pattern
Customer refund
Let support move fast without letting policy drift.
- Category
- MoneyCommon in Commerce & retail · Hospitality & travel · Fintech & payments
- Works through
- langchain · slack · zapier
- Proof
- Signed Decision DossierVerifiable against our published JWKS.
- Deploy
- Shadow Mode firstMeasure on your own traffic before anything is stopped.
What executes
A refund, credit, or goodwill adjustment is issued to a customer.
What normally goes wrong
Refunds are individually small and collectively enormous. Discretion is delegated widely and reviewed narrowly, so drift is only visible once it is a quarterly number.
The decision
The signals available at the moment of the action, and the rule that judges them.
Signals
- Amount against the agent's discretionary limit
- Refund history for this customer
- Original order margin
- Whether goods were returned
The gate
Refuse refunds beyond the issuing agent's discretion, and escalate patterns that look like repeat abuse rather than one-off service.
ALLOW
The refund issues within discretion.
ESCALATE
A larger or repeated refund waits on a supervisor.
BLOCK
The refund does not issue.
Four stages left to right. Input signals — user or agent identity, context and data, tools and resources, spend and budget, policies, history and reputation, and environment — enter the Decionis Protocol. Inside, the protocol normalizes context and intent, evaluates policies and rules, runs a deterministic risk and policy engine, and explains the reason and evidence. It emits a verdict: ALLOW (authorized), ESCALATE (needs approval or more info), or BLOCK (high risk or out of policy). The verdict drives an enforcement action: allow, block, require approval, or throttle and limit. Every decision is recorded for audit, learning, and continuous improvement.
The policy packs that decide this pattern
The bundles the Decionis evaluator ships, with every rule in the order it is tried.
Commerce Gate
Governance for storefront and marketplace decisions — price and promotion changes, inventory mutations, order acceptance and release, refunds, and Microsoft Partner Center or AWS Marketplace offer submission — against the merchant's margin, inventory, refund, and release-evidence floors.
commerce · commerce-v1 · 12 rules
Ops Spend Control
Dual-gate governance for back-office spend — spend admission (completeness, valid amount, verified vendor, expense/refund/credit limits) and disbursement authority (authorized role, segregation of duties, dual authorization, duplicate-payment detection) before money moves.
ops · ops-spend-v1 · 12 rules
Govern this pattern with a published Zap
Start from the workflow already running in your source system. Decionis adds the policy decision and returns signed evidence without turning Zapier into the authority.
Prove it, then deploy it
A verdict you cannot check is an opinion, and a gate you cannot measure first is a risk of its own.
View the signed proof
Every verdict on this pattern produces a Decision Dossier: the signals it saw, the policy version that judged them, and an Ed25519 signature anyone can check against our published JWKS — without an account, and without trusting us.
Deploy in Shadow Mode
Run this gate against your own traffic while it stops nothing. You get the verdicts it would have returned and the actions it would have held, so the decision to enforce is made on your numbers rather than ours.
Related patterns
Teams that hit this one usually hit these next.
Related concepts
This pattern is one answer to each of these.
What to do next
The same five steps for every pattern in the library.
- 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.