HooBuy Shoes Spreadsheet: Sizing & QC Checklist

For a shoe spreadsheet, record the exact size label and the sizing method behind it. Plan QC views for both shoes, labels and outsoles, then keep packaging choices separate from the fit decision.

A useful HooBuy shoes spreadsheet does more than collect product links and sizes. Shoes combine listing identity, several sizing systems, foot measurements, variant-specific construction and later warehouse evidence. If those fields are compressed into one note, two candidates that look similar can become falsely equivalent.

The row should answer three questions: which exact listing and option did the buyer intend, what sizing evidence supported that choice, and what observable checks must happen after arrival? It should not predict comfort or quality. The goal is a reproducible handoff from product discovery to order record to QC.

Choose the row unit before adding columns

Use one row for one source listing plus one intended option combination. If the same page offers two constructions, colorways or sizes under consideration, give each candidate a separate row. This prevents one selected-state price, chart or note from drifting across variants.

Give every row an internal candidate ID. Preserve the final source URL, marketplace, visible item ID, seller or shop identifier, observation date and original shared link where useful. The seller-page checklist explains when identity is strong enough to save.

Build an identity block that survives link changes

Keep translated labels in separate columns. A translation helps the editor read the row, but the original selector text is what can be matched to the order. Never replace a cryptic source label with a guessed model name.

Separate size label, sizing system and body evidence

A displayed number is incomplete without its system. Record the exact label selected, the stated sizing convention if the page identifies one, and any seller conversion separately. Do not assume that two listings using the same number describe the same internal length or fit.

Create fields for buyer foot length, buyer foot width and the measurement method and date. These are decision inputs, not product facts. Then record the seller's recommended foot-length range, stated internal or insole length, and chart unit only when the exact listing supplies them. Leave missing fields blank and add a blocking question instead of calculating unsupported conversions.

Preserve how each measurement was defined

“Length” may describe the foot, removable insole, interior space, outsole or shipping box. Give each its own column and record endpoints. A seller chart tied to foot length should not be compared directly with another listing's outsole length.

Add a field for tolerance or uncertainty only when the source provides it or when your own measurement method justifies a range. Do not invent precision by converting a rounded chart to several decimal places. Store the original unit and the normalized value together so later editors can audit the conversion.

Plan QC fields before the item arrives

QC requests work better when written from the pre-order record. Create expected-evidence fields for pair identity, selected color or version, left and right size labels, full outsoles, front and rear shape views, side profiles, visible defects, included components and packaging state. Mark each as required, useful or unnecessary for this candidate.

That priority prevents a spreadsheet from requesting every possible photograph. A high-consequence uncertainty, such as two unreadable size labels, deserves a targeted request. A feature already visible from a clear matching view may not.

Keep claims and later observations apart

Seller material, sole, cushioning or construction descriptions belong in attributed claim columns. Warehouse photographs can confirm visible labels, shapes, components and condition, but not hidden composition, support under use or durability. Use separate “seller states” and “QC shows” fields.

Do the same for stock and dispatch. A page state observed during discovery does not guarantee future availability. Record the time checked and move the row to recheck if it waits before ordering.

Add packaging and parcel-planning fields

Shoes can create a packaging trade-off. Record whether a retail box is included or only pictured, whether it has identity or collector value, and whether removal is merely being considered. Add warehouse-measured item weight and box dimensions only after they exist; before arrival, label any seller values as seller-stated estimates.

Do not put an estimated international shipping charge in the product-price cell. Keep product amount, domestic seller freight, optional services and later parcel amounts separate. This lets the researcher compare product finds without presenting incomplete landed cost as a bargain.

Use workflow statuses, not a vague score

1. Discovered: link saved but identity not fully checked.
2. Verified: final page, seller and intended option are reproducible.
3. Size unresolved: intended size lacks comparable evidence.
4. Ready to order: identity, size basis and blocking questions are closed.
5. Ordered: platform order ID is attached to the same candidate.
6. QC pending: warehouse evidence has not been reviewed.
7. QC decision: ship, seek evidence or inspect current after-sale options.
8. Archived: dead, rejected, replaced or completed, with reason.

Scores can hide fatal gaps. A row with strong photos and a low price but an unresolved size is not “mostly ready.” The blocking status should control.

Worked comparison: two size-42 candidates

Candidate A and Candidate B both display size 42. A ties that label to a listing-specific foot-length chart and keeps the exact colorway and seller identity. B shows a generic conversion image, gives no endpoints and changes price when another version is selected.

The spreadsheet should not call them equal. A can proceed if its chart matches the buyer's measured requirement and no other blocker remains. B stays on hold with one question: what foot-length or internal-length range applies to the exact intended version? The lower headline price does not resolve the evidence gap.

After arrival, attach the order ID and warehouse item ID to the original row. Record whether both received size labels match the order and whether the requested outsole and shape views exist. Do not overwrite the seller chart with the QC result; they answer different questions.

Minimum shoe-row checklist

• Stable candidate ID and final source identity.
• Seller and item identifiers where visible.
• Complete original option labels.
• Selected-state amount, currency and check date.
• Size label and sizing system kept separate.
• Buyer foot measurements with method and date.
• Seller chart values with defined endpoints and unit.
• One blocking size or inclusion question where needed.
• Prioritized later QC fields and current status.
• Packaging and weight values marked by source and stage.

A good row prevents a false comparison

The spreadsheet is valuable when another editor can reconstruct the intended shoe, understand the size basis and know which later photograph could change the decision. It should show uncertainty instead of hiding it in notes.

Protect the record from silent edits. Use a “last verified” date for the live page and a separate “row updated” date for editorial changes. If a seller changes the chart, option name or selected-state amount, append the new observation and mark which version informed the order. Do not replace the evidence that explains an existing warehouse item.

Archive rejected candidates with a short reason such as identity unresolved, size method incomparable or intended option unavailable. That history prevents the same weak listing from returning to the shortlist under a new nickname and helps future searches target the missing evidence rather than the same image.

Use the broader spreadsheet workflow for maintenance and the product-link guide when a destination changes. Keep identity, sizing, QC and packaging as connected but separate evidence blocks. That structure will not guarantee fit, but it will stop two incomplete records from pretending to be the same shoe.