Muhammad Tayyab
Apple switched on multiseat purchasing for most StoreKit 2 subscriptions on Oct 22. Here is what is on by default, what to decide this week, and how to price seats.
App Store multiseat subscriptions are live: since October 22, 2026, organizations and schools can buy your auto-renewing subscription in volume, and Apple has enabled this by default in App Store Connect unless you changed the setting before. If you run a StoreKit 2 subscription app, you are probably already listed in Apple Business and Apple School Manager today. This guide covers what is on by default, what to decide this week, and how to price seats so a team purchase does not undercut your own plans.
I build and ship indie apps from Lahore, and the pattern I keep seeing is that platform defaults get flipped on while founders are busy shipping. A default is a pricing decision somebody else made for you. Here is how to make it yours.
Apple's developer news post from October 22 announced volume purchasing for subscriptions. Organizations that use Apple Business or Apple School Manager buy seats through a single Apple In-App Purchase, then assign and manage them with their existing device management tools. Seats can be added or removed at any time.
Two other dates matter:
So there are two different channels. Volume purchasing through Apple Business and Apple School Manager is live now. Group purchases in the normal App Store flow are coming, and you can start testing them this month.
Apple's App Store Connect help page is the best reference for the rules. The parts that affect most indie apps:
The WWDC26 session on selling to groups and organizations adds that both purchase types require StoreKit 2, and that selling to groups is on by default for most StoreKit 2 subscriptions. You can limit a subscription to Apple School Manager only, or turn group and organization sales off entirely. Individual App Store sales continue either way.
If you have not touched your subscriptions since the StoreKit 2 migration or a commitment-plan change, open App Store Connect now and look at each one. The default may already be live.
From the WWDC26 session, the mechanics are:
The session also names App Store Server API group management endpoints that let you look up every group a customer belongs to and every member of a group. It does not list paths or response fields, so read Apple's documentation before you build against them.
The main shift for your code is that the buyer is no longer always the user. Someone pays, someone else gets a seat.
Opt in if your product already has a team story: shared workspaces, classroom use, a tool an IT admin would deploy to a fleet of devices. For those apps, volume purchasing opens a buying route that did not exist before, and it comes with Apple's own seat assignment, so you do not have to build invitations yourself.
Wait, or switch it off, if your pricing assumes one person per subscription, if your support load scales with accounts rather than seats, or if your backend cannot yet separate the buyer from the user. A half-ready multiseat setup is worse than none, because the first school that buys 40 seats will find every rough edge. If you are also deciding how to handle storefront-specific terms, my guide to Apple's EU terms covers a similar "decide before the default decides for you" problem.
Per subscription, App Store Connect lets you pick the App Store, Apple Business and Apple School Manager. Apple's help page says App Store availability cannot be removed after approval, so the real choices are whether to add the two organization channels and whether to allow multiple seats.
If your app is a personal tool, such as a habit tracker or a single-user photo editor, turn multiseat off. If a team could plausibly share it, leave it on and plan for it.
Turning multiseat off on an approved subscription needs a confirmation and has consequences, per Apple's help page:
Removing Apple Business or Apple School Manager from an approved subscription is stricter: only the Account Holder can do it, and existing subscribers will be cancelled at the end of their next renewal. Treat that as a one-way door and talk to your customers first.
If Family Sharing is on and you enable multiseat, only the group purchaser's access includes Family Sharing. Every other seat is for individual use. Apple also notes that once Family Sharing is turned on you cannot turn it off. If you are weighing Family Sharing, decide on multiseat at the same time.
Default pricing is a per-seat price. WWDC26 session 391 describes optional volume pricing with up to five price bands and per-seat discounts. The speaker's example is $19.99 per seat per month for seats 1 to 20, $13.99 for seats 21 to 40 and $10.99 from seat 41.
Here is that example worked through for a 50-seat purchase (Apple's example numbers, not a recommendation):
// example: Apple's WWDC26 volume-pricing example, 50 seats, per month
seats 1-20 : 20 x $19.99 = $399.80
seats 21-40 : 20 x $13.99 = $279.80
seats 41-50 : 10 x $10.99 = $109.90
total : $789.50
average/seat : $15.79 (about 21% below the $19.99 base)Session 391 puts that average at about 20% below base. For an indie app the question is whether a 20% discount at 50 seats still covers support, server cost and the commission. Do that math before you add bands. If your plans are already usage-based, see how a custom billing engine can handle per-seat and usage pricing and compare it with what Apple now offers.
Your app should grant access from the transaction StoreKit gives each assigned member, not from who paid. The simplest approach is to keep using current entitlements:
// example: grant access from whatever entitlement this Apple Account holds
import StoreKit
func hasActiveSubscription(groupID: String) async -> Bool {
for await result in Transaction.currentEntitlements {
if case .verified(let tx) = result, tx.productID == groupID {
return true
}
}
return false
}That works when each assigned member receives their own transaction, which is what Apple describes. Do not assume the person who purchased is the only one who needs access, and do not store a single "owner" flag on your server.
For group purchases in your own UI, Apple says your app collects the seat count and passes it into the StoreKit 2 purchase request. StoreKit 2 has a quantity purchase option for this:
// example: buying more than one seat (verify against current StoreKit docs)
let result = try await product.purchase(options: [.quantity(seats)])I have not tested this against the group purchase flow, because group purchases only reach the App Store this winter. Test it in the Sandbox Apple Account in November and read the App Store Connect API page on configuring multi-seat subscriptions before shipping.
If your backend maps one App Store transaction to one user, you need to revisit it. With seats, the purchaser pays and members redeem. Dashboards that count "subscribers" will start undercounting users and overcounting accounts, or the opposite. Decide now what you call a customer. Campaign attribution has the same problem: a campaign link credits one install, but one purchase may serve twenty people.
Organizations buy through Apple, but they still need a page that tells an IT admin what they are buying: seats, what each seat gets, data handling, and where to get support. A short team-plan page also helps when a school asks how to roll the app out.
They let a customer buy an auto-renewable subscription in quantities greater than one. The buyer is the group purchaser, who manages the shared subscription and controls who has access, so a team, classroom or organization can share one purchase.
Per Apple's help page, multiseat purchasing is enabled by default in App Store Connect unless you previously changed the setting. Subscriptions created before September 14, 2026 that do not use StoreKit 2, or that have Family Sharing on, are opted out by default.
Yes, with the Account Holder, Admin or App Manager role. New customers can then buy only one seat and the subscription leaves Apple Business and Apple School Manager. Existing subscriptions keep renewing, and the purchaser can remove seats but not add them.
Yes. WWDC26 session 391 says both group purchases and volume purchasing require StoreKit 2.
Default pricing is per seat. Volume pricing supports up to five price bands with per-seat discounts. In Apple's example, $19.99 for seats 1 to 20, $13.99 for 21 to 40 and $10.99 from seat 41 averages about 20% below base at 50 seats.
From November 2026 in your Sandbox Apple Account. Apple says group purchases reach the App Store this winter.
If you are building an app with team plans, or need help moving a billing setup to StoreKit 2, get in touch.
Composio Instant gives AI agents a wallet for paid tools, and Exa 3.0 and RunInfra are pitching agents as customers. Here's where agent payment standards like MCP, x402, ACP, AP2 and MPP actually stand, plus a practical checklist for making your SaaS or API something an agent can find, pay for and use safely.
Pieter Levels cancelled almost all his business SaaS, Marc Lou replaced Beehiiv with a vibe-coded newsletter tool, and McKinsey says 32% of organizations skipped at least one software purchase to build in-house. Here's a total-cost framework for deciding when building beats buying.
A fresh study found ChatGPT and Gemini quoting stale prices for recently repriced SaaS tools, often from old pages the vendor forgot about. Here's a practical checklist to make your free tier, limits and plan names unambiguous enough that AI assistants quote you correctly.