Customer Tracking Lookup Portal
A branded self-serve page where your customers type a PO or tracking number and see a clean status and ETA - so your CS team stops fielding "where's my order?" calls all day.
Customers enter a PO or tracking number and instantly see a sanitized status, ETA, and any CS-approved notes - and can subscribe to email updates. CS controls every field that's visible.
Before you start
- A shipment/status master keyed by order, PO, or tracking number (a spreadsheet is fine to start)
- Free Vercel, Supabase, and Resend accounts
- Claude Code installed on a Linux machine
The problem this kills
Your customer service team spends half its day answering the same question: "Where's my order?" Each call means tabbing into the carrier site, the ERP, and a tracking spreadsheet, then translating internal shorthand into something a customer can understand. Multiply that by every shipment in flight and you have people who were hired to solve real problems instead reading status lines aloud.
The fix is a page customers can use themselves. They type the number on their paperwork, they get a clean answer, and they can ask to be emailed when it changes. The phone stops ringing for the easy stuff.
What you'll build
A branded, customer-facing lookup page. A customer enters their PO, order, or tracking number and sees a sanitized status and ETA - only the fields you've approved for outside eyes. Internal notes, costs, and carrier margins stay hidden. CS can attach a manual note ("weather delay, rerouting through Memphis"), and that note only appears to the customer after a human approves it. Customers can subscribe to get an email whenever their shipment's status moves.
What's inside the Implementation Plan
The plan opens by interviewing you about your business - your current process, the systems and spreadsheets you track shipments in, the exact column names and number formats your data uses, your typical and peak shipment volumes, and your messy edge cases (split shipments, reused PO numbers, customs holds). It reflects a short spec back to you for a thumbs-up, then tailors the data model, the lookup logic, and every later step to your answers - not a generic template.
From there it walks you, prompt by prompt, through building the database, the customer lookup page, the CS approval screen for fields and notes, the subscribe-to-updates email flow, and a CSV import/export fallback so you can launch today even with no live connection to your system of record.
The governance it includes (this is the point)
- Login so only your team can reach the CS approval and admin screens.
- Row-level security so a customer can only ever see their own shipments - never anyone else's.
- A field whitelist - CS explicitly chooses which columns are customer-visible; everything else (internal notes, costs) is hidden by default.
- A human-in-the-loop gate - any manual status note is drafted, then reviewed and approved by a person before it publishes to the customer.
- A complete audit trail - who approved what, and when.
- Duplicate guards keyed on the order/tracking number so the same shipment can't be double-loaded.
Who it's for
Customer service leads and e-commerce / fulfillment operations who want customers to self-serve their own tracking. If you can describe how you track shipments today, you can build this - no prior coding required.
You've got this - paste the first prompt and let the agent interview you.