Cycle Count Scheduler & Task Generator

The problem this kills

Full physical inventories shut the warehouse down, burn a weekend, and still leave you with numbers nobody trusts a month later. So most teams either skip counting or chase fires when a pick face comes up empty.

Cycle counting is the fix - count a slice of the warehouse every day so the whole place gets covered over time without stopping work. But doing it by hand means somebody maintains a fragile spreadsheet, guesses which SKUs are "due," forgets the fast movers, and double-counts the same bin twice in a week. The discipline falls apart, and stock accuracy drifts right back down.

This plan kills that. It builds you a tool that decides what to count today - automatically, by ABC cadence and last-counted date, with off-cycle counts triggered by red flags like negative balances - and hands your lead a clean, approve-and-go task list.

What you'll build

A small web app your inventory control team logs into that:

• Stores your item master, locations, and your own count-frequency rules (A items every N days, B every M, C every Q - your numbers).
• Generates today's count tasks by looking at ABC class, last-counted date, item velocity, and value - so the items most worth counting come up first.
• Triggers off-cycle counts automatically when something looks wrong (e.g. a negative on-hand balance).
• Routes the generated list to an inventory control lead for approval before anything goes out - they can drop items, add items, and assign counters.
• Produces printable count sheets and a CSV export in the exact columns your WMS/ERP expects.
• Records counted dates when sheets come back, so tomorrow's list is smarter than today's.
• Keeps a full audit trail of who generated, approved, assigned, and closed every count.

What's inside the Implementation Plan

The plan is a single file you paste into an AI coding agent (Claude Code), which then builds the tool with you step by step. No prior coding needed.

Crucially, the plan opens by interviewing you about your warehouse - your ABC thresholds, how your SKUs and locations are named, your real count cadence, your peak-season volumes, and your messy exceptions (lot/serial items, staging bins, items in transit). It reflects a short tailored spec back to you and waits for your thumbs-up before it builds anything. You get a tool shaped to your operation, not a generic template you have to bend to fit.

Inside you'll find:

• The discovery interview and how the agent turns your answers into the data model and rules.
• A clean Supabase schema for items, locations, cadence rules, count tasks, and the audit log.
• The scheduling logic: ABC cadence + last-counted + velocity/value weighting + event triggers.
• The approval-and-assign screen for your lead.
• Printable count sheets and the CSV export path.
• A no-API fallback so you can build the whole thing today from a spreadsheet.

The governance it includes (this is the point)

This isn't a toy script - it's built like an internal tool should be:

• Login so only your team can use it.
• Row-level security so each organization only ever sees its own data.
• A human-in-the-loop approval gate - the tool drafts the day's count list, but nothing goes out until your inventory control lead reviews and approves it.
• Duplicate guards so the same SKU/location can't be scheduled twice for the same count date.
• A complete audit trail - who generated the list, who approved it, who counted, and when.

Who it's for

Inventory control analysts, cycle-count teams, and warehouse managers who want stock accuracy they can defend - without a full physical inventory and without waiting on IT to build them a tool.

You've got this. Open the Implementation Plan and paste the first prompt - the agent takes it from there.