How to Build a Wishlist Sale Tracker (Spreadsheet Template + Step‑by‑Step Workflow)

Overview

Sale events are easier to navigate when you decide your rules before the discounts appear. A tracker helps you answer practical questions such as: Is this the lowest price I have seen? Does another storefront offer a better final cost? Will a coupon apply? Does the version include the content I want? Is the purchase tied to a launcher, DRM system, or key region that matters to me?

The goal is not to record every available deal. It is to create a short, consistent list of purchases that are both good value and likely to be played. A spreadsheet is useful because it keeps price history, store preferences, and personal priorities in the same place. It also makes the process repeatable before a major seasonal sale, a publisher promotion, or a bundle launch.

For broader storefront context, compare this workflow with our PC game price comparison guide. If you are considering a bundle rather than an individual game, the Humble and Fanatical bundle value guide covers a similar decision from a bundle perspective.

How to estimate

Start by creating a spreadsheet with one row for each game and one column for each decision-making input. The following header row can be pasted into Google Sheets, Excel, or another spreadsheet application:

Game,Edition,Store,Store URL,Current Listed Price,Historical Low,Sale Price Date,Region/Currency,Tax or Fee Estimate,Coupon Value,Final Estimated Cost,DRM or Launcher,Key Notes,Bundle Status,Your Target Price,Priority,Hours Expected,Buy Decision,Last Checked,Notes

Use one row per store listing when the same game is available in several places. This makes comparison clearer than placing multiple prices in a single cell. For example, the standard edition on Steam and the same edition on GOG should be separate rows because the launcher, DRM, refund terms, coupons, and final checkout price may differ.

A simple cost formula

Estimate the amount you will actually pay rather than comparing only the large sale percentage. A basic formula is:

Final estimated cost = listed price + taxes and fees − usable coupon value

If your spreadsheet uses columns E through J from the header above, a formula for the final estimated cost could be:

=E2+I2-J2

Enter zero when a field does not apply. Keep taxes and fees as estimates until checkout because the final amount can depend on your location, currency, payment method, and the store’s checkout process. If a coupon has conditions, enter its value only when the game qualifies and the coupon can be used on that purchase.

Measure the discount against your own threshold

Do not treat the historical low as an automatic buy signal. Instead, compare the final estimated cost with your target price:

=IF(K2<=O2,"Buy candidate","Wait or review")

Here, K is the final estimated cost and O is your target price. You can add a second check for priority, backlog, or expected play time. A game that reaches a historical low but has low personal priority may still be less useful than a slightly more expensive game you expect to start immediately.

Populate the tracker efficiently

1. Export or copy your wishlist items from each storefront where you use a wishlist. If a store does not provide a convenient export, enter the game name and listing URL manually.
2. Standardize titles. Remove edition labels from the main game name when possible, then record Standard, Deluxe, Complete, or another edition in the Edition column.
3. Check the exact product page before recording a price. Search results, bundles, downloadable content, and base games can look similar.
4. Record the store, region, and currency beside the price. Do not compare an unconverted price with a local checkout total.
5. Check whether the listing is a direct purchase, a redeemable key, or a bundle entitlement. Add the relevant detail to Key Notes or Bundle Status.
6. Record the date in Last Checked. Prices and promotions change, so an undated number quickly loses value.

For additional tracking ideas, see how to track PC game prices and identify a wishlist low. The tracker here is designed to complement, not replace, a store’s own wishlist and sale notifications.

Inputs and assumptions

A useful tracker separates facts from personal assumptions. The listed price and store URL are observed inputs. Your target price, priority, and expected hours are personal rules. Keeping both types of information visible prevents a sale label from making the decision for you.

Store and purchase details

