Quick answer
Give the page a quick reality check: find the code, product type, named options, useful specifications, price basis and source URL. If the photos look convincing but the details cannot be tied to one product, keep the page as a visual lead rather than a comparison record.
Use a ninety-second first pass
- Identify the object. State the neutral product type before interpreting style names or marketing labels.
- Find a stable reference. Prefer a product code or exact page URL over a screenshot filename.
- Scan the full image set. Look for specifications, labels, measurements, packaging and option changes.
- Read the price context. Note currency, unit, quantity tier and what is included.
- Write the next question. Save the page only when one unanswered field can change your decision.
Give every candidate a stable identity
Record the source URL, page title, visible product code, date checked and a neutral description. If the code appears only inside an image, note where you saw it. Do not invent a code from a URL fragment or assume two similar names describe the same variant.
Separate visible evidence from interpretation
| Field | Record as evidence | Avoid turning into fact |
|---|---|---|
| Material | Published specification or clearly labelled close-up. | A texture guess based on one compressed photo. |
| Dimensions | Numbers, unit and measurement method shown for this item. | A familiar size label or scale estimated from a hand. |
| Included parts | Written package list tied to the selected variant. | Every object used as photo styling. |
| Availability | Current option state published by the responsible page. | An old image or a variant that still appears in a gallery. |
| Price | Currency, unit, quantity tier, inclusions and check date. | A bare number copied into a spreadsheet. |
Read the photo sequence for changes in product context
Catalog galleries often mix overview images, detail images, charts, packaging and multiple variants. Confirm where the selected product starts and ends. A size chart or accessory photo near the item may belong to a different option or a general category.
- Overview images show the same shape and construction.
- Detail images preserve the same color, hardware and option.
- Measurements name the object and method.
- Packaging images identify what is standard and what is optional.
- No image quietly switches to another model or set size.
Normalize the price before comparing it
A useful price record includes currency, price unit, quantity tier, selected variant, included parts, tax or fee context if stated, and the date checked. “12.50” cannot be compared until you know whether it refers to one item, one set, one sample, one carton or a starting tier.
Keep contradictions visible
When the title, image text, option selector and reply disagree, do not choose the field that makes the product look easiest to compare. Store the alternatives, mark the conflict and ask which current specification controls the exact code.
Specific but incomplete
The code and variant are stable, while one measurement or inclusion still needs confirmation.
Detailed but incoherent
Several specifications exist, but they cannot be tied to the same code, option or page state.
Build one candidate record before opening a chat
| Record field | What to enter |
|---|---|
| Identity | Product type, exact code, source URL and date checked. |
| Selected option | Color, size, model, material or set configuration. |
| Comparable facts | Relevant measurements, specifications, inclusions and published quantity context. |
| Evidence locations | Which caption, image, chart or listing field supports each fact. |
| Open question | The smallest unresolved issue that can change the decision. |
Remove pages that cannot support a next decision
Drop a candidate when the source is unstable, the product changes across the gallery, the code cannot be reconciled, or the page requires you to guess every practical field. A smaller set of traceable candidates makes later sizing, quantity and quote comparisons much easier.
