Backorder Tracker & Restock Notifier: Stop Losing Backorders in the Cracks
Import your open backorders and your incoming stock / PO dates, let the tool match each waiting line to the supply that will cover it, then have a CSR approve a single batch that notifies the affected customers and releases the lines to fulfill — with partial fills handled cleanly.
A logged-in tool where you import open backorders and incoming stock, the tool matches each backordered line to the inbound supply and arrival date that will cover it, a CSR reviews and approves one batch, and only then does it email the affected customers a restock notice and produce a clean release-to-fulfill CSV — with partial fulfillment supported.
Before you start
- A Supabase account (free)
- A Vercel account (free)
- A Resend account (free)
- An open-backorders export (the waiting order lines) and an incoming-stock / PO-dates export (CSV is fine)
- Claude Code or any AI coding agent
The problem this kills
A backorder is a promise you made and then stopped looking at. The order comes in, the item's out of stock, someone flags it "backorder" — and then it lives in a spreadsheet tab, an email thread, or a CSR's memory until the customer calls asking where their thing is. Stock lands at the dock, gets sold to the next walk-in order, and the person who's been waiting six weeks is still waiting, because nobody connected the new inventory back to the line it was promised to.
The day-to-day version of this is grim: a CSR exports open orders, eyeballs which ones are short, cross-checks a separate inbound/PO sheet to guess when stock arrives, and then — under pressure — hand-types release quantities and copies-and-pastes "good news, your order shipped!" emails one at a time. It's slow, it's easy to skip a line, and it's terrifyingly easy to notify a customer their item is back before the stock is actually allocated to them. Worse, run the report twice and you can release — or email — the same line twice.
Backorders aren't a memory problem, they're a tracking problem. Every waiting line should stay visible until it's filled, get matched to the supply that will cover it, and only get released and announced once a human says "yes, send it."
What you'll build
A simple internal web app for your CSR, fulfillment, and planning teams. You import your open backorders (every order line waiting on stock) and your incoming supply (on-hand that just landed, plus open POs with their expected arrival dates). The tool keeps every backordered line visible on one board and matches each line to the inbound stock and date that will cover it — fully or partially.
When stock is available, the tool drafts a release batch: which lines can ship now (and how much, because partial fulfillment is supported), which customers should get a "your item is back" restock notice, and which lines are still waiting and for how long. A CSR reviews the whole batch and approves it — and only then does the tool send the customer restock emails and produce a clean release-to-fulfill CSV for your warehouse or ERP. Nothing is announced or released until a person signs off, and the same order line can never be released twice.
What's inside the Implementation Plan
The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your business — how you track backorders today, where the open-backorder and incoming-stock data live, the real column names and the order-line ID in your exports, how you know when stock has truly landed vs. is still on a PO, your typical and peak backorder volumes, your exact rule for when a line is allowed to be released, whether you allow partial shipments, and the messy exceptions (cancelled lines, customer holds, an item that arrives short, two POs covering one line). It reads a short tailored spec back to you and waits for your thumbs-up before it builds anything, so the tracker matches how your business actually works — not a generic template.
From there it walks the agent through the data model, the backorder + inbound import with duplicate guards, the matching engine (line ↔ incoming stock and arrival date, with partial fills), the CSR review board, the human approval gate that sends notices and releases lines together, and the release-to-fulfill CSV export. Every step ends with a ready-to-copy prompt. There's a full "No API yet?" path that uses Google Sheet / CSV imports as the data source and produces a clean export in the exact columns your fulfillment system expects — so you can build and run the whole thing this afternoon, no matter what order system you're on.
The governance it includes (this is the point)
This tool emails your customers and releases orders to ship, so the controls aren't optional. The plan builds in login so only your team can use it, row-level security so you only ever see your own organization's orders and stock, a complete audit trail of who matched, who approved, and which customers were notified, a hard human-approval gate so no restock email is sent and no line is released until a CSR approves the batch, and duplicate guards keyed on the order line ID so the same backordered line can't be released — or its customer emailed — twice across re-runs.
Who it's for
Customer-service reps, fulfillment teams, and demand/supply planners — anyone who has to keep track of who's waiting on stock, figure out when it's arriving, and tell customers the good news without filling the wrong order first. If you can describe how a line gets flagged as a backorder and what has to be true before you'll release it, you can build this.
You've got this — start with the plan, paste the first prompt, and answer the interview. You'll have every backorder on one board with its restock date before the afternoon's out.