Partial Delivery POD: Keep Each Stop and Quantity Clear

A job with three deliveries can be complete at one stop and unresolved at another. If the office uses one whole-job quantity and a single “delivered” label, accounts may send an invoice pack that appears to confirm more than the receiver accepted.

Partial delivery POD records need to describe each delivery event clearly. The aim is to make the quantity and remaining work understandable without reconstructing the route from a driver's memory.

Distinguish the job total from the stop outcome

Record the booked consignment separately from the quantity planned for each stop. At delivery, record what the receiver accepted, what remained and the unit used.

If a PDF displays a whole-job quantity, do not assume it represents the quantity received at that specific location. Read the label and supporting notes. Software should make the distinction clear, but the office still needs to review the pack before relying on it.

Give each delivery its own identity

Use job reference, stop location, delivery order or customer reference and event time together. Similar customer names at different sites are not enough to identify the right evidence.

The record should answer:

• Which delivery stop does this evidence describe?
• What quantity was planned there?
• What quantity was actually accepted?
• What did the receiver say about the difference?
• Where did the remaining goods go?
• Who authorised the next action?

Keep photos, receipts and recipient details tied to the correct event. Never reuse a signature from one stop to fill a gap at another.

Test a short-delivery example

Consider a fictional job carrying twelve pallets. Site A expects five, Site B expects four and Site C expects three. Site B accepts only two because of a booking disagreement.

The office now needs evidence for five at A, two at B and three at C, plus an instruction for the two still on the trailer. The job's original twelve-pallet total is still useful context, but it is not evidence that Site B received four.

Confirm the remaining load does not get lost when the final planned stop is completed. Give the return or re-delivery a traceable reference and preserve the original attempt.

Keep corrections visible

If the driver entered the wrong quantity, establish the source of the corrected figure and retain an explanation. If the evidence is unclear, ask for clarification rather than inventing a neat answer.

Older records may link POD to stops differently from records created by a newer app. When evaluating software, inspect both an older job and a newly created multi-stop example. A confident demonstration on a single delivery does not prove all historical evidence is mapped perfectly.

Agree the billing treatment

Partial acceptance and the haulage charge are separate questions. Check the customer's terms and any instruction about waiting, return or re-delivery. The official invoice guidance covers invoice information; the operational pack must also explain the service performed.

Accounts should be able to see what is ready for billing and what needs commercial review. A completed route should not force an unresolved quantity dispute into a misleading invoice description.

HauliK supports multi-stop job dispatch and delivery evidence. Bring a partial delivery example to a demo and check stop mapping, PDF quantity labels and notes. Confirm which fields capture your quantities and exceptions instead of assuming a generic POD form is a full stock reconciliation system.