How much does a website cost in Italy in 2026
The method for reading a quote and comparing two offers on scope, not on the total.
Blog · Platforms
Shopify vs a custom website: how to choose in 2026
The platform is not the strategy. The real question is how you sell, who buys and how much of your way of working has to fit inside the site. Platform, costs and future freedom follow from there.
The wrong question
“Shopify or custom?” puts the tool at the centre. The useful question puts the way you sell at the centre.
A store with a hundred standard products, public prices and one warehouse has different needs from a company selling to customers with negotiated price lists, minimum quantities and ERP integration. The first can launch on Shopify in a few weeks. The second risks spending months adapting a platform that was not built for that workflow.
Before choosing, answer four questions: what do you sell, how do you price it, who buys it and who handles the order afterwards. The answers already rule out half the options. The platform is a consequence, not a premise.
This comparison does not crown a winner. It is here to show which choice costs less over time, not which one looks more modern in a presentation.
Where Shopify wins
Shopify is strong when commerce is standard and speed to launch matters more than customisation.
- Time to launchTheme, catalogue and payments are already connected. A first store can go online without building the infrastructure from scratch.
- Standard catalogueProducts, variants, images, collections and discounts fit the platform’s models without forcing.
- Payments and checkoutThe most delicate part of commerce is handled by the platform, with less integration and maintenance work.
- Themes and appsThere is a broad ecosystem. Many features are bought rather than built, though every app adds a subscription and another piece to maintain.
- Hosting and securityUpdates, certificates and infrastructure are the platform’s job. For a team without an IT department, that is a real advantage.
- External channelsMarketplaces, social and physical stores connect with less friction. If you sell across channels, the ecosystem helps.
Where custom wins
Custom makes sense when the way you work is the competitive advantage, not a detail to adapt.
- Prices and configurationsCustomer price lists, tiered discounts, rule-based configurations, complex quotes: the site can follow the rule instead of working around it.
- B2B and ERPOrders, stock, credit, payments and invoicing can talk directly to the ERP and accounting, without duplicate data entry.
- Performance and scaleVery large catalogues, unusual search and high-volume flows: the architecture is designed around the real load.
- Content and logicCalculators, configurators, private areas and content that changes by customer do not have to be reduced to a plugin.
- Ownership and lock-inCode and data stay yours. You do not depend on a subscription, an app or the rules of a platform that can change.
- SEO and accessibilityURLs, structured data, performance and markup are controlled from the start. You do not have to hope a theme or an app handles them well.
Comparison by dimension
Neither column is better in absolute terms. The question is which dimension weighs most in your model.
| Dimension | Shopify | Custom |
|---|---|---|
| Time to launch | Fast with a theme and a ready catalogue. | Depends on scope and integrations. |
| Catalogue | Standard, with variants and collections. | Any structure, however complex. |
| Pricing | Standard rules and third-party apps. | Any rule, including per customer. |
| B2B | Features and apps, with limits to check. | Built around the real process. |
| Integrations | Platform apps and APIs. | Direct connections to ERP, CRM and accounting. |
| SEO | Good if configured carefully. | Full control over URLs, markup and performance. |
| Performance | Depends on theme, apps and catalogue. | Depends on architecture and the work done. |
| Ownership | Data can be exported, but the store lives on the platform. | Code and data stay with the client. |
| Maintenance | Platform and app updates. | A maintenance plan and managed updates. |
The third option: hybrid
Shopify for commerce, a custom application for what the platform cannot do. It only works if the two worlds talk.
A common option is to keep Shopify as the sales engine and build an application around it for configurators, special prices or ERP integration. The customer sees a unique experience; the platform handles cart, payments and orders.
Hybrid makes sense when the standard part is genuinely standard and the special part is limited. If everything is special, the result is a distributed system with two maintenance plans and two points of failure. If nothing is special, Shopify alone is enough.
The main risk is synchronisation: products, prices, stock and orders need one source of truth. Without a data owner, hybrid becomes a more expensive way to have the same problems.
Total cost of ownership, not subscription
The monthly fee is the visible part. The real comparison includes everything needed to run the store.
- Shopify: subscription, theme, apps, initial development, migration, content, payment fees and app maintenance.
- Custom: analysis, design, development, hosting, security, backups, maintenance, improvements and internal time to coordinate them.
- Both: photography, copy, translations, customer support, training and analytics tools.
- The hidden cost: your team’s time. A system that needs ten manual steps a day costs money even when the subscription is low.
- The exit cost: migrating data, URLs and integrations has a cost. Ask from day one how everything is exported.
Compare scenarios, not isolated quotes. Ask both suppliers for the three-year cost, including maintenance, apps and internal hours. That is the number that matters.
Migrate without losing SEO
Whether you move to Shopify or to a custom build, migration is a project within the project. URLs are the part most often forgotten.
Map the URLs
List the pages that receive traffic and those with external links. Every old URL needs a new destination, not a generic home page.
Prepare the redirects
One 301 redirect per URL, tested before launch. Redirect chains and 404s are the fastest way to lose positions.
Move metadata and content
Titles, descriptions, copy, images and structured data. Do not let the new platform generate everything by itself: content is an asset.
Migrate products and data
Codes, variants, prices, stock, customers and orders. Check which fields get lost and decide what should not be migrated for privacy or obsolescence reasons.
Check analytics and Search Console
Tracking, goals, events and domain verification. After launch, monitor 404s, redirects and queries for at least one indexing cycle.
Test before switching off
Try orders, payments, email, returns and edge cases. Keep the old site reachable until the new one has passed the tests.
Quick decision matrix
A short guide to orient yourself.
| Scenario | Likely choice |
|---|---|
| Standard catalogue, fast launch | Shopify |
| Custom flows, ERP integrations | Custom site |
| Tight budget, strong identity | Hybrid |
Note. The choice depends on scope and team.
Frequently asked questions
Is Shopify better for SEO?
Neither Shopify nor custom is automatically better. SEO depends on URLs, metadata, content, performance and structured data. Shopify can do well if configured carefully; custom gives more control, but also more responsibility.
Can I sell B2B with Shopify?
Yes, Shopify has B2B features. Before choosing, check customer price lists, payment terms, credit, minimum quantities and ERP integration. If those rules are central, adaptation costs can change the comparison.
How much does a custom site cost compared with Shopify?
We do not publish figures because it depends on scope. The correct comparison is the three-year total cost: subscription, apps, development, migration, maintenance and internal time. A low subscription with many apps and manual work can cost more than a custom project.
Can I migrate from Shopify to a custom site?
Yes. You need data export, a URL map, redirects and checks on payments and integrations. The delicate part is not copying products: it is keeping traffic, orders and customer history.
Do I need a headless architecture?
Only if you have a precise need: highly custom experiences, multiple channels or unusual performance requirements. Headless adds complexity, cost and maintenance. If you cannot explain the benefit in one sentence, you probably do not need it.
Who owns the store data?
Your data must stay yours. Ask how to export products, customers, orders and content and what happens if you change platform. Ownership is proven in practice, not in the contract.
Choose by model, not by logo
Tell us what you sell, how you price it and who handles orders. We will say where Shopify is enough and where custom pays off.