Apple Custom App Pricing: who should use it

Apple's Custom App Pricing lets you sell your app to specific organisations at negotiated prices through Apple Business Manager or Apple School Manager — but it is not the right tool for every developer. Here is how it works and who actually benefits.

Most App Store pricing conversations focus on the familiar tier picker — choose a price point, choose territories, ship. But Apple runs a second, quieter pricing system in parallel: Custom App Pricing, distributed through Apple Business Manager (ABM) and Apple School Manager (ASM). It lets you sell your app to specific organisations at negotiated rates, skip the public storefront entirely, and build predictable B2B revenue without competing for search placement.

The catch: Custom App Pricing is designed for a specific type of sale. Use it for the wrong model and you will spend weeks in setup for little additional gain. This post covers how the mechanics work, which buyer profiles benefit most, where the system falls short, and how to switch it on in App Store Connect.

What "Custom App" actually means

In Apple's terminology, a Custom App is an app you distribute to one or more named organisations — not to the general public — via ABM or ASM. The organisation can be a business, government agency, school district, non-profit, or any entity registered with Apple Business Manager. The app itself may be:

• A white-labelled or lightly customised version of your public App Store title
• A purpose-built enterprise tool that was never intended for the consumer store
• Your standard app offered at a negotiated price point for volume buyers

Custom Apps do not appear in the App Store's public catalogue. Organisations receive a redemption URL or a managed distribution token; IT admins push the app to employee or student devices via Mobile Device Management (MDM), typically without the end user ever opening the App Store themselves. Apple's standard revenue share applies — 70/30 for most developers, 85/15 under the Small Business Program for those earning under $1 million annually.

Pricing mechanics: tiers, volume, and what you can negotiate

Custom App Pricing uses the same underlying price tier grid that governs regular App Store purchases — the same 900-plus price points Apple restructured in 2023. You pick a price point in your base currency (or let Apple auto-convert), and that price applies when the organisation's ABM account purchases licences.

Where Custom App Pricing diverges from the standard storefront:

• Per-organisation pricing. You can create a separate custom app variant for each buyer. One client gets Tier 10 (~$9.99), another gets Tier 3 (~$2.99). Apple tracks the association in ABM, so you can run genuinely different commercial agreements without managing multiple App Store accounts.
• Free distribution. You can set $0.00 for a custom app — common when you sell access via a separate SaaS contract and want to distribute the binary without collecting payment twice through Apple.
• No promo codes required. The organisation's ABM admin assigns licences directly. There is no consumer-facing redemption flow and no per-download promo code cap.

Understanding how those price tiers map to local currencies matters here, because organisations in different territories will see different converted amounts. If you are pricing for a Japanese enterprise client, for example, the yen tier you select is what appears in their ABM invoice — not a floating conversion. The Apple price tier system explainer covers that mapping in detail.

What you cannot do with Custom App Pricing:

• Set a price below Apple's minimum paid tier (~$0.99) unless the app is completely free
• Offer usage-based, seat-ramped, or dynamic pricing — tiers are fixed at purchase time
• Bypass App Review — every update must be reviewed before organisations can install it

The four buyer profiles that benefit most

Not every B2B scenario justifies the Custom App overhead. Based on Apple's published documentation and publicly reported use cases from independent developers, four buyer profiles tend to generate the clearest return on the setup investment:

Enterprise internal tooling is the most common entry point. If a company wants 500 employees to use your productivity app and does not want those employees manually searching the App Store, ABM-based Custom App distribution solves that in one admin action. The pricing flexibility means you can quote a volume price in your sales process, then configure the matching tier in App Store Connect before the deal closes.

Education is Apple's longest-running Custom App use case, formerly called Volume Purchase Program (VPP). School districts can purchase licences centrally and push them to student iPads without any interaction from the student. Apple School Manager handles reassignment when a student leaves and a new one arrives — something that conventional App Store purchases cannot do cleanly.

Government and healthcare buyers often cannot purchase through a consumer storefront for compliance or procurement policy reasons. A Custom App with ABM gives their IT teams the audit trail and centralised management they need. Phiture's market research has noted that regulated-industry verticals represent a growing share of B2B iOS app revenue, in part because those buyers specifically require managed distribution.

