4.4 Order acceptance rules: PO validation & promise logic

A Purchase Order (PO) is a binding legal contract, not merely a request. Once accepted, the factory commits significant resources—capital, production capacity, and legal liability. Accepting a PO with errors, such as incorrect pricing, ambiguous revision levels, or unrealistic delivery dates, creates a cascade of administrative rework and erodes profit margins. Therefore, a “Clean Order” policy is essential: if the PO data does not align with the established system of record, the order must be rejected immediately.

The “clean order” validation

This validation process must be automated. Relying on sales administrators to manually remember correct pricing is unreliable and risky. Every incoming PO must be systematically compared against the active Quotation and the Master Supply Agreement (MSA).

Action: If any of the following criteria fail validation against the system of record, the PO must be placed on Administrative Hold until the discrepancy is formally resolved.

Validation Point	Validation Requirement	Action on Failure
Pricing	PO Unit Price matches Quoted Price in System	Reject. Request Amendment.
Revision	PO Revision matches Current Engineering Revision	Reject. Clarify Rev level.
MOQ / MPQ	Quantity meets MOQ and is a multiple of MPQ	Round Up. Request authorization to adjust.
Incoterms	PO Terms match MSA Terms	Reject. Logistics liability risk.
Credit Status	Total AR plus New PO is within Credit Limit	Hold. Finance release required.

Promise-date logic (the commit)

The Requested Date represents the customer’s desired timeline. The Promise Date is the factory’s formal commitment. These two dates rarely align perfectly. The Promise Date must be calculated based on concrete operational constraints, not optimism.

The calculation formula

The standard formula for calculating the Promise Date is: Promise Date = T~~entry~~ + Max ( LTₘₐₜₑᵣᵢₐₗ , LT~~capacity~~ ) + Tₜᵣₐₙₛᵢₜ

Promise date calculation scenarios:

Standard Lead Time: For orders using bonded or confirmed in-stock materials, the Promise Date is simply the Order Entry Date plus the standard Manufacturing Lead Time.
Shortage / Lead Time Constraints: When critical components have lead times longer than the standard manufacturing cycle, they become the driving factor. In this case, the Promise Date is calculated as the Component Arrival Date plus one week for processing and assembly.

Capacity Saturation: If line utilization exceeds 95% for the customer’s requested week, the Promise Date must be adjusted to the first available “Open Slot” in the master production schedule.

Rule: The delivery date calculated by the ERP system must never be overridden based solely on sales pressure. Manually promising a Week 8 delivery when the system calculates Week 12 sets the entire production team up for failure.

Expedite rules (breaking the queue)

An expedite request asks the factory to displace another customer’s order or incur premium costs. Such services cannot be provided for free.

Category A: Supply Expedite (Material)

Trigger: Required when pulling in a delivery date necessitates air freighting raw materials or paying broker premiums.
Rule: The customer is responsible for 100% of the Purchase Price Variance (PPV) plus the freight cost difference.
Approval: A formal PO Amendment confirming these charges is required before any logistics are booked.

Category B: Manufacturing Expedite (Labor)

Trigger: Required when meeting a date requires scheduling Overtime (OT) or weekend shifts.
Rule: A flat fee is applied (e.g., an additional 15% of the order value or a fixed OT rate).
Constraint: Remember, you cannot expedite physics. Mandatory process times—such as cure cycles, burn-in, and thermal profiling—cannot be safely compressed.

Expedite evaluation constraints:

Any expedite request that would violate the Minimum Process Time for a given operation must be declined. Compressing these physical processes introduces an unacceptable risk of quality failure.
Expedite requests that require “Line Jumping” (delaying another customer’s confirmed build) require explicit approval from the VP of Operations before a commitment can be made.

The order acknowledgement (OA)

The PO is the customer’s offer; the OA is the factory’s formal acceptance. The legal contract is not formed until the OA is issued.

SLA: The Order Acknowledgement must be sent within 48 hours of PO receipt.

Content requirements:

Confirmed Quantity: (May differ from the PO quantity if MPQ rounding was applied).
Confirmed Price: (Must match the quoted price).
Promise Date: (The binding delivery commitment).
Incoterms: (Confirming the point of liability transfer).

Status:

Accepted: All dates and terms align with the PO.
Accepted with Exceptions: Dates have been shifted or prices corrected. This status requires formal customer confirmation.
Rejected: PO contains invalid terms that cannot be accepted.

Recap: PO Validation & Promise Logic

Validation Parameter	Requirement / Constraint	Action on Failure / Non-Compliance
PO Data Validation	Unit price, revision, Incoterms, and credit status must match system of record (Quotation/MSA).	Reject PO. Place on Administrative Hold.
Quantity Validation	Must meet Minimum Order Quantity (MOQ) and be a multiple of Minimum Pack Quantity (MPQ).	Round up quantity. Request authorization.
Promise Date Calculation	Promise Date = Order Entry Date + Max(Material Lead Time, Capacity Lead Time) + Transit Time. Never override ERP calculation.	Do not commit. Schedule to next available slot if capacity >95%.
Expedite (Material)	Customer pays 100% Purchase Price Variance (PPV) + freight difference. Formal PO amendment required.	Decline request if no amendment. Do not book logistics.
Expedite (Manufacturing)	Apply flat fee (e.g., 15% of order value). Must not violate mandatory process times (cure, burn-in).	Decline request if it compresses mandatory process times.
Order Acknowledgement (OA)	Must be issued within 48 hours of PO receipt. Must include confirmed quantity, price, promise date, and Incoterms.	Contract is not binding until OA issued. Status is “Accepted with Exceptions” if terms differ.