Key points:
- Ending a price at .99 is a well-studied effect in general retail, but its pull inside an app purchase screen is a separate, less settled question.
- A user buying inside an app has often already decided they want it. That’s a different mindset than someone comparing shelf prices.
- Treating .99 pricing as an automatic, guaranteed lift risks skipping the real test that would confirm it in your own app.
- It’s still a fair default, just one worth checking rather than assuming.
A pricing trick borrowed from a grocery aisle gets used on an app purchase screen without much thought about whether the two moments are even alike.
Why the comparison isn’t automatic
Charm pricing, a price just under a round number, has real, long-studied backing in general retail. The classic setting for that research is a shopper scanning shelf prices, comparing options, deciding what to put in a cart. An app purchase screen is a different moment. By the time a user reaches a price inside your app, they’ve usually already decided they want the feature or subscription behind it. That’s a different state of mind than someone still comparing items on a shelf, and it’s not obvious the same trick carries over cleanly.
| What’s actually settled | |
|---|---|
| Charm pricing in general retail | A real, well-studied effect |
| Charm pricing inside an app purchase screen | Less settled, worth testing in your own app |
Why it gets used without much thought anyway
A trick that’s well known elsewhere feels safe to copy without a second look, especially when setting a price already means making enough other calls. Assuming it carries over skips a real question though. Does someone who already wants your feature respond to a price ending the same way a browsing shopper does? Nobody’s settled that for every case, which makes copying the pattern by default more of a guess than settled fact.
Real-world scenario: A team priced a subscription at a round number at launch, then later tested a
.99-ending version against it to see if the classic effect would show up in their own app. The gap between the two was too small to settle anything clearly either way for their case. What they learned wasn’t that charm pricing fails. It was that assuming it would give them the same lift it gets credit for elsewhere, without checking their own purchase flow, would have been a guess dressed up as fact.
What actually settles the question
Testing it in your own app is the only way to know if it’s doing anything for your real users and your real flow. A general effect from elsewhere is a fair starting point, not a confirmed result for you. Treating it as settled either way, assuming it works or assuming it doesn’t, skips the actual test that would tell you something real.
What to actually do about it
- Don’t assume charm pricing carries straight into your app purchase screen. The moment is different enough from a shelf price to be worth its own test, not just a copy.
- Treat a .99 ending as a fair default, not a sure lift. It has real backing elsewhere, just no confirmed result for your app yet.
- Run your own test if the price point really matters to your revenue. That’s the only way to find out what’s actually happening in your real flow.
- Don’t overthink a low-stakes price. If the call doesn’t carry much revenue weight, a fair default is fine without a full test.
AppRankr’s ASO Inspector tracks your listing’s real conversion signals, a useful baseline before testing a pricing change against it.