1.6 Purchase order management

A Purchase Order (PO) is a formal financial contract. It defines the required physical configuration, the delivery schedule, and the quality standard for a transaction. If a PO is missing data or relies on unwritten assumptions, the liability for misunderstandings or delays often falls on the buyer. A structured PO clearly specifies what is being purchased, when it is required to arrive, and how it will be verified upon receipt.

The PO data requirements

Every PO generated by the ERP must contain a specific dataset to ensure clarity. Missing information can lead to suppliers delivering non-conforming or delayed material.

Identification & revision control

PO Number: A unique, auto-generated ERP identifier.
Revision: The PO Revision must be incremented with any change, including minor date adjustments (e.g. Rev A -> Rev B).
Date of Issue: The issue date confirms the validity window of the quoted price.

The line item definition

MPN (Manufacturer Part Number): The exact, complete alphanumeric string (e.g. “STM32F405RGT6”) must be used. Relying solely on internal ERP Part Numbers must be avoided, as suppliers may not recognize them.
Engineering Description: A brief, clear technical description (e.g. “MCU 32-bit ARM Cortex-M4”).
Quantity: An explicit unit count matching the quoted unit of measure.
Unit Price: The agreed contract price, referencing the Supplier’s formal Quote Number if applicable.

Commercial & physical logistics

Incoterms: Standardized delivery terms (e.g. “FCA Hong Kong”).
Payment Terms: Standardized corporate terms (e.g. Net 45 / Net 60).
Ship-To: The specific physical warehouse address and the attention party (e.g. “Attn: Receiving QA”).
The Promise Date: This should align with the “Dock Date” required by Production Planning, factoring in transit time.

Quality clauses

Traceability: Clauses such as “Vendor warrants all goods are new, original, and fully traceable to the Original Component Manufacturer (OCM)” must be included.
Date Code Restriction: Limits must be specified, e.g. “Date Codes must be ≤ 24 months at receipt unless pre-approved.”
Substitutions: It must be clarified that “Functional equivalents or physical substitutions are not allowed without prior written engineering approval.”

Financial approval thresholds

Risk increases with dollar value and technical complexity. A tiered approval matrix must be implemented in the ERP to manage financial commitments securely.

PO Value Threshold	Risk Category	Typical ERP Sign-off
< $5,000	Low (Class C / COTS)	Buyer
$5,000 – $50,000	Medium (Standard Production)	Sr. Buyer / Commodity Mgr
$50,000 – $250,000	High (Strategic Spend)	Supply Chain Director
> $250,000	Critical (CapEx/Mass Vol)	VP Operations / Corporate CFO
Any Value	NCNR or Custom Silicon	+ Engineering Leadership

The acknowledgement (ACK) discipline

The transaction is not fully established until the supplier provides written confirmation of acceptance.

The Expected Timeline:

The supplier should acknowledge receipt of the document promptly.
The supplier should provide a firm Confirmed Schedule (Commit Date) within an expected window (e.g. 48 hours).

Valid vs. Invalid ACK:

Valid: “We formally accept PO #12345 Rev B. Line 1 is confirmed for FCA delivery on 2023-10-15.”
Invalid: “Received, thanks.” (Confirms email receipt, but not the terms).
Managing Discrepancies: If the Supplier’s Commit Date differs from the PO Need Date, immediate follow-up is required to negotiate or formally update the ERP schedule to reflect the new reality.

Pro-Tip: If a supplier fails to provide an ACK, proactive follow-up is required. Waiting until the due date to discover the order was never processed must be avoided.

Change control & supplier substitutions

Uncontrolled changes can cause schedule disruptions.

Scenario 1: the supplier requests a date push

The Protocol: The downstream impact on the Master Production Schedule must be calculated.
- If there is a risk to the production line, this must be escalated to Supply Chain leadership to address the allocation priority.
- If the schedule can absorb the delay, the ERP “Commit Date” field must be updated. The original “Need Date” must be preserved for accurate vendor performance scoring (OTD).

Scenario 2: the supplier offers a “substitute” part

The Protocol:
- Procurement should not unilaterally approve technical component substitutions.
- Route the request to Engineering via a formal Deviation Request.
- If Engineering approves the substitute, the PO must be revised to explicitly state the new MPN to ensure Receiving QA expects the correct part.

Scenario 3: partial shipments

The Protocol: Partial shipments should ideally be authorized on the PO document (“Partials Allowed”).
- Coordination with Finance is required; the final inventory balance must be ensured to be received before the final invoice is paid.

The pre-flight PO quality audit

The PO must be reviewed for common discrepancies before issuing it to the supplier.

The Check	The Potential Issue	The Resolution
UoM Math	Ordering “100” (reels) instead of “100” (units).	The Unit of Measure must be verified clearly.
Price Match	Price differs from the Validated Quote.	Re-validation against the Quote is required.
Rev Control	Sending an outdated PDF revision.	The sent document must be ensured to match the ERP.
Spec Callout	Missing a specific color or finish code on a custom part.	Explicit Reference Notes must be added.
Ship-To Code	Defaulting to Corporate HQ instead of the Factory dock.	The physical Ship-To Code must be verified.

Final Checkout: Purchase order (po) management

Control Point	Engineering Requirement	Target Metric
Contract Fidelity	All mandatory fields and clauses populated.	100% Completeness
ACK Status	Confirmed Commit Date entered in ERP.	Tracked consistently
Revision Match	PO physical Revision matches BOM Revision.	Verified before send
Liability Limits	Signed agreements attached for NCNR items.	Required for NCNR
Age Limits	Date Code limits included on the document.	Communicated clearly
Authorization	Sign-off limits respected in the ERP workflow.	System Enforced