In-Transit Tracking & Receipt Reconciliation
Build an internal tool that tracks transfers while they're on the road and reconciles what shipped against what actually arrived — so shortages, damages, and lost-in-transit stop quietly vanishing from your books.
A logged-in app where you ship a transfer, mark it in-transit, count it at the destination, reconcile received vs shipped, capture a reason for every variance, get a receiving lead's approval, and export a clean receipt CSV plus a variance log.
Before you start
- A list of your shipped transfer orders (a CSV or Google Sheet is fine)
- Received counts from your destination locations
- Free accounts for Vercel, Supabase, and Resend (all have free tiers)
- No coding experience required — you'll paste prompts into Claude Code
The problem this kills
You ship 200 units from your main warehouse to a branch. Three weeks later the branch counts 188 on the dock. Where did twelve units go? Were they short-shipped, damaged on the truck, miscounted, or quietly stolen? In most operations nobody ever finds out — the receiving team just adjusts on-hand to whatever they counted, the transfer order gets closed, and the twelve missing units evaporate from the books with no reason attached and no one accountable.
Multiply that by every transfer between every location, every week. Those silent variances become real money: inflated shrink, surprise stockouts at the branch that "should" have inventory, and an in-transit balance that nobody trusts. When finance asks why the numbers don't tie out, all you have is a shrug.
The root problem is that stock in transit belongs to nobody. The moment it leaves the dock it's no longer in the source location's on-hand, and it isn't in the destination's on-hand until someone counts it. That gap is where variances hide.
What you'll build
A simple, logged-in web app that owns the whole transfer lifecycle:
- Ship — record a transfer order with the quantities that left the source location.
- In-transit — the moment it ships, those units move into an "owned by neither" in-transit bucket so they can't be double-counted at either end.
- Receive — the destination team enters the quantities they actually counted on the dock.
- Reconcile — the tool compares received against shipped, line by line, and flags every shortage, overage, and damage, requiring a reason on each one.
- Approve — a receiving lead reviews the reconciliation and the variances and gives the human thumbs-up. Only then does the destination on-hand finalize and the in-transit balance clear.
- Export — a clean receipt CSV and a variance log, in the exact columns your system of record expects.
What's inside the Implementation Plan
The plan is a single file you paste into Claude Code (a free AI coding assistant). It walks the AI through building the whole tool with you, step by step, each step ending in a ready-to-paste prompt.
Crucially, it opens by interviewing you about your business — your locations, how transfers move today, the exact field names and SKU conventions in your data, your typical and peak shipment volumes, who is allowed to approve a variance, and your messiest edge cases (partial receipts, split shipments, transfers that arrive in two trucks a week apart). It reflects a short tailored spec back to you and waits for your okay before building a single thing. The result fits how you actually run transfers — not a generic template.
Inside you'll find: the discovery interview, the data model, the in-transit bucket logic, the reconciliation and variance rules, the human approval gate, duplicate guards, and the CSV-export fallback so you can run the whole thing today even with no integration into your ERP.
The governance it includes (this is the point)
This isn't a throwaway spreadsheet macro. The plan builds in the controls that make a tool trustworthy enough to touch inventory numbers:
- Login so only your team can use it.
- Row-level security so each organization (and, if you want, each location) only ever sees its own transfers.
- A complete audit trail — who shipped, who counted, who approved, and exactly when.
- A hard human-in-the-loop approval gate — the tool drafts the reconciliation, but no destination on-hand is finalized and no in-transit balance clears until a receiving lead reviews and approves the variances.
- Duplicate guards — the same transfer order plus receipt can't be reconciled twice.
- Mandatory reason codes on every variance, so nothing changes the books without an explanation.
Who it's for
- Receiving teams at destination locations who count what arrives.
- Inventory control who need every variance reasoned and approved, not silently absorbed.
- Distribution and multi-location operators moving stock between warehouses, stores, or branches who are tired of in-transit being a black hole.
You don't need to be a developer. If you can describe how your transfers work and paste a prompt, you can build this.
You've got this — paste the first prompt and let the interview tailor the rest.