Product catalogue or online store: choosing the right website model
Showing products online and accepting online orders are different projects. One business may need technical details before quoting; another can sell a stocked product immediately. Before commissioning the website, look beyond product count and examine how the purchase decision is completed.
Work backwards from the final buying decision
Can price, dimensions, delivery coverage and options be confirmed without a conversation? If so, online ordering may be appropriate. If each job requires a survey, compatibility check or custom specification, a catalogue with an enquiry route may be a better first release.
For example, a standard accessory could go straight into a basket, while a made-to-measure cupboard may need a discussion about dimensions and materials. These are illustrative business models. One company can offer both; you do not need to force every product through the same buying process.
Design a catalogue as a complete experience
A catalogue website should explain the product and collect a relevant enquiry. Categories, specifications, dimensions, documents and quotation actions should serve that goal. When price follows a conversation, state beside the product what information the customer needs to supply.
Carry the product name or identifier into the enquiry form rather than asking the visitor to describe it again. Our Gerhman work provides a technical product presentation to examine. This is an example of digital presentation, not a claim about a client’s sales results.
Scope the operational side of ecommerce
A store needs more than a payment screen. Who updates stock, how are delivery options calculated, what happens after a failed payment and how are order statuses tracked? Resolve those responsibilities before comparing development proposals.
Model variants using actual product records. If a colour change affects the price, image or stock, the content system needs to represent that difference. “Unlimited products” does not remove the work of preparing accurate product information and keeping it current.
Make the first release small but complete
You do not have to add every product on the first day. Choose a representative category to test content entry, filtering and the enquiry or ordering journey. A page that accepts payment should not be presented as operational before the necessary process works.
Define the stages: product data model, sample products, user testing and expansion. Starting with a catalogue and adding checkout later may be possible. Planning identifiers, categories and editing needs early makes the work easier to scope, but it does not make the transition automatic or free.
Agree product addresses and measures of success
Google’s ecommerce documentation recommends understandable, consistent product URLs and warns about unnecessary alternative addresses for the same content. Stable product addresses are useful from the catalogue stage when planning future changes.
Measure relevant product enquiries for a catalogue, and verified orders and failed steps for a store. Write this decision note: “After finding this information, the customer should complete this action; this person on our team will manage it.” Continue with our product page guide or discuss the scope through our ecommerce service.
Frequently asked questions
Can a catalogue become an online store later?
It can be planned around a suitable product data model. Payments, stock, delivery and administration require additional work; the cost depends on the existing structure and new requirements.
Can a product website work without public prices?
It can be appropriate when pricing depends on a custom specification or technical discussion. Provide useful product information and explain the next step required for a quotation.