Purchase-Order Release and Supplier Acknowledgement: Lock the Baseline Before Production

Release one uniquely identified purchase-order revision and require the supplier to read it back before production, packing or invoicing proceeds. A reply that says received may indicate a message arrived, but it does not prove which attachment or revision was received or establish field-level acceptance. A reply with a different quantity, date, price or specification is a proposed change—not acceptance of the buyer's order.

The control loop is straightforward: approve the PO internally, dispatch the exact released revision, obtain an accept/reject/change response at the relevant line and schedule level, decide every exception, then reissue and re-acknowledge any approved amendment. Keep the superseded revision visible so nobody builds from an old attachment.

This is an operational control, not a conclusion about contract formation or document precedence. The legal effect of a PO, acknowledgement, click, email or silence depends on the parties' agreement and applicable law. Get qualified advice where that question matters.

Build the PO from approved inputs, not the latest attachment

The PO should assemble decisions that have already been made. It should not become a place where a buyer quietly invents a new product requirement or where a supplier fills a commercial gap by assumption.

Start with:

• the accepted offer and any clarified assumptions from the RFQ process;
• the controlled product specification, drawing, bill of materials and approved sample references;
• the released packaging specification, artwork and label revisions;
• confirmed item identity, supplier item cross-reference and units of measure;
• agreed unit price, currency, quantity, delivery basis and named place;
• realistic production and shipment dates rather than one undefined lead time;
• payment milestones and evidence required before each release; and
• required commercial, quality, packing and transport documents.

Resolve conflicts before release. If the quote says 1,000 pieces, the draft PO says 1,200 and the packaging brief says 100 cartons of 10, do not ask the supplier to choose. Reconcile the unit arithmetic and issue one baseline.

Give every controlled attachment an ID and revision. See attached specification is not a control when an email thread contains three files with the same filename.

Use a release checklist that can be reconciled line by line

Xero's current purchase-order guidance illustrates common PO fields including supplier, dates, order number, reference, currency, item, description, quantity and price. A manufacturing import order normally needs a more explicit operational cross-reference than an accounting entry alone.

Use this release matrix as OPL analysis and adapt it to the order:

Not every order needs every field on the face of the PO. It does need one controlled reference path to the field. If a separate specification or schedule controls, the PO must point to the exact approved revision and preserve the precedence agreed by the parties.

Separate internal approval, dispatch and supplier acknowledgement

Many systems distinguish internal creation and approval states. Xero, for example, allows purchase orders to remain in draft, move to awaiting approval and then be approved. That does not show that the supplier received or accepted the order.

Use distinct operational statuses:

Record dispatch evidence: date/time, channel, recipient, file hash or system transaction reference where available, and the exact attachment list. A filename alone does not prove which bytes were sent.

Require accept, reject or propose-change responses

Enterprise systems show why a simple received flag is weak. Oracle Procurement can require acknowledgement at document and schedule level. It allows a supplier to accept, partially accept, reject or propose changes to fields such as price, quantity and delivery dates. Proposed changes go back to the buying organisation for decision.

SAP supplier-confirmation documentation likewise describes confirmations containing confirmed quantities and dates, and distinguishes a confirmation from an order change request.

You do not need an enterprise portal to preserve that logic. Give the supplier a structured response sheet or portal fields with three options:

• Accept as issued: the supplier confirms the stated field, line or schedule.
• Reject: the supplier cannot accept it and states the reason.
• Propose change: the supplier gives the requested new value, reason, affected lines and consequence.

At minimum, ask the supplier to read back:

• PO ID and revision;
• supplier sales-order or confirmation reference;
• buyer item and supplier part number;
• specification, drawing, packaging and artwork revisions;
• quantity and unit of measure by line;
• unit price and currency;
• promised quantity by date or schedule line;
• agreed delivery basis and named place reference;
• required sample, inspection, test and document commitments; and
• each exception, with owner and decision date.

Set an acknowledgement due date appropriate to the order and risk. There is no universal 48-hour rule. If the supplier cannot confirm a date because it is waiting on material or capacity evidence, record that as an open exception with a new evidence date—not as an accepted schedule.

Treat every difference as an exception, not a silent overwrite

The supplier may have a legitimate reason to propose a change: raw material availability, capacity, a minimum batch, a unit conversion, a price error or an unrealistic delivery date. The proposal may improve the order. It still needs a decision.

Use this exception workflow:

