Comparisons

Which eCommerce platform to choose: the method, not the fashion

A platform is not a product to rank: it is a constraint to fit to your business model. Here are the variables that really matter.

Updated July 2026 · by the Zeno Web technical team

"What is the best eCommerce platform?" is a question with no answer, and not out of diplomacy: because a platform is not a product to rank, it is a constraint to fit to your business model. The same technology that makes one project fast and profitable makes another slow and expensive, and the difference is not in the technology: it is in the catalogue, the systems already in use and the people who will run the store.

This page does not crown a platform. It gives you the method we use before writing a single line of code: the variables that really matter, what the main technologies do well, and which scenario typically leads to which choice. If you have already narrowed it down to two names, skip straight to the direct comparison between PrestaShop and Shopify.

Why starting from the platform is the most common mistake

The wrong sequence, which we see all the time, goes like this: the technology is chosen on hearsay, then you find out what you need, then you spend months making the platform do things it was not designed for. The cost of that path is not in the initial quote: it comes later, in the form of corrective development, workarounds and functional compromises.

The right sequence is the opposite: first you define the operating model, then you choose the technology that supports it with the least friction. It works in both directions, even when the conclusion is "you can safely stay where you are": rebuilding a platform that works is an expense, not an improvement.

The six variables that really decide

1. The real complexity of the catalogue

Not how many products you have, but how they are built. A catalogue of 20,000 simple items is easier to manage than 300 configurable products with interdependent variants, custom-calculated prices or quantities. The concrete questions: how many variants per product? Are there attributes that change the price? Are there bundled products or configurators? Are there different price lists by customer type? Every "yes" narrows the field.

2. The systems the store must talk to

Management system or ERP, CRM, warehouse, couriers, email marketing platform, any marketplaces. For each one you need to know which direction the data flows and how often. A one-way overnight synchronisation of stock levels is a trivial problem; a real-time two-way synchronisation of orders, returns and customer records is a project in itself, and can by itself determine the choice of technology.

3. Who will run the store after launch

This is the most underestimated variable of all. An eCommerce does not end the day it goes online: that is the day it begins. If you have a dedicated person in-house, you can afford a platform that needs oversight. If the store will be run by carving out time between other duties, you need a technology that is forgiving. The answer to this question changes the recommendation more than the answer about budget.

4. The three-year budget, not the launch budget

The cost of an eCommerce has two components: the initial one, which you can see, and the recurring one, which you cannot see until it arrives. Subscriptions, licences, apps, sales commissions, hosting, maintenance, enhancements. A project that costs less at launch and more every month can be the right choice or the wrong one, depending on how long you plan to keep it. The useful number is the total cost over 36 months.

5. Time-to-market and risk level

If you are validating a new market, launch speed is worth more than technical perfection: better to be online within a few weeks with some limitations and learn from real data. If instead you are taking an established business online, with customers who already know you, an error in production costs more than a delay and it makes sense to invest in analysis.

6. The roadmap for the next two years

Expansion abroad? B2B sales alongside B2C? New channels or marketplaces? Subscriptions? These need to be said now, even if they are only hypotheses. A platform chosen for the current scenario and blind to the next one is a migration already scheduled, you just do not know it yet.

The technologies on the table, in brief

PrestaShop

Open source, self-hosted, very strong at handling complex catalogues, variants and B2B logic, with a solid Italian community and a real presence among SMEs in our country. It requires technical oversight, whether in-house or entrusted to a partner. It is the technology where we have the greatest depth: we are a PrestaShop Expert ★★★ certified agency since 2011.

Our work on PrestaShop →

Shopify

SaaS subscription, very quick to get started, with managed infrastructure and security and a very rich app ecosystem. Excellent for D2C projects with a simple catalogue and a strong marketing push. The limits lie in customisation beyond a certain threshold and in the structure of recurring costs, which grow with revenue.

How we work on Shopify →

WooCommerce

A WordPress plugin, very widespread, the natural choice for anyone who already has a WordPress site with content and established organic traffic. Flexible thanks to the huge range of plugins, but that is precisely its fragility: a mature WooCommerce store is often a layering of plugins from different authors, with maintenance costs and incompatibility risks that emerge over time.

Adobe Commerce (formerly Magento)

Designed for very large catalogues, multi-store and multi-country scenarios, with advanced B2B logic. Extremely capable and equally demanding: licence costs, infrastructure and specialist skills make it sensible only above a certain company size. Below that threshold it is an expense that does not pay back.

Headless and custom development

