Customs paperwork scatters across chats and USB sticks. Clerks need the container ID, attached files, core shipment fields, and who changed what — on one phone screen at the yard.
One container card for files, fields, and audit trail
Each package opens a container card with the unit ID on a QR header, status line, files tab, data fields, and a history timeline of uploads, deletes, and status changes.
Open files tab
QR-backed container header with file list and count badge.
Implementation narrative
Header shows the container graphic, unit ID, QR, and status such as train-arrival notice sent. Files tab lists documents with download actions and a count badge; empty and loading states cover zero and in-flight loads. Data tab holds container number, package number, destination group, and dates. History logs file load/delete and status changes with user attribution. Exit and Create copy sit on the footer.
- Open files tab: QR-backed container header with file list and count badge.
- Files loading: Placeholder rows while the files tab loads.
- Read shipment data: Container ID, package ID, destination, and date fields.
- Audit history: Timeline of file deletes, loads, and status changes.
- No documents yet: Files tab empty state when the package has no uploads.