Why product feed errors happen and what to check first

Locate the first incorrect value

Source → feed tool → export → receiving platform is the diagnostic path. Compare the same variant at the same update cycle; a correct current source record cannot explain a platform error generated from yesterday’s export.

Start with the affected scope. One SKU suggests a product-specific fact. A category-wide issue suggests a mapping or required-attribute gap. A sudden catalog-wide failure suggests a shared rule, format, credentials or retrieval problem. These are investigation priorities, not a substitute for the actual error.

For Merchant Center issues, use Google Shopping feed optimization when you need help tracing the full route.

Five feed problems and how to diagnose them

Treat the cases below as illustrative diagnostic patterns. Google and each marketplace define their own requirements; refer to the applicable specification and exact returned error.

• Missing GTIN or brand → likely cause: a source fact is absent, or the wrong field is mapped. Check: the exact variant barcode, supplier record, imported field and final output. Fix: recover the real manufacturer value or correct the mapping; follow the destination’s applicable exemption process when appropriate. Verify: the right product identity is received and the specific error clears after processing. Never invent identifiers.
• Price mismatch → likely cause: an old export, a sale-price rule or two price adjustments. Check: variant price and currency in the source, every transformation, exported price and the landing page or marketplace offer. Fix: correct the owning price rule and update sequence. Verify: the received value agrees with the intended offer after the next refresh.
• Attribute missing across one category → likely cause: the category changed its required fields, the mapping is wrong, or a shared attribute is blank. Check: destination category, required attributes and a passing sibling SKU. Fix: correct category assignment or map verified values. Verify: both the error count and the actual published attributes improve.
• Correct source, empty export field → likely cause: a later rule overwrites the enrichment or the exporter reads a different internal field. Check: before/after values for the relevant rules and the final field mapping. Fix: narrow the condition, correct rule order or select the intended field. Verify: affected and unaffected sample SKUs after a fresh import.
• Entire feed fails to process → likely cause: inaccessible URL, authentication, malformed output or parsing trouble. Check: retrieval status, platform processing time and the actual file, including header/delimiter/encoding where applicable. Fix: the delivery or formatting issue before editing product descriptions. Verify: a new successful processing run and a plausible received item count.

Worked trace: a price that changes between systems

Illustrative case: a lamp costs EUR 79.95 in the webshop. Channable imports 79.95, a destination rule reduces it to 74.95, and the Google export contains 74.95 while the landing page remains 79.95. The first divergence is the rule, so editing the source price would treat the wrong layer.

Check why the discount exists. If it is valid only for a marketplace offer, scope it to that destination. If the webshop promotion is intended, align the source offer and timing before exporting it. Google’s price requirements explain the required alignment for Shopping.

Export again, inspect the lamp’s price, and verify the receiving platform’s processed record. Then check an undiscounted product and the next scheduled update. This catches a rule that fixes one lamp while discounting the rest of the catalog.

Verify recovery and prevent the same error returning

Save the failing item, error, cause, owner, correction and verification result. Assign reusable product facts to the source owner, channel transformations to the feed owner, and platform account or policy issues to the person who can resolve them.

A clean export and a cleared platform error are separate checkpoints. Check product-level and account-level restrictions as well as data values. If acceptance is restored but impressions remain weak, continue with approved Google Shopping products not showing; more feed edits may not address the remaining problem.

For recurring rule problems, review our Channable expertise. For gaps in the source catalog, use the marketplace product-data checklist.