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

The store rotation problem

Most free-to-play games rotate their cosmetic store on a daily or weekly cadence. Each rotation features a curated selection of items — usually 4-8 variants spanning different categories, rarities, and price points. Done well, rotations drive repeat visits, create urgency ("buy it now or wait weeks for it to return"), and ensure the full catalog gets exposure over time.

Done poorly, rotations feel repetitive (the same items keep appearing), unbalanced (all Legendaries one day, all Commons the next), or poorly timed (a winter skin featured in July). The liveops team responsible for rotations needs to make these decisions quickly and consistently, often planning days or weeks of rotations in advance.

The bottleneck is almost always information access. To pick the right 6 items for Tuesday's store, you need to know: What is available? When was each item last featured? What rarity and price balance does this rotation need? What theme or event is running? Answering these questions from a spreadsheet or from memory does not scale past the first few weeks.

Selection criteria for a good rotation

A well-constructed store rotation balances several dimensions simultaneously:

Rarity distribution

Each rotation should span the rarity spectrum. A rotation with 6 Legendary items prices out casual players. A rotation with 6 Commons feels like a clearance sale. A balanced rotation might include:

• 1 Legendary (the headline item, creates aspiration)
• 1-2 Epic (premium but attainable)
• 2 Rare (solid mid-tier options)
• 1-2 Uncommon or Common (accessible entry points)

This mirrors how physical retail works — a store window shows the premium item but also displays items at every price point.

Category variety

A rotation should span categories so different player preferences are represented. If all 6 items are helmets, players who want outerwear or accessories see nothing for them. A balanced rotation touches 3-4 different categories.

In PolyDrobe, filter the catalog by status "Released" to see all shippable variants, then use category filters to ensure your selection spans multiple groups. The category tree in the project sidebar makes this visual.

Recency

Players notice when the same items keep appearing. A Legendary jacket that was in the store last Tuesday should not be back this Tuesday. The minimum gap depends on your catalog size — a game with 50 Released variants has less room than one with 500 — but most teams aim for at least 2-3 weeks between repeat appearances for any individual variant.

Tracking recency requires knowing when each variant was last featured. PolyDrobe's activity history shows every status change and update, but for dedicated rotation tracking, the most practical approach is using tags or metadata:

• Tag a variant with "Last Featured" and a date value: tag "Last Featured", value "2026-04-15"
• Or store rotation history in the variant's metadata JSON field: {"last_store_rotation": "2026-04-15", "rotation_count": 3}

When planning the next rotation, filter for Released variants and sort or search by the "Last Featured" tag to find items that have not appeared recently.

Pricing balance

The total price range of a rotation matters. If the cheapest item is 2000 coins and the most expensive is 3000, the rotation feels narrow and expensive. If the range spans 200 to 3000, there is something for every spending level.

Check prices on each candidate variant before finalizing the rotation. In PolyDrobe, variant prices are visible on the detail page and in filtered list views, so comparing prices across candidates is a quick scan rather than a spreadsheet lookup.

Thematic coherence (optional)

Some rotations are purely functional — the best available items that meet the balance criteria. Others are thematic: "Stealth Week" featuring dark-themed items, or "Neon Drop" featuring bright colorways. Thematic rotations drive stronger engagement because they tell a story.

If you use thematic rotations, search the catalog by keyword or tag to find items that fit. PolyDrobe's full-text search covers variant names, descriptions, and tags, so searching "stealth" or "neon" returns relevant candidates quickly.

A practical rotation planning workflow

Here is a step-by-step workflow for planning a week of daily rotations (7 days, 6 items each = 42 variant selections):

Monday: Pull the candidate pool

Filter the catalog to Released variants only. This is your candidate pool — everything eligible for store rotation. Note the total count. If you have 300 Released variants and need 42 selections this week, you have plenty of room for variety.

Monday: Check recency

Review the "Last Featured" tags or metadata to identify items that have not been in the store for 3+ weeks. These are your high-priority candidates — players have not seen them recently, and featuring them keeps the rotation feeling fresh.

Also flag items that were featured recently (last 1-2 weeks) so you can exclude them.

Tuesday: Draft the week

For each day, select 6 variants that satisfy the balance criteria:

1. Pick the headline item first — usually the highest-rarity variant that has not been featured recently
2. Fill in the rarity distribution: 1-2 Epic, 2 Rare, 1-2 Common/Uncommon
3. Check category variety — no more than 2 items from the same category per rotation
4. Verify price range spans from accessible to aspirational
5. Apply a theme if using thematic rotations

Wednesday: Review and adjust

Review the full week as a grid. Look for:

• The same item appearing twice in the same week
• A rarity tier missing entirely from any single day
• A category dominating multiple days in a row
• Price distributions that are too narrow or too wide

Adjust as needed. This is where a structured catalog pays off — you can quickly find replacement candidates by filtering for the specific rarity, category, and recency criteria you need.

Thursday: Lock and update

Finalize the rotation plan. Update the "Last Featured" tag or metadata on every selected variant so next week's planning starts with accurate recency data.

Comparing variants before selection

When two variants meet the same criteria — same rarity, same category, similar recency — the tiebreaker often comes down to visual appeal, thematic fit, or pricing strategy. This is where variant comparison is valuable.

In PolyDrobe, open both variant detail pages and compare thumbnails, textures (using the 3D viewer if a mesh is attached), prices, and metadata side by side. For teams using the MCP server, ask an AI assistant to pull up both variants and summarize the differences:

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

The assistant retrieves both records and presents a comparison, saving the tab-switching and manual data gathering.

Automating rotation queries with AI

For teams with PolyDrobe's MCP server connected to an AI assistant, many rotation planning queries become natural language questions:

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

The assistant queries the catalog with the appropriate filters, checks recency metadata, and returns a candidate list that meets all criteria. The liveops manager reviews, swaps out any items that do not fit thematically, and locks the rotation.

This does not replace human judgment — the liveops manager still decides what goes into the store. It replaces the 30 minutes of filtering, scrolling, and cross-referencing that precedes the decision.

Tracking rotation performance

After each rotation, the items that were featured are tagged with updated recency data. Over time, this builds a dataset:

• How many times each variant has been featured
• The average gap between features
• Which items are over-rotated (appearing too often) vs. under-rotated (rarely or never featured)

Export this data to Excel or JSON via PolyDrobe's Data Exchange feature and feed it into your analytics pipeline. Combine rotation frequency with sales data (from your game backend) to identify which items perform best in rotation and which are not worth re-featuring.

Key takeaways

• Good store rotations balance rarity, category, price range, and recency. Failing on any dimension makes the rotation feel repetitive, unbalanced, or stale.
• Track when each variant was last featured using tags or metadata so recency is a queryable field, not tribal knowledge.
• Plan rotations in weekly batches rather than day-by-day — this catches repetition and imbalance before it reaches the store.
• Use variant comparison to make tiebreaker decisions when multiple candidates meet the same criteria.
• AI agents connected via MCP can pre-filter candidates based on complex multi-criteria queries, reducing planning time from 30 minutes to 5.
• Export rotation history for performance analysis — combine feature frequency with sales data to optimize future rotations.