Platform support
Build a Back Market listing CSV for one platform
Back Market’s API guidelines say sellers can work in the API, in the back office, or by moving between them. The back office imports and exports CSV files for products, offers, and orders. FTP is deprecated. A listing CSV is limited to 15,000 lines, and the column list for a category is generated in the back office under Options, then Batch Listing Creation. The same document’s sample catalog is three columns. One listing can carry more than one country, and quantity is shared across those countries. The account itself sits on the AP, EU, or US platform.
Where does Back Market say the listing file comes from?
The guidelines tell a seller to open the back office for the platform the account is on: backmarket.co.jp for AP, backmarket.fr for EU, and backmarket.com for US. Preprod has the same three hosts with a preprod subdomain. Creating or updating listings through POST /ws/listings sends a JSON body whose catalog field is the CSV content as a string. The body also requires quotechar, delimiter, and encoding. The published example is quotechar "," delimiter "," encoding utf-8, and this catalog string: sku,quantity,price and then MY_SKU,50,123.45. A 400 example in that operation is the sentence “parameter catalog not found”. The guidelines say the column list for that catalog field is in the back office at Options, then Batch Listing Creation. They also say a new product cannot be created without a listing, and that a product already validated by Back Market stays as it is if you submit a change. You contact Back Market for changes to a validated product.
Country codes select the language and country of an action. The EU list in the guidelines is fr-fr, fr-be, es-es, de-de, de-at, it-it, en-gb, nl-nl, pt-pt, en-ie, el-gr, sk-sk, and sv-se. AP is ja-jp and en-au. US is en-us. The guidelines say you do not create a separate listing per country. listing_id and quantity are shared. comment, price, and warranty_delay are per country. On the product, weight and EAN are shared, and description, title, and price_new depend on the country. Setting quantity to 0 takes the listing offline. Those names are in the prose. The Batch Listing Creation download is the header row for the category.
Which CSV punctuation do the guidelines require?
The getting-started section says every file imported through the back office or the API is CSV, the field separator is a semicolon, the line separator is a line feed, and fields are surrounded by double quotes. The listings operation describes quotechar as “The separator of columns” and delimiter as “The delimiter of data”, and its example uses a comma between sku, quantity, and price. Those two passages do not give one punctuation rule. The file you download from Batch Listing Creation is the file for that category on that platform. The 15,000-line ceiling is stated for the CSV you submit. A separate note says Back Market might not accept more than 2,000 lines of SKUs to process per hour on the update-listing endpoints, and that reaching the limit can produce HTTP 429 Too Many Requests.
The guidelines also describe a web application firewall. A blocked call can be HTTP 403, and one example body uses the code bot-need-challenge with the message Forbidden. That is an API response in the guidelines, not a column in the CSV. The Seller Support Center link printed in the guidelines, https://merchant-support.backmarket.com/hc/en-us, returned HTTP 403 on 2 November 2026, so no help-center article is quoted here. The portal page https://api.backmarket.dev/ is the page that points at the bundled OpenAPI file retrieved for this article.
How do you map a supplier file onto the Back Market CSV?
- Open the back office for the platform on the account: AP, EU, or US. Go to Options, then Batch Listing Creation, and download the CSV for the category you are listing.
- In Golanto, choose Back Market. Record the platform, the country code, the category, and the date of that download. The mapper still opens on Amazon until you change the platform.
- Map supplier values onto the headers in that download. Keep the sample sku,quantity,price inside the API example. Do not replace the downloaded header with those three names.
- Use the punctuation of the file you downloaded. The guidelines require a semicolon in one section and show a comma in the listings example. The download settles the file in your hand.
- Keep one listing for the countries it already covers. Quantity applies to all of them. Price, comment, and warranty delay are the country-specific listing fields the guidelines name. A quantity of 0 is how the guidelines say you take a listing offline.
Worked example
A supplier row is not the Back Market category CSV
sku,title,price
PHONE-2,Refurbished phone,249.00These headings are a synthetic supplier sketch. The guidelines’ own catalog example is sku,quantity,price and MY_SKU,50,123.45. The same page says the columns for a category are generated under Options, then Batch Listing Creation. Quantity is shared across countries on a listing. Price is one of the country-specific listing fields the prose names. AP, EU, and US are different back-office hosts.
What this check cannot establish
Golanto does not log in to the Back Market back office or call POST /ws/listings. This page uses the API portal and the bundled OpenAPI file it references, both retrieved on 2 November 2026. The OpenAPI info version is 0.1.1. The file does not print the Batch Listing Creation header, and the three-column sample is an example of the catalog string. The getting-started section requires a semicolon separator and quoted fields. The listings example uses a comma and describes quotechar as the separator of columns. This page does not pick a winner. The Seller Support Center URL in the guidelines returned HTTP 403, so it contributes no column and no error sentence. HTTP 429 Too Many Requests is the response the guidelines attach to the hourly SKU limit. “parameter catalog not found” is the 400 example on the listings operation. Country codes are listed separately for the AP, EU, and US platforms. A CSV downloaded on one platform is the file for that platform.
Check your file
Start with a copy. Review changes before downloading your import file.
Open the template mapperOfficial references
Common questions
Is sku,quantity,price the Back Market listing header?
It is the example catalog string on POST /ws/listings. The guidelines say the columns for a category are in the CSV you generate at Options, then Batch Listing Creation. Use that download. The sample row MY_SKU,50,123.45 is the documentation’s example, not your catalog.
Does one Back Market listing CSV cover every country?
The guidelines say one listing holds every country you sell, and that quantity is shared while comment, price, and warranty_delay are specific to a country. The back office is still split into AP, EU, and US accounts. Download the category file from the account you are filling. The EU country codes printed in the guidelines run from France and Belgium through Sweden, and they are not the AP or US list.