The shop is the conversion point between dungeon loot and future progression. You place relics for sale, choose a price, observe how customers respond, and use the proceeds to prepare for later expeditions. The important detail for a guide site is that prices can be version- and variant-sensitive.
Quick answer
Use a stored verified price only when the relic, quality or stamp, and game version all match. If any of those dimensions differ, treat the lookup as missing instead of applying an assumed multiplier.
Read feedback as evidence
Customer behavior is part of the official shop-management loop. When researching a new value, change one relevant variable at a time, note the exact item variant and build, and keep the observation date. A useful record explains what was seen; a bare number copied without context cannot establish a current price.
The price guide distinguishes verification states:
- Verified records meet the published evidence standard.
- Community reported values are leads, not confirmed answers.
- Needs review means an update or conflict may have changed the answer.
- Outdated values belong to an older game version.
What the calculator calculates
The exact lookup does not manufacture a unit price. Once a verified unit price exists, it may calculate:
quantity total = verified unit price × quantityestimated profit = quantity total − cost entered by the user
The cost field is local input for convenience. It is not stored as game data and does not change the verified unit price.
Common mistakes
Avoid carrying forward an Early Access value after a major update, comparing a different quality as though it were the same item, or interpreting a zero as “no data.” On this site an unavailable answer is shown explicitly; zero is reserved for a real observed value if the game ever supports one and the evidence proves it.
Version notes
All production price records remain empty until current-build in-game evidence is retained. This lets the tool be useful and safe on day one without presenting demo values as facts.