Sales order: check customer changes before confirming new dates

A sales order is the seller's record of what a customer has ordered: products, quantities, prices, delivery details and agreed terms. It gives sales, planning, purchasing and fulfillment a common reference. It may also produce the confirmation sent to the customer.

For a manufacturer, the difficult question usually comes after entry: can you accept the customer's latest quantity and date without breaking another commitment? A saved order does not answer that. Check the materials, production slots and transport behind the proposed delivery before confirming a change.

Sales order, purchase order and invoice: which document means what?

The same transaction appears from two sides. Your customer's purchase order is incoming demand for your company. Your sales order records that demand on the seller's side. An upstream purchase order for components is a separate transaction with your supplier.

A quotation is an offer, while a sales order records an order in the seller's process. The precise approval and acceptance sequence depends on the commercial arrangement. Do not decide a document's legal effect from its label alone.

Oracle NetSuite's sales-order documentation describes the order as a record of a commitment to sell, distinct from posting the accounting transaction. That is a documented system workflow, not a universal rule for every ERP. Invoicing, reservation and release behavior depend on your system and configuration.

Keep the customer PO number and your sales-order number linked. They identify the same commercial flow but are not interchangeable document numbers.

What should a manufacturing sales order contain?

Record the commercial details your business needs, including customer, bill-to and ship-to addresses, prices, currency, payment terms and delivery terms. For coordination, the useful detail is often at the line and delivery-schedule level.

Keep these fields accessible:

• Customer PO reference, your order number and the specific line.
• Product code, agreed revision or configuration and unit of measure.
• Ordered quantity, quantity delivered, open quantity and any split delivery schedule.
• The customer's requested date and the current confirmed date, with shipment and customer-arrival dates identified separately.
• Change request, source document or email, revision, timestamp and responsible owner.
• Approval and customer acceptance evidence required by your agreed change process.

Retain the previous confirmed quantity and date when you revise the order. Overwriting them makes it hard to distinguish an original promise from a later recovery plan.

Microsoft Business Central documents customer references and separate quantities for partial shipment and invoicing. Those fields illustrate why one order-header status can be insufficient: one line may be delivered, another waiting for parts and a third awaiting the customer's decision.

How do you assess a customer's change request?

Suppose an email asks, “Can we increase the order and receive it a week earlier?” Record it as a change request under your agreed procedure. Acknowledge receipt without accidentally presenting an unchecked date as confirmed.

Assign one owner to collect the decision, then work through four checks.

1. Establish the requested change. Identify the affected order line, current confirmed quantity and date, requested quantity and date, delivery location and product revision. Ask whether the customer can use a split delivery. Check whether an order already released, shipped or invoiced needs a different change procedure.

2. Recheck usable material by date. Review finished goods, component requirements, existing allocations, quality holds and dated receipts. A supplier saying “shipped” does not establish when the material will be received, inspected and released for production. Use the need date as well as the supplier's promise date.

3. Verify capacity and outbound transport. Planning must check the relevant operations, people, equipment, testing and packing. Include handling and transit to the customer's location. Material availability alone does not create a production slot. Review effects on other accepted orders and get approval for any proposed displacement.

4. Approve an option before confirming it. Purchasing verifies supplier quantities and usable receipt dates. Planning checks the production sequence. The responsible commercial owner approves costs, freight and the proposal, then obtains customer acceptance through the agreed change process. Update the connected records and keep the evidence.

Microsoft's order-promising guidance distinguishes available-to-promise calculations from capable-to-promise scenarios and includes time for handling and shipping. Where your ERP provides these calculations, have planning verify their inputs and settings before using the result in a customer confirmation.

Worked example: 140 pumps requested earlier

This is an illustrative planning example, not a customer result. All dates are in 2026.

SO410 currently covers 100 pumps arriving at the customer on Friday, November 6. On Monday, October 26, the customer requests 140 pumps arriving on Friday, October 30: 40 more pumps and a delivery one week earlier.

