CS2 Trade-Up Guide

How to Buy CS2 Trade-Up Inputs Without Destroying Your ROI

Published July 9, 2026 · Updated July 9, 2026 · 4 min read
TL;DR

Buy CS2 trade-up inputs from a written basket plan, not by wear label alone. Set a maximum total cost and maximum average normalized input position, inspect each item's full float and skin-specific range, record the running cost and normalized sum, and recalculate every output after the final item. The contract remains worth executing only if the completed basket still meets both the normalized float target and current post-fee EV.

What should you calculate before buying any input?

Write down five things: the exact collection mix, input rarity and quality, maximum basket cost, maximum average normalized input position, and every eligible output. For each planned input skin, retain its minimum and maximum float so you can translate that normalized target into a raw listing target. Then calculate the output float, wear-specific price, probability, and net EV for that plan.

This prevents a common failure mode: buying several attractive low-float items before discovering that the remaining inputs are unavailable at a price that preserves profit.

Why is a wear label not precise enough?

Field-Tested spans 0.15 to below 0.38. Two items can share that label yet occupy very different normalized positions within their own skins' allowed ranges. Inspect the full numerical float for each listing, normalize it as (raw − skin min) ÷ (skin max − skin min), and retain the item identifier so you purchase the one you calculated.

If your marketplace rounds float in the search results, open the item detail or inspect link. Never assume a displayed 0.15 is safely below a calculated 0.1505 cap.

How do you set an input price cap?

Start with the maximum total cost supported by the contract's net EV and your required margin. Then decide how much of that budget can go to scarce low-float inputs.

Remaining budget = maximum basket cost − cost already committed
Average budget per remaining item = remaining budget / items remaining

The average is a guardrail, not a requirement. Paying more for one low-normalized input can be rational if it lets the other inputs be cheaper and still keeps the final output under a valuable wear boundary. A low raw float is not automatically low-normalized when its skin has a tight or elevated allowed range.

How should you track the basket while shopping?

FieldWhy it matters
Item and collectionPreserves the intended outcome probabilities
Exact float and skin min/maxDetermines the item's normalized contribution and output wears
Purchase priceDetermines current input cost
Trade availabilityPrevents timing assumptions from breaking
Marketplace item IDAvoids buying a similar but wrong listing

After every purchase, update the running normalized sum and remaining maximum:

Normalized item = (raw float − skin min) / (skin max − skin min)
Maximum remaining normalized sum = target normalized average × total items
                                   − purchased normalized sum

Divide that value by the number of items still needed to see their average normalized ceiling. Translate that ceiling back through each candidate input skin's range before filtering raw marketplace floats.

Should you buy the rarest inputs first?

Usually, source the hardest constraint first: a scarce collection, unusually low float, or strict price cap. Abundant filler can wait. But do not overpay simply because you have already started. Money spent on earlier inputs is a sunk cost; the remaining basket must still make sense at current prices.

What should you verify before submitting the contract?

  1. Confirm every item has the intended rarity, quality, and collection.
  2. Normalize every selected item within its own skin range and recalculate the exact normalized average.
  3. Recalculate output float separately for every eligible result.
  4. Refresh output prices, bids, and marketplace fees.
  5. Confirm all outcome probabilities total 100%.
  6. Compare current net EV with the actual amount paid.
  7. Review worst-case loss, not only expected ROI.

Use the formulas in our output-float guide and EV guide for the final check.

What sourcing mistakes most often erase profit?

When should you abandon an incomplete basket?

Stop when the lowest realistic cost of the remaining items pushes total cost beyond your cap, or when available inputs can no longer meet the target normalized average. You can hold or resell already purchased inputs, but completing a negative-EV contract does not recover their cost.

Frequently Asked Questions

Can I buy inputs by wear tier instead of exact float?
Wear tier is too broad for precise trade-up math. Inspect and record the exact float of every item, especially when an output is near a wear boundary.
Is it worth paying extra for a low-float input?
Only when its lower normalized position within that skin's own range improves the completed basket enough to raise realistic output value by more than the premium. Evaluate the whole basket, not the raw float in isolation.
What if one planned input becomes too expensive?
Recalculate before substituting it. A different collection changes output probabilities, and a higher float can change output wears. Abandon the plan if the revised basket no longer clears your cost and risk limits.
Should I recheck prices after buying all inputs?
Yes. Reprice every output and fee immediately before submission because EV can change while you source the basket.
CS2InputsExecution

Stop calculating contracts by hand

TradeUpTarget ranks opportunities found within each timestamped, bounded CS2 scan, with normalized float math, post-fee modeled EV, and execution state kept separate.

Open the Scanner →