Fields in an enrichment run
A single enrichment run can produce content across four field families. This page lists each field and explains what it’s for, so you can decide what to include in your config.
You don’t have to generate everything. Your generation config determines which fields a run produces, and since usage counts every item you send, generating only the fields you’ll actually use is the point.
Branded copy
The language that sells the product. This is the core of enrichment and where most merchants start.
SEO and discovery metadata
Content aimed at search engines and on-site discovery rather than at the shopper directly.
Page titles and meta descriptions are where SEO enrichment earns its keep, so that’s where the emphasis sits. Tag fields are not written into a meta keywords tag — search engines have ignored those for well over a decade, and spending enrichment on them would be waste.
AEO — answer engine optimization
Content structured so AI assistants and answer engines can understand and cite your products. This is the newest family and the reason enrichment matters beyond traditional search.
Marketing channel fields
Copy shaped to each destination’s conventions and constraints. This is FDX Enrichment’s breadth advantage: one run, content formatted for every channel your feed reaches.
Additional marketplace channels including eBay and Walmart are available in the FDX field set.
What appears alongside the generated content
Every enriched product also carries context so you can review it. These aren’t generated — they’re what makes the review possible.
- Original product data — your source values, kept beside the enriched output so you can always compare.
- Product identity — product name, ID or SKU, and brand.
- Product images — the imagery available for the product, which also informs generation and evaluation.
- Enrichment name and date — which run produced this content.
- Approval status — where the product stands: pending review, accepted, rejected, or edited.
Not included today: attribution
Enrichment generates language. It does not perform attribution — inferring structured attribute values like gender, color, size, or material, or assigning products to a taxonomy category.
Those fields exist in the broader field catalog and they matter, but they belong to a different job with a different standard: copy is judged on quality, while a structured attribute value is either exactly right or it breaks your filters and channel compliance. Attribution is not part of data enrichment today — it is on the roadmap.
What that means in practice right now: if your source data doesn’t state a material, enrichment won’t infer one, and it won’t write copy claiming one. See What makes good source data for how to close those gaps in the meantime.
Choosing your fields
A few patterns that work:
- Storefront-first — branded copy plus meta descriptions and alt tags. The fastest visible win on your own site.
- Ads-first — product titles plus the channel fields for the destinations you actually spend on.
- AEO-first — AI description, conversational Q&A, and intent Q&A, aimed at the surfaces that are growing fastest.
- Everything — appropriate once a config has proven itself, and the reason the breadth exists.
Where each of these lands in your feeds is covered in Where enriched fields go.