Each carrier has its own tracking format — UPS begins 1Z, USPS uses a twenty-digit number starting 94, Royal Mail ends with GB. A shipment tracking page that assumes one shape will fail on the rest.
What you can control
- Five carrier formats with their real prefixes and lengths.
- Status includes exceptions and label-created, the two states most tracking pages forget to design.
- Origin and destination are real city and region pairs, so a route map renders plausibly.
- Estimated delivery dates fall on both sides of today, which surfaces overdue-shipment logic.
Testing ideas
- Carrier detection. Paste a mixed batch into a single tracking field and check your app recognises each carrier from the format alone.
- Not-found state. These numbers have no shipment behind them, which is exactly what you need to design the "we can't find that parcel" screen.
- Whitespace. FedEx numbers are generated with spaces. Users paste them that way; your field should strip them.
- Statuses. Use the exception status to test delivery-problem banners and notifications.
What this is not
These match carrier formats but are not in any carrier's system. A tracking lookup will return no result — which is itself a case worth testing.