Business website or online store: choosing the right architecture

A business website usually informs and leads to an enquiry, visit or request. An online store completes a transaction and must support everything around it. Between them, a catalogue without checkout can present a complex offer without selling online.

Describe the action each audience must complete and what happens next inside the business. The right choice depends less on a label than on the complete journey and its operational needs.

This architecture suits sales that require a conversation, diagnosis, quotation, visit or tailored service. It can combine service pages, work examples, local information, FAQs and contact routes.

It still needs content governance, responsive behaviour, accessibility, security and suitable maintenance. A business website does not necessarily mean a single page or a project without technical requirements.

A store is appropriate when product, price, availability, delivery and terms can be described clearly enough to complete an order without a mandatory prior intervention.

Before choosing a platform, document catalogue, variants, stock, tax, payments, delivery, returns, accounts, invoices, support and compliance. Technology cannot repair an operating process that the team cannot fulfil.

Compare delivery as well as subscriptions, extensions, transactions, integrations, maintenance and administration time. Review each supplier’s current terms when deciding because they can change.

Assign ownership for product data, orders, refunds, incidents and customer requests. A low technical charge may require heavy manual work, while automation creates a different cost profile.

It may be possible to launch a catalogue or business site and add sales later, but only when architecture, data and contracts allow it. That evolution needs assessment; it is not automatic.

If online sales are likely, structure product data and identifiers now without building the whole checkout prematurely. Define the conditions that would trigger the next phase.

A Brussels plumber sells call-outs priced on site. A brochure site with one page per type of job, a clear service area, photographs of real work and a phone number visible everywhere meets the need exactly. A checkout would have nothing to sell.

A bakery taking cake orders for the weekend sits in between. A catalogue without payment, with an order form that states the lead time and collection in store, captures requests without imposing online stock management. Payment happens at collection; a full shop would come if volume justifies it.

A clothing brand shipping across Belgium needs a real shop: size and colour variants, stock per variant, delivery via a carrier, returns, online payment. A consultancy, by contrast, sells a relationship; its best architecture is a restrained brochure site that explains the method, shows anonymised cases and leads to a first conversation.

Between the brochure site and the shop lies an intermediate architecture: present each product on its own page, with photographs, description, indicative price and variants, but replace the buy button with a request for a quote or for availability. It suits made-to-measure products, negotiated prices, bulky items or trade customers who want to qualify before selling.

It keeps the search advantages of a shop — one indexable page per product with structured data — without the operational burden of payments, returns and logistics. It does require a quick human answer to every request, failing which it frustrates more than a plain contact form.

If online selling is envisaged later, this architecture is the best preparation: the products already exist with their identifiers, photographs and descriptions. Adding payment becomes an integration project, not a redesign.

An online shop is an activity, not a site. Every day, someone must process orders, prepare parcels, answer questions about delivery times, handle a return, update stock, correct a listing. An order placed on Friday evening and shipped the following Wednesday produces a negative review, whatever the quality of the site.

In Belgium, precise obligations come on top: a fourteen-day right of withdrawal for consumers, clear information on delivery costs and times before ordering, prices including VAT, terms and conditions explicitly accepted, an order confirmation sent on a durable medium. These rules translate into the interface and the texts, and a breach is sanctionable.

Before choosing a shop, do the exercise on paper with a typical week: how many orders, who prepares them, where the products are stored, how returns are handled, which carrier, which payment methods. If the answers are vague, the business is not ready for a shop, and the catalogue without checkout is the reasonable intermediate step.

Bancontact is essential for a Belgian audience and must be offered from launch, alongside international cards. Payconiq, bank transfer and sometimes payment on delivery or in store complete the offer depending on the customer base. Each method has its fee, its settlement time and its failure cases; the chosen payment provider determines what is available and at what price.

• For delivery, Bpost remains the densest network for private customers, with a choice between home delivery, pick-up point and parcel locker.
• Other carriers suit heavy parcels or business shipments better.
• Charges must be announced before the customer starts ordering, not discovered at the last step.

Collection in store is a valuable option for a neighbourhood business: it removes shipping costs, brings the customer back into the shop and simplifies returns. It only requires a clear process for preparing the order and signalling that it is ready.

Ask five questions. Can the customer complete the purchase alone, without a prior conversation? Are the product and its price stable and describable? Can the business ship or hand over within a time it is willing to display? Does the expected volume justify a shop’s fixed costs? Is someone available every day to process orders?

Five yeses: the shop is justified. One or two noes on the first questions: the catalogue without checkout or the brochure site fit better. A no on the last two: the business is not ready, whatever the quality of the site, and it is better to launch a simpler architecture and evolve.

In every case, structure now what will serve later: one page per service or product, clean photographs, useful descriptions, stable URLs. These foundations are common to all three architectures and make evolution possible without rebuilding everything.

Choose the simplest option that completes the necessary journey. Then check the team’s ability to maintain content and operations, compliance constraints, essential integrations and recurring costs.

Before building, test a few real scenarios: unavailable product, variant, cancellation, bespoke request or translation. Exceptions often reveal the architecture actually required.