✨ AI-powered next-gen commerce platform, Try free
+90 850 259 23 23
All articles
Product updates

How to choose an ecommerce platform: a buyer's guide for growing online stores

Hosted SaaS, open source or a custom build? How to compare ecommerce platforms on total cost of ownership, integrations, SEO, data export and lock-in, which questions to ask vendors, and how to test a shortlist with a trial store before you commit.

SBy Shopiyz Team11 min read

In short

  • Start from your business requirements, not from a feature list: channels, catalog size, markets, payments and the team that will run the store.
  • Compare total cost of ownership over several years, including transaction fees, paid apps, themes, development, hosting and your own team's time.
  • Integrations decide daily workload more than storefront design does: marketplaces, POS, payments, shipping, invoicing and marketing tools.
  • Check before you sign that you can export products, customers and orders in a standard format, and that URLs and redirects are under your control.
  • Build a small trial store on your top two or three options and run real tasks on each before you decide.

Choosing an ecommerce platform touches every part of an online business: page speed, marketplace listings, what you pay on every sale, how much manual work your team does and how hard it will be to leave if the platform stops fitting.

Feature checklists rarely explain why a store outgrows its platform two years later. This guide takes a different approach: start from your own requirements, compare the three platform models honestly, calculate the real cost of ownership, and test your shortlist with a trial store before you commit.

Start with your requirements, not the feature list

Before looking at any vendor, write a one-page requirements document. Answer these questions as a team:

  • What do you sell, and how many products? A small boutique has different needs from a parts supplier with a huge catalog and complex variants.
  • Where do you sell? Only your own website, or also on Amazon, eBay, Etsy or other marketplaces, social channels and a physical store?
  • Which markets? One country and one currency, or several languages and currencies from day one?
  • How do customers pay? Cards, digital wallets, buy now pay later, bank transfer, local payment methods in specific countries?
  • Who will run the store? A founder with no technical background, a marketing team, or in-house developers?
  • What must connect to the platform? Accounting or invoicing software, shipping carriers, a point of sale system, email and SMS tools, warehouse software.

Sort every requirement into must have, should have (within a year) and nice to have. Vendors will try to win you with nice-to-haves; decide your shortlist on must-haves.

The three platform models: hosted SaaS, open source and custom build

Almost every option falls into one of three categories. Each can be right; the question is which trade-offs fit you.

Hosted SaaS

A hosted software-as-a-service platform runs your store on the provider's infrastructure. You pay a subscription; the provider handles servers, security patches, updates, uptime and scaling.

  • Strengths: fast to launch, predictable costs, no server management, security and updates included.
  • Watch for: transaction fees on some plans, reliance on paid apps for core functions, limits on how deeply you can customize checkout or backend logic.

Open source (self-hosted)

Open source platforms give you the code for free. You install it on hosting you choose and maintain it yourself or with an agency.

  • Strengths: full control over code and data, large communities, freedom to customize anything.
  • Watch for: you are responsible for hosting, security updates, backups and compatibility between extensions. "Free software" is rarely free to run.

Custom build

A custom build means developing the store from scratch or on a headless framework, with your own team or an agency.

  • Strengths: exactly the experience and logic you want.
  • Watch for: the highest upfront and ongoing cost, a long time to launch, and dependence on the people who wrote the code. Every standard feature, from tax rules to abandoned-cart emails, must be built and maintained.

Hosted SaaS vs open source

Open source (self-hosted)

  • Software is free, hosting and maintenance are yours
  • Unlimited customization with developer time
  • You apply security patches and updates
  • Extensions from many vendors must stay compatible
  • Costs vary with traffic and development needs

Hosted SaaS

  • Subscription covers hosting, security and updates
  • Customization within the platform's framework
  • Provider patches and scales the infrastructure
  • Core features and integrations maintained by one vendor
  • Costs are more predictable month to month
Neither model is better in general. The right one depends on your team, budget and how unusual your requirements are.

Total cost of ownership: the number that actually matters

