Why spreadsheet rows are hard to compare

A sheet looks structured because information sits in columns. That does not mean the rows contain equivalent evidence. One jacket row may show measurements, lining photos, a current destination, and a weight note. Another may contain only a nickname, thumbnail, and price. Sorting those rows by price produces a neat table and a weak decision.

Separate missing information from negative information. A missing size chart means fit uncertainty remains. A destination that clearly shows a different product is negative evidence: the row should leave the shortlist.

Put seven fields on the same footing

FieldQuestion to answerRemove the row when…
CategoryDo the title, image, and destination describe the same item type?The destination is unrelated.
Link relevanceDoes the current page still match the spreadsheet description?The link is broken or materially different.
PhotosDo the images show the views this category needs?Only promotional or repeated angles appear.
MeasurementsIs sizing explained with usable dimensions?Fit matters and no usable measurement exists.
Price contextHow does it compare with similarly documented rows?Price is the only reason to save it.
Packed weightCould volume or packaging change the value?The likely parcel defeats the reason for choosing it.
UncertaintyWhat still needs checking?You cannot name the unanswered question.

Use a confidence note, not a decorative score

Write one sentence: “Strong measurements and lining photos; current source matches; packed weight unclear.” That note preserves the reason behind the decision. A single number hides whether the missing evidence concerns fit, construction, or delivery cost.

When the row and destination disagree

Trust the current destination for current details, but keep a record of the mismatch. A changed price may only require a fresh comparison. A changed color option may affect the exact row. A completely different item type ends the review. Do not merge old spreadsheet text with new destination details as if they were one confirmed record.

Worked example: two jacket rows

Row A

Lower price, thin evidence

  • One front image
  • No garment measurements
  • Unclear material description
  • No weight context

Decision: remove for now. The row creates more questions than it answers.

Row B

Higher price, usable evidence

  • Front, back, zipper, and lining views
  • Chest width and length shown
  • Current destination matches
  • Weight still needs checking

Decision: shortlist for weight and policy review.

This is a teaching example, not a real seller review or product claim. Its purpose is to show why evidence coverage matters more than the cheapest visible row.

A practical stopping rule

Keep a row only when you can explain what is known, what remains uncertain, and why the next click is worth your time.

Once two or three rows survive, stop collecting. Use the QC photo guide for visual checks and the shipping weight guide for parcel context.

How this page was reviewed

The comparison framework uses the same seven fields for every row so a low price or polished thumbnail cannot silently change the standard. The jacket example is explicitly hypothetical and makes no seller or product claim. Read the complete editorial method.