The 102-Trees Session Challenge - Run a Christmas Tree Lot Wiki
A real session goal from the community — what selling one hundred and two trees in a run actually demands.
Run a Christmas Tree Lot Wiki
Overview
The 102-tree challenge is a community session goal made famous by a real playthrough: sell one hundred and two Christmas trees before the session ends. It is not an in-game quest — the game tracks no such counter — but as a self-imposed benchmark it tests every skill the loop has, which is exactly why it makes you better.
This guide treats the number as a stress test rather than a trophy: the opening beats, the pace checkpoints and the streak breakers below are the same habits every high-volume session runs, just with a visible score attached.
- Goal
- 102 trees sold in one session
- Type
- Community benchmark
- Tests
- Stock rhythm + service speed
- Difficulty
- Mid — needs full sessions
The Session That Named the Goal
This is the run that gave the challenge its name — a player counting trees sold past the hundred mark. Watch the hands, not the number: the restocking between serves is the entire strategy, compressed into one session.
What the Challenge Actually Tests
One hundred and two sales in a session is a throughput test, not a luck test. At that volume, every second of dead time compounds: an empty shelf here, a slow checkout there, and the counter stalls dozens of sales short. The challenge quietly grades your restock rhythm and your selling routine at once.
It also tests stamina economy — the decision of what to do between customers, minute after minute. Players who treat the gaps as decoration time stall in the seventies; players who treat every gap as a mini-restock cruise past one hundred. The counter is honest about which player you are being today.
The 102-Tree Opening
High-volume sessions are won in the opening moves, not the final sprint — by the time the counter passes sixty, there is no time left to fix a bad opening. Four beats to set up a run that can actually reach three digits, each one cheap to do now and expensive to retrofit later.
Bank a deep opening stock
Order more than a normal first cycle — two or three families at depth. Restock trips are the tax on volume; prepay it.
Clear the lanes
Layout before customers: grouped rows and walking lanes, per the catalog guide. Traffic flow is throughput.
Lock the serve-restock alternation
One restock beat between every few serves, from the very first customer. The habit holds when the queue doubles later.
Hire at the first real stack
When checkout backs up past a couple of customers, a cashier pays for itself mid-challenge — this is the one hire worth making mid-run.
Pace Checkpoints
Rather than inventing minute marks your session will not obey, track these qualitative states — each one is a healthy or broken signal that predicts whether the counter reaches three digits long before the number itself does. Read them between customers; they update in real time.
| State | Healthy | Broken |
|---|---|---|
| Shelves | Rows never fully empty | Whole families sold out at once |
| Queue | One or two waiting, moving | Three or more, static |
| Cash | Always enough for the next order | Waiting on sales to afford restock |
| Attention | Alternating serve and restock | Parked at one station for minutes |
What Breaks the Streak
Three failure patterns end 102-runs early, and all three are visible a full checkpoint before the counter stalls. Learn them here instead of learning them at tree ninety — each one feels productive in the moment, which is exactly why it survives long enough to break the run.
The mid-run shopping trip
Pausing to browse upgrades at tree sixty is the classic stall. Prep before the run; shop after it.
Under-ordering at depth
Normal-size orders force constant truck trips. Volume needs depth — over-order your proven sellers.
Dropping the alternation
Serving five customers straight while shelves die trades visible sales for invisible empties.
After the Counter Hits 102
The number is arbitrary on purpose — it marks the point where your routine survived volume. Cash out the momentum: reinvest the wave immediately, bank the rest toward your next gate, and treat the run as a diagnostic of which habit slipped first. The next hundred starts with that answer, and the reputation routine keeps the crowd coming back for it.
Frequently Asked Questions
Is 102 trees an official in-game goal?
No — the game tracks no such counter. It is a community session benchmark named after a real playthrough, used as a self-imposed throughput test.
How long does a 102-tree run take?
A settled routine clears it inside a normal long session; the exact time varies with traffic and stock depth. Focus on the pace checkpoints rather than the clock.
Do I need game passes to hit 102?
No — the run rewards rhythm, not multipliers. Passes like 2x Cash raise the payout of the same sales, per the pass guide, but the counter is technique.
Which trees should I stock for volume?
Two or three reorderable families at depth — variety spreads buyers, depth feeds them. The tree catalog covers the mix logic.
Why do my runs stall in the seventies?
Almost always one of the three streak breakers: a mid-run shopping trip, under-sized orders or a dropped serve-restock alternation. Check the grid and fix that habit.
Can I run the challenge with friends?
Yes — a full server with the co-op roles assigned turns the challenge into a team benchmark with a shared counter.