Role
Product Designer
Client
Atlas Shippers
Duration
4 months

PROBLEM
SOLUTION
DELIVERABLES
Where this started
In February 2025, I sent a box to my niece in the Philippines with Atlas. It took four months to arrive, and the tracker told me almost nothing along the way.
February. I dropped the box off at the Livermore facility.
No updates. No texts or status changes; I tracked it by calling customer service.
Early June. My niece finally received the box.
Atlas Shippers International ships door-to-door cargo from the United States to the Philippines. Most customers send balikbayan boxes: large boxes of goods packed for family back home. After pickup, a box moves from a US warehouse onto a container ship, across the Pacific, through customs at the Port of Manila, and out to a local delivery hub.
For the sender and the family waiting on the other end, the online tracker is the only view into that trip. I led the redesign of the tracking flow end to end, from auditing the current page to a working prototype, working alongside Richelle, co-owner of Atlas.
Families need a clear answer to the question they ask for weeks: where is my box, and when will it arrive?
Defining the problem
Auditing the live tracker at a 375px phone width, five problems emerged. The pins on the screen match each finding.

The problem: Senders and receivers who check on a box for weeks or months have no phone-friendly way to see where it is or when it will arrive, and no updates unless they call customer service.
The goal
Redesign the tracker into a mobile-first experience that answers that question at a glance, remembers each box between visits, and keeps both the sender and the receiver updated without a call to customer service.
I studied tracking screens on Mobbin, mostly from food and parcel delivery, where arrival is minutes away. A balikbayan box takes weeks, so I adapted each pattern instead of copying it.
I used Claude as a working tool on this project, for research, synthesis, and building the prototype. The problem framing, the flow, and what made the final design were my decisions, shaped by feedback from Richelle.
Answer first
Logistics systems log a dozen internal events. The status screen groups them into four stages and leads with a delivery window, such as “Oct 18 – 22.” Sea freight and customs can shift by days, so a window sets an honest expectation. The full event log sits underneath for people who want it.
The ocean is the map
The status screen opens on the ship’s route across the Pacific. It gives a long, uneventful wait a visible sense of progress.
An input that helps
The tracker opens straight to the invoice field, with an example format, a “Where do I find my invoice number?” helper and a scan button. When a number isn’t found, the error repeats what was typed and shows what a valid number looks like.


Boxes that stay
Every tracked box is saved to the home screen until it’s delivered. Step notifications and a share link keep the receiver in the Philippines informed too. This is the gap I ran into as a sender: in four months, I never got a text update.

Before and after
The same task in both versions: entering an invoice number on a phone.

Measuring success
I don’t have production metrics to share yet. These are the signals I’d track with the Atlas team:
What I’d do next
This project taught me to design for a long wait, where the most useful thing a tracker can do is set an honest expectation and keep people updated along the way.