# App Store pre order: an iOS launch guide > Plan your App Store pre order with Apple's release windows, review steps, billing rules, and launch metrics. Build momentum without promising ranking lifts. - **Author:** Peter Sutarik - **Published:** September 21, 2026 - **Tags:** ios, app-store-pre-orders, app-launch, app-store-connect - **Reading time:** 9 min - **Canonical:** https://trysonar.app/blog/app-store-pre-order-ios --- ## Can an App Store pre order fuel launch-day rankings? An App Store pre order may support launch-day chart visibility, but a keyword-ranking boost remains **an unproven hypothesis**. Apple describes possible chart benefits without quantifying a guaranteed lift. Its search guidance names relevance, downloads, ratings, and reviews among ranking factors. [Apple's pre-order analytics guidance](https://developer.apple.com/help/app-store-connect-analytics/acquisition/pre-orders), [App Store search](https://developer.apple.com/app-store/search/). Pre-orders let customers order before release and receive an automatic download on release day. That gives your launch campaign a destination while customers wait. [Apple's pre-order overview](https://developer.apple.com/app-store/pre-orders/). My recommendation: judge the campaign by orders retained, downloads fulfilled, and whether new users complete the task you promised. Keep chart position and keyword position as separate observations. *By Peter. Apple documentation checked September 21, 2026. Planning checklists are editorial recommendations; examples are hypothetical, not Sonar launch results.* ## Which apps qualify, and how long can pre-orders run? A brand-new app has a **2–180-day** pre-order window; an existing app entering a new region has a **2–365-day** window. Count from pre-order publication. [Apple's timing guidance](https://developer.apple.com/app-store/pre-orders/). |App situation|Pre-order option|Planning implication| |-|-|-| |Never released anywhere|2–180 days after pre-order publication|Choose the release date around a deliverable product.| |Already released elsewhere, new target region|2–365 days after pre-order publication|Plan a regional campaign around local readiness.| |Previously released in the target region|Cannot return to pre-order there|Use an update campaign instead.| Sources: Apple's [pre-order overview](https://developer.apple.com/app-store/pre-orders/) and [regional publishing walkthrough](https://developer.apple.com/videos/play/wwdc2023/10015/). **Hypothetical example:** a subscription tracker available in Canada could use pre-orders to enter the US. It cannot turn its Canadian release back into a pre-order. [Apple's regional walkthrough](https://developer.apple.com/videos/play/wwdc2023/10015/). For your App Store pre order plan, list each intended storefront and its release history before choosing dates. Use the [app soft launch guide](https://trysonar.app/blog/app-soft-launch) to plan what you want to learn from a limited release. Treat Apple's maximum window as an allowance, not a recommended campaign length. ## How to set up an App Store pre order Prepare a reviewable app before publishing the offer. Apple's review guidelines require pre-order submissions to be complete and deliverable, with accurate metadata; a placeholder build is not sufficient. [App Review Guidelines, sections 2.1 and 2.3.11](https://developer.apple.com/app-store/review/guidelines/). ### Prepare the build and submission Attach the intended build to the app version and complete the required metadata before submitting. Apple's submission flow distinguishes **Add for Review** from **Submit for Review**: adding an item alone does not send it to reviewers. [Apple's submission instructions](https://developer.apple.com/help/app-store-connect/manage-submissions-to-app-review/submit-an-app/). Recommended pre-submission check: install the selected build, follow your reviewer instructions, and complete the main advertised task. Verify login access, purchase screens, support links, and the screenshots against that build. Record the build identifier in your launch worksheet so everyone checks the same artifact. ### Configure availability and publish after approval For a first release, open **Pricing and Availability → App Availability → Set Up Availability → Publish as Pre-Order**. Confirm regions and date, submit for review, then publish the approved offer with **Release This Version**. [Apple's setup instructions](https://developer.apple.com/help/app-store-connect/manage-your-apps-availability/publish-for-pre-order/). For regional expansion, open **Manage → Set Up Pre-Order** under App Availability. Select the release date and regions, then confirm; changes can take **24 hours** to appear. [Apple's regional demonstration](https://developer.apple.com/videos/play/wwdc2023/10015/). Use this original planning sequence to coordinate the work: 1. **Verify readiness:** identify the build, reviewer access, and promised functionality. 2. **Check regional eligibility:** record each storefront's release history and intended date. 3. **Complete publication:** confirm the appropriate review and availability actions. 4. **Inspect the public offer:** open the target storefront and check the date, assets, and purchase action. 5. **Begin promotion:** release campaign materials after your public-page check passes. Add these checkpoints to your broader [app launch strategy](https://trysonar.app/blog/app-launch-strategy), with an owner for each decision. Do not substitute a planned publication date for a verified public page. ![Five steps for preparing an iOS pre-order: verify readiness, check regions, publish the offer, inspect the page, and begin promotion.](https://trysonar.app/blog/app-store-pre-order-ios-hero.png) *Verify the public offer in each target storefront before starting promotion.* ## How do updates, date changes, and early release work? During an App Store pre order, releasing an updated version preserves the pre-order download date. The update can reach already-available regions immediately. [Apple's version guidance](https://developer.apple.com/help/app-store-connect/manage-your-apps-availability/publish-for-pre-order/). Revised dates must stay within **180 days** of initial pre-order publication for first releases, or **365 days** for regional expansion. Passed release dates cannot be edited. [Apple's date rules](https://developer.apple.com/help/app-store-connect/manage-your-apps-availability/publish-for-pre-order/). To deliver early, edit the regional pre-order and choose immediate release. Apple demonstrates this separately from changing the date or removing the offer. [Apple's release walkthrough](https://developer.apple.com/videos/play/wwdc2023/10015/). Removing the offer prevents delivery and charging unless you restore it before release. [Apple's removal rules](https://developer.apple.com/help/app-store-connect/manage-your-apps-availability/publish-for-pre-order/). Recommended change-control worksheet: record the affected storefronts, old date, new date, released build, campaign owner, and customer-facing explanation. Before confirming, read the selected regions aloud or ask a teammate to check them against the worksheet. Apple does not notify pre-order customers when you change the date or remove the offer. Communicate those changes through your own channels, and avoid putting an uncertain date into campaign creative. [Apple's pre-order marketing guidance](https://developer.apple.com/app-store/pre-orders/). For a hypothetical delayed launch, update the landing page and queued announcements together. Draft the customer explanation around the unfinished task and the revised expectation. Assign someone to check that the public message matches the decision you recorded. ## What happens to free and paid pre-orders? Both free and paid apps qualify; in-app purchases do not. Paid pre-orders charge at release, at the lower accepted or release price, subject to original terms. [Apple's billing rules](https://developer.apple.com/help/app-store-connect/manage-your-apps-availability/publish-for-pre-order/). At release, Apple notifies customers and automatically downloads the app to the ordering device; other eligible devices depend on automatic-download settings. [Apple's delivery details](https://developer.apple.com/help/app-store-connect/manage-your-apps-availability/publish-for-pre-order/). Treat delivery as the start of the customer journey when planning support and onboarding. Customers can cancel through their App Store account's Pre-Orders area. If a paid purchase fails because of billing, Apple says the customer must update payment information before downloading. [Apple's customer support instructions](https://support.apple.com/en-us/118414). For your App Store pre order messaging, explain the app's paid features separately from the act of ordering it. In a hypothetical free subscription tracker, avoid describing a pre-order as a paid subscription commitment. Ask support to review the landing-page wording and prepare answers about cancellation, availability, and access to premium features. ## How should you measure a pre-order campaign? Measure net orders and fulfilled downloads separately. Apple defines net pre-orders as orders placed minus cancellations, and provides pre-order conversion and resulting download metrics. Its reporting threshold is pre-orders from at least **five individual users**. [Apple's pre-order analytics documentation](https://developer.apple.com/help/app-store-connect-analytics/acquisition/pre-orders). For exported records, Apple's Pre-Order Report distinguishes period totals from cumulative totals and includes country and device fields. Match the reporting period before comparing campaign results. [Apple's report-field reference](https://developer.apple.com/help/app-store-connect/reference/reporting/pre-order-report). Use this recommended measurement worksheet: |Question|Evidence to record|Decision it supports| |-|-|-| |Are people ordering?|Orders and cancellations for the same period|Review the offer and acquisition channel.| |Where is interest coming from?|Territory and source breakdowns|Prioritize regional campaign work.| |Did orders become downloads?|Downloads attributed to pre-orders|Investigate fulfillment separately from acquisition.| |Did people reach value?|Your chosen in-app completion event|Inspect onboarding and product delivery.| |Did visibility change?|Dated keyword and chart observations|Describe movement without assigning causality.| The store measures above follow Apple's [analytics guidance](https://developer.apple.com/help/app-store-connect-analytics/acquisition/pre-orders); the decision column and in-app event are editorial recommendations. **Hypothetical calculation:** 500 orders minus 60 cancellations leaves 440 net pre-orders. Those invented inputs illustrate Apple's [net-order formula](https://developer.apple.com/help/app-store-connect-analytics/acquisition/pre-orders); they do not predict downloads, revenue, or ranking movement. For an App Store pre order review, annotate advertising, press, metadata edits, featuring, and release changes alongside the timeline. If downloads and rank improve together, report that observation without claiming the pre-orders caused it. Use the [App Store Connect analytics guide](https://trysonar.app/blog/app-store-connect-analytics) and [keyword rank tracking workflow](https://trysonar.app/blog/keyword-rank-tracking) to organize those separate views. My recommendation for the launch report: write the conclusion before choosing the chart. In a hypothetical report, “net orders increased after the announcement” is an observation worth investigating; “the announcement improved search rank through pre-orders” needs evidence that separates those effects. Keep the query, storefront, observation date, and acquisition activity attached to each ranking note. If you cannot separate overlapping changes, leave causality unresolved. ## What should be ready before launch day? Your released app must match what customers ordered. Apple requires pre-order apps to be deliverable as submitted and says material changes, including business-model changes, should trigger restarting pre-order sales. [App Review Guidelines, section 2.3.11](https://developer.apple.com/app-store/review/guidelines/). My recommended launch-readiness check focuses on the promise made in the listing: - **Core task:** complete the advertised outcome from a clean installation, including relevant error paths. - **Access:** test sign-in, account recovery, and the distinction between free and paid functionality. - **Operations:** assign someone to monitor service health and incoming support reports during release. - **Measurement:** verify that the intended completion event is recorded and distinguish internal tests from customer activity. - **Communications:** prepare the available-now message and check every destination link before sending. For a hypothetical subscription tracker, define successful activation as creating a renewal reminder and viewing it in the app. Test the path with a new account, then repeat it after denying optional permissions. Make the release decision against the verified task, not the number of people waiting. In the launch worksheet, give each unresolved issue an owner and an explicit decision: fix before release, remove an inaccurate promise, or postpone within the permitted window. Avoid a generic “ready” label that hides an untested purchase flow or an unavailable backend. For a solo launch, I recommend a short handoff note even if you are handing work to yourself. Record the approved build, public listing link, expected release date, unresolved issues, and where support requests will arrive. Add the exact check that would make you pause promotion, such as failing to complete the advertised task on a clean installation. An App Store pre order campaign should end with a product check and a measurement plan. Use the [onboarding guide](https://trysonar.app/blog/app-onboarding-that-protects-day-1-retention) when reviewing the first session. Assess the campaign on fulfilled demand and useful product engagement; keep any ranking benefit outside your guaranteed business case. ## FAQ ### How far ahead can I schedule an App Store pre order? Apple allows **2–180 days** for a brand-new app and **2–365 days** for an existing app entering a new region. Choose the window that matches the app's release history. [Apple's timing guidance](https://developer.apple.com/app-store/pre-orders/). ### Can an existing iOS app accept pre-orders? Yes, in a region where it has never been released. A previously released region cannot return to pre-order status. [Apple's regional publishing explanation](https://developer.apple.com/videos/play/wwdc2023/10015/). ### Does an App Store pre order guarantee higher rankings? No guaranteed lift is established by the cited guidance. Apple's possible chart benefits do not establish a causal keyword-ranking gain for your app. [Apple's pre-order analytics guidance](https://developer.apple.com/help/app-store-connect-analytics/acquisition/pre-orders). ### Can customers cancel before release? Yes, customers can manage cancellations in their account's Pre-Orders area. Include Apple's instructions in your support material rather than treating every recorded order as a committed launch customer. [Apple's cancellation instructions](https://support.apple.com/en-us/118414). *Make keyword research part of your launch checklist with Sonar. [Start free trial](https://trysonar.app/pricing).* --- Source: https://trysonar.app/blog/app-store-pre-order-ios — published by [Sonar](https://trysonar.app), an App Store Optimization platform for keyword research, difficulty analysis, and rank tracking.