Apple’s “not submitted for review” wording confuses founders because it sounds like a rejection of the product itself. It usually is not. It means the purchase record exists in App Store Connect, complete and untouched, but it never rode along with the app version that actually went to a reviewer.
Open the draft submission before you touch anything else. If the product is missing from that draft, add it there, not by editing the app. Upload a new build only if the current submission is already locked or the binary genuinely needs a code change.
The workflow below was checked against App Review Guidelines and Submit an In-App Purchase on 4 August 2026. The first source controls the rule or workflow; the second supports the article-specific implementation boundary.
The short version
- Open each purchase item and resolve incomplete metadata.
- Confirm the intended product shows a review-ready state.
- Open the draft submission and verify the app version is present.
- Add every intended product individually with Apple’s current Add for Review flow.
- Include a new subscription group when Apple’s current help requires it.
This failure sits inside the broader iOS subscription and in-app purchase review guide; come back to that pillar once the item itself is fixed and you want to check the rest of the release chain.
Why a finished product can still be invisible to review
Creating a product record in Monetization and submitting it to App Review are two separate actions, and App Store Connect does not force one to trigger the other. You can complete every field on a subscription or in-app purchase, save it, and still have a reviewer receive an app version that never references it. From the developer’s side the product looks done. From the reviewer’s side, it does not exist.
This gap shows up most often after a product was created late in a release cycle, after a resubmission that reused an old draft, or when a team assumed that “Ready to Submit” on the product page meant it had already joined the app’s submission. It had not.
Decide whether this needs a new build at all
In most cases, no. If the draft submission that contains your app version can still be edited, add the missing product to it and resubmit; the binary you already tested does not change. A new build is only necessary when the submission is locked and cannot accept edits, when Apple’s message points at the binary itself rather than at submission assembly, or when your paywall code also needs a fix. Do not bump the build number out of habit when the real gap is a missing line item in a draft.
Walk the current Add for Review flow
Apple’s help page for submitting an in-app purchase is the reference, not a screenshot from a prior release; the interface and its labels move over time. Open the product record, choose the current Add for Review action, and confirm it lands in the same draft as the related app version rather than a separate one. Before you submit, reopen that draft and count the items present against the list you intended to ship. A subscription that needs its own group, rather than joining an existing one, follows a distinct path in the same flow: Apple’s current instructions describe when a new group is required and how to attach it correctly.
Write the fix into your Review Notes plainly
Tell the reviewer, in one sentence, that this submission includes the purchase item that was missing before. Name the exact product identifier and give the shortest tap path from launch to the paywall. Notes cannot repair an item that is still absent, but they remove any doubt about whether this attempt actually contains the fix, which matters if the same reviewer sees the resubmission.
The next action depends on what is actually missing
| What you find | Next action | New build? |
|---|---|---|
| The product is complete but was never added to the draft submission | Add it with Apple’s current Add for Review flow and recheck the item count | No |
| One duration or tier was added while a sibling plan was left out | Add the missing plan to the same subscription group and draft | No |
| The product cannot be added because localization or review information is incomplete | Finish the missing fields, then add it to the draft | No |
| The app version itself needs a different identifier, purchase call, or UI | Correct the code, test the archive, upload a new build | Yes |
Do not delete and recreate a product that is otherwise complete just because it was left out of one submission; that trades a simple linkage fix for new identifiers and fresh entitlement work.
Patterns that keep causing this exact message
- The product was created and finished, then never added to the app version’s draft.
- One plan of a multi-tier subscription was added while its sibling was forgotten.
- A team resubmitted using an older draft that predated the product’s creation.
- The product could not be added because a required field, often localization, was still incomplete.
These are diagnostic patterns from the maintained AppRejectKit subscription corpus, not a rejection-rate statistic; Apple’s current documentation remains the actual policy source.
Do not let this turn into a bigger change
Resist rotating the product identifier or recreating the record once you know the cause is submission linkage, not the product itself. A new identifier means new App Store Connect configuration and a new entitlement mapping in your code, for a problem that a single Add for Review action would have solved. If the same app also has a subscription or group stuck in a pending status rather than simply missing, that is a related but distinct problem covered in subscription stuck in Waiting for Review.
Verification note: this diagnosis was checked against Apple’s current in-app purchase submission help on 4 August 2026. App Store Connect’s labels and the exact submission flow can change, so confirm against the live interface before you resubmit.
FAQ about in-app purchase not submitted for review
My purchase was approved before. Why is it saying “not submitted” now?
A prior approval is tied to a specific app version and submission. If a later version was assembled from a draft that predates the product, or the product was recreated, the new submission has to include it again explicitly. Past approval does not carry forward automatically.
Can I add the missing product without waiting for Apple to reject the current app version again?
Yes, if the draft that holds your app version is still editable. Add the product to that same draft and resubmit rather than waiting for a rejection to force the issue.
Will resubmitting the product reset anything about its configuration?
No. Adding an existing, complete product to a draft submission does not change its identifier, price, or history. It only changes which app version’s review includes it.
What if I do not see an Add for Review option on the product?
That usually means the product itself is incomplete: check localization, pricing, and review information first. An incomplete product cannot be added to a submission regardless of how the app version looks.
Conclusion
Fix complete product metadata, add the purchase item to the same draft submission as the app version, and resubmit. Upload a new build only when the current submission cannot be edited or the binary itself must change.
This is a submission-assembly problem in nearly every case; treat it as one before you touch the app.
Sources and references
- App Review Guidelines: accessed 4 August 2026.
- Submit an In-App Purchase: accessed 4 August 2026.
- Submit an app: accessed 4 August 2026.