Truck Stock Par-Level Manager
Track every van's on-hand parts against its par levels, auto-build a restock pick list per truck, and require a coordinator's approval before it becomes a pick ticket - so techs start every day fully stocked.
A login-protected internal tool that compares each van's on-hand parts to its par levels, drafts a per-truck restock list (and flags overstock), holds it for a coordinator's approval, then turns it into a pick ticket and a clean CSV export.
Before you start
- A free Supabase account
- A free Vercel account
- A free Resend account
- A spreadsheet or CSV of your vans, par levels, current on-hand counts, and a parts catalog with SKUs
The problem this kills
Every morning your techs roll out, and half of them are missing the one part they need for the second job. So they detour back to the warehouse, or worse, drive to a supply house and pay retail. Meanwhile another van is sitting on six of a fitting it hasn't touched in months. Nobody can see the whole picture, because "the picture" lives in a coordinator's head and three different spreadsheets.
Par levels - the min/max each van should carry - are the fix, but only if someone reconciles them against what's actually on the truck, every cycle, without missing a van. Doing that by hand is slow, error-prone, and the first thing that gets skipped when it's busy.
What you'll build
A small, private web app your parts coordinator logs into. It knows each van's par levels (which differ by tech specialty), takes in current on-hand counts, and instantly shows you the below-par gaps for every truck. It drafts a suggested restock list per van that respects min/max, flags anything overstocked, and refuses to double-count the same (van + SKU) line. The coordinator reviews the draft, approves it, and only then does it become a pick ticket plus a CSV you can hand to the warehouse or import into your system of record.
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 approve what the agent proposes.
It opens by interviewing you about your business - your vans and how par levels vary by specialty, your SKU and naming conventions, your real restock cadence and volumes, your approval rules, and your messy edge cases (loaner trucks, kits, non-stock specials). It reflects a short tailored spec back to you for a thumbs-up, then shapes the data model and every later step around your answers - so you get a tool that fits your shop, not a generic template.
From there it walks you step by step: set up the database and login, load your pars/on-hand/catalog (CSV or sheet - no integration required), build the gap calculation, the per-van restock draft, the approval gate, the pick ticket, and the CSV export. Each step ends with a ready-to-copy prompt.
The governance it includes (this is the point)
- Login so only your team can open the tool.
- Row-level security so each organization only ever sees its own vans and parts.
- A full audit trail - who changed a par, who approved a restock, and exactly when.
- A human-in-the-loop approval gate - the tool drafts the restock; a coordinator reviews and approves before anything becomes a pick ticket or transfer.
- Duplicate guards so the same (van + SKU) line can't be processed twice.
Who it's for
Parts and inventory coordinators, warehouse leads, and field supervisors who own truck stock and are tired of morning fire drills. If you can fill in a spreadsheet, you can build and run this.
You've got this - paste the first prompt.