Panos Samiotis

Case Study

Eagle1 Whereis.

Every shipment is a line between two points. Whereis draws it.

Whereis tracking UI on mobile

The idea

“Where is it?” is the oldest question in shipping — and every carrier answers it in a different language.

Whereis is an open source product by Eagle1 Systems that gives the question one answer. It has two connected parts. Whereis API standardizes logistics data from multiple carriers into a single response model. Whereis UI presents that model as an elegant, readable tracking experience.

The result is a cleaner way to work with a problem that is usually messy: every carrier has different payloads, different naming, and different event semantics. Whereis makes that complexity feel predictable.

Chapter one is live. Chapter two — a ground‑up rewrite, from API to interface — is under way, and I’m leading it end to end.


The challenge

Carrier APIs are fragmented by design.

Developers integrating shipment tracking usually have to normalize different response formats, different status vocabularies, and different data quality rules for each provider. Even simple questions like “where is this package now?” often require carrier-specific logic.

Whereis tackles that by enforcing one predictable shape:

  • A consistent event timeline schema for all supported carriers.
  • Standard status codes so API consumers can reason about shipment states without provider-specific branching.
  • A simple tracking ID format (operatorCode-trackingNum) that keeps requests explicit and lightweight.

At this stage, the system supports FedEx (fdx) and SF Express (sfex), with the architecture designed to expand to additional operators.


Chapter one

The last mile

In shipping, the last mile is the hardest part of the journey. In data, it’s the interface.

The backend prototype is written in TypeScript on the Deno runtime and exposes clean endpoints for both full timelines /whereis/{id} and the latest known status /status/{id}. It is designed for local Docker deployment with a minimal setup flow.

A clean model still has to reach a person. That was the work I took on. The UI is built with Fresh 2.x and Tailwind CSS, and it focuses on making logistics data readable at a glance: latest status, key route points, chronological events, and raw JSON visibility for developer trust.

Most of that work is invisible. Which events collapse into one, and which deserve their own row. How a missing scan reads as a pause, not an error. Logistics data is not a list — it’s a story with gaps in it, and a good interface tells it honestly.

Machine‑consistent at the API layer. Human‑clear at the interface. Chapter one delivered the last mile and took it into production.


Chapter two

The whole route

The fastest way to understand a system is to be the first to depend on it.

Running real shipments through Whereis showed where the model was elegant in theory and awkward in practice — the kind of knowledge you only get from the receiving end.

The rewrite starts from there. One continuous line, from a carrier’s raw event to a sentence a customer understands — rebuilt from the ground up, and held end to end.

This page will follow it as it ships.


Two points. One line. Chapter one drew the last mile. Chapter two draws all of it.