Say a mountain bike store is adding 50 models to Shopify, each available in four or five frame sizes. The store uses Small through X-Large labels on its website, the supplier spreadsheet lists centimeters, and the manufacturer's PDF shows stack and reach measurements the store doesn't currently display anywhere. The upload team receives all three files and asks: which set of size labels goes into Shopify, and what do we do with the rest?
The answer depends on decisions the store owner makes before the job starts. Bike frame charts for upload teams are more than a size guide. They map how the store sells sizes to how the catalog is structured, and they tell the team which measurements enter Shopify as variant fields, which go into descriptions, and which the store doesn't need at all.
Key takeaways
- Frame sizes exist in at least three notation systems (S/M/L, numerical centimeters, and numerical inches). Your upload team needs to know which system your store uses before they create a single variant.
- In Shopify, frame size is a variant option. Each size needs its own SKU, weight, barcode, and inventory quantity.
- Wheel size is a fixed specification for most models, not a variant. It becomes a second variant option only when a model genuinely ships in two wheel sizes.
- Rider height guide data belongs in the product description or a metafield, not in a Shopify option field.
- Send your upload team a size chart, the notation system you use on your storefront, weight by frame size, and barcode data before the job starts.
Why frame size notation needs deciding upfront
There is no single standard for bicycle frame sizes. Road bikes are typically measured in centimeters (50 cm, 52 cm, 54 cm, 56 cm, 58 cm, 60 cm). Mountain bikes often use Small through X-Large labels. Kids' bikes use wheel diameter in inches (12 in, 16 in, 20 in, 24 in). Some brands use their own custom codes: a major road brand uses S1 through S6, and another uses a system tied to stack height.
The same brand may use different notation across product lines, and a supplier spreadsheet may mix systems within one file.
Upload teams run into trouble when the store's storefront labels differ from what appears in the supplier file. If the supplier lists "54 cm" and the store sells "Medium," the team needs a mapping table, not the raw data alone. Without it, they either guess or stop and ask, which slows the job.
Before the upload job starts, decide:
- What size labels do customers see on your product pages?
- Do different bike categories (road, MTB, kids') use different systems?
- Is there a supplier-to-storefront size conversion table the team should follow?
Write these decisions down and include them in the handover file. The upload team can then set up variant options consistently across every model.
How frame size becomes a Shopify variant
Each frame size is a separate product variant in Shopify. As of November 2026, Shopify supports up to three options per product and up to 2,048 variant combinations per product, based on its variant documentation. For a typical bike model with five frame sizes, that works out to five variants under a single product.
The option name for frame size is usually "Frame Size." Option values are the labels customers see, for example "S," "M," "L," "XL," or "2XL." If a model is also available in two colors, the product has two options (Frame Size and Color), and each size-color combination becomes its own variant.
Each variant in a bike catalog typically needs:
| Field | Notes |
|---|---|
| SKU | Must be unique per size; most suppliers include size codes in the SKU |
| Weight | Larger frames weigh more; accurate weight affects shipping rate calculation |
| Barcode (GTIN) | Each size has its own barcode; confirm with your supplier |
| Price | Usually the same across sizes for most bikes; note any exceptions |
| Inventory quantity | Per size, per location |
Barcode data follows the GS1 global GTIN standard, where each product variant has a unique 13-digit EAN or 12-digit UPC. If your supplier file does not include GTINs by size, request the size-level barcode list before the upload job starts.
If your supplier file does not include weight by size, ask for it before the upload job starts. A single missing weight field means either estimated data in the catalog or a request to pause the job and wait for the information.
For keyword search and filter collections, the option name matters. "Frame Size" as a named option makes it straightforward to build collections based on size, since Shopify's collection conditions can filter by option values (as of November 2026). Inconsistent naming across models, for example "Size" for some and "Frame Size" for others, makes this harder to maintain later.
When wheel size is a variant and when it's a specification
Most bike models have a fixed wheel size for each model. A specific aluminum mountain bike comes in 29-inch wheels regardless of which frame size you order. In that case, wheel size is a specification that belongs in the product description, not a Shopify variant option.
Wheel size becomes a variant option only when a single model is offered in two different wheel sizes, for example a mountain bike sold in both 27.5-inch and 29-inch configurations. In that case, the product has two options: Frame Size and Wheel Size, and each combination is its own variant.
Adding wheel size as a variant option when it doesn't vary inflates your variant count, creates empty combinations, and makes the product page harder for customers to use. For the upload team, it also increases the rows they need to enter.
One clear rule: if the wheel size is the same for every frame size in the model, list it once in the product description as a specification and leave it out of the variant options.
The rider height guide in Shopify
Many bike brands publish a rider height recommendation for each frame size. For example, a medium frame might be recommended for riders between 170 cm and 180 cm (5 ft 7 in to 5 ft 11 in). This information helps buyers choose the right size before purchase.
In Shopify, there is no built-in variant field for rider height range. The options are:
- Description table: A formatted HTML table in the product body shows all frame sizes alongside their recommended rider height ranges. This is visible to everyone and requires no additional theme setup to maintain.
- Metafield: If the store uses a theme that displays metafields on the product page, a "Rider Height" metafield can hold the range for each variant and display it next to the size selector.
For most stores, a description table is the more practical choice. The upload team can enter it once per model, and it doesn't require any theme customization. The metafield approach is worth considering if the store has a large range and wants the height guide to appear dynamically next to the selected size, but it requires additional setup that goes beyond a standard upload job.
Decide which approach you want before the job starts, and include a sample in the handover file so the team can apply it consistently across every model.
Geometry data: what to send and what to skip
Bike geometry data (stack, reach, standover height, seat tube length, and effective top tube length) gives cyclists precise information for comparing fit. High-volume road bike and gravel bike retailers often include full geometry tables. Most general bike stores don't need to.
Before deciding, consider:
- Do your buyers use geometry data to make purchase decisions? Serious cyclists do; casual buyers usually don't.
- Does your brand's target customer have the knowledge to interpret stack and reach measurements?
- Can you maintain this data reliably when new models arrive?
If you decide to include geometry, the upload team needs it in a structured format per model and per size. A CSV or spreadsheet with columns for each measurement, one row per size, is the most practical format. The team will then format it as an HTML table in the product description.
If you decide to skip it, leave it out entirely. A partial geometry table (some models with data, most without) creates an inconsistent store experience and raises questions from buyers that the team can't anticipate when setting up the catalog.
What to include in bike frame charts for your upload team
The handover package for a bike catalog upload is more involved than for most product categories. Here is what to prepare before the job starts.
A complete handover typically includes:
- Size notation decision: Which labels appear on your product pages (S/M/L, cm, or inches), and a conversion table if your supplier file uses a different system.
- Frame size chart per model or category: The option values in the exact order they should appear on the product page.
- Weight by frame size: Accurate weights for each size in every model. If your supplier can only provide one weight per model, note that and the team will apply it uniformly.
- Barcode data by size: GTINs or EANs for each size variant. If a size has no barcode, confirm that so the field can be left blank intentionally.
- Rider height guide format: Whether to use a description table, a metafield, or nothing, with a sample for one model.
- Wheel size guidance: Whether wheel size is a specification (goes in description) or a variant (goes in the options), and which applies to which models.
- Geometry inclusion decision: Yes or no, and if yes, the data file for each model.
For our Shopify product data entry service, we work from exactly this kind of brief. It removes the back-and-forth that slows jobs down when the team encounters a decision point without an answer on file.
For more on what a full handover looks like across product categories, the sports and outdoor product upload service page covers how we handle data-heavy outdoor and sports catalogs.
If you're new to preparing product handovers in general, the guide on what to send your upload team walks through the core document format that works across most categories before you add product-specific layers like frame size charts.
For how other physical product categories handle dimension data, the article on furniture dimensions for upload teams covers the similar challenge of weight, size, and assembly data for flat-pack and furniture ranges.
Frequently asked questions
Can I use both S/M/L and centimeter labels for the same frame sizes on Shopify?
Yes, but Shopify's option values can only display one label per variant. The practical approach is to combine them: use values like "S (50 cm)" or "M (54 cm)" as the option values. This shows both systems to the customer without requiring two separate options. Decide on the format before the upload job starts so the team applies it consistently.
What if different bike models in my catalog use different frame size notation?
Document the notation system for each model in the handover file, or group models by notation type. For example, "road bikes use cm notation; MTB uses S to XL." The upload team then follows the correct system per model. Mixing notation across a range without a documented reason causes confusion for buyers comparing products.
Does each frame size need its own SKU?
Yes. Each Shopify variant requires a unique SKU to track inventory and process orders accurately. Most bike suppliers already include size-specific SKU codes in their product data. If the supplier file has only one SKU per model, ask for the full size-level SKU list before the upload job starts.
Can I add rider height range as a Shopify variant option?
No. Rider height is a recommendation to help buyers choose a size, not a product attribute that changes what they receive. Adding it as a variant option would create confusing combinations (for example, "Medium, 170-180 cm") and double the variant count for no practical benefit. Keep it in the description table or a metafield, as described above.
My supplier lists a size as 'one size fits all' for some accessories. How should the team handle that?
For accessories where frame compatibility or sizing is irrelevant (bottles, saddle bags, lights), leave the size option out entirely. The guide on one-size accessories and empty options on Shopify covers what happens when size options are added to products that don't need them and how to avoid the problem.
