For most small brands, the choice is between Shopify and PrestaShop Hosted, not PrestaShop Classic. Choose Shopify when you want hosted commerce and a theme plus a few apps can carry your store. Choose Classic only when a specific requirement needs access to the source code and someone is committed to running the installation. Hosted sits between them: PrestaShop’s software with technical management sold as a service, so the agreement decides what you still handle.

If you are weighing a custom build mainly because you want the store to look like your brand, you don’t need source code for that. Setka is our product, and it takes a third route: it builds the store from your brief and catalog inside its own e-commerce platform.

First find out which PrestaShop you’re being offered

PrestaShop sells two different things. Classic is source code you download for free and install. Hosted is presented as a ready-to-use store with technical management. A comparison of “free PrestaShop” with a Shopify subscription has usually mixed the two up.

With Classic, you or your implementation partner choose where the store runs and keep it running. With Hosted, the service agreement says which of that work moves to the provider. Neither the word hosted nor an agency’s PrestaShop badge tells you who fixes a module after an upgrade or maintains a custom theme. Ask.

Shopify Online Store includes the hosting. You configure the store and present your products with its themes, settings, and apps. You can commission custom work, but you don’t need any to start.

PrestaShop ClassicPrestaShop HostedShopify Online Store
How you startInstall the open-source softwareSign up for the Hosted serviceSubscribe to hosted commerce
Who runs the serversWhoever you or your partner chooseThe provider, within the service scopeShopify
Who keeps it updatedYou or your partnerWhatever the agreement coversShopify for the platform; you for the theme and apps
The customization questionWhat should the implementation change?What does this service support and maintain?Does it fit the theme, settings, an app, or custom work?
Choose it whenYou need code and deployment controlYou want PrestaShop without running it yourselfHosted commerce and its ecosystem fit your store

Code access pays off when you have a use for it

The open-source route lets an implementation team change the software itself. That matters when the business has a requirement that a hosted platform would make awkward or impossible.

A real requirement is specific: your warehouse system must receive a particular order status, or a purchasing rule must work a particular way. “We want flexibility as we grow” isn’t one. It turns a problem you might have later into a maintenance commitment you definitely have now.

Shopify trades some control over infrastructure and core software for a platform you never deploy. That’s often a good trade. Its theme editor and customization tools let you make changes without code, and it offers prompt-based creation and AI assistance too, so this isn’t a choice between a platform with AI and one without. Its current plans are on Shopify’s pricing page. When a requirement goes beyond those tools, an app or custom work may still be the answer. Decide by the behavior you need, not by a general verdict that one platform is flexible and the other closed.

The second change shows what you’re buying

Take a hypothetical ceramics brand with mugs, bowls, and vases. At launch it needs accurate dimensions, good photographs, delivery information, and an easy way to browse. A month later it wants a housewarming collection with advice on choosing a gift.

That second request changes what shoppers see: a new category introduction, a different set of featured products, clearer gift guidance. It doesn’t change how orders or payments work. Commissioning custom commerce software for it would solve a bigger problem than the brand has.

On PrestaShop, who makes that change depends on the installed theme, the modules, the editor, and the contract with your partner. On Shopify, it depends on the theme and the apps you’ve added. Either way, a managed server doesn’t write the gift guidance or decide which products to feature.

Owning the source code is one kind of control. Being able to make and publish the next useful change yourself is another, and in our view it’s the one proposals underweight, even though a store like this one uses it every month. Pay for code access when you need it. Judge every proposal on the second change as well as the launch.

What each route costs to run

Price the whole setup, not the license line:

  • The platform or service, hosting, and domain.
  • The theme and the modules or apps you actually need.
  • Initial design, configuration, and integrations.
  • Updates, compatibility fixes, support, and later changes.
  • Payment processing and any platform fees.

Classic removes the software license and nothing else. For a small brand without a code-level requirement, it is rarely the cheap option it looks like: the download is free, the person who installs, updates, and fixes it is not. Shopify includes hosting in the subscription. Apps, a paid theme, or custom development add to it, though a paid theme is a choice, not a requirement.

For Hosted, read the subscription and the implementation proposal together. A price that covers infrastructure but not custom-module work buys a different service from one that covers both. We’d take a clearly bounded scope over a lower starting price. Current prices are on PrestaShop’s site and Shopify’s pricing page.

Which one we would choose

Choose Classic when a concrete commerce or infrastructure requirement needs source access and you have a capable owner for the installation. A good technical partner is an asset; use them for work the business actually needs.

Choose Hosted when you want PrestaShop and its stated technical service covers your requirements. Get the support and customization scope in writing, and don’t assume it includes every Classic module or every promise an agency made.

Choose Shopify when its commerce features, app ecosystem, and theme workflow fit your operation and you want the platform to handle hosting. For a conventional store, it saves you commissioning the infrastructure.

Choose Setka when the real project is turning your products and brand into a store you can keep changing. Setka builds the homepage, category pages, product-page templates, navigation, and cart from your brief and catalog. For the housewarming collection, you’d open the page, describe the gift guidance and which products to feature, check the preview, and publish. Exact wording you edit directly, and every version of the store is saved, so you can go back. Products, checkout, paid orders, and inventory run in the same platform, and there is no theme code for you to maintain. That also removes the theme and implementation contract from the presentation budget.

Setka doesn’t run PrestaShop modules. If an integration or a purchasing rule decides your project, send the exact requirement to contact@getsetka.com and we’ll answer yes, no, or not yet. Requests go straight to the people building Setka.

If the store itself is what you want built, start with its audience, products, and the experience you want shoppers to have. Our store briefing guide turns that into input Setka can build from, or you can start your store directly.