Ecommerce as a service, explained

Ecommerce platforms sell you a whole site with a shop inside. Ecommerce as a service sells you only the shop and leaves the site to you. For anyone who already has a website they like, the second model is the one that fits.

The difference in one picture

A platform: your website lives inside their system. Themes, pages, blog, shop, all theirs. You customise.

A service: your website lives wherever you built it. The service provides the selling layer through an embed or an API. You integrate.

What the service layer contains

When a service beats a platform

When a platform still wins

Large catalogues with variants and inventory across locations, teams working in an admin all day, marketplaces and POS. Those are what platforms are for.

How AddTheShop does it

One script tag for the embed, a storefront API for custom frontends, a merchant API and MCP server for management, Stripe Connect for payments into your own account. No monthly fee; 2% per sale.

Questions

Is ecommerce as a service the same as headless commerce?

Close cousins. Headless describes the architecture (frontend separate from commerce engine). Ecommerce as a service describes the business model (rent the engine). AddTheShop is both.

Can I migrate off a service later?

Your products are a short list and your payments are already in your Stripe account, so yes, easily.

Who is the merchant of record?

You are. AddTheShop never holds your money.

Sell on the site you already have.

Products, cart and Stripe checkout from one script tag. Free to start, 2% per sale. Your AI installs it and runs it.

Add the shop

See the live demo

More guides