Skip to main content
Own shop · No rented platform

Building your own ecommerce without renting it from Shopify, PrestaShop or anyone

This is not about purism. A rented platform takes a cut of every sale, decides what you can and cannot do, and owns the place your business lives in. There are cases where that pays off, and cases where it does not. Here are both, with one of our own shops as the example.

An own online shop running, with its catalog and payment gateway

Let us start with what we will not say: that Shopify is bad. It is not. For a great many businesses it is exactly right, and building something custom would be an expensive mistake. The honest conversation is not «platform yes or no», it is what you are paying and what you are giving up, and whether in your specific case that adds up.

What you actually pay

The monthly fee is the least of it. What piles up are three layers: the fee, the transaction cut if you do not use their gateway, and the apps. That third one is the surprise: a shop with six or seven apps — subscriptions, reviews, invoicing, shipping, marketing — pays more in apps than in the platform itself, and each app is another fee, often one that grows with your volume.

Do the arithmetic before arguing about anything: add twelve months of platform, fees and apps, and compare it with the one-off cost of what you actually need. Sometimes the platform wins clearly. Sometimes the answer is uncomfortable.

What you give up without noticing

Three concrete things. The limit of the possible: if your business needs a pricing rule, a returns flow or a shipping calculation the platform does not contemplate, there is no technical conversation, there is a «you can't». Performance, because every app that touches the storefront tends to inject its JavaScript into your page and your speed stops being your business. And the data: your customers, your orders and your history live in a system that costs a project to leave.

When renting is the right call

Bluntly: when you are validating whether the product sells. When your catalog is small and your operation is the standard one. When you have nobody to maintain anything and do not want to. And when what is holding you back is not the site but demand: building a bespoke shop for a business that does not sell yet is solving the wrong problem with great style.

When your own pays off

When operations outrank the storefront. If you sell on marketplaces as well as your own site, if you work with several carriers on different rules, if your price depends on something the platform cannot compute, or if volume already makes the fees hurt, then the storefront stops being the problem and the system behind it becomes everything. There, building your own is not a luxury: it is what makes the business run without somebody reconciling by hand every night.

One of our own shops, built that way

This is not a theoretical example. eclipseando.com is built entirely without a rented platform: a custom front end with 8,132 municipality pages in seven languages, each language on its own URL; a custom FastAPI back end acting as till, warehouse and counter, with 1,370 automated tests; and four logistics providers integrated, each speaking its own way. Apple Pay and Google Pay included. We tell the whole thing, piece by piece, in the eclipseando case.

What matters about that case is not the numbers: it is that none of those pieces would have fitted a standard platform without a fight. The 8,132 pages compute themselves from data, they are not written one by one. And the four logistics providers are handled from one place, without one app per provider charging separately.

And a third way almost nobody mentions

You do not have to choose between renting everything and building everything. The combination we recommend most is leaving the storefront where it is — or building it simple — and putting operations in Odoo: stock, orders, invoicing, carriers and marketplaces in one place, with the site as just another channel. That way the day you change storefronts nothing collapses, because the business did not live there. It is developed in the five layers of a shop and in when to use Odoo Website and when not to.

Frequently asked questions

Is a custom ecommerce less secure?

Not for being custom. It is less secure if nobody maintains it, exactly like a rented shop with eight abandoned apps. What you should not do is touch payments: use a certified gateway and the card number never passes through your system.

What about SEO? Is it lost when leaving the platform?

It is lost if done badly. It is kept by preserving URLs or setting 301 redirects one by one. Boring work and non-negotiable; explained in migrating from PrestaShop to Odoo.

Who maintains it afterwards?

That is the right question and it must be answered before starting, not after. We hand over the code and maintain it if you want, but what we do not do is hand over something only we can touch.

Useful links inside FlexigoTech

Web and ecommerce developmentShops from scratch, with logistics and payments wired inThe eclipseando case, piece by piece8,132 municipality pages, seven languages and four logistics providersThe five layers of a shopThe order to build in so nothing has to be redone

What we do about this

Shopify connectorWhat it does, screenshots, versions and price.

Deciding whether to rent the shop or build it?

Tell us what you sell, how many references you have, where you sell today and what you spend monthly on platform and apps. We will do the arithmetic with you and tell you what fits, even if the answer is that you should stay where you are. Write to comercial@flexigobe.com or book a call.

Talk to an engineer