UGC in Amazon A+ Content: what's allowed, what isn't

Why customer content earns its place in A+

Start with the honest version of the numbers. Amazon's own Seller Central guidance says A+ Content can help increase sales by up to 8% for basic modules and up to 20% for Premium A+. Those are Amazon's aggregate figures for adding A+ Content at all, across all creative types; Amazon does not publish a UGC-specific lift, and you should distrust anyone who quotes one as if it were Amazon's.

The case for using customer content inside that band comes from everywhere else we can measure. Stackla's consumer research has consistently found shoppers rate authentic customer content as more influential on purchase decisions than brand-produced creative. On our own side of the fence, the storefront galleries Idukki runs for customers showed a conversion lift of roughly 20% in VWO-run tests on Idukki customer storefronts. That is an on-site number, measured on brand websites rather than on Amazon, and I am careful to label it that way. But the mechanism it demonstrates (shoppers trust evidence from people like them more than they trust a studio) does not switch off when the shopper happens to be on amazon.com.

A+ is where that evidence can legally live on Amazon. The image block, the bullets and the title are tightly templated. The A+ band is yours.

The exact prohibitions

Amazon's A+ Content guidelines are enforced by human moderators and they reject entire submissions over single violations. The rules that matter most for UGC:

• No customer review quotes, from anywhere. Not from your website, not from a third-party platform, and not even reviews left on Amazon itself. A pull-quote over a hero image is an automatic rejection.
• No star ratings or rating graphics. A five-star row rendered into an image is treated the same as a quoted review.
• No social handles, usernames or platform logos. The Instagram handle burned into the corner of a creator video, or a TikTok watermark, fails moderation. The content is fine; the branding on it is not.
• No watermarks of any kind, including your own agency's.
• No pricing, discount or promotion language. "20% off this week" has no legal home in A+.
• No calls to action that reference purchasing ("buy now", "add to cart"), and no time-sensitive claims.
• No contact information or links that point anywhere, on Amazon or off it.

Read that list again and notice what is not on it: the customer photo itself. A rights-cleared image of a real person using your product, cropped clean with nothing overlaid, is entirely acceptable. Nearly every rejection we see comes from decoration, not from the underlying content. The habit brands carry over from social media (credit the creator on-image, add the stars, add the quote) is precisely the habit Amazon prohibits.

Module dimensions worth knowing

A+ modules take fixed image sizes, and UGC rarely arrives at them. A vertical 9:16 TikTok frame does not become a 970×600 header banner without deliberate cropping, which is why "we'll just reuse the social assets" plans stall at the export step. The sizes you will use most:

The practical implication: pick UGC for A+ by crop survival, not just by how good the original post looks. A beautiful vertical video whose subject sits dead-centre survives a 970×600 crop; one whose action happens at the top edge does not.

The boundary nobody should sell you past: reviews stay put

A recurring question, and the answer deserves to be unambiguous: no tool can import your website reviews, Google reviews or any other external reviews into Amazon's review system. Amazon's community guidelines prohibit it, there is no API for it, and any vendor implying otherwise is describing something that will end badly for your seller account. Review syndication in the Amazon context means one thing only: the imagery and video your customers created can be formatted into A+ modules, Brand Story, Brand Store pages, Amazon Posts and ad creative. The reviews themselves stay on the platform where they were written.

The rights dimension: consent that names Amazon

Here is the part most brands discover late. A creator who replied "yes, of course!" to a rights request for your website gallery has consented to your website gallery. That consent does not automatically extend to Amazon A+ modules, and it certainly does not extend to Sponsored Brands Video running as paid media. Usage scope is the substance of a rights grant, not a technicality: the creator agreed to a context, and Amazon is a different context with different commercial weight.

The clean way to handle this is to name the surfaces in the original request: on-site galleries, email, Amazon listing content, and paid social or retail media, each as an explicit yes or no. Idukki's rights requests work exactly this way, and the rights ledger records the scope per asset. When an export for Amazon is assembled, assets whose consent covers only on-site display are excluded automatically rather than relying on someone remembering. Retro-clearing content one DM at a time is possible, but it is slow, and the best assets are always the ones you cleared properly the first time.

What Idukki automates, and what it hands you as a checklist

The tedious parts of this workflow are mechanical, so we made them mechanical. Collection pulls customer photos and video from the social platforms and review sources you already connect. Rights requests go out with Amazon named in the scope. AI tagging matches assets to products, an ASIN map connects your catalogue to your listings, and the compliance engine screens every asset for the automatable violations: overlaid text that looks like a quote or rating, detectable watermarks and platform logos, handles in frame, promo language in module copy, and dimensions that do not fit the target module. Anything flagged is held with a reason instead of shipping.

The judgment calls stay human, and we are explicit about which ones: claims that need substantiation, category-specific restrictions, and whether an image shows the exact variant the ASIN sells. Those arrive as a short checklist attached to the export, pre-filled where automation can be confident. The output is an Amazon Pack per ASIN: rendered files at module spec, named sanely, with the compliance report and rights scope attached, ready for whoever owns your Seller Central login. The judgment stays with you; the drudgery does not.