A product data quality framework is a defined set of quality dimensions, measurable rules, scores, owners and remediation workflows that keeps product data fit for its channels. Most frameworks measure completeness, accuracy, consistency, validity, timeliness and uniqueness, align with standards such as ISO 8000 and the GS1 Data Quality Framework, and report scores per category, supplier and channel.
A product data quality framework is a defined set of quality dimensions, measurable rules, scores, owners and remediation workflows that keeps product data fit for use in every channel. It replaces subjective judgements with thresholds that a PIM or data quality tool checks automatically. Most frameworks align with ISO 8000, the international data quality series, and with the GS1 Data Quality Framework, which describes good data as complete, consistent, accurate, time-stamped and standards-based.
What a product data quality framework contains
A complete framework has five components:
- Dimensions: the aspects of quality being measured.
- Rules: testable conditions per dimension, attribute and category.
- Scores and thresholds: how rule results combine into a score and what level is acceptable per channel.
- Ownership: who fixes which failures, defined in the product data governance model.
- Monitoring and remediation: dashboards, alerts and work queues with deadlines.
Frameworks fail most often at components four and five. Scores without owners produce reports that nobody acts on.
The six dimensions of product data quality
| Dimension | Question it answers | Example rule |
|---|---|---|
| Completeness | Are required attributes filled | All mandatory attributes for the class are filled for channel "web shop DE" |
| Accuracy | Does the value match reality | Measured dimensions fall within GS1 package measurement tolerances |
| Consistency | Do related values agree | Gross weight is greater than or equal to net weight |
| Validity | Does the value follow format and value rules | GTIN has 8, 12, 13 or 14 digits with a correct check digit |
| Timeliness | Is the data current when needed | Price and availability updated within 24 hours of an ERP change |
| Uniqueness | Is each product recorded once | No two active records share a GTIN |
Accuracy is the hardest dimension to automate. A record can be complete, valid and consistent and still describe the wrong weight. Accuracy needs sample audits against the physical product, the PLM source or a certified measurement. GS1 package measurement tolerances define when measured dimensions and weights count as accurate for a given package type.
How to score product data quality
A practical scoring model works at attribute, product and portfolio level:
- Rule weight: critical rules (identifiers, safety, regulatory data) carry more weight than descriptive rules.
- Product score: weighted share of passed rules, from 0 to 100, calculated per channel because channels require different attributes.
- Gates: a product with any failed critical rule cannot be published, whatever its overall score.
- Portfolio score: average product score per category, supplier and channel, tracked weekly.
An example for one product and one channel:
| Rule group | Weight | Result |
|---|---|---|
| Identifiers and safety (critical) | 40% | Passed |
| Mandatory technical attributes | 30% | 27 of 30 filled |
| Marketing content | 20% | 3 of 5 rules passed |
| Optional attributes | 10% | 4 of 10 filled |
The weighted score is 40 + 27 + 12 + 4 = 83 out of 100, and the product passes the critical gate.
Which KPIs to report
Report a small set of KPIs to management and a detailed set to data teams. Targets below are typical estimates.
- Channel readiness: share of active SKUs meeting the publication threshold per channel (target estimate: 95% or higher).
- Critical rule failures: count of products blocked by critical rules, with age.
- Average product score per category and supplier.
- Audit accuracy: share of sampled attribute values confirmed against the physical product or source (target estimate: 98% or higher for logistics data).
- Mean time to remediate: days from rule failure to fix.
Linking these KPIs to commercial outcomes, such as return rates and conversion, is covered in measuring product content ROI.
How to implement a framework in five steps
- Start from channel requirements. Collect mandatory attributes per channel and category, including regulatory fields.
- Write rules in the PIM. Store them as configuration attached to the PIM data model, so rules change with the model.
- Prevent errors at intake. Apply the same rules during supplier data onboarding so suppliers fix errors before data enters the master record.
- Assign owners and queues. Route each failed rule type to a named role with a deadline.
- Review quarterly. Retire rules that never fail, add rules for new channels and regulations, and recalibrate weights.
Practical next steps
Run a baseline: score the top 500 SKUs against the six dimensions for the two most important channels. Identify the five rules that fail most often and trace each to its root cause, such as a supplier template, a missing ERP field or an unclear owner. Set publication gates for critical rules first, then raise thresholds category by category. For independent PIM vendor comparisons that include data quality features, see PIM Vendors.
Frequently asked questions
What are the dimensions of product data quality?
The most common dimensions are completeness, accuracy, consistency, validity (conformity to format and value rules), timeliness and uniqueness. GS1 describes good data as complete, consistent, accurate, time-stamped and standards-based.
How do you measure product data quality?
Define rules per dimension, run them automatically in the PIM or a data quality tool, and calculate a weighted score per product, category, supplier and channel. Accuracy also needs sample audits against the physical product or a trusted source.
What is ISO 8000?
ISO 8000 is the international series of standards for data quality and master data, published by ISO. Part 1 (ISO 8000-1:2022) gives an overview of the series and its principles for data quality management.