Wholesale catalog with live stock: what it takes

A wholesaler who copies a retail store usually ends up with a website their customers never use.

The reason is straightforward. In B2B the price is not public, the quantity is not chosen three at a time, and the order is rarely paid by card on the spot. It is a different process, and it needs a different tool.

This article covers what a working B2B catalog needs — and when you do not need one at all.

Catalog versus shop: what changes

Four differences that shape the entire project.

Price depends on who is looking. The same product has one price for a distributor, another for a regular account and another for a first-time buyer.

There is no cart, there is a request. The buyer assembles a list, submits it, and waits for confirmation of price, availability and lead time. Immediate purchase is the exception.

Quantities are large and come in multiples. Sold by case, by pallet or by minimum order quantity. A free-entry quantity field produces orders you cannot fulfil.

The buyer already knows you. They do not need persuading with large photography. They need to place a forty-line order in five minutes.

That last sentence is the whole objective: speed of ordering, not persuasion. Judge every design decision against it.

Customer-specific pricing

The part that is consistently underestimated at quoting stage.

Three levels are usually needed:

Customer groups. Distributor, regular, new account. Each with a discount off list price.

Individual terms. A negotiated price for a large account that does not follow the group rule.

Volume breaks. One price from a hundred units, another from a thousand.

These three combine, and that is where the problem starts. If a customer belongs to a group, has their own negotiated rate, and orders at volume — which price applies?

That rule has to be decided before anything is built. The usual answer is that individual pricing overrides group pricing, and volume breaks apply on top. But it is a commercial decision, not a technical one, and if nobody makes it in advance it gets discovered in production on a wrongly issued invoice.

A related decision worth making early: whether prices are visible before login at all. Many wholesalers show the catalog publicly but hide all pricing behind a login. That is good for confidentiality and bad for search visibility, since a search engine cannot see what a visitor cannot see. A common compromise is public product pages with descriptions and specifications, and pricing behind login.

Stock pulled from the accounting system

In wholesale, stale stock figures cost more than in retail, because the order is large and the buyer has already planned around it.

Stock must come from your accounting or inventory system, not be typed in. Two options:

Scheduled sync, every few hours. Cheap, stable and sufficient if turnover is slow.

Real time, necessary if you also sell through other channels or deal in scarce items.

There is a third approach that works particularly well in wholesale:

publish status rather than the exact number. «In stock», «Check lead time», «To order». It reduces the pressure on synchronisation and does not show a competitor exactly what you are holding — which is a genuine objection from many wholesalers.

If you list items that come from a supplier's warehouse, mark them separately. That stock is typically less current, and the buyer should know.

Request instead of cart

The core process, and it needs designing rather than assuming.

The chain: buyer builds a list → submits a request → someone checks stock and lead time → confirms or offers an alternative → issues a proforma or invoice → order goes to fulfilment.

Two places it commonly breaks.

A request nobody sees. It goes to a mailbox opened once a day. In wholesale a day's delay usually means the order went elsewhere.

No reservation. The request comes in, the goods stay available until confirmation, and someone else buys them. The reservation needs a time limit: if the request is not confirmed, stock returns to available.

One further detail that saves a great deal of email: let the buyer see the current status of their request without asking. «Received», «Confirmed», «Shipped» removes most of the follow-up traffic.

Client login for repeat buyers

This is what turns a catalog into something used daily rather than once a quarter.

The useful minimum:

• their pricing, already applied, without asking
• order history and a button to repeat a previous order
• current order status
• their documents: delivery notes and invoices, downloadable
• saved lists of products they buy regularly

The most-used feature in practice is «repeat last order». A customer buying the same items monthly does in thirty seconds what used to be a phone call and two emails.

Document download is the second: it quietly removes a volume of administrative work that nobody counts until it disappears.

Export to PDF and Excel

It will happen: the customer will ask for the price list as a file. Every time.

Worth solving properly rather than producing it manually on request.

PDF with that customer's pricing, dated, with a validity period. For sending and printing.

Excel with product codes and prices. Many buyers load it into their own system, and if you do not provide it they will retype it with errors that become your problem.

One detail that prevents disputes: put the date and validity period on the document. Without it, someone will return a year later holding an old price list.

Cost and timeline

Work	Price	Timeline
B2B catalog	from €1,500	4-8 weeks
Group and customer pricing	from €500	1-2 weeks
Client login area	from €700	2-3 weeks
Connection to inventory system	from €400	1-2 weeks
Price list export	from €250	3-5 days

Prices exclude VAT. Third-party licences are separate.

The real timeline depends almost entirely on catalog data. Duplicate codes or products listed under several names can add two weeks before development starts.

When a plain website is enough

The honest part.

You do not need a B2B catalog if you have fewer than thirty products, if every customer pays the same price, or if every sale involves a technical conversation first.

In those cases a well-built website with a downloadable price list and a request form does the same job for a fraction of the cost.

The signal that you do need one is different: when your team spends several hours a day answering emails about price, availability and order status that the customer could look up themselves.

Count those hours for one week before deciding. It is a more reliable indicator than product count or turnover.

Order of implementation

1. Clean up the catalog. One product, one code, consistent across

systems. Nothing else works without this.

1. Decide the pricing rules. Written down, including which rule

wins when they conflict.

1. Check the interfaces. What your inventory system can export and

how often.

1. Build the catalog and request process.
2. Add the client login area.
3. Add price list exports.

Steps one and two are not development work, and they are where projects succeed or fail. Both can be done before you engage anyone.

In summary

A B2B catalog is measured by how quickly a regular customer places an order, not by how it looks.

Decide the pricing rules before anything is built, pull stock from your inventory system, and put «repeat last order» in the login area from day one.

Tell us how many products you carry, how many price groups you have and what you use for inventory. If a website with a downloadable price list would serve you better, we will say so. Quote within one working day.