---
title: "Apple Multiseat Subscriptions Are On by Default: Check Yours"
author: "Nate Laquis"
author_role: "Founder & CEO"
date: "2026-10-26"
category: "Cost & Planning"
tags:
  - Apple multiseat subscriptions
  - App Store Connect
  - StoreKit 2
  - volume pricing
  - B2B app subscriptions
excerpt: "Since October 22, 2026, businesses and schools can buy your app subscription in bulk through Apple Business and Apple School Manager unless you opted out. Here is what that means for your pricing, your support load and your revenue reports."
reading_time: "10 min read"
canonical_url: "https://kanopylabs.com/blog/apple-multiseat-subscriptions-default-on-app-store-connect-b2b-pricing"
---

# Apple Multiseat Subscriptions Are On by Default: Check Yours

## What Apple Switched On

On October 22, 2026, Apple started letting organizations and educational institutions buy app subscriptions in volume. A company or a school makes one In-App Purchase through Apple Business or Apple School Manager, gets a pool of seats, assigns those seats with their device management tools, and adds or removes seats whenever they like. For a founder who sells a subscription app, that is a new sales channel you did not have to build.

It is also a setting you did not have to turn on. Apple enabled multiseat purchasing by default in App Store Connect, unless you had previously adjusted that setting. If you never touched it, your subscriptions are already eligible for institutional sale. Nobody asked you.

That is the part worth stopping on. A default-on feature that changes who can buy your product, at what price, and through which channel is not a footnote. It is a pricing decision somebody made for you, and you should decide whether you agree with it.

The rest of this post is what I would check this week if one of our clients had a subscription app in the store. Most of it takes an afternoon. A little of it needs a code change.

