CS2 trade accepted but skin missing? How to trace the item

Problem this solves

A trade or marketplace says completed, but you cannot find the skin.

What you can do afterward

Match the order to Steam history, locate the missing step and prepare the right support request.

“Accepted” can describe a button you pressed, a marketplace order label or a completed Steam transaction. Start by identifying which one you have. A seller’s screenshot or a payment receipt is useful context, but neither substitutes for the record in your own Steam account. Avoid buying the item again while that distinction is unresolved.

Find the actual transaction before troubleshooting the inventory

Open Steam directly and confirm the account name and profile. If your browser, mobile app and desktop client use different accounts, write down which account received the offer. Then open your Steam Trade History. Find the relevant counterparty, date and item. Record the current status as Steam displays it; distinguish the incoming transaction from any outgoing one beside it.

Steam buy orders can remain active while awaiting a matching listing. Market history is available from the Community Market, and completed transactions have emailed receipts. Do not search only Trade History for a Market purchase. Market records and buy orders [3]

Compare more than the thumbnail. Use the full item name, wear category, StatTrak or Souvenir status and quantity. Add float, pattern or sticker details if you already have them. Two identical names do not necessarily identify the same individual skin. For a batch of cases, reconcile quantities instead: how many were ordered, included in the exchange and found afterward?

Choose your next evidence check

Compare the views that appear to disagree

Make a short record of where the item appears and where it does not. “My inventory is empty” is much less useful than “the signed-in Steam inventory shows the AWP, but the external site’s sell selector does not.” Capture any error before refreshing the page or reopening CS2 once to see whether the view changes.

Steam lets you open Inventory from your profile and control who else can view it. Your signed-in view and another service’s view need separate checks. Steam inventory access and privacy [2] Public visibility and a site’s refresh behavior are not reliable substitutes for checking your account. Ask that site which record it needs when its display conflicts with Steam.

For an older item, inspect Storage Units inside CS2. Stored items are absent from the Steam Community inventory; retrieve an item before trying to use or transfer it. After retrieval, search or scroll: it returns to its previous position rather than appearing at the top. Storage Unit behavior [4] A newly received, still-protected item cannot be put into storage, so storage is not the explanation for every recent trade. Protection restrictions [1]

If you can find the item but cannot select it for sale, read its description. Steam’s sell picker only displays eligible items. Market eligibility [3]Record any availability date and separate an item restriction from an account-wide error. Use the trade and Market restriction guidewhen the evidence points to availability rather than delivery.

Check what happened after the incoming trade

Trace forward from the incoming entry. Look for a later outgoing trade, reversal, Market sale or an action you remember taking with the item. Keep the times and time zones attached to each record. An old incoming screenshot does not answer whether a more recent event changed the account’s inventory.

A protected-trade reversal returns affected items to their previous owners. Reversal rules [1] Match the reversal to the original transaction before calling it a delivery failure. If money changed hands on an external site, ask that site to investigate the related order; do not assume its payment state updates merely because Steam’s item state changed. Completed Steam Community Market transactions follow a separate, final-sale rule. Market transaction policy [3]

Five examples of turning observations into a next step

These are illustrative cases, not reports from customer accounts.

1. The marketplace says accepted, but the Steam record is unfinished

Maya has an order number and an acceptance message. She cannot find a completed incoming exchange for the quoted skin. She saves the current Steam status and asks marketplace support to match the order to its delivery record. If Steam presents an action, she checks its recipient and contents before proceeding. She does not reorder to test whether delivery works.

2. The skin is in CS2 but absent from an external sell selector

Idris finds the exact finish and stickers in his signed-in account. The site shows no matching skin. He records the item’s restriction notice and the site’s error, then checks the connected profile and refresh information. His support question becomes why that selector omits this item, rather than where Steam sent it.

3. An older case collection seems short after retrieval

Lena expects 40 cases but sees only 12 at the top of her inventory. She searches the full inventory and checks the relevant Storage Unit. She reconciles the number still stored with the number retrieved instead of counting a single screen. The useful evidence is the collection total and storage contents, not an unrelated recent trade.

4. A completed trade is followed by a reversal

Omar has an incoming record and a later reversal affecting the same exchange. He saves both and includes the external order reference in a request to that marketplace. He asks how its order will be resolved against the changed Steam record. He does not treat a seller’s chat promise as proof that payment has already been returned.

5. The records still disagree after all relevant views are checked

Jo finds the correct incoming exchange, checks the exact account and item, and cannot find a later event explaining the absence. Steam and CS2 still show no item after reopening the views. Jo submits the compact evidence packet below. It describes the unresolved mismatch without inventing a cause or demanding a particular restoration outcome that the records have not established.

Copy a support packet that identifies the mismatch

For a Steam-side missing-item problem, start with Steam’s item support page and select the relevant issue. It provides routes for purchases, Trade History and missing or stolen items. For an external order or display problem, use that service’s official support entry point. A case involving both may need both records attached to the respective requests.

Copy this template and fill it in within your support request. Omit fields you cannot verify. Include only relevant screenshots and redact unrelated personal or payment information. Passwords, session cookies, authenticator codes and recovery codes do not belong in this packet.

Problem: Expected CS2 item is missing from [specific view].
Account/profile involved: [identify the correct account]
Transaction type: [Steam trade / Steam Market / external order]
Steam trade or Market record: [reference and displayed status]
External order reference, if applicable: [reference]
Item: [full name, wear, StatTrak/Souvenir, quantity]
Distinguishing details already available: [stickers, float, pattern]
Expected incoming event: [date, time and time zone]
Later relevant events: [outgoing trade / reversal / sale / none found]
Checked views: [signed-in Steam inventory / CS2 / storage / site]
Exact error or item restriction: [wording and displayed expiry]
Attachments: [transaction record and relevant inventory/error views]
Please investigate: [the specific mismatch between these records].

End with one concrete question: “Which later event explains this item leaving the account?” or “Why does order 123 show delivery when I cannot match it to a completed incoming trade?” Keep replies in the same support case as new evidence arrives. That gives the investigator a continuous record instead of several disconnected reports.