App Store Connect (July 2026): ‘Add for Review’ for IAPs and subscriptions got simpler
Apple updated App Store Connect’s submission flow so In-App Purchases and subscription items can be submitted directly from their own sections using ‘Add for Review’. It’s not a marketing headline, but it removes a common launch footgun and makes revenue plumbing more testable.
Apple quietly shipped a workflow fix that can save teams from a painful “why isn’t this purchasable?” launch day:
- Source: Apple, App Store Connect release notes (July 15, 2026)
- Read: https://developer.apple.com/help/app-store-connect/release-notes/
What changed
Apple says the submission process for In-App Purchases and subscriptions has been updated.
You can now submit:
- In-App Purchases
- subscriptions
- subscription groups
- non-renewing subscriptions
…directly from the In-App Purchases and Subscriptions sections in App Store Connect using Add for Review.
Why it matters (practically)
IAPs and subscriptions are not “metadata”. They are part of your product surface area.
When the review state is unclear, teams tend to discover problems late:
- the binary ships but the paywall is blocked
- the SKU is created but never reviewed
- the group is correct but the subscription item is not
This update makes the submission step more explicit and more local to where you actually manage the items.
Tiny win
Add one line to your release checklist:
“Are there any new or edited IAPs/subscriptions that need Add for Review separate from the binary?”
Then test your paywall with production config before you start paid spend.
Want help with ASO?
If you want this implemented for your app, check out our services - or run your workflow in APPlyzer.