For specialty manufacturers
The quantity typo that shipped 2,000 parts
Customer POs arrive as PDFs and somebody re-keys them into the ERP between two phone calls and an expedite. Part number, revision, quantity, price, due date, ship-to, terms. One afternoon somebody types 2,000 where the PO said 200. The job runs. You find out at shipping, or the customer finds out at receiving, and now you are eating material, setup, machine time and freight, and having a conversation about your quality system with someone who was happy with you last week. Reading a PO and typing it into the ERP is high volume, rule-bound and zero judgment — which is exactly the shape of work that should come off a person's desk, and exactly the shape a person is worst at. Nobody was careless. 2,000 and 200 look alike at the end of a long line on a scanned PDF.
What changed
Reading unstructured documents was a research problem for twenty years. A scanned print, a customer's spreadsheet format, a PO with the terms on page two — none of it parsed reliably, so every shop hired the parse. It works now. That is the only thing that changed, and it is enough.
Nothing else moved in your favour. 83.1% of manufacturers named raw material costs their top challenge in NAM's Q2 2026 Outlook Survey, up 25.6 points in one quarter, with 94.4% expecting further increases (215 respondents, fielded May 12–28, 2026). And volume is up: ISM's Manufacturing PMI hit 55.6% in July 2026, New Orders 56.7% (ISM Report on Business, July 2026). More POs, same office.
The mechanism, step by step
The agent watches the orders mailbox — including the customer who sends POs to one buyer's personal contact, because they all do.
It classifies the message. New PO, release against a blanket, change to an existing order, RFQ, schedule sharing notice, ordinary correspondence. A blanket release is not a new order and must not be entered as one.
It reads the document. PDF, scanned image, an order typed into the email body, a spreadsheet, an EDI file. It pulls customer PO number, line numbers, part number, revision, quantity per line, unit and extended price, requested date, ship-to, freight and payment terms, and the flow-down text on page two — first article requirements, C of C, source inspection, packaging specs, export control language.
It checks the extraction against what you already know. This is the step that catches the typo. Does the part exist at this revision? Does the unit price match the quote you sent or the blanket? Is the quantity inside the range this customer has ordered before, or an order of magnitude outside it? Is the requested date achievable against the lead time you quoted? Is the ship-to the one they use?
It drafts the order in the ERP. Not released. Drafted, every field populated, attachments filed against the order, with a note listing anything it could not read or match.
A person opens the draft, checks it against the PO on screen, and releases it. Ten seconds on a clean order. Their attention is on the exceptions, because the typing is already done.
The escalation rule, written before anyone builds
A price discrepancy, a changed lead time, or a new part number goes to a named person immediately, with the discrepancy stated. Not to a queue. Those three are not arbitrary — each is a commercial decision wearing the costume of a data entry task.
The PO says $18.40 and your quote said $19.10. That is not a typo to correct, it is a negotiation you did not know you were in. Sometimes they are on an old quote. Sometimes they are trying it on. The owner decides.
The PO asks for a date earlier than you promised. Accepting that quietly at order entry means the shop finds out when the job is already late. Pulling it in is a capacity question, and capacity lives on the floor.
A part you have never made is not an order. It is the front end of an engineering conversation — routing, tooling, gauging, first article, material sourcing. Entered as a normal order, all of that gets buried.
Add your own: a new customer with no credit terms, a revision letter you do not hold, ITAR language, a packaging change on a medical account. The list is yours. The rule is that it exists in writing and the agent follows it without discretion.
The write-back is the whole value, and your ERP decides it
An agent that reads POs and sends a tidy summary email is a demo. The value is that the order exists in the ERP with attachments filed, so scheduling, purchasing and shipping see it like every other order. Which means something has to be able to write.
Epicor Kinetic has documented, actively maintained integration tooling; NetSuite has a mature API. E2 Shop System from ECI received a third-party Grade D API assessment — no public endpoint reference, no OpenAPI spec, no sandbox, no documented auth flow (supergood.ai API Report Card) — and JobBOSS² shows the same pattern. Where a live write is not available, the fallback is a supported import file the agent produces and a person loads. Worse. Still beats typing.
What to do Monday
- Count last month's POs and how many were re-keyed by hand.
- Ask whoever does the entry which three customers' POs are the worst to read, and why.
- Write the escalation list. Start with price, date, new part number. Add three of your own.
- Search your ERP's name plus "API documentation." If the only way to find out whether an API exists
is to open a support ticket, that is your answer.
- Name the person who will review drafts. If nobody internal will own it, do not buy the agent.
Close
What it will never do: price a job, commit or revise a lead time, accept a change order, release an order to the floor, touch a traveler, a machine or any quality disposition, or email a customer on its own. A credit hold is a decision about a person, so it flags and somebody else decides. You approve that list before we build.
The Quote Clock is free, thirty minutes. Agent Blueprint $4,900. No build without a Blueprint, no fixed fee against an ERP API we have not tested.
Signet — AI that holds up. A division of Circle Square Consulting, Radnor, PA.