Most buyers don’t need to know how the usfans Product Spreadsheet is organized — but if you’re the kind of shopper who wants to understand the tool you’re using, this guide is for you. It walks through the schema (what’s in a row), the categorization (how products map to pages), and the verification workflow (how rows stay accurate week after week).
The row — what’s inside each product
Every row carries a consistent set of fields. The visible ones are the product name, a reference image, the seller link, and the category. Behind the scenes each row also tracks seller identity, a verification timestamp, a drift score (how far the live product has moved from the reference), and any buyer notes attached to the row. You don’t see the back-end fields in the public view — but they’re what the weekly verification workflow runs on.
The categories — where rows live
Rows map to one of eight public categories. There’s no multi-category stuffing — a shirt is a shirt, a cap is a cap. The eight pages are Shoes, Hoodies/Sweaters, T-Shirts, Jackets, Pants/Shorts, Headwear, Accessories, and Other Stuff. If a product genuinely spans two categories, it’s indexed in both and canonicalized to the primary one for the back-end row.
The verification workflow — how rows stay accurate
Verification runs weekly. Each row goes through three checks. First, the seller URL is fetched and must resolve to an active product page (not a category or a 404). Second, the live product name must still match the row name within a tolerance (minor variant renames are allowed; title overhauls are not). Third, the live product image is compared against the stored reference — same silhouette, same color-way, same print placement. If any check fails, the row is either repaired (if the seller just rebranded) or removed (if the product is gone).
Buyer notes — the social layer
Rows accumulate notes over time: “runs big by one size,” “fabric is heavier in person,” “ask for extra QC photos.” One note is a hint. Three consistent notes become a signal. Multiple contradictory notes usually mean the variants differ noticeably — worth reading before you add to cart.
Why this structure matters to you
Three practical outcomes:
- Links don’t rot. Weekly checks keep broken rows out of your path.
- Variants don’t confuse. If a seller swaps a product, the row either updates or disappears — you’re not shopping yesterday’s image on today’s product.
- Reference parity. The image-match check means what you see in the directory is what you get on the seller page.
What you can do with this knowledge
Mostly, shop with more confidence. But if you want to go further:
- Report drift. If a row’s live product has clearly moved from the reference, flag the row. It’ll go into the next verification sweep.
- Add a note. If you buy a row and have something useful to share (sizing, color, QC experience), the note helps the next buyer.
- Trust the system. Multiple consistent notes + recent verification = confident buy.
How the Product Spreadsheet differs from a generic sheet
Generic shared sheets don’t have row metadata, don’t have verification cycles, and don’t have category-first pages. The usfans Product Spreadsheet is spreadsheet-shaped where it needs to be (row by row, scannable, keyboard-friendly) and app-shaped where that helps (filters, mobile view, bookmarkable URLs). That hybrid is why it works for both power users and casual shoppers.
Related reading
If you’re new, start with usfans Spreadsheet. For the hands-on walkthrough, open the usfans Spreadsheet Guide. For a sense of what people are rating highest, read Best usfans Spreadsheet. For what’s new, see usfans Spreadsheet 2026.
Open the directory
Understanding the structure helps — using the directory helps more. Open the live sheet and pick a row. If you want to shop right now, hit Buy It Now.