Protect the risky orders. Leave the rest alone.
A thirty-dollar t-shirt and a three-thousand-dollar watch should not get the same evidence policy. Rules decide what is captured, whether the buyer reviews it and what return evidence is requested.
Set up in 5 minutes, no code · Works with Shopify and WooCommerce
One policy for every order is either too slow or too thin
Ask every buyer to approve and you add friction to orders that were never at risk. Ask nobody and you are exposed exactly where it costs most. Deciding case by case works fine, right up until volume arrives.
What you get
Three conditions that actually predict risk
Order value, product category or tag, and destination country. Deliberately few: a rule engine nobody can reason about is a rule engine nobody trusts.
Six evidence policy choices
Buyer mode, whether capture is required, return evidence, contract display, traceability checks, and what proof metadata gets written back into the platform order.
Defaults stay defaults
Rules are exceptions, not the whole policy. Anything a rule does not mention keeps your store-wide setting, so one narrow rule cannot quietly rewrite everything.
Sector presets
Start from a preset for electronics, jewellery, apparel or home and adjust it, instead of from an empty page and a blank stare.
Tightening only, where it matters
Traceability requirements — serial numbers, media per line item, quantity match — can be made stricter by a rule but never looser. A rule cannot open a hole in your own policy.
One effective policy per order
Everything downstream reads the same resolved policy, so what the webhook does, what the buyer sees and what gets written back cannot disagree with each other.
How it works
- 1
Set your default
Pick what happens for a normal order: record silently, notify the buyer, or require approval.
- 2
Add exceptions
"If the order total is over five hundred, require evidence capture and ask the buyer to review it."
- 3
An order arrives
Conditions are evaluated and a single effective policy is resolved for that order.
- 4
Everything follows it
Capture requirements, buyer messaging, return evidence and proof write-back all read that one policy.
Record one yourself, right now
Not a sample and not a video of the product — your own clip, through the real pipeline, ending on a real verification page you can send to anyone.
- 1Scan the code that appears and the recording screen opens on your phone.
- 2Film anything you have on hand for a few seconds.
- 3You get the sealed record and its public verify link.
Takes about a minute. Nothing is installed and no card is involved.
Under the hood
Facts, not adjectives. Everything below describes what the product does today — nothing here is on a roadmap.
Availability
Rules live in Settings, under Protections. The underlying capture policy is on every plan; conditional rules that act on platform orders need commerce integrations, which start at Pro.
Pricing- Condition dimensions
- 3Condition dimensions
- Policy fields a rule sets
- 6Policy fields a rule sets
- Sector presets
- 5Sector presets
- Conditions
- Order amount (greater than, less than, between), product category or tag, buyer country
- Policy fields a rule can set
- Buyer mode, capture required, return evidence, contract, traceability checks, proof write-back target
- Buyer modes
- Record, acknowledge, approval
- Write-back targets
- Off, order metafield, or metafield plus a timeline note
- Sector presets
- Electronics, jewellery, apparel, home, other
- Traceability options
- Media for every line item, quantity match, serial / IMEI / certificate number
- Resolution
- One effective policy per order, read by every downstream step
Questions people actually ask
How many rules can I have?
As many as you need. They are evaluated per order and resolve into a single effective policy, so overlapping rules produce a predictable result instead of fighting each other.
Why only three conditions?
Because the fourth one is where rule engines become unauditable. Value, category and destination cover the risk patterns merchants actually described to us; past that we would rather you decided explicitly.
Can a rule make things looser than my default?
Not for traceability requirements — those can only be tightened. Everything else a rule can set in either direction, because that is an ordinary policy choice rather than a safety net.
Do I have to build these from scratch?
No. Choose your sector, start from its preset, and adjust what does not fit.
Where merchants use this
Keep exploring
Each part is useful on its own. Together they turn one recording into an answer for every kind of claim.
Record every order and use it as evidence when a dispute comes up.
Set up PallasMark in 5 minutes and turn every order into evidence that wins. No credit card required.