App licences can be revoked and reassigned. Book licences cannot. That one difference should decide how your organisation buys.
Buying Apple applications in volume means the organisation keeps ownership: licences come back from leavers and retired devices and return to the pool. Apple publishes exact numbers to design around, 1,000 licences and 100 apps per Blueprint, transfers of up to 24,999 at a time, and purchase processing that slows past 5,000 licences. We set up volume app distribution for Indian organisations, including the recovery loop that most never build, remotely from Hyderabad.
- RevocableApps recovered and reassigned
- Not booksBook licences cannot be revoked
- 24,999Licences transferable at a time
- Even freePayment method required for free apps
Volume purchasing only saves money if licences come back.
The buying side is easy, and most organisations get it right. The recovery side is where the value actually sits, and it is the half that usually never gets built.
- Apps can be revoked and reassigned to different devices and users, which turns a purchase into a reusable asset rather than a per-person cost. That is the mechanism the whole model rests on.
- Without a leaver process that actually triggers revocation, the pool only shrinks: every departure quietly removes a licence from circulation and every new joiner becomes a fresh purchase, which is precisely the situation volume purchasing was meant to replace.
- Books are the permanent exception: user-only, non-revocable, non-reassignable. Book spend should be forecast as consumed, and mixing apps and books in one budget line produces a forecast that drifts every quarter.
- The measurable version of the question is simple: how many app licences left with departing staff in the last twelve months? That count, against what those apps cost to rebuy, is usually the entire business case for building the recovery loop properly.
Eight facts that shape an Apple application programme.
The organisation keeps ownership
Apps bought in volume can be revoked and reassigned to different devices and users, so the organisation retains full ownership and control of what it bought. That single capability is the entire commercial case for volume purchasing over asking staff to buy apps and claim reimbursement.
Books behave differently, permanently
Apple Books bought through Apple Business can be distributed only to users, never to devices, and they cannot be revoked or reassigned. A book licence issued to somebody who then leaves is simply consumed. That belongs in the budget conversation before the purchase, not in a reconciliation afterwards.
Assign to devices or to users
Managed apps can go to devices, or to users holding either a Managed Apple Account or an unmanaged personal Apple Account. Device assignment needs no Apple Account sign-in at all, which is usually the cleaner model for shared and corporate hardware such as billing iPads and field devices.
Installation works without the App Store
Through device management, apps install and update remotely even when the App Store app has been removed from the device. Locked-down deployments that hide the store entirely, common on kiosk and counter devices, keep full application delivery through the management platform.
A payment method is required even for free apps
Apple is explicit: the payment method must be set up before any app licences can be obtained, including free ones. Organisations planning a free-apps-only rollout discover this at deployment time, which is the worst moment for a finance approval to enter the critical path.
Buying is a role permission, not a login
Obtaining licences requires signing in as a user whose role carries the apps and books purchasing permission. It is a delegated capability held by named people, which deserves a deliberate decision alongside the wider role model rather than defaulting to whoever has administrator access.
Licences belong to an organisational unit
The organisational unit for the licences' initial assignment is selected at purchase. In an Indian group with several entities or locations, buying against the wrong unit strands the licences where the people who need them cannot reach them, and the correction is a transfer, not an edit.
Large purchases do not process immediately
Up to 5,000 licences process immediately. From 5,001 to 19,999 they process daily after 1:00 p.m. Pacific time, and at 20,000 or more daily after 4:00 p.m. Pacific. For an Indian organisation those windows fall overnight, so a large buy on the morning of a rollout arrives a day late by design.
Apple publishes hard limits. Design inside them rather than discovering them.
Each of these has stalled a deployment somewhere, and all four are avoidable with an hour of planning.
- Up to 1,000 licences and up to 100 apps per Blueprint. Estates with large application catalogues need to plan how apps are grouped rather than assuming one configuration can carry everything the organisation uses.
- Transfers move up to 24,999 licences at a time, transfers do not disrupt existing assignments, and only unassigned licences can be transferred. That last clause is the one that bites: licences already on devices or users must be recovered before they can move between units.
- Purchases above 5,000 licences process daily on Pacific time, and above 20,000 after 4:00 p.m. Pacific. For India that is an overnight wait at best, so large purchases belong in the week before a rollout, never on its morning.
- Redemption codes distribute only within the same country or region as your organisation, are unavailable in South Korea, and once redeemed can never be reassigned. Managed distribution avoids all three constraints, which is why it is the default recommendation.
Four things that keep an application programme from leaking money.
We build the reclamation loop, not just the purchase
Apps can be revoked and reassigned to different devices and users, which is what makes purchased software a reusable pool. We wire revocation into the actual leaver process, with a named owner, because a recovery step that exists only in a document recovers nothing.
We separate books from apps in the budget
Books are user-only, non-revocable and non-reassignable, so book spend is consumed the moment it is assigned. Treating it as recoverable is a forecasting error that compounds quietly, and it is far cheaper to prevent at budgeting time than to explain at year end.
We schedule purchases around the processing windows
Above 5,000 licences, purchases process daily on Pacific time, which reaches India overnight at best. We put large buys in the week before the rollout and reconcile the counts after processing, so the deployment date never depends on a purchase still in a queue.
We get the organisational unit right the first time
Licences are bought against an organisational unit, and correcting a mistake later means a transfer in which only unassigned licences can move. For Indian groups with multiple entities, mapping the unit structure before the first purchase avoids an unwind that touches deployed devices.
Four phases across roughly three to five weeks.
- 01Week 1· Week 1
Commercial and role setup
A payment method must exist before any app licence can be obtained, even a free one, and purchasing is a role permission that needs assigning to named people. Both are administrative rather than technical, and both block everything downstream until somebody owns them.
- Payment method configured and validated
- Purchasing permission assigned to named users
- Organisational unit structure confirmed
- Approval step for purchases agreed
- 02Week 2· Week 2
Application catalogue and assignment model
Which applications, whether each goes to devices or to users, and which need the separate full-featured or custom version a developer may offer for organisational deployment. Device assignment avoids requiring an Apple Account sign-in, which usually suits corporate hardware best.
- Application catalogue documented with owners
- Device-versus-user assignment decided per application
- Custom app requirements identified with developers
- Grouping designed against the 100 apps per Blueprint limit
- 03Week 3· Week 3
Purchase with the processing windows in mind
Up to 5,000 licences process immediately; larger purchases process daily on Pacific time, which lands overnight for India. Licences are bought against a specific organisational unit, so that selection has to be correct at the moment of purchase, not corrected afterwards by transfer.
- Licence quantities calculated per application
- Purchases scheduled ahead of the rollout date
- Initial organisational unit set correctly per purchase
- Licence counts reconciled after processing completes
- 04Weeks 4-5· Weeks 4-5
Distribute, then build the recovery loop
Applications deployed through the management platform and verified installing, then the part that pays for everything: a documented leaver and device-retirement process that revokes licences and returns them to the pool, with utilisation reporting so finance can see the pool working.
- Applications deployed and installation verified
- Leaver process that recovers app licences documented
- Licence utilisation reporting established
- Transfer procedure documented for reorganisations
Six situations where volume distribution changes the outcome.
A company reimbursing App Store purchases
Expensed purchases belong to the individual and leave with them, and there is no central record of what is deployed where. Moving to managed distribution makes each licence an asset the organisation owns and recovers, which typically pays for the change within one staffing cycle.
A retail estate with shared iPads
Device assignment installs apps without anyone signing in with an Apple Account, and installation works even where the App Store has been removed from the device. For billing counters and shared floor devices across Indian retail, that combination is the entire requirement.
A group restructuring its entities
Licences sit with an organisational unit and move only by transfer, up to 24,999 at a time, and only while unassigned. A group restructure therefore needs the licence position mapped in advance, not treated as an administrative afterthought once the org chart is signed.
A school distributing apps and books together
Apps go to devices or users and come back; books go to named users only and never come back. On a shared iPad programme, that difference decides what can be issued to a class set and what must be issued to individual students, and the budget should reflect it.
A firm that must evidence software entitlement
Central purchasing produces one record of what was bought, where it sits and who holds it. For audits, client security reviews and DPDP-era governance questions, that record is materially easier to present than a stack of expense claims scattered across personal accounts.
A team deploying a developer-supplied app
Developers may offer a separate full-featured version of an app, sometimes as a Custom App, for organisations deploying at scale. Establishing whether one exists before designing around the public version avoids rebuilding the deployment when the better option surfaces later.
How Indian organisations get applications onto Apple devices.
| Feature | Managed distribution | Redemption codes | Staff buy and claim |
|---|---|---|---|
Organisation retains ownership | Yes | No, once redeemed | No |
Revocable and reassignable | Yes | No | No |
Assignable to devices | Yes | No | No |
Works without the App Store on the device | Yes | No | No |
Cross-border distribution | Managed centrally | Same country or region only | Uncontrolled |
Recovered when somebody leaves | Yes | No | No |
Central visibility of what is deployed | Yes | Partial | None |
Finance administration | One purchasing route | One purchasing route | Per-person expense claims |
Suitable at scale | Yes | Legacy approach | No |
Right answer for a growing estate | Yes | Rarely | No |
Two content types, two very different sets of rules.
| Behaviour | Managed apps | Books | |
|---|---|---|---|
| Assignable to devices | Yes | No, users only | |
| Assignable to users | Yes, managed or personal Apple Account | Yes | |
| Revocable | Yes | No | |
| Reassignable to another person | Yes | No | |
| Recoverable when somebody leaves | Yes | No | |
| Installable without the App Store present | Yes, through device management | Not applicable | |
| Ownership retained by the organisation | Yes | Licence is consumed | |
| Budget treatment | Reusable pool | One-time spend per person |
Five steps, and the first one is commercial.
- 1
Set up payment and purchasing permissions
Week 1
The payment method is required before licences can be obtained, even free ones, and buying requires a user whose role carries the apps and books permission. We get both decided and configured first, because they are administrative gates on everything that follows.
- 2
Build the application catalogue
Week 2
Every application with an owner, a justification, and a device-or-user assignment decision. Where a developer offers a full-featured or custom version for organisational deployment, we identify it now, before the public version gets configured everywhere.
- 3
Design within the published limits
Week 2
Up to 1,000 licences and 100 apps per Blueprint. For larger Indian estates that shapes how applications are grouped, and grouping is far easier to design correctly at the start than to unpick once devices already carry the configuration.
- 4
Purchase against the right unit, at the right time
Week 3
Licences are assigned to an organisational unit at purchase, and quantities above 5,000 process overnight India time. Purchases are scheduled ahead of the rollout, the unit is verified before confirming, and counts are reconciled once processing completes.
- 5
Deploy, then build the recovery loop
Weeks 4-5
Applications deployed through the management platform, then a documented leaver and device-retirement process that revokes licences back to the pool. That loop is what converts volume purchasing from a buying mechanism into an actual cost control.
What Indian organisations ask about Apple volume app distribution.
Fifteen checks worth running.
Commercial setup
- Is a payment method configured?Required even for free apps.
- Who holds the purchasing permission?It is a role permission, held by named people.
- Is there an approval step for purchases?Decide before, not after.
- Which organisational unit is buying?Set at purchase time, corrected only by transfer.
- Is volume content available for our region?Availability is country and region dependent, so confirm rather than assume.
Assignment model
- Device or user assignment, per app?Device assignment avoids Apple Account sign-in.
- Do users have Apple Accounts where needed?Managed or personal both work for user assignment.
- Are we near 100 apps per Blueprint?A published limit.
- Are we near 1,000 licences per Blueprint?Also published.
- Do any apps have a custom organisational version?Developers may offer one for scale deployment.
Lifecycle
- Does the leaver process revoke app licences?Apps are revocable. Books are not.
- Are books budgeted separately from apps?Book spend is consumed, not pooled.
- Are large purchases scheduled ahead?Above 5,000 licences, processing is overnight for India.
- Do we know the transfer limit?24,999 at a time.
- Are licences unassigned before transfer?Only unassigned licences can move.
The pages around this one.
Managed Apple Accounts
The account identity behind user-based assignment, and the published service exclusions worth reading first.
Learn moreApple Business migration
What changed in the platform in April 2026, including the renamed Get Apps and Get Books.
Learn moreApple Configurator
The Mac tool for bringing retail-bought devices into Apple Business so apps can reach them.
Learn moreCount the app licences that left with departing staff last year.
Every application licence in that count was recoverable, because apps can be revoked and reassigned. That number, against what the apps cost to rebuy, is usually the whole business case for building the recovery loop properly. Enquiries answered within 4 business hours, and managed clients work under a 30 minutes response SLA.