How to track partial deliveries and order balances for project materials
A partial delivery does not close an order. Separate physical receipt, acceptance and the remaining quantity to make the next supply decision clearer.
A project order may arrive in several shipments. In that situation, “the order has been delivered” is not a sufficiently precise status. Procurement and site teams need to see which items have arrived, which have passed inspection and which are available for the intended use.
Partial delivery tracking starts with each purchase order line. In a supply chain connecting Türkiye, the Gulf or another project market, one item may be split across several pallets, containers or delivery locations. A single order-level status can hide that detail.
Separate dispatch from receipt and acceptance
Materials leaving a supplier, arriving at the delivery point and being accepted are different events. Keep these current quantities distinct:
- Dispatched but not yet received at the delivery point.
- Physically received and awaiting inspection.
- Accepted after the required checks.
- On hold because of damage, a nonconformity or missing documentation.
- Returned or removed from scope through an approved order change.
The same quantity must not appear in two current-state groups. An accepted item should no longer remain in the inspection queue. Dispatch and receipt totals are movement records; adding them to current-state quantities would count the same material more than once.
Name the balance you are measuring
An outstanding delivery balance and an outstanding acceptance balance answer different questions. The first shows how much of the current order scope has not been physically received. The second shows how much has not been accepted, including material already on site but still awaiting a decision.
Consider an illustrative order line for 100 units, with no cancellations or returns. The site has received 60 units. Of these, 55 have been accepted and 5 are awaiting inspection.
| Measure | Illustrative quantity | Meaning |
|---|---|---|
| Current order requirement | 100 units | Approved scope |
| Physically received | 60 units | Arrived, regardless of acceptance |
| Accepted | 55 units | Supported by an acceptance record |
| Awaiting inspection | 5 units | On site but not yet accepted |
| Not yet received | 40 units | 100 minus 60 |
| Not yet accepted in total | 45 units | 40 not received plus 5 awaiting inspection |
The 45-unit acceptance balance is not an instruction to order another 45 units. If the 5 units awaiting inspection are accepted, that balance falls to 40 without another delivery. A return, replacement or cancellation must be recorded with its supporting reference before the affected quantities are updated.
Connect each line to its evidence
A useful register contains the purchase order and line number, product code, unit of measure, approved quantity, delivery point, shipment reference, received quantity, accepted quantity and next action. Add batch or serial references where the item requires them.
Link physical receipt to the delivery record and the inspection outcome to an acceptance or nonconformity record. Photographs and correspondence may support the review, but do not close an order based only on a photograph when the quantity or acceptance status remains uncertain.
An invoice does not, by itself, establish that all materials have arrived or been accepted. Keep invoicing, payment, physical receipt and acceptance as separate statuses.
Give every open line an owner and a next action
“Pending” is not a complete action plan. Record why the quantity is open, who is responsible and when the next check is due. Material that has not been produced requires a different response from material in transit, at the wrong delivery point or awaiting site inspection.
A supplier's estimated date should not automatically become an approved delivery commitment to the customer. Retain the source of each date update and identify the order lines affected. For the time-related part of this workflow, see the site logistics ETA guide.
Use ERP and AI to support checking
An ERP workflow can match delivery lines to purchase orders, flag duplicate document entries and display outstanding quantities. AI can suggest product codes or quantities extracted from documents. A person should review unclear text, conflicting units and product-code mismatches before those suggestions become records.
An automated suggestion is not an acceptance decision. It should not close an order or create a new delivery promise. Keep unresolved differences visible for the responsible team to review.
Complete a final reconciliation before closing the order
Compare the current approved scope with the net accepted quantity. Review open returns, replacements, nonconformities and missing documents. Then record the closure decision, its supporting evidence and the decision owner. The next project review can then show what “complete” actually means.
For a project materials enquiry, share your item list, quantities and delivery locations through the RHB Group contact page.
Frequently asked questions
Can an order be closed after a partial delivery
One shipment arriving does not establish that the full order is complete. Review the current scope, acceptance status and open items before recording closure.
Is every item on site considered accepted
No. Physical receipt and acceptance are different records. Quantities awaiting inspection or held for a nonconformity should remain visible separately.
Can quantities with different units be compared directly
No. Cartons, pieces, kilograms, metres and square metres are not interchangeable. Where a verified conversion exists, record it together with its product or packaging source.
