How to Choose iOS 27 StoreKit Bundles and Suites? 2026 Independent Developer Guide

Apple’s eligibility guidance names iOS 27, iPadOS 27, macOS 27, and tvOS 27 or later, and requires StoreKit 2 for Bundles and Suites. (Apple’s Bundles and Suites requirements) This week, list every subscription, the apps it unlocks, and whether customers must still be able to buy it alone. Choose a Bundle when standalone purchases remain part of the offer; assess a Suite when multiple apps must operate as one subscription service. If other developers are involved, assess a multi-developer Bundle and treat Apple’s application and configuration as release gates, not formalities.

This guide is for you if you maintain one app with several subscription products, operate multiple apps that may share a paid service, or are planning a subscription partnership with another developer. It also helps you scope a StoreKit 2 migration and separate Xcode testing from the work required in App Store Connect.

Last updated October 25, 2026. Eligibility and process checked against Apple’s current Bundles and Suites documentation, Apple’s developer materials, and the linked StoreKit testing guidance.

iOS 27 StoreKit Bundles and Suites: choose by entitlement boundary

Start with what a customer is buying and what that purchase unlocks. The product label should follow the entitlement design; it should not drive it.

A Bundle is worth assessing when subscriptions can remain individually available and you want to offer a combined purchase alongside them. A Suite is the model to evaluate when a subscription represents a service across several apps and the customer should receive that service as a unified offer, rather than choosing among separately sold subscriptions. Apple describes these product boundaries and the eligibility process in its official Bundles and Suites overview.

Do not confuse either feature with an App Bundle in the traditional App Store Connect sense. That separate workflow creates and submits a group of apps for App Store distribution; it does not, by itself, define a combined auto-renewable subscription. Apple documents that app-group workflow separately in its App Store Connect guide to creating and submitting app bundles.

Before you compare the options, make an inventory with these fields for each subscription:

• Product identifier and current sales status.
• The app or apps whose features it unlocks.
• Whether a customer can buy it separately, now and after the change.
• Which team owns the entitlement decision and customer support.
• What happens when a purchase expires, is refunded, or cannot be verified.

This inventory exposes a common design problem: a product may be sold from one app while its benefits are expected in another. The storefront structure and the entitlement checks must agree. If they do not, a successful transaction can still leave a customer unsure which features they bought.

One app: adding a combined offer versus replacing standalone choices

If you maintain a single iOS app with several subscriptions, first ask whether customers still need to choose and buy each subscription separately. If yes, evaluate a Bundle as an additional way to combine those products. The presence of one app does not automatically make a Suite the right choice.

For example, imagine an app with separate subscriptions for distinct feature areas. If customers can choose either area alone, and some may want both, preserve that product distinction in your inventory. Then assess whether a combined offer fits the intended purchase experience. Do not convert separate products into a single service merely to make the storefront appear simpler.

A Suite needs a different product rationale. Ask whether the subscription represents a service that spans multiple apps and whether the customer should receive access as one coordinated offering. If the second app is only a future idea, do not build a Suite around an unconfirmed roadmap. First define the service, the apps that participate, and how the shared entitlement will be recognized in each app.

Your decision should also account for the existing subscription lifecycle. Apple’s general auto-renewable subscription setup guidance covers subscription configuration, but your choice still needs to fit your current products and how the app verifies and grants access. A new combined offer does not automatically mean you must rewrite the entire app. Scope the actual work: identify what must change in the product catalog, purchase presentation, transaction handling, and entitlement checks.

Multiple apps: shared access versus several separate products

When you maintain more than one app, count the entitlements, not just the app icons. Two apps may share a service, or they may offer distinct products that happen to come from the same team. Those are different subscription designs.

Assess a Suite when the customer is buying one service whose value is delivered across participating apps. Define which features each app unlocks and how every app checks the shared entitlement. A user who pays in one app should not have to guess whether another app is included or perform an unrelated purchase to activate the promised service.

Assess a Bundle when the products remain meaningful and purchasable on their own, even if customers may also want them together. That can preserve customer choice, but it makes product presentation and validation important: the combined offer must not imply benefits that the included subscriptions do not grant.

Use this decision branch before committing:

• If each subscription must remain available as a standalone purchase, assess a Bundle first. If the customer should still be able to choose one product without buying the others, preserve that path in the product design.
• If one subscription should unlock a coordinated service across several apps, assess a Suite. If the apps do not share a defined service or entitlement, return to the Bundle question instead.
• If more than one developer participates, assess the multi-developer Bundle route. If the teams have not assigned entitlement ownership, customer support, and operational responsibilities, pause the product decision until they have.
• If the app uses an older subscription implementation, check StoreKit 2 and target OS eligibility before estimating migration. If your deployment targets or purchase flow do not meet the published requirements, plan that work before applying.
• If Apple has not confirmed the application and configuration, do not schedule a public launch. A successful local test is evidence about your code, not approval or completed storefront setup.

This is a product and operations decision as much as a code decision. Write down who owns the shared entitlement, what each app promises, and how you will handle account changes before you begin implementation.

Partner teams: shared offer versus unapproved assumption

Apple’s materials include multi-developer Bundles, which makes collaboration a relevant option to investigate. But a conversation between teams is not a store-ready offer. Each participant should document the subscriptions involved, the rights those products grant, and which party is responsible for the customer-facing parts of the service.

Agree on the operational boundary before submitting anything. Decide how teams will coordinate entitlement changes, subscription support, release timing, and what happens if a participating app changes its product. These are not reasons to avoid a partnership; they are questions that can reveal whether the proposed Bundle has a coherent customer promise.

