What does an online shop cost in Switzerland? A 2026 budget model
A practical budget model covering planning, development, ERP, payments and operations across three ecommerce scenarios.
By Ralph Heezen
A webshop comprises several cost categories. Standard checkout differs from portals with customer pricing, live stock and ERP workflows. Define these responsibilities before comparing quotes.
EverDigital’s documented entry range for scoped website and webshop projects is CHF 5'000–15'000+, excluding VAT. Custom integrations, configurators and multi-tenant portals are scoped separately.
Three planning scenarios#
| Scenario | Planning range | Assumptions |
|---|---|---|
| Focused B2C/D2C shop | CHF 5'000–15'000+ | Clear catalogue, established checkout, one language, limited migration |
| Shop with custom ERP/tool bridge | Shop budget plus CHF 12'000–40'000 | Mapping, reads/writes, errors and monitoring |
| B2B portal | From about CHF 25'000; self-service from CHF 45'000; complex multi-tenant CHF 80'000–150'000 | Authentication, customer data, documents, approvals and workflows |
These are EverDigital planning ranges, not market statistics or fixed quotes. Design, data quality, sources, migration, languages and acceptance requirements affect price.
Cost categories#
1. Discovery and architecture#
Define buyers, range, source ownership, countries, languages and post-checkout workflows. The outcome specifies platform, flows, page types and deliverables. Migration also needs a URL and data inventory so valuable pages do not disappear.
2. UX and frontend#
Navigation, search, products, cart, checkout and accounts depend on variants and rules more than screen count. A technical configurator is different from three standard product options. Headless can improve flexibility but adds architecture; standard platforms may fit simpler processes. Our ecommerce service assesses this before choosing technology.
3. Product data and content#
Variants, media, attributes, stock, shipping classes, tax, translations and product copy need clear sources. Quotes should specify who supplies data, migrated types, languages, currencies, retained metadata and content approvals. Unclean tables add mapping and cleansing work.
4. Payments and transactions#
Assess TWINT, cards, PostFinance, invoices or QR invoices by provider. Include fees, refunds, partial cancellations, currencies, fraud checks and settlement reconciliation. Actual contract rates belong in the business case.
5. Integrations#
| Data | Ownership question |
|---|---|
| Products and variants | ERP, PIM or shop? |
| Prices | General, customer or group? |
| Stock | Periodic or near-live? |
| Customers | Which system assigns stable IDs? |
| Orders | Draft or approved ERP order? |
| Refunds | How do status and value return? |
An integration includes authentication, mapping, retries, duplicates, monitoring and recovery. Bexio preferably uses OAuth 2.0, with draft-first writes where appropriate. Customer-specific rules may need the B2B service.
6. Indexable pages, analytics and migration#
Architecture determines indexability, links, canonicals, schema, sitemap and loading. Migration adds redirects and old/new URL comparison. Define product-view, cart, checkout, purchase and refund events. Consent and identifiers limit attribution; complete channel attribution cannot be guaranteed.
One-off and ongoing costs#
A three-year comparison should include:
| Item | Pattern | Main drivers |
|---|---|---|
| Discovery, UX and build | One-off | Scope and approvals |
| Migration and cleansing | One-off | Data, URLs and languages |
| Integration | Build plus operation | Sources, volume and errors |
| Hosting/database | Ongoing | Traffic, media and availability |
| Licences | Ongoing | Platform, users and functions |
| Payments | Per transaction | Provider and contract |
| Monitoring/support | Ongoing | SLA and changes |
| Technical maintenance and development | Ongoing or sprints | Integrations, releases and new features |
Connector operations are modelled at CHF 290–1'500/month depending on number, SLA and changes. This is not a mandatory shop surcharge. Hosting, licences and payments are listed separately.
Example#
A single-language D2C shop with a clear range and standard checkout can start in the CHF 5'000–15'000+ range without custom ERP sync. A later bridge is a separately scoped flow.
A portal with customer pricing, documents and approvals starts from a different basis, around CHF 25'000, rising with self-service and multi-tenancy. The difference is business logic, permissions and tests.
What a comparable quote specifies#
- Customers, countries, languages and revenue model.
- Product, category and content types.
- Platform and architecture reasoning.
- Leading source per data type.
- Payments, shipping, tax and refunds.
- Migration, redirects and technical acceptance criteria.
- Analytics, consent and ownership.
- Device and integration tests.
- Hosting, licences, monitoring and SLA.
- Assumptions, exclusions and scope changes.
When a smaller launch fits#
A focused product range, one market and standard checkout can test a business case. Document future integration boundaries. If ERP prices, stock or approvals are essential immediately, deferring them may cost more than planning correctly from the start.
Choose the general ecommerce service or B2B portal specialisation according to the commerce, data and operational responsibility required.
Define your webshop scope
Review the complete scope, from planning to ERP and payments.
View ecommerce service