Lot / Batch Traceability Lookup

The problem this kills

When a supplier flags a bad ingredient or a lab result comes back out of spec, the clock starts immediately. Somewhere in your spreadsheets is the answer to "which finished products used that lot, where did they ship, and which customers have them?" - but pulling it together by hand means chasing batch records, cross-referencing production logs, and squinting at shipment exports while the regulator, the retailer, and your CEO all want a number now.

That manual scramble is slow, error-prone, and terrifying. Miss one blended lot and your recall is too narrow (a safety and legal disaster). Over-scope it and you pull product you didn't have to (expensive and reputation-denting). Either way, you can't confidently answer "what's the extent?" for hours or days.

This tool turns that scramble into a lookup. Type the suspect lot, get the full forward-and-backward trace, and put a human approval gate between the trace and any action.

What you'll build

A private, login-protected web app for your quality and supply-chain team that:

• Takes a suspect input - a single lot/batch number, or a date range, ingredient, or component criteria.
• Traces forward (one-down and beyond): suspect component lot -> finished lots that consumed it -> shipments -> customers, with quantities and locations at each hop.
• Traces backward (one-up and beyond): a suspect finished lot -> the component lots and suppliers that went into it.
• Handles the messy reality: partial lots, reworked and blended lots, multiple components per finished lot, and split shipments.
• Produces a clean affected list - products, shipments, and customers - deduplicated on lot + shipment line so nothing is double-counted.
• Routes that list through a human approval gate: your quality manager reviews and approves the scope before it's used.
• Emails the approved scope to your recall team via Resend and exports an affected-list CSV in the exact columns your recall-execution tool or process expects.

What's inside the Implementation Plan

• It starts by interviewing you about your business. Before writing a line of code, the plan has the AI agent ask you how your traceability actually works today - your lot and SKU naming conventions, how component lots map to finished lots, how blended and reworked lots are recorded, your shipment and customer data shape, your volumes, and your real edge cases. It reflects a short tailored spec back to you and waits for your thumbs-up. You get a tool built around your genealogy data, not a generic template.
• A step-by-step build, each step ending in a ready-to-paste prompt - no coding knowledge assumed.
• A data model for lot genealogy (component-to-finished links) and shipments that survives partial and blended lots.
• The forward/backward trace logic, with quantities and locations surfaced at every hop.
• The approval workflow, audit trail, email, and CSV export.
• A "No API yet?" fallback so you can build the whole thing today from a CSV or Google Sheet, with a clean CSV export back out.

The governance it includes (this is the point)

A recall scope is a high-stakes record, so this plan bakes in the controls from the start:

• Login so only your team can open the tool.
• Row-level security so each organization only ever sees its own genealogy and customer data.
• A complete audit trail - who ran which trace, what scope was produced, who approved it, and when.
• A hard human-in-the-loop approval gate - the agent drafts the affected list, your quality manager reviews and approves the extent of the trace, and only an approved scope can drive notifications, the email, or the export.
• Duplicate guards - dedupe on lot + shipment line so the same affected unit can't be counted (or actioned) twice.

Who it's for

Quality, regulatory, and supply-chain teams who need rapid one-up / one-down traceability for recalls, mock recalls, and investigations - in food, beverage, pharma, medical device, cosmetics, automotive, or any manufacturer who has to be able to answer "where did it go and where did it come from?" fast and defensibly.

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