Multiseat subscriptions are on by default. Check yours before Oct 22

· 6 min read

#apple-dev

If you sell an auto-renewable subscription with StoreKit 2, it can probably already be bought in bulk, because Apple turned multiseat purchases on by default. Volume Purchasing opens on October 22, 2026, so this week is a good time to decide whether you actually want that, and at what price.

Four coworkers smiling around a laptop at a table
Photo by Jud Mackrill on Unsplash

What changed

Apple announced two ways to sell one subscription to many people at WWDC26 and set the dates in a news post on September 16:

On October 13, Apple updated the Developer Program License Agreement. Among other changes, it adds terms for offering multiple seats through Group Purchases (Schedule 2) and for offering subscriptions to Apple Business and Apple School Manager organizations through Volume Purchasing (Schedule 3). You have to sign in and accept the new terms, so it is worth reading those schedules while you are there.

Am I opted in?

A stack of iPads in rugged school cases, one with a sticky note on its screen
Photo by Arthur Lambillotte on Unsplash

Apple's App Store Connect help page is clear about the defaults:

So if your app uses StoreKit 2 and your subscription doesn't use Family Sharing, the answer is most likely yes.

You find the setting under your app's Subscriptions, then the subscription, then Purchase Options. It asks two questions: whether a customer can buy multiple seats, and where the subscription can be bought (the App Store, Apple Business, Apple School Manager). Apple Business and Apple School Manager only sell multiple seats; the App Store sells both individual and group purchases. You need the Account Holder, Admin or App Manager role to change it.

Read the fine print before you flip anything

A few rules on that help page are easy to miss, and some of them can't be undone:

My reading is that "on" is the low-risk default and "off later" is the one with consequences for real customers. If you are unsure, it's better to decide now, before October 22, than after an organization has bought 40 seats.

Price it on purpose

By default every seat sells at your current price. In session 391, Apple shows volume pricing: up to five price bands, each with its own seat range and per-seat price. Apple's example uses $19.99 per seat per month for seats 1–20, $13.99 for 21–40 and $10.99 from seat 41, which works out to about 20% below the base price for a 50-seat purchase. The same session mentions plans available only on Apple School Manager, for verified educational institutions, with their own pricing.

Price increases also work differently for groups. According to Apple's pricing help page, the first seat follows the normal consent rules. Beyond the first seat, consent is needed if the group purchaser's total price goes up by more than 50%, or if they are in a country or region that needs consent for any increase. If the purchaser doesn't consent in time, the entire subscription expires, including all seats. One missed consent prompt can now cancel a whole team, so I would be careful with price increases on subscriptions that sell to groups.

What your code has to do

A hand holding an iPhone with its home screen open
Photo by Jotform on Unsplash

Less than I expected. For Volume Purchasing, session 391 describes no purchase code at all: the organization buys outside your app, and your job is making the subscription available. For Group Purchases, you build the UI where the buyer picks a number of seats and pass that count into the StoreKit 2 purchase. Apple then creates the invite link, tracks who accepts, and handles cancellations.

The detail that matters for most apps: for each member assignment, the App Store creates a transaction, and you grant that member access. If your app already decides access from the current entitlements, the member's device is handled like any other subscriber:

import StoreKit

func hasActiveSubscription(in groupID: String) async -> Bool {
    for await result in Transaction.currentEntitlements {
        guard case .verified(let transaction) = result else { continue }
        if transaction.subscriptionGroupID == groupID,
           transaction.revocationDate == nil {
            return true
        }
    }
    return false
}

This is my own sketch, not Apple's sample, and it only uses APIs that existed before iOS 27. What I could not find is Apple documentation that names the new seat-related fields in StoreKit or the App Store Server API. The session says there are new App Store Server API endpoints for group management (finding the groups a customer belongs to and the members of a group), and for custom invitation systems. If your access logic lives on a server keyed to the original purchaser, read those docs before winter, when Group Purchases arrives.

My short checklist

  1. Accept the updated license agreement and read Schedules 2 and 3.
  2. Open Purchase Options for each subscription and confirm what is on.
  3. Decide whether Apple Business or Apple School Manager makes sense for your app before October 22.
  4. If you keep multiseat, consider volume pricing instead of the flat default.
  5. Make sure access comes from verified transactions, not from who made the purchase.

Sources