1. Preserve the supplier's original response and identify the affected PO field, line and schedule.
2. Compare the proposed value with the released baseline.
3. Assess product, quality, compliance, packaging, cost, cash-flow and schedule effects with the appropriate owners.
4. Accept, reject or request clarification through an attributable buyer decision.
5. If accepted, issue a revised PO or controlled amendment under the agreed document process.
6. Mark the previous revision superseded and prevent it from remaining in the factory work pack.
7. Obtain acknowledgement of the new revision and close the exception only when the read-back matches.

Do not edit the buyer's spreadsheet to the supplier's date and lose the evidence that a change occurred. Do not let an ERP integration automatically turn a supplier proposal into an approved baseline without the configured buyer review.

If the change affects a material, component, dimension, process, manufacturing site, sub-supplier, packaging, artwork or test method, route it through the product change-control process. A PO amendment records the commercial release; it does not replace the technical or compliance assessment.

Reconcile the acknowledged PO at every later gate

Acknowledgement is not a one-time administrative task. Use the accepted revision as the reference at later decisions.

Before payment. Reconcile the supplier's proforma invoice to the acknowledged PO: entity, item, quantity, unit, price, currency, payment milestone and bank-account control. The proforma invoice checklist covers that transaction gate. An invoice mismatch is not a convenient way to amend the PO.

Before production. Take the acknowledged revision into the pre-production meeting. Confirm that production, quality and packaging teams have the same PO and controlled attachments. Do not release production if the sales contact acknowledged revision 3 but the line is holding revision 2.

During production. Compare promised schedule lines with evidence-based milestones. The supplier production lead-time guide explains how to replace one vague duration with attributable stages and dates.

Before packing and shipment. Reconcile finished quantities, pack-out, marks, documents, inspection status and agreed delivery basis. Approved partial shipment or split schedules should be visible as controlled revisions or acknowledged schedules, not improvised at the loading dock.

Before final invoice approval. Reconcile what was ordered, acknowledged, changed, shipped and invoiced. Preserve approved variations rather than forcing the accounts team to infer them from email.

Worked example: a date and packaging mismatch

This example is hypothetical and is not an OPL customer case.

PO AUS-1042 R03 contains two lines. Both cite product specification PS-18 R06 and packaging specification PK-18 R04. Line 10 is 2,000 units required for shipment on 15 October. Line 20 is 600 units required on 22 October.

The supplier replies:

• Line 10: accepts item, revision, quantity, unit price and date.
• Line 20: confirms only 400 units for 22 October and proposes 200 units for 5 November.
• Header note: proposes using old packaging artwork PK-18 R03 because printed cartons remain in stock.

The buyer should not mark the whole PO acknowledged.

The supplier's R03 response stays in the record. PO R04 becomes operative only after buyer approval and controlled release. If the supplier then acknowledges the R04 quantities, dates and packaging revision, the exception can close. The old cartons remain a separate disposition decision; their existence does not authorise their use.

Use a simple release and acknowledgement register

A spreadsheet can work at low volume if its status, ownership and revision rules are controlled. Use one row per PO line or schedule where differences matter. Record:

• PO ID and current revision;
• released date, approver and dispatch evidence;
• supplier acknowledgement reference and received date;
• line/schedule response status;
• acknowledged item, quantity, unit, price, currency and date;
• specification and packaging revisions;
• exception ID, proposed value, owner and due date;
• buyer decision and amendment reference; and
• final accepted revision and downstream gate status.

Run an exception view for unacknowledged, partially acknowledged, changed and overdue responses. Do not use no reply as a green status.

The immediate next step is to choose one open manufacturing order and reconstruct its baseline. Can you point to the exact approved PO revision, prove what was sent, show the supplier's line-level response and identify every unresolved difference? If not, stop the affected release and close those gaps before the order moves further into production.

The goal is not more paperwork. It is one shared operational truth: the buyer knows what it released, the supplier knows what it accepted, and every difference has an owner and an authorised path to a new baseline.

Sources

1. Xero Central — Create a purchase order
2. Xero Central — Submit and approve purchase orders
3. Oracle Procurement — How you manage purchasing documents requiring supplier acknowledgment
4. Oracle Procurement — Supplier acknowledgment of purchasing documents
5. Oracle B2B — Purchase Order Acknowledgment Inbound Transformation
6. SAP Help — Receipt of Supplier Confirmation
7. SAP Help — Vendor Confirmation