![Analytics dashboard showing subscription revenue and seat counts across several customers](https://images.unsplash.com/photo-1551288049-bebda4e38f71?w=800&q=80)

## Who Is Opted Out Already and Who Is Not

Apple carved out some exceptions, and they matter because they decide whether you have anything to do today.

- **Subscriptions created before September 14, 2026** are opted out by default if they do not use StoreKit 2, or if Family Sharing is turned on.

- **Subscriptions created on or after that date** follow the new default, which is on.

- **Custom app subscriptions** cannot be managed this way. They are available to institutions automatically.

- **StoreKit 2 is required.** If your app still runs the original StoreKit purchase flow, you are mostly outside the program, which may be good news or bad depending on what you want.

So the first job is a simple audit. Open App Store Connect, go through each subscription group, and write down three things for every product: when it was created, whether Family Sharing is on, and whether the app that sells it is on StoreKit 2. That gives you a list of what is exposed today and what is not.

Only a few roles can change the purchase options: Account Holder, Admin and App Manager. If your agency or a contractor set up the store listing and you never got a role, find out who has it before you need to change something on a deadline.

One more note on scope. This post covers the business and school side. Apple said group purchases for consumers are coming to the App Store this winter, with sandbox testing starting in November 2026. No date has been given for the consumer side, so treat anything you read that claims one as a guess.

## The Money: Volume Bands and What They Do to Revenue

Each seat defaults to your current App Store Connect price. You can set up to five volume price bands, and that is where the math gets interesting, because Apple's own example is a discount ladder.

Take a $19.99 monthly subscription. In Apple's example, seats 1 through 20 cost $19.99 each, seats 21 through 40 cost $13.99, and from seat 41 onward each seat costs $10.99. A company that buys 50 seats pays $789.50 in total, which is about $15.79 per seat, roughly 21 percent below the base price.

Run your own version of that before you decide anything. A few questions drive the answer:

1. **Who is your real buyer today?** If a meaningful number of your individual subscribers are actually employees expensing the app, a company bulk purchase could replace many full-price subscriptions with one discounted pool. That is a real revenue risk, not a theoretical one.

2. **What is your cost per seat?** If every active user costs you model inference, transcription minutes or storage, a 45 percent discount on the top tier can push a seat underwater. Subscription apps with AI features are the ones to check first.

3. **Do you have a sales motion at all?** If you have no way to reach a procurement team, the default will mostly sit there. If you do, volume pricing is a tool you were missing.

On Apple's cut, the October announcement did not mention commission, and I am not going to quote you a rate from a blog summary. Read your Paid Applications Agreement and the current subscription terms. The commonly reported structure is 30 percent, dropping to 15 percent after a subscriber has paid for more than a year, and nothing in this change appears to alter it. What nobody has explained is how that one-year clock applies when an organization reassigns a seat from one person to another. Ask your finance person to flag it, because it affects your margin model.

If you are still deciding between seat, credit and usage pricing in general, our breakdown of [credits vs seats vs usage for AI features](/blog/ai-feature-pricing-credits-vs-seats-vs-usage-saas) covers the tradeoffs, and most of it carries over to a pool of seats you did not design.

## What You Should Decide: Opt In, Opt Out or Reprice

There are three reasonable positions, and which one fits depends on the product.

### Stay opted in and price for it

This is right when your app is already something people use at work. Project tools, field service apps, language learning for teams, scheduling, note-taking, anything where a manager would plausibly buy for ten or fifty people. Set the volume bands on purpose. Do not accept a default where seat 41 is priced like seat 1 and then be surprised when a school district buys 400 seats at the wrong price. Decide where you want the discount to start, and make it start there.

### Opt out for now

This is right when your economics only work at consumer prices, when your support team cannot take institutional questions yet, or when you want to wait until Apple explains reporting. Turning multiseat off stops new seat sales and removes the subscription from Apple Business and Apple School Manager. Existing seats keep renewing until the group purchaser cancels, but nobody can add seats.

Be careful with the harsher switch. Removing Apple Business or Apple School Manager as a storefront cancels existing institutional subscribers at their next renewal, and only the Account Holder can do it. You do not want to find that button by accident. App Store availability itself cannot be removed once your app is approved.

### Treat it as a pilot

For most of the founders I talk to, this is the honest answer. Leave it on, set a conservative discount ladder, watch who buys over the next 60 days, and adjust. The cost of being wrong in a pilot is small. The cost of ignoring a default that redirects your best customers into a discounted pool is not.

Whichever way you go, write the decision down with a date. In six months nobody will remember why seat 21 costs what it does.

## The Engineering Side: StoreKit 2 and Entitlements

Multiseat requires StoreKit 2. If your app is on it already, most of what follows is verification. If it is not, this change is a reason to schedule the migration you have been putting off.

Here is what I would have a developer confirm, in order:

- **Entitlement checks come from the transaction, not from an account assumption.** A seat assigned by an organization is still an entitlement on a device, but the person using it did not pay. If your code assumes the buyer and the user are the same person, receipts, restore flows and "manage subscription" screens will behave oddly.

- **Your backend handles server notifications for seat changes.** Seats can be added, removed and reassigned at any time. If you keep your own user table with a subscription status, it has to follow those events or you will give away access to people whose seat was removed, or lock out people whose seat was just assigned.

- **Your paywall does not show a purchase prompt to someone who already has a seat.** It sounds obvious. It is the bug we see most often in subscription apps, because the paywall was written when there was only one way to be a subscriber.

- **Support can see why someone has access.** When an employee writes in saying they cannot use the app, "your company's seat was reassigned" is a different answer from "your payment failed." Give your support tooling a field for it.

If the app has no clean subscription layer at all, start with our guide to [implementing subscription billing](/blog/how-to-implement-subscription-billing) and the walkthrough on [building a subscription app with paywalls](/blog/how-to-build-a-subscription-app-with-paywalls). Both assume one buyer per account, which is the assumption this change breaks, so read them as a baseline and then add the seat cases.

A realistic effort estimate for a StoreKit 2 app that needs the entitlement and webhook cleanup is a few days to two weeks of developer time, depending on how much custom logic sits around your paywall. A StoreKit 1 app that needs the migration first is usually three to six weeks, because the migration touches restore flows, receipt validation and every place you read subscription state.

![Developer reviewing subscription entitlement code on a laptop](https://images.unsplash.com/photo-1460925895917-afdab827c52f?w=800&q=80)

## What Apple Has Not Told You Yet

Plan around the gaps, because Apple left a few open.

- **Reporting.** Apple has not said how institutional purchases will show up in sales reports and analytics. Until it does, assume your dashboards will undercount or blur them, and do not reforecast churn off a month where bulk seats landed.

- **Ranking.** How subscriptions are ranked inside Apple Business is not explained. Nobody can tell you yet whether a listing there needs the same attention as App Store search.

- **Consumer group purchases.** Coming this winter, no date.

- **The commission clock.** Covered above. Seat reassignment is unaddressed.

I would not wait on any of these to make a decision. I would wait on them before building anything big. A custom admin dashboard for institutional customers, for example, is the kind of project that looks smart now and gets obsoleted by what Apple ships in the spring.

There is also a backstory here. Apple has been steadily changing what it does and does not control in the store, from the EU rules we covered in [Apple's EU App Store terms](/blog/apple-eu-app-store-terms-october-2026-founders-guide) to the review changes this month. The pattern is that a policy changes on a Tuesday, the default favors Apple's preferred behavior, and the developer finds out in a newsletter. Put someone on your team in charge of reading the developer news feed once a week. It takes ten minutes.

## A One-Afternoon Checklist

If you only do five things this week, do these.

1. Log into App Store Connect and list every subscription with its creation date, Family Sharing setting and multiseat status.

2. Decide on each product: on, off or pilot. Write the decision and the date in your pricing doc.

3. If on, set your volume bands. Do not leave the defaults. Check that the lowest band still covers your cost per seat.

4. Ask your developer whether the app is on StoreKit 2 and whether the backend handles seat add, remove and reassign events.

5. Tell support and finance. Support will get questions from employees who did not buy the thing they are using. Finance will see revenue they cannot map to a user.

None of this is hard. All of it is easier before the first 200-seat purchase than after.

The bigger lesson is about the way founders treat store settings. App Store Connect is a pricing and distribution system, and it changes under you. Treat it like production infrastructure: someone owns it, changes get reviewed, and defaults get checked after every announcement.

![Founder reviewing a pricing spreadsheet with a calculator and notes](https://images.unsplash.com/photo-1554224155-6726b3ff858f?w=800&q=80)

## When to Bring in Help

You can do the audit and the pricing decision yourself. Bring in a developer when you hit any of these: your app is on StoreKit 1, your backend keeps its own subscription status and has no handling for seat changes, or you want to build a real B2B sales motion on top of the store rather than just tolerate the default.

That last one is where the opportunity is. A consumer subscription app that gets a quiet second life as a team product, with a proper admin view, seat pricing and a sales page, can grow without a new acquisition channel. It can also quietly cannibalize your best individual customers if you do it by accident. The difference is whether you made the call or Apple did.

If you have a subscription app and want a second pair of eyes on the pricing, the StoreKit 2 migration or the entitlement logic, [Book a free strategy call](/get-started).

---

*Originally published on [Kanopy Labs](https://kanopylabs.com/blog/apple-multiseat-subscriptions-default-on-app-store-connect-b2b-pricing)*