Skip to main content

Catalog completeness

Publish gate, not catalog quality score

Completeness measures how much required product data is filled before publish — a channel export gate. It is not the same as Catalog Quality in the Agent Control Center, which rolls up agent insights and pending approvals. Use both: completeness before export, agent findings for operational quality.

Completeness measures how much required product data is filled before publish.

Why it matters​

Channels reject or suppress listings with missing titles, images, or mandatory attributes. Completeness lets teams fix gaps before export jobs fail.

How scores work​

Each product or SKU gets a separate score for every channel and language you sell in. There is no single “global” percentage for the whole catalog.

A score reflects:

  • Required attributes on the product family (what your template says must be filled)
  • Channel-specific requirements (fields that matter only on Amazon, only on Shopify, etc.)
  • Destination rules where the integration enforces marketplace constraints

The platform also lists which attributes are still missing so editors know what to fix.

That is why product families and channels should be configured before you rely on completeness dashboards or publish automation.

→ Catalog fundamentals

In the PIM UI​

  • Product detail shows completeness by attribute group
  • Dashboard highlights SKUs that are below your thresholds
  • Scores update as editors fill fields or as imports add data

Via API and agents​

  • Product completeness APIs for integrations and reporting
  • MCP: analyze_product_completeness, find_products_needing_enrichment

Recipe​

Check and improve completeness