# From Shopify to Amazon: one UGC pipeline, every storefront If UGC already runs on your storefront, the expensive parts of the Amazon problem (collection, rights, product tagging) are already solved. The honest accounting: what transfers untouched, why ASIN mapping is the only genuinely new step, and where Amazon's assets-not-embeds model changes the rules. By Rohin Aggarwal · 2026-08-13 The question arrives about once a week now, usually from a brand that has run our galleries on Shopify for a year: can the same content go on our Amazon listings? The answer is yes, and the interesting part is how little new machinery it takes. Almost everything built for the storefront turns out to be the hard part of the Amazon problem, already done. **Quick answer** - The pipeline that powers on-site UGC (collect, rights, product-tag, curate) is the same pipeline Amazon surfaces need. It does not need rebuilding; it needs one extension. - The genuinely new step is ASIN mapping: connecting the product catalogue your content is tagged against to the Amazon listings those products sell under. - The delivery model differs completely. There is no widget JavaScript on Amazon; syndication means rendered assets at module spec published through Seller Central, not embeds. - Rights scope is the gotcha: consent gathered for on-site galleries does not automatically cover Amazon, so the extension starts with the rights request template, not the export button. The pipeline argument fits in one sentence: the expensive parts of putting customer content on Amazon are collection, rights and product tagging, and if UGC runs on your Shopify storefront today, all three already exist. What follows is the honest accounting. Some of the machine transfers untouched, one step is genuinely new, and in a few places Amazon is a different animal and pretending otherwise causes rework. ## What carries over untouched Collection transfers whole. The social connections pulling Instagram, TikTok and YouTube content into your library, the review-source connections, the hashtag and mention monitoring: none of it knows or cares which surface the content ends up on. Curation transfers with it: the moderation habits, the AI tagging that matches content to products, the labels your team already uses. Product tagging is the quiet workhorse here, because content tagged to a product is one lookup away from content tagged to an ASIN, which is the form Amazon needs. Rights transfer structurally but not automatically, and this deserves its flag before any machinery discussion. A grant scoped to your storefront covers your storefront. Amazon usage needs Amazon named in the scope, ideally in the original request. The mechanics are covered in [the A+ compliance guide](/blog/ugc-in-amazon-a-plus-content); the summary is that the extension to Amazon starts with your rights template, not with an export button. Brands that have been requesting broad, surface-named scopes all along discover their back catalogue is already Amazon-ready. Brands that requested narrowly get to choose between retro-clearing and starting the clock on new collection. ## ASIN mapping: the one genuinely new step The single piece of net-new configuration is the ASIN map: the table connecting products in your catalogue to the Amazon listings those products sell under. Your storefront reaches products by SKU or handle; Amazon reaches them by ASIN, with a parent-child variant structure that does not always mirror how your Shopify variants are organised. Building the map is a one-time exercise (import, match, review the ambiguous ones), and maintaining it is an occasional one, triggered by catalogue changes rather than by content. Once the map exists, every piece of product-tagged content in your library inherits an Amazon destination for free. That is the entire trick: tag once against your own catalogue, and let the map fan the same tag out to every storefront that sells the product. ## What changes: assets, not embeds The delivery model is where storefront habits must be unlearned. On Shopify, Idukki is a widget: a script renders live galleries, content updates without republishing, clicks are measured inside the embed. Amazon permits none of that. There is no third-party JavaScript on a listing, no live feed, no runtime anything. Syndication to Amazon means rendered static assets: images and video cropped to module spec, uploaded through Seller Central into A+ modules, Brand Story, your Brand Store, Amazon Posts and ad creative, then held until Amazon's moderation approves them. Publishing is a deliberate act with a review cycle, not a save button. The practical consequences follow from that. Updates are republishes, so "fresh content weekly" means a production rhythm rather than a feed setting. Selection standards rise, because a static asset cannot lean on the surrounding gallery for context: each image has to survive its crop and carry its own evidence. Assets, not embeds, is the phrase we use internally, and it changes which content wins. The vertical clip that shines in a storefront reel may die in a 970×600 A+ header, and an unremarkable square photo may be the best Posts candidate you own. ## The export: one library, every storefront Run end to end, the extended pipeline reads: collect as you already do, request rights with every surface named, tag to products as you already do, map products to ASINs once, then export per destination. The [Amazon Pack](/amazon) is the export format we build per ASIN: A+ imagery at module dimensions, Brand Story crops, Posts candidates and ad cuts, with the compliance screen run and the rights scope attached. Your storefront galleries keep running exactly as before; Amazon becomes a second consumer of the same library rather than a second content operation. Brands keep asking what the catch is, and the honest answer is scope discipline: the pipeline only fans out cleanly if rights were requested broadly and tagging was done properly. Both are habits the storefront work should have built already. The rest is just timing. **The practical decision:** If UGC runs on your storefront, you are one ASIN map and a rights-scope check away from Amazon. Keep collection, curation and tagging exactly as they are, learn the assets-not-embeds delivery model, and let each storefront consume the same library. ### FAQs **Q: Do I need a separate UGC workflow for Amazon?** A: No. Collection, curation and product tagging carry over from your storefront pipeline unchanged. The additions are an ASIN map connecting your catalogue to your listings, rights scope that names Amazon, and an export step that renders assets to each Amazon surface's spec. **Q: What is ASIN mapping?** A: The table connecting products in your own catalogue (reached by SKU or handle) to the Amazon listings those products sell under (reached by ASIN, with parent-child variants). Once built, every piece of product-tagged content inherits an Amazon destination through the map. **Q: Can the Idukki widget run on my Amazon listing?** A: No, and no widget can: Amazon does not allow third-party JavaScript on listings. Syndication to Amazon means rendered static assets published through Seller Central into A+ modules, Brand Story, Brand Store pages, Posts and ad creative. **Q: Does my existing on-site rights consent cover Amazon?** A: Not unless the request named Amazon as a surface. Consent is scoped to the usage the creator agreed to, so audit scope per asset before exporting; assets cleared only for on-site display should be excluded automatically rather than by memory. ### Sources - Amazon Seller Central, A+ Content publishing and moderation — assets are submitted and reviewed before going live; no third-party scripts on listings - [Idukki: Amazon syndication (product)](/amazon) — the Amazon Pack export described above - [Idukki: UGC in Amazon A+ Content](/blog/ugc-in-amazon-a-plus-content) — module dimensions and the rights-scope rule in full --- Canonical: https://idukki.io/blog/shopify-to-amazon-one-ugc-pipeline Tags: amazon, shopify, syndication, asin mapping, rights management, ugc