Feed error recovery

Fix feed errors by fixing the product record.

Paste a feed error, upload rejected rows, or connect the product records behind the feed. Central returns the missing facts, invalid fields, source/confidence state, review queue, and regenerated supported-channel or custom-feed preview.

Fix my feed errors Preview custom feed ↓

Supported channels + custom feeds · confidence on every fact · unsupported claims stay hidden

Google feed · rejection triage7 errors grouped
Required attribute missingfix
Value format rejectednormalize
Identifier fieldspreserved
Unsupported promotional claimheld
Resubmit previewready
source + confidence visible→ review output
why it matters

Feed errors usually point back to catalog gaps

A feed tool can report that a product was rejected. It cannot always tell you whether the real problem is a missing attribute, a malformed value, an unsupported claim, a category mismatch, or a product record that never had the required data.

Central connects the error to the record. It reads the rejected field, checks what the product currently knows, gathers missing facts where supported, and regenerates the output from verified data.

Central mechanism

Verified facts become reusable outputs.

  • Supported channels + custom feeds
  • confidence on every fact
  • unsupported claims stay hidden
input / output

What you enter and what Central returns

User entersinput
Input
Feed error text, rejected rows, product IDs, or current feed export.
Input
Product URL, CSV row, or existing catalog record behind the rejected item.
Input
Target destination such as Google Merchant Center, Bing Merchant Center, ChatGPT Shopping, Perplexity Shopping, or a custom feed.
Central returnsverified workflow
Output
Error-to-field diagnosis with product record gaps and channel rule notes.
Output
Missing facts, candidate values, confidence, sources, and review state.
Output
Regenerated output preview with ready, needs review, and blocked states.
operational map

The common feed failure patterns

Error pattern
Central action
Safer output
Required attribute missing.
Finds the underlying fact where source discovery supports it.
Field value with source trail and confidence.
Value is present but malformed.
Normalizes units, format, enum, or category mapping.
Channel-shaped value without changing the canonical fact.
Product claim is rejected or risky.
Checks whether the claim is supported.
Claim removed, held, or routed to review.
Category or variant structure is wrong.
Rebuilds product type, variant grouping, and channel-specific field shape.
Feed preview with fewer silent assumptions.
workflow

Feed recovery workflow

1

Paste the feed error or upload rejected feed rows

Paste the feed error or upload rejected feed rows.

2

Central maps the error to product IDs

channel fields, and canonical fields.

3

The product record is checked for missing facts

conflicts, unsupported claims, and formatting problems.

4

Central gathers

verifies missing facts where supported.

5

The regenerated feed output shows ready values

blocked values, and fields needing review.

6

The team approves the corrected output or exports a custom CSV/XML/JSON feed preview

The team approves the corrected output or exports a custom CSV/XML/JSON feed preview.

proof artifact

Proof artifact: rejected row to corrected output

Before Central

Before Central

Error: missing shipping weight and invalid product type for 12 SKUs. Error: unsupported "eco-certified" claim in description. Error: color value does not match channel expectation.

Source/confidence/review

Source/confidence/review

Product record has merchant price and title; source discovery finds package weight for 9 SKUs; 3 remain Needs source. No source supports certification. Merchant value preserved; display value normalized for channel output.

After Central

After Central

Feed preview shows 9 ready rows, 3 held rows, and product type mapping for review. Claim removed from channel description and moved to review. Canonical field stays intact; feed value is channel-ready.

outputs

Outputs for feed recovery

01

Error-to-field mapping with product record context

Error-to-field mapping with product record context.

02

Missing facts and source trail for blocked fields

Missing facts and source trail for blocked fields.

03

Review queue for unsupported claims and source conflicts

Review queue for unsupported claims and source conflicts.

04

Regenerated supported-channel or custom feed preview

Regenerated supported-channel or custom feed preview.

05

CSV/XML/JSON export where the destination can consume custom feeds

CSV/XML/JSON export where the destination can consume custom feeds.

06

Notes for fields that need merchant authority instead of external sources

Notes for fields that need merchant authority instead of external sources.

FAQ

Questions before you start.

Does Central replace my feed tool?

+

Not necessarily. Central improves the product record and can generate supported channel outputs or custom feeds. Some teams keep their existing feed tool and use Central as the verification and enrichment layer.

Can Central fix every feed rejection automatically?

+

No. Some errors need a source, a merchant decision, or a channel account change. Central should show the next action instead of hiding uncertainty.

What if the feed error is caused by a claim?

+

Central checks whether the product record can support the claim. Unsupported claims stay hidden or in review.

Can I export corrected rows?

+

Yes. Use supported channel outputs or custom CSV/XML/JSON exports where supported.