In-game store design: a curated shop, not a junk drawer

Most in-game stores are a wall of items. Currency packs, a few bundles, a battle pass, a cosmetic shelf, all stacked in a scrolling list a player has to dig through. It looks complete, and it converts badly. The store is the single screen where a player decides whether to spend, and treating it as a catalog instead of a conversion surface leaves money on the table every day.

The studios that monetize well in 2026 stopped thinking of the store as a list of everything for sale. They think of it as a curated shop — a small, intentional set of things presented to this player, at this point in their progression, for a reason. The difference is not cosmetic. It changes what converts.

The store is a conversion surface, not an inventory page

A conversion surface has one job: turn intent into a purchase with as little friction as possible. An inventory page has a different job: list what exists. Most in-game stores are built as the second and judged as if they were the first.

The tell is the scroll. If a player has to scroll past six things they will never buy to find the one thing relevant to them, the store is working against itself. Every irrelevant item is a small reason to give up, and giving up is free. A player who closes the store without buying has cost you nothing visible, which is exactly why this failure is so easy to ignore. There is no error in the logs. The player just leaves.

A curated shop inverts the layout. Instead of showing everything and hoping the player finds the right thing, it shows the few things that fit where the player is right now, and pushes the rest behind a tap. The player who wants the long catalog can still find it. But the default view is built to convert, not to enumerate.

Match the offer to the player's stage

The strongest principle in modern store design is that the right offer depends on who is looking. A player three days into your game and a player three months in are not in the same shop, even if the underlying items are identical.

Early on, the store should feel like starter momentum. A new player is trying to decide whether your game is worth investing in, and a first bundle that accelerates their early progress answers that question in their favor. It is not the place for a high-tier pack or a deep strategic purchase — those mean nothing to someone who has not yet committed.

Later, the same player is making different decisions. They understand the systems, they know what they are short on, and a well-chosen bundle now reads as a strategic choice rather than a leg-up. A struggling player at a difficulty wall wants the thing that gets them past it. A player who collects wants the limited cosmetic that completes a set. These are different shops for different intents, and showing all of them to everyone dilutes each one.

This is where the curated-shop idea becomes operational. You are not building one store. You are building a store that knows the difference between a player who needs help getting unstuck and a player who is hunting for the next collectible, and presents accordingly. Bundles that match player stage convert; bundles that ignore it become noise the player learns to scroll past.

Design the store after the game, not before

One of the most common and most expensive mistakes is designing the store first. A team decides on price points and pack contents early, then builds progression and difficulty around them. The result is a store that feels bolted on, because it was.

High-performing games reverse the order. They design the progression systems, the difficulty curve, and the reward pacing first, and only then insert purchases where they feel natural. The store ends up positioned at the moments where a player genuinely wants something — short on currency before an upgrade, stuck at a wall, close to completing a collection — rather than at arbitrary points the economy was never built to support.

The reason this matters for the store screen itself is that natural purchase moments are where curation has something to work with. If your game has a real progression wall at a known point, the store can meet the player there with a relevant offer. If the economy was designed backwards from a price sheet, there is no such moment to meet, and the store is left shouting generic packs at everyone. You cannot curate around purchase intent that the game design never created.

Bundles, pricing, and the cost of clutter

Bundles are the clearest example of why curation beats enumeration. A well-built bundle converts better than the same items sold separately, because it does the player's math for them — here is a set of things that go together, at a price that reads as a deal. Bundles aligned with a player's intent moment convert meaningfully better than standalone items, which is exactly why a curated shop leans on a small number of well-chosen bundles rather than a long shelf of individual SKUs.

But a bundle only works if it is the right bundle for the player seeing it. A starter bundle shown to a three-month veteran is clutter. A high-tier pack shown to a day-one player is clutter. The bundle mechanic is not magic — it is a way to package relevance, and packaging the wrong thing relevantly still converts nothing.

The honest trade-off is that curation requires you to decide what not to show, and that feels risky. A team worries that hiding an item means losing the sale to the one player who wanted it. In practice the opposite is usually true: showing fewer, more relevant things raises conversion across the base more than the occasional hidden-item sale costs you. A shop is a set of decisions about what belongs in front of this player. A junk drawer is the refusal to make those decisions, pushed onto the player to sort out — and most players do not sort. They leave.

What a curated store needs underneath it

A store that adapts to player stage and intent needs to know two things in the moment: who this player is, and what they are likely to respond to right now. That is the hard part, and it is why most stores stay static — it is easier to show everyone the same list than to compute the right shop per player.

The signals that drive a good curated store are the same behavioural ones that predict spending generally: where a player is in progression, what they are short on, whether they are stuck, what they have engaged with before. A store that reads these and assembles the right small set of offers per player is doing real-time curation. A store that shows a fixed list is leaving the curation to the player, who will not do it.

This is the part that is genuinely hard to build and easy to underestimate. Pulling the right offer for the right player at the moment they open the store — and changing it as the player's situation changes — is a system, not a screen. See how GameMantra assembles a per-player offer in real time → so the store a player opens reflects where they actually are, not a catalog of everything you sell.

The store is not a place to list your products. It is the one screen where a player decides to spend, and it converts in proportion to how well it understands the person looking at it. Build it as a shop, not a drawer.