Apple Volume Purchasing Is Live (Oct 2026): Your Subscriptions Are Already on Sale to Organizations

What Went Live, and What Is Already Switched On

Apple’s developer news item of 22 October 2026 is short. Starting that day, organizations that use Apple Business or Apple School Manager can “purchase the seats they need through a single Apple In-App Purchase, then assign and manage those seats using their existing device management tools,” adding and removing seats at any time. The second multiseat product, Group Purchases, lets an ordinary App Store customer buy several seats and invite other people. Sandbox testing for it opens on 28 October 2026 and the App Store launch is only dated “this winter.”

None of this is a surprise announcement. Apple previewed it at WWDC26 and posted on 16 September 2026 that multiseat purchases were “enabled by default for subscriptions in App Store Connect,” with Volume Purchasing dated for 22 October. What is new this week is that the default now has buyers behind it. A setting most teams never looked at has become a live sales channel.

Who is actually opted in depends on where you read. The App Store Connect API documentation says flatly that every auto-renewable subscription defaults to multiSeatStatus: ENABLED. App Store Connect Help adds the exceptions. Subscriptions created before 14 September 2026 that either don’t use StoreKit 2 or have Family Sharing turned on start opted out. Custom apps get no choice: their subscriptions are “automatically” available in Apple Business and Apple School Manager and “you may not opt out.”

So the likeliest team to be selling to organizations without knowing it is also the most modern one. If you use StoreKit 2, don’t use Family Sharing, and launched or re-created a subscription since mid-September, multiseat is on unless someone switched it off.

The Settings That Are Cheap Now and Costly Later

Every switch below can be changed at any time, but they don’t cost the same. The cost depends on whether an organization has already bought. All of the rules are from Apple’s App Store Connect Help page on purchase options and the App Store Connect API guide to multi-seat configuration:

The asymmetry is the first row. Before any organization buys, dropping the two organization channels costs you nothing. After one buys, the same click cancels that organization’s subscription at its next renewal. The renewal is the point where a school’s IT admin finds out that thirty students lost access. If you aren’t ready to serve assigned seats, the window to say so cleanly is now.

Disabling multiseat is the gentler exit. It removes the SKU from both organization stores but lets existing seat holders keep renewing at their current count. If you have to retreat after organizations have bought, that is the lever to pull, not the channel removal.

What an Assigned Seat Looks Like to Your Server

The plumbing shipped a month before the storefront. App Store Server API 1.22, dated 28 September 2026 in Apple’s changelog, added the fields that matter:

• inAppOwnershipType: "ASSIGNED": a new value next to PURCHASED and FAMILY_SHARED. Apple now describes the field as covering access “through Family Sharing, an organization, or a group.”
• quantity now means seats. For a multiseat subscription it is “the number of seats the purchase covers.”
• revocationType: "ASSIGNMENT_REVOKE": the organization or group purchaser removed the subscription from a person. Apple’s instruction is direct: “Revoke the customer’s access to the content the transaction provides.”
• Get Customer Groups and Get Group Members endpoints, which Apple marks as sandbox-only for now, plus new error codes including InvalidAssignedTransactionNotSupportedError and AssignedSubscriptionExtensionIneligibleError.

Two failure modes follow from that list, and they point in opposite directions. If your entitlement logic treats any value other than PURCHASED as “not a customer,” an assigned user will see a paywall for something their employer paid for. If it treats any non-refunded transaction as active and ignores revocationType, someone who leaves the organization keeps access after the admin takes the seat back. The first produces support tickets. The second leaks revenue quietly.

Where the Listed Subscription SDKs Stand

Most teams in our subscription analytics directory don’t parse App Store transactions themselves. A vendor SDK and backend decide whether a user is entitled. Each vendor’s public iOS SDK release notes on GitHub, checked on 23 October 2026, show where things stand:

“No mention” is not the same as “broken.” Adapty, Qonversion and Superwall validate on their own servers, and a backend can handle a new enum value without an SDK release. Treat the table as a list of what is publicly documented, and ask the vendors about the rest.

