Platform /  Features /  

Rules engine

Feature · Optimize & transform

If this, then fixed.

Across the whole catalog.

Feed rules apply conditional transforms to every matching SKU - write the fix once, preview what changes, and let it run on every import after that.

The difference

Rules vs. row-by-row edits

Without GoDataFeed

  • Fixes happen one row at a time in a spreadsheet
  • The same correction gets redone after every export
  • Nobody knows which edits were made, or why
  • A channel policy change means a week of manual edits

With GoDataFeed

  • One rule fixes every SKU that matches the condition
  • Rules re-run on every import, so fixes persist
  • The logic is written down, visible and editable
  • A policy change is a rule change, not a project

See it work on your own catalog.

Run a free feed audit

How it works

If/then transforms with preview - see affected SKUs before you commit.

Benefits

No spreadsheet surgery

Catalog-scale fixes stop being manual labor.

Fixes persist

Rules re-apply on every import - corrections survive data refreshes.

Logic you can read

The transformation is written down, not trapped in someone's habits.

Faster policy response

Channel requirement changes become rule edits.

Consistent output

Every matching product gets the same treatment.

Fewer regressions

Remove the guesswork of remembering which rows were fixed.

Capabilities

Conditional logic

If a field matches a condition, transform it - set, replace, append, combine. The rule reads any field in the catalog and writes the change everywhere it applies.

Catalog-scale application

Rules run against every matching SKU on every compile. A fix written once holds across the catalog as products come and go.

Preview before commit

Compile the feed and review the result before it ships - see the transformed data, not a promise about it.

Feature · Optimize & transform

Feed Rules Engine - Conditional Product Data Transforms | GoDataFeed

Apply if/then transforms across every matching SKU - write the fix once, preview the compiled result, and let it re-run on every import.

Rules engine

Rules engine is stage three

of six.

Fix attributes once, at catalog scale.

Every feature works from the same catalog. Upstream hands off clean data; this stage shapes it for each channel.

Questions

Feature · Optimize & transform

What can rules change?

Any field the feed carries - titles, descriptions, categories, prices, custom labels, image fields. If it's in the feed, a rule can transform it.

When do rules run?

On every feed compile. As the catalog changes, the rules keep applying, so fixes don't decay.

Can I see what a rule will do before it ships?

Yes - compile and review the feed output before submission, and check the affected products in the feed products table.

Write the fix once.

Start a 14-day trial or book a demo — we'll audit your feed free and show you your diagnostics baseline.

Start free trialBook a demo

Also in the box

Everything the monitoring loop

needs.

Alerting

Eligibility drops and sync failures to email or Slack, thresholds yours.

Feed history

Every published version diffable — what changed, when, by which rule.

Pre-submission validation

The same rulebook checks, run before publishing instead of after.

Error playbooks

Each channel error mapped to its fix, linked from the row.

Scheduled reports

Weekly eligibility digest per store, for the people who don't log in.

API access

Diagnostics data in your own BI, if that's where your team lives.