Repository navigation
Managing your collection
A collection item belongs to one account and is identified by:
printing + finish + condition + language.
Identical variants share a quantity. The same printing in French/NM and English/EX produces two items. Repeatedly adding the exact same variant increases its quantity instead of creating a separate row for each physical copy.
| Field | Meaning |
|---|---|
| Printing | Edition of the card in a specific set |
| Finish | Provider-defined treatment or edition category |
| Condition | Cardmarket-style grade |
| Language | Language of the physical card |
| Quantity | Copies held; never negative |
| Manual price | Optional per-copy valuation override |
| Notes | Free text, up to 1,000 characters |
Use the card's stock dialog in the web catalog or the result panel in Android. Select every variant field before submitting. The web stock dialog accepts 1–1,000 copies per adjustment. API deltas range from -1,000 to +1,000 and zero is rejected.
Stock additions use atomic database increments so concurrent additions do not overwrite one another.
Choose the same printing, finish, condition and language as the copies already recorded, then Remove. Removing more copies than exist returns a conflict. A mismatch in language or condition may look like missing stock even when another variant is owned.
A zero-quantity item can remain stored with its history and be hidden from normal collection results. Use quantity changes when you want to preserve that history.
Open the item's editor from Collection. You can set the absolute quantity, change notes and set or clear the manual price. The absolute quantity is limited to 0–100,000. A quantity change records the corresponding delta in stock history.
To correct printing, finish, condition or language, remove copies from the incorrect variant and add them to the correct one. Those identity fields are not edited by the quantity/notes/price form.
Use the recent-change/history controls that expose Undo. Undo applies the reverse delta to the item's current quantity; it does not restore the whole collection to an earlier snapshot. A transaction can only be undone once. If reversing an earlier addition would make the current quantity negative, undo fails with a conflict.
Undo concerns stock transactions, not a previous manual price or notes value. Imported quantity changes also create stock transactions, but there is no single “undo entire CSV import” operation.
Permanent deletion removes the item and its stock history. It is different from changing its quantity to zero and cannot be undone using transaction undo. Export your collection or keep a server backup before bulk cleanup.
The collection supports game, name, set, colors, finish, condition and language filtering through its API, with controls exposed according to the selected view. Sort options include name, newest sets, recently changed, quantity and unit price. Price sorting uses the manual override when set, otherwise the applicable market price; unpriced items sort last.
| Code | Label |
|---|---|
| MT | Mint |
| NM | Near Mint |
| EX | Excellent |
| GD | Good |
| LP | Light Played |
| PL | Played |
| PO | Poor |
Condition is an inventory attribute. Automatic source quotes are not individually adjusted for the condition or language of each owned item. Use a manual price if you need a specific valuation for a particular variant.
Home · Troubleshooting · Documentation baseline · Source
Documented baseline: server 0.20.1 / Android 0.11.0. Game data and trademarks belong to their respective owners.
Collectors
- Getting started
- Catalog and card pages
- Managing your collection
- Prices and valuation
- CSV import and export
- Account and preferences
- Android guide
- Supported games and sources
- FAQ
Server administration
- Docker installation
- Configuration reference
- Reverse proxy and HTTPS
- Single sign on
- User administration
- Synchronization
- Data checks
- Images and symbols
- Operations
- Backup and restore
- Updates and migrations
- Troubleshooting
Technical reference