Kids clothing size guides for Shopify need three data points before an upload can start: the size label (such as 2T or EU 92), the body measurements that match it, and the age range the size is designed for. When a team has all three, they can build variant rows correctly from the first file. Without them, the brief goes back and forth before a single product is entered.

Key takeaways

  • Kids clothing has three age tiers with different labeling conventions: infant (0 to 24 months), toddler (2T to 5T), and kids (sizes 4 to 16), and each uses different measurement anchors.
  • Upload teams need the size label, body measurements (height and chest at minimum), and the age range for each size option before they can build variant rows correctly.
  • When a range spans both infant and toddler sizes, the two age groups typically belong on separate Shopify products because their size scales are based on incompatible measurement standards.
  • Send a three-column size chart in the brief: size label, age range, and key body measurement (height in both cm and inches).
  • Specifying the size system (US, EU, or UK) and whether international labels should appear as combined option values (for example, "2T / EU 98") is a decision that affects how variant rows are structured across the whole catalog.

Why kids clothing sizing needs more preparation than adult sizing

Adult sizing generally runs on a single consistent scale: S, M, L, XL for most garments, or waist and inseam for bottoms. Kids clothing uses three distinct systems layered together, each with its own measurement anchor.

Infant sizes (0 to 24 months) are anchored on height and weight. A 3-6M garment fits roughly 60 to 70 cm and 6 to 9 kg, so a heavier or longer baby may need the next size up. Toddler sizes (2T to 5T) drop weight entirely and anchor on height and chest. Older kids sizes (4 to 16) add waist and inseam for pants.

This means an upload team working on a full kids range is dealing with three different sets of measurement fields depending on where in the size range they are. Sending one chart that covers all three tiers, with the right fields for each, removes a large chunk of back-and-forth.

A second point of complexity is international standards. US and EU size labels for the same garment look nothing alike. For the fashion product upload service this is a common briefing gap: a store selling internationally needs either a combined option value ("2T / EU 98") or separate listings, and that decision should be made before uploading begins.

Kids clothing size guides for Shopify: core data fields

Size chart data laid out on a workspace with garments sorted by age range
A complete size chart includes label, age range, and body measurements for each size option.

The minimum set of fields an upload team needs for a kids clothing size guide. These fields align with the data that Shopify stores per product variant (as of November 2026). See adding and updating products in Shopify for how variant options are entered in the admin:

FieldWhat to includeExample
Size labelExactly as it will appear in the Size option in Shopify2T, EU 98, 3-6M
Age rangeMinimum and maximum age in months or years2 to 3 years
HeightIn both cm and inches92 to 98 cm (36 to 38 in)
ChestIn cm and inches; skip for newborn and 0-3M if no chest data is available54 cm (21 in)
Weight (infants only)Approximate range in kg and lb; helps caregivers choose between overlapping sizes6 to 9 kg (13 to 20 lb)

For pants and bottoms in kids sizes (4 and up), include waist and inseam in the same units. If the garment is a one-size accessory such as a baby hat, note that explicitly: the team will set up the size option as "One Size" and confirm there are no other values expected.

Size systems: US, EU, and UK at a glance

If the store sells to international markets, the brief should specify which system the store uses and whether the other systems appear alongside it. The table below shows the three most common systems mapped against age ranges, based on widely published sizing standards (as of November 2026). EU sizes correspond to body height in centimeters: a size labeled EU 98 fits a child approximately 92 to 98 cm tall. For a full reference on how Shopify handles size options as product variants, see the Shopify Help Center guide to product variants.

Age rangeUS labelUK labelEU label
NewbornNB0-1M50/56
0 to 3 months0-3M0-3M62
3 to 6 months3-6M3-6M68
6 to 9 months6-9M6-9M74
9 to 12 months9-12M9-12M80
12 to 18 months12-18M12-18M86
18 to 24 months18-24M18-24M92
2 to 3 years2T2-3Y98
3 to 4 years3T3-4Y104
4 to 5 years4T4-5Y110
5 to 6 years5T / 55-6Y116
6 to 7 years66-7Y122