• Store: Record the storefront that will process the purchase, such as Steam, Epic Games Store, GOG, Humble, Fanatical, or Green Man Gaming.
• DRM or launcher: Note whether the game requires a particular launcher or has a DRM detail that affects your preference.
• Key notes: For key retailers, record the activation platform, stated region, seller or publisher information where available, and any redemption restrictions shown on the listing.
• Edition: Compare like with like. A lower-priced standard edition is not necessarily cheaper value if another listing includes expansions you intended to buy.
• Region and currency: Use the currency in which you will pay, or clearly record the conversion rate and conversion date if you are comparing currencies.

When buying from a key retailer, use the checks in our guide to legitimate game key sites. A low number in the Current Listed Price column is not enough if the listing’s activation details are unclear.

Historical lows and benchmarks

Historical Low should mean the lowest verified price you have chosen to track, not an unconfirmed number copied from a different edition or region. If you use a price-history service or a store record, note its source and the date in the Notes column. If you cannot verify the number, label it as an estimate rather than presenting it as a fact.

Your Target Price can be equal to the historical low, but it does not have to be. You might set a higher threshold for a game you want to play soon, or a lower threshold for a game already sitting in a large backlog. The important point is consistency: apply the same rule to every row during the sale.

Priority and purchase readiness

Use a simple priority scale such as High, Medium, and Low. Then add a readiness check:

• High priority: You expect to start it soon, have a specific reason to buy now, and the final cost meets your threshold.
• Medium priority: You want it, but can wait for another sale or a deeper discount.
• Low priority: You are interested but have no near-term plan to play it.

For early access or unfinished releases, add a note about your tolerance for changing features and development risk. Our early access buying guide provides a separate checklist for that decision.

Worked examples

Imagine a fictional game listed at 24.99 in your local currency. Your recorded historical low is 14.99, and your personal target is 16.00. The current sale price is 17.49, with an estimated 1.75 in tax and no usable coupon.

• Listed price: 17.49
• Estimated tax or fee: 1.75
• Coupon value: 0.00
• Final estimated cost: 19.24
• Target price: 16.00
• Decision: Wait or review

The advertised discount may look reasonable, but the estimated checkout cost exceeds the target. You could still buy if the game is high priority and you are ready to play it; the spreadsheet makes that an explicit choice rather than an impulse.

Now consider a fictional bundle containing three games you already want. The bundle price is 18.00, but only two items are likely to be played. Record the bundle as its own row and add a Bundle Status note listing the included games. Do not assign the entire price to each title and then add those values together. Instead, compare the bundle’s total cost with the value of the items you would realistically buy individually, while noting duplicate ownership and activation requirements.

For a storefront comparison, create rows for the same edition at two stores. Include any coupon, wallet credit, or bundle condition only when you can actually use it. The lower listed price wins only after currency, tax, edition, launcher, and purchase legitimacy have been checked.

When to recalculate

Recalculate the tracker whenever a sale begins, a price changes, a coupon becomes available, or a bundle is replaced. A practical routine is to review it once before a major sale, once near the end of the event, and whenever you are about to check out. Seasonal promotions, publisher events, and bundle rotations can change the inputs enough to make an older comparison unreliable.

Update the Historical Low column when you verify a new low, but preserve the old value in Notes with its date if you want an audit trail. Review your target prices quarterly or whenever your backlog, budget, or available play time changes. A target that made sense last year may no longer reflect your priorities.

Before buying, run this final checklist:

1. Is the game, edition, and platform correct?
2. Is the final estimated cost at or below your target, or is there a clear reason to override the rule?
3. Have you checked taxes, fees, currency, and coupon conditions?
4. Do the DRM, launcher, region, and key details fit your requirements?
5. Is this a game you expect to play before another likely sale?
6. Does the purchase add value beyond your existing subscription or bundle access?

After checkout, mark the row as Bought and record the final paid amount. That small step improves your future comparisons and shows whether your target prices are realistic. For subscription alternatives, see our PC game subscription comparison; for edition decisions, use the Steam edition guide. Revisit the sheet before each sale, refresh the inputs, and let the same checklist—not the sale countdown—decide what enters your library.