Order processing
Still typing the PO and then typing the whole order again? How to stop re-keying customer orders
Re-keying stops when an order is captured once, in a form a machine can read, and every later document is produced from that single record. The cheapest fixes are asking customers for spreadsheets and switching on your system's import. The dearest is a new ERP. In between sits a reader that turns emailed PDFs into checked, approved sales orders in the system you already run.
It is half past one on a Thursday and Sandra is back from lunch with three sheets torn off the pad by the phone. Each is a phone order from the morning, in her own shorthand. She types the first into Sage 50. Then she opens a Word template, because this customer pays up front, and types the same lines again as a pro-forma. Beside her keyboard is a stack of printouts. They are orders from the firm’s own website, which emails them to the office, where someone prints them so that Sandra can type them back in. A PDF purchase order arrived while she was out. That one will be typed twice as well.
Sandra is made up. The pad by the phone is not.
Everything she typed this afternoon had already been written down once, by the customer, by the website or by Sandra herself.
Key facts
- Re-keying is any time a person types information that already exists in a document or another system.
- On a typical order desk it hides in five places: the customer PO, web shop orders, spreadsheet orders, phone orders, and the documents raised after the order.
- Hull sales order processor roles are advertised at £12.21 to £15 an hour, which is the labour cost each re-keyed order carries.
- Sage 50 has no web API, meaning no built-in way for other software to talk to it over the internet, so stopping re-keying into it means an import file, Sage Data Objects or a connector.
- Keeping a person to approve every automated order removes the typing without removing the judgement.
Where does re-keying hide on an order desk?
In five places. Sandra’s Thursday has all of them, and most firms have at least three. The quotes below are from UK business owners and office staff on public forums, in their own words.
- The customer’s PO into your sales order. A customer emails a purchase order as a PDF. Sandra opens it, finds the account and types each line. One Sage 50 user put it plainly: “At the moment I am typing the PO and then typing the entire order out again in the SO which can be very time consuming” (Sage Community Hub). Another asked whether anyone could “automate the process of manually entering sales orders from PDF purchase orders received via email” (Sage Community Hub).
- Web shop orders. The website takes the order and emails a confirmation. The office prints it, and it joins the stack by Sandra’s keyboard. One Sage 50 user had web orders “which we are presently printing, and then typing back in to Sage” (Sage Community Hub).
- Spreadsheet orders. Larger customers send an Excel schedule, and each line is typed again. On UK Business Forums one firm described “a person manually inputting hundreds of transactions each month and it takes forever” (UK Business Forums).
- Phone and WhatsApp orders. The order is written on the pad or sits in a chat thread, then is typed into the system later, often by a different person and sometimes after the cut-off.
- The documents after the order. The sales order becomes a pro-forma, a picking list, a delivery note, a courier booking and an invoice. If any of those lives in a different system or a Word template, the same lines get typed a second or third time. Quoting has the same shape. One UK Business Forums member had got quotes down from what “used to take almost a full day” to about an hour, and still disliked doing them (UK Business Forums).
The pattern across all five is the same. The information had already been written down once, and a person became the link between two systems.
What does re-keying cost, and who pays for it?
The visible cost is hours. The hidden cost is errors, late orders and a desk that depends on one person.
Start with hours. The formula is Better Systems Co.’s own and every number is a labelled assumption. The ROI calculator lets you use your own.
- Say Sandra keys 20 customer POs a day from PDF or email, at 5 minutes each.
- Say she re-types 15 printed web orders a day, at 3 minutes each.
- Five days a week, 48 working weeks a year.
- A cost to the firm of £16 an hour, a little above the £12.21 to £15 an hour advertised for Hull sales order processor roles (Michael Page, Adecco), to allow for employer costs.
POs: 100 a week × 5 ÷ 60 × 48 = 400 hours a year. Web orders: 75 a week × 3 ÷ 60 × 48 = 180 hours a year. Total: 580 hours a year, or £9,280 of capacity at £16 an hour.
That is capacity released, not cash saved. It is roughly a third of one person’s working year spent as a photocopier. Linda, who owns the business, pays for it twice. She pays once in Sandra’s wages, and again in the work Sandra has no time for, such as ringing the customer whose orders have been getting smaller.
Then the errors. A case keyed as a single. An old price because the new agreement never reached the order desk. Two digits of a quantity swapped. We do not know your error rate, and neither does anyone selling you software. Counting it is one of the things an automation audit does. What we do know is that each error costs a credit note, a redelivery and a phone call, and that the customer remembers it longer than you do.
Then timing. An order emailed at 7pm sits under the next morning’s messages. If the van leaves before Sandra reaches it, the order misses a day. The customer does not see her inbox. They see the late delivery. A supplier whose system takes that order in at 7pm can have it on the first van, and customers notice which supplier that is.
And then the person. Every order desk has a Sandra, who knows that “Smiths” means account SMI003 and that “the usual” means six cases of the semi-skimmed. Who covers the order desk when she is on holiday? Orders wait or go wrong. That knowledge is in her head because the system never asked for it in a form it could keep.
What are the options, from cheapest to dearest?
Six, and you can combine them. The right answer for many firms is the second and the fifth together.
| Option | Rough cost | What it fixes | What it does not fix |
|---|---|---|---|
| Ask customers for spreadsheets or a set layout | Goodwill only | PDF reading, for the customers who agree | Most will not change for you |
| Your system’s own import | Time to build a template | Spreadsheet orders imported, not typed | Someone still prepares the file; errors in the file go in silently |
| Import tools such as Adept Tools, PostTrans or Excel2Sage | Licence per user or year | Better checking and field matching than the plain import | Still spreadsheet-in, so PDFs and emails are not covered |
| Web shop connector | Monthly subscription | Web orders arrive in the system without printing | Only the web orders; another supplier in the chain |
| Bespoke reader with human approval | £1,500 to £7,500 to build, £150 to £1,500 a month to support | Email, PDF and spreadsheet orders read, matched, checked and lined up for a person to approve, then written into the system you already run | Phone calls still need a person to answer them |
| New ERP, one system for stock, orders and accounts, with order reading built in | The dearest by a wide margin, plus migration and retraining | Everything in one system | Replaces the system your staff know; the order-reading part is often an add-on anyway |
On the first option, a reply in the Sage thread above said OCR, the software that reads text off a scanned page, had proved “a lot less reliable than just getting the orders in excel format”. That was honest for the tools of the time, and it is still true that a spreadsheet is easier to read than a PDF. The trouble is that Sandra rarely gets to choose what a customer sends her.
If your accounts system is Sage 50, the fifth option has one extra wrinkle. Sage 50 has no web API, so the reader writes through an import file, Sage Data Objects or a connector. Our post on getting emailed PDF orders into Sage 50 covers the routes and their costs, and the Sage 50 systems page covers the editions. Older or bespoke systems with no API at all are covered in how to integrate a legacy system that has no API.
Why keep a person approving every order?
Because the typing was never the valuable part of Sandra’s job. Her judgement was.
She knows which customer is on stop, which product is being discontinued, and which delivery address the customer really uses even though their PO says otherwise. Software that reads an order and writes it straight into Sage throws that away. Software that reads an order and shows it to her keeps the judgement and removes the typing.
In practice the approval screen shows the order as read beside the original PDF or email. Lines the software matched with confidence are green. Lines it was unsure about, an unknown product name or a quantity it could not read, are flagged. Sandra corrects or confirms, and clicks once. Anything with a problem the software recognised, such as a duplicate PO number or a price that does not match the account’s agreement, is held back for her to sort out and is not offered for approval at all.
This also answers the worry one Sage user raised in the same thread about web orders: “I’m not sure I want to trust anyone with API type access” (Sage Community Hub). With a person approving, nothing reaches the system that a named member of your staff has not seen. A record is kept of who approved what and when. Our plain-English guide to sales order processing automation explains the full step-by-step.
What does Sandra’s Thursday look like afterwards?
Half past one on the same Thursday. The PDF order that came in over lunch has been read and is waiting on her screen beside the original. She checks it and clicks once. The website’s order emails were read the same way, so nobody printed them. When the phone rang this morning she typed each order into a form on the screen while the customer was still talking, and the form became the sales order. The pad has a phone number and a doodle on it. The pro-forma came out of the same record without anyone opening Word.
Not every firm needs all of that at once. The typing that costs the most gets fixed first. For Sandra, the 580 hours a year in the example above become checking and clicking, and she spends the afternoon ringing customers who have gone quiet. Linda stops wondering whether the desk needs a second person just to keep up with the typing.
What we would do
We would begin with an automation audit at £500 to £1,250, credited against any build. We sit with the order desk, count how many orders arrive by each of the five routes above, time them, and collect fifty to a hundred real orders under a data agreement. The report tells you which of the six options fits, with the arithmetic done on your numbers and the cost of the typing in pounds. If a reader with approval is the answer, that is our sales order processing automation service, usually a quick win at £1,500 to £3,000 for one kind of order into one system. Where the re-keying is between two systems you already own, such as a web shop and Sage, it is a system integration job. Any unfamiliar term is in the glossary.
Sources
- Sage Community Hub, “Purchase and sales orders”: https://communityhub.sage.com/gb/sage-50-accounts/f/general-discussion-uk/117718/purchase-and-sales-orders
- Sage Community Hub, “Sage 50 Accounts - sales order generation - automation software”: https://communityhub.sage.com/gb/sage-50-accounts/f/general-discussion-uk/252855/
- Sage Community Hub, “Importing sales orders / invoices”: https://communityhub.sage.com/gb/sage-50-accounts/f/general-discussion-uk/203817/importing-sales-orders-invoices
- UK Business Forums, “Uploading Excel info to Sage”: https://www.ukbusinessforums.co.uk/threads/uploading-excel-info-to-sage.261887/
- UK Business Forums, “I hate quoting”: https://www.ukbusinessforums.co.uk/threads/i-hate-quoting.90897/
- Michael Page, sales order processor role, Hull: https://www.michaelpage.co.uk/job-detail/sales-order-processor/ref/jn-032025-6697236
- Adecco, order processor role, Hull: https://www.adecco.com/en-gb/job-search/order-processor-mk058-hull-east-riding-of-yorkshire/broadbean_644851779190287
Questions people ask
Our customers will not change how they send orders. Does that rule out automation?
No. Most order automation is built on the assumption that customers carry on sending whatever they send today, in PDF, email text or spreadsheet. The reading step is tuned to each customer's layout from real examples. You only ask customers to change if the volume from one of them is high and their format is unusually hard to read.
Will stopping re-keying mean fewer people on the order desk?
In firms of 10 to 100 staff it usually means the same people doing different work. The hours released go on chasing deliveries, calling customers and clearing backlogs that never got done. Where a business is growing, it means not hiring the next order processor. We model it as capacity released, not headcount removed.
Can we automate but still check every order before it goes in?
Yes, and we would insist on it. The approval screen shows the order as read beside the original document. A person releases it with one click or corrects it. Anything the software was unsure about is already flagged. Routine orders can be approved in bulk later, once accuracy on your own orders is proven.
What about orders that come in by phone?
Phone orders still need someone to take the call. What can change is the second typing: the call notes go straight into an on-screen form that becomes the sales order, rather than onto a pad to be typed later. If phone is most of your volume, we will tell you the project may not pay.