For many retailers, a website builder is the fastest and most affordable way to launch their first online store. A shop system with a broader range of features is usually worth it when your product range, business customers, integration needs, or international sales require more than what the standard website builder offers—or when additional apps and revenue-based fees drive up costs. This guide explains what website builders excel at, where growing stores reach their limits, ten signs it’s time to switch, and how the transition works, including data migration and redirects.
At a Glance
- Modular platforms score points for a quick launch, low upfront costs, and included hosting—often the right choice for testing a business idea.
- Limitations typically arise with large product ranges featuring variants, when dealing with business customers (net prices, tiered pricing, VAT ID numbers), with inventory management and marketplaces, and when selling to other EU countries.
- Growing costs: Apps and revenue-based fees increase as the storegrows. A 1% revenue fee on €50,000 in monthly revenue amounts to €6,000 per year.
- The system must be able to displaylegal requirements at checkout, such as the order button and, as of June 19, 2026, the right of withdrawal (§§ 312j, 356a BGB).
- Right to Switch: For data processing services such as Software-as-a-Service, the EU Data Act has regulated the right to switch providers since September 12, 2025; as of January 12, 2027, switching fees are prohibited (Articles 25 and 29 of Regulation (EU) 2023/2854).
- When moving, permanent redirects (301) forward all traffic from the old address to the new one. Google recommends this and notes that there may be temporary fluctuations in search rankings.
Status of legal texts and prices: October 4, 2026. The legal notices do not constitute legal advice.
What is the difference between a website builder and an e-commerce platform?
The line between the two is blurred, as e-commerce systems are also available as rental packages that include hosting. The differences lie primarily in the out-of-the-box feature set, in customizability, and in how additional features and interfaces are integrated. The table describes typical characteristics; in individual cases, the specific offer determines the details.
| Feature | Typical online store builder | Typical e-commerce system |
|---|---|---|
| Setup | in the editor using templates, no technical knowledge required | With more settings, often with support from the provider or an agency |
| Pricing model | Low base fee; additional features via apps, sometimes with revenue-based fees | Higher base fee in a subscription package or license plus maintenance; more features included as standard |
| Features | Basic features for selling to individual customers | Additional features include customer groups, B2B pricing, multilingual support, and multiple stores |
| Expansion | via the provider’s app marketplace | via modules, interfaces, and custom programming |
| Hosting and Updates | Included in the price | Included in the rental package; if self-hosted, this is the responsibility of the merchant or a service provider |
| Design | within the scope of the templates and the editor | From standard templates to custom designs |
What do online store builders do well?
- Quick launch: Templates, the editor, and pre-configured payment methods let you get a simple online store up and running in no time.
- Low upfront costs: A low monthly fee with no need for your own server makes getting started predictable.
- No technical effort required: The provider handles hosting, updates, security, and SSL certificates.
- Low risk when testing the waters: If you want to test a product idea, you can make your first sales without a large upfront investment.
For a store with a manageable product range and individual customers, a website builder can therefore suffice for years. Switching isn’t automatically worthwhile once you reach a certain sales threshold, but rather when your requirements grow.
Where do growing stores using a website builder reach their limits?
The following areas are typical growth thresholds. How high they are depends on the provider and the plan you’ve signed up for.
Large product range and many variants
As the product range expands, so does the effort required to maintain it. Things become critical when a plan limits the number of products or variants, when items with multiple attributes—such as size, color, and material—are difficult to list, or when prices and inventory levels cannot be updated via import. Check how many variants are possible per item, whether import and export via CSV or an API are available, and whether filters can be created based on these attributes.
Business Customers (B2B)
Business customers expect different prices and processes than retail customers: net prices, volume discounts starting at certain quantities, customer groups with their own terms, and purchase on account. The Price Indication Regulation (PAngV) governs only price indications to consumers (Section 1(1) PAngV). Therefore, anyone serving both retail and business customers in the same store generally needs both formats: total prices for consumers (Section 3(1) PAngV) and net prices for businesses.
When selling to businesses in other EU countries, the VAT identification number must also be provided. A tax-exempt intra-Community supply requires, among other things, that the recipient use a valid VAT ID number from another member state (Section 6a(1), sentence 1, no. 4, UStG); the Federal Central Tax Office confirms the validity upon request (Section 18e of the German Value-Added Tax Act (UStG)). Our article on B2B features in the shop system outlines the functions a shop should offer for business customers.
Inventory Management, Marketplaces, and Interfaces
If you also sell on marketplaces or use an inventory management system, you need the same inventory data across all platforms. If there’s no direct integration, inventory levels must be reconciled manually or linked via third-party services, which incur their own fees. Check which inventory management, accounting, payment, and shipping service providers are already integrated, whether an open interface (API) is available, and who manages the connection if issues arise.
Multiple Languages and Shipping Destinations
If you sell to other EU countries, you’ll need translated content, shipping zones, and the correct sales tax. If distance sales to private customers in other EU countries (together with certain services) exceeded €10,000 in the previous or current calendar year, the VAT rate of the destination country generally applies (Section 3c(1) and (4) of the German Value-Added Tax Act (UStG)).
Sales can then be reported via the special One-Stop-Shop (OSS) taxation procedure; participation must be registered with the Federal Central Tax Office (Section 18j(1) of the German Value-Added Tax Act). To do this, the online store must apply the correct tax rate for each country and be able to break down sales by country.
Legal Obligations at Checkout
The extent to which you can modify the ordering process itself depends on the system. It is crucial that new obligations are implemented in a timely manner:
- Order button: labeled “Place order with obligation to pay” or an equivalent, unambiguous phrase (Section 312j(3) of the German Civil Code (BGB)); without this wording, the contract is not concluded (Section 312j(4) BGB).
- Right of withdrawal: As of June 19, 2026, a “Withdraw from Contract” button that is constantly available, prominently displayed, and easily accessible during the withdrawal period (§ 356a BGB).
- EU Warranty Notice: As of September 27, 2026, the harmonized notice regarding statutory warranty rights (Art. 246a § 1 (1) No. 11 EGBGB).
Check whether your system includes these features by default or if you need an additional app for them. Our guide to legal texts in online stores summarizes all the mandatory information an online store must provide.
SEO, Load Time, and Control Over URLs
When it comes to search engine visibility, what matters is how much you can control yourself: page titles and descriptions, descriptive URLs, redirects, structured data, and load time. Add-on apps can integrate their own scripts; therefore, measure the load time after every extension is installed.
Having control becomes crucial, at the latest, when you migrate your site. If you can’t freely choose URLs or set up a large number of redirects, any future changes will be more time-consuming.
Data Export and Dependence on the Provider
The longer a store has been running, the more valuable its data becomes: customer accounts, order history, product descriptions, and images. Therefore, ask early on what data you can export and in what format.
For data processing services—which the EU Data Act explicitly includes Software-as-a-Service (Recital 81)—fixed rules for switching providers have been in effect since September 12, 2025. The contract must provide for a notice period of no more than two months to initiate the switch, a transition period of generally no more than 30 calendar days, and a data retrieval period of at least 30 calendar days (Art. 25(2) of Regulation (EU) 2023/2854). Data and assets of the provider that are protected by intellectual property rights or as trade secrets are not considered exportable data (Art. 2, No. 38).
As of January 12, 2027, no switching fees may be charged for switching providers; until then, only the direct costs incurred may be charged (Art. 29). Regular usage fees and agreed-upon penalties for early termination do not count as switching fees (Art. 2, No. 36). If in doubt, have an offer reviewed to determine whether it falls under this provision; background information can be found in our article on the EU Data Act.
Costs That Grow With Revenue
Apps for additional features and revenue-based platform fees can make a store more expensive with every step of growth. Here’s an example calculation: With €50,000 in monthly revenue, a 1% revenue fee amounts to €500 per month or €6,000 per year—in addition to the payment provider fees that apply to every system.
Therefore, compare the total annual costs against your projected revenue: base fee, apps, revenue-based fees, payment processing fees, and the one-time cost of switching platforms. Our guide “How Much Does an Online Store Cost?” shows you how to do this; the article “E-commerce Platforms Without Revenue Sharing” explains the long-term benefits of a model without revenue sharing.
10 Signs That Your Store Is Outgrowing Its Modular Platform
A single sign isn’t necessarily a reason to switch. If several apply, it’s worth comparing the total costs and features with those of a shop system.
| # | Sign | What You Should Check |
|---|---|---|
| 1 | Apps for basic functions account for a large portion of the monthly costs. | Which of these functions are included as standard in other systems? |
| 2 | Revenue-based fees increase with every successful month. | Total annual cost based on your projected revenue |
| 3 | Product ranges or variants hit pricing limits or are cumbersome to maintain. | Variant model, import and export, filters |
| 4 | Business customers ask for net prices, tiered pricing, or their own terms. | Customer Groups, Tiered Pricing, Net Price Display, VAT ID Verification |
| 5 | You manually reconcile inventory levels between the online store, the ERP system, and marketplaces. | Direct integrations instead of third-party services |
| 6 | Your distance sales to other EU countries are approaching €10,000 per year. | Tax rates by country, OSS reporting, languages, shipping zones |
| 7 | You cannot implement the new mandatory information in the checkout process on your own. | Order button, cancellation option, and warranty notice included by default |
| 8 | Addresses, redirects, or page titles cannot be controlled the way you need them to be. | URL structure, large numbers of redirects, structured data |
| 9 | Invoices, shipping labels, and returns are generated outside the store in spreadsheets. | Order management, receipts, shipping interfaces |
| 10 | You don’t know how to transfer your data when switching platforms. | Export formats, notice period, and transition rules in the contract |
How does the transition from a modular system to a shop system work?
A smooth transition follows six steps. Your current online store can remain online until the new one has been fully tested.
- Assessment: What data, features, interfaces, and contracts are currently in place? Note the notice period for your current provider and clarify what data they will provide and in what format.
- Select and test the system: Compare total costs, standard features, interfaces, support, and export options. Data protection considerations include server location, a data processing agreement (Art. 28 GDPR), and the issue of transfers to third countries; details can be found in our article on GDPR-compliant online store systems.
- Data migration: Products—including categories, variants, and images—as well as customer accounts and orders will be migrated. Whether customers retain their existing passwords depends on the source system; be sure to bring along proof of consent for the newsletter (Art. 7(1) GDPR).
- Plan Redirects: Create a list of all old URLs for products, categories, and content pages, and assign the appropriate new URL to each one. Google recommends permanent server-side redirects such as 301; update internal links and the sitemap to point to the new URLs.
- Test phase: Place one test order for each payment and shipping method, including emails, receipts, legal texts, mobile view, and a random sample of the redirects.
- Switchover and Follow-Up: Switch over the domain, activate payment and shipping providers for live operation, and monitor indexing and error pages in Google Search Console. Do not terminate the old contract until everything is up and running.
Schedule the switchover for a period of low sales volume, if possible. Google estimates that it takes several weeks or longer for medium-sized websites for the new URLs to replace the old ones in search results, and recommends keeping redirects in place for as long as possible—at least one year.
How XONIC Supports the Transition
The XONIC Shop System includes B2B features as standard: customer groups, tiered pricing, net price display, and automated VAT ID verification. Each package includes integration with 19 payment providers offering over 50 payment methods and more than 11 shipping carriers; Inventory management (14 integrations via the xoPort data interface) and marketplaces can be added starting with the Professional package. Packages start at €149 per month with annual billing plus VAT, with no revenue share (as of October 2026).
Data migration from your existing store is available as a service at a fixed price starting at €1,200 plus VAT: Products, customers, and orders are transferred; existing SEO URLs are redirected to the new ones via 301 redirects; and before going live, a test migration demonstrates the results using real data. Details are available on the Data Migration When Switching Shops page.
You can try out the system in advance in a free 30-day test environment with sample data. All packages are listed on the pricing page; fact-based comparisons with other shop systems can be found in our comparison overview.
Frequently Asked Questions About Store Builders and Store Systems
Sources
- Regulation (EU) 2023/2854 (Data Act), Articles 2, 23, 25, 29, and Recital 81
- Section 1 PAngV: Scope of Application and Section 3 PAngV: Total Price
- § 6a UStG: Intra-Community Supply and § 18e UStG: Confirmation Procedure
- § 3c UStG: Place of supply for intra-Community distance sales and § 18j UStG: Special taxation procedure (OSS)
- § 312j BGB: Obligations toward Consumers in Electronic Commerce and § 356a BGB: Right of Withdrawal
- Art. 246a § 1 EGBGB: Information Obligations
- General Data Protection Regulation (EU) 2016/679, Art. 7 and 28
- Google Search Central: Moving a Website with URL Changes, Redirects, and Google Search
Stephan Dunger
Stephan Dunger is one of the brains behind the XONIC store system. He has been developing the platform together with the team since 2012 - from the database to the interfaces to the checkout.
A passionate programmer, technical mind and consultant at the same time: with his in-depth knowledge of store systems and e-commerce, Stephan combines the depth of a developer with an eye for the big picture. Together with the XONIC team, he shapes the technical direction, consistently thinks about functions from the retailer's perspective and advises on customized solutions.
The result is software with a face: customers don't get an anonymous provider, but a direct line to the people who develop XONIC. Pragmatic, fast and at eye level.
