Apple Subscription Bundles vs Suites: Which Fits Your Apps?
Apple introduced Subscription Bundles and Suites at WWDC26. Both let a customer pay once for access to several auto-renewable subscriptions, but they solve different portfolio problems. This guide walks through the structural differences, the three bundle configurations, and the App Store Connect request steps so you can pick the right shape before you apply for early access.
Bundles and Suites at a glance
The quickest way to separate the two is to ask what the customer is buying and whether the parts remain available on their own. A bundle combines several subscriptions into one purchase while each included subscription can still be bought separately. A suite sells one subscription that unlocks a set of apps from a single developer, and the parts are not sold individually.
The structural comparison table below summarizes the rules. Use it as a first filter, then read the configuration sections for the details that matter to your portfolio.
When a Bundle is the better fit
Choose a bundle when you want to keep your existing standalone subscriptions on sale and add a combined offer on top. That preserves customers who only want one piece while giving multi-service customers a reason to buy more.
There are three configurations:
- Single-app bundle. One app sells several subscriptions separately and also offers them together. CatNavigator, for example, sells Norway, Sweden, and Finland subscriptions individually and combines all three in a Nordic bundle.
- Multi-app bundle from one developer. A single developer with two apps, such as TodoCat and CalendarCat, offers both subscriptions in one purchase while keeping each standalone.
- Multi-developer bundle. Two or more developers partner so their subscriptions are sold together. TodoCat and CalendarDog from different developers is the illustrative case.
A bundle holds up to five subscriptions, and a multi-developer bundle can involve up to five developers. Every included subscription must share the same duration, so monthly and annual products cannot sit in the same bundle. Each included subscription must also remain individually purchasable.
What the bundle configurations look like in practice
Single-app. CatNavigator is a navigation app with separate country subscriptions. A customer who only needs Norway buys Norway. A customer traveling across the region buys the Nordic bundle, which includes all three country subscriptions at a lower combined price. Everything unlocks inside the same app, so no second app or partner is involved, and the country subscriptions stay on sale individually with matching durations.
Multi-app, one developer. TodoCat handles tasks and CalendarCat handles scheduling. Each has its own subscription, and the developer can offer both in a bundle at a lower combined price. Standalone subscriptions remain available. If a customer cancels, they can choose to keep parts of the bundle rather than losing everything at once.
Multi-developer. A calendar app from one developer and a to-do app from another can be sold together. TodoCat and CalendarDog offer their monthly subscriptions as a pair for less than the combined standalone price. A customer already subscribed to TodoCat who joins the bundle gets upgraded access and a prorated refund for the unused standalone period. If they later want only TodoCat, they keep that subscription and drop the rest of the bundle at renewal.
When a Suite is the better fit
A suite makes sense when a related set of your own apps should be sold as one collection rather than as separate products. Apple Creator Studio is a useful reference for the purchase experience: creative tools such as Final Cut Pro, Logic Pro, and Pixelmator Pro are combined under one subscription.
A suite can cover up to 15 apps from the same developer, and the subscriptions inside it cannot be purchased individually. That constraint is the main trade-off. If you want to keep selling parts of your lineup on their own, a bundle is usually the more flexible choice because it works alongside existing business models.
A worked example: one developer offers PhotoCat for photo editing, VideoCat for video editing, and SoundCat for audio editing. A customer buys the suite subscription and gets access across all three apps. None of those three subscriptions is sold separately.
Requesting access from Apple
Access starts with Apple's request form in App Store Connect. Before you open it, gather the participating apps' identifiers and decide which configuration you want to offer.
Technical requirements. Apple lists Bundle and Suite purchase support on iOS 27, iPadOS 27, macOS 27, and tvOS 27 or later. Confirm every participating app meets that bar before submitting.
Configuration choices. After entering contact details, confirm that StoreKit 2 is implemented across the apps you plan to include. Then select one of: single-developer bundle, single-developer suite, or multi-developer bundle.
App identifiers. A single-developer bundle or suite request needs the App Apple ID of every app involved. Each App Apple ID is the numeric value shown on that app's submission page in App Store Connect, so collect them from the individual app records rather than from a shared account view.
Multi-developer roles. The form asks whether you are the primary or secondary developer. The primary developer is the seller of record and Apple's main contact; secondary developers contribute subscriptions to the bundle. Supply the App Apple IDs for your own apps and your partners' apps, so agree on the participant list before anyone submits.
Revenue split. Apple's public overview and the WWDC26 session do not explain how revenue is divided between developers or how secondary developers are paid. Settle the revenue split and payment arrangements with Apple during onboarding before you commit to a partnership.
Submission and onboarding. In a multi-developer bundle, the request and Apple's program addendum are per-developer obligations: each participating developer files their own and signs, so a single partner's submission does not cover the group. Once approved, Apple collects the subscription details and coordinates pricing and the launch date with everyone involved.
Planning checklist before you apply
Work through these questions in order; each one maps to a rule above.
- Do you want the included subscriptions to remain on sale individually? If yes, a bundle. If no, a suite is possible.
- How many apps and developers are involved? A suite is limited to one developer and up to 15 apps. A bundle holds up to five subscriptions and can involve up to five developers.
- Do all included subscriptions share one duration? If not, the bundle cannot be formed as planned.
- Are all participating apps on iOS 27, iPadOS 27, macOS 27, or tvOS 27 or later, with StoreKit 2 implemented?
- For a multi-developer bundle, who is the primary developer (seller of record and Apple contact) and who are the secondary contributors?
- Have you agreed the revenue split and payment arrangements with Apple and your partners?
- Has every developer in the bundle submitted their own request and signed the program addendum?
Once the structure is settled, choose a combined price that gives customers a clear reason to buy the package. Apple supports introductory and promotional offers on Bundles and Suites, so a discounted starting period or a promotion can sit alongside the standard price.
| Question | Bundle | Suite |
|---|---|---|
| What does the customer buy? | Several subscriptions in one combined purchase | A subscription covering a set of apps |
| Can they buy the included subscriptions separately? | Yes | No |
| Who can participate? | One developer, or up to five developers | One developer |
| What is the size limit? | Up to five subscriptions | Up to 15 apps |
| When does it fit? | Services sold individually with a combined offer | Related apps sold as a subscription collection |
Structural rules as described by Apple at WWDC26; confirm current terms in App Store Connect during onboarding.
Frequently asked questions
Can a bundle mix monthly and annual subscriptions?
No. Every subscription inside a bundle must have the same duration, so monthly and annual products cannot be combined in one bundle.
What happens if a customer already subscribes to one app and then joins a multi-developer bundle?
Joining the bundle upgrades their access and triggers a prorated refund for the unused portion of the standalone period. If they later want only the original app, they can keep that subscription and leave the rest of the bundle at renewal.
Can a suite include apps from more than one developer?
No. A suite covers up to 15 apps from a single developer. Multi-developer participation is only available through a bundle.
Do all participating apps need StoreKit 2?
Yes. The request process asks you to confirm StoreKit 2 is implemented across the apps you plan to include, and Apple lists support on iOS 27, iPadOS 27, macOS 27, and tvOS 27 or later.
How is revenue split between developers in a multi-developer bundle?
Apple's public overview and the WWDC26 session do not explain the split or how secondary developers are paid. Confirm the revenue split and payment arrangements with Apple during onboarding before agreeing to a partnership.