How to automate order entry in your ERP
Updated 7 min read
Automating order entry means the orders that arrive by email, PDF, Excel or WhatsApp are read, checked against your ERP data and saved as sales orders without anyone typing them. A person only reviews the ones that don’t add up: an unknown item, a different price or a new customer.
What does typing orders by hand cost today?
More than it seems, because the cost is spread out. At 2,000 orders a month and 5 minutes per order, that’s about 167 hours a month: one full-time person just copying data from a document into a screen. At €28 an hour, roughly €56,000 a year.
Time isn’t the only cost. A wrong quantity or item code becomes a wrong shipment, a return and an awkward phone call. When the person who knows the orders is on holiday, the orders wait.
Which orders can be automated?
Almost any order someone reads and types today. The most common in an SME:
- Emails with the order in an attached PDF, each customer with their own layout.
- Excel or CSV sheets the customer sends with their own item codes.
- Orders written in the body of an email (“send me 20 boxes of the usual”).
- Photos of a paper order or WhatsApp messages from sales reps.
- Orders taken by phone, transcribed and summarised.
How does it work, step by step?
-
Collect
Orders arrive in a dedicated mailbox (orders@, for example) or are forwarded by an email rule. Every document enters a queue, and nothing gets lost in someone’s inbox.
-
Read
The AI extracts the customer, order number, delivery date, shipping address and every line: item, quantity and price. It understands different layouts without a template per customer.
-
Check against the ERP
Every field is checked against your ERP: the customer exists, the customer’s item code maps to one of your items, the price matches their price list, there is stock, and the order isn’t already entered.
-
Review only the exceptions
What adds up goes through. What doesn’t reaches a person with the original document alongside and a suggested fix. Every correction teaches the system for next time.
-
Save to the ERP
The order is created through each ERP’s official route: Service Layer or DI API in SAP Business One, the external API in Odoo, the REST API in Holded, and connectors or file imports in Sage and A3.
-
Confirm and measure
The customer gets a confirmation, every order is logged with who reviewed it, and each month you measure the hours saved and the share of orders that needed review.
OCR, RPA or AI? How they differ
All three are sold as “order automation”, but they don’t do the same thing.
| Approach | Works well when | Where it breaks |
|---|---|---|
| OCR with templates | A few customers with fixed layouts that never change. | Every new layout needs a new template; a redesign breaks it. |
| RPA (bots that click) | Data has to move between screens with no API. | It’s fragile: a screen update stops the bot. |
| AI + the ERP’s API | Many customers, varying layouts and free text. | It needs checks and a person for unclear cases. That’s why we build them in. |
What does the company need to have ready?
- An ERP used every day. We start with read-only access.
- Reasonably clean master data: customers, items and price lists.
- 20 to 50 real example orders, in their real formats.
- One person who knows the process, to set the rules: what is accepted automatically and what gets reviewed.
Start with the customer or format with the most volume and expand from there.