Editing enriched content
Enriched content isn’t locked. Once you accept it, you shape it with the same tools you already use everywhere else in FDX — no new concepts to learn.
Enriched content behaves like raw data
Enrichment applies its output as a raw data override. That’s the whole trick, and it’s why editing is straightforward: the enriched value sits in the raw layer, so every tool that works on raw data works on enriched content too.
That gives you three ways to change it:
- Transformers — apply a rule to enriched fields the same way you would to any raw field. Append a size, enforce a character limit, standardize a term across a whole category.
- Transformed data overrides — change a specific product’s value directly. This is the tool for “this one title needs two words changed.”
- The feed build process — your normal build and export logic runs over enriched content exactly as it does over imported data.
Enrichment writes to new, dedicated fields in your database, applied as a raw data override — your imported source data is never replaced, and you can always compare what came in against what enrichment produced. Because the enriched value sits in the raw layer, everything downstream can act on it: transformers, transformed data overrides, and the feed build process.
Which tool for which job
One product needs a tweak
A pattern needs fixing
The voice is wrong across the board
Use a transformed data override on that product’s field. Fastest path when the copy is 90% right and you just want to adjust a word or a claim.
Edit downstream for exceptions. Fix the config for patterns. If you find yourself writing the same override more than a handful of times, that’s a config change asking to happen.
Seeing what changed
Because the original imported value is never replaced, you can always compare enrichment’s output against what your source system sent. That’s what makes enriched content safe to experiment with — and easy to walk back if a run didn’t land the way you wanted.