Product description — when Amazon actually shows it.

The product-description field used to be the second-biggest text block on the PDP — a 2,000-character paragraph below the bullets that carried half the listing's narrative weight. With A+ Content (a Brand Registry-gated feature) Amazon replaces the description with visual A+ modules on almost every surface a shopper actually sees. That makes the field feel optional. It isn't — it's just been pushed into a set of fallback states that most listing owners stop checking.

Where the description still shows up

Even with A+ live, the description text continues to render or contribute on several surfaces:

• Listings without A+ Content. Every third-party seller who isn't Brand-Registered, every generic ASIN where Amazon doesn't have an approved A+ template, and every product where A+ moderation is still pending. On these PDPs the description is the only long-form text after the bullets.
• The Amazon mobile app, in fallback states. When the A+ blocks fail to render — slow connection, older app version, certain country marketplaces with delayed A+ rollouts — the description renders in their place.
• Amazon's internal search-indexing. Every word in the description field is searchable. It's a lower-weight index than the title or backend search terms, but it still contributes to long-tail relevance.
• Affiliate and partner surfaces. Sites that pull product data through the Product Advertising API often use the description field as the body copy on their embed card, because the A+ HTML isn't exposed via API.
• The print-friendly view Amazon offers to some business buyers in B2B-eligible categories.

The character and formatting limits

The hard limits Amazon enforces inside Seller Central and the flat-file product_description field:

• 2,000 characters maximum, including spaces. Anything longer is truncated server-side and you'll never see the cut text on the live page.
• No HTML tags. Amazon strips almost all HTML on entry. The two exceptions Amazon historically tolerated — <br> for line breaks and <p> for paragraphs — are no longer reliable; assume all formatting will be flattened.
• No emojis, no special Unicode characters outside the standard Latin set. Most categories reject submissions containing them.
• No promotional language ("sale", "free shipping", "best on Amazon"), no contact information, no URLs to off-Amazon pages. These trigger automated moderation rejections.

How to write it for the audiences that see it

Treat the description as serving three audiences in parallel:

1. The shopper on a fallback surface. Plain, scannable prose. Two short paragraphs of 4–6 sentences each. Lead with the single most important benefit, follow with the most likely use case, close with the spec or compatibility note that prevents returns.
2. The Amazon search algorithm. Repeat the key product attributes (size, material, capacity, compatibility) in natural sentences — not as a comma-separated keyword dump. The algorithm indexes phrases in context, and stuffed lists frequently get demoted as low-quality content.
3. The affiliate-site visitor. The first 200 characters of the description are what most affiliate cards display. Front-load the brand, the product type, and the standout feature, so the truncated preview still sells.

Target length and pacing

Aim for 1,000–1,500 characters in production. Below 800 you're leaving SEO surface area on the table and the affiliate-card body looks unfinished. Above 1,800 you risk client-side truncation on the mobile fallback view, and the description starts competing with itself for the shopper's attention span. Two paragraphs of 500–700 characters each is the consistently strong shape.

The fallback-story rule

Imagine a shopper landing on the listing on a surface where A+ is hidden — slow mobile data, an older Amazon app build, an unsupported country marketplace, a third-party comparison site pulling via the Product Advertising API. Can the description alone, with nothing but the title, bullets and main image around it, still sell the product? If the answer is no, rewrite. The fallback case is more common than most analytics dashboards reveal, and listings that fail it quietly lose 5–15% of their potential conversion to surfaces nobody is actively monitoring.

Seller vs Vendor — same field, different ownership

Sellers edit the description directly in Seller Central or via the inventory file upload, and the change goes live within minutes. Vendors submit description copy through the New Item Setup form or via cs:// catalogue feeds, and Amazon's catalogue team may rewrite it to match Vendor Central style guides without warning. Vendors should treat the description as a copy recommendation rather than a guaranteed live string, and audit it monthly against what's actually rendering on the PDP.

What to take into the next episode

The description handles the fallback case. The next episode covers what hides the description on every primary surface: A+ Content — the module library, the image specifications per module type, the order that converts, and the comparison-table module that quietly cross-sells (or cannibalises) your own catalogue.