What to think about when building an online store

In a store project, the most time goes not into design but into decisions nobody has made: where the stock figures come from, what happens with returns, who is responsible for product descriptions. Those questions don't go away - they just arrive later, and by then they're more expensive.

Decide before development#

Where the product data comes from#

This is the single most important decision. If products already live in warehouse software or an ERP, you have to agree which system is the source of truth for each field. Usually: price and stock come from the system, images and descriptions live in the store.

Without that agreement, discrepancies appear within the first month and nobody knows which number is right.

Product structure and variants#

Does a product have sizes and colours? Are there ten combinations or a thousand? Does the price depend on the variant? Does some combination exist only for a particular customer?

The variant model is the hardest thing to change after the fact, because the whole catalogue's logic depends on it.

Payment and delivery#

In practice that means bank links, card payment and parcel machines. Most have a ready-made WooCommerce module. Check before quoting whether your chosen provider does - if not, that's a separate integration project.

Delivery cost has to be shown as early as possible. The most common reason people abandon a basket is a sum that appears unexpectedly at the checkout.

VAT and target markets#

Are you selling domestically or across the EU? Cross-border sales mean VAT rules determined by the destination country, which affects both how prices are displayed and how the accounting works. That's a business decision, not a technical detail, and it has to be settled before development.

The journey that actually matters#

The home page usually takes the most design time and is the least important page. Visitors arrive from search straight onto a product page.

The product page has to answer the questions that otherwise stop a purchase: what material, what dimensions, when will it arrive, can I return it. If the answer isn't on the page, the customer goes looking elsewhere - often at a competitor.

The basket has to show the full total including delivery as early as possible.

The checkout has to be as short as it can be. Forcing account creation is a sale lost in one click - offer guest checkout and put account creation after the order.

What not to do#

• Don't add a new plugin for every feature. Twenty plugins means twenty sources of updates and twenty possible conflicts on the morning of Black Friday.
• Don't launch without analytics. Ecommerce events - product view, add to basket, begin checkout, purchase - have to be in place before you publish. You can't collect that data retrospectively.
• Don't test with demo data. A catalogue that's fast with 20 products can be unusable with 5,000. Test at the real volume.
• Don't forget the emails. Order confirmation, dispatch notice and return information are part of the product. They get read more than any page in the store.

After launch#

A store needs more attention than an ordinary website. Payment modules update, delivery services change their APIs, major WooCommerce versions need testing. It's also worth walking the order flow through properly in the first weeks - every order from beginning to end, cancellations and returns included.

The most useful thing to do in the first month is look at the analytics for where the journey breaks, and fix that one place. It will do more than a new design.