In-Transit Inventory Tracker
Turn your open POs and shipments into a live expected-receipt forecast by SKU and warehouse, so planners stop stocking out and over-ordering when ETAs slip.
A private, team-only web tool that imports in-transit POs, builds an ETA timeline by SKU and warehouse, shows an expected-receipt forecast, lets a planner review and approve ETA changes before they hit planning, and fires low-stock alerts.
Before you start
- A free Supabase account
- A free Vercel account
- A free Resend account
- A list of your open POs/shipments (a spreadsheet or CSV is fine)
The problem this kills
You order stock, the container is "on the way," and then the receiving forecast lives in someone's head and three spreadsheets. Ship dates slip. Ocean freight runs a different lead time than a ground truck. A shipment arrives in two partial loads. Meanwhile your planning system still assumes everything lands on the original date, so you either panic-order more (and over-stock) or you trust the dates and stock out.
The pain is that nobody has a single, trustworthy answer to "what is actually arriving, at which warehouse, and when?" Every ETA change ripples into a planning decision, but those changes are buried in carrier emails and forwarder portals nobody reconciles.
This tool fixes that by making in-transit inventory a first-class, shared, auditable view - and by putting a human in front of any ETA change that would move the forecast.
What you'll build
A private web app for your supply and purchasing team that:
- Imports your open POs and shipments (by API or by CSV/Google Sheet - no integration required).
- Builds an ETA timeline by SKU and warehouse so you can see exactly what is in transit and when each line is expected to land.
- Produces an expected-receipt forecast that respects ocean-vs-ground lead-time variance and partial shipments.
- Routes every ETA change to a planner who reviews and approves it before the forecast updates.
- Sends low-stock alerts when on-hand plus confirmed in-transit won't cover demand in time.
- Exports a clean CSV in the exact columns your planning/ERP system expects.
What's inside the Implementation Plan
- A copy-paste runbook you hand to an AI coding agent (Claude Code) that builds the whole thing with you, step by step.
- It opens by interviewing you about your business - your warehouses, your SKU and PO-line naming, your shipping modes and lead times, your partial-shipment habits, and your approval rules - then tailors the data model and every later step to your real operation instead of a generic template.
- The full data model, import logic, ETA-timeline and forecast math, the planner approval gate, the alerting, and the CSV fallback - each as a ready-to-paste prompt.
- A verification checklist so you know it actually works before you trust it.
The governance it includes (this is the point)
- Login so only your team can open the tool.
- Row-level security so people only ever see their own organization's data.
- A full audit trail - who imported what, who changed which ETA, and when.
- A human-in-the-loop approval gate: the system drafts the new forecast from an ETA change, a planner reviews it, and only an approval commits it to planning.
- Duplicate guards keyed on PO line + container number so the same shipment can't be imported or counted twice.
Who it's for
Supply planners, purchasing teams, and inventory managers who live and die by arrival dates - especially anyone juggling ocean and ground freight, multiple warehouses, and shipments that show up in pieces.
You've got this. Paste the first prompt and let the agent interview you - by the end of the weekend you'll have a forecast you can actually trust.