Track the shipment.
Explain the exception.
We designed the shipment overview to lead into the exception that changes its progress.
The route console and milestone strip provide context; the exception record explains why the next step needs attention.
Explore the work ↓- PROJECT TYPE
- Interface design & front-end development
- DOMAIN
- Shipment milestones and exceptions
- DESIGN FOCUS
- Explaining shipment exceptions and revised arrival plans
The arrival plan needs an owner.
We gave the revised arrival plan a separate page with owned actions. That makes the response inspectable instead of leaving a changed arrival time as an unexplained status update. The sequence is about understanding the interruption and coordinating the next action, using authored shipment records.
The pages we designed.
The build brings shipment overview, exception detail and arrival plan into one workspace.
Project scope.
We designed and built 3 pages for this self-initiated project, including the layouts, responsive behaviour and front-end interactions. The interface uses sample business records.
The screenshots show authored interface states. Live accounts, operational integrations and production transactions are outside this portfolio build.
The gallery shows our rendered pages with identifying details masked.
A closer look.
Page by page.
Start with the overview, then explore the details. These are screenshots of the original interface, with names, contact details and identifying information blurred for privacy.
3 views Select any view to exploreHave a similar project?
Let’s discuss the work.
Tell us what your customers or team need to do. We can help define the pages, records and interactions around that task.