Where Custom App Pricing falls short

Custom App Pricing is not a general-purpose B2B tool. Several scenarios look like a fit on the surface but are not:

Small individual-licence sales. If a freelancer or a five-person team wants to buy your app, steering them through ABM registration adds friction that kills the deal. For buyers under roughly 20 seats, standard App Store pricing with volume promo codes or a separate SaaS subscription model is almost always faster.

Trial-and-convert funnels. Custom Apps bypass the App Store discovery loop, so the organic trial → conversion path does not exist. If your growth model depends on free trials converting to paid, a Custom App variant adds complexity without adding trial volume. See our breakdown of trial length strategies for consumer-oriented subscription flows that work better here.

Frequent pricing experiments. Custom App price changes require updating the App Store Connect configuration and communicating new terms to the buyer organisation — there is no automatic grandfathering or subscription upgrade flow analogous to what Apple provides for consumer subscriptions. If you plan to A/B test price points regularly, the consumer App Store is the right venue. We cover safe pricing experiments in the guide on how to A/B test iOS app prices safely.

Global consumer products. Custom Apps are invisible to the App Store algorithm and cannot earn organic reviews, chart placement, or featuring. If your primary moat is consumer virality, locking your app into a B2B-only distribution channel is a strategic mistake.

Setting it up in App Store Connect

Enabling Custom App distribution for an existing app takes roughly 20 minutes if your account is already configured correctly. Here is the sequence:

1. Enrol in Apple Business Manager or Apple School Manager. This is the buyer's responsibility, not yours — but you need at least one test ABM organisation to verify your setup. Apple's enrolment process for ABM typically takes one to three business days for identity verification.
2. Enable Custom App distribution in App Store Connect. Navigate to your app → App Distribution → Custom App Distribution. Toggle it on. You will be prompted to agree to the Custom App Distribution Agreement if you have not already.
3. Set a price for the custom variant. Under Pricing and Availability, add a custom price for the organisation's ABM ID. You can set different prices for different organisations. Leave the price at $0 if you are billing separately.
4. Submit for review. If this is a new app or a new binary, it must pass App Review before any organisation can redeem it. Existing App Store apps can often add custom distribution without a new review — but any binary change requires a new review cycle.
5. Share the redemption link or token. App Store Connect generates a URL you give to the buyer's ABM admin. They import it into their ABM account and assign licences to their device groups.

If you are already using the App Store Connect API for automated pricing updates, the API supports Custom App management as well — though the B2B pricing endpoints are less commonly documented. The API key setup guide covers the credential configuration that applies here too. If you are managing pricing across many organisations programmatically, you will want API access rather than clicking through App Store Connect per client.

One important operational note: Custom App licences are owned by the organisation, not by individual Apple IDs. That means if a company cancels its ABM account or loses its licences, users lose access — even if they paid for the app. Make sure your enterprise contracts clarify this and that your support process accounts for ABM-related access issues, which are outside your direct control.

Is Custom App Pricing right for you?

Run through four questions before committing to the setup:

1. Does your buyer have an IT department that manages devices? If yes, ABM is likely already in their stack.
2. Is the per-device sale price high enough to justify Apple's 30% cut on top of your sales overhead? A $1.99 per-device price across 50 seats nets you $70 after Apple's share — compare that against your cost of sales.
3. Do you need a different binary or feature set for enterprise buyers, or just a different price? If it is just the price, a discount code or separate SaaS contract may be simpler.
4. Can your buyer actually complete ABM enrolment? Small businesses in some markets find Apple's business verification process slow or difficult. Factor that into your sales cycle.

For developers with a clear enterprise buyer, Custom App Pricing is genuinely powerful: it removes consumer discovery noise, gives IT teams the MDM integration they require, and supports per-organisation commercial terms. For developers who are primarily B2C and exploring B2B as a secondary channel, the overhead usually outweighs the return until deal volume justifies it.

Sources and further reading

• Apple Developer — Custom Apps overview
• Apple Business Manager User Guide — distributing apps to your organisation
• Apple School Manager User Guide — purchasing and distributing apps
• Apple Small Business Program — eligibility and reduced commission details
• RevenueCat — iOS in-app purchase overview (B2B and enterprise context)