Receipt must identify package, recipient and exception; confirming some packages must not automatically close the remaining delivery.
Index
A delivery confirmation can hide missing packages when its proof covers only the entire order.
The rule that changes the scope
Receipt must identify package, recipient and exception; confirming some packages must not automatically close the remaining delivery.
A standard delivery app can handle signatures; customization fits separate packages and checks shared across business locations.
The receipt design must let recipients understand their confirmation before submission. Showing only an accept button can create ambiguous evidence about packages that never arrived. Include packages with unreadable identifiers and define who corrects their association. A signature or confirmation records a human decision; the interface must not expand that decision to the remainder of the shipment merely because closing everything would be more convenient.
Specify operational deliverables
- Associate each package identifier with its shipment and expected destination list.
- Separate received, refused and not presented at the time of checking.
- Link the receipt record to the packages actually confirmed.
Test the exception before acceptance
In a hypothetical scenario, the recipient accepts part of a shipment and refuses a damaged box; the proof must show both outcomes and leave the remainder open.
Reference for assessing scope
NN/g: writing task scenarios for usability testing
Prepare your project with Quantum9
Bring a multi-package shipment and an example of a recorded delivery exception.