Platform / Features /
Per-channel overrides
Feature · Map & syndicate
Same everywhere else.
Sometimes one channel needs a different title, a different category, a different price field. Per-channel overrides scope that divergence to a single feed - the catalog stays canonical for everyone else.
The difference
Without GoDataFeed
With GoDataFeed
How it works
Diverge a field for one channel without forking the catalog.
Benefits
One channel's quirk stops reshaping the whole catalog.
Every feed still compiles from the same record.
Remove the override and the channel rejoins the canon.
Divergences are documented by their own settings.
Corrections reach every feed except where deliberately overridden.
Each destination gets data shaped to its needs.
Capabilities
Override a mapping or value for one feed - title structure, category, image choice - while every other channel reads the canonical record.
Rules can apply per feed, so channel-specific requirements get channel-specific logic without leaking into the rest.
The exception is configuration, not a copied dataset - there is still exactly one catalog.
Feature · Map & syndicate
Diverge a field for one channel - title, category, image - while the catalog stays canonical for every other feed. Scoped, visible, reversible.
Per-channel overrides
1
Ingest the catalog whole, variants intact.
2
Fix attributes once, at catalog scale.
3
Maintained mappings for 200+ integrations, current when specs drift.
4
Catch errors before they ship, while they're free.
5
Push validated feeds on schedule, price and stock current.
6
Read every channel' feed's verdict back on one screen.
Questions
Field mappings and rule behavior for that feed - titles, categories, image fields, values - without touching other feeds.
No. Overrides apply at feed compile - the catalog record stays canonical.
Each override lives in its feed's configuration, so the divergence is inspectable where it happens.
Start a 14-day trial or book a demo — we'll audit your feed free and show you your diagnostics baseline.
Also in the box
needs.
Eligibility drops and sync failures to email or Slack, thresholds yours.
Every published version diffable — what changed, when, by which rule.
The same rulebook checks, run before publishing instead of after.
Each channel error mapped to its fix, linked from the row.
Weekly eligibility digest per store, for the people who don't log in.
Diagnostics data in your own BI, if that's where your team lives.