GB · intl mail · carriers
Finlay Crawley
I work in international mail and e-commerce logistics — carrier operations, customs, and the systems around them.
A lot of the job is unglamorous. Tracking events that don’t match. A manifest that fails validation. A customs field someone left blank. A lane that quietly died on Tuesday.
I build small systems around that: one view of a shipment, an exception queue with an owner, checks that catch the obvious mistakes before they become delays.
Open lanes
Click a row. Keys 1–5 · / scan · esc
-
A watch on routes, countries, and carrier performance. The point is to notice a lane going wrong before it turns into a week of firefighting.
-
One place to see shipments across carriers. Raw scans get turned into milestones and exceptions, so the queue is “what needs a person,” not a pile of events.
-
Each carrier wants the file slightly differently. This sits in front of that: shape the data, validate it, then hand it off.
-
Rules for classification and declaration data. Fewer repetitive checks, and a trail for why a decision was made.
-
A working view of live failures and repeat patterns across lanes. Built for diagnosis, not a weekly slide.
Approach
I still write the boring parts myself — Python, APIs, whatever the carrier or customs process actually requires. When I’m standing up a new internal tool I use Codex and Claude Code to move faster. They don’t replace knowing which exception matters, or when not to automate.
If a screen doesn’t make the next action obvious, it isn’t finished.
Handoff
Email is best. Click it to copy.
[email protected]