Steam Winter Sale 2026 Prep Worksheet - Lock Before Dec 17
![]()
If you searched steam winter sale in October 2026, you do not need another consumer “when is Steam cheap” countdown. You need a fill-in prep worksheet that locks three clocks before Discord invents a panic cut:
- Winter Sale window — December 17, 2026 – January 4, 2027 (Seasonal Sales)
- Release cliff for day-one join — released on or before November 17, 2026 (30 days before Dec 17)
- Price-increase lock — no base-price increase in any currency inside 30 days of Dec 17 (same cliff math)
This URL is that worksheet. It is not the Autumn Sale playbook (Oct 1–8 seasonal keep/hold). It is not the October triple-fest cooldown pillar (Cooking → Next Fest → Scream themed stack). Those URLs own October. This URL owns Winter prep from October planning — cite-worthy Nov 17 math outsiders can footnote.
Why this matters now
October is when studios either write the Winter staircase or lose it to themed-fest folklore. Upcoming Steam Events still stacks Cooking, Next Fest, Scream, and later Auto-Battler RPG Fest (Nov 16–23). Winter is the longest seasonal on the Seasonal Sales calendar. Teams that “decide Winter in December” discover they released Nov 20, raised EUR on Nov 25, or entered a custom discount that does not inherit seasonal exceptions.
Direct answer: Fill the worksheet below this month. Lock the Nov 17 release cliff and price-increase freeze. Enter Winter via the official seasonal Discount Management row — not a homemade “Winter vibes” custom week. Treat themed November discounts as a % staircase problem, not a false “discount cooldown blocks Winter” myth.
Who fills this worksheet
| Audience | Outcome |
|---|---|
| Beginners | One table: join / mid-sale join / sit-out |
| Developers / producers | Dated cliffs + package IDs + owner |
| Creators | Discord paste that stops December panic % |
| Companies | CapEx four-liner + diligence-ready receipt |
Time: 40–50 minutes first pass; 10 minutes to update after each October/November discount save.
Honest limit: Valve can update Seasonal Sales rows; re-check Steamworks before submit. Seasonals do not waive release or price-increase cooldowns. This worksheet models published Winter 2026 dates and Discounting rules — it does not replace partner permissions.
Non-repetition
| URL | Job |
|---|---|
| Autumn Sale playbook | Oct 1–8 seasonal ops |
| October triple-fest cooldown pillar | Cooking / Next Fest / Scream cooldown sheet |
| Cooking Fest playbook | Cooking eligibility + % |
| Scream V playbook | Horror eligibility + % |
| Final nine days | Next Fest demo ops |
| This URL | Winter Sale prep worksheet before Dec 17 |
Pair store ops with the Steam guide hub, 15 free Next Fest October demo metadata resources, and demo upload rejected - missing Steam Input default config when demo week still owns engineering time in October.
Steamworks rules you must quote (not invent)
From Discounting and Seasonal Sales:
- Winter Sale 2026 runs December 17, 2026 – January 4, 2027.
- Seasonal Sales (Spring / Summer / Autumn / Winter) are exempt from the 30-day discount cooldown and do not create that cooldown.
- Release cooldown — cannot discount for 30 days after Early Access release and Full Release (Launch Discount exception is separate and must be set pre-release).
- Price-increase cooldown — cannot discount for 30 days after a base-price increase in any currency. No exceptions. Decreases do not create this cooldown.
- Seasonals do not waive release or price-increase cooldowns.
- If your 30-day price-introduction cooldown ends during a seasonal sale, you may join mid-sale with a manually entered custom discount once clear — Steamworks says you should not feel pressured to move release dates only for a seasonal.
- The seasonal exception applies to discounts created specifically for the Seasonal Sale rows in Discount Management. A custom discount around the same dates does not inherit those exceptions.
- Discounts ≥20% (and other wishlist-email conditions in Steamworks) can trigger wishlist emails — model the lowest-priced package.
Pasteable diligence line:
Winter is seasonal-exempt for discount cooldown. Release and price-increase cooldowns still gate day-one join. Official seasonal Discount Management row only — custom overlap ≠ exemption.
The Nov 17 cliff (print this)
| Cliff | Date | Meaning |
|---|---|---|
| Winter Sale starts | 2026-12-17 | Seasonal window opens |
| Winter Sale ends | 2027-01-04 | Seasonal window closes |
| Day-one release cliff | 2026-11-17 | Latest release date to be ≥30 days clear at Dec 17 |
| Day-one price-increase cliff | 2026-11-17 | Latest price-increase date to be ≥30 days clear at Dec 17 |
| Auto-Battler Fest (themed) | 2026-11-16 – 11-23 | Near the cliff — staircase + honesty, not a false Winter blocker via discount cooldown |
Math check: Dec 17 minus 30 days = Nov 17. If you release or raise price on Nov 18, you are not clear for a day-one Winter discount on Dec 17. You may still join later in the sale when the 30-day window clears — write that mid-sale date explicitly.
Master worksheet (copy into your repo)
Save as docs/winter_sale_2026_prep_worksheet.md (or a Sheets twin). Fill every blank.
A — Identity
| Field | Your value |
|---|---|
| AppID / package IDs | ____ |
| Lowest-priced package name | ____ |
| Base price last changed (UTC) + currencies touched | ____ |
| Early Access release date (if any) | ____ |
| Full release date | ____ |
| Manage Pricing & Discounts owner | ____ |
| Worksheet owner | ____ |
| Last verified Seasonal Sales UTC | ____ |
B — Day-one eligibility gates
| Gate | Your date | Clear for Dec 17 day-one? (Y/N) | If no — mid-sale join date |
|---|---|---|---|
| Release (≥30 days before Dec 17) | ____ | ____ | |
| Price increase any currency (≥30 days before Dec 17) | ____ | ____ | |
| Launch discount still running? | ____ | ____ |
C — Official seasonal row (not custom)
| Field | Your value |
|---|---|
| Winter % on lowest package | ____ |
| ≥20% for wishlist-email plan? (Y/N) | ____ |
| Entered via seasonal Discount Management row? (Y/N/not open yet) | ____ |
| Screenshot path | ____ |
| Custom overlap week planned? (should be N) | ____ |
D — Staircase vs prior seasonals / themed cuts
| Prior window | Joined? | % | End date | Notes for Winter depth |
|---|---|---|---|---|
| Summer Sale 2026 | ||||
| Autumn Sale 2026 | Seasonal — does not create discount cooldown | |||
| Cooking Fest | Themed | |||
| Scream V | Themed | |||
| Auto-Battler RPG Fest (Nov 16–23) | Themed — near Nov 17 cliff | |||
| Custom weeklong / weekend | Creates discount cooldown for other themed/custom — not Winter |
E — November / December ops calendar
| Week | Focus | Owner | Done? |
|---|---|---|---|
| Oct 10–19 | Fill A–D; protect Oct demo ops | ||
| Oct 20 – Nov 2 | Scream honesty; do not invent Winter % from horror FOMO | ||
| Nov 3–16 | Freeze price-increase plan; decide release slips vs Nov 17 cliff | ||
| Nov 16–23 | Auto-Battler join/sit-out; do not confuse with Winter eligibility | ||
| Nov 24 – Dec 10 | Capsule / store review; confirm seasonal row open | ||
| Dec 11–16 | Final Discount Management check; Discord latch | ||
| Dec 17 – Jan 4 | Winter live; staffing for store Q&A |
F — Decision latch
| Decision | Circle one | One-line reason |
|---|---|---|
| Day-one Winter join | JOIN / MID-SALE / SIT-OUT | |
| Winter % band | % – % | |
| Price freeze until | ____ | |
| Release freeze until | ____ (or N/A released) |
Worked scenarios (patterns, not case studies)
Scenario 1 — Released May 2026, Autumn at 25%, no November price change
- Release cliff: clear.
- Price cliff: clear.
- Discount cooldown: irrelevant for Winter seasonal row.
- Decision: JOIN day-one; pick Winter % on the staircase (often similar or slightly deeper than Autumn — write the band, do not invent “must be 75%”).
- Ban: Custom “early Winter” week on Dec 10 that confuses the seasonal row.
Scenario 2 — Full release planned Nov 25, 2026
- Day-one Winter: blocked (release after Nov 17).
- Mid-sale join: cooldown clears ~Dec 25 — write the date; join with custom/mid-sale path only after clear per Steamworks.
- Ban: Moving release to Nov 15 only for Winter — Steamworks explicitly says you should not feel pressured to change release for a seasonal.
Scenario 3 — Released, but EUR price increase Nov 20
- Day-one Winter: blocked for packages affected by the increase rules (any currency increase triggers the cooldown).
- Mid-sale: clear ~Dec 20; document.
- Ban: “We only raised EUR, USD is fine” folklore — Steamworks says any currency.
Scenario 4 — Auto-Battler Fest discounter Nov 16–23
- Winter discount cooldown: seasonal exception still applies — themed week does not block Winter via discount cooldown.
- Still check: release/price cliffs; staircase depth so Winter does not look like a panic after a deep themed cut.
- Ban: Skipping Winter “because Auto-Battler used our cooldown.”
Scenario 5 — Unreleased Coming Soon with a demo
- Winter seasonal: for released games clearing price-introduction rules — do not pretend Winter = Next Fest.
- Path: demo discovery stays on Next Fest docs; Winter is a post-release seasonal plan.
- Ban: Entering Winter Discount Management on an unreleased SKU as if it were a fest registration.
Beginner path — 45 minutes this week
- Minutes 0–10: Open Seasonal Sales; paste Winter dates into section A.
- Minutes 10–20: Write release and last price-increase dates; mark Nov 17 cliffs in section B.
- Minutes 20–30: Draft Winter % band vs Autumn/Summer in section D.
- Minutes 30–40: Fill section E owners; decide JOIN / MID-SALE / SIT-OUT.
- Minutes 40–45: Discord paste + receipt stub. Do not open Discount Management until the seasonal Winter row is available and cliffs are honest.
Pass: You can state day-one eligibility in one sentence without asking Discord.
Developer path — gates W1–W6
W1 — Paste primary sources
Save:
W2 — Compute cliffs
Document Nov 17 math in the repo. Do not rely on a spreadsheet someone edited in July.
W3 — Package matrix
List every package that will carry the Winter %. Confirm the lowest package for wishlist-email planning.
W4 — Official seasonal row only
When Discount Management shows Winter, enter there. Screenshot. Reject custom overlap myths.
W5 — October / November contamination audit
Update the triple-fest pillar section E forward note to point at this worksheet. Log Auto-Battler intent without inventing Winter blockers.
W6 — Receipt + Discord latch
File winter_sale_2026_prep_receipt_v1.json. Paste Discord. Re-open only when dates or % change.
Failure modes
| Mistake | Symptom | Fix |
|---|---|---|
| “Themed cooldown blocks Winter” | Skipped seasonal | Quote seasonal exception |
| Custom Dec week as “Winter” | Lost exemptions | Official seasonal row |
| Release Nov 20 + day-one cut | Rejected discount | Mid-sale plan or sit-out |
| EUR raise Nov 20 | Blocked | Freeze prices before Nov 17 |
| <20% + expecting emails | Silent wishlists | Depth/package audit |
| Deciding % on Dec 16 | Panic cut | Fill worksheet in October |
| Treating Winter as Next Fest | Unreleased SKU confusion | Released-game seasonal only |
| No owner | Double submits | Section A naming |
CapEx four-liner
- Winter Sale is a seasonal Discount Management row — Dec 17 2026 – Jan 4 2027.
- We will not move release or raise prices after Nov 17 without accepting day-one ineligibility.
- We will not skip Winter because of themed discount cooldown folklore.
- We will not enter a custom overlap week and call it seasonal.
Company diligence questions
- What is our day-one Winter eligibility status (JOIN / MID-SALE / SIT-OUT)?
- What is the latest release and price-increase date on file?
- Who holds Manage Pricing & Discounts?
- Is Winter entered via the official seasonal row?
- What % band is approved vs Autumn/Summer?
- Which November themed fests are we joining, and did we update the staircase?
Discord paste
Winter Sale 2026 prep (seasonal)
Window: 2026-12-17 → 2027-01-04 (Seasonal Sales)
Day-one cliffs: release & price-increase clear by 2026-11-17
Status: JOIN / MID-SALE (clears ____) / SIT-OUT
Winter % band (lowest package): ____%
Official seasonal Discount Management row: Y/N/not open
Themed discount cooldown does NOT block Winter
Owner: ____
Receipt: winter_sale_2026_prep_receipt_v1.json as_of 2026-10-10
Receipt - winter_sale_2026_prep_receipt_v1.json
{
"receipt": "winter_sale_2026_prep_receipt_v1",
"as_of": "2026-10-10",
"primary_keyword": "steam winter sale",
"winter_window": {
"start": "2026-12-17",
"end": "2027-01-04"
},
"day_one_cliffs": {
"release_on_or_before": "2026-11-17",
"price_increase_on_or_before": "2026-11-17"
},
"app_id": "REPLACE_ME",
"lowest_package": "REPLACE_ME",
"decision": "JOIN_DAY_ONE|MID_SALE|SIT_OUT",
"mid_sale_join_date": null,
"winter_percent_band": {"min": 0, "max": 0},
"official_seasonal_row": false,
"custom_overlap_week": false,
"release_date": null,
"last_price_increase_utc": null,
"pricing_owner": "REPLACE_ME",
"notes": "Seasonal exempt from discount cooldown; release/price-increase still gate",
"outbound_docs": [
"https://partner.steamgames.com/doc/marketing/discounts/seasonalsales",
"https://partner.steamgames.com/doc/marketing/discounts",
"https://partner.steamgames.com/doc/marketing/upcoming_events"
]
}
Relationship to the October cooldown pillar
The October triple-fest worksheet already has a forward “Winter protection” stub. This URL owns Winter math: Nov 17 cliffs, price freeze, seasonal row, and mid-sale join. Keep October themed XOR fights on the pillar; keep Winter day-one eligibility here. Link both ways so nobody re-derives cliffs in Discord.
Relationship to Autumn
Autumn (Oct 1–8) is the prior seasonal. Joining Autumn does not create a discount cooldown that blocks Winter. Your job is staircase depth and store narrative, not invented blockers. If Autumn was skipped for release/price reasons, Winter may still be the first seasonal — write that explicitly in section D.
Creator Monday checklist
- [ ] Paste Winter dates from Seasonal Sales.
- [ ] Circle Nov 17 on a wall calendar (or digital twin).
- [ ] Freeze or schedule price increases before the cliff.
- [ ] Write JOIN / MID-SALE / SIT-OUT in one sentence.
- [ ] Draft % band vs Autumn — no Dec 16 vibes.
- [ ] Name pricing owner.
- [ ] Update October pillar forward note to this URL.
- [ ] File receipt stub even if Discount Management Winter row is not open yet.
Key takeaways
- Steam Winter Sale 2026 runs Dec 17, 2026 – Jan 4, 2027.
- Prep in October — do not invent % in mid-December.
- Nov 17, 2026 is the day-one release and price-increase cliff.
- Seasonals are exempt from 30-day discount cooldown.
- Seasonals are not exempt from release / price-increase cooldowns.
- Use the official seasonal Discount Management row.
- Mid-sale join is valid when cliffs clear during Winter.
- Themed November fests (including Auto-Battler) do not block Winter via discount cooldown.
- Model ≥20% on the lowest package if wishlist emails matter.
- Fill sections A–F; latch the receipt; paste Discord.
- This is a worksheet, not the Autumn playbook or October themed pillar.
- Cite Seasonal Sales, Discounting, and Upcoming Events.
FAQ
When is the Steam Winter Sale 2026?
Steamworks Seasonal Sales lists December 17, 2026 – January 4, 2027.
What is the Nov 17 release cliff?
To be eligible for a discount at Winter start (Dec 17), your release generally must be at least 30 days earlier — on or before November 17, 2026. Confirm against live Steamworks rules for your SKU.
Do themed fest discounts block Winter Sale?
Not via the 30-day discount cooldown. Seasonals are exempt and do not create that cooldown. Release and price-increase cooldowns can still block you.
Can I join Winter mid-sale if I release in late November?
Steamworks notes that if your price-introduction cooldown ends during a seasonal, you can join the sale already in progress once clear. Write the clear date; do not invent day-one eligibility.
Should I move my release to Nov 15 just for Winter?
Steamworks advises you should not feel pressured to change release dates only for a seasonal. Prefer an honest mid-sale plan over a rushed ship.
Is a custom discount on Winter dates the same as the seasonal row?
No. Custom discounts around seasonal dates do not inherit seasonal discount-cooldown exceptions. Use the official seasonal Discount Management entry.
How is this different from the Autumn Sale playbook?
Autumn owns Oct 1–8 seasonal ops. This worksheet owns Winter prep, Nov 17 cliffs, and the forward staircase from October planning.
How is this different from the October triple-fest cooldown worksheet?
That pillar owns Cooking → Next Fest → Scream themed stacking. This URL owns Winter seasonal prep and day-one cliffs.
What % should I set for Winter?
There is no universal number. Write a band against Summer/Autumn depth, hit ≥20% on the lowest package if emails matter, and avoid Dec 16 panic cuts.
Who should own Discount Management?
One named partner user with Manage Pricing & Discounts — section A. Two editors without a receipt cause double submits.
Related reading
- Stop Claiming Steam Auto-Battler Fest Without Autobattler Loops - 2026 — November themed identity gate near the Nov 17 Winter cliff
- Steam October Triple Fest Cooldown Worksheet - Cooking Next Fest Scream 2026
- Steam Autumn Sale 2026 - Discount Playbook Keep Hold for Indies
- Steam Cooking Fest 2026 - Themed Sale Discount Playbook for Indies
- Steam Scream V 2026 - Horror Fest Discount Playbook for Indies
- Stop Claiming Steam Cooking Fest Eligibility Without Cooking Loops - 2026
- Steam Next Fest Final Nine Days After Press Preview - Lock Before Oct 19 2026
- 12 Free Steam Wishlist Analytics Tools for Next Fest Week - 2026
- Steam guide
- 15 Free Next Fest October Demo Metadata Resources
- Demo upload rejected - missing Steam Input default config
Primary sources: Seasonal Sales · Discounting · Upcoming Steam Events.