Product data quality is not just field completeness inside a PIM or spreadsheet. A record can be internally complete while the website, PDF datasheet, manual, and localized page publish different facts. The usable definition of “done” is that a buyer sees a consistent, correctly scoped statement everywhere the model appears.
Select one exact model, open every public asset in a fresh session, and mark each item pass, fail, or not applicable. Preserve evidence for every failure. The product owner confirms the correct value; the publishing owner fixes the assets.
Product identity
Prove that every asset describes the same sellable item before comparing values.
- The exact model number appears in the page title, technical area, and linked document.
- Family names, suffixes, option codes, regional variants, and hardware revisions are explicit.
- A family-level datasheet lists every included model or clearly states its scope.
- Accessories and replacement models are not presented as specifications for the primary model.
Public-source coverage
Review all surfaces a buyer can reach, not only the CMS record.
- Hero summaries, specification tables, tabs, accordions, and comparison blocks agree.
- Downloadable datasheets, manuals, brochures, drawings, and certificates are inventoried.
- Legacy URLs, cached downloads, and distributor files you control are included.
- Each record stores a source URL or PDF page and the date it was checked.
Numbers, units, and limits
Normalize for comparison without discarding the original published statement.
- Minimum and maximum values retain their sign, inequality, tolerance, and significant digits.
- Units are convertible and use the correct quantity: pressure, flow, power, voltage, or temperature.
- AC/DC, gauge/absolute, nominal/maximum, and typical/guaranteed distinctions are preserved.
- Decimal separators, thousands separators, and unit symbols remain correct across locales.
Configurations and operating conditions
A value is only comparable when the surrounding conditions match.
- Each specification is tied to the applicable variant, material, size, output, or power option.
- Test temperature, medium, supply, load, and other governing conditions are visible.
- Footnotes stay attached when tables are copied into pages or translated.
- Conditional values are not promoted into unconditional marketing summaries.
Documents and revisions
Make the active file identifiable and retire obsolete public copies deliberately.
- Every PDF has a document number, revision, publication date, and applicable model scope.
- The page links to the intended current revision rather than a similarly named upload.
- Superseded documents are redirected, removed from navigation, or clearly marked obsolete.
- A product change lists which pages, PDFs, drawings, and translations require updates.
Localized pages
Treat translation as another publication surface with its own drift risk.
- Localized pages map to the same model and revision as the source-language page.
- Numbers, signs, units, option codes, and footnotes survive translation unchanged unless localized intentionally.
- Language alternates link back to each other and do not point to unrelated category pages.
- The correction workflow identifies every locale affected by a source-data change.
Evidence, ownership, and release gate
Turn findings into accountable corrections and verify the public result.
- Every conflict preserves both original statements and their public locations.
- Product or engineering—not an automated majority rule—confirms the authoritative value.
- Each correction has an owner, status, decision note, and completion date.
- The release is re-scanned from public URLs after deployment and CDN propagation.
Prioritize findings by customer impact
Fix the highest-risk contradictions first. A practical order is:
- Safety and hard limits: pressure, voltage, temperature, load, compatibility, and environmental ratings.
- Selection and quotation: ranges, accuracy, dimensions, connections, materials, interfaces, and option codes.
- Asset identity: a wrong PDF, manual, drawing, model family, or revision.
- Presentation consistency: formatting or terminology differences that do not change technical meaning.
High-risk findings should not be silently corrected by choosing the newest or most common value. Route the evidence to the technical owner and document the decision. For the full comparison method, readhow to audit a datasheet vs product page mismatch.
When to run the checklist
Apply it before a new model launches, after a specification or supplier change, during a website migration, after bulk translation, and whenever a PDF library is reorganized. For mature catalogs, re-check high-value or safety-sensitive models on a fixed cadence and sample the rest after every major publishing release.