Built for sellers expanding to every Amazon marketplace

Sell in 23 Amazon markets without writing 23 listings.

Utlista takes the catalogue you already have and rewrites every field for the marketplace it is going to, inside that marketplace's own limits, then hands you one upload file per country.

Your listing on amazon.de

Nordhaus Digitale Küchenwaage 5 kg, Edelstahl

  • Wiegt bis 5 kg in 1 g Schritten
  • Gebürsteter Edelstahl, leicht abzuwischen

What goes to amazon.fr

Nordhaus Balance de cuisine digitale 5 kg en inox

  • Pèse jusqu'à 5 kg par paliers de 1 g pour vos recettes du quotidien
  • Surface en inox brossé, facile à essuyer après utilisation

Not a translation of the German. Written for the French listing, inside Amazon's 75 character title limit.

Utlista is not affiliated with, endorsed by or sponsored by Amazon.

Three steps, one file per country

You stay in control of the copy. Nothing reaches Amazon until you have read it and downloaded the file yourself.

Any CSV or tab separated export from Seller Central. You tell us which column is which, so it does not matter which report you pick.

Any of the 23 Amazon marketplaces, from the United States and Mexico to Germany, Japan and Australia. Every product is rewritten once per marketplace you choose.

Every listing is checked against that marketplace's field limits before it can go in the file. Anything we are not confident in is held back until you say otherwise.

How it works, in full

inventory-report.txt

48 rows, 21 columns

Which column is which

  • seller-skuSKU*
  • item-nameTitle*
  • item-descriptionDescription
  • bullet-point1Bullet 1
  • bullet-point2Bullet 2
  • brand-nameBrand

Matched by name where we could. Only SKU and Title are required.

One product, every market

The same title is a different sentence in every store

Word order, compounding, spelling, script and units all change between marketplaces. Each one is written for separately.

Written as illustrations of each language difference. The before and after at the top of this page is real output.

What you actually get

Rewritten, not translated

Each field is written for the destination marketplace rather than passed through a translator.

Researched per marketplace

Every listing is built around the phrases that marketplace's own shoppers type, ranked by how often they are searched.

Every field inside its limit

Title, bullets, description and search terms are checked in code against that marketplace's limits, not left to a model.

Nothing ships unread

A listing that fails a check stays out of the upload file until you accept it. A suppressed listing costs more than a slow one.

One upload file per country

Tab separated, in the shape Seller Central expects. You upload it yourself, in your own account.

Your account stays yours

Seller Central is read only, or skip it and upload a spreadsheet. Utlista never changes, uploads or publishes anything on Amazon.

Every feature, problem by problem

Inside Amazon's limits

Every field written to its budget

The limits go in before a word is written, and every listing is checked against them in code before it can enter a file.

Title

75characters

Including spaces. A longer title is replaced by an Amazon written one.

Bullets

5 x 255characters each

The third-party seller figure, not the looser Vendor Central one.

Description

2,000characters

Written for the market, not padded to the budget.

Search terms

249bytes

Bytes, not characters. One byte over and Amazon discards the field.

Why search terms are counted in bytes

14 characters, 17 bytes

écran sécurité

Every accented letter is two bytes in UTF-8. 250 characters of French search terms can be close to 280 bytes, and Amazon drops whatever runs over without an error. Utlista counts and trims by byte, between characters, so a split letter never reaches a live listing.

Questions worth asking

No. A translation preserves your sentence; this writes a new one for the destination marketplace. A German compound noun becomes a French phrase in French word order, a Dutch compound stays welded together because splitting it would destroy the search term, and the everyday word is chosen over the dictionary word. The output is checked against Amazon field limits in code before it can go in a file.

Every Amazon marketplace, 23 in all: amazon.fr, amazon.it, amazon.es, amazon.nl, amazon.pl, amazon.se, amazon.de, amazon.co.uk, amazon.ie, amazon.com.be, amazon.com.tr, amazon.com, amazon.ca, amazon.com.mx, amazon.com.br, amazon.ae, amazon.sa, amazon.eg, amazon.co.za, amazon.co.jp, amazon.in, amazon.sg, amazon.com.au. Any one of them can be the source and the rest can be targets. Most of them do not price in euro, which matters when you plan the expansion rather than just the copy.

No, by design. If you connect Seller Central, Utlista asks Amazon for read access to your listings and nothing else, and it never writes to your account. Every run produces a tab separated upload file per marketplace which you download and upload yourself. A tool with write access to your catalogue is a tool that can damage it.

No. The catalogue you upload is read, never written to. A run creates new copy for other marketplaces and leaves the source listing exactly as it was.

That is the problem the quality gate exists for. Every listing is checked in code before it can enter the upload file: field lengths, search terms measured in bytes, required fields present, whether the text is actually in the target language, and whether it reads as localised rather than transliterated. Anything that fails is held back and shown to you with the reason rather than shipped quietly.

All 17 questions

Try it on ten of your own products

No card. You will have a real upload file for a real marketplace in a few minutes, and you can decide from that.