Incoming Inspection Checklist & Pass/Fail
Build your own guided incoming-inspection tool with AI: walk inspectors through item-specific checklists, record pass/fail with photos, and route failures to quarantine before they hit the pick face.
A logged-in tool where an inspector picks a receipt, runs the item's checklist with photos, records pass/fail, and a quality lead approves the disposition before stock is released to sellable on-hand or held in quarantine - with a full audit trail and CSV export.
Before you start
- A free Supabase account
- A free Vercel account
- A free Resend account
- A spreadsheet or CSV of receipts to inspect (no API required to start)
The problem this kills
Defective product slips onto the shelf because incoming inspection lives in someone's head, a clipboard, or a battered spreadsheet. One inspector checks dimensions, another forgets to look at the labeling, a third waves through a "close enough" deviation without anyone signing off. By the time a customer complaint or a failed audit surfaces the problem, the bad stock is already in the pick face, picked, and shipped.
The pain is real and expensive: rework, returns, chargebacks, scrapped inventory, and a quality manager who can never prove what was actually checked. Paper checklists don't dedupe, don't attach photos to the right receipt, and don't stop a release until a human has reviewed a borderline pass.
What you'll build
A guided incoming-inspection web app that your receiving and QC team logs into. The inspector selects a receipt, the tool serves the right checklist for that item or category (dimensions, function, labeling, packaging), and walks them step by step. They record pass or fail on each line, snap photos (required on any fail), and submit the result. A quality lead then reviews the inspection - especially any "pass with deviation" - and approves the disposition. Only then does the item get released to sellable on-hand or routed to quarantine. Every action is timestamped and attributed, and you can export a clean CSV in exactly the columns your system of record expects.
What's inside the Implementation Plan
The plan is a single markdown file you paste into Claude Code. It opens by interviewing you about your business - your receiving flow, who inspects, the systems and spreadsheets you use, your real item/SKU naming, your checklist items per category, your typical and peak receipt volumes, your approval rules, and your messy edge cases - so the tool is tailored to how you actually work, not a generic template. The agent reads a short spec back to you and waits for your thumbs-up before building anything.
From there it walks you through the whole build in copy-paste steps: the database and security, login, the receipt picker, the dynamic per-item checklist, photo capture, the pass/fail recording, the quality-lead approval gate, the disposition routing, and the CSV import/export fallback so you can run it today with no integration at all.
The governance it includes (this is the point)
- Login so only your team can use the tool.
- Row-level security so people only ever see their own organization's data.
- A complete audit trail - who inspected, who approved, what disposition, and when.
- A hard human-in-the-loop approval gate: the inspector records the result, but a quality lead must review and approve the disposition before stock is released or quarantined.
- Duplicate guards so the same receipt + inspection can't be processed twice.
- Photos required on fail so every rejection is evidenced.
Who it's for
QC inspectors, receiving teams, and quality managers who want to stop defects at the dock - without waiting on IT, learning to code, or buying a heavy QMS platform.
You've got this - paste the first prompt and let the agent interview you.