PikoBuy Hoodie Spreadsheet: Fabric, Measurements and Weight

Make the row describe one purchasable hoodie

A broad title such as “heavy oversized hoodie” is not an identity. Begin with the final seller URL, marketplace, product identifier, store name, listing title and the date checked. Then save the exact colour, size, version, quantity and selected price state. If an option menu mixes hoodies, zip-ups, sets or accessories, record the branch that creates the price.

PikoBuy's current guide tells buyers to confirm specifications, colour and size, then select specifications, colour, size and quantity when submitting an order. It also says prices are subject to the actual purchase. That makes the chosen configuration—not the headline card—the useful unit of comparison.

Keep the original option wording beside a plain-English working note. The translation helps you scan the sheet; the source wording protects the order from a subtle variant mismatch. Add a live-page status such as matched, ambiguous, unavailable, replaced or unchecked. “Matched” means the intended offer is visible today. It does not mean stock, quality, authenticity or fit has been guaranteed.

Split fabric language into claims you can audit

Do not put “cotton hoodie” into one all-purpose material cell. Use separate fields for seller-stated fibre composition, fabric construction, lining or inner finish, fabric weight claim, care label evidence and the date each claim was observed. Preserve percentages exactly when shown and write “not stated” when they are absent.

Fibre, structure and surface are different ideas. Cotton and polyester are fibre names; fleece, French terry and knit describe constructions or finishes; brushed, washed and heavyweight can describe treatment or marketing. A page may use several of these words without explaining the composition. Keeping the terms separate prevents a smooth marketing phrase from becoming a false specification.

GSM, when a seller provides it, normally describes mass per unit area of fabric. It is not the finished garment weight. A hoodie with a lower fabric-weight claim can weigh more because of size, panels, hardware, lining or decoration. Record GSM as seller-stated unless supported by a defined measurement, and never back-calculate composition or warmth from it.

A visible care or fibre label can support what was printed on the received garment. It cannot independently verify that the fibres match the percentages. Likewise, a warehouse photo can show nap, knit direction, pilling, staining or a surface mismatch, but it cannot prove hand feel, warmth, breathability, shrinkage or long-term durability.

Record flat measurements with named endpoints

Size letters are labels, not dimensions. Save the seller's size chart with the product identifier and check date, then record each measurement exactly as defined. Useful hoodie fields can include chest width, body length, shoulder width, sleeve length, hem width and hood dimensions, but only when the listing gives a method or a warehouse request can define one.

Every measurement needs four parts: the garment state, start point, end point and units. “Chest 60” is ambiguous. “Garment laid flat; straight across from underarm seam to underarm seam; 60 cm” is reproducible. Specify whether the zip is closed, the ribbing is relaxed, the hood is excluded and the sleeve runs from shoulder seam or centre back.

Do not silently double a flat chest width and call it body circumference unless your sheet clearly labels the calculation. Do not compare a raglan centre-back sleeve length with a set-in shoulder-to-cuff length. If the seller chart uses another path, retain both values and mark them non-equivalent.

Measure a hoodie you already own using the same endpoints. Store that reference garment, date and method in the sheet. The comparison is more useful than choosing by a generic S–XL conversion, but it remains a planning tool: cut, stretch, fabric thickness and personal preference can change fit.

Label every weight by object, source and stage

One “weight” column causes expensive confusion. Create distinct fields for seller-stated garment weight, warehouse item weight, packaging included, packed parcel contribution and evidence date. Add size and variant scope because a larger hoodie, zip hardware, embroidery or lining can change the result.

Weight and fabric weight must stay separate. A 400 GSM claim does not mean a 400-gram hoodie. Record the wording and units exactly. If a seller gives a range, save the range and the sizes it covers rather than selecting the convenient midpoint. If the warehouse later provides a figure, append it instead of replacing the seller claim.

PikoBuy's shipping estimator currently asks for destination, product type, weight, length, width and height. That is why the spreadsheet should pass evidence forward without pretending an item-only figure is a final shipping quote. Folding, compression, outer packaging and other parcel contents remain unknown until packing.

Write the QC plan before the hoodie reaches the warehouse

PikoBuy's public guide says warehouse handling includes check-in, photo confirmation and defect checking. Its shipping terms say buyers can view inspection photos or purchase additional detailed photos, while professional inspection is not available for every special product. The practical response is a short, observable priority list—not an assumed photo count or a promise of laboratory verification.

Start with identity: exact colour, size label, version, closure, pocket layout, hood construction and included parts. Then check visible condition: stains, holes, tears, broken hardware, major print damage, uneven embroidery, detached seams and obvious panel mismatch. For a zip hoodie, include zipper alignment and visible operation evidence when available.

Request measurements only when they can change the decision. Name the endpoint and show the tape in the same frame where feasible. A request such as “lay flat, zip closed, measure straight across the chest from underarm seam to underarm seam in centimetres” produces stronger evidence than “check size.” Record whether the method was followed.

Before asking for label removal, packaging disposal or other irreversible handling, check the current return rules. PikoBuy's return page says eligibility depends on seller participation, resalable condition, time in the warehouse and packaging requirements. A QC request should reduce uncertainty without damaging the option to return.

Worked comparison: two “heavyweight” hoodie finds

Suppose Listing A and Listing B both use “heavyweight” in the title. A states 80% cotton and 20% polyester, shows a 420 GSM claim, defines chest width and body length, and offers separate pullover sizes. B shows a lower selected price and a “500g” badge, but mixes zip-up and pullover versions and does not explain whether 500g refers to the garment, a sample size or packed weight.

1. Create separate rows with final URLs, product IDs, seller identities and check dates.
2. For A, record fibre percentages and GSM as seller-stated claims. Save the chart endpoints and intended colour-size option.
3. For B, preserve “500g” verbatim, mark object and size scope unknown, and record the exact pullover branch that produced the price.
4. Compare the charted chest and length with one reference hoodie measured by the same method.
5. Give both candidates the same identity, label, decoration and visible-condition QC priorities.
6. Add one chest measurement request only if the chart evidence remains decision-critical.
7. Keep warehouse weight and packed volume unknown until evidence exists.
8. Mark A order-ready if it meets the acceptance brief; keep B in research until its version and weight scope are clarified.

B may ultimately be better, but a lower price and a larger-looking number do not resolve the evidence gaps. The spreadsheet shows exactly what must be confirmed rather than rewarding whichever title sounds more substantial.

Use a three-state hoodie decision gate

Mark a row order-ready only when the source is live, the exact option is selectable, measurement basis is usable, material claims are properly scoped, the selected price is current and critical unknowns are documented. Mark it research when one seller answer, chart match or defined measurement could change the choice. Mark it reject when the intended version is unavailable, option and chart cannot be matched, or a must-have measurement is outside the accepted range.

Before submitting the purchase, compare the imported title, colour, size, quantity and price with the saved state. After arrival, add the warehouse date, observed labels, defined measurements, visible-condition result, item weight and packaging state. Never overwrite the pre-order record; the difference between promise and observation is valuable.

A good PikoBuy hoodie spreadsheet does not certify fabric or predict fit. It makes the decision explainable: which product was chosen, what the seller claimed, how measurements were defined, what the warehouse showed and which uncertainty the buyer knowingly accepted.

Continue the product-record workflow

Use the seller-page checklist to qualify the offer, the shoe field guide when comparing category methods, and the warehouse photo routine after the selected hoodie arrives.