Your wholesale customers want to reorder, not browse.
Most wholesale buyers already know what they want. It's roughly what they ordered last month, sent over from a PDF price list by email. Build the portal for that before anything else.

A B2B ordering portal for wholesale customers should start with reordering, not a catalog. Let each buyer see their own prices and past orders, repeat an order with edits, order by SKU or by uploading a list, see stock and lead times they can plan around, and pay on the terms you've already agreed. Then connect each order to inventory and invoicing so nobody on your side retypes it.
Look at how orders arrive today
Ask a wholesale business how orders come in and the answer is rarely "through the website." It's an email with a spreadsheet attached. A PDF order form, filled in by hand and photographed. A text to the sales rep. A phone call on Thursday morning, every Thursday morning.
Someone on your side then types each one into the system that actually runs the business, checks the price against the customer's agreement, checks stock, and sends a confirmation. When it goes wrong, it's usually in that typing: the wrong pack size, last season's price, a line skipped.
Nobody designed this process. It grew one good customer at a time, and it works because a few people on your team know every account by heart. That's also why it gets fragile the week one of them is on leave, or the week a big customer doubles their order.
So when a team decides to build a wholesale portal, the temptation is to copy the retail store, with the same product pages, the same browsing, and the same cart. That's built for a customer who doesn't know what they want yet. Your wholesale buyer usually does.
Decision guide
Retail store vs. wholesale portal
| Consideration | Retail storefront | Wholesale portal |
|---|---|---|
| Starting point | Browse and discover. | Last order, saved lists, quick order by SKU. |
| Price | One public price, maybe a promotion. | This customer's price list, tiers, packs and minimums. |
| Payment | Card at checkout. | Agreed terms, invoices and credit limits. |
| Stock | In stock or not. | Quantities, lead times and partial-shipment choices. |
| Who orders | One person. | Several buyers per account, sometimes with approvals. |
Start from last month's order
The first screen a wholesale buyer should see after signing in is their own history. Last order, the one before that, and the items they buy most.
From there, the most useful buttons are plain ones:
- Reorder, which copies a past order into the cart for editing.
- Saved lists, for the standing order, the weekend top-up, and the seasonal one.
- Quick order by SKU, a simple grid where a buyer who knows the codes can type them with quantities.
- Upload a list, because many buyers keep their own spreadsheet and would rather not retype it either.
Browsing still matters for new products and occasional extras. It just isn't the main job. When a buyer does browse, it's often to answer a question for their own customers, such as ingredients, specifications or certifications. Put those details where they can find them, and let them download a spec sheet without calling their rep.
One detail makes reordering feel trustworthy: tell the buyer what changed since last time. If an item is discontinued, show the replacement you'd suggest. If a price moved, show the new one before they submit, not on the invoice. If a pack size changed, say so on the line. A reorder that quietly differs from the original is how disputes start.
A wholesale buyer's favorite page is last month's order with a button that says do it again.
Show their price, not the price
Wholesale pricing is personal. One customer has a negotiated price list, another gets volume tiers, a third buys only in full cases, and a fourth has a minimum order. A portal that shows a single list price, with a note that "your price will be confirmed," brings the email back.
The buyer should see their price, their pack sizes, and their minimums, right on the product and in the cart. They should see their payment terms, such as invoice on net terms or card, and their available credit if you set limits.
Account structure matters too. A restaurant group may have several locations, each with its own buyer, and one person who approves orders over a certain amount. That's worth modeling before launch, not discovering after. The same goes for delivery addresses, since a group with six kitchens has six of them, and for who receives the invoice, which is often not the person who placed the order.
And leave room for the things that still need a conversation. A buyer who wants a price on a new item, a bigger volume, or a special order should be able to ask from the portal, and get the answer in the same place, rather than starting a new email thread.
Tell them what they can plan around
A retail customer wants to know if something is in stock. A wholesale buyer wants to plan. Can I get forty cases by next Tuesday? If not, how many, and when's the rest?
That means showing available quantities, not just "in stock," along with lead times for made-to-order or back-ordered items, and a clear choice about partial shipments: send what's ready, or hold until it's all here. Whatever you show has to come from the same source your warehouse uses, or the portal will make promises your team has to break by phone.
Cutoff times belong here too. If orders in by 2 p.m. go out the same day, say so where the buyer is deciding, and show which delivery day an order placed now will actually get.
How the work moves
One reorder, end to end
- Buyer opens last month's order
Edits quantities, adds two items by SKU.
- Portal shows their terms
Their prices, packs, minimums and lead times.
- Order submitted on terms
Net terms or card, within the credit limit.
- Order lands ready to fulfill
In inventory and invoicing, with nothing retyped.
- Buyer and rep see the same status
Including any partial shipment.
Connect it before you decorate it
The portal is only worth building if the order arrives on your side ready to fulfill. That means it flows straight into whatever runs inventory and invoicing, with the right customer, prices and terms already attached, so nobody retypes it. Sales reps should see their customers' orders too, so they're still part of the relationship rather than cut out of it.
Don't expect every customer to switch on day one. Launch with a handful of accounts who order often, let their reps walk them through it, and fix what they trip on. For the customers who'll keep emailing spreadsheets for a while, consider reading those attachments into the same order queue, so your team at least works from one place.
Several commerce platforms now include B2B features such as company accounts, customer-specific catalogs and payment terms. Check how far they go for your business before building something custom. Often the right answer is a platform's B2B features plus custom work on the parts that are specific to you, such as the connection to your inventory and invoicing, the order rules and the approvals.
That combination of storefront, order rules and the systems behind them is our ecommerce work, with the portal itself built as a web application when a platform can't stretch far enough. If your orders still arrive as attachments, send us a typical week of them, and we'll show you what a reorder-first portal would look like for your buyers.
Related work: Spin:Market.
We build alongside the people doing the work.
Bring us the problem you’re thinking about.