Architecture · Official sources first
Apple Universal Purchase, without the ambiguity
Understand how one App Store record connects iPhone, iPad, and Mac apps, what must match, what stays platform-specific, and which decisions cannot be undone.
In brief
Universal Purchase uses one App Store Connect app record for related platform versions. The platforms share the app record and commerce relationship, while each platform ships its own build and can have platform-specific product-page information. Plan it before creating separate records: existing records cannot be merged.
On this page
One storefront relationship, multiple platform deliveries
Universal Purchase connects related Apple-platform apps through one App Store Connect record. Customers can discover the platform versions as one app relationship, and eligible in-app purchases can be shared. It does not mean one binary, one screenshot set, or one undifferentiated product experience.
Make the decisions that cannot be repaired later
- 01Confirm the customer promise
Decide whether one purchase should unlock the related iPhone, iPad, and Mac experiences.
- 02Use the existing app record
Add macOS to the iOS app record when building the Universal Purchase relationship.
- 03Align the bundle identifier
Apple requires the same bundle ID for the related platform versions.
- 04Avoid separate records
Existing records cannot be merged later. Stop before creating a second record if one relationship is the goal.
- 05Plan the durable result
Once at least two platform versions are approved, Apple says the Universal Purchase remains and a platform version cannot be removed.
Know what is shared and what deserves platform work
App identity
- Shared record
- Apple ID, SKU, bundle ID, app-level name and subtitle
- Platform delivery
- Separate target, build, version, and release cadence
Store page
- Shared context
- Brand identity and the product relationship
- Platform proof
- Description, promotional text, screenshots, previews, and version details should fit the device
Trust
- App level
- Privacy answers must cover all platform behavior
- Per device
- Accessibility support is assessed and declared by device
When macOS is added, Apple transfers most existing app information but calls out promotional text, description, and screenshots as information to supply for the new platform. Treat that as a useful minimum, not permission to leave the Mac page generic.
Plan purchases, existing users, and replacement behavior
In-app purchases configured under one app can be shared across its iOS and macOS platform versions. That continuity depends on your implementation: verify product identifiers, receipt and transaction handling, account state, restoration, family or subscription behavior, and the copy explaining access.
Universal Purchase implementation checklist
- 01Record
Add macOS to the existing record; verify Apple ID, SKU, bundle ID, roles, agreements, and availability.
- 02Builds
Use separate targets and platform-appropriate versions; keep an internal release map when numbers diverge.
- 03Commerce
Exercise purchase, restore, subscription status, refunds, and account access on every platform.
- 04Data
Test sync, migration, local storage, file ownership, conflicts, and offline recovery for existing users.
- 05Listings
Write and design proof for each device rather than duplicating the iPhone product page.
- 06Review
Submit platform versions separately and give reviewers a reproducible cross-platform test path.
- 07Support
Prepare help content and diagnostics that identify platform, version, build, purchase state, and migration path.