Data Sources and Verification
How manufacturer evidence supports public specifications.
What counts as evidence
We use manufacturer manuals, datasheets, support documentation and product pages for the exact configuration. Authorized retailer material can fill a gap, but conflicts require an explicit human decision. A manufacturer URL alone is not enough: the evidence must support the actual field value and variant.
What appears publicly
Product specification rows link to their supporting source, section or page when available. Public pages show verified values and a review date. Private reviewer identifiers, internal notes, import errors and audit records remain in the administrator system.
What remains unknown
Missing source-backed features, dimensions, prices and bank permissions stay unknown. An unknown feature does not mean a motor lacks that feature, and unknown series permission does not mean connecting batteries is safe. Partially verified records are labeled explicitly.
How corrections work
An administrator can add evidence, reject an unsupported value or flag a conflict. Resolving a conflict requires selecting supporting evidence and recording notes. Source health and reference edits trigger quality recalculation; archived and test products cannot become indexable public records.