Assume each pump needs two brackets, there is no scrap allowance in this simplified example, and no finished pumps are available. There are 80 usable brackets available to this order after other allocations.

Buying only the additional 80 brackets is not enough to establish the earlier date. The existing 120 were due to become usable on November 3, after the requested customer arrival.

Purchasing investigates a recovery option. The supplier confirms that 120 brackets can become available on October 27 and another 80 on October 29. For the planning scenario, assume transport and receiving arrangements support those dates, including inspection and release. Until the receipts actually pass those steps, they remain dated commitments rather than physical usable stock.

Now check production. The plant has slots to complete 100 pumps across October 28–29 and the remaining 40 on Monday, November 2. These slots include assembly, testing, packing and loading. All other required materials are available, and the slots do not displace another customer's order.

Outbound transport takes one working day after completion and loading; there is no weekend operation or delivery in this example.

The feasible proposal under these assumptions is 100 on October 30 and 40 on November 3. It is not 140 on October 30. More brackets do not remove the capacity constraint.

Before offering that split, confirm supplier charges, overtime if any, freight, delivery terms and internal approval. Ask the customer whether 100 units on October 30 meets its immediate need and whether it accepts the balance on November 3. Keep the current confirmed plan and the proposed alternative identifiable until the change is accepted under the agreed process.

For real orders, replace these assumptions with evidence. Include actual calendars, yield or scrap requirements, routing, receiving lead time, customer receiving hours and transport constraints.

What should the revised confirmation say?

A useful proposal identifies the order, the affected line, quantities and arrival dates. For this example, the substance is:

Proposed change to SO410, line 1, customer PO C827: 100 pumps arriving October 30, 2026, and 40 arriving November 3, 2026. Please confirm whether this split meets your requirement.

That wording is a draft proposal, not proof of acceptance or a message to send automatically. Add the agreed commercial details and qualifications your process requires. Resolve conditions before issuing the final confirmation.

After acceptance, update the sales-order schedule and the relevant production and supplier records through authorized procedures. Link the accepted revision, the supplier commitments and the internal approvals. Preserve the original plan and the request that caused the change.

A supplier follow-up task should state its own precise requirement: PO, line, part, quantity, shipment or arrival milestone and the date needed for production. Use purchase order tracking and order confirmation to resolve that evidence; do not forward a customer arrival date as though it were the supplier's delivery deadline.

Keep the accepted plan under review

Give each outstanding dependency an owner and a next check. Reopen the feasibility decision if a receipt slips, material fails inspection, capacity changes or the customer changes the requirement again. A confirmed schedule still needs execution.

Cartograph's data model connects customer orders, production, parts and supplier orders. Scout Agent can follow up with suppliers by email and phone to confirm orders, check progress and expedite supply within your team's rules. The shared inbox keeps coordination tasks and their evidence together.

Use that supplier evidence in the team's customer decision. The responsible people still verify feasibility, approve commercial changes and confirm the revised commitment with the customer.

Questions teams ask

Is a sales order the same as a purchase order?

They represent different sides of an order. The buyer issues a purchase order; the seller records a sales order. A manufacturer may also issue separate purchase orders for components. Link the references without confusing customer demand with upstream supply.

Does creating a sales order prove the delivery date is feasible?

No. Check usable material by date, allocations, production capacity, handling and transit. Reservation or order-promising behavior depends on the ERP and its configuration; a saved record alone does not prove the plan can be executed.

What should you do when the customer changes the quantity or date?

Preserve the current confirmed plan, record the request and assess its effects. Obtain the necessary supplier, planning and commercial approvals, then secure customer acceptance through the agreed change process before treating the alternative as the revised commitment.

Can you offer a partial delivery?

Check whether the customer accepts it and whether your terms and procedures allow it. State each quantity and customer-arrival date, confirm costs and dependencies, and retain acceptance. Do not assume an earlier first batch makes the whole order on time.