When a manufacturer or distributor decides to “sell online”, the first idea is usually a shop: prices, a cart, a checkout. For many B2B businesses that is the wrong starting point. Prices are negotiated, quantities change from order to order, and buyers want to check specifications before they talk to sales. A cart can’t hold any of that. A well-built product catalogue website often can.
In practice there are three models: a catalogue that ends in a request for quote, trade prices behind a login, or a full B2B store. Here is how to choose, and what a strong catalogue needs either way.
The short answer
- Choose a catalogue with enquiry or request for quote when prices depend on quantity, specification or destination, and most orders start with a conversation. This fits most manufacturers and exporters.
- Add trade pricing behind a login when approved customers have known price lists and keep asking “what’s my price?”, but orders can still go through sales.
- Build a full B2B store when repeat customers order standard products at agreed prices often enough to justify linking the site to your stock and accounting systems, and you have people to run it.
In every model, the foundation is the same: clean product data, specification-rich product pages and an easy way to ask for a quote.
Online catalogue vs online store: the three models
1. A catalogue with enquiry or request for quote
Every product has its own page with specifications, photos and datasheets. Instead of “Add to cart”, buyers see “Add to quote list”, and their request reaches sales as a structured enquiry.
Suits made-to-order and configurable products, prices that move with volume, materials or freight terms, and buyers who are new to you. It is the natural fit for exporters, whose price depends on currency, destination and the agreed Incoterms rule (which costs and risks the seller takes on).
The trade-off. Buyers can’t serve themselves, so a request for quote website depends as much on how quickly sales reply as on its design.
2. A catalogue with trade prices behind a login
The catalogue stays public, so new buyers and search engines can see it. Approved trade customers log in to see their prices, stock availability, price lists or restricted documents, and still order through a quote list, email or a sales rep.
Suits distributors, wholesalers and brands with a dealer network, where each customer group has a known price and the common questions are “how much for me?” and “do you have it?”.
The trade-off. You now run accounts: approving applications, removing access when a buyer’s employee leaves, and keeping website prices in step with your ERP or price list. Out-of-date trade prices do more damage than none. And gate the prices, never the products: search engines don’t log in, and nor do buyers who haven’t met you yet.
3. A full B2B store
A B2B ecommerce website is much more than a consumer shop with a login. It usually needs customer-specific prices and quantity breaks, ordering on account with credit terms, purchase order numbers, quick ordering by product code, reorders from order history, several users per customer company and correct tax invoices. Some large buyers also expect punchout: they open your catalogue from their own procurement system, fill a cart, and send it back to that system for approval.
Suits frequent repeat orders for standard products such as consumables, spare parts and components, especially when customers already ask to order online.
The trade-off. It is the most expensive model to build and run, and most of the cost sits in integration. Prices, stock, customers and orders must stay in sync with your ERP and accounting systems, or the store shows the wrong prices and promises stock you don’t have.
| At a glance | Catalogue with enquiry | Catalogue with trade login | Full B2B store |
|---|---|---|---|
| Prices shown | None, or “from” prices | To approved accounts | Account-specific, at checkout |
| How orders happen | Quote request, then sales | Quote, email or rep, at known prices | Online, on account or by card |
| Best for | Variable pricing, new buyers | Price lists by customer group | Repeat orders of standard items |
| Systems involved | Email or CRM | Accounts and synced price lists | ERP, stock, accounting, shipping |
| Ongoing effort | Product updates, fast replies | Plus approvals and price updates | Plus orders, returns and support |
Five questions that decide it
1. Can you publish a price that’s right most of the time?
If the honest answer to “how much is it?” is “it depends”, a price on the page will usually be wrong, and a cart would force you to pick one anyway. That points to a catalogue with request for quote. Fixed price lists per customer group suggest a trade login. List prices with agreed account discounts make a store realistic.
2. How complex is a typical order?
A standard part in a standard quantity can go through a checkout. An order that needs a drawing, a sample or a technical check can’t, and a cart just creates orders someone has to unpick by phone.
Check it yourself. Take your last 20 orders and mark each one that could have been placed without a conversation. If only a handful qualify, a store would serve a small corner of your business.
3. Who is buying: new customers or repeat ones?
New buyers need evidence and a person to talk to. Repeat buyers want speed: the same product at the same price, with less email. Many businesses have both, hence the common pattern of a public catalogue plus a login for existing accounts.
4. What would it need to connect to?
List where your prices, stock, customer records and orders live today. If they sit in an ERP the website can’t read from, every figure on a store must be synced by hand or by a custom integration. Ask early whether your system offers an API or a reliable export: that answer can move the budget more than any design decision.
5. Who will run it every day?
A catalogue needs someone to keep products current and answer quotes fast. A trade portal adds approvals and price updates. A store adds orders, payment problems, returns and customer questions, and an understaffed store disappoints customers faster than any catalogue.
If your answers point different ways, start with the simplest model that serves your best customers today. A well-built catalogue can grow; a store launched too early is hard to take back.
What a strong product catalogue website needs
With or without a login, these parts separate a B2B product catalogue that brings in qualified enquiries from an online brochure.
Structured product data first
Before anything is designed, agree what you record for every product: code, name, category, applications, the specifications buyers select by, units, variants, certificates and files. Keep it in one source, such as a spreadsheet, a product information management (PIM) system or an ERP export, so the website isn’t the only place the truth lives. Clean data makes filters, comparison and translation possible, and it is what you will need to add trade pricing or ordering later.
Specification filters buyers actually use
Build filters from the attributes buyers search by, such as material, size, pressure rating, voltage or standard, not by your internal product groupings. Show how many results each option returns, avoid dead ends with zero results, and make filters comfortable on a phone. Filters can also generate thousands of near-identical URLs, so decide which filtered pages search engines should see; our guide to e-commerce SEO explains how.
Specifications on the page, datasheets to download
Put the key specifications in a real table on each product page, where people, search engines and AI assistants can read them, then offer datasheets, drawings and CAD files as labelled downloads. Our guide to B2B website design covers specification tables, certificates and why standard datasheets shouldn’t sit behind a form.
A quote list that sends clean enquiries
A single enquiry form works for one product. Buyers often need several, so give them a quote list: they add products, variants and quantities as they browse, then send one request. A good quote list:
Agree the fields with your sales team before design starts. Our guide to web form design covers what makes people finish a form, and tracking enquiries in GA4 shows how to measure them.
Pages in the languages your buyers use
A buyer searching in their own language won’t find a catalogue that exists only in yours. Each language needs its own URLs, translated descriptions, specification labels and filters, a translated quote form and routing to a sales contact who speaks that language. If you sell across borders, our guide to selling internationally online covers languages, currencies and delivery.
Product pages search engines can find
Give every product and category its own indexable page with a unique description, not a flipbook of the printed catalogue that is hard to search, read on a phone or link to. Describe each product with schema.org Product markup so search engines understand it, but don’t expect rich results by default. Google’s merchant listings are only for pages where people can buy, and its product snippets need a price or genuine reviews. Without either, a product can still rank as an ordinary result.
Choose a platform that leaves room to grow
The platform matters most if you might add trade pricing or ordering later. WordPress handles a catalogue well: products can be a custom content type, or WooCommerce products with the cart replaced by a quote request (usually through an extension), which keeps a route to online ordering open. Hosted store platforms are built around checkout and suit fixed-price products sold from day one. WordPress vs Wix vs Shopify compares ownership, languages and running costs, and the e-commerce website design guide explains what a full store involves.
Frequently asked questions
Is a product catalogue website cheaper than an online store?
Usually, yes. A catalogue has no checkout, payments, shipping rules or order management; the work is in product data, templates, filters and the quote list. In a B2B store, integration is often the biggest variable, so scope it before comparing quotes.
Should a B2B website show prices?
Show a price wherever you can publish an honest one, even a “from” price, because it saves both sides a call. Where you can’t, show what drives the price, such as minimum order quantity, lead time and options, and how quickly you quote, so “price on request” doesn’t read as “expensive”.
Can a catalogue without prices rank on Google?
Yes. B2B buyers often search by product type, specification or standard, and product and category pages that answer those searches in detail can rank without a price. What you give up is presentation: without a price or reviews, Google won’t show extras such as price or star ratings beside the result.
Can trade pricing or online ordering be added later?
Yes, if the product data is structured, the platform can support accounts or a store, and product URLs stay the same or are redirected one by one. Plan for it now, even if you only build the catalogue.
What to do next
Decide from how you actually sell, not from what consumer shops look like. For most B2B sellers, that means a product catalogue website with a quote list first, and trade pricing or online ordering once repeat customers ask for it.
If a catalogue fits, our website design and development service covers it on WordPress: structured product pages, specification filters, downloadable datasheets and a quote list that sends clean enquiries to your inbox or CRM, in the languages your buyers use. If you are leaning towards a trade portal or a full store, a dedicated commerce platform is usually the better route, and our WordPress, Wix and Shopify comparison sets out the options. Product data and a clear enquiry route come first in every model.