# Does the Number of In-App Purchases You List Affect Conversion?

> A long list of purchase options feels like it should give users more reason to buy. Often it just gives them more reason to pause. Here's the real tradeoff.


**Key points:**
- More purchase options can mean more ways to say yes, but also more time spent comparing before buying anything at all.
- A user facing a long list of similar choices sometimes leaves without picking one.
- A shorter, clearer set of options tends to be faster to weigh and act on.
- There's no fixed right number. It's worth checking which of your current options actually convert before assuming more is better.

A longer list of things to buy sounds like it should mean more chances to make a sale. Sometimes it just means more chances to stall.

## Why more options can work against you

Each extra purchase option adds a bit of real work for the user. Compare this tier against that one. Figure out which bundle actually fits. Weigh a one-time buy against a subscription. That work isn't free. A user who has to do too much of it before buying anything can end up buying nothing at all, closing the screen instead of finishing a comparison they never fully committed to. A shorter list skips most of that friction, since there's simply less to weigh.

| | What tends to happen |
|---|---|
| A few, clearly different options | Faster choices, less time spent comparing |
| Many similar options | More time spent comparing, more chances to stall |

## Why teams keep adding options anyway

Each option on the list got added because it looked fine on its own, a new tier here, a slightly different bundle there, each one easy to defend by itself. The cost of adding them one at a time is easy to miss, since no single addition looks like the problem. It's the full list, not any one option, that ends up slowing a user down. A list built option by option rarely gets looked at as a whole once it's live.

> **Real-world scenario:** A team had grown their purchase options over time, adding a new tier or bundle each time a specific customer request seemed worth meeting. Eventually they had a long list, each option fine on its own, the whole set genuinely too much at a glance. Trimming it down to a few clearly different choices, cutting near-duplicates that mostly competed with each other instead of offering a real difference, led to faster checkouts and more users finishing a purchase instead of browsing and leaving unsure.

## What to actually check before changing anything

Look at which of your current options actually convert, not just which ones exist. An option nobody picks isn't adding real value. It's just adding a line a user has to read past before reaching the one they'll actually choose. Cutting options that rarely convert, or merging ones too close to really differ, is usually safer than trimming the whole list without checking first.

## What to actually do about it

1. **Check conversion by each option, not just your overall purchase rate.** An option nobody picks still adds friction for everyone who has to read past it.
2. **Merge or cut options too close to really differ.** Near-duplicate choices mostly compete with each other instead of adding real value.
3. **Don't assume more options always means more revenue.** A shorter, clearer list sometimes converts better by simply asking less of the user.
4. **Revisit your full list now and then, not just when adding something new.** A list grown one piece at a time rarely gets reviewed as a whole unless you make a point of it.

[AppRankr's ASO Inspector](/aso) checks your listing's real conversion signals, a useful starting point before reworking your purchase options.

