Write the buying brief before the first row
Put four short lines above the table: the job the item must do, the spending ceiling you are willing to consider, one non-negotiable requirement, and one deal breaker. “Light rain jacket for daily walking; roomy over a sweater; no dry-clean-only fabric” is more useful than “find a good jacket.”
This brief gives you a stable reason to remove products. A row can be popular, inexpensive and well photographed while still failing the actual job. It works the same way whether you begin with a shared list or a blank table.
Recommended row fields
You do not need every field for every product. Start with the core set, then add details only when they change the decision.
| Field | What to record | Why it matters |
|---|---|---|
| Item and category | Plain-language product name and one category. | Keeps unlike products out of the same comparison. |
| Use case | The job this specific row might solve. | Prevents attractive but irrelevant saves. |
| Catalog link | The Findsindex or organized page where you discovered it. | Preserves the browsing context. |
| Raw source | The current marketplace or source URL, when visible. | Lets you verify that redirects and catalog labels still match. |
| Variant | Color, size, configuration, quantity or model. | Stops one visible price or photo from being applied to every option. |
| Evidence | Measurements, useful photos, material notes, specifications or recent feedback. | Separates what is shown from what is assumed. |
| Critical check | The measurement, fit point, connector or construction detail that could disqualify it. | Keeps research focused. |
| Visible price | The item figure and currency shown for the selected variant. | Preserves the number without pretending it is the delivered total. |
| Weight and packing | Known weight, dimensions, box choice and what is still estimated. | Makes shipping uncertainty visible. |
| Cost scenario | Item, domestic delivery, service costs and a clearly labeled shipping estimate. | Allows fairer comparisons without inventing a quote. |
| Alternative | The closest comparable row and why it may be better. | Reduces attachment to the first acceptable find. |
| Open question | One unanswered issue and the person or page that can answer it. | Turns uncertainty into a next action. |
| Status | Inbox, checking, comparing, waiting, review-ready, remove or delivered. | Makes the next step obvious when you return later. |
Use statuses that describe the next action
Interesting, but not yet worth detailed work.
One or two specific details need confirmation.
Place it beside the closest alternatives.
Do not advance until a meaningful unknown is resolved.
The row is coherent enough for a final current-page check.
Record the reason so the same weak row is not reconsidered later.
Avoid vague statuses such as “good,” “maybe” or a colored star. They describe a feeling, not the next task.
Add only the fields your category needs
Footwear
Foot length, insole reference, width, outsole, heel and box preference.
Clothing
Garment chest, shoulder, length, rise or inseam; fabric; lining; care; packed weight.
Bags and accessories
Dimensions, capacity, hardware, closures, lining, attachment points and scale.
Electronics
Connector, voltage, device compatibility, battery information, included parts and route restrictions.
Example: an honest row is better than a complete-looking row
Decision
Light rain jacket for walkingEvidence
Garment chest and length; lining, zip and seam photos; source matches catalog pageOpen question
Fabric breathability and packed weight remain unconfirmedStatus: Wait. The row already explains why it has not advanced. That is more valuable than filling every cell with uncertain information.
Keep the sheet useful after the decision
- Date the last current-page check instead of putting “2026” in every title.
- Keep rejected rows with a short reason for a limited time, then archive them.
- After delivery, record fit, measured weight, packaging and any difference from the saved evidence.
- Do not store account credentials, payment details, addresses or private support conversations in a shared sheet.
If a field does not help you compare, verify, estimate or decide, it probably does not belong in the working view.