RevenueCat’s change is the most concrete, and it comes with two caveats its own pull request spells out. First, the SDK only reads the assigned value from StoreKit “when building with Swift 6.4+.” On older toolchains, “non–family-shared cases” still map to .purchased. Second, it adds a public enum case, which the PR flags as risky for apps that switch on PurchaseOwnershipType without an @unknown default. And the SDK change is about representing the ownership type. On 26 August 2026 a RevenueCat staff answer on its community forum said “RevenueCat does not support assigned organization seats yet” for entitlement checks and suggested promotional entitlements as a stopgap. Nothing we found in public says whether the backend now activates entitlements for assigned transactions. That is the question to put to RevenueCat in writing.

Billing is a second open question, and it matters for every percent-of-revenue vendor. RevenueCat and Adapty both meter on gross revenue (we worked through the denominators in RevenueCat vs Adapty vs Superwall vs Qonversion). One organization buying forty seats is one transaction with quantity: 40. Whether your vendor books that as forty seats of revenue, or as one subscription at the single-seat price, decides both your dashboards and your bill. No vendor documents this yet. If you are close to a free-tier ceiling, the exact ceiling on each free plan is where a single large school order could push you over.

Worked Example: A 40-Seat School Order

Here is how the documented pieces fit together. We have not watched a production order happen. Take a language-learning app with one monthly subscription, built on StoreKit 2, no Family Sharing, created in October 2026, so multiseat is on by default.

1. A school buys 40 seats in Apple School Manager. That is one In-App Purchase, and its transaction carries quantity: 40.
2. The IT admin assigns 40 students through their device management provider. Each student’s device sees the subscription with ownership type assigned, not purchased.
3. Your app checks entitlements. If the app was built with an SDK or toolchain that maps assigned to purchased, the students probably get in. That happens by luck, not by design, and it means your analytics count 40 individual purchasers who never paid you. If your backend rejects unknown ownership types, all 40 hit the paywall.
4. In January, five students leave. The admin removes their seats, and their transactions carry revocationType: ASSIGNMENT_REVOKE. If nothing in your stack reads that field, the five keep access.
5. You decide in February to stop selling to schools and remove Apple School Manager. The school’s remaining 35 seats are canceled at the end of the next renewal. If you had disabled multiseat instead, they would keep renewing at 35 and could not add seats.

Every step uses a field or rule Apple documents today. The open questions are the ones in step 3: how your stack interprets assigned, and how your vendor meters quantity.

What to Do This Week

1. Find out whether you are selling to organizations. In App Store Connect, open each auto-renewable subscription’s purchase options. Or call GET /v1/subscriptions/{id} and read multiSeatStatus and marketSettings. If marketSettings includes APPLE_BUSINESS or APPLE_SCHOOL, you are live in that channel.

2. If your stack is not ready, narrow the channel before anyone buys. Removing APPLE_BUSINESS and APPLE_SCHOOL while you have no organization subscribers costs nothing. Doing it later cancels them at renewal. Group Purchases on the App Store are not live until “this winter,” so the organization stores are the only multiseat buyers right now.

3. If you want the channel, handle both directions. Grant access on ASSIGNED, revoke it on ASSIGNMENT_REVOKE, and make sure every switch over ownership type has a default branch. On RevenueCat, that means building with Swift 6.4+ on SDK 5.97.0 or later, and confirming that entitlements activate for assigned transactions. On Adapty, Qonversion or Superwall, ask the vendor directly, because nothing in their public release notes covers it yet.

4. Ask your vendor one billing question in writing. How does a multiseat transaction count toward tracked revenue: by seat, or as one subscription? It is the same kind of contract-specific boundary question we raised in the Apple link-out rate piece. It costs little to ask now and a lot to find out from an invoice.

What This Piece Does Not Claim

