A catalogue presents products and collects enquiries; an online store also manages transactions and order operations. Decide which workflow the business is ready to support. A small manufacturer can show materials, dimensions and minimum-order information, then request project details for a written quotation. Adding a payment button alone does not create a complete stock, shipping or returns operation.
Decide where the commercial decision actually happens
A product catalogue website helps buyers understand what you make and request a conversation or quotation. An online store completes more of the transaction: choosing a product, calculating an order and paying through a defined process. These are different operating models, not two visual styles for the same page. Choose based on how the business sells rather than assuming that every product photograph needs an add-to-cart button.
For example, a small manufacturer may produce variations that depend on dimensions, materials or order quantity. The buyer might need an agreed specification before any price is meaningful. A clear catalogue and a useful quote request can fit that workflow better than a cart that cannot represent the real order. Another business selling fixed, stocked items may need a different solution.
Write down the point at which the business can responsibly confirm availability, price and delivery. If that point is after a discussion, the website should not imply instant confirmation. This protects clarity for the customer and helps the project team avoid building a shallow checkout that leaves operational questions unresolved.
Prepare product information as a consistent catalogue
For each product family, gather a public name, short purpose, relevant properties, approved images and the information needed for a quotation. Use a consistent order so buyers can compare items. Technical details should be checked by the business; the website designer should not infer materials, tolerances or certifications from a photograph.
Separate publicly useful information from documents that need controlled sharing. A sample drawing may help explain a product, but confidential specifications or customer-specific files should not enter the public asset folder by accident. If downloadable sheets are provided, identify their version and owner so they can be updated with the corresponding product page.
A catalogue can remain simple without being vague. Group products logically, give detail pages meaningful descriptions and show a clear enquiry route. Avoid creating hundreds of nearly empty pages from minor naming differences. The objective is to help a buyer identify the right discussion, not inflate the page count.
Scope transaction features as additional responsibilities
A store needs more than a payment button. It may require stock handling, delivery rules, order states, customer communication and a process for correcting errors. External payment and fulfilment services also introduce accounts, fees and configuration that somebody must maintain. These responsibilities should be visible in the proposal before the visual design is approved.
For a catalogue request form, preserve the product context and let the buyer describe the intended use or quantity without demanding unnecessary private information. Confirm that a request has been recorded, not that an order has been accepted. The team reviewing requests should see enough information to continue the conversation, with duplicates and test records handled sensibly.
At handover, document how new products are added, who checks specifications and how old sheets are retired. If the business later needs online sales, treat that as a scope change with operational review. A well-designed presentation catalogue is a complete product when it supports the actual sales process; it is not an unfinished shop merely because it does not collect payments.
Write down a sample transaction before choosing features. Follow one realistic product enquiry from the buyer's first question to an agreed quotation. Note which details are fixed and which require discussion. If price depends on a reviewed drawing or quantity, a simple cart may misrepresent the process rather than simplify it.
Use that example to design the catalogue form. Preserve the selected product family and ask only for information needed to continue. Do not claim that a submitted enquiry reserves stock or confirms a delivery date. The confirmation should match the actual record created and the business's next step.
Also plan how product information changes. A revised material description should update the page and any downloadable sheet together. A discontinued item needs a clear replacement or retirement decision, not an abandoned detail page that still invites orders. This maintenance is relevant to a catalogue even without online payment. Treating it as part of the operating model helps the business choose an appropriately scoped site and recognise when a later store project is genuinely needed.
Practical checklist
- Prepare specifications
- Define the quotation process
- Separate stock and payment requirements
A concrete example: A small manufacturer can show materials, dimensions and minimum-order information, then request project details for a written quotation.
A boundary to keep clear: Adding a payment button alone does not create a complete stock, shipping or returns operation.
Your next step
Tell Orvunweb about your project
