Tracking Number Reconciler

The problem this kills

A customer emails: "Where's my order?" You check the system. It says shipped. But there's no tracking number on it - and nobody noticed, because shipping marks orders shipped in one place and the carrier hands back tracking numbers in another, and the two lists never actually get compared.

Meanwhile the carrier export has tracking numbers that don't match anything you can find - orphans created by a re-print, a typo in the order reference, or a label voided and re-made. Both gaps are invisible until a customer or a chargeback finds them for you.

Reconciling the two lists by hand is the kind of tedious, error-prone work that quietly eats an afternoon a week and still misses things. This tool does the matching, shows you exactly what didn't line up, and won't let a fix go through until a human signs off.

What you'll build

A small, login-protected web app where your fulfillment and customer-service team:

• Imports the orders-marked-shipped list and the carrier tracking export (CSV today, API later).
• Lets the tool match orders to tracking numbers - including fuzzy matches on order and PO references, because real data is messy.
• Sees three clean buckets: matched, untracked orders (shipped, no tracking), and orphan tracking numbers (tracking with no order).
• Lets ops review each unmatched item and decide - assign the right tracking number, or mark it as an exception with a reason.
• Closes the run only after a person approves - producing a reconciled report and an exception queue for follow-up.

What's inside the Implementation Plan

The plan is a single file you paste into Claude Code (a free AI coding agent). It builds the whole tool step by step, and every step ends with a copy-paste prompt.

Crucially, the plan opens by interviewing you about your business - your shipping process, which systems and exports you use, exactly how your order numbers and PO references are formatted, your typical and peak daily volumes, and the weird edge cases that break naive matching. It reflects a short tailored spec back to you, you give a thumbs-up, and only then does it build. You get a tool shaped to your data, not a generic template you have to bend to fit.

The governance it includes (this is the point)

This isn't a throwaway script. The plan bakes in the controls that make a tool safe to actually use on real orders:

• Login so only your team can get in.
• Row-level security so each organization only ever sees its own orders and tracking.
• A complete audit trail - who matched what, who approved, and when.
• A human-in-the-loop approval gate - the tool drafts the matches and resolutions; a person reviews and approves before anything is committed and the run is closed.
• Duplicate guards - the same order-plus-tracking pair can't be reconciled twice, even if you re-import the same file.

Who it's for

Fulfillment ops and customer-service teams who live in shipping queues and carrier portals, ship from more than one place or carrier, and are tired of finding out about a missing tracking number from an angry customer. If you can use a spreadsheet, you can build and run this.

You've got this - paste the first prompt and let the interview tailor the rest.