Commission. Apple’s 22 October and 16 September posts don’t state what Apple takes on Volume Purchasing or Group Purchases, and we haven’t verified it. The 13 October 2026 Apple Developer Program License Agreement update lists changes to Schedule 2 (Sections 1.1(b), 1.2(d)(iv), 3.1, 3.8(c)) for Group Purchases and Schedule 3 (Sections 1.1(b), 1.2(d)(iii), 3.1, 3.8(a), 3.8(c)) for Volume Purchasing. The terms are there, in the agreement you accepted, and not in this article.

Vendor support. The SDK table reflects public GitHub release notes on 23 October 2026, not vendor confirmation or testing. A vendor may handle assigned transactions on its servers without saying so in an SDK changelog, or may have shipped support since. Ask the vendor before you rely on either reading.

No listing changes. RevenueCat, Adapty, Qonversion and Superwall are scored in our directory on published pricing, billing basis and free-tier limits, and none of those moved this week. If a vendor publishes a policy on metering multiseat revenue, the listing gets updated against that vendor’s own pricing page.

FAQ

Is my subscription already available to organizations?

Probably. Every auto-renewable subscription defaults to multiSeatStatus: ENABLED. The exceptions are subscriptions created before 14 September 2026 that don’t use StoreKit 2 or that have Family Sharing on. Custom apps cannot opt out at all.

What happens if I turn off Apple Business later?

Existing subscribers in that channel are canceled at the end of their next renewal, and only the Account Holder can make the change. Disabling multiseat instead lets existing seat holders keep renewing at their current count.

How does an assigned seat show up in transaction data?

As inAppOwnershipType: "ASSIGNED", with quantity giving the seat count on the purchase. When a seat is taken back, the transaction carries revocationType: "ASSIGNMENT_REVOKE" and Apple says to revoke access. All of this is in App Store Server API 1.22 (28 September 2026).

Does RevenueCat support it?

iOS SDK 5.97.0 (21 October 2026) adds an assigned ownership type, but only reads it on Swift 6.4+ builds. A 26 August 2026 staff answer said entitlement support for assigned seats wasn’t there yet. Confirm the current backend behaviour with RevenueCat.

What commission applies?

Apple’s announcements don’t say. The governing terms are in Schedules 2 and 3 of the Apple Developer Program License Agreement as updated on 13 October 2026.

Sources: Apple Developer News, “Offer your subscriptions to businesses and schools,” 22 October 2026 (Volume Purchasing start; default-on; 28 October sandbox date and “this winter” for Group Purchases). Apple Developer News, “Get your subscriptions ready for iOS 27,” 16 September 2026 (multiseat enabled by default; Volume Purchasing dated 22 October 2026). Apple Developer News, “Updated Apple Developer Program License Agreement now available,” 13 October 2026 (Schedule 2 and 3 sections listed). App Store Connect Help, “Manage purchase options for auto-renewable subscriptions” (pre-14 September opt-out exceptions; custom apps; channel removal cancels at next renewal; App Store availability cannot be removed after approval; Family Sharing interaction). App Store Connect API, “Configuring multi-seat subscriptions for organizations” (multiSeatStatus, marketSettings values, ENABLED default, DISABLED behaviour, Family Sharing auto-disable). App Store Server API changelog, version 1.22, 28 September 2026, and the inAppOwnershipType, quantity and revocationType reference pages. RevenueCat purchases-ios release 5.97.0 (21 October 2026) and pull requests #8064 and #8072 on GitHub (Swift 6.4+ condition; enum-case risk; Customer Center and win-back handling). RevenueCat Community thread “Apple organizational subscription volume purchasing: RevenueCat entitlement support,” staff answer of 26 August 2026. Adapty (AdaptySDK-iOS), Qonversion (qonversion-ios-sdk) and Superwall (Superwall-iOS) GitHub release notes, last eight releases each, checked 23 October 2026. Billing-basis figures are from ToolMasta’s verified directory listings. Nothing here is legal advice.