The monthly subscription is the most visible cost and often the least important one. Estimate total cost of ownership (TCO) over a realistic period, such as three years, including every line below.

  1. Platform fees: subscription or license, and how the price changes as you grow (more products, staff accounts, orders or stores).
  2. Transaction fees and commissions: some platforms take a percentage of each sale on top of payment processing, or charge extra if you use a payment provider other than their own. Over thousands of orders, this can outweigh the subscription.
  3. Payment processing: card and wallet fees charged by the payment provider. Check whether you can connect your own merchant agreement.
  4. Apps and plugins: list every function you need (reviews, marketplace sync, product filters, subscriptions, B2B pricing, translations) and check whether it is built in or a paid add-on. Many stores end up paying more for apps than for the platform.
  5. Themes and design: a premium theme, design customization or agency hours.
  6. Development: initial setup, custom features, integrations and ongoing changes.
  7. Hosting, security and maintenance: for self-hosted setups, servers, CDN, SSL, backups, monitoring and the hours spent on updates.
  8. Internal time: the hours your team spends on manual work the platform does not automate, such as updating stock on several channels or creating invoices by hand.

Integrations decide your daily workload

A beautiful storefront does not save time. Integrations do. Check each category:

  • Marketplaces: if you sell or plan to sell on Amazon, eBay, Etsy or other marketplaces, look for native integrations with real-time stock sync and central order management, not just a product feed. Our guide to multichannel ecommerce software explains what a good marketplace integration looks like.
  • Payments: the payment methods your customers expect in every market you serve, and whether you can choose your provider.
  • Shipping: carrier connections, label printing, rates at checkout and tracking emails.
  • Point of sale: if you have a physical store, a POS that shares stock and customer data with the website.
  • Invoicing and accounting: automatic invoice creation when an order is completed.
  • Marketing: email and SMS campaigns, abandoned-cart reminders, product catalogs for Google and social channels.

For every integration, ask: who maintains it, what happens when it fails, and does it cost extra?

SEO, speed and content: check before you commit

Organic search is a long-term asset, and the platform sets its ceiling. Check that you can:

  • Edit titles, meta descriptions and URLs for products, categories and content pages.
  • Create 301 redirects yourself, in bulk if needed.
  • Generate an XML sitemap automatically.
  • Output product structured data with price and availability.
  • Control how filter and sort URLs are indexed, so faceted navigation does not create duplicate pages.
  • Run multilingual SEO properly, with separate settings per language and hreflang tags, if you sell in several markets.
  • Serve fast pages on mobile: image compression, modern formats, a CDN and lean theme code.

Test real pages from stores already running on each platform in PageSpeed Insights, and check their structured data with the Rich Results Test. Our ecommerce SEO guide covers what to look for in more depth.

Moving from an existing store? Read our replatforming SEO checklist before you plan the switch.

Data ownership, export and lock-in

The best time to plan your exit is before you sign up. Confirm the following:

  • Data export: you can export products (with variants and images), customers and order history in a standard format such as CSV, at any time, without paying extra.
  • Domain ownership: the domain is registered in your name, and you can point it elsewhere.
  • URL control: you can set your own URL structure and redirects, so a future migration does not wipe out your search rankings.
  • Contract terms: monthly billing or a clear annual term, no exit fees, and clear terms for what happens to your data if you cancel.

Questions to ask every platform vendor

Use the same list for every vendor:

  1. What exactly is included in the plan we would need, and what costs extra?
  2. Do you charge any transaction fee or commission on sales?
  3. Can we use our own payment provider or merchant agreement?
  4. Which of our must-haves are built in, which need an app, and which need development?
  5. How do your integrations handle stock and order sync, and what happens when a sync fails?
  6. How do we export all our data, and in what format?
  7. Who handles security, updates, backups and uptime?
  8. What does migration support look like, including data import and URL redirects?
  9. Is there a long-term contract, minimum term or cancellation fee?

Platform evaluation checklist

  1. 01Must-have requirements written and agreed
  2. 02Three-year total cost of ownership estimated for each option
  3. 03Transaction fees and app costs included
  4. 04Marketplace, payment, shipping and POS integrations confirmed
  5. 05SEO controls tested: titles, URLs, redirects, sitemap, structured data
  6. 06Data export tested with a real sample
  7. 07Contract, exit terms and support reviewed
  8. 08Trial store completed for the top options
Score each shortlisted platform against the same list so the decision is based on evidence, not on the best demo.

The trial-store method: test before you decide

Demos show the best path through a product; a trial store shows daily reality. Narrow your list to two or three options and run the same test on each.

The trial-store method

  1. 1

    Pick 20–30 real products, including tricky variants

  2. 2

    Import them in bulk

  3. 3

    Build the homepage, a category and a product page

  4. 4

    Connect a payment method and a sales channel

  5. 5

    Place and fulfill a test order

  6. 6

    Export the data back out

  7. 7

    Score each platform

