Store Rotation Planning: Finding the Right Variants for Daily and Weekly Offers

The store rotation problem

Most free-to-play games rotate the cosmetic store daily or weekly, featuring four to eight variants across categories, rarities and price points. A good rotation brings players back, creates urgency, and gives the whole catalog its turn in the window.

A bad one repeats itself, tilts (six Legendaries on Tuesday, six Commons on Wednesday), or drops a winter skin into July. The liveops team making those calls plans days or weeks ahead and needs the decision to take minutes.

The constraint is information. To pick six items for Tuesday you need to know what is available, when each item last appeared, what balance this rotation needs, and what event is running. Answer that from a spreadsheet or from memory and it holds for about a month.

What a good rotation balances

Rarity distribution

Each rotation should cover the spectrum. Six Legendaries price out the casual player. Six Commons read as a clearance sale. A balanced set looks more like:

• 1 Legendary, the headline that creates the aspiration
• 1 to 2 Epic, premium and attainable
• 2 Rare, the solid middle
• 1 to 2 Uncommon or Common, the accessible entry

A shop window works the same way: the expensive piece front and center, with something at every price behind it.

Category variety

Six helmets leaves the outerwear and accessory players with nothing. Touch three or four categories in each rotation.

In PolyDrobe, filter by status Released to see everything shippable, then work the category filters to spread the selection. The category tree in the sidebar shows the spread at a glance.

Recency

Players notice a repeat. A Legendary jacket featured last Tuesday should not headline this Tuesday. The gap you can afford depends on catalog size, since 50 Released variants leave less room than 500, and most teams hold repeats to two or three weeks apart.

Recency tracking means recording when each variant last appeared. The activity history covers status changes and updates; for rotation history, tags or metadata work better:

• Tag the variant "Last Featured" with the value 2026-04-15
• Or store it in the variant's metadata JSON: {"last_store_rotation": "2026-04-15", "rotation_count": 3}

Next planning session, filter for Released variants and read the "Last Featured" tag to surface the ones players have not seen.

Pricing balance

A rotation running from 2000 to 3000 coins reads narrow and expensive. One running from 200 to 3000 has a door for every spending level.

Check the price on each candidate before you lock the set. Variant prices show on the detail page and in filtered lists, so the comparison is a scan rather than a lookup.

Thematic coherence (optional)

Some rotations are functional: the best available items that meet the balance criteria. Others tell a story. "Stealth Week" runs dark items; "Neon Drop" runs bright colorways. Themed rotations pull harder because players read them as an event.

Search by keyword or tag to assemble one. Full-text search covers variant names, descriptions and tags, so "stealth" or "neon" returns the candidates.

A practical planning workflow

Seven days of rotations at six items each comes to 42 selections. A week of planning runs like this.

Monday: pull the candidate pool

Filter to Released variants. That pool is everything eligible, and its size tells you how much variety you can afford. Three hundred Released variants against 42 selections leaves plenty of room.

Monday: check recency

Read the "Last Featured" tags and pull out the items nobody has seen for three weeks or more. Those are your first picks. Flag the ones featured in the last fortnight so you can rule them out.

Tuesday: draft the week

For each day, pick six variants that hold the balance:

1. Choose the headline first, usually the highest-rarity variant that has been out of the store longest
2. Fill the rarity spread: 1 to 2 Epic, 2 Rare, 1 to 2 Common or Uncommon
3. Cap each category at two items per rotation
4. Check that the price range reaches from accessible to aspirational
5. Apply the theme, if the week has one

Wednesday: review the grid

Read the whole week at once and look for:

• An item appearing twice in seven days
• A day with a rarity tier missing
• A category running three days straight
• A price spread that has gone narrow or absurd

Fix what you find. A structured catalog is what makes the fix cheap, because a replacement candidate is a filter away on rarity, category and recency.

Thursday: lock and update

Finalize the plan, then update the "Last Featured" tag or metadata on every selected variant, so next week's planning starts from accurate data.

Comparing variants before selection

When two candidates match on rarity, category and recency, the choice comes down to look, theme or price strategy.

Open both variant pages and compare thumbnails, textures in the 3D viewer, prices and metadata. With the MCP server connected, ask the assistant instead:

"Compare the Desert Storm Hoodie and the Urban Shadow Hoodie. Show me price, rarity, last featured date and thumbnail for both."

It pulls both records and lays the differences side by side, which saves the tab-switching and the copying.

Automating the queries

With MCP connected, most of the planning turns into questions:

"Find 6 Released variants for tomorrow's store rotation: 1 Legendary, 2 Epic, 2 Rare, 1 Common. All from different categories. None featured in the last 3 weeks."

The assistant runs the filters, checks the recency metadata and hands back a candidate list. The liveops manager reads it, swaps whatever clashes with the theme, and locks the rotation.

The judgment stays with the manager. What the assistant takes is the half-hour of filtering, scrolling and cross-referencing that used to come first.

Tracking rotation performance

Each rotation updates the recency data on the items it featured, and over a season that becomes a dataset:

• How often each variant has been featured
• The average gap between appearances
• Which items are over-rotated, and which have never been in the store at all

Export it to Excel or JSON through Data Exchange and feed your analytics pipeline. Put rotation frequency next to the sales numbers from your backend and you can see which items earn their slot and which ones to retire.

Key takeaways

• A good rotation holds rarity, category, price range and recency together. Drop one and the store reads repetitive, lopsided or stale.
• Record when each variant was last featured in a tag or metadata field, so recency is queryable instead of remembered.
• Plan a week at a time. The grid shows repetition and imbalance while you can still fix them.
• Compare variants directly when several candidates tie on the criteria.
• An assistant on MCP can pre-filter candidates against a multi-part query and cut planning from half an hour to five minutes.
• Export the rotation history and read it against sales data to decide what deserves another slot.