Order Approval
Past a certain size, an order is worth a second pair of eyes before it goes out. Iraca lets you set an amount above which confirming a sales order raises it for approval instead of committing it — and the person who raised it can't be the person who approves it.
This is switched off for everyone until you set a threshold. Until then, orders confirm exactly as they always have.
Setting the threshold
Go to Settings → B2B & Wholesale and fill in Approval threshold for sales orders. (It used to live on the Orders settings card; it moved to the B2B page, where the rest of the wholesale controls are.)
Enter the amount in dollars — 500 holds every sales order of $500 or more. The comparison includes sales tax, so a $490 order carrying $40 of tax counts as $530 and is held.
- Leave it blank to switch the step off. Sales orders confirm straight through, whatever the amount.
- Enter 0 to hold every sales order. Blank and zero are genuinely different settings, so an empty field never quietly means "approve everything".
The threshold applies to sales orders you create by hand. Purchase orders and orders imported from a marketplace are never held — a marketplace order was already placed and paid for by the customer, so there is nothing left to approve.
What happens when an order is held
Confirm the order as usual. If it's at or above your threshold, Iraca holds it at Pending Approval instead of confirming it.
While an order is waiting:
- Nothing ships. You can't fulfill it, buy labels for it, or mark it shipped.
- Nothing is sent to the customer. The order confirmation email waits until the order is approved — telling the customer first would make the approval a formality over an order you'd already promised.
- The order can't be edited. Its total is fixed while someone rules on it, so nobody can change the figure out from under the approver.
Held orders show a yellow Pending Approval badge on the Orders list and have their own filter there, so they don't get lost.
Approving or rejecting
Only an owner can approve — a stricter rule than most actions in Iraca, which admins can also take. An admin can confirm an order, so an admin isn't a higher pair of eyes on one.
On top of that, the approver has to be someone other than the person who confirmed the order. If you confirmed it yourself, the Approve and Reject buttons don't appear for you and the banner tells you another owner has to step in. That's the whole point of the step: it isn't a second click, it's a second person.
Open the order and choose:
- Approve — the order becomes Confirmed, everything unlocks, and the customer gets their confirmation email. Who approved it and when are recorded on the order.
- Reject — the order goes back to Draft so it can be changed and confirmed again. You're asked for a reason, which is worth giving: whoever picks the order back up sees it in a banner at the top, and "no" on its own doesn't tell them what to change. Nothing is sent to the customer.
Every step is kept in the order's Activity trail — who confirmed it, who ruled on it, what they said.
Fixing a rejected order
A rejected order behaves like any other draft. Edit it, delete it, or confirm it again.
If you trim it back below the threshold, the next confirm goes straight through and the rejection banner clears. If it's still above the threshold it's held again — and if a different person confirms it the second time, it's now that person who can't approve it. The rule always follows the most recent confirmation.
There's no override
There is deliberately no "approve my own order anyway" button. If one person genuinely needs to be able to commit an order of that size on their own, raise the threshold in Settings — that's a decision about how your business runs, it's recorded, and it applies consistently. A bypass on a single order is a decision taken under pressure to ship, and it leaves no trace.