How to build an online store: choosing the platform, what drives build and running costs, payments and PCI DSS, selling in several currencies, the checkout research and a launch plan with a checklist.
An online store is three projects in one: a website people enjoy using, a set of business systems (stock, orders, payments, tax, shipping) and an operation that must run every day after launch. Most store budgets go wrong when the first part gets all the attention and the other two are discovered late.
This guide covers the decisions in the order they matter: the platform, what drives the cost, payments and card security, selling across currencies and markets, the checkout, product data and search, and a launch plan you can follow. It is written for retailers and brands selling in the UK, the USA, Canada, the UAE, Australia, India, Singapore and Europe. Platform fees and research figures are given with their source and date; we do not quote our own prices without a scope.
Key takeaways
- Choose the platform for your catalogue, team and growth plan: hosted platforms are quickest, open source gives control, enterprise and headless builds suit complex catalogues and integrations.
- Platform fees are a small part of the total: design, integrations, data migration, apps or extensions, payments and the team who runs the store cost more.
- Use a payment integration that keeps card data off your servers; handling card numbers yourself brings hundreds of PCI DSS security controls into scope.
- Unexpected extra costs are the most common reason shoppers in the USA give for abandoning a checkout, so show shipping, tax and fees early.
- Plan the launch as a project of its own: data, redirects, payments, tax, emails, analytics and a rehearsal before the switch.
Step one: choose how the store is built
There are five broad ways to build an online store. The right one depends on the size of your catalogue, how unusual your processes are, who will run the store and how much control you need over hosting and code.
| Route | Examples | Suits | Watch out for |
|---|---|---|---|
| Hosted platform (SaaS) | Shopify | Most retail and direct-to-consumer brands that want to launch quickly and not run servers | Monthly plan and app subscriptions; you work within the platform's own rules and hosting |
| Open source on your own hosting | WooCommerce on WordPress, Magento Open Source | Stores that want full control of code, data and hosting, or that already run WordPress | You are responsible for hosting, updates and security |
| Enterprise platform | Adobe Commerce, Shopify Plus | Large catalogues, several brands or regions, B2B pricing, high order volumes | Licence quoted by the vendor, longer projects, specialist skills |
| Headless or composable | A commerce engine behind a custom front end, such as Next.js | Brands that need a front end the platform's themes cannot give, or one back end for several channels | Two systems to build and run instead of one |
| Custom build | Your own commerce application | Unusual business models that no platform supports | Highest cost; payments, tax and security are all yours to build |
For most businesses the real choice is between Shopify, WooCommerce and Magento. Our comparison of Shopify, WooCommerce and Magento sets out their fees, hosting, licensing and extensions as of November 2026. If your front end needs to go beyond what a theme allows, our headless and composable commerce service covers the separate front end and the engine behind it.
Which kind of store build fits?
Question 1: Do you want to launch quickly without running servers or patching software?
Question 2: Is your catalogue, pricing and checkout close to standard retail?
- YesA hosted platform such as Shopify
- NoGo to question 4
Question 3: Do you already run WordPress, or want full control of code and hosting with a modest catalogue?
- YesWooCommerce on managed hosting
- NoGo to question 4
Question 4: Do you have large or complex catalogues, several brands or regions, or B2B rules such as customer-specific prices?
- YesMagento, Adobe Commerce or Shopify Plus
- NoGo to question 5
Question 5: Does the front end need a design or a mix of channels that no theme can give?
- YesHeadless commerce
- NoStart with a hosted platform and review after launch
What drives e-commerce development cost
A store’s budget has two parts: what it costs to build and what it costs to run. Platform fees are the visible line in both, but rarely the largest.
| Cost | One-off or running | What decides it |
|---|---|---|
| Platform plan or licence | Running | The platform and plan; enterprise licences are quoted by the vendor |
| Hosting | Running (open source) | Traffic, catalogue size and the level of management you buy |
| Design and theme | One-off | A customised theme or a custom design; number of page templates |
| Apps or extensions | Running and one-off | How many features come from paid add-ons versus custom code |
| Integrations | One-off, plus upkeep | ERP, stock, accounting, shipping, marketplaces, CRM and email tools |
| Data migration | One-off | Products, variants, customers, orders and URLs to bring across |
| Payments | Running | Provider rates per transaction, cross-border and currency fees |
| Content and photography | One-off and running | Product descriptions, images and translations |
| Marketing and search | Running | Search, paid media, email and marketplace fees |
| Support and improvement | Running | Updates, fixes, security patches and new features |
Published platform fees, as examples
The vendors publish their own figures, and they show how the cost moves between licence, hosting and add-ons. As of 13 Nov 2026:
| Platform | What the vendor publishes |
|---|---|
| Shopify | Plans from £25 a month billed monthly (£19 billed yearly) on the UK page, up to Advanced at £344 (£259); Plus starts at £1,800 a month. Prices are shown in local currency per country. |
| WooCommerce | The core plugin is free; WooCommerce estimates hosting at 25 to 350 USD a month for most stores and extensions at 29 to 299 USD a year each. |
| Magento Open Source | Free to download under the OSL 3.0 licence; hosting, extensions and development are separate costs. |
| Adobe Commerce | No list price is published; the licence is agreed with Adobe. |
Source: Shopify UK pricing page; WooCommerce pricing page; Adobe Commerce documentation and Magento Open Source repository (all checked 13 Nov 2026)
The sources are Shopify’s UK pricing page, WooCommerce pricing and the Magento Open Source repository. Shopify shows each country’s prices in its own currency, so a buyer in Canada or Australia sees CAD or AUD plans; the comparison article lists those too.
Where the build budget goes
On most store projects the largest one-off items are design, integrations and data migration, not the platform. A store that only needs a well-made theme, a payment provider and a shipping app is a small project on any platform. A store that must sync stock with an ERP, show customer-specific prices, sell in several currencies and import ten years of orders is a large one on any platform. If you sell to businesses, our B2B e-commerce portal development service covers accounts, price lists, quotes and ERP sync.
Payments and card security
Every store that takes card payments has obligations under the Payment Card Industry Data Security Standard (PCI DSS). As Stripe’s integration guide puts it, anyone involved with processing, transmitting or storing card data must comply, and a business that handles card data directly “might be required to meet more than 300 security controls” (Stripe integration security guide, checked 13 Nov 2026). The practical answer is to use a payment integration where card details go straight to the provider: a hosted checkout, embedded payment fields or the platform’s own payments. Your store then never sees a card number, which keeps most of those controls out of scope.
Never store card numbers
Do not store full card numbers or security codes in your own database or logs. Use the payment provider's tokens, and keep only what providers return as safe to keep, such as the card brand, last four digits and expiry date.
Payment fees differ by market
Card fees depend on the provider, your country and where the shopper’s card was issued. WooPayments, the payment service built for WooCommerce, publishes rates per country that show the pattern:
| Account country | Base card fee | International card | Currency conversion |
|---|---|---|---|
| USA | 2.90% + 0.30 USD | +1.50% | +1.00% |
| UK | 1.50% + 0.25 GBP | +2.00% | +2.00% |
| Germany | 1.50% + 0.25 EUR | +2.00% for cards from outside Europe | +2.00% |
Source: WooCommerce documentation, WooPayments fees (checked 13 Nov 2026)
The full list is on the WooPayments fees page. Shopify publishes its Shopify Payments rates per plan on each country’s pricing page, and charges an extra fee when you use a third-party payment provider instead (2% on Basic down to 0.2% on Plus on the UK page). When you sell abroad, compare the international card and conversion fees, not only the headline rate.
Selling in several currencies and markets
Selling to buyers in more than one of our eight markets raises four questions: which currencies you show and settle in, how tax is calculated and collected, how goods are shipped and returned, and which consumer and data protection rules apply. All three main platforms can show prices in more than one currency, each in its own way: Shopify converts prices per market through Shopify Markets (full features need Shopify Payments), WooPayments’ multi-currency feature changes the prices shown but not the currency of your payouts, and Adobe Commerce sets allowed and display currencies per store view, with a base currency per website.
Tax is where cross-border stores most often get caught. VAT, GST and sales tax rules on imports and online sales differ by country, and registration thresholds change. Check the rules with each country’s tax authority or an accountant before you open a market, and choose a tax engine or app that supports the countries you sell to. On data protection, the same rules apply as for any website: the GDPR for shoppers in the EU, UK GDPR in the UK, and the national laws of the other markets, depending on where your customers are.
Before you open a new market
- Prices: local currency shown, rounding rules and whether prices include tax
- Payments: the methods shoppers in that market expect, and the fees for foreign cards
- Tax: registration, rates, invoices and how tax is shown at checkout
- Shipping: carriers, duties, delivery times and a returns address
- Legal pages: terms, returns policy and privacy notice for that market
- Language and units: spelling, sizes, weights and date formats
- Customer service hours that match the market's day
Want a second opinion on your plans?
Tell us what you are working on. A specialist will look at it and reply with practical next steps.
Get in touchThe checkout: where stores lose sales
Baymard Institute’s list of 50 studies puts the average documented online shopping cart abandonment rate at 70.22% (Baymard Institute, cart abandonment rate statistics, page updated 28 Oct 2026). Many of those shoppers were only browsing. Among US online shoppers who abandoned a checkout for other reasons, the reasons below were the most common.
Several of these are design and development decisions, not marketing ones. Show shipping and tax before the final step, offer guest checkout, keep the form short, test the checkout on real phones, show the returns policy where people decide and offer the payment methods each market expects. Our conversion rate optimisation service audits checkouts against this kind of research.
Product data, search and structured data
Good product data is what makes a store findable, both in your own search and in search engines. Plan the catalogue structure before the design: categories, attributes, variants, and which fields each product type needs.
Google supports two kinds of product structured data: product snippets for pages where people cannot buy directly, and merchant listings for pages where they can, which can carry details such as shipping and return policies (Google Search Central, product structured data). Most platforms output basic product markup; check that yours includes price, availability and the return and shipping details you want shown, and that it stays correct when prices change.
Product data to settle before the build
- Category tree and the filters shoppers need on each category
- Attributes and variants per product type (size, colour, material, pack size)
- Image standards: sizes, backgrounds, number of views
- Product description template and who writes it
- Identifiers: SKU, barcode or manufacturer part number
- Stock source of truth and how often it syncs
- Prices, tax classes and any customer-specific prices
A launch plan for a new or rebuilt store
A store launch is safest when it is rehearsed. The timeline below is the order we follow; the length of each stage depends on the catalogue, the integrations and the data to migrate.
Discovery
Requirements and platform
Catalogue, integrations, markets, payments, tax and shipping rules; platform choice and a written scope.
Design
Templates and checkout
Home, category, product, cart, checkout and account templates, tested as a prototype on phones first.
Build
Store, integrations and data
Theme or front end, apps or extensions, integrations, and repeated trial imports of products, customers and orders.
Testing
Orders end to end
Test orders in every payment method and market, tax and shipping checks, emails, refunds and returns.
Launch
Switch and redirects
Final data import, redirects from old URLs, payments and tax switched to live, analytics and monitoring.
After launch
Measure and improve
Conversion, search, speed and support queries reviewed weekly for the first month.
Launch checklist
- Payments live and tested with real cards, including a refund
- Tax and shipping checked for every market and product type
- Order, shipping and account emails reviewed and branded
- Old URLs redirected to their new pages, and the sitemap submitted
- Product structured data checked with Google's testing tools
- Analytics and conversion tracking recording test orders
- Privacy notice, cookie consent, terms and returns policy published
- Stock and order sync with the ERP or warehouse confirmed
- Backups, monitoring and an out-of-hours contact in place
- A rollback plan if the switch fails
After launch: running the store
The work does not stop at launch. Platform updates, extension updates, security patches, new payment methods and seasonal campaigns all need someone who knows the store. On open source platforms that includes the server and the software itself; on hosted platforms it is mostly apps, theme and integrations. Decide before launch who does this work and how quickly they respond.
What to measure in the first three months
- Conversion rate by device, and where in the checkout people leave
- Searches on your own store that return no results
- Page speed on phones for the home, category and product templates
- Orders, refunds and returns by product, to spot data or description problems
- Payment failures and declined cards by method and country
- Support questions that the product pages or policies should have answered
- Search impressions and clicks for product and category pages
Review these weekly for the first month and monthly after that. Most early fixes are small: a missing filter, an unclear delivery date, a payment method a market expects. Each one is cheaper than the traffic it takes to win the lost sale back.
The team and the contract for a store build
A store project needs more than developers. The roles below cover most builds; on a small store several are combined in one person, and on a large one each may be a small team.
| Role | What they own |
|---|---|
| Project manager | Plan, scope, budget, communication and the launch date |
| UX and UI designer | Templates, the checkout and the design on phones first |
| Platform developer | Theme or front end, configuration, apps or extensions, custom features |
| Integration developer | ERP, stock, accounting, shipping and marketplace connections |
| QA tester | Test orders, payments, tax, emails and devices |
| SEO specialist | URL structure, redirects, structured data and Merchant Center feeds |
Most store builds suit a fixed price for the launch, because the templates, integrations and data can be written down in discovery. The work after launch (new features, campaigns, updates) suits a monthly team or time and material, because it changes every month. Our engagement models page compares the options.
Red flags in an e-commerce proposal
- No discovery of your catalogue, integrations and markets before the price
- Data migration and redirects missing from the scope
- Apps or extensions assumed but not listed, with their running costs left out
- The store, domain or payment accounts set up in the supplier's name
- No test orders in every payment method and market before launch
- No plan for who updates the platform, theme and extensions after launch
Stores we have built
Our portfolio includes stores on Shopify and on Magento. On Shopify, Perfume Shop sells fragrances from well-known brands worldwide and ASE Martial Arts Supply is the store of a long-standing retailer of martial arts equipment. On Magento, Sea Rush sells aquatic and water sports gear, The Health Store took a local health retailer online and Delyla sells premium organic yarns and fibres.
We work across the main platforms: Shopify development, WooCommerce development and Magento development. Our e-commerce page brings together design, development, marketing and support for online stores, and the custom software development guide covers contracts and team models if your store needs custom systems behind it.
Get an estimate: tell us about your store through the quote form, or read more about our e-commerce development service. A specialist replies within one business day with questions, an approach and a cost range.
Get new guides by email
Articles and guides from our team, and company news. Unsubscribe at any time.
About AcmaSoft
AcmaSoft designs and builds websites, mobile apps and custom software, and runs SEO and digital marketing for its clients.
- Years of experience
- 17+
- Clients served
- 650+
- Projects delivered
- 2,000+
- Products shipped
- 300+

