What changed
Apple has moved its iOS 27 subscription expansion from WWDC preview material into an active developer rollout. Developers can now request access to Bundles and Suites, which package multiple auto-renewable subscriptions into one Apple In-App Purchase. A Bundle can combine services inside one app, across several apps from the same developer, or across apps owned by different developers; a Suite gives one developer a single subscription that unlocks a set of services across its apps.
The configuration is more concrete than the June announcement. Apple says a Bundle can contain up to five subscriptions and a multi-developer Bundle can involve up to five developers. A Suite can cover as many as 15 apps. Apps must use StoreKit 2 and support iOS 27, iPadOS 27, macOS 27 or tvOS 27 or later for purchases, and multi-developer participants must each submit interest, sign Apple’s programme addendum and provide their subscription details before Apple configures the package.
Multi-seat subscriptions are becoming a first-class App Store product
Apple has also switched on multi-seat purchasing controls in App Store Connect for subscriptions. Volume Purchasing lets organisations procure subscription seats through Apple Business Manager or Apple School Manager and assign them through existing device-management systems. Group Purchases let one subscriber buy several seats in one transaction and invite other people, with Apple handling the invitation and seat-assignment flow.
The dates are now specific. Apple says Volume Purchasing launches on 22 October 2026 and Group Purchases will arrive this winter. Multi-seat purchasing is enabled by default for subscriptions in App Store Connect today, although developers can disable it entirely or manage availability separately for the consumer App Store, Apple Business and Apple School Manager.
Why it matters
For subscription apps, this creates a distribution path between ordinary consumer subscriptions and a full enterprise sales process. Small teams can buy several seats without going through a company procurement system, while larger organisations can use the Apple Business and School Manager channels they already use for app deployment. Cross-developer Bundles also give independent apps a native way to sell a combined package without asking customers to manage several separate subscriptions.
Apple is also taking responsibility for more of the purchase lifecycle. The App Store shows all apps included in a Bundle or Suite, upgrades existing standalone subscribers into a Bundle with a prorated refund for unused time, and lets customers later keep individual services or cancel the package from their Apple Account. That reduces some of the billing and entitlement plumbing developers would otherwise have to build themselves.
Limits and open questions
Bundles and Suites still require Apple approval and are configured in batches rather than created instantly in App Store Connect. Apple says the purchasing capability will be available later this year, so the request process is live before the complete customer rollout.
Apple’s public material describes eligibility, StoreKit requirements and customer handling, but it does not yet provide a general self-service workflow for multi-developer configuration or enough public detail to compare the commercial mechanics with developers’ existing direct partnership arrangements. The next useful signals will be approved live Bundles, the final customer rollout, and the operational rules developers encounter when several companies share one subscription product.