Platform /  Features /  

Variant model

Feature · Ingest & catalog

Variants, structured once.

Reshaped per channel.

Channels disagree about variants - item groups for Google, parent-child for Amazon, flat lists elsewhere. The variant model keeps one canonical structure in the catalog and reshapes it to each channel's spec downstream.

The difference

One variant structure vs. per-channel forks

Without GoDataFeed

  • Each channel's variant rules handled by hand
  • Parent-child errors repeat on every marketplace
  • Size and color options flatten into separate products
  • A variant fix has to be made once per channel

With GoDataFeed

  • One canonical structure lives in the catalog
  • Channel templates reshape it to each spec
  • Parents and children stay linked everywhere
  • Options and attributes survive the trip

See it work on your own catalog.

Run a free feed audit

How it works

One canonical variant structure, remapped per channel downstream.

Benefits

No structure forks

One variant model serves every channel's format.

Fewer grouping errors

Linked variants stop arriving as orphaned products.

Options intact

Size and color data lands in the right channel fields.

Cleaner PDP grouping

Channels that group variants get the data to do it.

One fix, all channels

Correct the structure once, downstream shapes follow.

Marketplace-ready

Parent-child requirements are met from the same record.

Capabilities

Canonical structure

Variants import as the platform structures them - parents, children, options - and stay related in the catalog.

Per-channel reshaping

Channel templates map the structure to each destination's model: item_group_id for Google, parentage for marketplaces, flat lists where required.

Attribute continuity

Size, color and option attributes carry through to the fields each channel expects them in.

Feature · Ingest & catalog

Product Variant Management for Feeds | GoDataFeed

Keep one canonical variant structure and reshape it per channel - item groups for Google, parent-child for marketplaces, options intact everywhere.

Variant model

Variant model is stage one

of six.

One variant structure, reshaped per channel.

Every feature works from the same catalog. This is where it enters - and everything downstream inherits what lands here.

Questions

Feature · Ingest & catalog

How do variants map to Google Shopping?

The channel template writes the shared identifier into item_group_id so Google groups the variants correctly.

What about marketplaces that need parent-child files?

The same canonical structure is reshaped into the parentage format the marketplace requires.

Do variant attributes carry over?

Yes - options like size and color flow into each channel's designated attribute fields.

Structure variants 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.