Blog

How to build an ecommerce website: the steps in order, from catalogue to launch

How to build an ecommerce website in the right order: catalogue, rules, platform, payments, shipping, pages and test orders, with a launch checklist.

By Rokibul Hasan8 min read

  • E-commerce
  • Web development
A designer sketching website wireframes on paper next to a laptop.

Most guides on how to build an ecommerce website begin with choosing a theme. That is the easiest decision to reverse. A catalogue with no weights, a loss-making shipping rate or an untested checkout will cost you far more in your first month than the wrong template.

This guide gives the steps in the order that avoids rework, from catalogue to launch. It is for owners building a first store or rebuilding one, and it holds whether you end up on Shopify, WooCommerce, a website builder or a custom build.

The order matters because each step feeds the next. Shipping rates need weights, weights live in the catalogue, and the catalogue tells you which platform can hold it.

How to build an ecommerce website: the order and the reason

Step What you end up with What goes wrong if you skip it
1. Catalogue One spreadsheet of every product Limits and missing data surface after launch
2. Rules Where you sell, tax, returns, privacy Duties you did not plan for
3. Platform A choice based on your real data You pick a brand, then fight it
4. Payments A live provider, card data off your site Security work you did not budget for
5. Shipping Rates that protect your margin A loss on every distant order
6. Pages The pages buyers really use A polished home page and weak product pages
7. Back office Orders reach stock and accounts Retyping everything from day one
8. Test and launch Proven orders, refunds and redirects Customers find the bugs for you

Step 1: Build the catalogue in a spreadsheet

Before you open any platform, make one spreadsheet with a row for every variant.

  • SKU. A unique code for each variant. Stock sync, accounting and marketplaces all match on it later.
  • Title and description. Written for buyers, answering what they would otherwise email you about.
  • Options. Size, colour, material, and which combinations really exist.
  • Price and cost. Customers never see your cost, but step 5 depends on it.
  • Weight and dimensions. Measured after packing, because shipping rates use them.
  • Images. Named so they match the SKU, with the same angles across a range.
  • Barcode. Where one exists, since marketplaces and shopping feeds ask for it.
  • Stock count. A real count on the day you load it.

Count your variants early. A T-shirt in 4 sizes and 5 colours is 20 variants, each with its own SKU and stock figure, so a range of 20 shirts is 400 rows. That number decides how long loading will take, and it can rule platforms out: Squarespace allows 250 variants a product and Wix allows 1,000.

Step 2: Settle the rules your store must follow

Decide where you will sell and ship, then find out what that obliges you to do. Two examples catch new stores out:

  • US sales tax. In South Dakota v. Wayfair in June 2018, the Supreme Court ended the rule that a seller needed a physical presence in a state before that state could require it to collect sales tax. Each state now sets its own thresholds, so selling into a state can create a duty before you have ever been there.
  • EU accessibility. The European Accessibility Act applies from 28 June 2025, and the EU's guidance for businesses names online shops among the services covered. It gives an exception for service businesses with fewer than 10 staff and under €2 million in turnover. National laws apply it, so check the countries you sell in.

Write your returns, shipping and privacy policies now too, because their terms shape the checkout. I am a developer, so treat all of this as a prompt to speak to an accountant or lawyer in your own market.

Step 3: Choose the platform with that data in hand

Most advice on how to build an ecommerce website puts this step first. By now you know your variant count, your countries and your channels, which is what the decision should rest on. My guide to the best ecommerce platform by business type gives a shortlist. If you are drawn to Wix or Squarespace, read when a website builder is enough first.

Load your most complicated product into a trial before you decide. Then pick a theme by how it shows products like yours.

Step 4: Set up payments so card data stays off your site

Open your payment account early. The provider will want business and bank details, and you cannot run a true test order without it.

The safe default is that card numbers go straight to the payment provider and never touch your server. Hosted platforms work this way already. On a custom build, use the provider's hosted payment page.

This also decides your security paperwork. To qualify for SAQ A, the card industry's lightest self-assessment for online stores, all elements of the payment page must come only and directly from a PCI DSS compliant provider. In February 2025 the PCI Security Standards Council clarified that the newer criterion on script attacks applies to embedded payment forms such as iframes, and does not apply to sites that redirect customers to the provider. Ask your provider which setup you are on. For choosing between gateways and wallets, see my guide to ecommerce payment integration.

