Skip to main content
Coal
Log in
Part II Chapter 03 Chapter overview

The outstanding wishlist balance

A post-launch model for separating backlog conversion, removals, and replenishment hidden inside the outstanding wishlist total.

6 min read Updated

Practical question

If the outstanding wishlist balance is flat after launch, does that mean nothing is happening?

Short answer

No. A flat balance can hide substantial purchases and removals offset by equally substantial new additions. Read the balance together with its component flows and acquisition cohorts.

What changes at launch

Sales become the primary commercial outcome

Before launch, a wishlist is a useful proxy for future demand. After launch, the meaning changes: some outstanding wishlists are an old backlog awaiting the right moment, some are new demand, and some will leave through purchase or removal.

Old and new wishlist cohorts can have different purchase probabilities. Discounts, updates, festivals, review milestones, and other commercial events may reactivate different parts of the pool.

Stock and flow

The balance is one frame of a moving system

Opening outstanding wishlists + additions − purchases/conversions − deletions and other removals = closing outstanding wishlists.

Model terms

Keep stock, flows, and cohorts separate

Stock metric
Outstanding wishlists at one point in time.
Flow metric
Additions, purchases or conversions, deletions, and other removals during a period.
Cohort metric
The eventual and time-to-purchase behavior of wishlists acquired in a period or around an event.
Depletion
Reduction of an existing cohort through conversion or removal.
Replenishment
New post-launch wishlist demand entering the pool.
Reactivation
A commercial event causing older outstanding wishlists to purchase.

Worked example

A stable balance can contain healthy conversion and healthy replenishment

A game opens the week with 50,000 outstanding wishlists. It gains 2,400 new wishlists, while 1,800 purchase and 600 are deleted or otherwise removed. The closing balance is still 50,000.

Illustrative weekly wishlist reconciliation
ComponentWishlistsRole
Opening balance50,000Stock at week start
Additions+2,400Replenishment flow
Purchases/conversions−1,800Depletion flow
Deletions/other removals−600Depletion flow
Closing balance50,000Stock at week end
Inferred A stable balance is compatible with several very different underlying systems; the components determine the interpretation.

Manual workflow

Reconcile the pool once per reporting period

  1. Record the opening outstanding balance.
  2. Export additions, purchases or conversions, and deletions for the same dates.
  3. Calculate the expected closing balance and compare it with the reported stock.
  4. Annotate discounts, updates, festivals, and other commercial events.
  5. Split by acquisition cohort when the available report supports it.
  6. Describe depletion, replenishment, and reactivation separately before judging health.

Interpretation limit

A growing balance is not automatically healthy

Growth may reflect strong replenishment, weak conversion, or both. A shrinking balance may reflect successful backlog conversion, weak acquisition, removals, or several effects at once. Compare component flows, sales, event timing, and cohorts before choosing an action.

Sources and navigation

Further reading

Valve · Steamworks Documentation

Wishlist Reporting

The primary source for additions, purchases, deletions, daily reporting delay, regional data, and the MonthCohort export field. The stock-and-flow interpretation in this guide is an analytical model built on those reported components.