Can your ERP create sales orders from emailed POs on its own?

“We pay for an ERP. Why is someone still typing these orders in?” Your customers email their POs to a shared mailbox. Someone on your team opens each one, switches over to the ERP and keys the sales order line by line. You already pay for the mailbox and the ERP. So it’s fair to ask whether the software you own has already solved this for you.

The honest answer is partly. Most ERPs offer some help, and for simple orders from known customers it may be enough. But none of it knows your customers the way your order desk does. That gap is where the hours still go.

A morning on a busy order desk

It’s 8:15 on a Monday. Your order desk opens the shared mailbox and finds 31 POs from the weekend. A few are tidy PDFs. One is a spreadsheet with 70 lines and a second tab of notes. One is a sales rep forwarding a customer’s order from their phone with “please enter, rush” on top. The rest are short emails from buyers who type what they want and sign off.

Ask the person working that pile what slows them down. It’s rarely the typing. It’s the small decisions between keystrokes.

• Their numbers, not yours. A restock PO lists 40 lines of the buyer’s own part numbers. Each one has to be traced to your item before it can go on the order.
• Units that don’t agree. The buyer orders by the box and you sell by the each, or the other way round. Somebody has to know how many come in a box of that item.
• A price from an old PO. The buyer copied last year’s order and last year’s price came with it. Nobody spots the gap until the invoice is short-paid.
• A different layout from every account. One customer’s PDF puts the ship-to at the top. Another buries it in the email signature. A third leaves it out and assumes you remember.
• POs forwarded by your own reps. The real customer is two emails down the thread, under somebody else’s name.
• The afternoon pile. POs that land after lunch get keyed tomorrow. By then the buyer has emailed again to ask whether you received it.

Each of these is a judgment call your team makes dozens of times a day. That’s why the work doesn’t shrink when you add people. It just spreads across more desks.

What the keying costs

Keying costs you three ways. Hours go into typing. Errors come back as returns, credits and reships. Slow confirmations turn into chasing calls. Only the hours show up on a timesheet, so they’re what you can count today.

The other two are real even when nobody tracks them. A wrong unit on one line means a reship and a credit memo. A missed price gap means a short payment your receivables team has to chase. Both get booked as warehouse or collections problems. The order desk never sees the bill.

Volume makes all of it worse. The Federal Reserve Bank of Dallas surveys Texas manufacturers every month. It asks Texas factories whether their orders rose, fell or stayed the same over the prior month and turns the answers into indexes. If you supply manufacturers across Dallas–Fort Worth, it’s a public, checkable way to watch demand move. A month when orders jump is a month when hand-keyed entry falls behind.

To size the hours, you need three numbers: how many people key emailed orders, how many hours a week each of them gives it and what an hour of their time costs you loaded. The example below uses two people at eight hours a week and $30 an hour. Put your own figures in.

People doing it

2

Hours each, per week

8

Loaded cost per hour

$30

Hours per month

69

Cost per year

$24,960

Hours back per month

35–49

An estimate from the numbers above, not a client result. It assumes 50%–70% of the work can be taken off your team; your audit checks that against your own numbers.

That example comes to 832 hours a year. That’s before a single reship or credit memo is counted.

Can your ERP do this on its own?

Your ERP is good at holding clean orders once they’re in. The hard part is the step before: reading what each customer meant and turning it into the right lines.

Many ERPs do offer some help with that step. Some let your team start a quote from inside the customer’s email, though the lines still get typed by hand. Some can send an attached PO to the right person. Newer ones go a step further and can draft a simple order from a plain email for someone to approve.

That help tends to stop at the same places. A PO laid out differently from the last one trips it up. So do the buyer’s own part numbers, a box on the PO when you sell by the each and a price copied from an old order. A PO your rep forwarded, with the real customer two emails down the thread, usually lands back with a person to sort out. For a desk where orders come in every layout, that leaves most of the judgment calls with your team.

What we take off your team

This starts from the shared mailbox your customers already send to and connects to the ERP you already use. Nothing changes on their side.

Every PO is read, whatever the format. The 70-line spreadsheet, the PDF from a purchasing system, the scanned page and the three lines typed into an email all get the same treatment. The rep’s forwarded order is traced back to the real customer. Each line is matched to the right item, even when the buyer uses their own part number. Units are converted to how you sell. The PO price is compared with what that customer pays.

Then the checks your team makes today run on every order. Is this ship-to on file for this account? Did a buyer who always takes 20 just ask for 200? Is that item discontinued? These get written down during setup, so they’re applied the same way at 8 a.m. on Monday and at 4:45 on Friday.

Clean orders go straight into the order system you already run. Or they wait there for a quick approval, if you’d rather someone signs off first. You decide per customer. Anything unclear goes to a person with the question marked: this part number has no match, this price is below what you charge them. Your team answers, and that answer is kept. Next week the same part number goes straight through.

Here is what that Monday morning looks like before and after.

What changes for your order desk

The difference shows up in ordinary days. A buyer who emails at 2 p.m. sees the order confirmed that afternoon, so nobody on your team has to stop and dig through the inbox to answer a chasing call.

Your order desk stops being a typing pool. The people who know your customers spend their time on the handful of orders that need them: the new part number, the odd ship-to, the quantity that looks like a slip of the finger. Each one arrives with the question already marked, so it takes minutes rather than a morning.

Wrong shipments get rarer, because the unit and price checks run on every line instead of when someone has time. Fewer reships means fewer credit memos, and fewer short payments for receivables to chase.

How each customer orders stops living in one person’s head. When your most experienced person takes a week off, the rules they carried are already written down and orders keep moving. A busy month stops landing on two people’s desks, and month end gets calmer because nothing is waiting to be keyed.

For more on the rest of a distribution business, see our automation guides for distributors. For how the work runs as a project, see order automation for distribution and manufacturing. For the wider view, see the guide to automated PO processing for distributors.

Where to start

First, find out how much of your order desk is judgment calls rather than typing.

1. Pull one normal week of POs. Take them from the shared mailbox and sort them by customer.
2. Mark the hard ones. Flag each PO that needed a part-number lookup, a unit conversion or a price question.
3. Count the awkward ones. Note the spreadsheets, the long orders and the POs your reps forwarded.
4. Time the keying. Track how long that week of entry took, and note the chasing calls.
5. Pick who goes first. Start with the customers who send you the most POs.

The free 20-minute audit call looks at how orders reach you and where the hours go. You get a written plan within 48 hours and a fixed-scope quote after the audit. Your first workflow goes live within 14 days of access to your tools.