Approvals
Holding orders for a decision — which ones, who decides, and how they do it.
Store adminsA store can hold orders until somebody approves them. If your store does approvals at all, which orders get held is your decision, and you can change it whenever your organisation does.
Which orders get held
Four rules, and they add up. An order is held if any of them catches it.
| Rule | Use it when |
|---|---|
| Every order | Nothing leaves without a look. The default when a store has no policy. |
| Above an amount | Small orders should just go. |
| By payment method | Anything billed to the company is checked; a personal card is not. |
| A named buyer | One person's orders need a second pair of eyes. |
There is also an exemption that beats all four, set per person on the Team tab. A manager you trust can be let straight through a policy that holds everybody else.
Who gets asked
| Routing | Goes to |
|---|---|
| Default | Your store's approver list, then its admins. |
| The buyer's manager | Whoever they report to on the Team tab. Different for each buyer, which is the whole reason this exists. |
| A named person | One person on your roster, whoever placed the order. |
| An email address | Somebody who has no account here at all. |
How approving works
The approver gets an email with the order on it and a link. The link is the permission — they do not need an account, and they do not have to find anything. They approve or reject, and the buyer is emailed either way.
Rejecting asks for a reason, and the buyer sees it. "Rejected" with no explanation is a second email you will end up writing by hand.
What the buyer sees
Checkout tells them before they submit. A store that holds everything says so; one that holds orders over an amount says their order may be held. They are never surprised by it afterwards.
