Customer Catalog with Contract Pricing: Show Every Buyer Their Real Price
Give each B2B customer a login where they see their own contract prices, add to a cart, and submit for sales approval — with pricing approving the price file and effective dates before anything goes live, and sales approving the order before it commits.
A web portal where each B2B customer logs in, browses your catalog at their own contract prices, adds items to a cart, and submits an order; pricing approves the contract price file and its effective dates before they go live, sales reviews and approves each submitted order, and the tool produces a clean order record plus a CSV export in the exact columns your order system expects.
Before you start
- A Supabase account (free)
- A Vercel account (free)
- A Resend account (free)
- A customer-specific price list (CSV or Google Sheet, with effective dates)
- Your product catalog (CSV or Sheet)
- Claude Code or any AI coding agent
The problem this kills
Your sales team negotiated contract pricing with each customer — but the customer can't see it. So they call to ask "what's my price on this?", they order off an old quote, they buy the wrong part because nothing tells them what they're entitled to, or they dispute the invoice after the fact because the price wasn't what they expected. Every one of those is a phone call, an email thread, a credit memo, or a strained relationship.
Meanwhile pricing keeps the real numbers in a spreadsheet with effective dates that nobody outside the building can see, and orders arrive by email in a dozen formats that someone has to re-key into your order system. The prices are right there. The customers just have no window into them, and you have no clean front door for the orders that come back.
You don't need a six-figure portal project or a developer to fix this. You can build the window yourself.
What you'll build
A private web portal where:
- Each B2B customer logs in and sees only their own contract prices — never another customer's.
- They browse your product catalog, see their negotiated price on every item, add to a cart, and submit an order with their PO number.
- Pricing uploads and approves the contract price file — including the effective dates — before any of it is exposed to customers. Future-dated prices stay hidden until they kick in; expired prices fall away automatically.
- Sales gets notified of every submitted order, reviews it, and approves it before it becomes a real order. Nothing commits without a human saying yes.
- Approved orders produce a clean order record and a CSV export in the exact columns your order system expects — so you can build and use this today even with no integration to your ERP.
What's inside the Implementation Plan
The plan is a single file you paste into an AI coding agent (Claude Code). It walks the agent through building the whole tool, and it opens by interviewing you about your business — your customers, your SKU and price-list conventions, your effective-date rules, your approval flow, your order volumes, and your messy edge cases — so the tool is tailored to how you actually sell, not a generic template. The agent reads a short spec back to you, you confirm it, and only then does it build.
Inside you'll find:
- A guided discovery interview the agent runs first, so the data model matches your real price lists and catalog.
- Step-by-step build instructions, each ending with a ready-to-paste prompt.
- The contract-price import with effective-date logic baked in.
- Customer login, the catalog-with-my-prices browsing screen, the cart, and the order-submission flow.
- The pricing approval gate and the sales approval gate.
- A verification checklist and the CSV-export fallback so it works without any API to your existing system.
The governance it includes (this is the point)
This isn't a toy. The plan builds in the controls your finance and sales leaders will ask about:
- Login so only your customers and your team can get in.
- Row-level security so every customer sees strictly their own pricing and orders — never another account's.
- A complete audit trail: who uploaded which price file, who approved it, who submitted which order, who approved it, and when.
- A hard human-in-the-loop approval gate twice over — pricing approves the price file and effective dates before exposure, and sales approves each order before it commits.
- Duplicate guards so the same price row (customer + SKU) can't be loaded twice and the same order (customer + PO) can't be submitted twice.
Who it's for
- B2B sales teams tired of fielding "what's my price?" calls and re-keying emailed orders.
- Pricing teams who want their contract prices shown exactly as negotiated, with effective dates honored, and approved before they go live.
- Operations / order management pros who want a clean, deduped front door for customer orders.
You don't have to be a developer. If you can fill out the interview honestly and paste prompts, you can build this in a weekend.
You've got this — paste the first prompt.