Product Feed

A product feed is a CSV, XML, or API stream containing product IDs, titles, descriptions, images, prices, and availability — the source of truth for shopping and dynamic ads. Production concepts decide whether creative can be made at catalog scale or only for hero moments. Anything that requires a person to open a canvas per SKU stops working around the fortieth product. The brands that ship the most variants treat production as a system of templates, rules and specs rather than a series of one-off files. Read it next to Dynamic Product Ads (DPA), sku, gtin.

Define it once, then apply it everywhere. Lock type ramp, palette, logo placement, offer treatment and legal lines in a shared brand system, and build templates that accept the product feed as input. Every export should already respect the placement's safe zones so nothing needs a manual crop after the fact.

Quality control is checkable, not subjective: does the asset meet the platform's ratio and file requirements, does key content sit inside the safe area, is text legible at thumbnail size, and does the product read in the first frame? Run that checklist before spend, because rejections and silent crops cost more than the render did. Why this matters commercially: The feed is the substrate of ecommerce advertising. Broken feed = broken DPAs, disapproved products, and missing revenue.

In Xeli this is a rule an agent enforces, not a note in a brief. Templates read the catalog, respect the brand system, and output every required ratio for every SKU at ad-ready resolution — so a 400-product drop becomes a queue to approve rather than a month of files. In the context of creative & production, that means the concept stops being something a person re-applies by hand every campaign and becomes a rule the system enforces on every asset it produces.

The recurring problems are predictable: not validating feed after every sync; using product photos with no lifestyle context; missing gtin or mpn attributes that block shopping ads. Each of these is a process gap rather than a knowledge gap — which is why the fix is usually a checklist, a template or an automated rule instead of more training.