App Store 2.3.11 rejection: Pre-order promises
By The Draftbit team · Updated
Sources checked
This guide is for iPhone and iPad apps offered for pre-order whose submitted or released experience differs from the advertised product.
A pre-order is a promise about the app people will receive. Apple’s 2.3.11 requires a complete, deliverable submission and an eventual release that isn’t materially different from what you advertised.
Compare the promised and current versions
Review the pre-order description, screenshots, pricing model, and core features against the build you’re preparing to release. We’d keep a short change list so you can distinguish a corrected bug from a different product or business model.
Address material changes honestly
If the product has changed materially, Apple’s instruction is to restart pre-order sales. Follow the current App Store Connect process and review instructions rather than quietly replacing the advertised offer.
For a smaller mismatch, correct the relevant assets and confirm that the complete app is available for review. A pre-order isn’t a route for submitting a mostly unfinished build.
Test the promised main workflow and verify the saved pre-order information. Explain the change to Apple and confirm which build and offer now match. Avoid promising a release date the app’s readiness can’t support.
Messages this guide can help with
App Store 2.3.11 rejection; app store 2.3.11 denial; Guideline 2.3.11; Pre-order promises
Official sources
We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.
- Apple App Review guideline 2.3.11 Checked 22 September 2026