Week in App Store Ops — Multi-Seat Subscriptions Live, EU Commission Settled, Play API 36 Final Call

Apple's Volume Purchasing went live October 22 and Group Purchases hit sandbox this month — the best B2B window of the year. Plus: EU's lower commission rates are in, and Google Play's API 36 deadline reaches existing apps in November.

Three threads converged this week for app developers: Apple's multi-seat subscription features moved from announced to live, the EU App Store commission changes that took effect October 1 have now fully settled into developer economics, and Google Play's API 36 deadline reaches existing apps in November. None of these is a surprise — but together they mark a genuine turning point before Q4 sprints into full gear.

Apple's Multi-Seat Moment Is Live — and Moving Faster Than Expected

If you ship a productivity tool, project manager, developer utility, or any app with a team use case, October 22 was your date. Volume Purchasing — the mechanism that lets schools and businesses buy multiple seats of your subscription through Apple Business Manager and Apple School Manager — went live that day. Apple confirms the feature is on by default in App Store Connect unless you actively opted out.

The fine print matters. Subscriptions created before September 14, 2026 default to opted out if they don't use StoreKit 2 or have Family Sharing enabled. If you're running a legacy subscription product and haven't migrated to StoreKit 2, you're leaving institutional revenue on the table right now.

Group Purchases land in sandbox this month

Alongside Volume Purchasing, Apple is opening Group Purchase testing in Sandbox Apple Accounts starting November 2026, ahead of a consumer launch this winter. Group Purchases work differently from volume purchasing: a single subscriber buys seats and invites others — think family-plan logic applied to B2B. The StoreKit 2 requirement applies here too, and the App Store Server API is gaining group-management endpoints for server-side membership lookups.

A revised Developer Program License Agreement, dated October 13, 2026, now covers both features. Reading the group and volume purchase sections before your winter update is worth the 15 minutes.

• Check App Store Connect: are your subscription products opted in to Volume Purchasing?
• If you're still on the legacy StoreKit 1 flow, this is the clearest deadline you've had to prioritize the migration.
• Stand up a Sandbox Apple Account to test Group Purchase flows once Apple opens the gate this month.

The B2B angle here is bigger than it looks. Productivity and utility apps have long complained that Apple's subscription model was built for consumers. These two features are the first concrete move toward institutional purchasing parity. Worth revisiting your pricing tier structure before you configure volume discount levels.

EU Commission Rates — The Recalibration Has Landed

For developers selling to European users, Apple's revised App Store commission rates have been live since October 1. The standard rate drops to 26% (from 30%); routing through an alternative payment provider brings that to 20%. That's a meaningful shift for high-volume subscription apps where margin variance across markets matters at scale.

A few notes on scope:

These platform-level differences need to be part of your net revenue model, not just your headline revenue share assumption. If you're running a 39-market pricing strategy, the EU and China territories now carry a meaningfully different take rate. AppsOps's PPP pricing tool handles local purchasing-power adjustments; layer in the actual commission rate per territory when modeling subscription economics for the Q4 renewal cohort.

It's too early to call the EU impact material at scale, but directionally, reports suggest net revenue is up slightly for mid-sized subscription apps since October 1. The alternative billing route (20%) adds operational overhead — you handle tax, receipts, and refunds — so it's not automatically the right call for indie developers.

Google Play API 36 Deadline: Existing Apps Are Now In Scope

This one has been on the calendar since mid-year: starting November 1, 2026, existing Android apps must target API level 36 to remain available for download on Google Play. New app submissions required API 36 since August. If your Android build hasn't cleared the API 36 checklist, this is the last-mile moment — not next sprint, this one.

The practical risks cluster around three areas: targetSdkVersion compliance, edge-to-edge display enforcement, and the predictive back gesture that ships with API 36. The edge-to-edge change has the biggest ASO surface-area impact: your Google Play screenshots should reflect the full-bleed UI now in consumers' hands on Pixel 10 and Android 16 devices. Screenshot sets built against API 34/35 may look dated and hurt conversion. If you need to refresh Play Store creative quickly across languages, AppsOps's localization cost calculator can scope the effort.

The Week's Throughline

Monetization infrastructure at Apple is becoming more institutional, commission economics are shifting in regulated markets, and Android's API upgrade cycle is forcing a maintenance pass. None of these is a crisis — but all three reward teams who read the changelog early. For developers with any B2B or productivity angle, the next 30 days — Volume Purchasing live, Group Purchases entering sandbox — are the best window this year to get ahead of the winter cohort.

Sources and further reading

• Apple Developer News
• ppc.land — Apple App Store multi-seat subscription coverage
• Game World Observer — EU App Store commission changes
• Android Developers — Google Play API level targeting requirements