Preparing for Apple's EU fees 2026 confirmation now

Apple is reportedly close to confirming that its revised EU App Store terms, the Core Technology Commission structure it announced back in June, will take effect on January 1, 2026 as originally scheduled. That is not a surprise. What is worth acting on now, seven weeks out, is that the Apple EU fees 2026 confirmation is arriving at exactly the point in the calendar when most finance teams have already locked their 2026 budget assumptions, which means the studios that benefit most from the new terms are also the ones most likely to have modelled the old ones by mistake.

What is actually being confirmed

As we covered in Apple's Core Technology Commission and the 5% math, the new structure replaces Apple's per-install Core Technology Fee, roughly EUR 0.50 per install above one million annual installs, with a flat 5% revenue-based commission plus separate tiered store services fees for developers who adopt the alternative EU terms. That announcement in June set the January 2026 effective date; this month's reported confirmation is Apple closing off any remaining ambiguity about whether the timeline would slip, not a change to the mechanics themselves. The Coalition for App Fairness has continued to argue the structure is not DMA-compliant, and that argument has not gone away, but a live regulatory objection is a different risk than an uncertain effective date, and buyers should stop conflating the two.

Why "preparation" and "reaction" are different postures

A studio reacting to the Apple EU fees 2026 confirmation in January is a studio that finds out its actual EU platform costs after the quarter has already started, at exactly the point when a budget correction is most disruptive to run. A studio preparing for it now is modelling both fee structures against its own historical EU revenue distribution while there is still time to decide whether switching to the alternative terms makes sense for each title, rather than defaulting into whichever structure a finance system happens to have configured.

Regulatory pressure is not unique to Apple this cycle

Apple is not the only platform reshaping its terms under regulatory pressure heading into next year. Google has spent the second half of 2025 opening the US Play Store to rival stores and alternative billing under the Epic v Google injunction, and Japan's Mobile Software Competition Act is due to take full effect in December, requiring both Apple and Google to open alternative app stores and payment options there as well. None of that changes the mechanics of Apple's EU fees 2026 confirmation directly, but it does mean any UA or finance team building a 2026 platform-cost model needs to track more than one jurisdiction's terms at once. A model built purely around the EU Core Technology Commission while ignoring parallel changes in the US and Japan will understate how much of next year's platform cost picture is genuinely in motion.

The preparation checklist to run before January

• Pull each EU title's actual revenue-per-install distribution for the trailing twelve months, not an average across the portfolio, since the old per-install fee and the new revenue-based commission affect high- and low-monetising titles very differently.
• Model both fee structures, old and new, against that distribution for every title currently on or considering the alternative EU terms, including the tiered store services fees, which add a second cost variable beyond the headline 5% figure.
• Flag any title where the two models produce a materially different outcome to whoever owns that title's 2026 budget line, since a title-by-title adoption decision is more defensible than a blanket portfolio move.
• Confirm with finance which 2026 budget draft is currently in circulation and whether it already assumes the new Core Technology Commission or still carries the old per-install fee forward by default.
• Set a checkpoint in December to revisit the model if the Coalition for App Fairness's compliance challenge produces any regulatory response before the January effective date.
• Cross-check the EU model against whatever assumptions the same finance team is already carrying for US Play Store compliance and Japan's December market-opening requirements, since a platform-cost model built jurisdiction by jurisdiction in isolation is more likely to miss where two changes compound for a title with meaningful revenue in more than one of these markets.
• Assign a single owner for the EU fee model rather than leaving it split across finance and UA, since a confirmation this close to the effective date leaves little room for a handoff gap between teams to cause a missed deadline.

Apple EU fees 2026 confirmation: a worked example

Take a hypothetical portfolio of three EU-facing titles at a mid-size publisher, Studio D. Title X is a high-monetising strategy game generating EUR 4 million in EU App Store revenue a year from 1.2 million installs. Title Y is a hybrid-casual puzzle game generating EUR 1.5 million from 3 million installs. Title Z is a smaller hyper-casual title generating EUR 300,000 from 2 million installs. Under the old per-install Core Technology Fee, exempting the first million installs annually, Title X pays roughly EUR 100,000 a year, Title Y pays roughly EUR 1 million, and Title Z pays roughly EUR 500,000, a cost that falls hardest on the two lower-revenue, higher-volume titles. Under the new 5% Core Technology Commission, Title X's fee rises to about EUR 200,000, Title Y's falls to about EUR 75,000, and Title Z's falls to about EUR 15,000. For Studio D's portfolio, the new terms clearly favour Title Y and Title Z and cost more for Title X, the opposite of what a single portfolio-wide adoption decision would assume if someone only looked at the blended total. This is why the preparation checklist above calls for a title-by-title model rather than one number for the whole slate. A publisher with a similar spread of high- and low-monetising titles could easily reach the wrong adoption decision by averaging.

What to watch next

Between now and January 1, three things are worth tracking. Whether Apple issues the confirmation as a standalone announcement or folds it into other App Store guidance will signal how much further detail, such as final store services fee tiers, arrives with it. Whether the Coalition for App Fairness escalates its compliance objection into a formal regulatory complaint before the effective date, which would not change the January start date but could reopen the mechanics later in the year. And whether Japan's Mobile Software Competition Act, reaching full effect in December, produces early guidance from Apple that hints at how it plans to handle multiple simultaneous alternative-terms regimes across jurisdictions. A UA or finance team that has already run the title-by-title model will be able to absorb any of these three developments as a footnote rather than a rebuild.

What changes for a UA team specifically

None of this changes a live campaign today. What it changes is the confidence a UA lead can put behind next year's EU cost-per-install targets in a Q1 2026 planning document, because a target built on an unconfirmed or outdated fee assumption is a target that will need correcting mid-quarter, at a worse time than now. Buyers running EU web shop or alternative-billing flows should treat this confirmation as the trigger to finalise, not start, the modelling work, since the underlying mechanics have been public since June and the only genuinely new information this month is the timeline itself holding as scheduled. The studios best positioned for January will be the ones who treated this as a July modelling exercise with a November confirmation, not a November surprise with a January deadline.

Related archive reading

These articles provide related context and remain subject to their stated review status.

• Liftoff's confidential IPO filing, read as a UA buyer
• The Ledger #22: EU Terms and Web Shop Holiday Readiness