A shop sign says “cheap shots.” The transaction window says something more useful: which shots, how many, and what you will actually pay. Read that window before deciding whether the offer is cheap.
This checklist is for Interlude-style servers. Private servers can change shops, currencies and client windows, so use the fields your client actually exposes. A missing detail is a reason to check the server’s documentation, not to guess.
Read the item, not just its icon
Open the tooltip and check the complete name. A recipe is not the finished piece of equipment. A weapon enchant scroll is not an armor enchant scroll. Similar icons do not settle either question.
For equipment, check the grade and enchant value wherever they are displayed. For consumables, check the type and grade. For materials, check the quantity. Compare those details with what you agreed to buy; a chat message or store title does not change the item in the window.
If you cannot identify an important property in the tooltip or confirmation screen, pause. Ask how to inspect it on that client before paying.
Work out the total yourself
First establish whether the displayed price is per item, for the selected quantity, or for the whole package. Do not move between those meanings halfway through the calculation.
Here is a hypothetical purchase, with invented prices: 500 units at 120 adena each cost 60,000 adena. If the confirmation screen shows 600,000, stop and check both the quantity and the price. Counting the digits is more useful than remembering roughly what the number looked like.
Check the currency too. A custom server may offer a shop interface that uses something other than adena. The familiar-looking window is not enough to identify what leaves your inventory.
Buying from a shop and selling to one are different jobs
Read whether the character is selling stock or buying it. When buying, check what you receive and what you pay. When selling, check what leaves your inventory and what you receive.
For a hypothetical sale, suppose a buy shop offers 2,500 adena per material and you select 40 materials. The expected payment is 100,000 adena. Those are arithmetic examples, not suggested market prices. If the screen instead offers 40,000, resolve the mismatch before accepting.
Do not rely on the shop title saying “BUY HIGH.” Compare the actual offer with other relevant shops, using the same item and unit quantity. A large total can simply mean the shop wants a large stack.
Treat a reopened trade as a fresh offer
Check the other character’s name inside the transaction window when your client shows it. Pay attention to lookalike characters in names, especially if someone says they are using an alt.
Then check both sides: your items and currency, their items and currency. If the trade is cancelled, reopened, or its contents change, run those checks again. This is a checking habit; it does not depend on your client having a particular two-step confirmation system.
Do not let “someone else is buying it now” rush the decision. If the deal requires sending your item first and trusting a later payment, the promised payment is not part of the exchange currently on screen.
Keep the last check short
Before the final action, answer five questions:
- ▸Is this the correct character and transaction direction?
- ▸Is the exact item, grade and enchant what was agreed?
- ▸Is the quantity correct?
- ▸Does unit price × quantity match the displayed total and currency?
- ▸Has anything changed since the last check?
You do not need a downloaded “trade verifier” or someone else logging into your account to answer those questions. Do not hand over your password to complete a shop purchase or enable an advertised offline-shop feature. Use the server’s published instructions for its own features.
Before budgeting for your next purchase, measure net adena from a farming run. For upgrade risks, read our enchanting guide, or browse the guide index.
Sources and version notes
NCSOFT’s original Chronicle 5 interface notes describe character and clan names in trading and private-store windows. Its original command guide documents player trading and private selling. These historical references do not establish how a custom server implements its client.
NCSOFT’s 2024 scam advice also recommends rechecking a restarted trade. That is general safety guidance, not evidence for a particular Interlude confirmation sequence.


