Integrity
The feed is publicly reachable, within limits, safely decoded and parseable as XML or CSV.
A good ecommerce feed is readable, complete and consistent across the catalog. This educational framework helps teams locate upstream weaknesses before measuring them with a scan.
Use these dimensions to organize ownership and investigation. They are not a disclosure of the production scoring weights.
The feed is publicly reachable, within limits, safely decoded and parseable as XML or CSV.
Supported fields needed to identify, describe, price and route products are present where applicable.
The same representation rules are applied across rows and identifiers remain unique.
Product ID, brand and recognized GTIN or MPN coverage support stable identity.
Titles and descriptions contain enough source information to describe the product.
A primary image and product destination are present with valid HTTP or HTTPS URL syntax.
Prices include a positive amount and currency, while availability uses a supported value.
A product category or product type is present, while factual correctness remains a catalog-owner decision.
A durable vocabulary for catalog, ecommerce and marketing teams. It includes questions that may still require another tool or human verification.
The current score uses actual parser evidence and 13 supported product rules. Findings expose severity, affected counts and recommendations without publishing unnecessary internal weighting detail.
Run the same public export through a versioned audit and record the product count and score.
Start with file blockers and critical failures affecting the widest portion of the catalog.
Correct the catalog field, source mapping or feed generator rather than patching a temporary export.
Create a fresh feed and confirm the expected records and values are present.
Re-run the audit and investigate unexpected score, count or issue changes.
Use each channel's own diagnostics for policy, website, processing and account-specific decisions.
Product Feed Scan parses public XML and CSV feeds incrementally, applies versioned rules to supported fields and groups failures by impact. It does not predict platform policy decisions, modify feeds or guarantee channel approval.
No. They are an educational framework for discussing feed quality. The production score uses a versioned set of deterministic rules and documented severity deductions.
Yes. A file may parse successfully while many products lack identifiers, descriptions, images, valid price representation, availability or categories.
No. Platform approval can also depend on policies, account settings, destinations, the website and facts not visible in the source feed.
Measure the current export, group failures by root cause, repair upstream data or mappings, regenerate the feed and compare the next result using the same ruleset.
Scan a public XML or CSV feed, review the free score and unlock the complete private report only if you need every affected product.