Correct the record, visibly.
A useful product database will occasionally be wrong or become outdated. The response should be fast, proportionate and traceable.
What counts as a correction
Incorrect specifications, model confusion, broken evidence, misleading availability, calculation errors and conclusions materially affected by new evidence all require review. Spelling and formatting fixes do not normally require a public note.
Investigation
Check the original source, manufacturer documentation, model and regional variant. Preserve the disputed value and evidence internally until the change is resolved. Do not silently replace a contested fact merely because another page says something different.
Publication
Correct the structured field first so every comparison and recommendation updates from the same source. Material editorial changes should include the date, what changed and why. A CoffeeScore affected by invalid test data must be withdrawn or marked under review.
Reader reports
A dedicated corrections contact channel is being prepared. During the public beta, the automated data-quality audit remains the primary research queue.
No retaliation or preference
Retailers, manufacturers, affiliates and readers receive the same evidence review. Commercial value does not determine whether a correction is accepted or how prominently it is disclosed.
A dated corrections log will become part of the permanent database when the production CMS is connected.