Guideline 3 price verification rejected twice for an auto-renewable subscription, even after confirming and changing the price

Receiving the same request after confirming and changing the price does not necessarily mean the new price is wrong. The unresolved issue could be the intended amount, a mismatch between App Store Connect and the submitted build, or insufficient information about what the subscription provides.

I would stop changing the price until you have reconciled the exact configuration reviewed by Apple. Prepare a one-page evidence sheet containing:

1. The subscription product ID, subscription group, billing duration and current status.
2. The current base-storefront price, its effective date, localized storefront prices, and any scheduled price changes, introductory offers or trials.
3. A screenshot of the complete Subscription Prices section and an export of current and upcoming prices.
4. A physical-device recording of build 119 showing the path from launch to the Pro paywall and the Apple purchase sheet. Include the device storefront and currency.
5. Confirmation that the paywall obtains the localized price from StoreKit’s Product.displayPrice rather than a hard-coded value.
6. A concise list of the recurring features or content unlocked by Pro, so the reviewer can verify what the customer receives for the stated price.

Reply in the Resolution Center for the October 20 rejection, because that keeps the evidence attached to the affected submission. You can place a shorter copy in the App Review notes so the next reviewer sees it when opening the build.

A focused reply could be:

“We confirm that the intended price for product [product ID] is [localized price] per [billing period] in the [storefront] storefront. This is the current effective price in App Store Connect, with [no scheduled price changes / the following scheduled change].

“Build 119 retrieves and displays the localized price directly from StoreKit. The attached recording shows the paywall and Apple purchase sheet on the reviewed device, and the attached reconciliation sheet lists the product configuration, storefront prices, offers and the functionality included with Pro.

“Could you please clarify whether the remaining concern is (a) the intended price amount, (b) a discrepancy between the submitted build and App Store Connect, or (c) the description of the subscription’s value? We will address the specific issue immediately.”

If the recent price change was deliberate, state both the previous and current price with their effective dates. Avoid changing it again merely to trigger another review; first make the configuration and customer-facing presentation internally consistent.

@GetResubmit Thank you for the suggestions. Here’s my experience with the same rejection.

I received the Guideline 3 rejection (“can you confirm the following In-App Purchase product(s) have the correct intended price(s)?”) on three submissions in a row. Confirming the price in the Resolution Center wasn’t enough on its own. What eventually worked:

1. I confirmed the price in the Resolution Center each time, and after the second rejection I also lowered the monthly price, in case the concern was that it looked too high.
2. I explained where the product sits in the lineup. The reviewer seemed to lack context, so I said that Pro is the highest tier, aimed at clinicians with heavy daily use, and that lighter users can choose the Basic or Plus tiers. I also said all tiers are auto-renewable and that each tier’s price and features are shown on the in-app subscription screen before purchase.
3. I updated the subscription descriptions so the value of each tier was clearer.
4. I requested an App Review appointment. After several written rounds, a live conversation settled it. The reviewer said the new price and updated description were no longer a concern.

During the process, one reviewer rejected a build over a Device Capabilities issue, saying the app wouldn’t install on an M3 iPad Air. I couldn’t reproduce it, since I had already installed the same build on an M3 iPad Air through TestFlight. The reviewer in my App Review appointment installed it on both iPhone and iPad without any problem, and he offered to move the app up in the queue. The app was approved the same day, so the appointment really helped in my case.