Inbound PO-to-Backorder Matcher

The problem this kills

A container clears the dock. Three pallets of the SKU forty customers have been waiting on are now sitting in the rack. And they keep sitting - because matching that received quantity to the right open backorders is a manual, error-prone slog across a receiving sheet, an open-orders report, and somebody's memory of who promised what.

So the stock ages in the warehouse while the orders age in the queue. The squeaky customer gets allocated first, not the one who's waited longest. Two CSRs both grab from the same lot. And nobody can later explain why this order shipped and that one didn't.

This tool turns that scramble into a calm, auditable five-minute routine: receive, match, review, approve, release.

What you'll build

A small, secure web app your team logs into. Receiving uploads (or pastes) the inbound receipt. The tool reads the received quantities, finds every open backorder for those SKUs, and proposes a release plan - allocating the arrived units by FIFO (oldest backorder first) or by priority (a rule you define, like customer tier or promised-ship date), whichever your business uses.

A planner sees the proposed plan side by side with what's actually on hand, adjusts if needed, and approves. Only then does the tool commit the release: it produces a clean release/pick list and drafts a "good news, your order is shipping" notice for each affected customer. Nothing is released until a human says go.

What's inside the Implementation Plan

• It interviews you first. Before writing a line of code, the plan has the AI agent ask you about your receiving and allocation process - your SKU and order-number conventions, where your receipts and backorders live, your typical and peak inbound volumes, and your exact allocation rules. It reflects a short spec back to you for a thumbs-up, so you get a tool tailored to your warehouse, not a generic template.
• A step-by-step build you paste into Claude Code one prompt at a time.
• The full data model for receipts, backorder lines, proposed allocations, and approved releases.
• FIFO and priority allocation logic, with partial-fill handling when the received quantity can't cover everyone.
• The planner review-and-approve screen with a human approval gate.
• Customer release notices via Resend.
• The "No API yet?" fallback: run the whole thing from Google Sheet / CSV exports and produce a clean CSV release list in the exact columns your system of record expects.

The governance it includes (this is the point)

• Login so only your team can open the tool.
• Row-level security so each organization only ever sees its own receipts and orders.
• A complete audit trail - who matched, who approved, who released, and exactly when.
• A hard human-in-the-loop approval gate - the AI drafts the release plan, a planner reviews and approves, and only then is anything committed.
• Duplicate guards - a backorder line can't be double-allocated, and the same receipt can't be processed twice.

Who it's for

Supply/demand planners, receiving teams, and customer-service reps who manage backorders and want arriving stock to reach waiting customers in the right order, fast, without a spreadsheet circus - and without writing code.

You've got this. Paste the first prompt and let the agent interview you.