Documentation

Catalog QA / Data Quality

What is scanned, how scoring works, and known limitations for Magento API coverage.

Scan scope

• Product core fields: SKU, name, type, status, visibility, price, special price, update timestamp.
• SEO fields: URL key, meta title, meta description.
• Media fields: base image and gallery presence indicators.
• Taxonomy fields: category assignments.
• Inventory best-effort fields: stock status and salable quantity.
• Feed fields: brand, GTIN, and weight where available in attributes.

Scans run via Magento APIs and do not install Magento modules.

Scoring model

• Score starts at 100.
• Each open issue applies a penalty based on severity, configured rule weight, and affected item count.
• Category scores are calculated from penalties in each category: SEO, Media, Pricing, Stock, Variants, Feed.
• Scores are clamped to 0..100.

Use rule weight overrides per org to tune score sensitivity for your catalog priorities.

Issue lifecycle

• Open issues are updated on repeated scans by stable fingerprints.
• Full scans can resolve open issues not seen in the latest run.
• Ignored issues remain ignored until manually unignored or ignore expiry passes.
• Audit timeline includes opened, updated, resolved, ignored, unignored, and reopened events.

Known limitations

• MSI inventory endpoints are best-effort; some environments expose only legacy stock fields.
• Configurable children and super-attribute data depend on attribute availability through product payloads.
• Duplicate URL key detection is best-effort and may be limited by API pagination settings.
• Top-seller targeting depends on optional API data paths and may be unavailable per store setup.