Researching Amazon's own rules — the constraints every text field has to respect.

Q&A analysis told you what shoppers ask. Review analysis told you what they keep saying once they own the product. Episode 03 turns to the third research stream that has to be on the desk before Module 8 starts drafting: Amazon's own published rules. Every text field on a detail page — title, bullets, description, A+, Brand Story, backend keywords, images — sits inside a category-specific constraint set Amazon documents publicly and updates on its own schedule. Writing without that constraint set on the desk is how rejected uploads, suppressed listings, and quiet ranking penalties happen.

Two layers of rules, not one

Treat Amazon's published rules as two stacked layers:

1. The general ruleset. The rules that apply to every category — what "Amazon's Choice" considers, how the SERP is composed, what counts as a complete product detail page, the generic image standard, the backend keyword policy.
2. The category-specific ruleset. A second, narrower layer that lives inside the category's flat file and style guide — additional required attributes (for apparel: material, heel height, care instructions; for grocery: nutritional panels; for electronics: power and certification data), category-specific title patterns, and image rules that override the generic ones.

Both layers have to be researched. The first is easier to find and changes less often. The second is where most of the costly mistakes happen, because sellers assume the general rules are the whole picture and skip the category sheet.

Where Amazon publishes the general rules

The canonical entry point is Seller Central's help page for how products are presented in the Amazon store — usually surfaced under "Amazon presents" or the equivalent local-market wording. The page is worth reading top to bottom on a schedule, because Amazon edits it without announcement. The headline statements are predictable — fast shipping, competitive price, in-stock — but the page also spells out the badge logic (the small product highlights that appear on the SERP), the structural order of a detail page (image, price, bullets, description, A+, Brand Story), and the implied priority order of how shoppers consume it.

Read the order itself as a rule. The fact that bullets sit before the description and A+ sits below the fold is not a layout accident; it is Amazon's own published statement of where it thinks attention goes. That ordering should shape how Module 8 sequences its work and how content priorities are triaged when a SKU is being optimised in stages.

Image rules: generic baseline, then category overrides

The generic image rules are non-negotiable: the product must be recognisable, the main image is a photograph (not an illustration), the product fills at least eighty-five percent of the frame, it is shown in full, and the background is pure white. From there, the rules narrow per category — what is allowed in the secondary slots, whether lifestyle imagery can appear at certain positions, whether infographics with overlay text are tolerated.

Amazon publishes detailed image requirements with examples per category. Read them for the slot you are actually filling, not the slot you wish existed. The most common policy violations come from a designer following the generic guide and ignoring the category-specific override — text overlays in the main image, props that imply contents that are not included, comparison shots in slots that do not permit them.

Bullets: the rule is "be aware they may not all show"

Amazon is explicit about something most sellers forget: the platform does not always display every bullet point. Mobile views, certain category layouts, and ongoing UI experiments can collapse, truncate, or suppress later bullets. The implication is direct: write the most important information into bullets one, two, and three, and treat four, five, and beyond as "still required, but assume some shoppers never see them". Module 8 Episode 06 will turn this into a concrete bullet-ordering rule; Episode 03 is where the constraint is named.

Category-specific attribute fields

Some categories expose attribute slots that simply do not exist elsewhere. Apparel and shoes are the classic example — heel height, material composition, care instructions, fit type, season. These fields are not optional decoration; they feed both the filtered SERP (the left-rail filters shoppers actually click) and the structured-data layer Amazon uses to match queries. A jacket missing its insulation type is functionally invisible to the shoppers who narrow their search by that attribute.

The takeaway is mechanical: pull your category's attribute list before you start writing, and make sure the brief explicitly covers every required and every recommended field — not just the ones that feel relevant.

Search terms: the published budget and the published rules

Backend search terms have their own published ruleset, and it is much stricter than most sellers treat it. For Germany the documented budget is fewer than 250 bytes (other marketplaces, notably the US and Japan, use different limits). The rules also explicitly tell you what to do — fill the field with synonyms, spelling variants, abbreviations and alternative product names — and what to avoid: repetition of words already in the title or bullets, brand names you are not entitled to use, promotional language, subjective claims, punctuation that the tokeniser ignores anyway.

Two of Amazon's own warnings inside that page deserve to be quoted in any internal brief. First, Amazon "reserves the right not to use all submitted keywords for product retrieval" — under the labels of search efficiency, manipulation prevention, and irrelevance. Second, the tokeniser does not learn invented words on the fly: stuffing a backend field with a fantasy term to test whether you can rank for it is wasted budget, because the algorithm has no prior signal that the term exists. Both warnings bound the field's realistic ceiling.

The category-specific flat file is the master constraint sheet

Sitting above everything is the category-specific flat file (the inventory template you download from Seller Central for your exact product type). Earlier modules walked through where to find it and how to fill it; in the Module 8 context the flat file plays a different role — it is the single document that encodes every field-level rule that applies to your SKU. Maximum character counts per field, allowed values per attribute, required vs optional, the category-specific title pattern Amazon expects, the bullet-count limit, the variation theme rules.

Two practical consequences:

• Use the specific template for your product type, not the generic catch-all template. A generic template will accept your upload but will omit category-specific required fields and quietly weaken the listing.
• When a later episode talks about titles, bullets, or attributes "in general", verify against your downloaded flat file before applying the advice. The general guidance is right for most categories; your category is one of the exceptions roughly as often as it isn't.

If you have not yet downloaded the flat file for your ASIN, stop and do that now — every remaining episode in Module 8 assumes it is on the desk.

Refresh schedule: this is not a one-time read

The single most underrated rule about Amazon's rules is that they change. The image policy, the search-term byte budget, the attribute pipeline, the bullet display logic — each gets edited on Amazon's own cadence with no notification. Put a recurring slot in the calendar (quarterly is the minimum; monthly for active sellers) to re-open the published pages, diff against last time, and update the internal brief. Module 8's output decays without that maintenance.

What this episode hands off

Episode 03's output is a per-category constraint sheet that travels alongside the Q&A themes from Episode 01 and the review themes from Episode 02. It names the title pattern, the bullet count, the character limits per field, the required attributes, the search-term budget, the image rules and the category-specific overrides. With that sheet, the keyword work from earlier modules, the Q&A analysis, and the review analysis on the desk, Episode 04 can finally consolidate everything into the foundation document that the rest of Module 8 writes from.