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
Demo: sales order processing automation
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.
| They wrote | Matched to | Qty | Price |
|---|---|---|---|
| usual | Frying oil, 20 litre drum | 1 | £27.00 |
| usual | Burger buns, tray of 48 | 2 | £18.00 |
| usual, plus 2 extra | Chips, 4 × 2.5kg box | 4 | £46.00 |
| Goods | £91.00 | ||
| Delivery | Free | ||
| Total before VAT | £91.00 | ||
"Usual" matched to the three lines on this customer's last four orders.
Jo asked for tomorrow, but today's 2pm cut-off has gone. The earliest delivery day is Thursday.
Answer the question above first.
Approved. This is the moment the order would go into Sage.
Nothing was sent anywhere. This is a demo, and every example in it is made up.
The email, as it arrived
Purchasing at the hotelMonday, 10.22am
PO 4471
Please supply against PO 4471 for delivery Wednesday:
CH-204 Chopped tomatoes 6 x 2.5kg x 2
OL-110 Olive oil 5 litre x 1
FL-032 Plain flour 16kg x 1
Regards, Purchasing
Order, ready for Sandra
Nothing has been read yet. Press "Read it" and watch what a person would otherwise type.
| They wrote | Matched to | Qty | Price |
|---|---|---|---|
| CH-204, chopped tomatoes | Waiting for you | 2 | £21.00 |
| OL-110, olive oil | OL-110, Olive oil, 5 litre | 1 | £24.50 |
| FL-032, plain flour | FL-032, Plain flour, 16kg | 1 | £9.50 |
| Goods | £55.00 | ||
| Delivery | £10.00 | ||
| Total before VAT | £65.00 | ||
CH-204 is not on the product list. The description matches CH-240, Chopped tomatoes, 6 × 2.5kg.
The goods come to £55.00, under the £75 minimum. A £10.00 delivery charge has been added.
Answer the question above first.
Approved. This is the moment the order would go into Sage.
Nothing was sent anywhere. This is a demo, and every example in it is made up.
The email, as it arrived
Sam at the takeawayTuesday, 11.48am
Re: order
Sorry Sandra, make that 3 drums of oil not 5.
And add a box of mayo sachets.
Sam
Change to order 10482, ready for Sandra
Nothing has been read yet. Press "Read it" and watch what a person would otherwise type.
| They wrote | Matched to | Qty | Price |
|---|---|---|---|
| 3 drums of oil not 5 | Frying oil, 20 litre drum | 3, was 5 | £81.00 |
| add a box of mayo sachets | Mayonnaise sachets, box of 200 | 1, new | £12.50 |
| no change | Chips, 4 × 2.5kg box | 6 | £69.00 |
| Goods | £162.50 | ||
| Delivery | Free | ||
| Total before VAT | £162.50 | ||
Found the open order this email is replying to. It has not been picked, so it can still be changed.
Two lines differ from the order as it stands. Both are marked.
Answer the question above first.
Approved. This is the moment the change would go into Sage.
Nothing was sent anywhere. This is a demo, and every example in it is made up.
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.
The customer, the delivery day and each line come off the email as written, including "usual" and a product code with two digits swapped.
What the customer wrote sits beside the product it was matched to, so a person can see both at a glance.
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.
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.
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.
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.
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.
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.
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.
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.