Orders entered for you, with the mistakes caught first.
Restaurants and grocers send orders as PDFs, Word files and emails, each in their own format. We build order processing that reads every one, checks each line against your catalogue and drafts the order and the reply for your team to approve.
Where the orders slow down.
Every customer has their own format.
One sends a PDF, another a Word file, another a list typed into an email. Someone retypes them all.
One typo ships the wrong order.
A 12 typed as 21 means a credit, a second trip and a customer who has to call you.
Mistakes in the order itself.
Totals that don’t add up, items you no longer carry, a delivery date before the order date.
Busy mornings before the cut-off.
Orders pile up right when the team has the least time to check them.
What we built for a food distributor.
A client project, shown with sample data. Orders are read from the inbox they already arrive in.
A restaurant’s order arrives by email.
It reads the order and pulls out each line, the total and the delivery date.
It finds five problems.
The total doesn’t match the items, the olive oil is discontinued, so it suggests the replacement, and the delivery date is before the order date.
Your team fixes them in a few clicks.
The order is created, and a confirmation email to the customer is saved as a draft for you to send.
Other things we could build for a distributor.
Answers for customers’ questions
Delivery days, cut-off times and product questions answered from your own information, in your inbox or on your website.
AI assistantsSupplier invoices, checked for you
Invoices are read and checked against your rules, and anything that doesn’t match is flagged for a person.
Document processingA dashboard of the week’s orders
Orders, open problems and your busiest customers in one place, instead of a stack of spreadsheets.
Custom software
What stays with your team.
- Approving every order. Nothing is created or sent until someone on your team approves it, as in the project above.
- Substitutions. The replacement for a discontinued item is a suggestion. Whether it suits the customer is your team’s decision.
- Credit and special prices. Customer terms and special prices follow your rules, and anything unusual goes to a person.
Customer information.
Orders carry names, emails, delivery addresses and account terms. The personal information in them is covered by PIPEDA, and in Quebec by Law 25.
We agree in writing where orders are processed and stored, who can see them and which AI services, if any, read them. If your customers’ data needs to stay in Canada, we plan around that from the start.
It works with your inbox and your order system.
Orders are read from the inbox they already arrive in. Each line is checked against your catalogue and price list, and the finished order goes into your order or accounting system, or a spreadsheet, wherever your team works today.
- Your order inbox
- Catalogue and price list
- Order, inventory or accounting system
- Spreadsheets
Questions distributors ask.
More on cost, data and ownership in the FAQ.
What formats can it read?
Orders sent as PDF or Word, as in the project above, scans and orders typed into an email. If customers send something else, bring examples to the first call.
What happens when it isn’t sure?
It flags the line for a person instead of guessing. Your team sees what it read and what looks wrong.
Does it work with our system?
If your order or accounting system lets other tools add orders, yes. If it doesn’t, the order can be prepared for quick entry or a spreadsheet. We check on the first call.
Do our customers have to change how they order?
No. They keep sending orders the way they do now.
Retyping orders, invoices or forms?
Start with a free one-hour call. Bring a few real orders, and we’ll show you what it would catch.