Then follow Apple’s application and follow-up configuration process. Apple may require additional information or agreements, and the team should treat approval as an outcome to verify, not something guaranteed by eligibility. Keep separate records for the application, Apple’s response, any requested materials, configuration in App Store Connect, and the release decision. The WWDC 2026 discussion of in-app purchases, Bundles, and Suites is useful context, but the current official documentation remains the place to recheck the live requirements.

If a partner cannot identify who owns the entitlement or handles customer issues, do not use a combined purchase to conceal that gap. Resolve the responsibility first, then reassess whether a multi-developer Bundle matches the actual offer.

Existing subscriptions: targeted migration versus a full rewrite

If your subscription flow predates StoreKit 2, begin by auditing what it does today. Find the code that starts purchases, receives and verifies transactions, restores access, and updates entitlements. Compare those responsibilities with the changes needed for the Bundle or Suite you are considering.

Apple’s published requirements call for StoreKit 2 and the specified target operating systems. That does not establish that every existing screen or subscription feature must be replaced. The migration scope depends on your current implementation and on which apps need to recognize the new purchase. You may need to revise transaction and entitlement handling in participating apps while leaving unrelated parts of the product untouched.

Keep the investigation concrete:

• Identify the purchase and verification paths currently in production.
• Trace how each subscription maps to app features.
• Mark the apps and deployment targets that must support the combined offer.
• Test how the app responds to an active, expired, or unavailable entitlement.
• Estimate changes per app before promising a release date.

Do not infer eligibility from a successful build alone. A build can show that the code compiles for a selected target; it cannot confirm that all participating apps meet Apple’s requirements or that the App Store Connect product configuration is complete.

Milestones: application, local test, and release are separate gates

Treat the work as a sequence of gates. That makes it easier to spot what is still unknown and prevents a green local test from being mistaken for a launch approval.

Product definition. Finish the SKU and entitlement inventory. Decide whether standalone purchase paths remain, whether the offer spans apps, and who owns each entitlement. If the product promise is still changing, hold off on configuring the storefront.

Eligibility review. Verify StoreKit 2 use and the target OS requirements against Apple’s current documentation. Check each participating app rather than assuming the main app is representative. Apple may revise eligibility or submission steps, so verify the guidance again before you file.

Application. Submit the required information and wait for Apple’s response. If Apple asks for additional subscription details or agreements, record those as open work. Do not treat submission as approval.

Configuration. After confirmation, complete the required subscription setup in App Store Connect. Keep a record of the product identifiers and the apps that must recognize the entitlements. Apple’s subscription configuration documentation can help with the surrounding auto-renewable subscription setup, but follow the Bundles and Suites instructions for the specific offer.

Local and sandbox testing. Use Xcode to test the StoreKit behavior in a controlled environment. Apple explains how to set up StoreKit testing in Xcode and how to test StoreKit at different development stages with Xcode and the sandbox. These resources support code and purchase-flow testing; they do not replace the application or App Store Connect configuration.

Release acceptance. Check the offer as a customer would see it, complete the available purchase path, and verify which features become available in every participating app. Confirm that standalone products still behave as intended if the design promises them. Release only after the store configuration, purchase result, and entitlement delivery agree.

Xcode 27 can help you exercise StoreKit behavior locally, but keep test evidence and store readiness in separate records. A local result answers, “Does this implementation behave as expected in this test setup?” Store configuration and Apple’s application process answer different questions. The distinction matters most when several apps or developers are involved.

FAQs: choosing a model and confirming eligibility

What separates a StoreKit Bundle from a Suite?

A Bundle is the option to examine when separate subscription products still have independent value and customers may buy them individually as well as together. A Suite is intended for a service that spans apps as a unified subscription offer. Decide from the purchase and entitlement model, not from the number of apps in your portfolio.

Is a Suite appropriate when I only have one iOS app?

Usually, start by asking whether your current subscription products remain separately purchasable. If they do, assess whether a Bundle adds a useful combined option without removing individual choices. A Suite is better evaluated when the service itself spans participating apps. Do not choose a model based only on plans to build another app later.

Can separate developers participate in one subscription offer?

Apple’s documentation includes multi-developer Bundles, so teams can investigate that route. They still need to meet Apple’s application and configuration requirements. Before applying, define which subscriptions participate, what each entitlement grants, who supports customers, and how teams coordinate product changes. A partnership agreement or shared plan alone does not establish that Apple has approved the offer.

What does my app need to support for Bundles and Suites?

Apple’s published guidance specifies iOS 27, iPadOS 27, macOS 27, or tvOS 27 and later, and requires StoreKit 2. Review every participating app’s target and purchase implementation. Then test the local StoreKit flow separately from App Store Connect setup and Apple’s application process; passing one does not complete the others.

When Mac access becomes part of the release plan

Once you settle the subscription model, the remaining work may require a macOS environment to build and verify the StoreKit implementation. A Windows or Linux workstation cannot run Xcode, while buying a Mac solely for occasional acceptance testing can leave you paying for hardware you rarely use. Keeping the only Mac on a developer’s desk also creates a handoff dependency when another team member needs to reproduce a purchase issue.

If you already have a suitable Mac and expect frequent, sustained work, using it locally may be the simplest choice. If you need a temporary or shared macOS test environment, VMSPIN offers access to a hosted real Mac through VNC, SSH, or a web console. You can compare the available Mac rental options and pricing before deciding whether that model fits the project. It is not a substitute for a physical device when you need hardware-specific testing, and a rented environment does not bypass Apple’s review or configuration process.

Your next action is to finalize the entitlement map, confirm the StoreKit 2 and target OS requirements, and keep local testing separate from Apple’s approval and store setup. If your team then needs a macOS environment for Xcode validation without buying another machine, review VMSPIN’s Mac access options against the duration and testing needs of this release.