Order approval workflow: checks that don’t slow you down
Approval steps in order processing usually fail in one of two ways. Either every order needs a signature, so the approver clicks through dozens without really reading them, or every order waits for the one person who’s allowed to approve, and the dispatch cut-off slips past while they’re in a meeting.
An order approval workflow is the set of checks an order passes, and the sign-off it needs, between arriving and becoming a sales order in your ERP. A good one checks every line automatically, shows the approver only what needs judgement, and asks for a second approval only where the value or risk justifies it.
What should be checked on each order line?
Line checks have definite answers, so they should be done by code against your ERP rather than by someone squinting at two screens. For every line:
- Product code exists. If the customer uses their own part numbers, check whether there’s a known mapping to yours.
- Unit of measure makes sense. An order for 10 of something sold in packs of 10 might mean 10 packs or one. Flag quantities that aren’t a multiple of the pack size.
- Stock is available for the quantity and the requested date, or the shortfall is shown.
- Price matches the customer’s price in the ERP, not just the list price. Show both figures when they differ.
- Line total adds up. Quantity times unit price should equal the line value printed on the PO.
Then, for the order as a whole:
- Customer matched to the right account, including the right branch for groups with several.
- PO number not already received from this customer.
- PO total matches the calculated total. A gap usually means a missed line, a misread quantity or a price the customer expects you to honour.
- Delivery address is one already on the account, or is clearly flagged as new.
- Delivery charge on the PO matches what you’d normally charge. If carrier prices move, check it again before invoicing, which we cover in checking carrier costs before invoicing.
When the order was read from an email or PDF, add one more: any field the extraction step wasn’t confident about. We explain how that scoring works in PDF purchase order data extraction.
How do you write warnings people don’t ignore?
An order review queue that shows a warning on every order teaches people to stop reading warnings. A few rules keep them meaningful:
- Attach each warning to a field. “Price differs” next to line 3 is useful. A red banner at the top of the order is not.
- Say what the system expected. “PO says £4.20, account price is £3.95” lets the reviewer decide in seconds.
- Separate errors from warnings. An unknown product code or a missing customer means the order can’t go into the ERP yet, so it should block approval. A low-confidence delivery date or a new delivery address deserves a look, and the reviewer can approve once they’ve looked.
- Remove warnings nobody acts on. If one is overridden every time, either the rule is wrong or the data behind it is. Fix it rather than training people to click past it.
- Record overrides with a reason. A short note such as “agreed old price with buyer” is enough, and it makes the audit trail useful later.
When does an order need a second approval?
Keep two-person approval for the small number of orders where a mistake is expensive or the risk is unusual. Typical triggers are:
- order value above a set threshold
- a price override that takes the line below the customer’s account price by more than a set margin
- a new customer, or a first delivery to a new address
- a customer on stop or over their credit limit, if your ERP holds that information
- orders keyed in by hand from a phone call, where the person entering the order shouldn’t also be the only one approving it
Keep the list short and make the reason visible. The second approver should see straight away why the order has come to them.
A quick sense check on the thresholds: say you take 80 orders a day. If five of them need a second approval, that’s a manageable task for a manager. If thirty do, the thresholds are set too tight and you’ve rebuilt the bottleneck you were trying to avoid.
When is it safe to auto-approve orders?
Automatic approval is safe when an order meets conditions where a person’s review would add nothing. A reasonable starting definition is all of the following:
- a known customer, matched with certainty
- every extracted field above your confidence threshold
- every line check and order check passed, with no warnings at all
- order value below a modest limit
- no duplicate PO number
Already-paid web shop orders are often the easiest place to start, because payment is settled and the data didn’t need reading from a document.
Our own default is that a person approves every order. Automatic approval comes with our Standard plan, which is rule-based, and our Growth plan, which adds confidence scoring. Even then it stays switched off until the client asks for it, usually after a few weeks of seeing how clean orders come through. When it does go on, start narrow, with one channel or a few trusted customers, and keep sampling some auto-approved orders by hand for a while.
What should the audit trail record?
Every order should carry a history you can read months later without asking anyone:
- when it arrived, and the original email and attachments
- what was extracted, and the confidence of each field
- every check result and every warning shown
- each change a reviewer made, with the value before and after
- who approved it, when, and any override reason
- whether it was approved automatically, and under which rule
- when it was created in the ERP, and the reference used
That record settles disputes quickly, shows new staff how decisions are made, and gives you the evidence to adjust thresholds rather than guessing.
Keeping the review queue moving
The design of the screen matters as much as the rules behind it. An inbox-style queue, with the oldest and most urgent orders first, keeps work visible. Showing the original email beside the extracted order removes the need to switch windows. Editing a field in place, approving in one click, and putting an order on hold with a reason all save more time than any single check. If you have a dispatch cut-off, show it on the queue so nobody has to remember it.
Order approval workflow checklist
Use this to review an existing sales order approval process or to plan a new one:
- Product codes checked against the ERP, with customer part numbers mapped
- Pack sizes and units of measure checked
- Stock checked for the quantity and date requested
- Prices checked against the customer’s account price, with both figures shown
- Line totals and PO total recalculated and compared
- Customer and branch matched to the correct account
- Duplicate PO numbers detected
- New delivery addresses flagged
- Low-confidence fields flagged against the field, missing details left blank
- Blocking errors separated from warnings
- Overrides require a short reason
- Second approval limited to a short, written list of triggers
- Auto-approval rules written down, off by default, and sampled once on
- Full audit trail of changes, approvals and ERP references
- Original email visible beside the order in the queue
Every rule above can be tuned to how your business works, because your integration is set up around your rules. Our order review page shows how the queue and checks look in practice, and if you’d like to talk through your current process, get in touch.