Sales order automation turns the purchase orders customers email you into sales orders in your ERP without anyone retyping them. Software reads each PO, finds the customer and the items, checks the prices and the PO number, and creates the order. An order that fails a check goes to a person on your order desk first.
Most of an order desk’s day goes to the orders that are slightly off: a customer’s own part number, a price from an old quote, a PO sent twice. A FlowRunner flow enters the clean orders on its own and brings only those to your order desk.
- 1PO arrivesA PDF, a spreadsheet, or the email text
- 2Agent reads itCustomer, PO number, every line
- 3Checked in your ERPCustomer, items, prices, duplicates
- 4Order desk decidesOnly the lines that don't match
- 5Order createdAnd the customer gets an acknowledgment
One PO, start to finish
Here is a sample PO from Ridgeline Mechanical, a contractor buying for a job site. The flow read the PDF and checked it against NetSuite. Line 1 matches. Lines 2 and 3 don’t.
| Their part number | Qty | Price | Amount |
|---|---|---|---|
| RM-PVC-075, 3/4" PVC 90 elbow | 20 CS | $18.40 | $368.00 |
| Matched to your item PVC-E90-075 at their price. | |||
| 44-1180, 1/2" copper tee | 200 EA | $1.12 | $224.00 |
| Their price on file is $1.19. The PO is $14.00 under. | |||
| RM-VLV-200, 2" brass ball valve | 6 EA | $46.00 | $276.00 |
| No item on file matches this part number. | |||
| Total | $868.00 | ||
The flow holds the order and asks the order desk in Slack:
Slack, the #order-desk channel
PO 4500-21877 from Ridgeline Mechanical needs a decision
Line 2, 1/2" copper tee, 200 EA. PO price $1.12, their price $1.19.
Line 3, RM-VLV-200, 6 EA. Closest items on file:
What exactly does the PO say on line 3?
"RM-VLV-200, 2 in brass ball valve, full port, 6 EA at $46.00."
Maria picks BV-200-BR and accepts $1.12, because the rep agreed that price on the phone. The flow creates the sales order in NetSuite and adds RM-VLV-200 to the cross-reference, so the next PO with that part number maps on its own. Then it emails the buyer:
Thanks for PO 4500-21877. It is entered as sales order SO-10482: 3 lines, requested for Nov 18, with line 2 at your price of $1.12. Reply to this email if anything looks wrong.
Orders that pass every check go straight in. Every run keeps a step-by-step record, so when the customer asks about line 2 next month, you can see who accepted $1.12 and when.
The same flow runs on NetSuite, Acumatica, Microsoft Dynamics 365 Business Central, SAP Business One, and Sage Intacct. POs come in through Gmail or Outlook, spreadsheets are converted with CloudConvert, and the questions go out in Slack or by email.
The exceptions that slow order entry
| Exception | What it looks like | What the flow does |
|---|---|---|
| Customer part number | They order “RM-VLV-200”, your item is BV-200-BR | Looks it up in your cross-reference, asks when there is no match |
| Unit of measure | 20 of an item you sell by the case of 25 | Asks whether they mean cases or pieces |
| Price | A price from an old quote or an expired contract | Asks whether to accept it, use your price, or hold |
| Duplicate PO | The same PO resent “in case you didn’t get it” | Stops it and shows the existing order |
| Ship-to | A new job site, or no address at all | Asks the order desk to confirm or pick one |
| Credit hold | The account is over its limit or past due | Sends the order to your credit contact |
| Stock | A line you can’t fill by the requested date | Asks about a backorder, split, or substitute |
| Messy email | Two POs in one email, or a PO plus terms and conditions | Splits the POs and skips what isn’t one |
Other ways distributors automate order entry
| Approach | How it works | When it fits |
|---|---|---|
| A FlowRunner flow | Reads emailed POs, checks them in your ERP, asks your order desk on Slack or email, and enters the order | Orders arrive by email in many formats and you want your own rules and routing |
| EDI | The customer sends an X12 850 PO and you return an 855 (Stedi’s 850 reference) | Large customers who already require EDI |
| Customer portal | Customers order on your site, which writes to the ERP | Customers willing to change how they order |
| Order-entry tools | Products built only for order capture, such as Conexiom and Proton | One job, and your ERP is on their supported list |
| ERP-native agents | An agent inside the ERP watches a mailbox, such as Business Central’s Sales Order Agent | Your whole process lives inside that one ERP |
Microsoft’s Sales Order Agent for Business Central matches items by item number, GTIN, or cross-reference and works inside Business Central. Microsoft documents that it creates a sales quote first, reads PDF, PNG, and JPG attachments, and identifies customers by the sender’s email address. Anything outside Business Central, such as a spreadsheet PO or a credit question for someone in Slack, stays outside the agent.
For the purchasing side of the same transaction, see the PO approval workflow and purchase order automation software. Distributors and 3PLs can see more on the logistics page.
How to start
Start with the five customers who email you the most POs. Their formats repeat and their part numbers are known.
For the first two weeks, send every order to the order desk before it is created. Each correction goes into the cross-reference. Once a customer’s orders come through for a week with no corrections, let their clean orders go straight in.
Frequently asked questions
What is sales order automation?
Sales order automation is software that takes a customer's order as it arrives, checks it against your customer, item, and price data in the ERP, and creates the sales order without anyone retyping it. Orders that fail a check go to a person on the order desk instead of going in wrong.
Can you automate order entry without EDI?
Yes. An AI agent can read the purchase orders customers already email you, whether they come as a PDF, a spreadsheet, or text in the email body, and a flow can check and enter them in the ERP. EDI stays the right channel for the trading partners who already send it.
What happens when an emailed purchase order doesn't match?
A well-built flow stops that order and asks a person. The order desk sees the PO, the mismatch, and the choices, decides on Slack or by email, and the flow creates the sales order with the correction and keeps a record of who decided.