Many e-commerce platform providers charge a percentage of sales in addition to the base fee—as a transaction fee, revenue share, or “performance-based fee.” What sounds like a small markup becomes the biggest cost driver as the business grows. This guide breaks down the different models and highlights the questions merchants should ask before signing a contract.
At a Glance
- Revenue sharing means that system costs automatically increase along with sales—regardless of whether the provider delivers more value.
- Even just 1–2% of revenue significantly exceeds any flat-rate plan when monthly revenue reaches five- to six-figure amounts.
- Fixed monthly rates make system costs predictable and reward growth rather than taxing it.
- In addition to the revenue share, costs are often hidden in apps, payment surcharges, and mandatory upgrades —the total price is what matters.
What does revenue sharing mean for e-commerce platforms?
In revenue-based models, the merchant pays a monthly base fee plus a percentage of each sale to the platform provider—partly as an upfront commission, partly hidden as a “transaction fee” that is waived only if the merchant uses the platform’s in-house payment service. Even enterprise licenses for well-known systems often tie licensing costs to gross merchandise volume (GMV). The effect is always the same: system costs scale with the merchant’s revenue—not with the provider’s performance.
How does this compare to fixed costs?
A simple example calculation illustrates the difference—assuming a provider with a €149 base fee plus a 1.5% share of sales versus a fixed-price package for €449 per month:
| Annual Revenue | Model with 1.5% commission | Fixed price: €449/month |
|---|---|---|
| €100,000 | €1,788 + €1,500 = €3,288/year | €5,388/year |
| €500,000 | €1,788 + €7,500 = €9,288 per year | €5,388/year |
| €1,000,000 | €1,788 + €15,000 = €16,788/year | €5,388/year |
| 3,000,000 € | €1,788 + €45,000 = €46,788/year | €5,388/year |
The calculation illustrates the pattern: For very small shops, a revenue-based model may seem more cost-effective—but starting at medium revenue levels, the situation reverses, and as the business grows, the merchant pays more each year for the same service. In this example, the break-even point is around €240,000 in annual revenue; above that, the merchant’s success effectively subsidizes the platform provider.
What other costs are associated with shop systems?
- App and plugin subscriptions: Basic features such as filters, reviews, or B2B pricing can quickly cost several hundred euros extra per month in app store ecosystems.
- Payment surcharges: Merchants who don’t use the platform’s in-house payment service may face penalty fees per transaction with some providers.
- Mandatory upgrades: Revenue or traffic limits force merchants to switch to more expensive plans.
- Agency and operation: With open-source systems, there’s no license fee, but merchants are responsible for hosting, updates, security, and development themselves.
E-commerce platforms can therefore only be compared based on total costs: base fee + commission + apps + payment processing + operations, calculated based on your own projected revenue.
When is which model the best choice?
Revenue-based modular systems are suitable for test projects and very small product ranges, where the absolute cost is initially negligible. On the other hand, those who want to grow in a predictable manner, serve repeat customers, or build a B2B business will find fixed costs more predictable—the margin per sale remains constant, and system costs can be budgeted years in advance.
How XONIC Calculates
The XONIC Shop System operates with fixed package prices starting at €149 per month—with 0% revenue share, no transaction fees, and no requirement to use an app store: hosting, updates, and support are included in the packages, and the feature set doesn’t require any paid add-on plugins. Whether the store generates €10,000 or €10 million in revenue, the system costs remain the same. A comparison of the four packages can be found on the pricing page.
Frequently Asked Questions About E-commerce Platform Costs
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.
