Parcel Tracking & Delivery Exception Monitor

The problem this kills

Outbound shipments mostly behave - and then a handful don't. A parcel sits at a sort facility for five days. A delivery fails and nobody notices. Something quietly gets returned to sender while the customer is emailing you asking where their order is. By the time anyone spots it, the goodwill is gone and you're eating a reship or a refund on top.

Today that monitoring is a person scrolling through a carrier export, eyeballing statuses, and trying to remember which ones they already chased. Exceptions slip through. The same problem gets flagged twice. Resolved issues get re-alerted. And there's no clean record of who decided to reship versus refund versus file a carrier claim.

What you'll build

A small internal web app that turns your tracking export into a tidy exception queue:

• Import your shipped tracking numbers and their latest statuses from a CSV or Google Sheet - including the expected delivery date for each.
• Detect the shipments that need a human: stuck in transit, delivery failed, returned to sender, or past their expected date - using rules you define with the tool during setup.
• Recommend an action for each exception (reship, refund, carrier claim, customer outreach) based on your own decision rules.
• Gate every action behind a coordinator: nothing is executed or logged until a person reviews the exception and approves the recommended action.
• Alert the right people through Resend, and export a clean CSV exception/action log in the exact columns your downstream systems expect.

It avoids the classic traps too: it dedupes on tracking number plus status change, so the same problem isn't flagged twice, and it won't re-alert exceptions that have already been resolved.

What's inside the Implementation Plan

• A full, paste-it-in runbook written for a non-coder - you build the whole thing by pasting prompts into an AI coding agent (Claude Code).
• It opens by interviewing you about your business - your carriers, your statuses, your expected-date logic, your volumes, and your real decision rules - so the tool is tailored to how you actually ship, not a generic template. The agent reads a short spec back to you and waits for your thumbs-up before building anything.
• Step-by-step build instructions, each ending in a ready-to-copy prompt.
• A "No API yet?" fallback so you can build and use the whole thing today from a carrier export - no integration required.
• A verification checklist so you know it actually works.

The governance it includes (this is the point)

This isn't a script that quietly changes things behind your back. Governance is built in:

• Login so only your team can use the tool.
• Row-level security so people only ever see their own organization's shipments.
• A complete audit trail - who flagged it, who approved the action, what action, and when.
• A hard human-in-the-loop approval gate - the tool drafts the recommended action, a coordinator reviews and approves, and only then is anything committed or logged.
• Duplicate guards so the same tracking-status change can't be processed or alerted twice.

Who it's for

Customer service teams, logistics coordinators, and fulfillment leads who are responsible for outbound shipments and tired of finding out about delivery problems from the customer first. If you can fill in a spreadsheet, you can build this.

You've got this - paste the first prompt and let the agent interview you.