Incoming Inspection Logger: Catch Bad Lots Before They Hit Stock

The problem this kills

A truck backs up to the dock, the lot gets signed for, and now somebody in receiving QC has to decide: is this good enough to put into stock? To do it right they need the item's inspection plan — what characteristics to check, the spec and tolerance for each, and how many units to sample — then they have to actually measure, write it all down, and make a call: accept, reject, or quarantine.

In most warehouses that lives on a clipboard and a binder of inspection sheets, or a spreadsheet someone built years ago. So the sample size is guessed instead of pulled from an AQL rule (the standard way to decide how many to check based on lot size and how strict you're being). A characteristic gets skipped. A borderline reading gets waved through under dock pressure. A rejected lot quietly slips into stock because nobody flipped its status. And when the supplier or an auditor asks for the records six months later, they're a stack of paper nobody can search.

You don't need a six-figure quality module bolted onto your ERP to fix this. You can build the inspection logger yourself, this weekend.

What you'll build

An internal web tool your receiving-QC team logs into. You import two things you already have — your item inspection plans (per item: the characteristics to check, the spec/tolerance, the sample rule) and your receipt data (PO/lot, supplier, quantity). When a lot arrives, the inspector picks it, and the tool does the setup work: it computes the sample size from the item's AQL or sampling rule and lays out the exact checklist of characteristics to record. The inspector enters measurements and pass/fail attributes right on the screen.

Then the tool tallies the results against the plan and proposes a disposition — accept, reject, or quarantine — but it does not act on it. A QC inspector, or a QC lead for the borderline cases, reviews the evidence and approves the call. On accept, the lot is cleared. On reject, the lot goes to quarantine (never auto-released), a non-conformance record (NCR) is opened and linked, and a supplier-quality notice goes out by email. You click once to export the inspection records as a CSV in the exact format your QC system wants.

What's inside the Implementation Plan

The downloadable plan is a single markdown file you paste into an AI coding agent. It opens by interviewing you about your own receiving-inspection process — your item and characteristic naming, your SKU and lot conventions, which AQL tables or simple sample rules you use, your accept/reject/quarantine policy, who approves a borderline call, and your messiest edge cases (skip-lot, dock-to-stock suppliers, split lots) — and then it reads a short spec back for your thumbs-up before it builds anything. That's the difference between a tool shaped to your quality system and a generic template you have to fight.

From there it walks the agent through the data model (inspection plans and characteristics, receipts/lots, inspections, measurements, dispositions, NCRs), the importers, the duplicate guard on PO/lot + receipt, the sample-size and checklist engine, the measurement-capture screen, the review-and-approve disposition gate, the quarantine + NCR link, the supplier-quality email, and the final export. Every step ends with a ready-to-copy prompt. There's a full "No API yet?" path: import from CSV, export a clean inspection-records CSV in your QC layout, and you never have to touch your ERP's API to ship.

The governance it includes (this is the point)

This is quality control — the controls are the product, and an auditor will want to see them. The plan builds them in: a login so only your team can use it; row-level security so each site or organization only ever sees its own lots and plans; a complete audit trail of who inspected, who approved which disposition, and when; a hard human-approval gate so no lot is accepted, rejected, or released from quarantine until a person signs off; and duplicate guards (on PO/lot + receipt) so the same lot can't be inspected and dispositioned twice. A rejected lot physically goes to quarantine and links to an NCR — it can never auto-release into stock. That's the traceability story your quality manager and your ISO auditor want.

Who it's for

Receiving inspectors, incoming-QC technicians, and warehouse quality staff who check goods before they hit stock — plus the QC leads who own the borderline calls and the supplier-quality follow-up. If you can explain to a new hire how a lot gets sampled and what makes one worth rejecting, you can build this — no developer required.

You've got this — open the plan, paste the first prompt, answer a few questions about how your receiving inspection actually runs, and you'll watch your first lot get a sample size, a checklist, and a clean disposition.