Sales order: what it holds and how a PO becomes one
A sales order is the seller’s record of what a customer ordered: the items, quantities, prices, delivery address and dates. It usually starts from the customer’s purchase order, and it drives the pick, the shipment and the invoice. This guide covers what a sales order holds and how it differs from a purchase order and a quote. It then follows an emailed PO into your ERP and lists what goes wrong in order entry.
What a sales order holds
The Association for Supply Chain Management (ASCM) keeps the standard dictionary of supply chain terms. The ASCM Supply Chain Dictionary defines a customer order as an order from a customer for a particular product, number of products or service. It calls this actual demand, to set it apart from a forecast.
The sales order is the seller’s record of that customer order. Each new order gets a unique sales order number during order entry. ASCM notes that promising, scheduling, cost accounting and invoicing all use that number.
In an ERP, a sales order has a header for the whole order and one line per item. The field names in the table come from Microsoft Dynamics 365 Business Central, as one example.
| Field | Where it sits | What it does |
|---|---|---|
| Customer | Header | Brings in the customer’s prices and payment terms, and the credit limit the order is checked against |
| Ship-to address | Header | Says where the goods go, which can differ from the billing address |
| External document number | Header | Holds the customer’s PO number, so the shipment and the invoice trace back to their document |
| Requested delivery date | Header or line | Sets the starting point for the date you promise |
| Payment and shipping terms | Header | Decide when the invoice is due and who pays the freight |
| Item number | Line | Your number for the item, which an item reference ties to the customer’s part number |
| Quantity and unit of measure | Line | How many, and in which unit: each, box or pallet |
| Unit price and line discount | Line | Come from the customer’s price agreement or the accepted quote |
| Quantity to ship | Line | Lets you ship part of a line now and the rest later |
The customer’s PO number deserves its own field. Business Central records it in the External Document No. field, and a setting can make that field mandatory before an invoice posts.
Sales order vs purchase order vs quote
One sale passes through several documents, and each has its own author and job. ASCM’s definitions separate them clearly.
| Document | Issued by | What it is | What it sets in motion |
|---|---|---|---|
| Quote | The seller | A statement of price, terms of sale and the goods offered. ASCM notes that a quote given in response to an inquiry is usually considered an offer to sell. | Nothing in the plant or warehouse yet |
| Purchase order (PO) | The buyer | The buyer’s authorization to formalize the purchase, with part numbers, quantities, prices and terms | Order entry at the seller |
| Sales order | The seller, from the PO | The seller’s own record of the customer order, under its own number | The promised date, picking or production, the shipment and the invoice |
| Order acknowledgment | The seller | A message that the PO arrived. ASCM notes that it usually implies acceptance of the order and its terms. | The buyer’s check that prices and dates match the PO |
A quote becomes a sales order when the customer accepts it. In Business Central, you convert the accepted quote into a sales order. Until then, Microsoft notes that a quote has no effect on planning, reservations or availability.
The PO stays the buyer’s document, and the sales order is yours. The purchase order template shows the fields a buyer’s PO usually carries. The invoice comes last: Business Central does not invoice a sales order line until it ships, unless you ship and invoice in the same step.
How an emailed PO becomes a sales order
A PO that arrives by email comes in the customer’s own format: a PDF, a spreadsheet, a scan or lines typed into the message. Someone on the order desk turns it into a sales order in six steps.
The check step relies on two ERP features. Credit limits make Business Central warn about the credit limit and overdue balance when you enter a sales order. Order promising calculates a ship date from stock and planned receipts, or from what you could make or buy.
Where AI fits in order entry
AI can read the PO, match each line and draft the sales order. A person then approves, changes or rejects the draft before it enters the ERP.
Microsoft builds the same approval into its own agent. Its Sales Order Agent for Business Central reads customer emails and their attachments, finds the items and drafts a sales quote first. It asks a person to review every outgoing message, and its FAQ states that it does not post documents.
ThriveAI’s order desk automation does this for emailed POs. It reads each order, checks it against your items and prices, and drafts it for a person to approve. Your data is designed to stay at rest on your own server in Canada. Inference runs on that same server with an open-weight model, or through a frontier model under a written zero-data-retention control.
Text extraction from images explains how software reads a scanned PO, and human in the loop covers what a person should approve.
What goes wrong in order entry
An error made at order entry travels with the order until someone notices it: at the dock, on the invoice or in a short payment. These are the usual errors, each with the check that catches it before entry.
- The wrong item. The customer’s part number maps to an old item, or to none. A current table of item references maps each customer number to yours.
- The wrong price. The PO carries last year’s price or an expired quote. Compare every line with the customer’s current price, and send any difference to a person.
- The wrong unit. The PO says 10 boxes and the order says 10 each. Store the customer’s unit on the item reference, and Business Central copies it onto the order line.
- The same PO entered twice. A customer resends a PO, or sends a revised one, and both become orders. Search open orders for the PO number before you enter a new one.
- A missing PO number. The customer cannot match your invoice to their PO, so the payment waits. Make the external document number mandatory, as Business Central allows.
- A credit warning passed over. The order ships to a customer who is past due. Business Central warns at entry but still lets you post, so set a rule for who may release the order.
- A date promised without checking. The order desk accepts the requested date, and part of the line becomes a backorder. Order promising checks stock and supply first.
Treat a revised PO with the same care as a new one. Compare it line by line with the order already entered, then change only what the customer changed.
Before you automate order entry
Four things decide how well drafting orders works, whether a person or software does the reading.
- Item references. Keep a list of each customer’s part numbers mapped to yours. If it lives in one person’s head, write it down first.
- Price files. Record the price each customer should pay for each item, with the dates each price applies.
- A test set. Gather recent POs from your main customers, with the sales orders your team entered from them.
- The ERP’s import. Find the file layout your ERP accepts for orders, or a test company where you can try the drafts.
With those four in place, you can check each draft against an order your team already entered, before any draft reaches the live ERP. Order to cash follows the order past entry, to the invoice and the payment.