Trackline: every parcel, every carrier, one status.
An internal web app for a team that ships every day. It gathers the shipments of several carriers, polls their tracking APIs, and shows one normalized status and the full history of each parcel.
- Built with
- Nuxt · PostgreSQL · Drizzle · Better Auth
- Status
- In progress
Trackline on made-up data. Northgate Supply and the people in it are fictional.
How it works
Every parcel, followed for you.
Shipments come in from the shop, carriers are polled in the background, and the team only looks at what needs a human.
01One status for every carrier
Each carrier speaks its own language. Trackline turns their tracking events into one status, refreshed in the background.
02Incidents handled, not missed
An anomaly or a parcel that stops moving opens an incident, taken by one operator at a time and closed with a resolution note.
03Late parcels, paid back
Each carrier service has a delivery promise. When a parcel misses it, Trackline opens a case, prepares the refund claim with its evidence, and reminds the team every day until the deadline.
04Several companies, one tool
Each order is tied to the company that sold it. Lists filter by company, and alerts go to the people who cover it.
Promises
Built to be trusted with a team's parcels.
An internal tool still has to earn its place. Here is what Trackline guarantees to the people who use it.
One person per incident.
An incident has one owner at a time. Taking over a colleague's case is an explicit step, never an accident.
Nothing closes without a reason.
Closing an incident requires a resolution note, and there is no bulk close that would skip it.
Carrier keys stay locked.
Carrier credentials are encrypted at rest and never reach the browser.
Two-factor for everyone.
Every account confirms a code on an unknown device, with an authenticator app as an option.
Not there yet
- No tracking page or status e-mail for the end customer yet.
- Delivery promises are measured for domestic home delivery only, not pickup points or international.
- The no-movement threshold is the same for every carrier, so slower carriers raise false alarms.
- Carriers are polled one after another, which will need parallel calls as volumes grow.
- Notification e-mails are not retried when the mail server is down.