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)

MODE,URN,GAME,SET,NAME,CARDMARKET_ID,TCGPLAYER_ID,CONDITION,PRICE,QUANTITY,VARIANTS,HIDDEN,COMMENT,NOTES,REFERENCE

​
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

ColumnRequired?Purpose
MODEYesCREATE to create a new listing, UPDATE to update your existing listing.
URNOne of URN or (GAME + SET + NAME) or an external ID is requiredManagem’s unique catalog identifier (e.g., urn:managem:pokemon:set/surging-sparks/card/1). Most precise.
GAMEConditionalGame name as recognized by Managem (used alongside SET and NAME), "Pokemon", for example.
SETConditionalSet as recognized by Managem (used with GAME and NAME). "Surging Sparks", for example.
NAMEConditionalCard/product name as recognized by Managem (used with GAME and SET). "Vulpix" for example.
CARDMARKET_IDConditionalExternal marketplace identifier (if you prefer to map via Cardmarket).
TCGPLAYER_IDConditionalExternal marketplace identifier (if you prefer to map via TCGplayer).
CONDITIONYesMust be one of the valid conditions listed below. If invalid, the row will fail validation.
PRICEYesListing price in pence, “100” for £1
QUANTITYYesInteger quantity for the listing.
VARIANTSOptional (recommended when variants exist)Use when a card/product has multiple variants (e.g., language/edition/packaging). Include the variant identifier shown in the catalog or your listing.
HIDDENOptionaltrue/false. When true, the created/updated listing is hidden from buyers.
COMMENTOptionalFree-form comment visible to buyers (same as listing comment).
NOTESOptionalPrivate notes, visible only to you.
REFERENCEOptionalThird-party integration reference (for example your internal listing ID). Non-empty values set/update the reference, and empty values clear it.

​
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. 
MODE,URN,GAME,SET,NAME,CARDMARKET_ID,TCGPLAYER_ID,CONDITION,PRICE,QUANTITY,VARIANTS,HIDDEN,COMMENT,NOTES,REFERENCE
CREATE,urn:managem:pokemon:set/surging-sparks/card/16,,,,,,NM,350,1,,,,SKU65125,partner-ref-16
  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”. 
MODE,URN,GAME,SET,NAME,CARDMARKET_ID,TCGPLAYER_ID,CONDITION,PRICE,QUANTITY,VARIANTS,HIDDEN,COMMENT,NOTES,REFERENCE
CREATE,,Pokemon,Surging Sparks,Vulpix,,,,LP,200,5,,true,"Quick delivery",,erp-vulpix-001
  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. 
MODE,URN,GAME,SET,NAME,CARDMARKET_ID,TCGPLAYER_ID,CONDITION,PRICE,QUANTITY,VARIANTS,HIDDEN,COMMENT,NOTES,REFERENCE
CREATE,,,,,794271,,NM,2,1,,false,,,cm-794271
  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. 
MODE,URN,GAME,SET,NAME,CARDMARKET_ID,TCGPLAYER_ID,CONDITION,PRICE,QUANTITY,VARIANTS,HIDDEN,COMMENT,NOTES,REFERENCE
UPDATE,urn:managem:pokemon:set/surging-sparks/card/16,,,,,,NM,325,1,,,,,

​
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.