Parts Issue to Work Order
Record every spare part pulled from the stockroom against a work order or asset, decrement stock the moment a storeroom lead approves the issue, and post the part cost to the job — so your repair costs are real and your on-hand count is finally accurate.
A web tool where a tech requests parts for a specific work order, the system checks stock availability, a storeroom lead approves the issue, and only then is stock decremented and the part cost posted to the work order. It blocks issuing more than you have on hand, handles returns to stock, rolls up true parts cost per work order and per asset, and exports a clean parts-usage ledger as CSV.
Before you start
- A Supabase account (free)
- A Vercel account (free)
- A parts inventory export with cost and on-hand quantity (CSV is fine)
- An open work-order list (CSV/sheet)
- Claude Code or any AI coding agent
The problem this kills
A tech walks up to the storeroom window, grabs two bearings and a contactor for the conveyor that just went down, and walks out. Maybe they scribble it on a clipboard. Maybe they don't. By the end of the week your on-hand count is fiction, the work order shows labor but no parts, and when finance asks what that repair actually cost, nobody can say. Worse, the next time someone needs that bearing it's not on the shelf — even though the system swears you have three.
The two failures feed each other. Stock drifts because issues aren't recorded, and repair costs are wrong because the parts that went into the job were never attributed to it. So you either stock out at the worst possible moment, or you carry a fortune in "ghost" inventory that's already been consumed. And every attempt to fix it with a shared spreadsheet falls apart the first time two people edit it at once, or someone issues four of a part you only had two of.
This is exactly the kind of small, rules-based, high-stakes tracking that a purpose-built internal tool does far better than a spreadsheet — and you do not need to be a developer to build it.
What you'll build
A simple internal web tool for your stockroom. You import two files — your parts inventory (each part with its cost and on-hand quantity) and your open work-order list. A tech opens the tool, picks the work order (or asset) they're fixing, searches for the parts they need, and requests a quantity. The tool checks availability in real time and won't let anyone request more than is on hand.
Each request lands in a queue for the storeroom lead. The lead reviews it — right work order, quantity actually available — and clicks Approve. Only then does the tool decrement stock and post the part cost to the work order. Returns to stock work the same way: a tech files a return, the lead confirms it, and stock goes back up. Behind the scenes the tool rolls up the true parts cost for every work order and every asset, and exports a clean parts-usage ledger as CSV — the exact columns your CMMS or accounting system expects.
What's inside the Implementation Plan
The plan is a single file you paste into an AI coding agent. It opens by interviewing you about your business — how techs request parts today, what your part numbers and work-order IDs actually look like, where cost comes from, your typical and peak volumes, who's allowed to approve, and your messiest edge cases (kits, cores, negative stock, emergency after-hours pulls) — and then tailors the data model, the validations, and every later step to your answers. This is a tool shaped around your stockroom, not a generic template.
From there it walks the agent through the database schema, the two CSV imports with their duplicate guards, the availability check, the request-and-approve flow, the stock-decrement-and-cost-posting on approval, returns to stock, the per-work-order and per-asset cost roll-up, and the parts-usage CSV export. Every step ends with a ready-to-copy prompt. Because the whole thing runs on CSV in and CSV out, you can build and use it this weekend even if you have no live connection to your CMMS or ERP.
The governance it includes (this is the point)
This changes both your stock count and your job costs, so it's built like it matters: login so only your maintenance team can use it, row-level security so you only ever see your own site's parts and work orders, and a complete audit trail of every request, approval, issue, and return — who did what, and when. Nothing moves stock automatically: a parts issue is a request until the storeroom lead approves it, and that approval is the hard human-in-the-loop gate before any quantity is decremented or any cost is posted. Returns need confirmation too. And duplicate guards on each issue transaction mean the same pull can't be processed twice — so your on-hand count and your repair costs both stay honest.
Who it's for
Maintenance storeroom keepers who are tired of a stock count that's always wrong, maintenance techs who want parts issued in seconds without paperwork, and facilities cost owners who need to know what a repair really cost. If you can explain how a part gets from the shelf to a job today, you can build this.
You've got this — open the plan, paste the first prompt, and let it interview you about your stockroom.