Your customers send purchase orders the way they always have: a PDF attached to an email, a photo from a job site, sometimes a fax. Someone on your inside sales team opens each one and types every line into your ERP. This guide walks through the real ways to stop that, in the order worth trying them.
How much does typing in orders actually cost?
Email is still one of the main ways customers order. In a Distribution Strategy Group survey of more than 3,500 distributor customers, published in 2016, about 74% of end users said they order by email frequently or very frequently. The same publisher estimated that keying those orders can take 20% to 40% of the time of several customer service reps.
Hand-keyed orders also cost more to process. A 2018 APQC report found a median cost per sales order of $10.00 through traditional channels at companies that track first-time data accuracy, and $16.50 at companies that don’t. Orders through digital channels ran $3.10 and $5.10.
Esker, which sells order automation, sponsored the report, but the benchmarks are APQC’s.
Then there are the errors: a wrong item, a dropped digit, a missed ship-to. Each one turns into a credit, a return or an unhappy phone call.
What should you fix before buying anything?
Start with the process. No tool fixes a messy one.
- Count your orders by channel. Pull four weeks of orders. How many came by email, EDI, your web store, phone and fax? Which customers send the most lines?
- Send every order to one inbox. Orders sitting in five reps’ personal inboxes can’t be tracked, let alone automated.
- Ask your biggest customers for something cleaner. A spreadsheet in your layout, your web store or EDI all beat a PDF.
- Write down customer part numbers. Most of the work in order entry is matching their item number to yours. If those cross-references live in one rep’s head, get them into P21 first. They’re yours, whichever tool you pick.
What can Prophet 21 already do?
Prophet 21 has three standard ways to take in orders without anyone typing them, according to Airdev, which builds custom order entry for P21:
- EDI. Inbound 850 purchase orders become sales orders, and P21 can send back acknowledgements (855), ship notices (856) and invoices (810). Rules are set per trading partner, and most P21 shops run EDI through a provider. It’s worth it for large customers who already do EDI. It’s overkill for a customer who sends five POs a month.
- Import files. P21’s Scheduled Import Service Manager (SISM) picks up order files on a schedule; it’s set up under Setup, Imports/Exports. Airdev notes the files must match P21’s import layout, and orders that fail validation are held for someone to fix.
- The API. P21’s Transaction API can post sales orders without anyone using the screens. Airdev notes that API access is licensed separately, so ask your Epicor rep what your license includes.
The catch, per Airdev: P21 has no built-in way to read a PDF or the body of an email. Something has to turn that PDF into an EDI document, an import file or an API call. That’s the job of the AI tools below.
On Eclipse, Infor SX.e, Acumatica or Sage? Ask your reseller the same question: which of these doors does my license open?
Which off-the-shelf apps do this?
- Conexiom. On July 14, 2026, Conexiom and Epicor expanded their partnership to automate sales orders, AP invoices, quote requests and vendor acknowledgements for Prophet 21 and Eclipse users. Conexiom says it has over 600 customers and more than 95% accuracy; those are its own numbers. If you’re on P21 with steady volume, it’s the natural first call.
- Esker. Esker’s order management software takes orders from email, EDI and portals, checks them against your ERP’s products, pricing and quantities, and routes discrepancies to a person. The only ERP connector named on that page is SAP, so ask how it would reach P21.
- Parseur. A lighter, pay-as-you-grow tool. You forward PO emails, it pulls each line into its own row, and it pushes the data to Excel, Google Sheets, a webhook or Zapier. You still have to match items to your numbers and get the rows into P21, usually through an import file.
When does a custom build make sense?
When the apps don’t fit how your customers actually order. Common reasons: lots of free-text emails (“same as last time, plus 20 more of the 3/4-inch ball valves”), photos from job sites, heavy use of customer part numbers, contract pricing that has to be checked on every line, or per-order fees that don’t pencil out at your volume.
A custom build is also the only option where the matching rules are yours to change. The trade-off is that someone has to maintain it.
How do you set it up, step by step?
- Gather samples. Four weeks of real orders, grouped by customer and format.
- Pick the door into your ERP. EDI for big EDI-ready customers, an import file or the API for everyone else.
- Write the exception rules. Unknown item, a price that doesn’t match the contract, a ship-to not on file, a quantity far outside the customer’s normal, a requested date you can’t meet, a PO number you’ve already entered (a revision or a resend), a line described only by spec (size, schedule, grade, pressure class). Anything that trips a rule goes to a person.
- Run side by side for a week or two. The AI drafts each order while your team keys as usual. Compare line by line.
- Go live with approval. A person reviews every draft before it posts. Track minutes per order and how many get flagged.
- Add customers one at a time. Start with the senders whose POs are cleanest and most frequent.
What could this look like for a real distributor?
This is an illustration, not a client story. The numbers are made up to show the math.
Say you run a 30-person industrial distributor in Houston on Prophet 21. Three inside sales reps key about 120 emailed orders a day, averaging six lines each. If each order takes five minutes to read, look up and enter, that’s 10 hours of typing a day, more than one full-time person.
Now say an AI tool drafts each order and your reps check instead of type. If a clean order takes a minute to check, and one in five gets flagged and takes the full five minutes, the daily total drops to about three and a half hours.
Your real numbers depend on how clean your customers’ POs are. That’s exactly what the side-by-side test tells you.
When should you just buy an app?
Buy if you’re on P21 or Eclipse, most orders come from repeat customers on standard POs, and your volume justifies a subscription or per-order fee. The Conexiom and Epicor partnership is built for exactly that.
If your volume is low and the PDFs are clean, a tool like Parseur plus a P21 import file may be all you need. Build only after you’ve seen the apps run on your own orders and they fall short.
Whoever you talk to, ask where your PDFs are stored, whether they’re used to train AI models, and what it costs at your monthly order count.
Want a second opinion?
BlueHill is based in Spring, in north Houston, and works with clients over video and in person around Houston. The Order & Invoice Entry package reads emailed and scanned orders, matches each line to your item numbers and pricing, and puts every order in front of a person to approve. It’s a one-time setup, and the price is fixed in writing after a free call and a 90-minute walk-through of how your work gets done ($500, credited toward the build). You can own it and run it yourself, or BlueHill can run it for you for a monthly fee that covers checking on it and fixes when a customer changes its PO form.
Setup typically takes two to three weeks, including side-by-side testing on your real orders. How approved orders get into P21 depends on your license and setup; that’s the first thing checked on the call, and you’ll get a straight answer. See how it fits wholesale distribution, or book a free 30-minute call.