The Best Ecommerce Platform Depends On What You Sell

Every list of the best ecommerce platforms is written by somebody with a horse in the race, and this one is no exception. So here is the bias up front: we build one. What follows is still worth reading, because the honest answer to "what is the best ecommerce platform" is that the question is wrong, and the useful version of it is answerable in about five minutes.

There is no best platform. There are four shapes of platform, and the one that fits depends on two things about you: who is going to build the storefront, and what you sell.

The four shapes

1. Hosted, all in one

The platform runs the storefront and the backend together. You pick a theme, install apps for anything the core does not do, and you are selling the same week. Shopify is the obvious example, and BigCommerce and Squarespace sit in the same shape.

Choose this if nobody on your team writes code. That is not a consolation prize. Getting a real store online without a developer is a genuinely hard problem and these products solve it well.

The constraint is that the theme is the ceiling and the app store is the extension model. When you need behaviour nobody has built an app for, the answer is usually that you cannot have it.

2. Self-hosted and open source

You run the software yourself. WooCommerce on WordPress is the common one; Magento, now Adobe Commerce, is the enterprise end of it.

Choose this if you want to own and modify everything and you have somebody to keep it patched. The code is yours to change, which is real freedom.

The constraint is that hosting, updates, security and performance become your job. Plenty of businesses take this on and then quietly discover they bought a maintenance contract with a store attached.

3. Headless and API-first

The backend is a service with an API. The storefront is an application your developers write, in whatever framework they already use, and it talks to the backend over HTTP. This is the shape we build, and Commerce Layer, Medusa and the headless tiers of the larger platforms are also in it.

Choose this if you were going to write a front end anyway. That is the whole test. If a developer is building the storefront regardless, then having the catalog, orders, payments and shipping already solved behind an API is a large amount of work you do not have to do.

The constraint is that you are taking on the storefront. There is no theme to fall back on and no app store to fill a gap. If nobody is writing that code, this shape is worse for you than the first one, not better.

4. Fully custom

Everything written for you, including the parts every store has.

Choose this if your commercial model genuinely does not resemble a shop. That is rarer than it feels from the inside. Most businesses that reach for this need one unusual thing and a completely ordinary catalog and checkout underneath it, which is shape three.

The question that actually decides it

Before comparing features, answer this: who writes the storefront?

If the answer is nobody, you want shape one and the rest of this article does not apply to you. If the answer is a developer on your team or an agency you are already paying, shapes one and two are both going to frustrate that person and shape three exists for them.

Feature comparison tables are mostly noise at this stage. Every serious platform has a catalog, a cart, discounts and a checkout. The differences that matter are structural, and the structure is decided by that one question.

The second question: what do you sell?

This one has a hard edge to it, and it is the reason a lot of people end up reading articles like this one in the first place.

Every hosted platform publishes a list of businesses it will not serve, and decides which payment methods a restricted category may use. Hemp, THCA and CBD sit in or near that boundary for most of them. Those policies are theirs, they change, and a competitor's summary of them is not evidence, so read the current version on their own site before you build anything on it.

What that means practically: if you are in a category a platform restricts, the feature comparison stops mattering. The best ecommerce platform for you is one that will still have you as a customer in six months, and that is a different question from which one has the nicer theme editor.

Where we fit, and where we do not

dashfordevs is shape three. One backend behind as many storefronts as you want, with the catalog, orders, customers, payments and content behindone typed API, and the regulated categories treated as a supported case rather than an exception. If that description matches your situation, thecomparison with a hosted platform goes into the detail.

We are the wrong answer if nobody on your team writes code. We are also the wrong answer if you depend on a large installed base of apps from somebody else's ecosystem, because those integrations are theirs and they do not travel. Both of those are common, and in both cases shape one is genuinely the better buy.

How to actually decide

• Write down who builds the storefront. Not who could. Who will, this quarter.
• Check the acceptable use policy before the feature list, on the platform's own site, if you sell anything near a restricted category.
• Ask what leaving looks like. Whether your catalog, customers and orders come out through an API you can call yourself is a better question than any feature.
• Ignore the rankings, including this one. Four shapes, two questions. The answer falls out.

If shape three is where you land and you want to see what building against an API actually looks like, theecommerce API documentation is open and needs no account to read, andthe developer case is the longer version of that argument.