A late purchase order can disrupt several customer promises. Check free stock, compare dates and agree a realistic delivery option before changing the plan.
Connect the supplier update to stock availability and the customer’s delivery plan.
The supplier says the goods will arrive “in a few days.” Your customer expects delivery on Sunday. The warehouse has some stock, but another order already needs part of it.
A supplier delay becomes harder to manage when each person works from a different version of the situation. Purchasing knows the latest estimate, sales remembers the original promise, and the storekeeper is asked to release stock that is already committed.
Start by connecting the late purchase order to the customer orders it affects. Then check quantities, dates and realistic alternatives before promising a new delivery.
Here is a practical routine for an electrical-goods wholesaler in Butwal. The business, quantities and dates below are hypothetical.
Confirm the item, unit and physical receipt before updating the available quantity.
Confirm what is late and what is still uncertain
Record the purchase order, item code, unit, original required date, quantity received and open balance. Ask the supplier for a revised arrival estimate at your receiving location, the quantity expected and the next confirmation time.
“Dispatched” and “ready to use” are different milestones. Allow for transport, counting and any inspection your process requires. Label an estimate as an estimate until supporting information improves its reliability.
ERPNext’s Purchase Order documentation illustrates useful controls: item-level required dates, warehouse references and separate received and billed progress. These are examples of information to retain, rather than proof of any WorkSphere feature.
Keep the original date alongside the revised estimate. Replacing it removes the evidence needed to understand the delay later.
Calculate what you can actually release
Suppose the review takes place on 13 November 2026. One customer needs 80 identical switches by 15 November. All quantities use individual pieces, and there are no damaged units, returns or other commitments beyond those shown.
| Check |
Quantity |
Meaning |
| Usable stock physically on hand |
50 |
Includes all earlier receipts |
| Reserved for a different confirmed order |
20 |
Keep this commitment separate |
| Free stock for this customer |
30 |
50 minus 20 |
| Current customer requirement |
80 |
Count this order once |
| Shortfall against the requirement |
50 |
80 minus 30 |
The supplier purchase order was for 100 switches. Forty have already been received and are already reflected in the 50 on hand. The remaining 60 are outstanding on that purchase order.
Free stock is 30 pieces, not 70. Adding the earlier receipt of 40 again would double-count it. The 60 still on order are future supply; they cannot be released from today’s shelf.
ERPNext’s Purchase Receipt documentation describes separate receipts for partial deliveries and retaining the remaining purchase-order balance. The practical lesson is to distinguish ordered, received and currently usable quantities.
Hypothetical calculation separates free stock from earlier receipts and future supply.
Compare arrival dates with the customer deadline
In this example, the supplier originally promised arrival on 12 November. Its latest estimate is 17 November, after the customer’s 15 November deadline.
For planning, assume all 60 incoming switches will pass receiving checks by the end of 17 November, and customer delivery needs one further calendar day. Assume the business and customer can receive deliveries on the dates shown. These are planning assumptions, not a transport guarantee.
That makes 18 November the proposed date for the remaining 50 switches. It does not make the original deadline achievable.
If the customer accepts a split, 30 could be delivered on 15 November and 50 on 18 November. After the incoming 60 are accepted and 50 are allocated to that balance, 10 remain unallocated. The 20 reserved for the other order remain protected throughout.
Recheck the plan if the incoming quantity, inspection result, transport capacity or another commitment changes.
Keep original commitments visible beside revised estimates and proposed delivery dates.
Offer a choice the customer can evaluate
Before contacting the customer, check whether a partial delivery is useful. A contractor may need the full quantity before starting a job. Thirty switches may help one project and create extra handling for another.
Possible options include an agreed split, an approved equivalent from another supplier, or a revised full-delivery date. Check specifications before proposing a substitute. Confirm extra delivery charges and who approves them; do not quietly add a cost to the customer’s order.
A clear message could say:
“We can prepare 30 of your 80 switches for 15 November. The remaining 50 depend on a supplier delivery currently estimated for 17 November; our proposed delivery is 18 November after receiving checks. Would a split help, or do you need the full quantity together? We will update you again on 14 November.”
This hypothetical message separates confirmed capacity from a conditional estimate. Record the customer’s response before changing the agreed plan.
Offer a useful delivery choice and record the customer’s response.
Give each team a specific next action
Use one shared exception record linked to the affected purchase and sales orders.
| Owner |
Next action |
Evidence or review point |
| Buyer |
Confirm the remaining 60 and arrival estimate |
Supplier update by 14 November |
| Storekeeper |
Check and protect the two allocations |
20 for the other order; 30 for this one |
| Sales coordinator |
Agree a useful delivery option |
Customer response and next update date |
| Dispatch lead |
Check capacity for the proposed dates |
Booking or documented availability |
| Accounts |
Review approved extra costs, if any |
Cost approval and payment requirements |
For planned WorkSphere workflows, evaluate links between purchase-order exceptions, inventory allocations, CRM conversations and follow-up tasks. Manufacturing businesses would also check whether late materials affect a production job before confirming finished-goods delivery. HRM can help identify staff availability where that information is needed for receiving or dispatch planning.
These are workflow requirements to assess. They do not assert that the integrations are currently available.
Check feasibility and agreement before changing the customer promise.
Close the delay only after the outcome is recorded
At the next review, check whether goods arrived, how many were accepted, what was delivered and whether the customer’s remaining requirement changed.
A supplier’s dispatch message is an update, not evidence that the customer order is complete. Keep the issue open until the agreed outcome is verified, or an approved change closes the remaining requirement.
Retain the original dates and actual results. They provide a better basis for reviewing supplier reliability than a list containing only the latest estimates.