4.4 Order acceptance rules: PO validation & promise logic
A Purchase Order (PO) is not a suggestion; it is a binding legal contract. Once accepted, the factory commits capital, capacity, and liability. Accepting a “dirty” PO (incorrect price, ambiguous revision, impossible date) creates a blast radius of administrative rework and margin erosion. A “Clean Order” policy is operated on: If the data does not align with the system of record, the order is rejected immediately.
The “clean order” validation
Section titled “The “clean order” validation”This check must be automated. Sales admins must not be relied upon to “remember” the pricing. The PO must be compared against the active Quotation and Master Supply Agreement (MSA).
Action: When any of the following criteria fail validation against the established system of record, the PO must be placed on Administrative Hold until the discrepancy is 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. |
Pro-Tip: “Phantom Revisions” must be watched out for. Customers often copy-paste old POs. If they order Rev A, but the active Rev is B, and it is accepted, there is a legal obligation to build obsolete product or face a non-conformance penalty.
Promise-date logic (the commit)
Section titled “Promise-date logic (the commit)”The Requested Date is the customer’s wish. The Promise Date is the factory’s commitment. These two rarely align perfectly. The Promise Date is calculated based on constraints, not optimism.
The calculation formula
Section titled “The calculation formula”Promise Date = Tentry + Max ( LTₘₐₜₑᵣᵢₐₗ , LTcapacity ) + Tₜᵣₐₙₛᵢₜ
Promise date calculation scenarios:
Section titled “Promise date calculation scenarios:”- Standard Lead Time:
- For bonded or definitively in-stock material, the Promise Date equals the Order Date plus the standard Manufacturing Lead Time.
- Shortage / Lead Time Constraints:
- Critical components with lead times exceeding the standard manufacturing lead time dictate a Promise Date calculated as the Component Arrival Date plus one week for processing and assembly.
- Action: Clearly communicate the specific “Gating Item” driving the extended schedule to the customer.
- Capacity Saturation:
- Line Utilization exceeding 95% for the customer’s Requested Week requires the Promise Date to slide to the first available “Open Slot” in the master production schedule.
Rule: The ERP’s calculated date must never be overridden based solely on sales pressure. Manually overriding a system-calculated Week 12 delivery to promise Week 8 sets the entire team up for inevitable failure.
Expedite rules (breaking the queue)
Section titled “Expedite rules (breaking the queue)”An expedite request is a request to displace another customer or incur premium costs. It cannot be free.
Category a: supply expedite (material)
Section titled “Category a: supply expedite (material)”- Trigger: Pull-in requires air freighting raw materials or paying broker premiums.
- Rule: Customer pays 100% of the PPV (Purchase Price Variance) + Freight delta.
- Approval: PO Amendment required before booking logistics.
Category b: manufacturing expedite (labor)
Section titled “Category b: manufacturing expedite (labor)”- Trigger: Pull-in requires Overtime (OT) or Weekend shifts.
- Rule: Flat fee applied (e.g. $+15\%$ of order value or fixed OT rate).
- Constraint: You cannot expedite physics. Cure times, burn-in cycles, and thermal profiles cannot be compressed.
Expedite evaluation constraints:
Section titled “Expedite evaluation constraints:”- Requested expedites violating the Minimum Process Time must be declined. Compressing physical processes introduces an unacceptable risk of quality failure.
- Expedite requests necessitating “Line Jumping” (delaying another customer’s scheduled build) require explicit VP Ops approval before commitment.
The order acknowledgement (OA)
Section titled “The order acknowledgement (OA)”The PO is the offer; the OA is the acceptance. The contract is not formed until the OA is sent.
SLA: 48 Hours from PO Receipt.
Content requirements:
Section titled “Content requirements:”- Confirmed Quantity: (May differ from PO if MPQ rounding applied).
- Confirmed Price: (Must match Quote).
- Promise Date: (The binding date).
- Incoterms: (Confirming transfer of liability).
Status:
Section titled “Status:”- Accepted: Dates and Terms align.
- Accepted with Exceptions: Dates shifted; Price corrected. (Requires Customer confirmation).
- Rejected: Invalid Terms.
Final Checkout: Order acceptance rules: Purchase Order (PO) validation & commitment logic
Section titled “Final Checkout: Order acceptance rules: Purchase Order (PO) validation & commitment logic”| Control Point | Passing Criteria | State |
|---|---|---|
| Price Match | Exact match to active quote ID. | Match / Mismatch |
| Material Check | ”Clear to Build” (CTB) analysis complete; shortages identified. | Complete |
| Date Feasibility | Promise date accounts for longest lead-time component. | Verified |
| Engineering Status | No active Engineering Change Orders (ECOs) or “Stop Ships” on this | Clear |
| Expedite Fee | If expedited, fee is added as a separate line item. | Added / N/A |