peekgenticBook a call

Guide · Order entry

Order entry automation: how to automate order entry from email and PDF POs

How order entry automation works: read emailed and PDF POs, map customer part numbers to your items, check prices, and post approved orders to your ERP.

By Miguel GutierrezCo-founder, Peekgentic · Dallas
· 9 min read
Preview card reading Order entry automation: from email to ERP
Peekgentic

In brief

Order entry automation means software reads each customer purchase order, whether it arrives by email, PDF, EDI or a portal, and fills in the sales order for you. It finds the customer and ship-to, matches the customer's part numbers to your item numbers, checks quantities, units and prices against your ERP, and flags anything that doesn't fit. A person looks at the draft next to the PO and approves it. Then it posts to your ERP through its API or import tool. The hard part is not reading the PDF. It's the mapping: knowing that a customer's part number, unit and price mean a certain line in your system.

  • Order entry automation reads POs from email, PDF, EDI or portals and drafts the sales order in your ERP.
  • APQC, 2016 (Esker-sponsored): total cost to manage a sales order ran $5.11 for top performers to $40.87 for bottom performers.
  • Order entry mapping, meaning field mapping, customer part number cross-references and unit conversions, decides whether it works.
  • Route exceptions to one queue: unknown parts, price mismatches, revised POs, new ship-tos.
  • Keep a person approving, post through the ERP's API or import tool, and measure minutes per order from a baseline.

What order entry automation is

Most manufacturers and distributors still have someone at an order desk with two screens. One shows a customer's PO, usually a PDF attached to an email. The other shows the sales order screen in the ERP. That person reads one and types into the other: customer, ship-to, PO number, part numbers, quantities, prices and dates.

Order entry automation takes the typing out of that job. Software does the reading and the filling in. A person still decides. Epicor, which sells this kind of tool, calls manual order entry labor-intensive and time-consuming and lists the forms orders still arrive in: mail, fax, email, paper, PDF and spreadsheets.

This guide covers how automated order entry works, what "order entry mapping" means, how to handle exceptions, and how to pick an approach for the ERP you run.

Order entry from an emailed PO, start to approval. Sample data, no real customer. All demo videos
A sample customer's PO arrives in the order inbox (sample data)The PO is read: customer, lines, quantities and dates pulled out (sample data)The customer's part numbers matched to the sample item list (sample data)The sales order entered in the sample ERP (sample data)A person approves before the confirmation goes out (sample data)

What manual order entry costs

The best public benchmark is older, and it was paid for by a vendor. In 2016, the research group APQC published Cutting the Costs of Sales Order Processing, sponsored by Esker, which sells order automation. It used benchmarking data from 608 organizations.

Total cost to manage sales orders, per order

APQC benchmarking data, 608 organizations, 2016. Covers the whole "manage sales orders" process, not typing alone.

  1. Top performers$5.11
  2. Median$24.21
  3. Bottom performers$40.87

Source: APQC, Cutting the Costs of Sales Order Processing, 2016 (sponsored by Esker).

The same report split costs by how orders came in. At the median, orders through paper-heavy channels cost $12.60 each, and orders through digital channels cost $4.00. These are 2016 dollars, so use them as a rough range.

Errors cost as much as time. A review of 93 studies on clinical trial data found a pooled error rate of 6.57% when people read records and copied the data out, and 0.29% when they typed from a form built for data entry. That's medical data, not POs. But the lesson carries over. A customer PO was designed for the customer's system, not yours, so copying it is the error-prone kind of typing.

How automated order entry works, step by step

  1. Capture. The software watches the shared order inbox, a fax-to-email line, an EDI feed or a customer portal. It picks up each order with its attachments, and sets aside emails that aren't orders.
  2. Read. Document AI pulls out the header (customer, PO number, order date, ship-to, bill-to, ship method, requested date) and every line (part number, description, quantity, unit, price). It works on PDFs, scans, spreadsheets and orders typed in the email body.
  3. Map. Each value is matched to a record in your ERP. "ACME Corp, Plant 2" becomes customer 10442, ship-to 003. The customer's part number becomes your item number. This is the step that decides whether the whole thing works. More on it below.
  4. Check. The draft is tested against your rules. Is the price the contract price? Is the quantity a full case? Is the date possible given lead time? Is this a duplicate of yesterday's PO? Is the account on credit hold?
  5. Approve. A person sees the PO and the draft order side by side, with anything uncertain highlighted. They fix it or click approve.
  6. Post. The approved order goes into the ERP through its API or its import tool, not by a bot typing into screens. The customer gets a confirmation.
  7. Learn. When a person fixes a mapping, like a new customer part number, it's saved so the next order maps on its own.

What "order entry mapping" means

Order entry mapping is the set of rules that turns what the customer wrote into what your ERP needs. It has three layers.

  • Field mapping. Which part of the PO goes in which ERP field. The customer's "PO #" goes in your customer PO field. Their "Deliver by" goes in your requested ship date.
  • Value mapping (cross-references). Turning the customer's codes into yours: their part number to your item, their unit to your unit, their ship-to name to your ship-to code.
  • Rules. What to do when something doesn't match, such as a price that's off by more than a set amount.

