Channel sprawl - supported channels + custom feeds Supported channels + custom feeds

Stop rewriting the same SKU for each selling channel.

Import a product record, CSV row, or enriched catalog. Central returns channel-shaped titles, attributes, schema, supported channel outputs, custom CSV/XML/JSON feed previews, source/confidence context, and review states from one verified record.

Build channel output Preview custom feed ↓

Supported channels + custom feeds · confidence on every fact · AI drafts, verification decides what ships

One record · many outputsrules instead of rewrites
Canonical factsverified
Storefront copyready
Marketplace bulletsneeds review
Schema outputready
Unsupported channel claimheld
source + confidence visible→ review output
why it matters

Every channel asks for a different shape

The product is the same. The output is not.

Your storefront wants readable copy. Google wants structured attributes. ChatGPT Shopping and other AI-readable surfaces need facts they can parse. PMax wants campaign-ready product data. Custom partners ask for CSV, XML, JSON, or JSONL. The old answer is to keep rewriting and remapping the same SKU.

Central starts from the canonical product record, then adapts the verified facts to the destination.

Central mechanism

Verified facts become reusable outputs.

  • Supported channels + custom feeds
  • confidence on every fact
  • AI drafts, verification decides what ships
input / output

What you enter and what Central returns

User entersinput
Input
Product URL, CSV row, catalog export, or existing Central record.
Input
Target destination such as storefront, Google Merchant Center, Bing Merchant Center, ChatGPT Shopping, Perplexity Shopping, or custom feed.
Input
Optional channel rules, required columns, or sample feed format.
Central returnsverified workflow
Output
Verified canonical record with sources, confidence, and review state.
Output
Destination-shaped output preview with ready, needs review, and blocked fields.
Output
Custom CSV/XML/JSON export shape from verified fields.
operational map

How Central handles channel sprawl

Channel pain
Central action
Output
Same description rewritten for every destination.
Generates channel copy from verified facts and destination constraints.
Storefront copy, marketplace-style bullets, or feed descriptions without unsupported claims.
Attribute names and formats drift.
Maps canonical fields into destination fields.
Channel-specific value without changing the product truth layer.
Claims are safe in one channel but unsupported in another.
Checks source support before output generation.
Risky claims held or removed from the destination preview.
Custom partner feeds require a different structure.
Uses verified fields to build custom CSV/XML/JSON output.
Previewable export with missing fields clearly marked.
workflow

Channel adaptation workflow

1

Start with an enriched product record or import products that need channel output

Start with an enriched product record or import products that need channel output.

2

Choose a supported channel or define a custom feed shape

Choose a supported channel or define a custom feed shape.

3

Central checks required fields

existing facts, source confidence, and review state.

4

Verified fields are adapted into titles

descriptions, bullets, attributes, schema, or feed columns.

5

Missing

unsupported values stay visible in the output preview.

6

The team approves

exports, publishes, or returns to enrichment for missing facts.

proof artifact

Proof artifact: one record, multiple output previews

Canonical record

Canonical record

Verified title, brand, GTIN, price, material, dimensions, compatibility, care, and product type. Claim: "works with all devices." Merchant title is too long for a destination.

Channel rule check

Channel rule check

Google requires required attributes; custom partner wants XML fields; AI-readable output wants schema and provenance. No source supports universal compatibility. Title adaptation uses verified fields only.

Output preview

Output preview

Google feed row, custom XML snippet, Schema.org/JSON-LD, and storefront copy from the same record. Claim removed from bullets and shown as Needs source. Channel-ready title preview with preserved facts.

outputs

Outputs Central can prepare

01

Product-page copy and structured product attributes

Product-page copy and structured product attributes.

02

Google Merchant Center, Bing Merchant Center, ChatGPT Shopping, and Perplexity Shopping outputs where enabled

Google Merchant Center, Bing Merchant Center, ChatGPT Shopping, and Perplexity Shopping outputs where enabled.

03

Custom CSV, XML, JSON, or JSONL feeds where the destination can consume custom formats

Custom CSV, XML, JSON, or JSONL feeds where the destination can consume custom formats.

04

Schema.org/JSON-LD and x-central metadata for AI-readable product data

Schema.org/JSON-LD and x-central metadata for AI-readable product data.

05

Review queues for missing fields, conflicts, and unsupported claims

Review queues for missing fields, conflicts, and unsupported claims.

FAQ

Questions before you start.

How does Central support destinations beyond supported channels?

+

Central uses supported channels plus custom feeds. Custom CSV/XML/JSON feeds can cover destinations that accept custom formats.

Can the same record create different titles or descriptions?

+

Yes. Central can adapt the wording to the destination while keeping claims grounded in the same verified facts.

What happens when a channel needs a missing field?

+

The output preview should show the missing field and route the product back to enrichment or review.

Can I keep my existing feed tool?

+

Yes. Central can improve the product record and export feed-ready data into the stack you already use.