An order-status screen should answer the customer's next question: is the order accepted, what happens next, and do I need to do anything? A moving van illustration can look reassuring while conveying very little. For a small business, a clear set of meaningful milestones often provides more value than an elaborate tracking view that suggests precision the operation cannot supply.
Use milestones with business meaning
A custom-print shop might use Artwork received, Proof awaiting approval, In production and Ready for collection. Each status should reflect an event the business can reliably record. Explain what the customer needs to do when progress depends on them, and make the relevant action available from the status screen. Avoid a percentage-complete bar when the remaining work cannot be measured that way. A customer may interpret ninety per cent as almost ready, even if the final approval or delivery stage is the least predictable part.
Show freshness and uncertainty
If the screen is displaying previously saved information, identify when it was last updated. Android's offline-first architecture guidance discusses local and network data; the customer-facing decision is how to communicate their difference honestly. A cached Ready for collection state may be useful, while a cached driver position can be misleading. Choose wording suited to the evidence. An estimated arrival window is different from a confirmed appointment. When a milestone slips, state the current situation and any available next step rather than leaving an old optimistic message in place.
Connect status to service recovery
Customers need a route to ask about an unexpected delay, correct an address or provide a missing approval. Keep the order reference available for support. Test multiple orders with similar names, a partially fulfilled order and a cancelled item within a larger order. Decide whether the overview should show the whole order or separate fulfilment groups. Observe what customers ask after reading the screen; repeated questions reveal missing meaning. Judge the design by whether it helps customers plan their next action, not by how much time they spend watching the tracker.
- Which operational event makes each status true, and who records it?
- Does the screen distinguish an estimate from a confirmed commitment?
- Can customers see when the displayed information was last refreshed?
- What action is available when progress depends on the customer or has stalled?