Partial Receipt & Backorder Tracker
See, per PO line, how much you've actually received versus ordered, what's still on backorder, and the latest promised date for the balance — so buyers always know what's still coming and can close a line short only after it's reviewed and logged.
A web tool where you import PO lines and receipt records, and it computes received / remaining / % complete for every line, ages the backorder, and shows the supplier's latest promised date for the balance. Overdue backorders are highlighted, a buyer can flag a line to close short, an approver reviews and signs off, the line is marked complete, and you can export the open backorders as a clean CSV.
Before you start
- A Supabase account (free)
- A Vercel account (free)
- An open-PO-lines export and a goods-receipts export (CSV is fine)
- Claude Code or any AI coding agent
The problem this kills
You ordered 500. The dock received 300 last Tuesday and another 80 yesterday. So how many are still coming, and when? Your buyer can answer that — but only after digging through the PO, the receiving log, and a string of emails from the supplier promising "next week." Multiply that by a few hundred open lines across dozens of suppliers and the truth is simple: nobody actually knows the real outstanding balance until something runs out.
That is how partial deliveries quietly turn into stockouts. A line is "open" in the system but everyone assumes it's basically done. A backorder slips three weeks past its promised date and no one chases it because no one could see it was overdue. And when a buyer finally decides to accept the short and stop expecting the rest, that decision lives in their head — not in any record anyone can audit.
This is exactly the kind of running-balance, many-moving-parts tracking a small internal tool does far better than a spreadsheet — and you do not need to be a developer to build it.
What you'll build
A simple internal web tool for your buyers and planners. You import two files — your open PO lines (what was ordered) and your goods receipts (every partial delivery, with quantities and dates). The tool adds up all the receipts against each PO line and shows you, on one screen: ordered, received, remaining, and % complete for every line. It handles multiple partial receipts against the same line, ages each open backorder from its promised date, and highlights anything overdue so your buyers chase the right suppliers first.
When a buyer decides a line is effectively done — the supplier will never ship the last few, and it's not worth waiting — they flag it to close short. That doesn't just happen: an approver reviews the under-delivery, signs off, and only then is the line marked complete and removed from the open view. Every closure is logged. At any moment you can export the remaining open backorders as a clean CSV in the exact columns your system or your expediting list expects.
What's inside the Implementation Plan
The plan is a single file you paste into an AI coding agent. It opens by interviewing you about your business — how your POs and receipts are identified, how a receipt references the line it fulfills, where the supplier's promised date comes from, your typical and peak line volumes, who's allowed to close a line short, and your messiest edge cases (over-receipts, returns, unit-of-measure mismatches) — and then tailors the data model, the math, and every later step to your answers. This is a tool shaped around how you receive, not a generic template.
From there it walks the agent through the database, the two CSV imports with their duplicate guards, the received-versus-remaining engine, backorder aging and promised-date display, the buyer's close-short request, the approver's review-and-sign-off gate, and the open-backorder CSV export. Every step ends with a ready-to-copy prompt. Because the whole thing runs on CSV in and clean CSV out, you can build and use it this afternoon even with no live connection to your ERP.
The governance it includes (this is the point)
Closing a backorder short means telling the system you've given up on goods you ordered — so it's built like it matters: login so only your team can use it, row-level security so you only ever see your own organization's POs and receipts, and a complete audit trail of every import, close-short request, approval, and export — who did what, and when. The close-short is a request until an approver signs off — the hard human-in-the-loop gate before any line is marked complete. Duplicate guards on the PO line (for the running balance) and on the PO line plus delivery reference (for receipts) mean the same delivery can't be counted twice and a balance can't be double-tracked.
Who it's for
Buyers and planners juggling many partially-delivered POs who can't easily see what's still outstanding, which backorders are overdue, and what the supplier last promised. If you can explain how you tell a finished line from an open one, you can build this.
You've got this — open the plan, paste the first prompt, and let it interview you about how you receive.