Example: one PO line mapped to an ERP sales order

On the customer POERP fieldMapped valueHow it got there
Buyer: ACME Corp, Plant 2Customer / Ship-to10442 / 003Ship-to address matched to the customer's saved ship-tos
PO # 4500-88213Customer PO number4500-88213Copied as is; checked for duplicates
Item: AC-77810 "Bracket, SS, 4in"Item numberBRK-SS-0400Customer cross-reference: AC-77810 = BRK-SS-0400
Qty 10, UOM: CSQuantity / Unit240 EAUnit conversion: 1 case = 24 each
Unit price $48.00 / CSUnit price$2.00 / EAConverted to your unit, then checked against the contract price
Deliver by 11/14Requested ship date11/12Delivery date minus 2 days transit for this ship-to

Illustration. Codes and prices are made up.

Most ERPs already have a place for customer cross-references. Sage 100's Alias Item Maintenance has a Customer alias type tied to a customer number. Acumatica's help says item cross-references link your inventory ID to the ID a customer or vendor uses. If yours is out of date, that's the first thing to fix. Automation is only as good as the cross-references it maps to.

Templates per customer vs. layout-agnostic AI

Older tools need a template for each customer layout. Someone draws boxes around where the PO number and lines sit. That works until the customer changes their PO form, and then that customer's orders fail. Newer tools read a PO without a fixed layout. Epicor's ECM automation page says its capture reads key fields without templates, and Rossum says the same of its order tool. Either way, the mapping layer stays. A tool can read "AC-77810" perfectly and still not know which of your items it is.

Reading the PO is the easy part. Knowing what the customer meant, in your item numbers, is the job.

Handling exceptions

No setup reads every order perfectly. The goal is to catch the odd ones, not to pretend they don't exist. Common exceptions:

  • Unknown part number. New to you, or a typo. Hold the line, suggest likely matches, and save the answer once a person picks one.
  • Price mismatch. The PO price doesn't match your price list or quote. Flag it. Don't silently use either price.
  • Revised POs and change orders. The same PO number arrives again with changes. Show what changed instead of creating a second order.
  • New ship-to. A person should confirm a new address before goods ship there.
  • Notes in the email body. "Ship partial, rush line 3." Make sure these reach the order, not just the PDF.

Put every exception in one queue with the reason shown. If the person reviewing has to dig to learn why an order stopped, the time savings disappear.

EDI vs. email vs. portal orders

Three ways orders arrive

EDIEmail and PDFPortal
What it isStructured data, often an X12 850 purchase orderWhatever the customer's system printsYour website where customers place orders
Who uses itLarge customers who require itMost mid-size and small customersRepeat buyers willing to log in
Typing neededNone once set upAll of it, unless automatedNone; the customer types
Main limitSetup per trading partnerEvery layout is differentMany customers won't change how they buy

Most order desks get all three. EDI covers a few large accounts. A portal covers some repeat buyers. See our order processing portal guide for that path. The email pile is usually what's left, and it's where automating order entry from email pays off. All three should end in the same review step and the same checks.

Notes by ERP: where people still retype

  • Sage 100. Visual Integrator (VI) can import into data entry files. A Sage community post walks through building VI imports into data entry, so orders land where a person can still review them. Answers on Sage's community forum point developers to the Business Object Interface rather than a REST API.
  • Epicor Kinetic and Prophet 21. Kinetic's REST API page says what's in the user interface is available through REST. For P21, Epicor's partner directory names Conexiom for order automation. Full details are in our Epicor order entry guide.
  • Acumatica. Cloud based, with an API, and cross-references built in. The retyping usually comes from POs whose part numbers were never added to those cross-references.
  • NetSuite. Oracle's help covers sales order imports by CSV, in one file or split into header and line files, with the customer referenced by internal or external ID. Imports work for batches. Daily emailed POs still need someone, or something, to read them first.
  • QuickBooks. Intuit says sales orders are available in QuickBooks Desktop Premier and Enterprise. Check what your edition supports before you plan, since that decides what the automation can create.

Your options compared

Ways to automate order entry

OptionExamplesBest forMain limit
Order automation productsEsker, ConexiomHigher volume desks that want a packaged productSet up per customer; fit with your rules varies
Document AI (IDP) toolsRossum, NanonetsTeams with IT help to connect the outputReads the PO; mapping and ERP posting are on you
ERP add-onsEpicor Sales Order AutomationShops that want to stay in one vendor's toolsTied to certain ERPs; test on your messiest POs
Zapier or similarEmail parser plus a zapA few simple, steady layoutsBreaks when a layout changes; see why zaps break
Custom buildBuilt for your desk on your ERP's APIMany layouts, revised POs, business-specific checksA real project; needs an owner and scope

Vendor accuracy numbers are the vendors' own claims. Test any option on 50 of your real POs, including the worst ones. For a side-by-side of email tools, see the best email order entry automation tools. If someone pitches screen-typing bots, read AI vs. RPA for order entry first.

