Cardmarket CSV Export: What Sellers Need to Know
Last updated:
This guide describes which files Lumex Pro creates for Cardmarket, what is in them and how to use them. All details on columns, codes and limits come straight from Lumex Pro's export code.
In short
- Lumex Pro creates two kinds of files: a CSV in the Cardmarket API schema (semicolon) and a bulk listing file for Cardmarket's "List Bulk Items" web form (comma).
- Both files are UTF-8 with a BOM, and lines end with CRLF.
- Only approved cards (status
approved) that have a price are exported. - We did not find a CSV upload function for listings in Cardmarket's seller area (as of July 2026, please double-check in the Cardmarket help center). How you actually enter cards is explained below.
Important first: Cardmarket and CSV
As of July 2026, we found no feature of its own in Cardmarket's seller area to upload listings as a CSV. Entering many articles at once works through the "List Bulk Items" web form, which browser extensions can fill in. Cardmarket may change this. Check the current state in the Cardmarket help center before you build your workflow on it.
Format 1: CSV in the Cardmarket API schema
The columns match the schema of the POST /stock endpoint of the Cardmarket REST API. We compared it with the open-source tools pymkm and mkmcsv, which work with real Cardmarket data. Lumex Pro currently has no API access to Cardmarket and does not upload this file itself. It is intended for possible later API access; that is not a commitment.
File properties:
- Semicolon separator, UTF-8 with BOM, CRLF line endings.
- One header line, then one line per article.
- Prices use a dot and two decimals, for example
1.50. - The flags (
isFoil,isSignedand so on) are written as0or1. - Condition and language are written as number codes. If either is unknown or cannot be mapped, the cell stays empty.
- A field is wrapped in double quotes if it contains a semicolon, a double quote or a line break. Double quotes inside the text are doubled.
- If a text field starts with
=,+,-,@, a tab or a line break, Lumex Pro prepends a'. Spreadsheet programs then treat the field as text, not as a formula.
The header line is:
idProduct;amount;price;idLanguage;condition;isFoil;isSigned;isAltered;isPlayset;isReverseHolo;isFirstEd;comments
A sample line with made-up values (idProduct 123456, two copies, 1.50, German, Near Mint, foil):
idProduct;amount;price;idLanguage;condition;isFoil;isSigned;isAltered;isPlayset;isReverseHolo;isFirstEd;comments
123456;2;1.50;3;2;1;0;0;0;0;0;
Condition codes
| Abbreviation | Name | Code in the file |
|---|---|---|
| MT | Mint | 1 |
| NM | Near Mint | 2 |
| EX | Excellent | 3 |
| GD | Good | 4 |
| LP | Light Played | 5 |
| PL | Played | 6 |
| PO | Poor | 7 |
Language codes
| Abbreviation | Language | Code in the file |
|---|---|---|
| EN | English | 1 |
| FR | French | 2 |
| DE | German | 3 |
| ES | Spanish | 4 |
| IT | Italian | 5 |
| CS | Chinese Simplified | 6 |
| JP | Japanese | 7 |
| PT | Portuguese | 8 |
| RU | Russian | 9 |
| KO | Korean | 10 |
| CT | Chinese Traditional | 11 |
The mapping comes from the selection lists of a Cardmarket account (as of 1 July 2026) and was compared with the open-source tools pymkm and mkmcsv. What Cardmarket itself shows is always authoritative.
File size
Lumex Pro writes at most 500,000 rows and 250 MB per file. Larger inventories are split into several files automatically.
Format 2: bulk listing file for "List Bulk Items"
This format is made for Cardmarket's "List Bulk Items" web form. The form loads one expansion at a time and matches rows by card name, not by idProduct. It is usually filled in with a browser extension. Lumex Pro points to an open-source extension by a third party for this, but does not operate it. Lumex Pro gives no warranty for the function, security or continued availability of the extension. You use it at your own risk; check its permissions and source code before installing.
File properties:
- Comma separator (not semicolon), UTF-8 with BOM, CRLF line endings.
- Condition and language are written as text, for example
Near MintandGerman, so the file stays readable before you load it. - Foil and signed are written as
YorN. - Prices use a dot and two decimals.
The header line is:
Name,Set,Language,Condition,Quantity,Price,Comment,IsFoil,IsSigned
The same sample card in this format:
Name,Set,Language,Condition,Quantity,Price,Comment,IsFoil,IsSigned
Example Card,Example Set,German,Near Mint,2,1.50,,Y,N
Splitting by expansion and page
The Cardmarket form shows an expansion in blocks of about 100 cards, sorted by collector number. The extension only finds cards on the page that is currently loaded. That is why there are two routes:
- Page-aware export (Magic): Lumex Pro works out which form page each card should appear on and creates one file per expansion and page. It also provides a link that opens the form with the matching expansion and page.
- Classic export: one file per expansion, with at most 100 rows per file. This is the fallback if the page calculation does not fit an expansion. Cards without a page calculation (Pokémon, for example) are output this way as well.
If Cardmarket shows more than 300 articles for an expansion, the form does not page any further. Lumex Pro then calculates the page within the rarity (common, uncommon, rare, mythic) and sets the rarity filter in the link. For other rarities there is no link in that case, so use the classic export.
In the page-aware export you can also pick a pricing rule that is applied to the prices when you download.
How to proceed
- Scan and review cards, set the price in staging and approve them.
- In the Listing area, choose the format and download the file.
- For the bulk listing file: open the Cardmarket form for the expansion and load the file with the browser extension.
- Mark the cards as listed in Lumex Pro so they do not appear in the file again on the next export.
Common pitfalls
- Wrong separator: the API schema uses semicolons, the bulk listing format commas. When you open a file in a spreadsheet program, it helps to choose the separator manually.
- Empty condition or language cell: the card has no condition or language in staging, or the value is not one of the codes listed above.
- Card missing from the file: it is not approved or has no price.
- Card not found in the form: it sits on a different form page than the calculation predicted. Use the classic export in that case.
Further reading
The home page shows how scan, staging and export fit together in Lumex Pro. Plans are on the pricing page. If you are still deciding whether to sell on Cardmarket regularly, the guide Becoming a Cardmarket Seller is a good start.
Frequently asked questions
- Can I upload the CSV file to Cardmarket directly?
- We did not find a CSV upload function for listings in Cardmarket's seller area (as of July 2026, please double-check in the Cardmarket help center). The file in the API schema is meant for Cardmarket API access, which Lumex Pro does not use at the moment. For bulk listings there is the bulk listing format for Cardmarket's web form. Check the current state in the Cardmarket help center.
- Why semicolons and a BOM?
- The file in the API schema is semicolon-separated and UTF-8 with a BOM, and lines end with CRLF. The BOM marks the file as UTF-8 so special characters in card names and comments survive. The bulk listing file, by contrast, is comma-separated.
- Which cards end up in the file?
- Only approved cards (status approved) that have a price. Cards without a price are not exported; you set the price in staging beforehand.
- What does the condition code in the file mean?
- The file contains a number instead of the condition name. Near Mint (NM), for example, is written as 2. The full mapping is in the table in this guide.