A cross-functional bug and logistics tracker

The problem

When an ecommerce brand ships through third-party logistics partners, problems come from everywhere at once. A parcel is lost in transit, a package goes back to sender over a bad address, a product arrives with a faulty part, a firmware quirk confuses a customer. Spread across inboxes and chat threads, issues like these quietly sit unresolved, and nobody can see which ones keep coming back.

What I built

One shared Notion workspace where every issue gets logged the moment it’s reported and tracked until it’s closed. Each entry carries the same structure:

• Priority and status, so the team can see at a glance what’s urgent and what’s still in progress.
• Issue type, split into delivery, hardware, and software, because each one routes to a different owner.
• Context overview and notes, so whoever picks it up doesn’t have to ask what happened.
• Date reported and date resolved, which turn the tracker into a record of how long things actually take.
• Resolution notes, added once an issue closes, so the fix is documented for next time.
• A Recurring tag that flags problems showing up more than once.

Views for every question

The same data answers different questions depending on who’s looking. There are seven saved views: all issues, by issue type, active issues, critical and high priority, resolved, a chart of issues by type, and a board for moving issues through each status.

Why it matters

Nothing sits unresolved without someone being able to see it. And because every issue is tagged and dated, patterns surface on their own. When the same part keeps failing or the same carrier keeps losing parcels, the Recurring tag and the chart make it obvious, which turns a pile of tickets into a case for fixing the root cause.