Automate sales order entry without replacing your ERP

A customer emails a purchase order as a PDF. Someone in sales admin opens it, finds the customer in the ERP, looks up each item from the customer’s own reference, types in the quantities, checks the price and sends a confirmation. The next day it happens again, with another customer, another layout and another way of writing references.

People often ask whether they need a new ERP to get out of this. Usually they don’t. Your ERP can already take orders through a door other than the keyboard. The work is to prepare what arrives by email so it can go through that door, with the right checks, and to leave your team the parts that genuinely need judgment.

Where your orders come from

Before automating anything, look at the channels.

EDI. Structured documents exchanged directly between the customer’s and the supplier’s systems, following standards. GS1 France lists the order, the despatch advice and the invoice as the most widely used EDI messages in the French market. When a large customer orders through EDI, the order already arrives clean. That part is solved.

Customer portals. Some distributors let customers order online. The customer does the typing, which moves the data entry rather than removing it.

Email. Everything else: a PDF generated by the customer’s system, a spreadsheet, a photo of a paper form, a few lines in the body of the message. For many distributors this is most of the orders from small and mid-sized customers, because setting up EDI takes work that many of them have never done. Even “light” EDI doesn’t remove the typing: describing web-form EDI, GS1 notes that data entry stays manual.

Email is where automation makes sense.

Your ERP already has a way in

Most current ERPs can create an order without anyone using the entry screen. Two examples among many:

• Microsoft Dynamics 365 Business Central documents an API endpoint that creates a sales order.
• Odoo can import data into any business object from an Excel or CSV file, and also offers an API.

Check the limits first. Odoo’s documentation, for instance, says its external API isn’t available on some subscription plans. Some older ERPs only accept a file import, or a connector sold by the vendor. So the first question is simple: through which door does your ERP accept an order, and on what conditions?

If that door exists, there’s no reason to replace your ERP to automate order entry.

What you can automate around the ERP

Here is the typical flow.

1. Collection. Orders arrive at a dedicated address. A first pass separates real orders from chasers, questions and read receipts.
2. Reading. Pick out the customer, their PO number, the lines, quantities, delivery date and address. For a customer whose POs always look the same, a template is enough. For layouts that vary, an AI tool can help, as long as everything then goes through the checks.
3. Reference matching. Customers write their own item references, not your item codes. A cross-reference table per customer links the two, and it grows as orders come in.
4. Checks. Price against the customer’s price list, pack size, available stock, credit limit, duplicate POs. That last one matters: a customer who resends a PO “just in case” shouldn’t create two orders.
5. Draft creation. The order lands in the ERP unconfirmed, with discrepancies flagged at the top.
6. Approval. Someone in sales admin reviews it, corrects anything that needs it and approves. The ERP then produces the confirmation, delivery note and invoice as usual.

A concrete example of a useful check: a customer orders “12 cases of 50” of an item you sell individually. Is that 12 or 600? Someone in a hurry can get it wrong either way. A check that compares the quantity with the pack size on the item record raises the question before the order reaches the warehouse.

Another check you shouldn’t leave to the ERP alone is credit. In Business Central, for example, exceeding a customer’s credit limit triggers a warning when the order is entered, but the documentation says you can still post. If your rule is to block, the flow has to enforce it.

What should stay with your team

The aim is a prepared order that someone checks in a few seconds when everything is normal, and really examines when something is off.

These stay human:

• new customers, with no terms or reference mappings on file yet;
• unknown or ambiguous references;
• differences between the PO price and the agreed price;
• quantities that are unusual for that customer;
• credit limit overruns;
• changes and cancellations to orders already entered;
• and, at the start, approving every order, until you see what the flow misses.

Your sales admin team knows your customers. They know who always orders on Mondays, who writes references backwards and who negotiates every line. That knowledge then goes into handling exceptions, instead of being buried in typing.

A note for companies invoicing in France

What you capture on the order ends up on the invoice, and in France the invoicing rules are getting stricter. Since 1 September 2026, every French company must be able to receive electronic invoices; large and mid-sized companies must also issue them, and small businesses will have to from 1 September 2027. The French Ministry of the Economy is explicit that an ordinary PDF sent by email will no longer count as compliant.

The reform also adds new mandatory details, including the customer’s company ID (SIREN) and the delivery address when it differs from the customer’s. The customer’s PO number, when they issued one, was already mandatory. A badly identified customer or a PO number lost at entry becomes a problem later, so capturing it cleanly at order time pays off.

When it isn’t worth it

Automating order entry isn’t always a good idea. Hold off when:

• Volume is low. A handful of orders a day, each keyed in a few minutes, doesn’t justify a flow you’ll have to build and maintain.
• Every order is a negotiation. If orders arrive as free text with special requests each time, most of the work is judgment, not typing.
• Your ERP has no usable way in. Without an API or import, the remaining option is software that drives the screen like a person would, and it breaks whenever the interface changes.
• Your master data is a mess. Duplicate customers, item codes that change, no mapping to customer references: clean up first, or you’ll automate the errors.
• Your big customers are ready for EDI. Then EDI is the better answer for them.
• Nobody can handle exceptions. A flow that flags problems nobody looks at is useless.

How to start

Start by counting. How many orders a week, from which customers, in what form? How long does a simple order take, and a messy one? Your own numbers are worth more than any average you’ll find online.

Then pick two or three customers whose orders always look the same and arrive regularly. Build the flow for them only: reading, checks, draft, approval. For a few weeks, watch what your team corrects. If corrections become rare, extend it to more customers. If they stay frequent, you’ll know why before spending more.

We’ve described this flow in a use case on customer orders checked before they reach the ERP. If supplier prices cause the same kind of trouble upstream, our article on what to check before importing a supplier price list picks up from there.

If you’d like us to look at your own order flow, tell us about it. We’ll tell you honestly what’s worth automating and what isn’t.

Sources

• GS1 France, EDI : échange de données informatisé (in French; most used messages, limits of web-form EDI).
• Microsoft Learn, Create salesOrders, Register new customers (credit limit warning) and Sell products, Business Central documentation.
• Odoo, Export and import data and External API, version 20.0 documentation.
• French Ministry of the Economy, Tout savoir sur la facturation électronique pour les entreprises (in French).
• Service Public Entreprendre, Tout savoir sur la facturation (in French; checked by the publisher on 7 August 2026).