How many packages did you order last month? Guess. Now check. You were wrong, weren't you?

Most people have no idea what's supposed to show up at their door. That's a problem the day one goes missing. You call the retailer, they ask for the order number, the tracking ID, the delivery date — and you're digging through three email accounts and two apps to find it.

Amazon, Shein, and DoorDash all keep this history. That's the point. Your buying habits are worth more than the shipping fee. Self-host your own delivery log and you hold the record instead.

Why a log beats your inbox

Your email already has the data. But it's scattered across confirmation emails, shipping notices, and marketing spam designed to bury the useful part. When a package vanishes, you need three things fast: what it was, when it was due, and the tracking number. A dedicated log puts all three on one screen.

It also does something your inbox can't: show you the pattern. "Three packages expected this week, one arrived." That gap is your early warning.

The 10-minute setup

You don't need a fancy app. Start with Grocy or a simple self-hosted spreadsheet like Grist or NocoDB, all of which run in one Docker container on any old machine.

Create a table with five columns:

  • Item — what you bought
  • Store — where from
  • Ordered — the date
  • Expected — the delivery estimate
  • Status — ordered, shipped, arrived, missing

Bookmark it. When you place an order, add a row. Takes 15 seconds. When a box lands on your porch, flip the status to "arrived."

Make it automatic (later)

Once you're comfortable, forward shipping emails to a self-hosted parser. Tools like n8n can read a confirmation email, pull the tracking number, and drop a new row into your table without you typing a thing. That's a weekend project, not a first-day one. Skip it until the manual version proves useful.

The privacy win

Delivery-tracking apps like Route or Shop ask for your email login or forward all your receipts to their servers. That's every purchase you make, handed to a company whose business is selling shopping data. Your self-hosted log sees the same information — but it never leaves your machine. No third party learns you bought a pregnancy test, a lawyer's book, or twelve energy drinks.

When it pays off

A package goes missing. You open your log, copy the order number and tracking ID, and file the claim in two minutes. The retailer sees an organized customer, not a confused one. Claims filed with exact details get approved faster.

Your one action today: spin up NocoDB in Docker, make the five-column table, and log the next thing you order. One row. That's the whole habit.