B2B Self-Service Reorder Portal
A login portal where your repeat B2B customers reorder from their own order history or your catalog at their contract pricing, then submit — with inside sales approving every order before it touches your ERP, so staff stop re-keying the same orders.
A live portal where a customer logs in, reorders from their history or your catalog at their own pricing, and submits a PO — inside sales reviews and approves it, and only then is a clean order record plus an ERP-ready CSV produced.
Before you start
- A free Supabase account
- A free Vercel account
- A free Resend account (for order notifications)
- A CSV of customer order history (who bought what, when)
- A product catalog CSV with your customer-specific / contract pricing
The problem this kills
Your best B2B customers order the same things over and over — and every single time, someone on your team re-keys it. They email a PO, or call it in, or send a photo of last month's order with "same again plus two." Inside sales squints at it, hunts down the right contract price, types it into the ERP, and prays they didn't fat-finger a SKU or a quantity.
It's slow, it's error-prone, and it scales by hiring more people to type. Meanwhile your customers would happily serve themselves — if you gave them a clean way to do it that respected their pricing and their order history.
This plan kills the re-keying. The customer does the data entry (because they're reordering their own stuff), your team just approves, and the ERP gets a clean record every time.
What you'll build
A self-service reorder portal for your repeat B2B customers:
- Customers log in and see only their own account — their order history, their catalog, their pricing. Never anyone else's.
- They reorder in two clicks — "buy it again" straight from a past order, or add from the catalog at their contract price.
- They submit with their own PO number, and the order lands in a review queue.
- Inside sales reviews and approves every order before anything is committed. The portal drafts; a human decides.
- On approval, you get a clean order record and an ERP-ready CSV in exactly the columns your system expects — so even with no live ERP integration, this is fully usable on Monday.
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 paste prompts.
- It opens by interviewing you about your business. Before it builds anything, the plan makes the agent ask about your real order data, your SKU and pricing conventions, your approval rules, and your messy edge cases — then it tailors the data model and every later step to your answers. This is not a generic template you have to bend to fit; it's shaped around how you actually sell.
- A step-by-step build, each step ending in a ready-to-copy prompt.
- The full governance layer (logins, per-customer isolation, audit trail, the approval gate, duplicate guards) baked in from the start.
- A "No API yet?" fallback so you can launch from a Google Sheet / CSV today and wire up the live ERP later.
- A plain-language verification checklist so you know it actually works.
The governance it includes (this is the point)
This is not a toy. The plan builds in the controls that make a tool safe to put in front of customers and trust near your ERP:
- Login so only your real customers and your team can get in.
- Row-level security so each customer sees only their own history, catalog, and pricing — never another account's.
- A complete audit trail — who ordered what, who approved it, and exactly when.
- A hard human-in-the-loop approval gate — a portal order is only ever a draft until inside sales approves it. Nothing reaches the ERP without a person saying yes.
- Duplicate guards keyed on customer + customer PO number, so the same order can't sneak in twice.
Who it's for
- B2B customers who reorder regularly and want to serve themselves without a phone call.
- Inside sales who are tired of re-keying orders and want to spend their time on exceptions, not transcription.
- CSRs who field "same as last time" requests all day and want a faster, cleaner way to handle them.
You don't need to be a developer. If you can describe how your customers order today and answer a few questions about your data, the plan does the rest.
You've got this — paste the first prompt and let the interview tailor it to your business.