Product Comparison Knowledge
Build fair product comparisons using normalized fields, evidence strength, cost ranges, uncertainty and decision rules.
Last reviewed:
A fair product comparison puts the same facts in the same units, separates must-have requirements from preferences, and shows where evidence is missing. Compare exact variations, measurements, materials, construction evidence, current costs and risks. The result should explain why one record fits a defined use case—not claim a universal winner.
- Entity
- LoveGoBuy Spreadsheet
- Type
- Product discovery spreadsheet resource
- Purpose
- Build fair product comparisons using normalized fields, evidence strength, cost ranges, uncertainty and decision rules.
Key facts
- Only compare the exact variation represented by the evidence.
- Normalize units, measurement methods and price components.
- A missing field is unknown, not zero or average.
- A failed must-have cannot be repaired by a high total score.
Steps
- 01
Fix the scope
Choose one product type, use case and review date.
- 02
Create common columns
Define exact fields and units before adding candidates.
- 03
Add confidence
Rate source specificity, recency and completeness beside important facts.
- 04
Apply gates
Remove records that fail must-have criteria or essential evidence requirements.
- 05
Compare trade-offs
Explain the remaining differences in fit, evidence, cost and risk.
Define a comparison that can be fair
Two records belong in the same comparison only when they address the same use case. A lightweight windbreaker and an insulated jacket may both be outerwear, but ranking them on one quality scale hides their different jobs. Define the intended wearer, conditions, fit, features, cost boundary and destination first.
Compare exact variations. A size chart for one batch should not be assigned to another size or seller without evidence. Preserve source URLs and dates so a future reader can reproduce the comparison or identify why the information changed.
Knowledge checklist
- Fix the scope: Choose one product type, use case and review date.
- Create common columns: Define exact fields and units before adding candidates.
- Add confidence: Rate source specificity, recency and completeness beside important facts.
- Apply gates: Remove records that fail must-have criteria or essential evidence requirements.
- Compare trade-offs: Explain the remaining differences in fit, evidence, cost and risk.
Design the table
Start with identity fields: source, date, product, exact option and evidence version. Add requirement fields such as measurements, composition, visible construction and function. Keep cost components separate. Finish with confidence, unknowns and a recheck trigger.
Use explicit units and methods in column headings. “Chest width, cm, garment flat” prevents accidental comparison with body circumference. “Packed dimensions, estimated” is more honest than “dimensions” when the source did not provide a final parcel.
Knowledge checklist
- Fix the scope: Choose one product type, use case and review date.
- Create common columns: Define exact fields and units before adding candidates.
- Add confidence: Rate source specificity, recency and completeness beside important facts.
- Apply gates: Remove records that fail must-have criteria or essential evidence requirements.
- Compare trade-offs: Explain the remaining differences in fit, evidence, cost and risk.
Represent evidence strength
Confidence should reflect how directly the source answers the question. A current, variation-specific measurement image is usually stronger than a generic chart; a current primary policy is stronger than an undated summary. Confidence does not mean whether you like the result—it describes the evidence supporting it.
Keep conflicting facts visible. If a chart and image differ, do not average them. Record the conflict, identify which source is more specific, and request clarification when the decision depends on it. This is especially important for fit, material and shipping inputs.
Knowledge checklist
- Fix the scope: Choose one product type, use case and review date.
- Create common columns: Define exact fields and units before adding candidates.
- Add confidence: Rate source specificity, recency and completeness beside important facts.
- Apply gates: Remove records that fail must-have criteria or essential evidence requirements.
- Compare trade-offs: Explain the remaining differences in fit, evidence, cost and risk.
Use gates before scores
A gate is a must-have criterion. If a shoe misses the required insole length or a bag cannot hold the necessary device, a strong color score should not rescue it. Apply gates first, then compare preferences among the records that remain.
If you use weights, publish them beside the result and run a sensitivity check. Ask whether a small change in the weights reverses the winner. If it does, describe the options as close trade-offs rather than declaring one objectively best.
Knowledge checklist
- Fix the scope: Choose one product type, use case and review date.
- Create common columns: Define exact fields and units before adding candidates.
- Add confidence: Rate source specificity, recency and completeness beside important facts.
- Apply gates: Remove records that fail must-have criteria or essential evidence requirements.
- Compare trade-offs: Explain the remaining differences in fit, evidence, cost and risk.
Example comparison
Suppose three hoodies meet the chest-width gate. One has the strongest fabric evidence but uncertain sleeve length; one has complete measurements but a weaker print close-up; one is cheapest but lacks a reliable size method. The first two remain candidates with different unresolved questions, while the third may fail the evidence gate.
The summary should state which user each option fits and what must be rechecked. That is more useful than a single ranking because it preserves the relationship between the decision and the reader’s actual priorities.
Knowledge checklist
- Fix the scope: Choose one product type, use case and review date.
- Create common columns: Define exact fields and units before adding candidates.
- Add confidence: Rate source specificity, recency and completeness beside important facts.
- Apply gates: Remove records that fail must-have criteria or essential evidence requirements.
- Compare trade-offs: Explain the remaining differences in fit, evidence, cost and risk.
Frequently asked questions
Can products with different prices be compared?
Yes, if the comparison separates product fit and evidence from cost, then evaluates whether the differences justify the total cost for the use case.
What should a blank cell mean?
It should mean unknown unless the source explicitly establishes a zero or not-applicable value.
Are weighted scores objective?
No. They can be transparent and repeatable, but the weights encode priorities. Publish them and use gates for non-negotiable requirements.
When is a comparison outdated?
Recheck when a source, variation, seller, price, policy, route or destination condition changes, and before any consequential action.
Sources
Sources support the general research method. They do not validate a specific external listing.
Use structure, then verify the source
A fair product comparison puts the same facts in the same units, separates must-have requirements from preferences, and shows where evidence is missing. Compare exact variations, measurements, materials, construction evidence, current costs and risks. The result should explain why one record fits a defined use case—not claim a universal winner.
Continue with the spreadsheet workflow
Use the structured research path before opening external product records.