Amazon Ads REC AI prompts: ASIN checks before ads repeat weak product claims

Amazon Ads' June 22, 2026 update says Responsive eCommerce Creative can automatically build and optimize display ads from products, product detail pages, Brand Stores, previous campaigns, uploaded videos, and AI-generated image or video assets. Amazon also says REC prompts are expected to expand beyond Amazon in July, using product-specific questions that can send shoppers into Alexa for Shopping.

For US sellers, and for UK sellers advertising through Amazon DSP or managing Amazon.com and Amazon.co.uk catalogs, the recovery risk is not only ad performance. The risk is that a weak product claim, wrong compatibility phrase, unsupported lifestyle image, unauthorized logo, or confusing variation detail becomes automated creative and then creates an ad rejection, ASIN issue, IP complaint, or product-detail-page dispute.

Short answer: treat the detail page as the source file

Start with the ASIN, not the campaign. REC can pull meaning from the product detail page and related brand assets, so a small listing weakness can become a larger advertising weakness once the creative is reused across placements.

• Export ASIN, SKU, marketplace, brand, product type, parent-child family, advertised products, destination page, Brand Store page, and campaign name.
• Screenshot title, bullets, images, A+ Content, Brand Store sections, variation structure, product claims, compliance attributes, and current offer status before enabling REC or AI creative.
• Flag words that carry legal, safety, compatibility, origin, medical, environmental, warranty, age, or performance meaning.
• Separate Amazon.com and Amazon.co.uk records because language, restricted-category, claim, and ad-placement review can differ by marketplace.
• Keep an edit log that shows who changed the listing or asset, why the change was made, and whether the ad campaign was refreshed afterward.

Review prompts before they become customer questions

Amazon says prompts can draw from product detail pages, Brand Store content, and campaign data. That makes the prompt review different from normal keyword review. The seller has to ask what a shopper may be invited to ask and whether the source page can support the answer.

• Test likely prompt subjects: fit, size, material, ingredient, compatibility, battery, warranty, age range, use case, pack count, country of origin, and comparison wording.
• Remove or correct claims that sound stronger in question form than they are on the actual product file.
• Do not let a prompt imply that an accessory is made by, endorsed by, or equivalent to a protected brand unless the evidence and listing language support that position.
• For regulated or sensitive products, compare every prompt topic against the compliance file and restricted-products route before increasing spend.
• If Alexa for Shopping or another automated answer points to the wrong product detail, preserve screenshots and campaign records before editing the page.

Separate ad moderation from listing recovery

An ad rejection is not always an ASIN deactivation, but repeated or serious ad-policy issues can still create a broader account problem. The response should name the route Amazon is actually reviewing.

• Use ad moderation cleanup when the issue is image quality, copy, landing-page mismatch, unsupported promotion wording, or creative asset status.
• Use ASIN Listing Deactivation when the ad exposed a product identity, variation, catalog, detail-page, or offer-status problem.
• Use Product Detail Pages Infringement when the advertised product does not match the page, bundle, condition, compatibility claim, or package customers saw.
• Use Intellectual Property when the problem is trademark use, logo rights, brand authorization, protected images, rights-owner complaints, or misleading affiliation.
• Use Restricted Products when the creative or prompt repeats a claim that triggers safety, age, medical, environmental, ingredient, battery, or category-compliance review.

Build a REC evidence packet before scaling spend

The useful packet is small. It should let someone reconstruct what REC was allowed to read, what it generated, where it ran, and what Amazon said if the ad or ASIN was blocked.

• Save the REC setup, creative previews, AI-generated assets, uploaded videos, Brand Store source pages, product detail pages, and selected ASIN list.
• Preserve moderation status, rejection reasons, support case IDs, campaign change history, and the date each asset was approved, rejected, paused, or removed.
• Map each claim in the creative to the product detail page, packaging, test report, authorization letter, supplier record, or compliance document that supports it.
• Keep a marketplace column for US, UK, and any third-party publisher placement so off-Amazon delivery does not blur the source of the issue.
• If a case opens, attach the narrow record first instead of sending a broad ads, listing, compliance, and IP bundle all at once.

The practical closing test is whether the seller can explain one clean line: this ASIN fed this creative, these claims came from these source records, these assets were authorized, this prompt was accurate, and this Amazon route is the one that should review it. If that line is still weak, return to the ASIN listing owner context before automated advertising turns a small page issue into a harder recovery case.