Step 5: Work out shipping before you design anything

Shipping is where a store loses money without noticing, so run the numbers per order before you promise anything on a banner. This is an illustration with made-up costs:

Line Amount
Sale price $40.00
Product cost -$16.00
Card fee at 2.9% + 30¢ -$1.46
Packaging -$1.00
Postage, nearby zone -$7.50
Left for ads, returns and overheads $14.04

Now change one thing at a time. Ship the same order to a zone costing $14 and you keep $7.54. Offer 10% off on the nearby zone and you keep about $10.16. This small table tells you where a free shipping threshold can sit, which zones need a higher rate and how much room you have for discounts.

Then decide who pays for returns and what happens to the original postage, because the same maths applies in reverse.

Step 6: Build the pages buyers actually use

Work in order of how much they affect a sale:

  1. Product page. Clear photos, the price, delivery cost and time, a variant picker showing what is in stock, and the returns policy.
  2. Collection pages and search. Filters built from your real attributes, which you already have from step 1.
  3. Cart and checkout. No surprise costs at the last step, and guest checkout if your platform allows it.
  4. Home page. Last, once you know what you want to send people to.

Design for phones first. Adobe's forecast for the 2026 US holiday season, reported by Digital Commerce 360, has mobile at 57.4% of online sales.

Product pages also need to speak to search engines. Google's merchant listing documentation requires a name, an image and an offer with a price and currency in your structured data. Good themes usually handle this. On a custom build it is on your task list.

Step 7: Decide what happens after an order

Walk one order through your business on paper. Who gets told? Where does the stock figure drop? How does the sale reach your accounts, and how does tracking reach the customer?

At low volume, doing some of this by hand is fine, and it shows you what is worth automating. Write the steps down anyway. The systems a growing store needs can wait until a task repeats every day.

When it does, an order export or a report is the kind of single automation my marketplace MVP plan covers. It starts from $2,500, as a starting price, and every project gets a fixed quote after a short brief.

Step 8: Test with real orders, then launch

Run this script on the finished store before anyone else sees it:

  1. Buy with a real card, on a phone, using mobile data.
  2. Refund that order and check that the money and stock both come back.
  3. Buy a low-stock variant until it sells out, and see what the page does.
  4. Apply a discount code and confirm tax and shipping recalculate.
  5. Check out to every shipping zone, including the most distant.
  6. Force a failed payment and see what the customer is told.
  7. Read every email a customer receives, on a phone.
  8. Confirm the order reaches whoever packs it and whatever records it.

If you are replacing an existing site, map every old URL to its new one first. Google's site move guidance says to use permanent server-side redirects, go straight to the final page, and keep them generally for at least a year.

Then switch the domain at a quiet time, place one more real order on the live site, and watch the first few customer orders closely. Avoid launching in the middle of your busiest season if you have any choice.

FAQ

Do I need to code to learn how to build an ecommerce website?

No, not for a standard store. Shopify, Wix, Squarespace and similar platforms let you load products, set up payments and choose a theme without writing code. You need a developer when a store has to do something the platform and its apps cannot, such as a custom product flow or a connection between systems. Most of the hard work in a first store is catalogue data, shipping and policies, none of which involve code.

Can I build an ecommerce website for free?

Not one that takes payments and stays free. Wix's Free plan does not include accepting payments. The WooCommerce plugin costs nothing but needs paid hosting, and Woo puts that at $25 to $350 a month for most stores. Shopify offers a short free trial, then a paid plan. Every option charges card processing on each sale as well, so budget for a plan or hosting, a domain and payment fees from the start.

How many products do I need before launching a store?

Fewer than most owners think. Launch with the products you can photograph, describe, price and ship properly, even if that is a small part of your range. A short catalogue with complete data sells better than a long one with gaps, and it lets you test orders, shipping and returns at low risk. Add the rest in batches, using the same spreadsheet, so your SKUs and attributes stay consistent as the catalogue grows.

If you need more than a theme can do, send me a short brief: what you sell, roughly how many products and variants, where you ship and what already exists. You can start from the Advanced website plan, see how I work on the page about building a website with me, or read what an ecommerce website costs before you set a budget.