Shipment milestones in context
Make tracking milestones belong to the right package
Show which package owns each milestone and how the screen communicates delayed or unavailable estimates.
- ✓Milestones survive package changes
- ✓Old estimates look current
- ✓Empty event histories lack guidance
Tracking reports with package identity
Package-specific timeline evidence
Connect the selected package and visible events before and after switching.
Honest estimate wording
Ask the fulfillment owner to define uncertain-date feedback instead of implying a delivery guarantee.
Mixed-status follow-up checks
Give engineering a split-order scenario that exposes stale milestones.
Establish the package behind the timeline
An order tracking screen can show several shipments with different delivery estimates. In your product, prepare a synthetic split order with one dispatched package and another still being prepared. Capture the order heading, package selector, milestone list, and last-updated text. Record the expected display timezone and the test shipment states. A screenshot of a delivered badge does not establish that a carrier delivered anything; it only records what the interface reported.
Capture package switching and delays
Record opening the second package, expanding a milestone, and switching back to the first. Include a delayed state where an estimated date has passed in the test fixture. An example issue is Package two keeps package one's delivered milestone after switching tabs. Preserve the item labels and timeline in the same recording. Separate the stale milestone from wording about an uncertain delivery estimate, because those concerns need different product decisions.
Agree on the visible status contract
Upload supported screenshots or recordings to Retick, or use browser capture. Inspect AI candidate issues, edit mistaken shipment identities, reject carrier diagnoses, and annotate the milestone that persists across packages. Example acceptance criteria: switching packages updates the timeline and item summary together; completed milestones remain distinguishable from pending ones; and an unavailable estimate is labeled without presenting an old date as current. Have the fulfillment owner approve the meaning of each displayed status before exporting the task.
Check less tidy shipment histories
After implementation, manually repeat with one package, duplicate milestone dates, and a package that has no tracking events. Inspect expanded event text at a narrow viewport and verify that timezone labels remain readable. Confirm actual shipment events and carrier updates in your own operational systems. Retick does not contact carriers, monitor deliveries, or verify package location. Use fictional tracking references and omit customer addresses before recording; automatic redaction is not included in this workflow.
Download the reviewed findings for a manual file handoff, or export selected issues from the individual media item to a connected Trello board and list. Include the package-switching sequence so the developer tests the mixed-status condition rather than only a straightforward single-shipment timeline.
Review a tracking timeline transition
Capture the package selector and the milestone state it controls.