Skip to content
AppDues
Log in
Contact salesSign up

Apple Advanced Commerce API: When It Helps and What to Check

Apple's Advanced Commerce API is designed for complex in-app purchase setups — especially large catalogs and bundled subscriptions — while keeping App Store payment processing, tax handling and customer support. This guide explains the two use cases, the requirements, the limitations, and a practical decision checklist.

What problems does it solve?

Two patterns drive the API. First, extensive libraries of purchasable content — for example a creator platform with tens of thousands of creators or an education platform with thousands of courses — can be hard to create and maintain inside App Store Connect. Second, complex subscriptions where several subscriptions are bundled together, such as a base streaming subscription with optional premium channel add-ons. Using multiple subscription groups for the second pattern can leave customers with multiple subscriptions, which is harder to implement, harder for customers to understand, and harder to manage for both sides. The API was first announced at WWDC in June 2024 without documentation, with a detailed overview and full documentation following later.

Key features

You can host and manage your own SKU catalog instead of configuring everything in App Store Connect, specify product details dynamically at runtime, bundle multiple subscriptions into a single purchase, and retain App Store commerce benefits including payment processing, tax handling and customer support. In practical terms, product data moves closer to your own systems while checkout and commerce infrastructure stay with the App Store.

Requirements checklist

Check every requirement before planning a migration: use StoreKit 2; implement in-app subscription management; use App Store Server API and Server Notifications V2; support iOS 15.0+ and equivalent OS versions; and pass a separate approval process. Treat the approval step as a gating item — do not assume eligibility until it is confirmed.

Limitations to plan around

Purchases made through the API cannot be promoted on the App Store, do not support subscription offers, cannot use Family Sharing, and are not compatible with StoreKit Testing in Xcode. Some limitations may change in future, but building in hope of a near-term change is risky. Plan testing, promotion and sharing workflows around the current limits.

Should you use it? A decision checklist

Use this decision check: 1) Is your catalog very large and difficult to manage through App Store Connect? 2) Do you need bundled subscriptions with optional add-ons billed as one subscription? 3) Can you meet the StoreKit 2, server API, OS version and approval requirements? 4) Can your business accept no App Store promotion, no subscription offers, no Family Sharing and no StoreKit Testing in Xcode for these purchases? If the answer to the first two is no, or the last two is no, standard StoreKit is likely the better fit. Two concrete examples illustrate the fit: individual creator subscriptions where each creator sets a price and users can subscribe to many accounts — without the API each would need a manually created product in its own subscription group — and a core package with add-ons, like a TV service offering extra channels, billed and managed as a single subscription.

What this signals

The API serves a narrow use case, but it shows willingness to evolve the App Store for complex business models while preserving core commerce infrastructure. For eligible apps it could streamline product management and open new monetization options; for others it is a signal of continued investment in App Store commerce capabilities.

Advanced Commerce API vs standard StoreKit at a glance
CheckAdvanced Commerce APIStandard StoreKit
Catalog managementHost and manage your own SKU catalog; specify details dynamically at runtimeConfigure products in App Store Connect
Bundled subscriptionsBundle multiple subscriptions into a single purchaseMultiple subscription groups can create multiple subscriptions
Commerce infrastructurePayment processing, tax handling and customer support retainedApp Store commerce infrastructure
Key constraintsNo App Store promotion, no subscription offers, no Family Sharing, no StoreKit Testing in Xcode; separate approval requiredStandard StoreKit implementation for straightforward models

Summary based on the captured feature, requirement and limitation details; confirm current Apple documentation before implementation.

Frequently asked questions

What problems does the Advanced Commerce API solve?

It is aimed at two patterns: very large in-app purchase catalogs that are hard to maintain in App Store Connect, and bundled subscriptions where add-ons should be billed as one subscription instead of several separate ones.

What are the requirements for using it?

You must use StoreKit 2, implement in-app subscription management, use App Store Server API and Server Notifications V2, support iOS 15.0 or later and equivalent OS versions, and pass a separate approval process.

What are the main limitations?

Purchases cannot be promoted on the App Store, do not support subscription offers, cannot use Family Sharing, and are not compatible with StoreKit Testing in Xcode.

Should most apps use it?

Consider it when a huge catalog is difficult to manage through App Store Connect, or when you need bundled subscriptions with optional add-ons. For straightforward purchases or subscriptions, standard StoreKit remains the better choice.