A front end separated from the eCommerce back end, or a solution built from scratch. It makes sense in specific cases: deep integration with an existing digital product, extreme performance requirements, sales models that no standard platform covers. Outside those cases it is almost always complexity you pay for without receiving a proportionate benefit.

Typical scenarios and where they lead

B2B company with customer price lists and a management system to integrate.

Where it usually leads: PrestaShop or Adobe Commerce depending on size. The deciding factor is not the catalogue: it is the complexity of the pricing rules and the depth of the integration with the management system.

D2C brand launching a new line and needing to validate the market.

Where it usually leads: Shopify. Launch speed and the absence of maintenance are worth more than customisation at this stage.

Manufacturer with a technical catalogue and a product configurator.

Where it usually leads: PrestaShop with dedicated development, or a custom solution if the configurator is the heart of the product and not an accessory.

Publisher or media company with already strong organic traffic on WordPress.

Where it usually leads: WooCommerce, so as not to break the content ecosystem that is already generating the traffic. The cost of migrating the content often outweighs the benefit of a more robust platform.

Store already online that sells but no longer grows.

Where it usually leads: Nowhere, to begin with. In most cases the problem is not the platform but the conversion rate, the content or the acquisition channels. First you measure, then possibly you migrate. It is exactly the path we describe for an eCommerce that is underperforming.

Want an opinion on your specific case?

Thirty minutes, with no sales pitch: you tell us about your situation and we tell you how we read it.

No commitment: if now is not the right time, we will tell you.

The five mistakes we see most often

  1. Choosing on hearsay. "A friend recommended it" and "I read it on a blog" are not analysis. Someone else's case is not yours.
  2. Ignoring the recurring cost. Comparing two development quotes without comparing the three-year costs is comparing one number with another number that measures something different.
  3. Oversizing. Buying a technology designed for volumes you do not have, in the hope of having them. You pay for complexity today for a hypothetical benefit tomorrow.
  4. Undersizing the management. Focusing everything on the launch and not asking who will upload the products, handle the orders and update the content once things are running.
  5. Changing platform to solve a marketing problem. The most expensive case of all: you rebuild the store, you spend, and the conversion rate stays exactly the same because the problem was never there.

What if the choice turns out to be wrong?

It happens, and it is not a tragedy, but it is good to know in advance what going back costs. Changing platform means rebuilding the theme, rebuilding the integrations, replacing modules with different equivalents and mapping all URLs with 301 redirects so as not to lose the rankings you have earned. The catalogue and history migrate; the user experience is rebuilt.

The order of magnitude is similar to a new project, with the added constraint of not interrupting sales. That is why half a day of analysis before choosing is, in proportion, the investment with the highest return of the whole project.

How we approach the choice with you

We do not arrive with a recommendation in our pocket. The first conversation is for mapping the six variables above onto your real case, and putting them in writing: if we cannot justify a choice with a document you can challenge, that choice is not well enough founded.

If you are also wondering who to entrust the project to, an established organisation or an individual professional, that is a decision to take together with this one, not after it: we cover it in the comparison of collaboration models for an eCommerce project. You will find all the comparisons in the eCommerce comparisons section.

Frequently asked questions

There isn't one. There are platforms that are more or less suited to a specific catalogue model, set of integrations and way of managing the store. Anyone who answers this question with a flat name is describing their own specialisation, not your project.

It depends almost entirely on three factors: catalogue complexity, number and depth of integrations, and level of design customisation. A standard project on a SaaS platform and a project with a custom ERP integration differ by an order of magnitude. The serious way to answer is to start from your specifications, not from an average rate.

Yes, and it is a legitimate strategy if you know from the start that you will do it and you design the content architecture so that it is portable. It becomes a problem when it is a discovery instead of a plan.

The partner first, if you trust their method. An agency that recommends the same technology to everyone is not choosing: it is selling what it knows how to do.

Technically, almost always yes. The difference lies in the cost: whether a proven connector already exists, or one has to be developed and then maintained over time. It is one of the first things we check, because it can shift the budget significantly.

Continue with

PrestaShop and Shopify compared

The direct comparison between the two most discussed platforms.
Read →

Is an agency or a freelancer better?

Continuity, skills and risk: how to choose the supplier.
Compare →

Back to all comparisons

The full section with all the comparisons.
Go to the index →

Want to start from your own eCommerce data?

With Shop Analyzer you can analyse your online store yourself and see what emerges, before you even speak to us.

No commitment: if now is not the right time, we will tell you.

Have a question about a specific case?

Write to us: we reply with our reading of the situation, with no sales steps.

No automatic quotes: first we work out whether we can be of use to you.