Download the reference collection
Use the CSV button on the collection page. The file contains a header row and 10 product references with names, categories, and URLs. It is a reference export, not an order form or a service integration.
Import with headers
Open the CSV in a spreadsheet application or use its text import function. Keep the first row as column names. If your locale expects a different separator, select comma during import and confirm that each URL remains in a single cell.
Keep URLs intact
Do not remove the id query parameter from a Copwhere product URL. It connects the address to the selected listing. Test a copied URL after import if your application reformats it.
Add context rather than unsupported facts
Extend the sheet with your own check date, intended option, and open questions. Avoid copying old prices into a field labeled current unless you actually rechecked them. Keep the original export separately if you need a clean reference later.
Verify the import before editing the file
After opening the CSV, inspect the header row and count the product rows. The supplied collection has ten references. Check that each product name, category, and URL occupies the intended column. If all values appear in one column, use the application’s text import controls to select comma as the separator and preserve quoted fields. Avoid manually splitting every row before checking whether the import settings explain the result.
Open one complete product URL from the imported file and compare it with the source collection. Keep the id parameter intact. If the application shows a friendly display label, inspect or copy the underlying address before assuming the full reference was preserved. Save a clean baseline copy after the import is correct. This gives you something to return to if later sorting or editing goes wrong. A short verification at this stage is easier than repairing a working file after personal notes and comparison fields have been added to a malformed import.
Use text for reference fields that should not be calculated
Product identifiers and URLs are reference text. Treat them as text even if an identifier contains long numeric sections. A spreadsheet application may interpret some values automatically, which can be useful for dates and numbers but undesirable for a reference key. Check the visible value after import and preserve the original source string in your baseline. Do not convert an identifier into a number for the sake of sorting.
Likewise, label observation dates deliberately instead of relying on an application to infer ambiguous date formats. Keep the event meaning in the column header. If you later add numeric measurement fields, give them consistent units and store explanatory methods in adjacent text fields. Separating reference text, dates, and numeric observations makes the file easier to use and reduces accidental reinterpretation. The aim is not to turn a small CSV into an elaborate technical project; it is to make sure the application’s convenience features do not silently change the information that connects your notes with the intended product.
Sort the whole table, not an isolated column
When sorting a working copy, keep the rows together. Sorting product names without their URLs can detach references from the items they describe. Use the application’s table or range selection so all related columns move as a unit. Before a major reorganization, save a copy. After sorting, check a few names against their destination addresses and confirm that the associated notes still belong to the same candidates.
The same principle applies to filtering and copying visible rows. Make sure you understand whether your application includes hidden rows or only the selected cells in an export. A reference file can look correct on screen while a copied fragment loses a field needed to identify the intended option. Test a small export before sharing a larger working version. These habits protect the relationship among name, category, URL, and your observations. That relationship is the practical value of the spreadsheet, so preserving it matters more than achieving a particular order or visual layout.
Keep exports small, labeled, and appropriate for the recipient
When exporting a working file, choose the fields the next reader actually needs. A product reference handover may only require the name, intended option, complete URL, and one question. Your private notes or account-related records do not belong in that export. Keep the detailed working version separately and inspect the exported file before sharing it. Check that important meaning is carried in text rather than only through color or comments.
Name the file according to its purpose and include a short explanation of the date fields if they are present. An export date should not be mistaken for a fresh check of every destination. If you are sharing a comparison result, include the relevant criteria and preserve any unresolved questions. This helps the recipient use the information without inheriting assumptions from your private workflow. A clean CSV export is a useful bridge between the website’s collection and your own tools when its references remain complete and its scope remains clear.
A practical exercise
Open a copy of the downloaded CSV and sort the complete table by category. Verify two product names against their URLs afterward. Export the copy and inspect the header row and one complete address. If a value changes unexpectedly, return to the baseline before adding personal notes. This small trial lets you learn the application’s import and sorting behavior with a clean reference set, reducing the chance that a later operation detaches an important observation from the candidate it was meant to describe.