What is Apple's Core Technology Commission and what changed on 1 January 2026?
Apple replaced its per-install Core Technology Fee with a Core Technology Commission (CTC) for European Union developers, and as of 1 January 2026 there is a single business model for every EU developer instead of a fork between old and new terms. Under Apple's terms the CTC is a 5% commission on qualifying digital-goods sales, and it has been in effect since 26 June 2025. It applies whether an app is distributed through the App Store, through Web Distribution, or through an alternative marketplace. Notarization for iOS apps and Apple's layered service fees for the EU remain in place, so the CTC is one line item in a stack, not the whole cost.
The practical headline for founders and engineering leaders is that the economics of shipping an EU iOS app changed shape. The old Core Technology Fee charged a flat amount per first annual install above a threshold, which punished free and high-volume apps regardless of whether they earned revenue. The Core Technology Commission is tied to qualifying digital-goods sales instead, which moves the cost closer to a percentage of what you actually monetise. That is a meaningful difference for the financial model behind any consumer or prosumer app aimed at Germany, the Netherlands, the Nordics, Switzerland, or the UK-adjacent EU market.
Why does this matter for how you distribute an EU app?
Because the same 5% CTC now attaches across the App Store, Web Distribution, and alternative marketplaces, the fee is no longer the deciding factor between distribution channels the way the per-install fee once was. That reframes the decision around reach, trust, payment friction, and update tooling rather than a single punitive install charge. Web Distribution and alternative marketplaces become more viable to model seriously, especially for apps with large free user bases that previously feared the per-install exposure.
It does not make them automatically cheaper. You still carry notarization, you still carry Apple's layered EU service fees where they apply, and you take on the engineering and operational cost of running distribution yourself. The right answer depends on your monetisation mix. A subscription app with strong conversion may prefer the discovery and payment trust of the App Store; a free app with millions of installs and indirect monetisation may finally have a defensible case for web distribution.
How do the old and new EU models compare?
| Dimension | Old Core Technology Fee (CTF) | New Core Technology Commission (CTC) |
|---|---|---|
| Charging basis | Per first annual install above a threshold | 5% of qualifying digital-goods sales |
| Effective from | Prior EU DMA terms | 26 June 2025; single model for all EU developers from 1 January 2026 |
| Free / high-volume apps | Exposed to install-count cost | Cost tracks monetised sales, not raw installs |
| Distribution scope | Applied under alternative terms | Applies across App Store, Web Distribution, alternative marketplaces |
| Still in place | Notarization, service fees | Notarization, layered EU service fees |
How should EU app teams re-model their App Store economics for 2026?
Start by separating gross revenue from net revenue in your model. Take qualifying digital-goods sales, apply the 5% CTC, then layer Apple's applicable EU service fees and any commission on top, and only then look at your true contribution margin per user. Many EU teams built their pricing on assumptions from the CTF era; those spreadsheets are now stale. If your app is free with in-app purchases, the shift usually helps you, because your cost scales with sales rather than downloads. If your app is a high-ARPU subscription, the change is more neutral and you should focus on the total fee stack rather than the CTC alone.
Second, treat distribution as a portfolio decision. Model the App Store, Web Distribution, and at least one alternative marketplace side by side using the same net-revenue method. Include the hidden engineering cost of each channel: web distribution means you own installation flows, update delivery, and trust signalling; alternative marketplaces mean integrating with a third-party store's tooling. A realistic model prices the build and maintenance work, not just the headline fee.
Third, budget for notarization and review as recurring operational overhead, not a one-off. Every EU release path still passes through Apple's notarization, so your release calendar and QA process must assume that gate. Teams that plan submissions around it ship predictably; teams that treat it as an afterthought lose weeks. If you are estimating overall budget, our breakdown of what mobile app development costs in 2026 gives a grounded starting point before you layer EU-specific fees on top.
What does this mean if you outsource or offshore your mobile build?
An experienced outsourced mobile team turns this from a policy headache into a modelling exercise. The value is not just writing Swift; it is owning the App Store economics, the distribution decision, and the release mechanics so your in-house leadership can make a revenue call with real numbers. At ILMTEC our senior India and UAE engineers build the financial model alongside the app, run notarization and submission as routine, and set up whichever distribution channels your economics justify. If you want a resilient, well-planned launch, our mobile app development team plans the CTC impact into the roadmap from day one rather than discovering it at launch.
Getting to the store is its own discipline. Regardless of whether you ship through the App Store, web distribution, or a marketplace, you still need a disciplined submission process, and our App Store and Google Play launch checklist covers the practical gates that catch teams out. And if you are still selecting a partner to own this end to end, the questions in how to choose a mobile app development company will help you separate teams that understand EU distribution economics from those that only quote a build price.
What should you do first?
Audit your current EU App Store financial model this quarter. Recompute net revenue per paying user under the 5% CTC plus applicable service fees, then pressure-test whether web distribution or an alternative marketplace changes the picture for your specific monetisation model. Re-price if the numbers moved, and make sure your release process explicitly accounts for notarization. Do this now, while the single-model transition is fresh, so your 2026 roadmap is built on the real fee structure rather than the retired one. The teams that re-model early will price and distribute with confidence; the ones that wait will keep budgeting against rules that no longer exist.
