Industries/ Wholesale/ Email and PDF order capture
Order entry automation for orders that arrive by email
Customers keep ordering exactly as they do now: an email, a PDF purchase order from their system, a spreadsheet or a photo of a list. The software reads each one, matches it to the account and your product codes, checks it, and either creates the order or puts it in front of a person with the problem highlighted.

- Used by
- Your sales office, customer service and credit control
- Takes the place of
- Retyping emailed orders, PDFs and spreadsheets each morning
- Connects to
- Your orders inbox, ERP, price lists and product codes
- Built with
- Our workflow automation service
Where it hurts today
A normal week, before it exists
By the time the office opens, the shared orders inbox has filled overnight, and every customer orders in their own way. A hotel group's purchasing system sends a PDF with its own product codes. A café sends an email typed on a phone: same as last week, but double the milk. A builders' merchant sends a spreadsheet with the columns in a different order each time.
Someone in the sales office opens each one, works out which account it belongs to when it comes from a personal address, translates each customer's codes into yours, checks pack sizes, keys it into the ERP and replies to confirm. The cut-off for the first van doesn't move, so the morning is a race, and that is when a 12 becomes a 21.
Asking these customers to use a portal doesn't always work. Larger customers' purchasing systems send purchase orders by email and nothing else, and their buyers will not log in to every supplier's website. Smaller ones just like email. Those orders will keep arriving as documents, so the job is not to change the customer. It is to stop your team retyping what they send.
What it does
Email and PDF order capture, feature by feature
What happens between an email arriving and an order appearing in your ERP, and where a person still makes the decision.
- 01
Reads emails, PDFs and spreadsheets
Plain emails, PDF purchase orders, Excel and CSV attachments, and photos or scans of written lists. The software picks out the customer, the delivery date, the lines and the quantities, and keeps the original attached so anyone can check what was actually sent.
- 02
Customer part numbers mapped to yours
Larger customers use their own codes and descriptions. Every confirmed match is remembered, so once someone says that 'FRY OIL 20' means your rapeseed oil drum, the next order from that account matches on its own. The mapping table is visible and editable, not hidden inside a model.
- 03
Price, pack and stock validation
Each line is checked against the account's contract price, pack size, minimum quantity and stock. A price that differs from the one you would charge, a quantity that isn't a whole case, a line you have discontinued: each is flagged on the line itself, with the reason.
- 04
Straight-through processing for clean orders
Where every line matches and every check passes, the order is created in the ERP and the customer gets a confirmation, without anyone opening it. You decide which accounts and which kinds of order may go through on their own, and you can start with none.
- 05
An exception queue built for speed
Orders that need a person show the original document on one side and the extracted order on the other, with problem lines highlighted. The reviewer fixes the line, confirms the match once and creates the order. The aim is that a review is a decision, not a retype.
- 06
Duplicate and amended orders caught
Customers resend orders, reply with 'add two more cases', or send a revised purchase order under the same number. The software spots a repeated PO number or a near-identical order from the same account, asks before creating a second one, and links amendments to the original.
A day with it
How the day runs instead
A normal morning in the sales office once order capture is running.
- 11.20pmCustomer's purchasing system
A hotel group's system sends a PDF purchase order for one of its sites. The software reads it, matches every line through codes learned from earlier orders, finds the prices agree with the contract, and creates the order for the morning pick.
- 6.50amCafé owner
Emails from a phone: same as last week, plus two cases of oat milk, and no croissants. The software finds last week's order, applies the changes and holds it for review, because you have set every 'same as last week' order to get a person's eye first.
- 8.00amSales office
The first order in the review queue has an unknown code on one line. The reviewer sees the PDF beside the extracted lines, picks the right product, ticks remember this match and creates the order without retyping any of it.
- 9.30amCredit controller
One order passed every product check, but the account is over its limit. Instead of being created, it sits in the credit queue with the original email attached. The credit controller calls the customer and releases it once a payment comes in.
- FridaySales office manager
Looks at which accounts sent orders that needed review this week, and why. Two customers keep sending a different code every time, so the manager asks their buyers to use the codes on your price list.
What it connects to
Works with what you already run
Order capture sits between your inbox and your ERP. It reads from four places and writes to one.
Shared orders inbox
The mailbox your customers already send to, for example in Microsoft 365 or Google Workspace. The software reads new messages and attachments, and the original stays in the mailbox exactly as it always has.
ERP or order processing system
Customers, products, contract prices and stock are read for checking, and confirmed orders are written back as sales orders, with the source document attached where the ERP allows it.
Customer code mappings
The table of each customer's codes and descriptions against yours, built up as the team confirms matches. It can start from any cross-reference spreadsheet your office already keeps.
Outgoing email
Confirmations and queries go back to the sender from your orders address, in the same thread, so when a customer replies to say a line is wrong, the reply lands beside the order it is about.
The first version
Start small, then grow it
A first version should be useful on day one and small enough to get right. This is where we would usually draw the line, and what tends to follow once people are using it.
In the first version
- Orders read from your shared inbox: emails, PDF purchase orders and spreadsheets
- Matching to accounts and product codes, with a code table that learns
- Price, pack size, minimum and stock checks on every line
- A review screen with the original document beside the extracted order
- Every order held for review at first, then automatic for chosen accounts
Once it is in use
- Photos and scans of handwritten lists read as well
- Confirmations and short-stock replies sent from your orders address
- EDI and Peppol orders brought into the same checks and queue
- A weekly report of unmatched codes and why orders needed review
Buyer's guide
Before you commission one
Four decisions worth making before automating order entry, so the software fits the orders you actually receive.
- 01
Packaged order automation or built for you
Sales order automation is an established software category, sold as stand-alone products and as add-ons to some ERPs. If one reads your customers' formats well and writes cleanly to your ERP, it may be the better buy. Built for you makes sense when the checks depend on your own pricing and credit rules, or per-document fees outgrow owning it.
- 02
What to gather first
A few weeks of real incoming orders, untouched, across every format you receive. Any cross-reference spreadsheets of customer codes. Your rules for when an order must be checked by a person, written down if they are not already. And the accounts that send the most orders, because that is where automation saves the most retyping first.
- 03
Who should own it
The sales office or customer service manager. They own the review queue, decide when an account is trusted to go straight through, and keep the code mappings tidy. Credit control owns the credit holds and whoever runs the ERP owns the connection, but the queue needs one named owner who checks it every morning.
- 04
How you will know it is working
Watch how long orders wait between arriving and being created, how many need review and why, which accounts still send codes that never match, and how many deliveries are corrected because of an entry mistake. Track the review reasons over time: a short list of the same few reasons is a good sign.
Terms worth knowing
The words you will meet
- OCR
- Optical character recognition: software that turns a scanned page or a photo into text. On its own it gives you words, not an order. The real work is deciding which words are the customer, the lines and the quantities, then checking them against your products and prices.
- EDI
- Electronic data interchange: orders sent from system to system in an agreed structured format, such as the X12 850 purchase order or a Peppol eOrder. Where a large customer offers EDI, it is usually a better route than email. Order capture is for everyone who sends documents instead.
- Straight-through processing
- An order that goes from arrival to your ERP with no person touching it, because every line matched and every check passed. The aim is not to make every order straight-through, but to let the clean ones go so people have time for the ones that need judgement.
Handled with care
The details that matter here
Automating order entry swaps the risk of typos for the risk of confident mistakes. These are the places we are most careful.
A person in the loop until trust is earned
We start with every order held for review, so your team sees what the software would have done before it does anything on its own. Automatic creation is switched on account by account, by you, once that account's matches have been right for long enough to trust.
AI only where the input is messy
Reading a scanned list or a chatty email needs a language model. Checking a price against a contract does not. We use rules for every check and the model only for reading, and the extracted order is always checked against your real data before anything is created.
Customer documents and where they go
Purchase orders carry names, addresses and prices. Any provider that reads them for you is a processor under UK GDPR and EU GDPR, which means a written contract. We agree with you where documents are processed and stored, choose providers that do not train on your data, and log who viewed or changed each order.
Every decision traceable
For each order we keep the original email, what was read from it, which matches and checks applied, who reviewed it and what they changed. When a customer disputes a delivery weeks later, your team can show what was sent and what was entered.
Guides
Worth reading first
Questions
What buyers ask first
What happens when order automation can't read an order?
It says so and stops. Any line it cannot match with confidence, any price that disagrees with the contract and any quantity that breaks a pack size goes to the review queue with the reason beside it. Uncertain orders are not created quietly. A person decides, and when they confirm a match, the software remembers it for that customer next time.
Do customers need to change how they send orders?
No, and that is the point. They keep emailing the same address in the same format. If a customer later wants to try a trade portal, both routes end in the same ERP, so nothing changes for your warehouse. Occasionally, where one account's orders are hard to read every time, we might suggest asking them for a spreadsheet instead of a photo.
What is the difference between order automation and EDI?
EDI is a structured feed agreed between two systems, usually with larger customers, and where you already have it, it is the better route. Order automation is for orders that arrive as documents written for people to read. The two sit side by side, and if a customer moves to EDI later, their orders can still pass through the same checks.
Can order entry automation read handwritten or faxed orders?
Often, though not always. Clear photos of neatly written lists can usually be read, and every line the software is unsure of is marked. Smudged faxes, crossed-out lines and products described by nickname are harder, and those go straight to review. We test on a sample of your real orders early and tell you which kinds are worth automating.
Can AI extract data from purchase orders reliably?
Language models read typed purchase orders and chatty emails far better than older template tools did, but they still make mistakes, and they make them confidently. That is why every extracted line is checked against your real products, prices and account rules before anything is created, and why anything uncertain goes to a person. We measure it on your own orders before switching anything to automatic.
Send us last week's messiest orders
Pick a handful of real orders that arrived by email, PDF or photo, with customer details removed if you prefer. We will reply within 48 hours with which ones could be read and checked without retyping.
More for wholesale
What else we build for wholesale and b2b
Trade ordering portals
A logged-in store for trade buyers with account-specific price lists, minimum quantities, pack sizes, order pads and one-click reorder from history. Customers order when it suits them, and orders arrive already checked against price and credit rather than in an inbox.
Ordering apps for reps
Your field reps take orders on a tablet at the customer's premises, with live prices, stock and the account's history to hand. The app keeps working in a cellar or a basement with no signal and syncs as soon as it is back online.
Pricing and quoting tools
Your pricing rules, from contract prices and volume breaks to promotions and approval thresholds, taken out of a fragile spreadsheet and turned into a tool anyone on the team can use, with a full history of what was quoted to whom.
ERP and accounts integration
Orders, customers, prices and stock flowing between the portal and your ERP, warehouse system or accounts package, with one agreed system in charge of each piece of data. Nothing is retyped, and a failed sync alerts someone instead of vanishing.
Demand forecasts and reorder alerts
Forecasts by product line that account for seasonality, promotions and supplier lead times, with reorder points and alerts when a line starts selling faster or slower than expected, so buying decisions start from a tested number rather than last year's gut feel.


