On this page
What “AI order entry” has to mean for a distributor
A customer’s purchase order rarely arrives in a form your ERP can take. It is written in the buyer’s part numbers, descriptions and units, as a PDF from their purchasing system, a scan, a spreadsheet or three lines in an email. Someone on the sales desk re-keys it: the customer account, the delivery address, which catalogue item each line means, the price. According to our case study, a sales rep spends on average 4–7 minutes per line when creating quotes and orders by hand.
Software that reads the PDF into fields removes the typing and leaves that work where it was. The software worth buying decides which of your products each line means and prepares the sales order for approval. What the manual work costs per order is worked through in the cost of manual order entry.
What AI order entry software has to get right for a distributor
Six requirements, each with what ERP Agent does.
- Orders as customers actually send them. A PDF exported from a purchasing system, a signed order scanned or photographed, an Excel list, lines typed into the email. ERP Agent reads the email body and its attachments: PDF (scanned PDFs included), Excel, CSV, Word, images and forwarded emails.
- The buyer’s part numbers, not yours. ERP Agent maps the buyer’s material numbers and article codes to your catalogue, shows the customer’s code on the line and learns from each order your team sends, so the next purchase order with the same number gets the same product. See purchase order to sales order automation.
- The right customer and the right address. It looks the customer up in your customer register, alerts the rep when there is no match and flags a delivery address that differs from the one in your ERP.
- The agreed price. Prices come from the data and rules configured for your company; once your ERP is connected, from its own price logic, customer-specific prices included. Your team can edit any price.
- No template per customer. Template-based capture needs a layout set up for every customer’s order form. ERP Agent identifies the products from the customer’s own words and part numbers, so a customer who orders for the first time is handled like your largest account.
- Nothing saved that the ERP does not know. Product codes are checked against the ERP before anything is saved, a line too vague to identify goes on your placeholder code, and a person approves before the sales order is created. Every line carries a match score from 0 to 100, and lines under 80 are marked.
Ten orders to test any AI order entry tool with
Take them from your own inbox: orders your team has already entered, so you can compare each draft with the sales order that was actually created.
| Test order or line | What it tests | What ERP Agent does with it |
|---|---|---|
| A PDF order exported from a customer’s purchasing system, in their material numbers | The buyer’s own part numbers | Maps the numbers to your catalogue, shows the customer’s code on the line and learns from each order your team sends. |
| A signed order scanned to PDF, or a phone photo of one | A document nothing can be copied from | Read with OCR and matched line by line like any other order. |
| Order lines typed into the email, with no attachment | No document at all | Reps forward or paste it as it is; there is nothing to tidy up first. |
| “CONTACTOR 3P 18A 24VDC COIL, 6 EA” | A rating that must not be confused | Proposes the 24 V DC coil version; the 230 V AC coil versions are pushed down. |
| “M12 anchor bolts for concrete, as last time, 50” | A line that leans on what the customer bought before | With sales history, proposes the product this customer buys, and marks the line when a detail such as the length is not stated. |
| A line with only the buyer’s code, the first time you see that code | What the tool does when it cannot know | With nothing else to go on, the line goes on your placeholder code with the buyer’s wording kept. The rep picks the product, and once the order is sent the agent has learned the pair. |
| An order from a company that is not in your customer register | An unknown customer | Alerts the rep straight away that no customer matches. |
| An order for delivery to site, with no postcode | A delivery address that differs from the account | Tidies the address, fills in a missing postcode and flags that it differs from the one in your ERP. |
| A Swedish or German order against your English catalogue | Another language | Identifies the right products across languages. |
| An Excel order of several hundred lines | Volume | Takes about half an hour, split into batches that run in parallel; lines appear in the review table as they are matched. |
Count four things for every tool: lines with the right product, lines your team had to change, orders where the customer or the address was wrong, and the minutes a person spent per order including review.
Where the other kinds of software stop
| Kind of software | What it is built to do | What is left for your order desk |
|---|---|---|
| Document capture and OCR | Turns the order into text and fields | The line still says “nyloc M10 A2” or the buyer’s material number: someone finds the product, the unit and the price. Template-based capture also needs a layout for every customer |
| EDI | Structured orders from accounts that already send your product codes | Every customer who orders by email, PDF and Excel in their own words |
| CPQ configurators | Builds quotes for configured products from option rules | Incoming purchase orders, which it was not made to read |
| AI built into the ERP | Features the ERP vendor ships inside its own product, for that one ERP | Whatever falls outside those features. ERP Agent works on top of any ERP and is built for distributors’ orders: the buyer’s part numbers, a score and reasoning on every line, orders in other languages |
| A general AI assistant | Writes fluent text on request | It does not know your catalogue, your customer prices or your ERP unless someone connects them, so it cannot turn a buyer’s material number into your product code |
| ERP Agent | Prepares the sales order with your products and the customer’s prices | Checking the marked lines and approving |
EDI and your webshop keep running as they are. ERP Agent takes on the orders people write by email, PDF and Excel.
How to run the test in a week
Orders your team has already entered make the fairest test: the right answer is in your ERP.
Pull 30 to 50 entered orders
Mix them: clean PDFs, scans, orders in the buyer’s part numbers, a long Excel order, one from a new customer and one in another language.
Start from your catalogue file
Send an export of your product catalogue and start the same week. Past orders and sales history help the agent learn your customers’ part numbers and what they usually buy.
Forward the original emails
Reps forward each order to your company’s own agent mailbox, or drop it into the web app and pick sales order. A typical order takes the agent 3–8 minutes.
Compare each draft with the order that was entered
Line by line: product, quantity, price, customer and address. The AI quote agent pilot checklist covers sales orders too and has a scoring sheet.
Work out the saving
Put your monthly order lines into the cost calculator, and use the cost of manual order entry to add what entry errors cost you.
ERP Agent in numbers
- 4–7 min
- per line when a sales rep creates quotes and orders by hand, according to our case study
- Over 95%
- average automation across our customers
- 3–8 min
- for the agent to prepare a typical request
- 1–3 min
- in fast mode, for requests of up to about 50 lines
- 0–100
- match score on every line; under 80 is marked for review
ERP Agent is live with steel, HVAC and fastener distributors. How the agent works on orders, step by step, is in AI order entry automation for distributors; the terms are in what order entry means. The same agent prepares quotes from the same kind of request: see quote automation and the LVI-WaBeK customer story.
