An app pre-order isn't a sale until launch day, and plenty of them fall away before the charge lands

An app pre-order looks like a sale, and on your dashboard it even counts like one. It is not. When someone pre-orders your app on the App Store or Google Play, no money moves. The buyer is charged nothing until the app launches, and until that moment they can back out for free, no questions asked and no note to you. So the pre-order number you are watching climb is a list of people who said they are interested, not a list of people who have paid. The charge happens later, at release, and by then the list is shorter than it was.

That gap between the pre-order count and the money that actually lands matters most on launch day, which is exactly when you are provisioning servers, promising rewards, and forecasting revenue off the biggest number you have. Here is how an app pre-order works on each store, where the buyers quietly drop off between reserving and paying, and what that shrinkage costs you if you plan as though every pre-order is already a customer.

Why an app pre-order is a promise, not a payment

You can put an app up for pre-order before it is ready, and both stores will collect interest for you. What neither store does is collect money. On the App Store and on Google Play, a pre-order authorizes a future charge and nothing more. The buyer agrees to be billed when the app becomes available, and the store holds that intent until release. No charge clears at the moment of pre-order, so nothing has been earned and nothing has been paid. The practical effect is that a pre-order is the softest commitment a customer can make. It costs them nothing to place and nothing to abandon, which is a fine deal for them and a number you have to read carefully.

What happens between the pre-order and the charge

On the App Store, the charge lands at release and not before

Apple does not bill a pre-order customer when they tap to reserve your paid app. The charge is processed on the release date, when the app downloads to their device, and only then does the pre-order turn into a purchase. You can keep an app available for pre-order for a set window before launch: between 2 and 180 days for a first-time release, and up to 365 days for an app already available in other regions. During that whole window the customer owes you nothing. If you remove the app from pre-order, those customers simply do not receive it and are not charged, unless you list it for pre-order again before release.

On Google Play, the payment is checked about two days early

Google runs the same basic model with one extra step that quietly trims your list. A Google Play buyer is not charged until the release date either, but Google checks their payment method about two days before release. If the card is declined at that check, or if the buyer paid with Google Play balance and does not have enough credit when the app is released, Google cancels the pre-order automatically. The buyer did nothing wrong and hears about it as a notification, and you never see that order convert. So on Google Play your pre-order count is trimmed twice: once by everyone who cancels on their own, and again by the payment checks that fail right before launch.

Where the pre-orders quietly fall away

The free cancellation nobody has to tell you about

The largest leak is the one built into the feature. A customer who pre-orders can cancel at any point before the release date, from their account, for free, and without ever contacting you. There is no refund to process because there was no charge, and there is no signal sent to you because there is nothing to report. The reservation is there one day and gone the next. This is not abuse and it is not friendly fraud. It is the pre-order working exactly as designed, and it means some unknown share of your count is made of people who changed their mind and cost you a headline number rather than a dollar.

The payment failures at the finish line

The second leak lands at the worst possible time, right at release. On Google Play especially, the payment check about two days out and the charge at release together strip out every pre-order attached to a declined card or an underfunded balance. These are people who genuinely meant to buy and still do not convert, because the card on file expired, hit a limit, or came up short. You planned for them as customers all the way through launch, and they fall out in the final hours as cancellations you cannot appeal and did not cause.

What the gap actually costs you

A pre-order that never charges is not a refund. Nothing is clawed back because nothing was ever paid. The cost is quieter, and it shows up in the decisions you make on the strength of a number that is softer than it looks.

Capacity you provision for buyers who never arrive

Launch day is when apps fall over, so you scale up for it. You add server capacity, raise database and storage limits, warm up caches, and budget for the model calls or media processing your app runs per new user. If you size that spend against the raw pre-order count, you are provisioning for a crowd that will be smaller by every free cancellation and every failed payment. The compute you reserved, the storage you allocated, and the third-party API quota you pre-bought are real money, spent whether or not the pre-orders behind them ever became paying installs. Sizing launch capacity off a conservative fraction of the count, not the count itself, is the difference between a tight launch and an expensive one.

Rewards you owe whether they pay or not

Google Play pre-registration is a free signal, not a purchase, and it is often tied to rewards you promise to hand out at launch, in-game currency, an exclusive item, a cosmetic. Those rewards go to people who install when the app goes live, and installing is free. So the reward is a cost you take on for a signup that carries no payment and may never lead to one. Pre-registration is a genuinely useful demand gauge, but treat the rewards as an acquisition cost you pay up front for reach, not as a bill that the pre-registered users are going to settle later.

A slipped launch date can refund the whole book

There is one more cost that is easy to miss until it happens. On Google Play, if your pre-order item is not available three days after its stated release date, Google cancels the transaction and offers the buyer a refund. Miss your own launch window by more than three days and Google does not hold your pre-orders for you, it unwinds them. Every pre-order that would have charged on release day instead becomes a cancelled order and a refund offer, and you are rebuilding your pre-order book from scratch at exactly the moment you were counting on it to convert.

The price rule that can lower what your pre-orderers pay

Both stores protect the buyer on price, and it is worth understanding before you run a pre-order promotion. On the App Store and Google Play alike, a pre-order customer is charged the lower of two numbers: the price they saw when they reserved, and the price on the release date. Raise the price between pre-order and launch and your pre-order customers still pay the lower price they locked in. Drop the price during the pre-order period, say to spark more reservations, and everyone who already pre-ordered at the higher price is charged the new lower one too. The discount is not just for the new reservations you are trying to attract. It reaches back to every buyer already on the list, which is fine if you planned for it and a surprise dent in your launch revenue if you did not.

After launch, a pre-order is just a normal purchase

The special rules end the moment the app is released. Once the pre-order charges and the app downloads, it is an ordinary purchase and it follows the ordinary refund path. On Google Play that means the buyer has the standard 48-hour window in which Google can grant a full refund on its own, and after that they come to you. On the App Store it means the buyer requests a refund through Apple, and Apple decides. So a pre-order does not give a buyer any extra refund rights after launch, and it does not give you any extra protection either. Whatever you already know about refunds on each store applies from release day forward, unchanged.

The moment a pre-order charges at release, it becomes a purchase on the same App Store Server Notifications and Real-time Developer Notifications that RefundHalt already reads. The reservations that never charged leave no trace on those feeds, because no money ever moved. What does show up is the refunds and cancellations that follow launch, so watching those feeds tells you what your pre-order cohort is actually worth once the free part is over and the paying part begins.

The short version

An app pre-order is a reservation, not a sale. On the App Store and Google Play, the buyer pays nothing until the app launches, can cancel for free until then, and on Google Play can be auto-cancelled by a failed payment check about two days before release. Both stores charge the lower of the pre-order and release-day price, so a mid-pre-order discount reaches everyone already on the list. Miss your Google Play launch date by more than three days and the whole book is cancelled and refunded. Count pre-orders as interest, forecast from a conservative fraction of them, and treat the release-day charge as the first moment a pre-order is really worth anything.