Inbound Damage & Discrepancy Claim Logger

The problem this kills

Freight shows up on the dock damaged or short. Your clerk is busy, the truck is leaving, and the carton gets shoved into a corner "to deal with later." By the time finance hears about it, the photos are gone, nobody noted the seal status, the carrier's claim window has closed - and you eat the loss.

Carriers and vendors win these disputes for one reason: you can't prove what arrived broken. The fix is not more meetings. The fix is capturing clean, time-stamped, photo-backed evidence at the exact moment of receipt, then routing it through a person who decides whether to file a claim.

What you'll build

A simple web app your dock team opens on a phone or tablet:

• A receiving clerk scans or types the PO / receipt reference, picks the carrier, records seal status, snaps photos right at the dock, and logs the damage type and quantity.
• Photos are stored safely and stamped with the time (and location where the device allows it).
• A claims coordinator sees every logged incident, reviews the evidence, and either sends it back for more detail or approves it.
• Only after approval does the tool generate a clean claim packet (PDF and CSV) and email it to the right carrier or vendor contact.

It's mobile-first, it works in a few taps, and it refuses to let the same damaged shipment be claimed twice.

What's inside the Implementation Plan

The plan is a single file you paste into Claude Code. It does the building for you, step by step.

It starts by interviewing you about your business. Before it writes a single line, the plan makes the AI agent ask you about how your dock actually works - your PO and receipt numbering, which carriers you use, what "damage" categories you track, your typical and peak inbound volumes, who is allowed to approve a claim, and your messy edge cases (mixed pallets, concealed damage found days later, partial shorts). It reads a short tailored spec back to you, you confirm it, and only then does it build. You get a tool shaped to your warehouse - not a generic template you have to fight.

Inside you'll find:

• A plain-language explanation of what you're building and why.
• The discovery interview that tailors the data model to your real fields and naming.
• The full stack setup (database, photo storage, login, email) with copy-paste prompts.
• The dock capture form, the coordinator review queue, the approval gate, and the claim-packet generator.
• A verification checklist so you know it actually works.
• A no-API fallback: even if you can't connect to your WMS or ERP today, the tool exports the claim packet as CSV/PDF and emails it - so it's fully usable right now.

The governance it includes (this is the point)

This isn't a toy form. Governance is built in from the start:

• Login so only your team can use it.
• Row-level security so each organization only ever sees its own incidents.
• A complete audit trail - who logged what, who reviewed it, who approved it, and when.
• A human-in-the-loop approval gate - the tool drafts the claim, but a coordinator must review and approve before any packet is generated or sent.
• Duplicate guards so the same PO + carton + photo set can't be turned into two claims.

That's the difference between a spreadsheet and a tool finance can trust.

Who it's for

• Receiving clerks and dock leads who catch the damage but never had a fast way to document it.
• Claims and finance coordinators who need real evidence to win carrier and vendor disputes.
• Warehouse and operations managers tired of writing off "unrecoverable" freight losses.

You don't need to be a developer. If you can describe how your dock works, you can build this.

You've got this - paste the first prompt.