Names and categories
Names describe the source listing; categories help with browsing. Category labels may be broad, and a product’s source title may include promotional wording. Treat those labels as catalog data rather than independent evaluation.
URLs and identifiers
A full URL should open the intended product. In this collection the id query parameter identifies the listing on Copwhere. Keep the complete value when copying or importing the row.
Options and observations
An option field records a selection such as size or color. An observation field describes something you actually checked. Keep them separate so that a planned choice does not appear to be a confirmed product detail.
Dates and status
A date is meaningful when its purpose is clear. Label it “checked on” or “saved on” as appropriate. Personal workflow status should be distinguished from seller stock status, which this collection does not publish.
Give every column one primary meaning
A column is easier to sort and understand when its values answer one kind of question. Keep category, product name, selected option, and personal next step in separate fields. If a cell contains a size, a price observation, and a question, another reader has to interpret the prose before they can compare it with the next row. Separate fields make that comparison more direct and reduce copying errors.
Choose column names that tell you the source and meaning of the value. Source category and personal project are different labels even if both group items. Intended size and observed label are different fields even when they contain the same text. This is especially useful when a sheet becomes collaborative. Another person can see whether they are entering a source detail, a plan, or a completed observation. The structure does not have to be elaborate; it just needs enough separation to stop different kinds of information from being mistaken for one another when rows are exported, copied, or revisited.
Keep units and methods visible for measurements
A number without a unit or method is an incomplete measurement reference. Put the unit in the header when the entire column uses the same unit, and keep the measuring method in an adjacent note when it matters. Flat width, circumference, and a measurement taken under tension are different observations. Do not place them in the same column under a generic size label and expect the number alone to explain the difference.
For example, a top comparison might use chest width in centimeters, body length in centimeters, and method notes. A separate printed-size field preserves the source label. This lets you compare your familiar garment with a candidate without substituting a letter size for a dimension. If the method is unclear, keep the value marked unresolved rather than calculating from an assumption. A well-labeled column makes the limitation visible and tells you what question to ask next. It also prevents a later export from turning a carefully qualified observation into an apparently precise but context-free number.
Use categories for browsing and identifiers for identity
Categories help you narrow a list, but they may be broad or inconsistent across sources. An item placed under footwear may have a more specific type in another catalog. Use the category as a browsing label, not proof that two entries are identical. Keep the full product identifier or URL as the reference key when you compare or merge rows. Similar names and images are helpful cues, but they are not reliable substitutes for the exact address.
If you create your own categories, preserve the source category in a separate field. Your personal grouping can describe how you intend to use the item, while the original field records how the catalog organized it. This distinction makes later maintenance easier. You can change your project groups without losing the imported data, and another reader can understand why two otherwise different categories appear in your list. Clear identity fields protect the reference, while flexible categories make it easier to browse according to the task you are working on.
Make status labels describe an action state
Use personal workflow statuses that readers can interpret without guesswork. Examples include needs option check, needs measurement, ready for comparison, and archived. Define each status briefly if you share the sheet. A single word such as approved can be ambiguous: it might imply a decision, an inspection result, or an action by someone else. Choose the label that matches the actual event rather than the most reassuring-sounding word.
Keep destination information separate. If you record something shown on a seller page, include its source and observation date in the appropriate field. It should not silently become your personal task status. When a task is completed, add the result that explains the change. Moving a row from needs measurement to ready for comparison is meaningful when the new measurement and method are available beside it. This keeps status useful as navigation through your work, instead of turning it into another unexplained judgment that a future reader cannot trace back to evidence.
A practical exercise
Choose a column in a working sheet and write a one-sentence definition. Check whether every value in that column fits the definition. If some cells contain personal tasks and others contain source claims, split the meanings into separate fields. Keep the original data in a baseline while you reorganize the working copy. This exercise improves a sheet through clearer meaning, rather than merely changing column widths or colors while leaving readers to guess what the entries are supposed to describe.