In this article11 sections
- The five common sales order processing errors
- Quick checklist to stop mistakes before you hit Confirm
- Practical tactics you can apply today
- When to move beyond manual checks: EDI, standards and automation
- Combining automated capture with human control
- Example workflow and roles
- How to measure whether your controls are working
- Practical pitfalls and how to avoid them
- Checklist for choosing capture or EDI
- Final practical plan for the next 30 days
- Closing note and next step
TL;DR: If your team types orders from emails and PDFs into the ERP by hand, expect wrong SKUs, UoM mismatches, price errors, wrong delivery addresses and duplicates. This guide lists the usual mistakes, what they cost downstream, and practical checks to stop them before you confirm an order.
You type orders from emails and PDFs into the ERP by hand. You have a small team. They are busy and under pressure. Mistakes happen.
Why this matters now. Manual entry still dominates many back offices. Intelligent document processing exists, but adoption is uneven: one study shows many businesses are only just starting with AI and automation, with about one in six firms reporting they are implementing at least one AI application in the survey mentioned. See the Office for National Statistics for context [ons.gov.uk](https://www.ons.gov.uk/businessindustryandtrade/itandinternetindustry/articles/understandingaiuptakeandsentimentamongpeopleandbusinessesintheuk/june2023).
Human entry also remains common for invoices and orders. A research summary reproduced by IBM notes heavy manual work on invoices and approvals, with a high proportion of document data still keyed by people [ibm.com](https://www.ibm.com/think/topics/intelligent-document-processing). That matters because the more manual touches you have, the more opportunities for error. Brightpearl reports that automation can reduce manual touch-points on orders dramatically, citing an example figure of 80% fewer orders needing manual touches in a specific case [brightpearl.com](https://www.brightpearl.com/blog/order-management/order-processing-errors). If you cannot or will not automate every order today, you need controls that catch common mistakes before confirmation.
The five common sales order processing errors
These are the mistakes seen most often when orders are keyed manually. Each subsection describes the error, the downstream cost and how to catch it before confirming the order.
1) Wrong SKU or product code
What it looks like. The operator selects the wrong SKU from a dropdown or mistypes the product code. The PDF or email shows a product name, but the ERP uses codes. Small differences in names mislead staff.
Downstream cost. Picking the wrong item causes wrong-picks at the warehouse. That leads to returns, credit notes and re-shipping costs. Sales and warehouse teams spend time correcting paperwork. Customer satisfaction falls and handling time for the account rises.
How to catch it before confirmation.
-
Use an item search that matches common name fragments, not just exact codes. If the ordered name contains a customer-specific phrase, flag it for review.
-
Require a quick product confirmation field that shows the SKU, description and pack size side by side with the submitted name.
-
Present the operator with the last price and last-purchase date for that SKU. A big mismatch should trigger a pause.
-
If you get the order as structured data via EDI or integration, map incoming GTIN or EAN values to your GTINs. See GS1 on EDI and GTIN use for standardised item IDs [gs1.org](https://www.gs1.org/standards/edi).
Example. Say an order arrives as a PDF requesting "Green Widget XL". The operator selects SKU GW-XL but your system has wired sizes differently. A quick confirmation pane showing SKU, image and pack UoM would have exposed the mismatch immediately.
2) Wrong unit of measure or pack size
What it looks like. The order says "12 per pack" but the operator records the item as single units or as a different pack size. The ERP converts without warning.
Downstream cost. Shipments under- or over-sized. Stock records become inaccurate. Purchasing gets distorted demand signals. Invoicing for the wrong quantity creates disputes and time-consuming credit notes.
How to catch it before confirmation.
-
Display both the ordered UoM and the ERP UoM side by side. Include a simple conversion factor and pack image where possible.
-
Block orders that mix UoMs for the same SKU on one line and force a split-line entry with a confirmation.
-
Add a sanity check: if the converted quantity is unusually large relative to recent orders for that account, flag it for manual approval.
3) Wrong price, discount or terms
What it looks like. Your team keys a price from the email or presumes a list price and forgets a contract price or customer-specific discount.
Downstream cost. Under-billing means lost margin and invoice corrections. Over-billing costs customer trust and triggers disputes. Both outcomes create credit control and finance work.
How to catch it before confirmation.
-
Show the customer contract price and last invoiced price next to the entered price. Any variance prompts a mandatory reason note.
-
Apply simple business rules that auto-apply known contract prices. If a new price is used, require manager approval.
-
Keep a visible audit trail on the order screen listing the price source: list, contract, promo code or operator override.
4) Wrong delivery address or delivery instructions
What it looks like. The operator types a postcode or address line incorrectly. A corporate customer has multiple sites and the wrong site is chosen. Special delivery instructions are missed.
Downstream cost. Parcels go to the wrong depot. Couriers return goods. Re-delivery costs escalate. Customers complain and may refuse the goods. Stock and logistics teams waste time resolving the issue.
How to catch it before confirmation.
-
Use an address lookup tool that validates postcodes and shows the formatted address. A live lookup prevents common typos.
-
If the customer has multiple sites, show recent deliveries to each site and the default site for that customer.
-
Require confirmation for high-cost orders or orders with time-critical delivery windows. For these orders, include a mandatory confirmation checkbox for delivery instructions.
5) Duplicate orders or duplicate lines
What it looks like. The same order arrives by email and via a portal, or two salespeople enter the same PDF. The operator does not spot duplicate reference numbers. Lines are accidentally repeated when copying and pasting.
Downstream cost. You pick and ship twice. Inventory and demand forecasts are wrong. Finance issues double invoices, then has to process returns and refunds. Customer relations are harmed.
How to catch it before confirmation.
-
Match incoming orders against recent orders by customer name, order value and reference number. If a close match appears, prompt the operator to confirm whether this is a duplicate.
-
For repeated reference numbers, block confirmation until the duplicate check is resolved.
-
Implement a simple throttling rule: if two orders arrive for the same customer with an identical line set within an X-hour window, mark them as possible duplicates and force a short hold for review.
Quick checklist to stop mistakes before you hit Confirm
Use this checklist as a pre-confirm audit for any manually keyed order. The table below can be printed and pinned at the team desk, or implemented as a mandatory verification step in the ERP.
| Check | Why it matters | Action if fail |
|---|---|---|
| SKU matches product name and image | Prevent wrong picks | Correct SKU or escalate to product master data team |
| Unit of measure correct and conversion verified | Prevent quantity and billing errors | Split lines or correct UoM and re-calc totals |
| Price equals contracted price or has approved override | Protect margin | Apply contract price or attach approval note |
| Delivery address validated by postcode lookup | Prevent mis-delivery | Correct address or call customer to confirm |
| No recent possible duplicate order | Prevent double-ships | Hold and verify with sales or customer |
| Order total within expected range for this customer | Catch extreme errors | Flag for manager approval |
| Mandatory fields completed (customer PO, delivery window) | Prevent missing data at pick/pack | Request missing info before confirmation |
Practical tactics you can apply today
These tactics work with your current team and ERP. They focus on low-effort controls that catch most errors before they propagate.
-
Build a two-second confirmation panel on the order screen. Show SKU, image, UoM, price and address in one compact view. Make it required reading.
-
Maintain a simple exception queue. Orders that fail any of the checklist checks route to one person for quick review. Keep the queue under control by limiting exceptions per shift.
-
Use recent-order matching. The ERP should warn if a near-identical order was entered in the last 24 hours.
-
Make price overrides traceable. Require a short reason and a manager ID for any manual price change.
-
Show last-shipped quantities per SKU per customer on the order screen. Large deviations should be highlighted in red.
If your team processes many PDFs and emails, consider capture tools that extract line items and present them to the operator rather than replacing the operator entirely. Intelligent document processing can reduce keystrokes while keeping human oversight. IBM summarises these methods under intelligent document processing and notes that a large share of document data is still being entered manually, which is why hybrid approaches are common [ibm.com](https://www.ibm.com/think/topics/intelligent-document-processing).
When to move beyond manual checks: EDI, standards and automation
If you handle regular volumes from the same trading partners, standard electronic formats cut errors. Electronic data interchange sends structured order data straight into your systems, reducing manual re-keying and the mistakes that come with it. GS1 explains how EDI and GTINs let systems exchange structured documents reliably across the supply chain [gs1.org](https://www.gs1.org/standards/edi).
EDI and structured integrations are not free. Implementation takes time and governance. But for repeat business, EDI can remove entire classes of human error and reduce operational overhead.
Retail and distributor-focused ERP vendors also provide end-to-end automation and workflow rules. These systems often report significant reductions in manual tasks and exceptions. For example, Brightpearl describes how automation lets teams stop re-keying and reduces manual touch-points on orders in some implementations [brightpearl.com](https://www.brightpearl.com/blog/order-management/order-processing-errors).
If you are unsure which route to take, consider this rule of thumb: if more than one staff member rekeys the same incoming order type repeatedly, automate the capture for that channel first.
Combining automated capture with human control
Automated capture tools can extract text, line items and totals from emails and PDFs. But raw extraction is not a turn-key solution. The industry moves toward intelligent document processing to combine extraction with validation and exception handling. IBM covers this as part of the broader automation trend in document work [ibm.com](https://www.ibm.com/think/topics/intelligent-document-processing).
A practical hybrid setup looks like this:
-
Capture. The system extracts header fields and line items from the PDF or email.
-
Validate. The capture engine runs basic rules: SKU match, UoM conversion, price check and address validation.
-
Present. The extracted order and any exceptions appear in a short verification screen for the operator.
-
Confirm. The operator resolves exceptions or approves the order. The system logs the decision and source.
This approach cuts keystrokes and keeps human judgement where it belongs: on the exceptions.
Example workflow and roles
-
Operator. Reviews captured data, resolves simple mismatches and confirms. Uses the confirmation panel for fast checks.
-
Resolver. Handles exceptions that need product master data, contract review or customer contact.
-
Manager. Approves price overrides and high-value exceptions.
-
IT/business analyst. Maintains rules, updates SKU mappings and reports frequent failure types so the business can fix root causes.
This division of labour keeps processing fast and prevents a single person from becoming a bottleneck.
How to measure whether your controls are working
Measure the right numbers. Track these KPIs weekly and review trends in a short ops meeting.
-
Order exception rate. Percentage of orders that hit at least one check and require resolver action.
-
Order rework cost. Time spent per exception multiplied by average hourly cost to quantify the overhead. If you use external figures, ensure they come from a credible source.
-
Returns and credit notes per 1,000 orders. Falling returns mean fewer fulfilment errors.
-
Average time to confirm an order. Too slow and the team will bypass checks.
If you choose to pilot capture software, compare these KPIs before and after the pilot. Brightpearl cites large reductions in manual touch-points where automation is configured correctly [brightpearl.com](https://www.brightpearl.com/blog/order-management/order-processing-errors).
Practical pitfalls and how to avoid them
-
Pitfall: Overcomplicated rules that slow the team. Keep rules simple. Start with the checks that catch the biggest rework costs.
-
Pitfall: No owner for exceptions. Assign one person per shift to own the queue. Set a maximum queue time.
-
Pitfall: Relying solely on tools without reviewing captured failures. Track the failure reasons and fix the upstream issue, for example poor PDF formatting from a trading partner.
Checklist for choosing capture or EDI
-
Is the order flow repeatable and high volume from the same partners? If yes, favour EDI or structured integration.
-
Are most orders coming as unstructured PDFs and emails but from many different customers? If yes, start with intelligent capture and validation.
-
Do you have clear master data for SKUs and customers? If no, fix master data before automating capture; automation amplifies master data errors.
For background on EDI and standardisation consider the GS1 overview on EDI [gs1.org](https://www.gs1.org/standards/edi).
Final practical plan for the next 30 days
Week 1: Map the error types. Pull last 3 months of returns, credit notes and customer queries and tag the cause. Focus on SKU, UoM, price, address and duplicates.
Week 2: Implement the confirmation panel and the checklist above in the ERP for new orders. Make it mandatory and quick to use.
Week 3: Create an exception queue and assign owners. Decide escalation rules for price overrides and high-value orders.
Week 4: Run a report to compare exception rate, time to confirm and returns. Decide whether to pilot automated capture or EDI for the highest-volume channels.
Closing note and next step
Manual order entry will always carry some risk. But practical controls and small automation steps reduce the most damaging mistakes. If you want a short technical walkthrough on automating capture from emails and PDFs, see the step-by-step post on our blog: /blog/automate-order-entry-from-email-and-pdf.
If you are weighing hiring another order processor versus automating, this post may help: /blog/hiring-an-order-processor-or-automating.
If you want help designing the confirmation panel and exception rules, or to discuss which channels suit EDI, see our services page: /services.
For a no-pressure call about options, tools and a realistic roadmap from manual checks to partial automation, contact Khairos. Book a free intro call: /contact
Sources
Still typing orders into the ERP by hand?
In a 30-minute call we look at how orders reach your team and show which steps could run without retyping.