A purchase order can be accepted while only part of the order has arrived. If the record has only an “open” or “done” checkbox, that middle state becomes difficult to manage. You need to know which lines arrived, which quantities remain outstanding, and which delivery documents explain the difference.
This guide shows how to track partial deliveries on purchase orders using a line-level receiving log. It includes a fictional split-delivery example, quantity calculations, exception handling, and a weekly review. The focus is operational recordkeeping; your business’s approval, accounting, and payment rules remain separate decisions.
Track receipt by order line, not by the entire shipment
A shipment and a purchase order are different records. One shipment can contain only some lines from an order, and one order can arrive in several shipments. A single status attached to a shipping notice cannot tell you whether every ordered item has been received.
Give each PO line an identifier and preserve its item description, quantity, and unit of measure. Use that line identifier in each receipt entry. A vendor item code is useful, but it may not be enough when an order contains the same item for two locations or different requested dates.
Distinguish expected, delivered, checked, and recorded. A dispatch email is evidence of the supplier’s update, not your confirmation that the goods arrived. A receiving record should state what was actually counted or otherwise verified under your process and who made that record.
If a delivery includes several orders, split the receipt across the appropriate PO lines. Do not attach the entire delivery total to each order. Keep the shared delivery reference so you can reconstruct how the shipment was allocated.
Use a receiving log with clear quantity definitions
Start with a stable copy of the sent PO. Then add receipt events without changing the original order to make the numbers look complete. A compact receiving log needs the following information:
- Order identity: PO number, version or issued reference, vendor, and line identifier.
- Ordered amount: quantity and unit of measure from the relevant order line.
- Receipt event: date, delivery reference, recorded quantity, recorder, and receiving location.
- Evidence: packing slip, delivery note, relevant photo, or other receiving record.
- Running position: cumulative recorded quantity and outstanding quantity.
- Exception: shortage, apparent damage, substitution, disputed count, or incorrect item.
- Follow-up: owner, supplier response, expected next event, and review date.
Write your quantity convention into the log. In the simple example below, “received” means quantities accepted into the order’s receipt total under the receiving process. Items held aside for clarification are described separately until their treatment is resolved.
Different systems may use “received” differently. The important point is consistency and visibility. Do not subtract a damaged item from one report while including it in another without explaining the difference.
A fictional example: one order, three receipt events
Imagine a studio orders 24 storage bins and 10 label packs under PO-104. Line 1 is 24 bins measured individually. Line 2 is 10 packs, each containing the supplier’s stated number of labels. The studio records both the order unit and the pack description so nobody later counts individual labels as packs.
The first delivery contains 14 bins and 6 label packs. After checking the items, the receiver records those quantities against lines 1 and 2 with delivery reference DN-201. The PO is partially received: 10 bins and 4 label packs remain outstanding.
The second delivery contains 8 bins and 4 label packs, recorded under DN-219. The label-pack line is now complete, but the bin line still has 2 outstanding. The purchase order as a whole remains partially received even though one line is fully received.
| PO line | Ordered | First receipt | Second receipt | Outstanding |
|---|---|---|---|---|
| 1: storage bins | 24 each | 14 each | 8 each | 2 each |
| 2: label packs | 10 packs | 6 packs | 4 packs | 0 packs |
A third delivery supplies the remaining 2 bins. Once that event is checked and recorded, both lines have zero outstanding. The receipt state can become received. Administrative closure, invoice checks, or other business steps may still remain; receipt completion alone does not resolve them.
Calculate outstanding quantities from the event history
For an unchanged order line with no returns or corrections, the basic calculation is ordered quantity minus cumulative received quantity. After the second delivery in the example, the bin line has 24 − (14 + 8) = 2 outstanding. The label-pack line has 10 − (6 + 4) = 0.
Calculate each line in its own unit. Adding 24 bins and 10 packs into “34 items” may produce a total, but it does not help reconcile the order. Keep the line-level position visible even if a summary dashboard uses a simpler status.
Use receipt events rather than repeatedly typing a new cumulative total. If the cumulative figure changes from 14 to 22, the event history should explain the additional 8 and identify the delivery that supplied them. Otherwise, a typo and a genuine delivery look the same.
If a receipt entry was wrong, correct it through the appropriate documented process. Preserve why the running total changed. Do not add a fictional negative delivery or rewrite an old packing slip merely to make the current number agree.
Resolve pack sizes before posting the count
Unit mismatches are easy to miss. A PO may order 10 packs while a delivery note states 100 individual labels. Those numbers can describe the same physical quantity, but only if the relevant pack size is confirmed. Record the conversion and its source rather than relying on memory.
Keep the supplier’s product description and the order unit readable. A short internal code without a unit can cause the receiver to record a carton as one item when the order expects the units inside it. Make the expected count clear before the next delivery arrives.
When packaging differs from the order, pause the affected entry until the count and conversion can be verified. Other correctly identified lines can still be recorded. One ambiguous package should not require inventing a receipt total for the entire shipment.
For a recurring supplier, reuse verified item information carefully. Check whether the current order uses the same pack size. Catalog descriptions can change, and a previous order’s conversion should not silently override the current document.
Keep shortages, damage, and substitutions visible
A packing slip may state a quantity different from what the receiver counts. Record both the supplier’s stated quantity and the observed discrepancy in the exception record. The receipt total should follow the verified treatment under your receiving process, not automatically copy the supplier document.
For apparent damage, identify the item, quantity, condition observed, and relevant photos. Keep any hold or review status visible. Avoid describing an unexamined item as accepted merely because it physically reached the site.
For a substitution, record the ordered item and the delivered alternative separately. Identify who can decide whether the alternative is acceptable. Do not rename the PO line to the substitute before that decision is made, because doing so erases the original request.
Ask the supplier a focused question with the PO and line references. “PO-104 line 1 has 2 bins outstanding after DN-219; please confirm the remaining delivery plan” is more useful than “Where is the rest?” Record the response and its date without treating an estimate as a guaranteed arrival.
Separate a genuine order change from a receipt
If the business decides it no longer needs the remaining quantity, that is an order decision. It is not a delivery. Preserve the original order and record the authorized cancellation or amendment through the appropriate workflow.
Similarly, an unexpected extra item should not automatically increase the ordered quantity. Identify the overage and decide how it will be handled. A system that prevents received quantities exceeding the order can help expose this discrepancy, but it does not choose the commercial resolution.
Returns also need their own understandable record. State which prior receipt they relate to and what happens next: replacement expected, credit under discussion, or another agreed outcome. The original arrival still happened even if the goods later left the site.
If your receiving app does not support the needed correction or return state, keep the exception in a linked record and use the supported workflow. Do not force an unsupported event into an unrelated field just to clear an outstanding flag.
Review open orders with a decision-focused checklist
Review the lines that still have outstanding quantities, not just the age of the PO. For each one, check the last receipt, supplier’s latest response, expected next event, and operational consequence. A small outstanding quantity may matter more than a large one if it prevents the next task.
Assign one follow-up owner. Multiple people chasing the same supplier can create inconsistent answers while everyone assumes someone else updated the record. Note when the supplier was contacted and when the next review should occur.
Check for receipts that arrived physically but were never entered, duplicate entries, unresolved unit conversions, and lines incorrectly marked complete. Compare the event references with the underlying delivery documents rather than checking arithmetic alone.
When an outstanding line is no longer expected, confirm the actual resolution before closing it. “Old” is not a meaningful closure reason. A clear closing note might identify a completed final delivery or a documented cancellation decision.
Keep receiving separate from invoice approval
The receipt log explains what arrived and how it was recorded. An invoice explains what the supplier billed. These records can inform each other, but one does not replace the other. A complete delivery does not by itself establish that an invoice amount, tax treatment, or payment timing is correct.
Provide the relevant PO, receipt events, and exceptions to the person handling the invoice under your business process. If a bill covers only part of an order, line references make the comparison easier. Preserve disputed or unresolved quantities so they remain visible during that review.
Our purchase order template covers the original order record. Use it as the baseline, then let the receiving history explain the later events instead of editing the order after every arrival.
Prevent a delivery note from becoming two receipts
Choose a duplicate check before entering a receipt. Compare the PO, delivery reference, date, line, and quantity with existing events. A colleague may already have recorded the delivery while you were away, or a supplier may have resent the same note with a new email subject.
Do not assume identical quantities mean duplication. Two genuine deliveries can contain the same amount. The event references and physical receiving information should explain whether they are separate arrivals. If the reference is missing, resolve that uncertainty before posting an entry that could falsely complete the order.
In a shared receiving process, agree who records the event and how others know it has been entered. Even a simple handoff note can prevent double entry. The cumulative quantity should be the result of verified events, rather than a target people adjust until the PO appears finished.
Use Vendraft for line receipts and purchase-order status
Vendraft creates purchase orders and preserves a snapshot when an order is marked sent. Its official listing describes sent, accepted, partially received, received, and closed states, with receipt recording that prevents quantities exceeding the order. Its company, vendor, order, and receipt data stays on the device unless you choose to share or export.
View Vendraft on the App Store for current features, plan access, and compatibility. Keep the supporting delivery documents and exception decisions alongside the workflow. Accurate receiving depends on real counts and clear units as much as on a status label.
Sources and example scope
Product capabilities were checked against the official Vendraft listing and product page. PO-104, the quantities, documents, and studio are fictional. The calculations illustrate the stated simple receipt convention, without prescribing accounting treatment, payment approval, or purchasing authority.