Store/Branch Replenishment Request Portal
Build an internal portal where stores and branches request stock from the central warehouse, the tool checks DC availability and suggested quantities, and every request routes to a coordinator for approval before a transfer is created - replacing the email-and-text scramble.
A store submits a replenishment request, the tool checks distribution-center availability and suggests quantities, a coordinator reviews and approves the fulfillment quantities, and the tool generates a transfer/pick list, exports a clean CSV, and emails a confirmation to the store.
Before you start
- A free Supabase account
- A free Vercel account
- A free Resend account
- A spreadsheet or CSV of DC on-hand stock and your store min/max (par) levels
The problem this kills
Right now, your stores and branches ask for stock the way people ask for anything in a hurry: a text to the warehouse, an email to a coordinator, a note scribbled on a packing slip, a phone call at 4:55 on a Friday. Nobody has the full picture. The distribution center (DC) gets the same SKU requested twice in one day by two people at the same store. Somebody asks for 200 of something the DC has 12 of. Requests get lost, double-fulfilled, or quietly ignored, and the store finds out only when the truck shows up half-empty.
The fix isn't a bigger ERP project. It's one small portal that turns the chaos into a clean, reviewed queue: stores submit structured requests, the tool instantly checks DC on-hand and suggests a sensible quantity, duplicate same-day asks get merged, and a real human at the DC approves the numbers before anything becomes a transfer.
What you'll build
A simple, login-protected web app with two sides:
- For store/branch staff: a clean request form (or quick CSV upload) where they enter what they need. The tool caps each line at the store's par/max, flags when the DC is short, and shows the suggested quantity so they aren't guessing.
- For the DC coordinator: a review queue that consolidates duplicate same-day requests, shows availability next to every line, and lets the coordinator adjust and approve the fulfillment quantities. Approval is the gate - nothing becomes a transfer until a person says yes. On approval, the tool generates a transfer/pick list, exports a CSV in your exact columns, and emails the store a confirmation.
What's inside the Implementation Plan
- It interviews you first. Before it builds anything, the plan has the AI agent interview you about your real process - your stores and SKUs, how your DC stock and par levels are named, your typical and peak request volumes, and your approval rules. It reads back a short tailored spec, you give a thumbs-up, and only then does it build. You get a tool shaped around your business, not a generic template you have to bend yourself into.
- A step-by-step build you complete by pasting prompts into an AI coding agent - no prior coding needed.
- The store request form with par/max caps and DC-shortage flags.
- The coordinator review queue with same-day consolidation and a hard approval gate.
- Transfer/pick generation, a clean CSV export, and a Resend confirmation email.
- A "No API yet?" fallback so you can run the whole thing today from a spreadsheet of DC stock and export an approved fulfillment CSV - no integration required.
The governance it includes (this is the point)
This isn't a free-for-all form. The plan builds in the controls that make a tool safe to trust:
- Login so only your team can use it.
- Row-level security so each store sees only its own requests, and the DC sees the whole queue.
- A complete audit trail - who requested what, who approved it, what they changed, and when.
- A hard human-in-the-loop approval gate - the tool drafts suggested quantities, a coordinator reviews and approves, and only then is a transfer written.
- Duplicate guards - requests are deduped on store + SKU + request day so the same need can't be processed twice.
Who it's for
Store managers and branch staff who are tired of begging for stock by text. DC distribution coordinators drowning in ad-hoc requests. Anyone running multi-location transfers who wants one reviewed queue instead of an inbox full of "can you send me..." messages.
You've got this - paste the first prompt and let the agent interview you.