Apple: App Store Connect now lets you submit IAPs and subscriptions via ‘Add for Review’

Original source: Apple - “Submit an In-App Purchase” help doc (linked from the Jul 15, 2026 App Store Connect release notes)

• https://developer.apple.com/help/app-store-connect/manage-submissions-to-app-review/submit-an-in-app-purchase

The headline

IAP and subscription items can now be sent to review from the IAP/Subscriptions sections, without bundling everything into a full app submission.

Apple’s release notes say you can submit:

• In-App Purchases,
• subscriptions,
• subscription groups,
• non-renewing subscriptions,

directly via Add for Review.

Why this matters (practically)

This is small UX, but it reduces “review plumbing” friction in the exact places teams tend to accumulate risk:

• Launch checklists: fewer manual steps means fewer missed switches before a campaign.
• Ops ownership: marketing, product, and revenue teams can coordinate IAP changes without treating an app binary as the bottleneck.
• Fewer accidental coupling failures: if your IAP metadata is blocked, you are less likely to derail an otherwise-ready app update.

What to double-check

• Change management: IAP changes still affect purchase UX, receipts, and support volume. The easier the submit button is, the easier it is to ship a breaking pricing/entitlement edge.
• Sequence clarity: if your launch depends on both a binary and a paywall/IAP change, document the order (what needs to be approved first, what can be staged).

Tiny win

Write a one-page “revenue release runbook” that answers:

1. Where IAP/subscription changes get submitted (now: the IAP/Subscriptions sections).
2. Who owns the final review click.
3. What gets sanity-checked after approval (paywall display, purchase, restore, server entitlement, CRM receipts).

Read the original: https://developer.apple.com/help/app-store-connect/manage-submissions-to-app-review/submit-an-in-app-purchase