A+ moderation — rejection reasons, rebuild discipline, queue control.

Every A+ Content project, every A+ Premium upgrade, every Brand Story carousel passes through the same Amazon content-moderation queue before it goes live. The first pass is usually the only one anyone sees — but when a project comes back rejected, the response from most teams is to guess at what broke, edit something obvious, and resubmit. The honest version is that Amazon's rejection codes map to a small, recurring set of issues, and once the map is clear, rebuild becomes a 30-minute job rather than a multi-day back-and-forth.

The eight rejection reasons that recur

1. Unsubstantiated superlatives. "#1", "best-selling", "leading", "the most", "guaranteed", "100% effective", "clinically proven" — anywhere in copy, image overlays or alt-text. Amazon's bar is that the claim must be substantiable on the destination PDP itself, not in marketing material elsewhere. Most rejections here are "#1 in [category]" claims that can't be tied to a current BSR position on that ASIN.
2. Third-party trademarks and retailer logos. "As seen on QVC", "available at Walmart", "winner of the Reddot Award", Costco / Target / Tesco logos embedded in lifestyle imagery, certifications shown without a verifiable badge. Even your own retail partners' marks trigger rejection inside Amazon's surface.
3. Off-platform references. URLs, QR codes, email addresses, phone numbers, social handles, "visit our website", "scan to learn more". Anything that routes the shopper off Amazon is removed at moderation.
4. Promotional pricing and time-limited claims. "Save 20%", "limited offer", "free with purchase", "ends Friday", currency symbols anywhere on imagery. A+ is treated as evergreen content; price and promotion live on the offer level.
5. Customer reviews or rating quotations. "Rated 4.8 stars", "★★★★★ review from John", screenshotted Amazon reviews used as image content. Even your own genuine reviews can't be quoted inside A+.
6. Text overlaid on the main hero image that duplicates the title. Particularly common on Premium full-bleed hero modules — the overlay copy ends up being the same brand-plus-product-name string already in the title and is flagged as redundant/promotional. Amazon allows benefit copy, not title duplication.
7. Lifestyle imagery without the actual product visible. A mood shot of a kitchen without the product on the counter, a landscape shot without the camera in frame. A+ is product content; the product has to appear in at least one frame of every image module.
8. Comparison-chart cells with marketing copy instead of attribute values. "Best value!", "our top pick", "★★★★★" in chart cells. Comparison cells take short factual values (numbers, materials, yes/no) — anything else is rejected on the comparison module specifically.

The rebuild discipline that earns approval on pass two

When a project comes back rejected, Amazon returns the rejection reason — usually a numbered code with a short description — against the specific module that triggered it. The discipline that gets the project through on the second submission:

• Read the rejection reason against the module, not the project. The rejection is module-scoped; the other modules in the project are usually fine. Don't rebuild the whole stack.
• Map the reason to the recurring list above. 90% of rejections land in one of the eight patterns. Identify which one, then fix the exact element it points to — not "tighten the copy".
• Re-read every other module against the same rule. If a superlative triggered the rejection in Module 3, the same superlative is usually somewhere in Module 6. Fix all instances of the pattern across the whole project before resubmitting — second-pass rejections on the same pattern in a different module cost another full moderation cycle.
• Re-submit without unnecessary edits. Editing other modules "while we're in there" extends the moderation pass and re-opens previously-approved content for re-review. Touch only the rejected module unless a cross-cutting fix is required.

The moderation timeline that's actually realistic

Amazon publishes a 24–72 hour SLA on A+ moderation. The realistic timeline:

• Off-peak (January–September, Tuesday–Thursday submissions): 24–48 hours on standard A+, 48–72 on Premium and Brand Story.
• Pre-peak (October to early November): 3–5 days as the queue fills with seasonal updates.
• Peak (mid-November through December, Prime Day week): 5–10 days, occasionally longer. Resubmissions sit behind first-time submissions in the queue.
• Friday-afternoon submissions: add a day in any season — Saturday/Sunday moderation throughput is lower.

Queue-control tactics for peak season

• Freeze the A+ stack 30 days before the peak event. Any A+ change submitted inside that window risks getting stuck behind the wider queue and going live after the event. Tactical promotions live on the offer level, not in A+.
• Batch ASIN mapping changes separately from copy changes. Mapping a new ASIN to an already-approved A+ project doesn't go through full moderation — it propagates in hours. Copy or image edits on an approved project trigger a fresh pass. Separating the two keeps the fast operation fast.
• Stage the rollout for brand-wide changes. A Brand Story edit that propagates to every ASIN simultaneously is high-risk during peak. Either ship it three weeks pre-peak with full bake time, or wait until the post-peak quiet period.
• Open a Brand Specialist case for stalled critical changes. If a project has been "Submitted" for more than 7 days on a non-Q4 schedule, a polite case referencing the project ID and the business reason usually surfaces it. Don't open cases on routine submissions — it costs queue-position goodwill for the cases that do matter.

What this hands off to the next episode

Standard A+, Premium, Brand Story and the moderation playbook together cover the brand-controlled visual surface on the listing. The next episode steps back to the writing layer — the editorial review pass that catches problems before they reach Amazon's queue at all.