Ecommerce: rent a template or build custom?
You want to start selling online, and you are stuck on the first question: rent a store on a hosted platform and be live next week, or build something custom that fits how your business actually works. The fear runs both ways. One path makes you one of thousands of near-identical shops. The other looks like months of development and a bill to match.
This is a strategic decision rather than a technical one, so it deserves an honest comparison. Here is what each path really gives you, what it takes away, and how to tell which one fits your plan.
What actually makes an online store work
Before the platform question, a reality check: the software is not what makes a store successful. Three things sit underneath it, and they matter regardless of which route you take.
Strategy. Who you are selling to, what your competitors already do well, and what you need the store to achieve in the next twelve months. Every later decision gets easier once these are written down.
Brand. Online, your visual identity carries the credibility that a physical shop gets from its location and staff. This is not decoration, it is the reason a stranger trusts you with card details, which is why we treat brand identity as part of the commercial work.
Experience. If a customer cannot find what they came for, or checkout feels like paperwork, they leave. The gap between a good and a bad checkout flow is measured directly in revenue, and it is the single highest-leverage thing to get right.
Hosted platforms: what you get
Hosted platforms work on a subscription model. You are renting a shop, and the fittings come with it: templates, payment providers, shipping integrations, hosting and security handled for you.
Speed to market. Pick a theme, upload products, start selling. Days, not months.
Low entry cost. A predictable monthly fee instead of a project budget.
No technical overhead. Updates, certificates and uptime are someone else's job.
Simple operation. Your team manages products and orders in an admin interface without needing a developer on call.
For testing demand, for a first product line, or for a business whose requirements genuinely are standard, this is the sensible answer, and there is nothing amateur about choosing it.
Where the rented model starts to hurt
The limits do not appear on day one. They appear when you grow.
You look like everyone else. Themes are shared. Building a distinctive brand experience inside one is possible only up to a point.
Functionality has a wall. Custom pricing rules, complex shipping logic, a deep ERP integration: either awkward, expensive, or simply not available.
Costs creep. Transaction fees, paid apps for capabilities you assumed were included, and tier upgrades as traffic grows. The advertised price is the floor.
You do not own it. Terms and pricing can change, and your answer is to accept or migrate. That is a business risk sitting under your main revenue channel.
Custom: what you are buying
A custom store is built around your business logic instead of the other way round, and you own both the software and the customer data. That is the whole proposition, and it is worth being clear about what it buys and what it costs.
On the plus side: no functional ceiling, an experience that is unmistakably yours, performance you control because there is no code you did not ask for, and integrations with whatever you already run. If your differentiator is a configurator, a loyalty mechanic or an unusual pricing model, this is the only path where it exists at all.
On the honest side: a higher up-front investment, two to six months from strategy to launch, and a dependency on the team that builds it. You are also signing up for maintenance, because a system that never gets updated becomes the legacy system you are replacing today.
How to decide
Four questions usually settle it.
Time horizon. Where should this store be in three years? Testing an idea points at renting. Building a market position points at owning.
Fit. Write down the five things your store must do that a competitor's cannot. If a hosted platform handles all five, rent. If it handles two, you already have your answer.
Total cost. Compare three years, not one month. Subscription plus transaction fees plus apps against a one-off build plus maintenance.
Risk. How much of your revenue is acceptable to run on infrastructure whose terms you do not control?
The same logic applies beyond ecommerce; we walked through the wider version in what a website actually costs, and if you already have a store that is underperforming, why your website is slow is usually the more urgent read.
How we run a custom build
We start with discovery rather than design: interviews and a workshop to map your business goals, your customers and the competitive picture, then clickable wireframes so the purchase flow can be tested before anyone writes code. Cutting this phase is the most expensive saving available in a store project.
Design and development then run in two-week cycles so you see progress continuously instead of waiting for a reveal. We build on a modern JavaScript stack with a headless CMS, which is what keeps the storefront fast and the content editable without a developer. The detail is on our web development and custom software pages.
Launch includes data migration, a redirect map for anything already indexed, and training your team on the system they now own. Then the work continues, because the first three months of real customer behavior always teach you something the plan did not.
If you want a straight answer about which side of this decision you are on, tell us what you sell and to whom, and we will say so.
Frequently asked questions
Is a hosted store platform good enough to start with?
Often yes. If you are testing demand or selling a straightforward catalog, a hosted platform gets you live in days at a predictable monthly cost. It becomes a problem when your requirements outgrow what the platform allows.
What does a custom online store cost?
Realistically from around EUR 2,000, rising with catalog size, payment and shipping logic, and every system it has to integrate with. The trade-off is that you own the result instead of renting it.
How long does a custom store take to build?
Two to six months from strategy to launch for most projects. The build itself is rarely the long part; discovery, design, integrations and testing are.
What are the hidden costs of a rented store?
Transaction fees, paid apps for functions that should be standard, and forced upgrades to higher tiers as traffic grows. The monthly fee you sign up for is rarely the monthly fee you end up paying.
Can I migrate from a hosted platform to a custom store later?
Yes, and many companies do exactly that once the platform starts limiting them. Plan the migration properly: product data, customer accounts, order history and a redirect map for every indexed URL.