Sneaker Spreadsheet Database

Sneakers are the highest-traffic category inside the Hipobuy Spreadsheet. They also carry the highest risk — fakes with poor materials, wrong colorways, and obvious stitching flaws flood the market daily. The Sneaker Spreadsheet Database exists to filter that noise. Every entry includes size runs, price tiers, batch codes, and a live QC gallery. If a pair is listed here, it has passed at least one verification cycle.

Database Architecture

The sneaker module is structured as a relational index. Each product record contains a primary SKU, linked batch identifiers, seller node IDs, and a composite trust vector. The trust vector is made up of four sub-scores: Material Accuracy (MA), Shape Precision (SP), Stitching Consistency (SC), and On-Foot Verification (OFV). These four numbers are averaged into the overall Sneaker Authority Score shown on the main spreadsheet view.

When a new batch is released — for example, an updated version of a Jordan 1 Chicago — the database does not overwrite the old record. Instead, it forks the record, assigns a new batch ID, and runs the scoring pipeline from scratch. Buyers can then compare the old batch and the new batch side by side before making a purchase decision.

Size Run Accuracy

One of the biggest pain points in replica sneaker shopping is size inconsistency. A US 10 in one batch may fit like a 9.5, while another batch runs true. The database solves this through an aggregated size mapping table. Every verified purchase submits a "size accuracy report" — the buyer states what they ordered, what arrived, and how it fit. Over time, this builds a statistically reliable size translation layer for each batch.

Price Tier Mapping

The database splits sneakers into four price tiers: Budget (under $40), Mid-Range ($40–$80), Premium ($80–$150), and Luxury ($150+). Each tier has its own expected quality floor. A Budget pair with a Material Accuracy score above 80 is considered a "diamond in the rough" and flagged with a special icon. A Premium pair below 85 triggers a warning badge, signaling that the price may not match the quality.

Drop Calendar Integration

The sneaker module is synced with a drop calendar that tracks factory production schedules, not retail releases. When a factory announces a new batch, the database creates a pre-order node. Buyers can set alerts for specific SKUs, and the system will notify them when the batch goes live, when QC samples arrive, and when the first verified purchases start reporting back.