Do not turn a partial collection into a new booking or a final total. Record what was confirmed on each attempt, calculate the remaining quantity once, and make the next decision explicit.
1. Keep one booking and add attempt records
A partial pickup begins with one important distinction: the booking still describes the intended collection, while each vehicle visit describes what happened at that attempt. Do not replace the original booked quantity with the quantity collected on the first visit. Do not create a second freight job merely because goods remain. Keep the booking identifier, collection location, original booked quantity, and chosen unit basis visible; then attach a separate attempt record for every collection event.
Use an explicit unit basis before comparing numbers. “Pieces” may mean cartons, pallets, crates, bundles, or another agreed handling unit. A count is only comparable when the booking, collection confirmation, and remaining calculation use the same stated basis. If the booking says “18 pallets” but the site confirms “36 cartons,” record both facts if useful, but do not subtract one from the other unless an authorised conversion basis is available and recorded. This is suggested internal practice, not a carrier requirement or universal industry standard.
2. Follow the field decision sequence
| Current finding | Suggested internal record action | Suggested next decision |
|---|---|---|
| Confirmed collected quantity is lower than the remaining quantity | Record this attempt and calculate the new remaining quantity on the same unit basis | Name an owner to decide whether another collection is appropriate |
| Confirmed collected quantity equals the remaining quantity | Record the attempt and show zero remaining quantity | Mark quantity reconciliation complete; retain the booking and attempt history |
| Reported quantity uses a different unit basis | Record both stated quantities without subtraction | Seek a recorded conversion basis or quantity clarification |
| Message says goods are ready but does not confirm collection | Record it as readiness information, not a collected quantity | Wait for a distinct attempt reference and quantity confirmation |
| Later message appears to repeat an earlier collection | Preserve both messages and compare references, time, unit, and confirmer | Treat it as unresolved until duplication or a separate attempt is clarified |
First, identify the original booking and read its quantity exactly as booked. Second, record the visit as an attempted pickup, including its own attempt reference, date or time, vehicle or driver identifier where available, and the unit basis used in the confirmation. Third, obtain or record the quantity actually confirmed as collected for that attempt. A driver statement, site count, collection note, or another available confirmation may support the record; do not label an unverified number as confirmed.
Fourth, compare the attempt quantity with the remaining quantity before that attempt, not automatically with the original booking. Fifth, calculate the new remaining quantity once: previous remaining minus confirmed collected quantity, using the same unit basis. Sixth, if the figures cannot be compared, mark the reconciliation unresolved rather than guessing. Seventh, record a next decision: hold for clarification, arrange another collection, or mark the booked quantity fully collected only when the record supports that conclusion.
The supplied FedEx material is a carrier-specific US example, not an operational rule for other carriers or services. It shows that a pickup process can provide a confirmation reference, and that an attempted-pickup outcome can distinguish whether packages were collected. It does not prescribe this worksheet, its fields, or a partial-pickup policy for your fleet.
3. Use a small reconciliation worksheet
An adaptable worksheet can keep the conversation factual. Suggested fields are: job identifier; original booked quantity and unit basis; attempt reference; attempt date or time; quantity confirmed collected on that attempt; evidence or confirmer; previous remaining quantity; new remaining quantity; discrepancy note; decision owner; and next action. Preserve an entered attempt even when a later correction is needed. Add a correction note or a later confirmation instead of silently overwriting the earlier record.
The worksheet is an original suggested internal practice. It is not attributable to FedEx, not a carrier requirement, not a universal industry standard, not a Malaysia service rule, and not a legal obligation. Its purpose is modest: help dispatch, the driver, and the collection site discuss the same numbers without treating an assumption as a completed collection.
4. Make the next decision visible
A partial pickup does not itself answer what should happen next. The remaining quantity may be ready for a later vehicle, may need confirmation, or may reveal that the booking basis was unclear. Give one person or role ownership of the next decision, and state the decision in plain words. Avoid vague updates such as “balance pending” without a unit, owner, or next action.
Use the table as a desk-side prompt. Each row is a suggested internal decision, not an instruction from a carrier. It helps the team distinguish a confirmed partial collection from a mismatch, duplicate message, or unconfirmed count.
5. Desk-side decision table
Read the current attempt against the remaining quantity immediately before that attempt. Retain the original booking even if the result needs clarification.
6. Fictional example / 虚构示例
Fictional example: Booking FP-204 lists 18 pallets for collection. The first attempt, A1, has a site-confirmed collection of 11 pallets. The dispatcher keeps FP-204 unchanged, records A1 separately, and records 7 pallets remaining. Later, a message says that “7 pallets are ready,” but does not show whether they were collected. That message is not entered as another collection. It becomes an unresolved readiness note until a later attempt has its own reference and quantity confirmation.
On the second attempt, A2, the site confirms collection of 7 pallets. The record compares A2 with the 7 pallets remaining before A2, records zero pallets remaining, and marks the quantity reconciliation complete. It does not add 11 and 7 again to a revised booking, and it does not erase A1. If A2 had instead confirmed 6 pallets, the worksheet would show 1 pallet remaining and name the decision owner for the next action. This fictional example is only an illustration; it is not a result, service promise, or carrier policy.
7. Close the quantity question without closing unrelated work
Before calling the quantity reconciliation complete, run this five-item check. Confirm that the original booking remains identifiable; every collection event has its own attempt reference; each compared number has the same explicit unit basis; the current remaining quantity has been calculated from confirmed prior events only; and any discrepancy has an owner and explicit next decision. These checks do not prove delivery, settle payment, establish loading capacity, or replace a delivery-proof process.
Reuse the existing AI conceptual fleet illustration labelled “Illustrative image: warehouse staff checking a packing document beside cartons and a parked freight truck.” It is illustrative only and does not evidence a collection, a count, a carrier method, or a completed outcome. The narrow differentiation of this guide is the control of collected-versus-remaining pieces across repeat pickup attempts, without overwriting booking history or counting a later collection twice.
- Five-item close check: original booking is retained and identifiable.
- Five-item close check: every visit has a distinct attempt reference.
- Five-item close check: all compared quantities use the same stated unit basis.
- Five-item close check: remaining quantity uses confirmed prior events only.
- Five-item close check: a discrepancy has a named owner and next decision.
Source: FedEx US: pickup notifications and attempted-pickup outcome
Try the decision with fictional records
The demonstration runs independently. It does not connect to customer data, real dispatches, payments or the original project backends.
Open the matching demoExplore the full workflow