De-Kit / Breakdown Tracker

The problem this kills

You bought (or built) finished kits, but now a customer wants just one part. So someone "breaks down" a kit at the rack and tries to fix the numbers by hand: knock one kit off the count, add its pieces back, hope nobody fat-fingers it. Multiply that by a busy week and your on-hand balances drift. Cycle counts stop matching the system. You oversell components you don't actually have, or you sit on kits the system swears are still whole.

The math itself is simple - it's the discipline that's hard. Every de-kit has to decrement the right finished kit, increment the exact components from that kit's bill of materials (BOM), account for anything damaged when you cracked the box open, and never let someone de-kit more kits than you actually have on the shelf. Do that consistently, with a record of who approved what, and the chaos disappears.

What you'll build

A small internal web app for your kitting and inventory-control team. You pick a finished kit and how many to break down. The app reads that kit's BOM, shows you exactly which component SKUs go up and by how much, lets you flag any components damaged during breakdown, and then holds the whole move for an inventory lead to approve. Nothing touches your balances until a human says yes. When it's approved, the app writes the inventory moves (kits down, components up), logs every detail, and gives you a clean CSV in the exact column layout your system of record expects.

What's inside the Implementation Plan

The plan is a complete, paste-and-go runbook for an AI coding agent (Claude Code). You don't write code - you answer questions and copy prompts.

It opens by interviewing you about your actual business - your kits, your BOM format, your SKU naming, your volumes, your approval rules, and your messy edge cases - so the tool is tailored to how you work, not a generic template. The agent reads back a short spec, you give it a thumbs-up, and only then does it build.

From there you get step-by-step build instructions, each ending in a ready-to-copy prompt:

• A data model shaped around your kits, BOMs, and components.
• A de-kit screen with live BOM math and a damaged-component flag.
• A human approval gate before any balance is written.
• Guards that block de-kitting more than you have on hand, and stop the same transaction from being processed twice.
• A full audit trail and a CSV export in your system's exact columns.

The governance it includes (this is the point)

This isn't a toy spreadsheet macro. The plan bakes in the controls a real inventory operation needs:

• Login so only your team can use the tool.
• Row-level security so each organization only ever sees its own data.
• A human-in-the-loop approval gate - the app drafts the de-kit, an inventory lead reviews quantity and resulting component adds, and only an approval commits the move.
• A complete audit trail - who broke down what, how many, what got damaged, who approved, and when.
• Duplicate guards so the same de-kit transaction can't be committed twice.
• On-hand guards so you can never de-kit more kits than you actually have.

Who it's for

Inventory control specialists and kitting leads who are tired of hand-patching stock counts every time a customer wants a single part - and who want a real, governed tool without hiring a developer.

You've got this. Make the folder, start Claude Code, and paste the first prompt.