Loading page
Steam describes a counter offer as a new trade offer sent back to the other person. Treat its contents as a fresh proposal: compare what leaves each inventory and what comes back, then verify the account. Agreement in a chat or approval of an earlier version does not automatically approve the revised item lists.
| Record | Your offered side | Other side |
|---|---|---|
| Original hypothetical proposal | Item A | Item B |
| Revised hypothetical proposal | Item A and Item C | Item B |
| Review question | Did an extra item leave your side? | Did the expected return remain? |
These names stand for distinct items, not live prices. The revision changes the proposal even if Item B and the recipient look familiar. Compare both sides rather than looking only for the one object you originally wanted to receive.
Steam’s incoming-offer workflow describes responding, changing contents and sending a counter offer. That produces a new offer. The current interface may translate the action names, but the distinction between revising and accepting remains essential.
Do not assume a previous confirmation automatically applies to the revised contents. A familiar conversation can provide context without becoming approval of a particular item list. The pending-versus-accepted guide helps distinguish a proposal awaiting a decision from the result of an already completed operation.
Identify what you would give and what you would receive. Check full item names, variants and quantities rather than relying on list length. An extra similar-looking weapon may change the meaning of the offer. The trade item-name checklist focuses on that two-sided review.
If a field is unclear, stop before making a decision. It is easier to ask a specific question about one item than reconstruct a mistaken assumption after another operation. You can understand the difference by reading existing records without actually sending a counter proposal.
Review the intended account, not just the display name or avatar. A new proposal still needs the same care about recipient identity as the original. The SteamID checklist explains why visible profile decoration is insufficient.
If the item name contains a promised amount, treat that as text rather than a payment field. Steam trade offers cannot contain Steam Wallet funds. The Wallet boundary guide covers another financial distinction; neither it nor a chat agreement turns a revised item exchange into proof of money received.
A proposed change is not a completed trade, and a completed trade must be read under the relevant current rules. For CS2, the Trade Protection guide addresses eligible protected trades separately. Check eligibility and consequences for the completed trade before deciding which action applies.
Check the current records for both proposals. A counter offer is a reason to review the revised contents, not evidence that the earlier proposal is still valid or that either exchange has completed.
A concise comparison lists the original contents, revised contents, direction of each item and intended account. Mark the specific difference that matters. If you cannot explain it, leave the decision pending rather than accepting a list merely because a conversation sounded agreeable.
Use the support-evidence checklist for an unexplained discrepancy. Do not include trade tokens or authentication codes in a public comparison. The useful result is an accurately read new proposal, not an automatically inherited approval or a real transaction performed to demonstrate the workflow.
Sources checked on 2 November 2026. Labels and locations can vary by client version and language. Match the described state in your own current interface.
What you should know before you begin.
No. Steam describes it as a new trade offer sent back to the other person.
Yes. A revised proposal can change either side’s items, variants or quantities.
No. Trade offers cannot include Steam Wallet funds, and message text is not a received-payment field.
