Sales order processing automation

Customer orders that go into your system without anyone typing them

Emailed and PDF orders are read, checked against your prices and your rules, and lined up for your team to approve. The typing goes. The checking stays with a person.

What it is: Sales order processing automation takes the orders that arrive by email, PDF attachment or spreadsheet, reads the customer, products, quantities and delivery details, checks them against your price list and your rules, and shows them to a person to approve before they are written into your existing order system. It removes the re-typing, not the human decision, and it works with the system you already have.

Sandra types the same order twice. Sixty times a day.

Sandra has run the order desk at a food wholesaler for 14 years. Orders come in by email overnight, most of them as PDFs. Each morning she opens one, finds the customer's account in Sage 50 and types it in, line by line. She knows that "the usual" from the café round the corner means two cases of the 2.5kg cheddar, and that the school orders have to be in by 2pm to make the next-day van.

Say she keys 60 orders a day at four minutes each. That is four hours of every working day spent copying. When she is on holiday, orders go in late or wrong, because half the rules are in her head.

The orders are already read when Sandra sits down. Each one is on her screen beside the customer's original, matched to the right account and the right products, with the 2pm cut-off and the minimum order already checked. She reads it, clicks approve, and it is in Sage. The three the software was unsure about are waiting at the top, each with a note saying why.

She spends the morning on the phone to customers. The rules that lived in her head are written down, so the desk still works in August.

The people in this story are made up. The work is not. Your own figures come from the assessment.

What it is worth. Sixty orders a day at four minutes each is about 960 hours a year. At £20 an hour all in, that is £19,200 of Sandra's time. These are example figures, not a client result. The assessment replaces them with yours. Try your own numbers in the calculator. Or watch a sample order go through.

Who it is for

Wholesalers, distributors, food suppliers and manufacturers whose trade customers send orders by email, PDF, spreadsheet or portal, and whose office types them in by hand.

What you get

  • Your orders inbox watched for you. Nothing changes for your customers.
  • The customer, delivery address, products, quantities, dates and references read from the email, the PDF or the spreadsheet.
  • Each order matched to your customer accounts and product codes, including the names each customer uses for your products.
  • Your rules applied every time. Cut-off times, minimum order values, carriage charges, credit holds, substitutions.
  • One screen where your team sees the order as read, side by side with the original, and releases it with one click.
  • Anything it is unsure about held for a person. Unknown products, missing quantities, prices that do not match, duplicates.
  • The sales order created in your existing system, by a route that system supports.
  • A record of every order, every change and who approved it.

Price

£1,500 to £7,500

Emailed orders into one system is usually at the lower end. Several ways of ordering, customers with their own names for your products, or more than one system push it higher. See the pricing page for how bands are set.

Ask about sales order processing automation

How it goes

  1. We collect real orders

    We take 50 to 100 real orders from your inbox, with customer details covered by a written data agreement, and use them to design and test.

  2. We teach it your customers and your rules

    The reading is tuned to the way each of your customers lays out an order. Rules such as minimum order and cut-off are written as plain checks you can read.

  3. We connect it to your system

    Orders are created in your order system the way it expects them, tested first against a copy.

  4. It runs alongside your team

    For the first weeks your team types orders as normal and compares. When it has proved itself on your own orders, they switch to approving.

Questions people ask

Our customers all send orders in different formats. Does that matter?

That is the normal case and it is what the reading step is built for. Each customer's layout is learned from real examples. Odd ones are held for a person until they are handled reliably, so a strange format never produces a wrong order.

What about phone orders?

Phone orders still need someone to take them. Where they are a large share, we look at a simple reorder page for regular customers, or a quick form for the person taking the call, so nothing is typed twice. We will tell you if too few of your orders are written down for the project to pay.

Does it work with Sage 50?

Yes, in most set-ups, although Sage 50 has no API, which is the usual way for one program to talk to another. Orders reach it through its import features, the Sage Data Objects developer interface, or an established third-party connector, and the right route depends on your edition and volumes. Sage 200, Xero, QuickBooks, Pegasus Opera, Khaos Control and Business Central each have their own supported route. See the systems pages for detail.

How accurate is it?

We measure that on your own orders while it runs alongside your team, and agree the pass mark in writing before it goes live. Anything the software is unsure about goes to a person, so the practical question is how many orders need a human look, not how many go wrong.

Related reading

Find out what the typing is costing you

A 20-minute call. You tell us about your Sandra, your Dave or your Phil, and how the job gets done today. We tell you honestly whether automating it would pay, and what it would cost.