Goods Receipt vs PO Checker
Match incoming material against the purchase order - item, quantity, and lot/cert - flag over/under shipments, wrong items, and missing paperwork, then approve before stock is added and the invoice is paid.
A private web tool where a receiver picks a PO, enters what physically arrived (item, qty, lot/cert), sees discrepancies flagged automatically, gets a buyer/lead to approve any over/short/substitute, and exports a clean goods-receipt CSV plus a put-away list.
Before you start
- A free Vercel account
- A free Supabase account
- A free Resend account
- Your open purchase orders as a CSV or Google Sheet (PO, item, quantity due)
The problem this kills
The truck shows up, the packing slip lands on the dock, and someone has to figure out - fast - whether what arrived actually matches what you ordered. Right quantity? Right item? Right lot and cert paperwork? In most shops this happens on a clipboard or a side spreadsheet, and the misses are expensive: an over-shipment you pay for, a short you don't notice until production stops, a substitute part nobody approved, or a lot number that never got captured for a part that legally needs one.
By the time the discrepancy surfaces, the stock is already counted in and the invoice is already in line to be paid. Now you're chasing the supplier, reversing a receipt, and explaining the variance. The fix is to catch it at the dock, before anything is posted.
What you'll build
A small, private web app for your receiving team. A clerk picks an open PO, enters what physically arrived, and the tool instantly compares it line-by-line against the order: matched, over, short, wrong item, or missing required lot/cert. Anything outside tolerance gets flagged. Nothing becomes an official receipt until the right person signs off - the receiver confirms the physical count, and a buyer or lead approves any discrepancy. Then you export a goods-receipt CSV (in the exact columns your system expects) and a put-away list for the floor.
It handles the real-world mess: partial receipts across multiple deliveries, over-receipt tolerance, required lot/cert capture only where the item demands it, and a duplicate guard so the same delivery line can't be received twice.
What's inside the Implementation Plan
The plan is a single file you paste into an AI coding agent (Claude Code), and it builds the tool with you step by step. It opens by interviewing you about your business - your receiving process, the systems and sheets you use today, your real field and item-code conventions, your tolerances and approval rules, and your messy exceptions - so the tool is tailored to how you actually receive, not a generic template. It reads a short spec back to you for a thumbs-up before writing a line of code. From there it walks through database, login, the receiving screen, the matching/flagging logic, the approval gate, and the exports - each step ending in a ready-to-paste prompt.
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 POs and receipts.
- A full audit trail - who received, who approved, what changed, and when.
- A hard human-in-the-loop approval gate - the tool drafts the receipt and flags discrepancies; a person confirms the count and a buyer/lead approves any variance before anything is posted or exported.
- Duplicate guards keyed on PO line + receipt instance, so the same delivery line can't be processed twice.
Who it's for
Receiving clerks and stockroom staff who log deliveries, and the buyers and leads who approve discrepancies. If you live between the loading dock and the ERP, this is for you. No coding background needed.
You've got this - paste the first prompt and let the agent interview you.