How to measure it

Measure a baseline for two weeks before you start. Then track:

  • Minutes per order. From arrival to entered, including fixing mistakes.
  • Orders per person per day. How much one person can handle.
  • Error rate. Wrong item, price, quantity or ship-to found after entry, as credits, returns or angry calls.
  • Order-to-confirmation time. Hours from the PO arriving to the customer getting your confirmation.
  • Touchless share. Orders approved with no edits. This should rise as the mapping fills in.

Common mistakes

  • Skipping the mapping. Buying a reader and assuming it knows your items.
  • Dirty cross-references. Old aliases that point to discontinued items will map orders to the wrong part, quickly.
  • Posting without a person. Keep someone approving each order until the error rate proves out.
  • Typing into screens. Bots that copy keystrokes break after ERP upgrades. Use the API or import tool.
  • Ignoring revisions. Change orders are where manual desks lose the most time.
  • Starting with every customer. Start with your top customers by volume and grow.

How Peekgentic does it

Peekgentic is a Dallas firm that builds custom order entry automation for manufacturers and distributors. The software reads each emailed or PDF PO in whatever layout the customer sends, maps the customer's part numbers, units and prices to your ERP, and fills in the order. A person on your team approves every order before it posts, in the system you already run. Nothing has to be replaced.

For a Garland manufacturer, one desk process went from 4 hours to 15 minutes, and they've saved over $100K in under 8 months.

See how order processing works. In North Texas, see order entry automation in Dallas-Fort Worth.

Read next: How to stop retyping customer POs into your ERP · Esker alternatives for order processing · Ordermatic vs. a custom build

Common questions

What is order entry automation?

It's software that reads customer purchase orders from email, PDF, EDI or a portal, fills in the sales order in your ERP, checks it against your data, and puts it in front of a person to approve before it posts.

How do I stop retyping customer POs into my ERP?

Have software read each emailed PO and attachment, map the customer's part numbers, units and prices to your ERP records, and post a draft order through your ERP's API or import tool for a person to approve. You keep your ERP; the retyping goes away.

How do I automate order entry from email?

Connect the shared order inbox, have software read each PO and attachment, map customer part numbers, units and prices to your ERP records, flag anything that doesn't match, and have a person approve each draft before it posts through your ERP's API or import tool.

What is order entry mapping?

It's the rules that turn what a customer wrote into what your ERP needs: which PO field goes in which ERP field, cross-references from the customer's part numbers to your items, unit conversions, and what to do when something doesn't match.

Do I need a template for every customer's PO layout?

Not with newer tools. Many read POs without fixed templates. You still need the mapping: the tool can read a part number correctly and still not know which of your items it is.

Is EDI better than email order automation?

EDI is cleaner when a customer can send it, but setup is per trading partner and most smaller customers won't use it. Most desks use EDI for a few large accounts and automate emailed POs for everyone else.

Can automated order entry run with no person involved?

The typing can be automated. Keep a person approving each order until your error rate proves out, and always route exceptions like unknown parts, price mismatches and new ship-tos to a person.

Which ERPs does order entry automation work with?

Most of them, including Sage 100, Epicor Kinetic and Prophet 21, Acumatica, NetSuite and QuickBooks Desktop. How the order gets in depends on the ERP: an API, an import tool, or both.

Who automates order entry for manufacturers in Dallas?

Peekgentic is a Dallas firm that builds custom order entry automation for Dallas-Fort Worth manufacturers and distributors. The software reads emailed POs and fills in the order, and a person approves it in the ERP you already run.

Sources

  1. APQC, Cutting the Costs of Sales Order Processing, 2016 (sponsored by Esker)
  2. Garza et al., Error Rates of Data Processing Methods in Clinical Research: A Systematic Review and Meta-Analysis, 2023 preprint, PMC
  3. Epicor, Sales Order Automation for Kinetic (product page), checked Oct. 18, 2026
  4. Epicor, ECM Automation Solutions (product page), checked Oct. 18, 2026
  5. Epicor, Open REST API (product page), checked Oct. 18, 2026
  6. Epicor Partner Directory, Conexiom, checked Oct. 18, 2026
  7. Sage 100 Help, Alias Item Maintenance: Fields
  8. Sage Community Hub, Tips for creating Visual Integrator imports into data entry files
  9. Sage Community Hub, REST API web service thread
  10. MYOB Acumatica Help, Managing Item Cross-References, checked Oct. 18, 2026
  11. Oracle NetSuite Help, Sales Order Import, checked Oct. 18, 2026
  12. Intuit QuickBooks Help, Create a sales order in QuickBooks Desktop
  13. Esker, Order Management (product page), checked Oct. 18, 2026
  14. Rossum, Order Management (product page), checked Oct. 18, 2026
  15. Nanonets, Purchase Order Management (product page), checked Oct. 18, 2026

More from Peekgentic

Published October 18, 2026 · Written by Miguel Gutierrez, Co-Founder, Peekgentic (Dallas, TX). Every statistic links its source.