Key Takeaways
- Choose the buying route around the decisions required to complete an order, rather than assuming every product needs an add-to-basket button.
- A catalogue can work well when specification, price or delivery needs a conversation. It still needs useful product information and a clear next step.
- An online shop needs reliable pricing, stock, payment, delivery and after-sales processes behind the checkout.
- A mixed approach can suit businesses with both standard products and bespoke orders, provided the difference is clear to customers.
- Test the full enquiry or order journey before investing in a large build, and keep product data organised so future changes remain practical.
A product catalogue website helps people understand and select products, then contact the business or request a quote. An online shop lets them complete a purchase through the website. Many e-commerce and retail websites need elements of both.
The right choice depends on how the sale works. A standard item with a known price and straightforward delivery may be suitable for checkout. A made-to-measure product requiring a site survey may need a carefully designed enquiry process first.
Adding online payment before the business can fulfil the resulting promise creates work for customers and staff. Equally, forcing somebody to telephone for a simple repeat order can create avoidable friction. Start with the buying decisions and work backwards to the website.
Follow One Realistic Purchase from Start to Finish
Pick a representative product and describe what must be known before the business can accept an order. Include quantity, dimensions, compatibility, finish, delivery location and any installation or account requirements.
Then identify who supplies each answer. The customer may know the colour they want but need advice on the correct fitting. Your team may need to check a supplier's lead time before confirming delivery.
Use an illustrative example: a retailer sells standard desk lamps and made-to-order lighting assemblies. The lamp may be ready for checkout. The assembly may require a drawing, compatibility check and confirmed quotation. Treating both products identically would make one of those journeys awkward.
Discuss those differences in an ecommerce development consultation before choosing software. The platform should support the agreed sales process, not decide the process because a theme happens to contain a cart icon.
When a Catalogue Website Is a Good Fit
A catalogue is worth considering when customers need product research but the final transaction depends on information that cannot yet be calculated reliably online. Examples include bespoke dimensions, project quantities or delivery that requires a site-specific arrangement.
It can also suit a business that sells through an existing account manager or distributor network. The website may help buyers shortlist products, download specifications and arrive at a more informed conversation.
The benefit depends on the quality of the enquiry route. A catalogue with poor information and a generic contact form may simply transfer extra work to the sales inbox. Customers should know why they need to enquire and what will happen next.
Ask whether a catalogue is the intended long-term model or a sensible first stage. A temporary approach can still be useful if it has clear ownership, a review point and a product data structure that will support later online ordering.
When an Online Shop Makes More Sense
Checkout is a stronger candidate when the customer can choose a valid product, see an accurate total and understand delivery without a separate conversation. The business must then be able to process and fulfil that order consistently.
Check the boring details early. Are stock figures dependable? Can the delivery rules handle the postcodes and quantities you accept? What happens if a payment succeeds but the order cannot be sent to the warehouse?
Assign responsibility for refunds, cancellations, failed payments and customer support. Buying an ecommerce platform does not decide those policies or provide staff to operate them. The website should communicate the process the business is prepared to honour.
Before choosing a platform, check how to compare Shopify and WordPress running costs against the work your team will do.
Review the applicable requirements in the GOV.UK online and distance selling guidance, including information customers need before ordering. Selling through enquiries or over the telephone does not automatically remove distance-selling responsibilities. Get advice appropriate to your products and customer type where needed.
A Quote Basket Can Bridge the Gap
A quote basket lets visitors collect several products or configurations before sending one enquiry. It can be more useful than asking them to copy product names into an email, especially when a project involves multiple items.
Keep the language clear. If the visitor is requesting a quotation rather than placing an order, every stage should say so. Avoid payment-style confirmation messages that imply the business has accepted a sale.
Carry the relevant product identifiers, selected options and quantities into the enquiry record. Let the buyer add context such as a project date or delivery location, but do not demand information that the sales team never uses.
Test how staff receive the request. A tidy front-end basket has limited value if the email loses the selected options or arrives in an unmonitored inbox. The responsible person needs enough information to respond without asking the customer to repeat everything.
Choose the Route Product by Product
You do not have to make one decision for the entire range. Standard accessories might be available to buy, while larger project items use a quote request. Samples might follow a separate process again.
| Product situation | Route worth testing | What must be clear |
|---|---|---|
| Standard item with reliable price and delivery | Online checkout | Total, availability and fulfilment terms |
| Product requiring specification advice | Catalogue enquiry | Information needed and expected response |
| Several items forming one project | Quote basket | Product options, quantities and project context |
| Approved trade account with repeat orders | Account-based ordering | Access, agreed pricing and order rules |
| Bespoke item requiring a survey | Consultation or survey request | What happens before a quote can be issued |
Make the difference visible on the product page. A customer should not discover at the final step that one item cannot be purchased with the others.
For trade customers, our guide to WooCommerce and Shopify for B2B pricing covers the separate questions around account rules and complex prices. A quote basket and a trade checkout solve different problems; do not assume one automatically replaces the other.
Give a Catalogue Proper Product Pages
A product catalogue should answer the questions that help someone choose. Depending on the product, that can include dimensions, materials, finishes, compatibility, drawings, installation requirements, care instructions and availability guidance.
Write the information where customers can use it. A PDF can provide a printable specification, but it should not be the only way to discover what a product is or whether it fits a need.
Organise the catalogue into useful categories and connect related products. Google's ecommerce site-structure guidance explains the importance of navigation and links in helping Google understand a site. Give visitors and search engines clear paths to individual product pages.
On Shopify, use keyword mapping for products and collections to plan which customer searches each page should answer.
Use accurate photographs and consistent product names. If something is available only on request, say so. If lead times vary, explain how to confirm them. A catalogue can reduce unnecessary questions only when the information is maintained and trusted.
Keep Search Markup True to the Buying Route
A catalogue can be discoverable in ordinary search without offering direct checkout. Do not confuse general search visibility with eligibility for particular shopping features.
Google's product structured-data guidance distinguishes product snippets from merchant listings and describes different requirements. Use the type appropriate to the page and its real purchasing experience. Valid markup does not guarantee that Google will show a rich result.
Never invent an offer price or stock status merely to satisfy a field. If the business cannot confirm the price until after a specification review, the visible page and structured information should reflect that reality.
An SEO service can review the catalogue's search structure alongside its buying journey. Keep the commercial goal clear: useful product discovery that leads to suitable enquiries or orders, rather than a larger number of thin product pages.
Measure Enquiries and Orders Differently
For a shop, track completed orders and the operational records that confirm them. For a catalogue, distinguish a product enquiry from a qualified opportunity and an accepted quote. These are separate stages, often separated by days or weeks.
Ask the sales team what happened to a sample of enquiries. Were the products suitable? Was the required information present? Did the customer receive a timely answer? A growing form-submission count can hide a poorly qualified or badly handled pipeline.
Our guide to website traffic without enquiries helps identify friction before the contact step. After that step, the business needs a process for ownership and follow-up.
Agree a small reporting routine that connects website activity with sales outcomes without pretending every system measures the same thing. Record known attribution gaps and avoid labelling every download as a sales lead.
Budget for the Work Behind Both Options
A catalogue usually avoids some checkout configuration, but it still needs product management, content, search, forms and ongoing support. A complex searchable catalogue can require more work than a small shop selling a handful of standard products.
When checking how much a website costs in the UK, compare total responsibilities rather than a page count. Include product data preparation, photography, imports, enquiry routing, training and future updates. For a shop, add the payment, tax, delivery and operational integrations required by the actual business.
Also compare staff time. A catalogue may create manual quotation work; a shop may need more effort maintaining prices and stock. Estimate the recurring tasks using a small trial rather than assuming automation removes them all.
Ask for a CMS development plan that makes routine product changes manageable. Someone in the business should know where the information lives, who approves it and how an outdated specification is corrected.
Start with a Small Working Journey
Before commissioning the full range, prototype one category and a few representative products. Include the simplest purchase and the awkward enquiry that currently takes several emails to resolve.
Test the customer-facing steps and the staff response together. Check that the right product details arrive, the next action is understood and nobody mistakes a request for a confirmed order.
One product and its usual route to a sale make a useful starting brief. Talk us through that journey, without sharing private customer details, and we can help define the first build and any later phases.
Frequently Asked Questions
What is the difference between a catalogue website and an online shop?
A catalogue helps customers research products and make an enquiry or quote request. An online shop supports a purchase through checkout. A business can combine both routes when different products require different buying decisions.
Can a catalogue website appear in Google search?
Yes, a catalogue can be discoverable when its pages are useful and accessible to search engines. Specific product-rich-result or shopping features have separate requirements. Use accurate content and appropriate markup without inventing prices or availability.
Is a catalogue website always cheaper to build?
No. A large catalogue with complex search, specifications, imports and quote workflows can require more work than a small straightforward shop. Compare product data, functionality, integrations and ongoing responsibilities rather than the presence of a checkout alone.
Can we add online payments to a catalogue later?
Often, but it needs planning. Keep product data structured and review pricing, stock, delivery, account rules and after-sales processes before adding checkout. Some catalogue designs or platforms may need changes to support the intended ordering experience.
Should a quote request use the same language as a purchase?
No. Make clear that the customer is requesting a quotation and explain the next step. Preserve the product options and quantities in the request, and avoid confirmation wording that implies an order or price has already been accepted.
