Storefront setup

IAP price and availability App Review checklist

An approved product can still fail in the app if pricing, availability, product status, or storefront assumptions are wrong. Review needs the same purchase path users will see.

Quick answer

Before submission, confirm each IAP has price, availability, status, metadata, and app-side visibility aligned. Apple App Store Connect guidance says availability can be set by country or region and that an IAP may still be unavailable even after availability is set if status needs action. AppReviewReady interpretation: build a storefront matrix rather than testing only one sandbox account.

01

Create a storefront product matrix

List every IAP product, product ID, type, price, availability regions, status, app screen, and launch dependency. A product can be correct in one storefront and invisible or mispriced in another.

Include whether the app should hide, disable, or explain a product when the user's Apple Account storefront cannot buy it. A blank paywall is weaker than a clear unavailable state.

02

Verify price and copy together

  • Paywall text should match the product duration, entitlement, and displayed price.
  • Localized price, tax, duration, and currency assumptions should be checked in target markets.
  • Temporary price changes should have start, end, and rollback owners.
  • High price points should be reviewed for support, refund, and fraud exposure.
  • Screenshots and custom product pages should not advertise unavailable prices.
03

Treat removal from sale as a user-impacting change

Removing an IAP from sale can affect users who already bought consumables or expect to buy matching add-ons. Apple's guidance calls out user communication considerations when deselecting regions or removing products from sale.

AppReviewReady interpretation: never remove a product only in App Store Connect while leaving active merchandising in the app. Update banners, paywalls, emails, and support macros before the change reaches users.

04

Test purchase visibility and failure states

  1. Load products from StoreKit with a sandbox account for the target storefront.
  2. Test product missing, price unavailable, product removed from sale, and network failure states.
  3. Purchase, cancel, interrupt, refund, and restore where applicable.
  4. Verify server entitlement and client UI agree after every StoreKit result.
  5. Confirm Review Notes identify any product hidden behind account or region state.
05

Prepare IAP availability review notes

This note is useful when the reviewer needs a specific account state or product screen. Keep it focused on reaching the purchase, not on defending the business model.

After launch, revisit the matrix before seasonal campaigns or territory changes. A product hidden from one market can still be referenced by screenshots, push campaigns, email links, or server-side merchandising.

If the app caches product data, verify stale prices are cleared when StoreKit returns a new value or no product. Showing an old price is a conversion and trust problem even when checkout displays the correct App Store sheet.

Copy-ready frameworkAdapt every bracketed field
IAP availability review:
Products: [ids]
Storefronts tested: [list]
Prices: [base and local]
Unavailable behavior: [hide/disable]
Review account state: [eligible]
Sandbox result: [date]
Remove-from-sale plan: [if relevant]
Sources

Primary references checked for this guide

Policy statements above are grounded in the linked Apple documentation. Operational recommendations are AppReviewReady's interpretation and should be tested against your app and the current guideline text.

Put it to work

Check IAP storefront setup

Review price, availability, product status, and purchase states before App Review.

Open the tool