Not all delayed purchase orders delay the same way. Three patterns account for many delayed PO exceptions: supplier-side delays, approval-hold delays, and partial-receipt exceptions. Each starts in a different place, follows a different resolution path, and propagates differently through inventory and fulfillment.
Why classification comes before escalation
A delayed PO is often treated as a single type of operational problem. An alert appears, someone investigates, and a buyer or planner is asked to resolve it. That workflow breaks down when the person receiving the alert cannot tell whether the delay sits with a supplier, an internal approver, or an incomplete receipt.
The distinction matters because the first action is different in each case. A supplier-side delay calls for contact with the supplier and a review of the PO expected receipt date. An approval-hold exception requires an internal escalation to the person or queue blocking release. A partial-receipt exception requires investigation of the remaining quantity, not just the quantity already received.
The propagation profile also differs. A delay may have little effect when sufficient safety stock is available, or it may immediately threaten open orders for a critical component. A partial receipt can be especially difficult because the ERP may show progress, or even a completed line, while the missing quantity remains operationally important.
Pattern is an input to prioritization, not a substitute for it. A low-propagation supplier-side delay on a critical component matters more than an approval-hold on a non-critical item. Classification helps determine the right path. Inventory position, demand, and downstream commitments determine urgency.
Pattern 1: Supplier-side delay
A supplier-side delay begins outside the buying organization. The supplier misses a production date or supplier dispatch date, and the ERP receives an updated shipment date. In other cases, the supplier sends no update at all. In many ERP integrations, that silence is itself a delay signal because the expected movement or confirmation never arrives.
The resolution path usually starts with the buyer. The buyer contacts the supplier to establish what happened, confirms a revised date, and adjusts the PO expected receipt date. If the material is needed sooner, the team may also look for partial stock elsewhere or consider another source.
Its downstream effect depends heavily on inventory coverage. If the item has a healthy buffer, the delay may remain a planning exception with low cascade impact. If the item is already close to its safety stock threshold, the same delay can affect production plans, open customer orders, or later transport commitments.
That means a supplier delay should not be ranked by age alone. A two-day delay for a low-demand item may be less urgent than a one-day delay for a component that supports several open orders. The relevant question is not only, "How late is the supplier?" It is also, "What will run short if the revised date slips again?"
Pattern 2: Approval-hold delay
An approval-hold delay originates inside the organization. The PO is stuck in an internal approval queue, often because it exceeds a value threshold or requires review across departments. Until the PO is approved, the shipment cannot be placed or released to the supplier.
This can look similar to a supplier delay once time passes. The expected receipt date moves out, production may face a shortage, and downstream orders may be exposed. But the resolution path is entirely different. Contacting the supplier does not remove an internal hold. The next step is to identify the approver, understand what is blocking the decision, and push the PO through the appropriate workflow.
Approval age is a useful signal, but it does not establish priority on its own. A 72-hour approval queue age may be highly urgent when the PO covers a critical component with limited safety stock. The same queue age may require less immediate attention when the item is non-critical and inventory is ample.
Consider a procurement analyst at a mid-size manufacturer who receives three PO alerts on the same morning:
- One PO has been in an approval queue for 72 hours.
- One supplier has missed the dispatch date for a critical component.
- One fast-moving inventory item was partially received, with 40% of the ordered quantity still outstanding.
The first alert should go to the internal approver or procurement owner responsible for releasing the PO. The second needs supplier or buyer follow-up, with immediate review of component coverage and open orders. The third needs an investigation of the residual quantity and a decision on whether to wait or place a new PO. Three alerts, three escalation paths.
Pattern 3: Partial-receipt exception
A partial-receipt exception occurs when the PO was dispatched and only part of the order arrived. For example, 60% of the ordered quantity may be received while the remaining 40% has no new ETA. The initial receipt can make the exception appear less urgent than it is, especially when the ERP records the delivered quantity prominently.
The resolution path combines supplier and logistics follow-up. The team needs to establish whether the residual quantity is still with the supplier, in transit with the carrier, delayed at a handoff, or no longer scheduled. It then has to decide whether to wait for the balance, source the missing quantity elsewhere, or place a new PO.
This pattern creates a specific data quality risk. Some ERP configurations close a PO line when it reaches a receipt threshold. If the line is considered complete after a configured percentage is received, the remaining quantity may become invisible in normal exception views. The shortage then reappears only when inventory falls below a threshold or a fulfillment request cannot be met.
For fast-moving items, that delay in visibility can be costly operationally even when the original receipt looked substantial. A 40% shortfall may not affect today's orders, but it can remove the buffer needed for the next replenishment cycle. The exception should therefore be evaluated against demand and safety stock, not just the percentage already received.
Classification depends on ERP normalization
ERP systems do not represent PO exceptions in one consistent format. An approval-hold exception may be stored as a status flag in one ERP and as a separate workflow item in another. Supplier confirmations, shipment dates, receipt thresholds, and residual quantities may also be represented differently by vendor and configuration.
That variation makes direct comparison unreliable. A status that appears to mean "approved" in one system may indicate only that one stage of a multi-tier workflow is complete. A closed PO line may indicate a full receipt in one configuration, but a receipt threshold in another. Accurate classification therefore requires an integration layer that normalizes these representations before assigning a pattern.
Tenoro reads ERP hold codes to classify PO exceptions by pattern type. Each type receives different priority treatment based on its resolution path and propagation profile. The purpose is not to replace the team's judgment, but to make the relevant context visible earlier: who needs to act, what quantity is exposed, and where the delay is likely to travel next.
The practical implication is straightforward. Different delayed PO patterns require different escalation paths. Knowing whether an exception is supplier-side, approval-hold, or partial-receipt at the moment it is detected changes how quickly the right team can act.