← Friday Seller Tools

Seller guide

What are the character and byte limits for marketplace listing fields?

Count title, bullet, description, and search-term fields in the unit the current marketplace template uses, then separate a measurable length problem from category rules, unsupported claims, and other reasons an upload can fail.

Start with the exact marketplace, category, and field

There is no safe universal listing-length table. Amazon, Walmart, Shopify, and eBay use different caps, and a category, product type, program, locale, or upload template can be stricter than a general help-page limit. Record the marketplace, field name, category or product type, locale, and the date you checked the current template. Treat a remembered limit from another listing as a lead to verify, not as evidence that the present field will be accepted.

Identify whether the cap uses characters or bytes

A character cap counts Unicode code points; a byte cap measures the encoded value. Plain ASCII letters often make those totals look identical, but accented letters, curly punctuation, non-Latin scripts, and emoji use multiple UTF-8 bytes. Count both and apply the unit named by the current field rule. For a byte-limited field, a character counter alone can say the copy fits while the encoded submission is still over budget.

Measure every repeated field independently

Titles, descriptions, and search terms are usually single values, while bullet or feature fields repeat. Check each bullet against its own cap instead of adding them into one total. Preserve whitespace and punctuation exactly as the validated input will submit after your preparation system normalizes it. A useful audit reports the measured count, applied cap, unit, and overage for each field so a reviewer can trace why a row was flagged.

Use a truncation preview only to locate the problem

A mechanical preview at the limit shows how much copy must be reconsidered, but it is not publishable editing. It can stop mid-sentence, remove a qualifier, orphan a list, or change the meaning of a factual claim. Rewrite from verified product facts, keep the most decision-useful information, and count again. Never silently cut a SKU, GTIN, model number, compatibility statement, warranty condition, or required safety language merely to fit.

A within-limit result is not an approval

Length is one deterministic check. A field can fit and still fail because a required attribute is missing, an identifier is invalid, markup is unsupported, a claim lacks evidence, or the selected category applies another rule. Verify the current template, run the other relevant structural and claim checks, and have a human review the final copy before upload. If the marketplace rejects it, preserve the exact message and diagnose that evidence instead of guessing that length caused the failure.

Tools that help with this

Every paid output is a draft for your review before you publish, appeal, or activate anything. Friday does not access your seller account.

More seller guides

Browse all guides →