An online store is an operational system as well as a visual catalogue. Before choosing the platform, document how products, payments, stock and fulfilment work today. The cost and risk usually sit in those rules rather than the number of screen designs.

Start with representative products

Collect examples covering a simple item, variants, an out-of-stock item and any product needing a quote or special delivery. Define the source of truth for price and stock, who updates it and how frequently it changes. Clean catalogue data is part of the build, not an automatic by-product of installing a shop.

Our BuildVolume project shows category, shop and product-detail interfaces for a specialist catalogue. NORDflam offers another product-discovery example. The public previews demonstrate interface work; they do not establish live sales or merchant integration outcomes.

Treat payment as a full journey

Choose a payment provider after checking current merchant eligibility, fees, supported methods and settlement terms directly with that provider. Confirm who owns the merchant account. Avoid handling raw payment-card data in your own application when a hosted provider flow fits the requirement.

Test successful, failed, cancelled and delayed payments. Verify server-side payment notifications, duplicate handling, order status and confirmation emails. A checkout success screen must not be the only evidence that an order was paid.

Resolve fulfilment and support

  • Delivery regions, collection options and exclusions.
  • Shipping calculations for bulky or unusual items.
  • Stock reservation and what happens when inventory changes.
  • Returns, refunds and customer-support responsibilities.
  • Tax and consumer-facing terms checked for the actual business.

Keep legal policies consistent with the business and obtain qualified advice where necessary; a generic template cannot determine compliance.

Launch a manageable scope

Agree which catalogue and fulfilment cases the first release supports, and document what remains manual. Build a test order checklist that staff can repeat after changes. Explore our ecommerce development service for scope and examples, then use the planning estimator to prepare the initial budget conversation.