RtK

Outbound registration that mirrors the receive wizard

Send is the outbound registration hop before WeLink document work: container number, guided photos, defect capture, then submit-and-next. Yard staff register the leave; other depot users attach docs in WeLink. Leaving early still warns.

Enter container number

Step one captures the outbound container ID.

1 / 8

Implementation narrative

Problem

Outbound handoff needs the same proof as inbound, or the depot loses the trail when a unit leaves the yard. Operators should not learn a second UI for send, and should not mix registration with the document-packing roles in WeLink.

Solution

Send opens with the container number, then the same exterior photo slots, retake/save review, defect checklist, and defect photo gallery. Completion offers submit-and-exit or submit-and-next. The incomplete-exit modal keeps the operator on the page when receive/send data is unfinished. Customs packages stay in the WeLink Mini-App.

Outcome
  • Enter container number: Step one captures the outbound container ID.
  • Capture required sides: Guided slots for door end and both long sides.
  • Review and retake: Full-frame review with retake and save actions.
  • Filled photo slot: One exterior photo filled with retake affordance.
  • Mark defects: Multi-select checklist before defect photos.
  • Photograph defects: Defect gallery with count before final submit.
  • Guard incomplete exit: Warning that leaving home discards unsaved send data.
  • Submit or continue: Completion offers submit-and-exit or submit-and-next.

User flow