Product data quality is easiest to improve when the team can see it as a measurable operating system. A scorecard turns vague complaints such as “the catalog is messy” into a shared view of which products, attributes, suppliers, and channels need attention.
The six dimensions of product data quality
A useful scorecard separates different failure modes. A product can be complete but inaccurate, accurate but inconsistent, or rich in content but not ready for a specific channel.
- Completeness: Are the required fields populated for the category and channel?
- Accuracy: Do values match the source of truth, product specification, and approved business rules?
- Consistency: Do units, names, formats, and values follow the same conventions?
- Uniqueness: Are duplicate products, SKUs, variants, and assets under control?
- Freshness: Are price, availability, compliance, and other time-sensitive fields current?
- Channel readiness: Can the product pass the requirements of each destination without manual repair?
A practical weighting model
Start with a 100-point score. Weight completeness at 25 points, accuracy at 20, consistency at 15, uniqueness at 10, freshness at 10, and channel readiness at 20. A regulated or marketplace-heavy catalog may increase the weight of accuracy and channel readiness.
Score at the product level, then aggregate by category, supplier, brand, channel, and market. The aggregate score is useful for leadership; the underlying exceptions are what operators need to fix.
Suggested scorecard fields
| Dimension | Example checks | Evidence |
|---|---|---|
| Completeness | Title, description, category, price, availability, images, required attributes | Required-field rules by category |
| Accuracy | Specification, dimensions, identifiers, claims, price, stock | Source record or approved reference |
| Consistency | Units, casing, colour names, naming patterns, decimal formats | Controlled vocabulary and normalization rules |
| Uniqueness | SKU, GTIN, variant and image duplication | Duplicate report and merge decision |
| Freshness | Last update, stock age, price age, expiring compliance values | Timestamp and source-system status |
| Channel readiness | Category mapping, identifiers, image rules, policy fields, landing page | Channel validation result |
Set thresholds that trigger action
Use simple thresholds at first. For example, a product can be green at 90–100, amber at 75–89, and red below 75. Add hard stops for critical fields: a missing price, availability, legal claim, or channel-required identifier may block publication even when the overall score is high.
Do not use one threshold for every category. A fashion product and an industrial component have different required attributes. Rules should inherit from category and channel requirements.
Move from score to workflow
Every red result should become an actionable exception with an owner. Group repeated errors by root cause: one supplier sending the wrong unit, one mapping that creates empty categories, or one import that strips variant values. Fixing the root cause improves many products at once.
Compare the scorecard with the product data quality checklist and use the PIM data quality guide to define a repeatable review cadence.
Measure business impact
Connect quality scores to outcomes such as search exits, zero-result searches, feed disapprovals, returns, support contacts, conversion rate, and revenue per session. The goal is not a perfect number for its own sake. The goal is to show which quality improvements make the catalog easier to discover, trust, compare, and buy.
Start with a sample of important products, establish a baseline, fix the highest-impact issues, and measure again after publication. The Completeness Checker can turn the first manual audit into a repeatable validation step.
