Demo: sales order processing automation

The order types itself in. Sandra says yes.

Three emails, the way customers write them. Press "Read it" and watch what Sandra would otherwise type. Where the software is unsure, it asks her.

The email, as it arrived

Jo at the caféTuesday, 3.10pm

order for tomorrow

Hi Sandra,

Usual please, plus 2 extra boxes of chips. Need it tomorrow if poss.

Thanks, Jo

Order, ready for Sandra

Nothing has been read yet. Press "Read it" and watch what a person would otherwise type.

Customer
The café, account CAF014
Delivery day
Wednesday
They wroteMatched toQtyPrice
usualFrying oil, 20 litre drum1£27.00
usualBurger buns, tray of 482£18.00
usual, plus 2 extraChips, 4 × 2.5kg box4£46.00
Goods£91.00
DeliveryFree
Total before VAT£91.00
  • Matched

    "Usual" matched to the three lines on this customer's last four orders.

  • Needs you

    Jo asked for tomorrow, but today's 2pm cut-off has gone. The earliest delivery day is Thursday.

Sandra, her customers, the products and the prices are made up. So are the rules this demo checks: orders in by 2pm for next-day delivery, a £75 minimum, and a £10 delivery charge under it.

In short: sales order processing automation reads an emailed or PDF order, matches each line to your products and each customer to their account, checks it against your rules such as cut-off times and minimum order values, and leaves it waiting for a person to approve. Nothing goes into your order system until someone has said yes.

What you just watched

  1. The email is read

    The customer, the delivery day and each line come off the email as written, including "usual" and a product code with two digits swapped.

  2. Each line is matched

    What the customer wrote sits beside the product it was matched to, so a person can see both at a glance.

  3. Your rules are checked

    The cut-off time and the minimum order are applied by ordinary software, the same way every time, including in August when Sandra is away.

  4. A person approves

    Anything doubtful waits with a question. The order goes nowhere until someone says yes, and a record shows what was read, what was changed and who approved it.

What it would be worth to you

That depends on how many orders your office types in and how long each one takes. Count it in a minute with your own two numbers, or read how order processing automation works on a real order desk.

Questions people ask

Is the demo reading these emails for real?

No. It plays a fixed sequence over three sample orders, so it costs nothing to run and nobody can misuse it. In a project the software reads your customers' real emails and PDFs, and we test it on a hundred of your past orders before it goes anywhere near your system.

What happens when it gets one wrong?

It is built to stop and ask. Anything it cannot match to your product list, or that breaks one of your rules, waits for a person with a note saying why. Every order is shown beside the customer's original, and nothing goes into your system until someone approves it.

Which part is AI?

Only the reading of emails and documents that are laid out differently every time. Prices, cut-off times, minimum orders and stock are checked by ordinary software that follows your rules. A person approves every order.

Does it work with our system?

Usually. Sage 50, Sage 200, Xero, Pegasus Opera, Khaos Control and most bespoke systems can take an order in by a supported route. The assessment checks how yours can, before anything is quoted.

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.