Checks 1–3: is the title compliant, are the bullets complete, is there a description?
The first three checks are the text customers and Amazon's search read. The title must be inside the category's length limit, free of promotional phrases, symbols and all-capital words, and must carry the attributes buyers search by: brand, product type, key attribute, size or count. The bullets must all be filled, each stating a specific attribute or use, not a slogan. The description must exist and must not duplicate the bullets word for word.
- Title: open the listing; verify length is inside the limit and the brand, type and key attributes are present.
- Bullets: verify every bullet field is filled with a specific fact and none is empty or a slogan.
- Description: verify it exists, reads as prose about the product, and does not repeat the bullets verbatim.
Checks 4–6: do the images meet the rules, are identifiers valid, are category attributes filled?
The next three checks are the data-quality rules that cause suppressions. The main image must show the product on a pure white background with no text, graphics, borders or props, at or above the minimum size; additional images may show use and scale. Product identifiers must be valid and match the product. Every attribute the category requires must be filled on every variant; a single empty size on one child listing is enough to suppress it.
- Images: view the main image; verify pure white background, no overlays, and size at or above the minimum.
- Identifiers: verify the identifier validates and matches the physical product's packaging.
- Attributes: open each variant; verify every required attribute for the category is filled, with no empty fields.
Checks 7–9: are variations consistent, is the price above the floor with the Buy Box known, is stock synced?
The structural and commercial checks come next. Variations must be consistent: every child has the variation attribute filled, the parent groups the right children, and no child is orphaned. The price must be at or above the owner's floor for the SKU, and the Buy Box status must be known with its cause when the store does not hold it. Stock on the marketplace must match the store's stock so that a sale on one does not oversell the other.
- Variations: verify every child shows its size or colour and belongs to the right parent; look for children not visible on the parent page.
- Price and Buy Box: verify the price is at or above the floor and note whether the store holds the featured offer and, if not, why.
- Stock: compare marketplace available quantity with the store's; verify they match or that the sync rule explains the gap.
Checks 10–12: are reviews and questions answered, do ad terms convert at a margin, is the listing free of warnings?
The last three checks are about interaction, spend and health. Customer questions should be answered from product data, and reviews that raise a product issue should be read as signal. Sponsored-ads search terms should be checked for spend against conversions and the SKU's margin after fees, with terms that spend and never convert negated. The listing should carry no suppression and no quality warning in Seller Central's listing views.
- Q&A and reviews: verify open questions are answered and note any review theme that points at a product or listing problem.
- Ads terms: read the search term report; verify terms with spend and no conversions are negated, and advertised SKUs have a positive margin after fees.
- Health: open the suppressed and listing quality views; verify the listing appears in neither, or note the field named.
How should the checklist be run across a catalog?
The checklist should be run first on the SKUs that carry the most marketplace revenue, then by parent listing, because variations share failures: a missing attribute on one child is usually missing on its siblings. Record each check as pass or fail per listing and keep the record; it is the baseline for the next audit and the evidence for which fixes were worth the most. Re-run after any rule change announced in Seller Central, because rules apply retroactively.
Failures suggest fixes, and fixes should come from product data. A missing attribute is filled from the product sheet; an image that fails the rule is replaced from the store's own assets; a title over the limit is shortened without dropping searchable attributes.
What does the Marketplace FTE add to a manual audit?
The Marketplace FTE on ftes.ai runs these twelve checks on every listing on every marketplace daily, ranks failures by revenue at risk, and proposes each fix in Approvals with the failing field named and the corrected listing drafted from product data and checked against the rule. Price is checked against the floor the owner set; stock against the store; ad terms against the margin after fees. A rule change that suppresses a listing overnight is in the next morning's brief.
What it does not add is a price below the floor, a claim the product sheet does not support, or a reply to a sensitive review. Those are proposals for a person, or escalations, and the floors and caps never move on their own.