PikoBuy Shoes Spreadsheet: Size and QC Fields That Matter

Start with shoe identity, not a size cell

Shoes that share a familiar silhouette can still be different offers. Before entering any size, save the final seller URL, marketplace, product identifier, store name, listing title, intended model, colourway and check date. Keep the original option text next to your interpretation. That evidence lets you tell a source change from a simple update later.

PikoBuy's current process asks the user to confirm product specifications, colour and size, then choose specifications, colour, size and quantity when submitting the purchasing order. The platform also says prices remain subject to the actual purchase. Your row should therefore describe one selectable configuration, not the whole listing.

Use separate fields for version or batch wording, colour label, size label, quantity, included parts and selected price. If the page groups adult and youth sizes, shoes and accessories, or standard and premium versions, record the branch that produced the selected price. A photo gallery, headline price or translated title cannot substitute for that state.

Give the source a status: live and matched, live but ambiguous, replaced, unavailable or unchecked. A matched source means the page currently shows the intended shoe and option. It does not prove quality, authenticity, stock or fit.

Build a size evidence chain instead of converting by habit

A shoe size number is incomplete without its system. Save the visible label exactly, then add the stated system—such as EU, US men's, US women's, UK, centimetres or another seller-defined scale—only when the page identifies it. Do not infer a system because a number looks familiar.

Keep four different concepts in separate columns:

• Foot target: the wearer's measured longer-foot length and any width concern.
• Seller recommendation: the size or foot-length relationship printed on this listing.
• Selected label: the exact option that will be sent in the order.
• Physical evidence: a later insole, outsole, label or other warehouse measurement, including method and units.

These values are related but not interchangeable. Foot length is not automatically insole length. An outsole includes exterior structure and is not a direct fit measurement. A printed label confirms the received marking, not the internal space. Even an insole measurement can mislead if the insole is curved, difficult to remove or measured along a different path.

Measure both feet on the same occasion, using the longer result as the planning input, and note socks or orthotics that materially affect the intended fit. Record the tool, units, endpoints and date. A rounded measurement copied from memory is weaker evidence than a reproducible one.

Read the seller size chart as a listing-specific claim

Capture the chart image or values with the product identifier and date. Record its title, units, body part or shoe component, endpoints, tolerance note and any recommendation text. If the method is unclear, write “method not stated.” Do not silently combine a centimetre column from one listing with a size label from another.

Check whether the chart changes when the model or option changes. Some pages place several charts in one description, show a generic marketplace chart or use recommendation language that does not match the selectable labels. A chart earns a matched status only when the connection to the intended option is clear.

Keep seller statements in their own evidence class. “Choose one size larger” is advice, not a measurement. “Suitable for wide feet” is a claim unless the page defines width. A conversion table found elsewhere may help form a question, but it cannot override the seller's current option label.

When the chart and selector conflict, pause. Ask which label corresponds to the intended foot-length range, then save the answer with its source and date. The safest spreadsheet exposes the conflict rather than resolving it with a guessed universal conversion.

Turn fit worries into observable warehouse QC fields

PikoBuy's public guide says warehouse handling includes check-in, photo confirmation and defect checking. Its shipping terms also say inspection photos are available and that additional detailed photos may be purchased, while professional inspection cannot be provided for every special product. That supports a focused request, not an assumption about a fixed photo count or guaranteed measurement service.

Plan checks in priority order. First confirm identity: both shoes, selected colour, printed size labels, model details and included accessories. Next inspect visible condition: major stains, tears, deformation, detached parts, obvious glue overflow, mismatched panels and damage to closures. Then request only measurements that have clear endpoints and could change the decision.

A measurement request should name the object, path, start point, end point, units and required visibility. “Measure the shoe” is vague. “If the insole is removable without altering the product, show the tape from heel edge to longest toe edge in one frame” is auditable. If the method is unavailable, record the evidence gap rather than treating another dimension as equivalent.

For paired products, add symmetry fields: left and right label match, colour match, major panel alignment, sole shape, visible height and accessory count. Photos can reveal visible differences, but they cannot prove comfort, cushioning performance, material composition, long-term durability or authenticity.

Keep return eligibility in view. PikoBuy's current return rules identify new sneakers as a category whose anti-theft buckle and tamper-proof sticker, if present, must remain intact and functional. Do not request removal of packaging, labels or accessories before checking whether that action could affect returnability.

Record weight and packaging without turning them into quality scores

Shoe finds often reach the shipping decision with weak packaging data. Create distinct fields for seller-stated item weight, warehouse item weight, shoebox included or unknown, outer packaging state, evidence date and source. Never copy one pair's value across every size or version.

Weight helps plan a parcel, but heavier does not mean better. A scale value may include a box or packing material; a seller estimate may describe another size. Mark each figure as seller-stated, warehouse-observed or estimated, and do not mix them in one “weight” cell.

Record whether the original box is part of the buyer's acceptance criteria. It may provide structure or collectible value, but it can also add volume. Do not promise savings from removing it, and do not request removal until return consequences and protection needs are understood. The product row should hand off evidence to later parcel planning, not make an international-shipping choice before the item arrives.

Worked comparison: two similar listings, two different evidence chains

Imagine two visually similar running-shoe listings. Listing A offers sizes 39–45 and shows a chart linking labels to foot length, but it does not explain width. Listing B offers the same number range, uses a lower headline price and shows an outsole-length table that applies only to one model family.

1. Create separate rows with final URLs, product IDs, store identities and check dates.
2. Select the intended dark colour and size state on each page; save the resulting option text and price scope.
3. For A, label the chart value “seller foot-length recommendation.” Do not call it an insole measurement.
4. For B, record “outsole length” and the named model family. Mark the target option's chart match unresolved.
5. Add the wearer's longer-foot measurement and width concern without automatically choosing a size.
6. Plan identity, paired-label and visible-condition QC for both candidates. Add one clear insole request only if that evidence is decision-critical and feasible.
7. Record packaging and weight as unknown until supported by the selected listing or warehouse record.
8. Keep A as a qualified candidate; pause B until the chart-to-option relationship is clarified.

Listing B may still become the better choice, but its lower price and similar pictures do not cure the evidence mismatch. The spreadsheet keeps the two offers comparable without pretending they are equivalent.

Use a shoe-specific order gate

Mark a row order-ready only when source identity, exact option, size basis, selected price and critical unknowns are documented. Mark it research when a seller answer or measurable field could change the choice. Mark it reject when the intended variant is absent, the chart belongs to another product, the pair cannot meet a must-have requirement or the link has been replaced.

Before submitting through PikoBuy, compare the imported product, colour, size, quantity and price with the saved source state. After warehouse arrival, append evidence rather than overwriting the pre-order record. Record labels, visible condition, measurements, weight and packaging with fresh dates. If the received identity or condition differs, decide within the current return window instead of waiting for parcel planning.

A good shoes spreadsheet does not predict fit. It makes the reasoning inspectable: what was selected, what the seller claimed, what was measured, what remains unknown and which uncertainty the buyer accepted.

Continue the evidence workflow

Use the seller-page checklist to qualify the offer, the source-link guide to preserve its origin, and the warehouse photo routine when the selected shoes arrive.