For a store that uses US labels only, the team will enter each US label as a separate variant value. For a store that lists both US and EU labels, the combined option value approach ("2T / EU 98") keeps the product page clean while covering both markets. Either way, the decision should be consistent across the catalog so variant rows follow a single naming convention.

When to split infant and toddler into separate products

This is the question that most often causes delays on a kids upload. The short answer: when a range covers both infant sizes (0 to 24 months) and toddler sizes (2T and up), those two groups usually belong on separate Shopify products.

The reason is that infant and toddler sizes use different measurement anchors. Infant sizes are built around height and weight. Toddler sizes drop weight entirely. If you combine them into a single Size option, a dropdown showing "0-3M, 3-6M, 6-9M, 9-12M, 12-18M, 18-24M, 2T, 3T, 4T, 5T" looks correct on the merchant side but becomes confusing to shoppers who are used to either month-based or year-based labels, not a mix.

A clearer structure for most stores is two products: "Baby [Name] (0 to 24 months)" and "Toddler [Name] (2T to 5T)." If you want them on one product, include that instruction explicitly in the brief. The upload team will follow whatever structure the merchant specifies, but they need that decision in writing before they build the variant rows.

This is similar to how menswear data fields require a decision about whether two-part sizes (waist plus inseam) go into separate options or combined values: either approach works in Shopify, but the team needs a clear rule to follow consistently.

What to put in the brief for a kids clothing upload

Children's clothing items labeled with size tags and sorted for catalog data entry
Consistent size labels across the catalog start with a clear brief before uploading begins.

A brief for a kids clothing upload that covers size guide data should include:

  1. The size system the store uses (US, EU, UK, or combined labels like "2T / EU 98").
  2. A size chart with at least three columns: size label, age range, and height. Add chest and weight for infant sizes. Add waist and inseam for older kids pants.
  3. The infant/toddler split decision: whether products spanning both age groups should be listed as separate products or as a single product with a combined size range.
  4. Any sizes marked "One Size" (baby hats, infant mittens, bandana bibs): note which products these are so the team doesn't add empty size options.
  5. The measurement units: confirm whether the store displays cm only, inches only, or both. This determines how the size guide metafield or page content is structured.

For the size guide itself (the chart shoppers can open on the product page), that is usually a Shopify page or metafield that the merchant creates separately. The Shopify product data entry service handles the variant structure and size option values; the size guide page link, if one exists, can be added as a metafield during the same job.

You can see how the same brief approach works for other product types in the womenswear size runs guide and the frame size charts guide for bike stores.

For more guides on fashion product uploads, see the Women's Clothing hub.

Frequently asked questions

Can I use both US and EU size labels on the same Shopify product?

Yes. You can include both in one Size option value (for example, "2T / EU 98") or list them as separate options. The combined approach reduces shopper confusion on internationally marketed stores. Whichever you choose, include that instruction in your upload brief so the team applies it consistently across every product in the range.

What if my supplier uses different size labels from my store?

Include both sets of labels in the brief: the supplier's label and the label you want in the store. For example, your supplier might label a garment "86" (EU) while your store sells in US sizes (12-18M). The upload team will map the supplier's size to the store label during data entry. A two-column reference table in the brief (supplier label to store label) is a clear and practical approach.

Should I include weight in the size guide for older kids (5 years and up)?

No. Weight as a sizing guide is standard for infant sizes (0 to 24 months), where a heavier or longer baby may need a different size than the age range suggests. For toddler and older kids sizes, height and chest measurements are the standard anchors. Including weight for older sizes adds clutter without helping shoppers choose.

What is the difference between a size guide and a size chart for Shopify products?

They mean the same thing in product data work. A size chart is a table of size labels with their body measurements. When the upload team refers to the size guide, they mean that table. Whether your store displays it as a size guide popup, a linked page, or a plain text section is a separate decision about the product page layout, not the data entry.

Do I need a separate size chart for each product, or can I use one chart for the whole range?

One chart for the range is usually cleaner if the same size labels apply consistently (for example, all tops use the same 2T-to-5T scale with the same chest measurements). If a product type has different sizing (infant onesies vs. toddler jackets), include a separate chart for each product group in the brief. The upload team will reference the chart that matches each product's category.