Running identical tasks on every shortlisted platform turns a subjective choice into a comparison.

While you work, note:

  • How long each task took and how many times you needed documentation or support.
  • What required an app or developer that you expected to be built in.
  • How the storefront performs on a phone on a normal mobile connection.
  • Whether the export gave you clean, complete data.

Ask the people who will use the admin daily to do the tasks themselves; their experience is the best predictor of life after launch.

Example scenario: a home goods brand chooses its next platform

Here is a hypothetical example. A small home goods brand sells on its website and one marketplace. Its self-hosted store has become slow, and every plugin update risks breaking something. The team wants to add a second marketplace and a pop-up shop.

  1. Requirements: The team lists its must-haves: native marketplace integrations with stock sync, a POS for the pop-up, solid SEO controls, and no dependence on a developer for everyday changes.
  2. Shortlist: It compares staying on open source with a better agency, a custom build and two hosted SaaS platforms.
  3. Cost of ownership: Over three years, the custom build is ruled out on cost and time. The open source option looks cheap until hosting, maintenance hours and paid extensions are added.
  4. Trial stores: Both SaaS options get the same real products, a test order and a full data export.
  5. Decision: The team picks the platform where marketplace sync, POS and SEO are built in, and where the export was clean. It then plans the migration using its redirect map.

The lesson: the platform that looks cheapest on a pricing page is not always the cheapest to run. A structured comparison and a hands-on trial reveal the difference.

Choosing Shopiyz as your ecommerce platform

Shopiyz is a hosted SaaS ecommerce platform. Servers, security and updates are handled for you, so your team can focus on selling:

  • Transparent costs: a free plan to start, no commission on your sales and no contract. See pricing.
  • Built-in channels: 42+ marketplace integrations, including Amazon, eBay, Etsy and Temu, with real-time stock sync and central order management.
  • Store and online together: Retail POS and omnichannel features keep stock and customer profiles in sync between your store and website.
  • Payments: 30+ payment methods including Stripe, PayPal and Klarna, and you can connect your own merchant agreement.
  • SEO under your control: titles, descriptions, URLs, redirects and sitemap in one place, schema.org product markup, WebP images, a CDN and per-language SEO settings with hreflang.
  • No-code design: a drag-and-drop website builder with your own domain and automatic SSL.
  • Easy to switch: import tools for products, customers and orders, bulk CSV import and export, and a support team that guides your migration.

You can open a trial store on the free plan and run the tests above, or talk to us about your requirements.

Frequently asked questions

Is hosted SaaS or open source better for a small online store?

For most small and mid-sized stores, hosted SaaS is the simpler choice because hosting, security and updates are handled for you and costs are predictable. Open source makes sense when you have reliable development capacity and needs that a hosted platform genuinely cannot meet.

What hidden costs should I look for when comparing ecommerce platforms?

Look beyond the monthly subscription: transaction or sales commission fees, payment processing, paid apps and plugins, premium themes, developer hours for customization, hosting and security for self-hosted setups, and the internal time your team spends maintaining everything.

How do I avoid vendor lock-in with an ecommerce platform?

Confirm that you can export products, customers and orders in a standard format such as CSV, that you own your domain, that you can set your own URLs and redirects, and that there is no long contract or exit fee. Ask for a sample export during the trial.

How long should I test an ecommerce platform before choosing?

Long enough to complete realistic tasks: importing part of your catalog, building key pages, connecting payments and a sales channel, and placing a test order. A focused week or two per shortlisted platform is usually enough.

S

Shopiyz Team

The Shopiyz editorial team of product, growth and e-⁠commerce specialists.

Email newsletter

Get new articles in your inbox

E-⁠commerce guides, Shopiyz updates and growth tactics; hear about it when a new article is out.

Unsubscribe any time · No spam, we promise

Start selling with Shopiyz

Turn insights into action, open your store today

Reading is great, selling is better. Start now to build a professional e-⁠commerce store on your own domain.

Start freeNo credit card required · 7 days free

Cookie Preferences

We use cookies to personalise your experience and collect analytics data. Cookie Policy

Privacy Preferences

Choose which cookies to allow. Strictly necessary cookies are always active.

Strictly necessaryRequired

Required for session management and security.

Analytics

Usage statistics and service improvement.

Marketing

Ad measurement and retargeting.

Preferences

Language and interface personalisation.