Skip to main content
A well-formed CSV is the key to fast, trouble-free imports. This page shows the exact header, what each column means, and several examples you can copy.

​
The exact header (copy this)

​
Important

  • The header must match exactly (names and order).
  • Include all columns even if you leave some values blank for a row.
  • Files with the wrong header are rejected before upload is accepted.

​
What each column means

​
Guidance on identifiers

  • Best: URN – precise and fast to match.
  • Also fine: External IDs (CARDMARKET_ID or TCGPLAYER_ID).
  • Good when curated carefully: (GAME + SET + NAME). Make sure the strings match Managem’s catalog text.

​
Conditions

The following condition values are valid for listings. For example, if your listing is in “Near Mint” condition, you would use NM as the value.
  • Mint: MT
  • Near Mint: NM
  • Excellent: EX
  • Good: GD
  • Lightly Played: LP
  • Played: PL
  • Poor: PO

​
Examples

  1. CREATE using a URN (recommended)
In this example, we’re creating a new listing by using Managem’s URN identifier, to target a specific item (single card), creating it with a “Near Mint” condition for £3.50 and a quantity of 1. It also has a seller note, indicating a SKU that the seller will recognise upon receiving an order containing it.
  1. CREATE using Game/Set/Name
In the following example, we’re creating a new listing for Vulpix, in the Surging Sparks (Pokemon) set. Upon processing this row, our system will perform a search, attempting to match the game, set and name fields with a specific item. We’ve also added a comment to the listing: “Quick delivery”.
  1. CREATE using an external marketplace ID
Here, we’re using Cardmarket’s ID for Vulpix in the Surging Sparks (Pokemon) set, to create a new listing.
  1. UPDATE an existing listing (explicit URN)
In the following example, we’re updating an existing listing for Vulpix, adjusting its price to £3.25 and setting its quantity to 1. Because REFERENCE is empty in this row, any existing integration reference is cleared.

​
Validation rules

  • Every row must identify one catalog item (via URN, GAME+SET+NAME, or external ID, such as CARDMARKET_ID or TCGPLAYER_ID).
  • Types are strict (prices are in pence, quantity is integer, HIDDEN is true/false).
  • If a value isn’t recognized (e.g., an unknown condition), the row will be recorded as an error with an explanatory message.

​
REFERENCE behavior

The REFERENCE column is primarily for third-party integrations, to assist them with connecting their internal records with Managem listings.
  • Use REFERENCE to store your integration’s listing ID for this seller listing.
  • Non-empty values are trimmed and saved.
  • Empty values clear any stored reference.

​
Tips

  • Quote values that contain commas: e.g., "Pikachu, the Brave".
  • Keep variants consistent with the identifiers you see in the listing form/catalog.
  • Batch large jobs logically (e.g., one file per game or per set). We’ll still split into optimized batches under the hood.
  • Test small first — upload 5–10 lines, confirm counters move the way you expect, then run the big CSV.