Seasonal Reorder Point Adjuster

The problem this kills

Every year the same thing happens. Demand spikes for the holidays, or summer, or back-to-school, and you find out you under-ordered when the shelves are bare. Then the season ends and you're sitting on stock you bought at peak levels because nobody dialed the numbers back down.

Most teams "handle" this by editing reorder points in a spreadsheet from memory, or by leaving them flat all year and eating the stockouts and the overstock. The seasonal logic lives in one planner's head. When they're on vacation, it doesn't happen. And when two people both bump the same SKU "to be safe," you've now double-counted the season and over-bought.

This tool turns that tribal knowledge into a repeatable, scheduled, auditable process.

What you'll build

A small web app your planning team logs into that:

• Loads your base reorder points and min/max levels from a CSV or Google Sheet.
• Loads your seasonal index (the multiplier for each category in each month or season window).
• Computes the adjusted reorder point and safety stock for each SKU, for each season window, with the effective dates the change should kick in.
• Shows a planner the proposed changes side by side with the current levels, so they can review and approve before anything is committed.
• Produces a scheduled change list and a clean level-update CSV in the exact columns your ERP or WMS expects, complete with effective dates.

It builds up before the rush and draws down after, on a schedule, instead of in a last-minute panic.

What's inside the Implementation Plan

The plan is a single file you paste into an AI coding agent (Claude Code), and it builds the tool with you step by step.

It opens by interviewing you about your business. This is the important part: before it writes a line of code, the plan has the agent ask you about your real categories, your SKU naming, your season windows, your peak and lull months, your typical and peak volumes, and your approval rules. It reads back a short tailored spec, you give it a thumbs-up, and only then does it build. You get a tool shaped around how you plan, not a generic template you have to bend to fit.

Inside you'll find:

• The full discovery interview (the questions the agent asks you first).
• The data model for base levels, the seasonal index, and the scheduled changes.
• The seasonal math, explained in plain language.
• The approval screen and the human gate.
• The duplicate guard that stops a season from being applied twice.
• The CSV export with effective dates, in your system's column names.
• A no-API fallback so you can build the whole thing today, even with no integration to your ERP.

The governance it includes (this is the point)

This isn't a loose spreadsheet macro. The plan bakes in the controls that make a tool safe to run on real inventory:

• Login so only your team can use it.
• Row-level security so each organization only ever sees its own data.
• A full audit trail of who proposed, approved, and exported every change, and when.
• A hard human-in-the-loop approval gate - the tool drafts the seasonal changes, a planner reviews and approves them (and the effective dates), and only then are they committed to the change list and the export.
• Duplicate guards keyed on SKU plus season window, so the same seasonal adjustment can never be stacked on twice.

Who it's for

Demand planners, category managers, and purchasing teams who manage reorder points across products that swing with the seasons - and who are tired of doing it from memory every year.

You don't need to be a developer. If you can describe how your team plans for a busy season, you can build this.

You've got this - paste the first prompt and let the interview tailor it to your business.