Skip to content

Sales order entry

This playbook covers sales order entry: turning the purchase orders your customers email into sales orders in your ERP. It describes the work today, what our forward-deployed engineers build and who does what at each level of the autonomy ladder.

Customers email purchase orders to a shared customer service inbox. Some are clean PDFs produced by the customer’s own system. Some are scans, some are spreadsheets and some are three lines typed into the body of an email. At a distributor, orders also arrive by EDI and by phone.

Someone on the order desk opens each one, finds the customer account and keys the order into the ERP: the purchase order number, the ship-to address and, for every line, the part number, quantity, unit of measure, price and requested date. Then an order acknowledgment goes back to the customer.

The keying is the visible part. The time goes into what the purchase order does not say.

  • The customer uses their own part numbers. The translation lives in a spreadsheet, or in the head of whoever has handled the account for years.
  • The price on the purchase order does not match the price list or the quote, and someone has to find out which is right.
  • The customer orders in eaches and you sell by the box.
  • The requested date is inside your lead time, so someone has to ask the scheduler.
  • The same purchase order arrives twice, or arrives again as a revision that looks like a duplicate.

The work touches the order desk, inside sales for price questions, the credit manager for accounts on hold and the scheduler or the warehouse for dates. The workflow owner is typically the customer service manager.

  • Screens: an order screen that shows the customer’s purchase order beside the order being entered and records every field and every correction. A view of each stopped order that says why it stopped.
  • Queues: an order queue fed from the customer service inbox, where each purchase order arrives with its original email and attachment. An exception queue for orders that need a person.
  • Rules: the checks your order desk makes from memory, written down. Price against the price list and open quotes. Credit limit and account holds. Unit of measure and pack quantity. Requested date against lead time. Duplicate purchase order numbers. Ship-to against the addresses on the account. With them goes a cross-reference from each customer’s part numbers to yours, built from order history and kept up by the order desk.
  • Integrations: reads of customers, items, prices, credit status and open orders from the ERP. One write-back: create a sales order, through an interface the ERP supports, with the ERP’s own validation still applied.

EDI orders already arrive as data. They join the same queue and pass through the same rules. Phone orders are keyed on the same screen by the person who takes the call.

Level What the agent does What people do
Level 0 (Recorded) Nothing yet. The order desk keys orders into a screen that records every field and every correction.
Level 1 (Assisted) Reads the emailed purchase order and drafts the order: customer, lines, quantities, prices and dates. Flags what does not match. The order desk checks the draft and keys the order.
Level 2 (Prepared) Builds the complete order, with part numbers translated and every check run. A person reviews each order and approves it. Nothing reaches the ERP without that approval.
Level 3 (Supervised) Enters orders that match the price list and the credit limit, for customers on its list and under its amount limit. The order desk handles the mismatches and spot-checks a sample of what the agent entered.
Level 4 (Autonomous) Owns order entry, including routine follow-up the rules cover, such as asking a customer for a missing ship-to address. The order desk sets the rules and reviews a sample.

Sales order entry can go all the way to Level 4. An order is checked again after entry, by the ERP’s own validation and by the acknowledgment the customer reads. An order caught before it is released to the floor or the warehouse can be corrected or cancelled.

The sensible place to start Level 3 is repeat orders of standard parts from customers who send clean purchase orders. The customer list grows from there.

Level 4 does not mean every order. The rules still send some to a person: a first order from a new customer, a part with a new drawing revision, anything above the amount limit.

When the agent sends email, such as a request for a missing ship-to address, it sends from an address your IT team sets up for this workflow, under a name and signature the workflow owner decides.

Exception Who it usually goes to
A part number that is not recognized, or that matches two of your items Order desk
A price on the purchase order that differs from the price list or the quote Inside sales for the account
An order that takes the customer over the credit limit, or an account on hold Credit manager
A requested date inside lead time Scheduler at a manufacturer, purchasing at a distributor
A ship-to address that is not on the account Order desk
The same purchase order number as an open order: a duplicate or a revision Order desk
A scan that cannot be read, or handwritten changes on a typed order Order desk
Special terms in the notes: ship complete, a named carrier, certificates required Order desk
A drawing revision on the purchase order that differs from the current one Engineering or quality
  • Purchase orders received per day, by customer and by how they arrive.
  • Time from the email arriving to the order being in the ERP.
  • How often the agent’s draft or prepared order matched the final order, field by field.
  • Corrections at approval, by field and by customer.
  • Exceptions by reason, who resolves them and how long each one waits.
  • Errors found after entry: changed orders, credits and returns traced back to an entry mistake.
  • What the sample reviews find at Levels 3 and 4.

These are things to measure, not targets. The threshold for each level is set with the workflow owner and written down before that level starts.