Spare Parts / MRO Inventory Tracker
Build an internal tool that tracks maintenance spare-parts (MRO) inventory by bin, logs usage against work orders, flags low critical spares, and exports a planner-approved reorder requisition - so a repair never stalls because the bearing was out of stock and nobody knew.
A logged-in storeroom tool where issuing a part to a work order updates on-hand, low critical spares get flagged, the maintenance planner approves reorder suggestions behind a human gate, and you export a usage log plus a reorder requisition CSV.
Before you start
- A spare-parts list (CSV or Google Sheet) with part, bin, on-hand, min/max, supplier, and which assets use each part
- Free accounts for Vercel, Supabase, and Resend
- Claude Code installed on your machine
The problem this kills
The press line goes down. The technician walks to the crib for the bearing - empty. Nobody flagged it because the spare-parts list lives in a spreadsheet that only gets opened when something's already on fire. Now you're paying overtime, expediting freight, and explaining the downtime in the morning meeting.
The real failures hide in the gaps: on-hand counts that drift away from reality because issues never get logged, critical single-source spares that quietly hit zero, reorder points nobody trusts, and "I thought we had three of those." When the storeroom and the work orders don't talk to each other, the parts you actually need are the ones you run out of.
What you'll build
A simple, login-protected web tool your maintenance team actually uses:
- A storeroom register of every spare part - by bin, with on-hand, min/max, supplier, and the assets each part fits.
- An "issue a part" screen: a technician records a part issued to a work order, and on-hand drops automatically.
- Automatic low-stock flagging, with critical and single-source spares called out loudly.
- A daily low-stock email so problems surface before the line is down.
- A human approval gate: the maintenance planner reviews suggested reorders and approves them before anything is committed.
- A clean export: a usage log and a reorder requisition CSV in the exact columns your purchasing system expects.
What's inside the Implementation Plan
The plan is a runbook you paste into an AI coding agent (Claude Code), which then builds the tool with you step by step - no coding experience required.
It opens by interviewing you about your business - your crib layout and bin naming, your part numbers, which assets use which spares, how work orders are numbered, your typical and peak issue volumes, and exactly which spares count as critical or single-source. It reads back a short tailored spec and waits for your thumbs-up, so the tool fits your storeroom, not a generic template.
From there it walks through every step - data model, import, the issue screen, low-stock logic, the planner approval gate, the daily email, and the CSV exports - each ending with a ready-to-paste prompt.
The governance it includes (this is the point)
This isn't a toy spreadsheet replacement - it's built with the controls a real storeroom needs:
- Login so only your team can touch inventory.
- Row-level security so each site or organization sees only its own parts and usage.
- A full audit trail - who issued what, to which work order, and when.
- A human-in-the-loop approval gate - the AI drafts reorder suggestions, the planner reviews and approves, and only then is a requisition committed and exported.
- Duplicate guards so the same issue can't be logged twice (dedupe key = part + bin + transaction).
Who it's for
Maintenance planners, storeroom and crib attendants, and technicians who keep production running - anyone tired of finding out a critical spare is gone only when they need it.
You've got this - paste the first prompt and let the agent build it with you.