DELIVERY HANDHELD ACCEPTANCE CHECKLIST
Purpose: trace a delivery action through local capture to confirmed server state.
Use: approved test route, disposable parcels/identifiers and test evidence.
This is a proposed test plan, not a carrier's operating procedure or EPCIS schema.

Reviewer / date / service owner:
Device / OS / application / back-end versions:
Permitted offline actions and required evidence for this service:
Access, retention and exception policies:
Targets for capture errors, pending events and upload delays:

For each test record input, expected state, device feedback, server history,
dispatch/customer view, actual evidence, pass/fail and issue owner.

[ ] Correct parcel and stop information loaded.
[ ] Wrong parcel/stop caught before confirmation.
[ ] Successful delivery and unsuccessful attempt remain distinct events.
[ ] Local save, submission and server confirmation are visibly distinct.
[ ] Pending work survives the approved application/device restart.
[ ] Reconnection uploads permitted pending work.
[ ] Lost acknowledgement causes retry of the same event identifier.
[ ] Retry creates no extra accepted delivery.
[ ] New legitimate attempt retains its own event identifier.
[ ] Original event time, server receipt time and time-zone context retained.
[ ] Clock uncertainty and missing location handled explicitly.
[ ] Evidence stays attached to the right parcel/event when tasks switch.
[ ] Evidence upload failure is visible and has a resolution route.
[ ] Device, server, dispatch and customer views reconcile.

ILLUSTRATIVE TEST (not a measurement of any carrier)
Event E-103: delivered 10:14 while offline.
Server first accepts E-103 at 10:22; acknowledgement is lost.
Device retries E-103 and receives confirmation.
Expected: one delivery event; original time 10:14; first receipt 10:22;
8-minute delay; retry causes no second delivery.
Assumption: consistent clocks and time-zone interpretation.

Record capture failures, accepted duplicates, evidence mismatches, pending-event
count and upload delays, including unusually long delays rather than only averages.
Perform vehicle-related handheld entry tests while safely stationary.
Final decision, unresolved issues, owners and retest dates:

Yenra guide and source context:
https://yenra.com/wireless-computers/
Prepared October 6, 2026. Recheck exact model/version documentation.