Consumable vs Non-Consumable In-App Purchases Explained

Consumable in-app purchases are items that get used up and need to be bought again. Virtual currencies, energy packs, extra lives, and power-ups all fall into this category. Once a user spends their coins or uses their boost, it is gone, and they can purchase more if they want. Non-consumable purchases work differently. These are permanent unlocks tied to a user's account indefinitely. Ad removal is the most common example, and it is more widespread than most people realize: games with ad removal account for 90% of all mobile games. Once a user buys a non-consumable, they own it permanently and can restore it across devices without paying again. The distinction is not just definitional; it determines how Apple's ecosystem handles receipts, device syncing, and restoration.

Apple's App Store handles consumables and non-consumables in fundamentally different ways, and understanding this is critical before you write any purchase logic. Consumable items appear in the receipt once, are not synced across devices, and cannot be restored. If a user reinstalls your app or switches phones, their consumable inventory does not come back. That is by design, because consumables are meant to be spent and repurchased. Non-consumable items, on the other hand, are permanently associated with the user's App Store account. Apple's built-in restoration system handles syncing them across all of a user's devices automatically. Misclassifying a purchase type has real consequences: if you mark a consumable as non-consumable, Apple's system detects the mismatch and can trigger automatic refunds, since the platform expects the item to reset upon use.

Virtual currencies are one of the most frequently misclassified purchase types. The key question is whether the currency gets spent and depleted or whether it unlocks something permanent. Purchasing 100 in-game coins for $0.99 is consumable because those coins get spent during gameplay and the user buys more when they run out. But if buying a currency package unlocked a permanent status, like a VIP badge or an account-level feature, that would be non-consumable. The determining factor is not what the item is called but how it behaves: does it deplete with use, or does it persist indefinitely? Getting this right from the start prevents a cascade of issues downstream, from incorrect receipt handling to users who feel they were charged unfairly.

Consumable purchases require server-side tracking to manage inventory accurately and prevent manipulation. Storing consumable state locally on the device creates a vulnerability, since local storage can be altered by users with the right tools. A proper implementation tracks how many of an item a user has, decrements that count when the item is used, and validates purchases server-side before granting the item. This is especially important for items like energy packs or resource bundles in games where economy balance directly affects engagement and revenue. The technical overhead is real, but so is the revenue risk of skipping it.

Non-consumable purchases are simpler to implement because Apple handles most of the heavy lifting. Your job is to set a persistent flag on the user's account when the purchase is made and check that flag wherever the feature is gated. Apple's restoration system takes care of syncing the purchase across devices, so users who reinstall the app or upgrade their phone get their purchase back without contacting support. The most important thing is making sure your restoration flow works correctly before you ship. Users who lose access to something they paid for permanently are among the most vocal sources of negative reviews.

Beyond the technical implementation, the consumable versus non-consumable distinction needs to be communicated clearly to users. People expect consumables to run out; that is the implicit contract when they buy energy refills or extra lives. They expect non-consumables to last forever; that is the implicit contract when they pay to remove ads. When the experience does not match the expectation, users feel misled regardless of what the terms say. A streamlined, transparent purchase process that makes the nature of each item obvious at the point of sale reduces friction, increases conversion, and reduces the likelihood of disputes or refund requests. Developers who get this balance right, using consumables for frequent low-value transactions and non-consumables for high-value permanent features, consistently see stronger retention and more stable revenue over time.