In short

Customers send purchase orders as PDFs, scans and emails in every layout imaginable, and someone retypes them into the order system. The improved process reads each order, matches it to the customer and products you already hold, flags anything that doesn't match, and prepares the order record.

The sales administrator confirms each order before it is created. Nothing is entered into your system until a person has checked it.

  • Sector Small manufacturers
  • Role Sales administrator
  • Job Purchase orders into the order system

The job today

Purchase orders arrive in the sales inbox as PDF attachments, scanned paper or text in the body of an email. The sales administrator opens each one, finds the customer, looks up product codes, checks quantities and agreed prices against the customer file, and types the order into the system. Busy weeks mean a backlog, and typing errors mean wrong deliveries.

Where it breaks

  • Every customer's form is laid out differently.
  • Product codes on the customer's order don't always match yours.
  • Prices or delivery dates on the order sometimes differ from what was agreed, and it's easy to miss.
  • Retyping is slow and errors only show up when the wrong goods arrive.

The improved process, step by step

  1. Collect the orderPurchase orders arriving by email are picked up from one agreed mailbox or folder.
  2. Read the fields AI preparesAn assistant reads the customer, order number, lines, quantities, prices and dates from the document, whatever the layout.
  3. Match to your recordsEach line is matched to the customer account, your product codes and the agreed price list held on file.
  4. Flag the mismatchesUnknown codes, price differences, odd quantities or unreadable fields are highlighted next to the original document.
  5. The sales administrator confirms A person approvesThe sales administrator checks the prepared order against the original, resolves the flags and confirms it. Only then is it created.
  6. Create the recordThe order is created in your system with the original PDF attached, and the customer acknowledgement is drafted for approval.
PDF order forms into your system at a small manufacturer: process diagramSteps: 1. Collect the order; 2. Read the fields (AI prepares); 3. Match to your records; 4. Flag the mismatches; 5. The sales administrator confirms (a person approves); 6. Create the record 01 Collect the order 02 AI PREPARES Read the fields 03 RULES CHECK Match to your records 04 RULES CHECK Flag the mismatches 05 A PERSON APPROVES The sales administrator confirms 06 Create the record
The process at a glance. Teal steps are prepared with AI help; the amber step is where a person approves.

Where a person must approve

A person approves

The sales administrator confirms every order before it is created in the system.

Any price or delivery difference from what was agreed goes to the person who owns that customer, not just the sales administrator.

The data boundary

  • The assistant reads purchase orders from one agreed mailbox or folder, not the whole company email.
  • It can prepare an order record but cannot create it without a person confirming.
  • Original documents are kept with the record they produced.
  • Every extraction, change and confirmation is logged.

Checklist before you start

  • Orders arrive in one mailbox or folder we can point the system at.
  • Our product codes and customer price lists are up to date and accessible.
  • We know which customers use their own product codes, and have a mapping.
  • We know what counts as a mismatch worth stopping for.
  • One person confirms orders, with a named cover.
  • We know where originals must be kept and for how long.

This is an illustrative walkthrough of a common pattern. It is not a client case study, and the details will differ in your organisation.