Customer POs into your ERP, checked against the quote.

A buyer emails a PO, sometimes with the drawing attached. Someone on your desk finds your part, checks revision and price against the quote, judges the date and enters the order. A release gets matched to its blanket first.

The proof of concept hands that same stack of POs to AI, which writes up a draft order showing every check it made. Whatever it can't resolve is held, with the reason. Your ERP never sees it.

Revisions. A PO line usually carries the customer's part number, a revision letter and often a drawing number: "4471-220 Rev D per drawing 4471-220". The first step is finding your part at the revision ordered, the second is checking that against the revision you quoted. Rev D on the PO and Rev C on the quote stops the order. Some ERPs default an order line to the latest approved revision unless someone overrides it, so an older-revision PO can reach the floor wrong without anyone mistyping a thing.

Blankets and releases. Repeat customers often send one blanket PO for a year's quantity at a set price, then release against it: release 7, 400 pieces, on the dock the 14th. Releases come as emails, schedule spreadsheets or supplier-portal postings. In Epicor a release sits under an order line with its own quantity, ship-by date and ship-to; in SAP the same thing is often a scheduling agreement with delivery schedule lines. Each release belongs on its blanket line, and a released total that runs past the blanket has to be caught.

Requested dates and partials. Buyers write "need by" or "required on dock", sometimes a different date per line, sometimes split deliveries on one line. Your desk weighs that against lead time, material and shop load before the acknowledgment goes out with a promise date. The proof of concept schedules nothing. It flags requested dates inside the lead times you give us, and "ship complete" orders whose lines are spread across dates.

Configured lines and quality notes. A made-to-order line may have no part number at all: "36 in. guard, 304 stainless, #4 finish, per quote Q-2218", so the configured part or the options the quote listed have to be found. Quality requirements ride along: a certificate of conformance with each shipment, material test reports with the first, a first article inspection, a PPAP level for automotive work, often printed as clause codes that point to the customer's quality document. Unit price is checked against the quote's quantity break, with tooling or NRE billed once on its own line.

Who checks the drafts. Pick whoever settles the tricky POs today, often the customer service lead. That person, the one who knows order entry best, is your reviewer. Revision, price, which blanket each release landed on and the flagged dates get the closest look, along with each hold reason set beside what your desk did with that PO at the time.

Say yes, and new POs go through the same checks for roughly 30 days as they come in.

Each draft order waits for someone on your desk to approve, edit or return it before it posts to your ERP. The comparison table stays in use, so the live month is scored the way the test was. No second job starts in that time.