Shrinkage & Adjustment Summary
Build an internal tool that rolls up every inventory adjustment by reason, location, and dollar impact, trends your shrink rate, and emails a manager-approved monthly summary to leadership and loss prevention.
A login-protected app that imports adjustment transactions, normalizes messy reason codes, aggregates shrink by reason/location/dollar, trends the shrink rate, flags what's getting worse, and emails a manager-approved monthly summary plus a CSV to leadership and loss prevention.
Before you start
- A free Vercel account
- A free Supabase account
- A free Resend account
- A CSV or Google Sheet export of your adjustment transactions (reason code, location, cost)
The problem this kills
Every month someone in inventory control, finance, or loss prevention pulls a giant export of adjustment transactions and starts wrestling with it in a spreadsheet. Count variances, damage, scrap, theft, write-offs - all jumbled together, with reason codes that look like "DMG", "Damage", and "damaged-rcv" depending on who keyed them. You spend hours pivoting by reason, by location, by dollar impact, eyeballing whether shrink is creeping up at one site, and then hand-building a summary deck for leadership.
It's slow, it's error-prone, and by the time the report lands the month is already over. Worse, there's no record of who approved the numbers or what root-cause notes were attached.
What you'll build
A small, login-protected web app - just for your team - that takes your adjustment data and does the boring, high-stakes parts for you:
- Imports adjustment transactions from a CSV or Google Sheet (no integration required to start).
- Cleans up inconsistent reason codes by mapping them to a tidy standard set.
- Aggregates shrink by reason code, by location, and by dollar impact.
- Calculates and trends your shrink rate month over month.
- Flags locations and reasons that are trending up so nothing sneaks past you.
- Drafts a monthly shrinkage summary that a manager reviews, annotates with root-cause notes, and approves.
- On approval, emails the summary plus a clean CSV to leadership and loss prevention.
What's inside the Implementation Plan
The plan is a single markdown file you paste into an AI coding agent (Claude Code), which then builds the tool with you step by step. No prior coding needed.
It opens by interviewing you about your business - your current process, the systems and spreadsheets you use, the exact field names and reason-code conventions in your data, your typical and peak adjustment volumes, your approval rules, and your messy edge cases. 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. This is not a generic template - the tool fits how your warehouse actually works.
From there it walks through setup, the data import and reason-code normalization, the aggregation and shrink-rate trending, the trending-up flags, the manager review-and-approve screen, and the Resend email + CSV export. Every build step ends with a ready-to-copy prompt.
The governance it includes (this is the point)
This isn't a throwaway spreadsheet macro - it's a controlled internal tool, by design:
- Login so only your team can open it.
- Row-level security so people only ever see their own organization's data.
- A complete audit trail - who imported, who approved, and when.
- A human-in-the-loop approval gate: the AI drafts the summary, a manager reviews it and adds root-cause notes, and only then does anything go to leadership or loss prevention.
- Duplicate guards that dedupe on adjustment ID so the same transaction can't be counted twice.
Who it's for
Loss prevention teams, finance, and inventory control managers who own the monthly shrinkage number and are tired of rebuilding it by hand in a spreadsheet every period.
You've got this - paste the first prompt and let the agent interview you.