Shipment Status Board

The problem this kills

You have shipments moving with four different carriers, and every carrier calls the same thing something different. One says "OFD," another says "Out for Delivery," a third says "In Transit - Final Mile." A customer emails asking "where's my freight?" and your coordinator has to log into three portals, copy a PRO number, squint at a status, and translate it in their head. By the time they answer, the status has changed again.

Nobody has a single picture of what's actually in flight. Worse, a wrong "Delivered" status slips into your customer-facing system, a customer gets a "your order arrived!" note, and it didn't - now you're cleaning up trust, not freight.

This tool gives you one board. Every active shipment, every carrier, one normalized set of statuses, updated from the CSVs and status emails you already get - and a human gate so the dangerous transitions ("delivered," "exception") never go live until a coordinator says so.

What you'll build

A private, login-protected web app for your customer service and traffic coordinators:

• An import box that takes a carrier CSV export or a pasted status email and reads the updates out of it.
• Status normalization that maps each carrier's wording to your single, shared set of statuses (In Transit, Out for Delivery, Delivered, Exception, and whatever else you use).
• Automatic matching of each update to the right shipment in your shipment master by PRO / tracking number.
• A live board grouped by status, so anyone can see at a glance what's moving, what's stuck, and what's done.
• An exception queue for shipments the carriers flagged as a problem.
• A human approval gate: an update that would move a shipment to Delivered or Exception sits in a review list until a coordinator confirms it - only then do the customer-facing fields change.
• Email alerts to the right person when an exception lands or a confirmation is waiting.

What's inside the Implementation Plan

The plan is a single file you paste into Claude Code. The agent does the building; you answer questions and approve.

It opens by interviewing you about your business - your carriers, the exact column names in their exports, how your PRO/tracking numbers are formatted, your real status vocabulary, your peak-day volumes, and your messy edge cases (split shipments, reused tracking numbers, partial deliveries). It reads back a short tailored spec and waits for your thumbs-up before it builds anything. You get a tool shaped around how your freight actually moves - not a generic template.

After that, it walks you step by step: standing up the database, building the importer and the carrier status mapping, the matching logic, the board and exception queue, the approval gate, and the email alerts - each step ending in a ready-to-paste prompt.

The governance it includes (this is the point)

• Login so only your team can open the board.
• Row-level security so each organization only ever sees its own shipments.
• A full audit trail - who imported what, who confirmed which transition, and exactly when.
• A human-in-the-loop gate before any shipment goes to Delivered or Exception in customer-facing fields. The import drafts; a coordinator reviews and approves; only then does it commit.
• Duplicate guards keyed on PRO/tracking number + status timestamp, so the same update can't be processed twice no matter how many times the CSV gets re-pasted.

Who it's for

Customer service reps and traffic / dispatch coordinators who spend their day chasing freight status across carrier portals and answering "where is it?" - and the ops leads who want those status calls made consistently and the risky ones double-checked by a person.

You've got this. Make the folder, start Claude Code, and paste the first prompt.