BOM Builder & Component Availability Checker

The problem this kills

You have kits to build and shelves full of components, but the question "how many can we actually build today?" takes someone an hour of squinting at spreadsheets - and the answer is stale by lunch. One missing washer caps a whole production run, and nobody spots it until the line stops. Shared components quietly get double-counted across kits, so the plan promises more than the parts can deliver.

So planning happens by gut. Purchasing chases the wrong shortages. A kit gets started, then halts halfway because the one constraining part ran out three units ago. Everyone "knows" the BOMs, but the math that ties on-hand to buildable quantity never gets done consistently.

What you'll build

A small, private web app for your team that does the kitting math the moment you ask:

• Store your bills of materials - which components and quantities go into each kit - with versions, so you always know which recipe was used.
• Import your component on-hand (CSV or Google Sheet - no integration needed).
• For every kit, it computes the buildable quantity from current on-hand and names the single limiting (short) component that caps the run.
• It handles multi-level / nested BOMs if you have sub-assemblies, and flags components shared across kits so the same part isn't promised twice.
• A planner reviews and approves the build plan before it's used to reserve components or trigger purchasing - nothing is official until a human signs off.
• It exports a clean component shortage list as CSV so purchasing knows exactly what to buy and how much.

What's inside the Implementation Plan

A complete, paste-and-go runbook for Claude Code. It's written for a non-coder: plain language, one step at a time, with a ready-to-copy prompt at the end of every step.

Most importantly, the plan opens by interviewing you about your operation - how your BOMs are structured, your part-number conventions, whether you run nested sub-assemblies, how you count on-hand, your typical and peak kit volumes, and your messy exceptions. It reflects a short tailored spec back to you for a thumbs-up, then builds the tool around your recipes and your rules instead of a generic template.

Inside you'll find: the discovery interview, the data model (kits, BOM lines, components, on-hand), the buildable-quantity and limiting-component math, multi-level BOM handling, the shared-component allocation logic, the planner approval gate, the CSV shortage export, and a verification checklist so you know it actually works.

The governance it includes (this is the point)

This isn't a throwaway script. It's an internal tool with the controls operations leadership expects:

• Login so only your team can open it.
• Row-level security so each organization only ever sees its own data.
• A full audit trail - who defined which BOM version, who imported on-hand, who approved which build plan, and when.
• A hard human-in-the-loop approval gate - the tool drafts the build plan and shortage list; a planner reviews and approves before any component is reserved or any purchase is triggered. The AI never commits on its own.
• Duplicate guards so the same kit-and-BOM-version can't be defined twice and the same on-hand import can't be processed twice.

Who it's for

Production and kitting planners, inventory control analysts, and purchasing teams who own assembly readiness - and who want a real tool this weekend, not another fragile spreadsheet.

You've got this. Open Claude Code and paste the first prompt.