ClearStock is live on the Shopify App Store.Install free →

← All blogs

Guides9 min read

Baby and kids store inventory: size runs, safety lots, and the growth clock

Baby store inventory runs on growth stages, safety lots, and gift spikes: a size-run allocation worked example and a recall-readiness checklist.

InventoryX is in development and not available today. ClearStock is the live Shopify app.

March: a couple registers at your store for a stroller and a car seat. April: the shower happens and gift buyers sweep the registry. June: the baby arrives, and someone panic-buys a swaddle in a size you were about to mark down. September: the same family is back for the six-month stage. A baby store's year isn't a season calendar — it's a stagger of clocks, one per customer, all out of phase.

That changes what inventory discipline means. Growth stages replace fashion seasons, safety rules dictate what you must be able to trace, and gift buyers purchase in patterns no smooth velocity curve predicts. This guide covers the three mechanics with a size-run allocation worked example, a lot-trace habit that makes recalls survivable, and a 20-minute recall drill. The apparel matrix in general — structuring styles, sizes, and color variants — is owned by the clothing store inventory guide; this piece stays with baby and kids.

The growth clock replaces seasons

Every customer in a baby store ages out of your products on a schedule that has nothing to do with weather. A family touches the store intensely for two to three years — newborn gear, then stages, then toys — and then mostly leaves. Demand by stage is remarkably stable across the year, but each stage is short, which produces a different buy signal than fashion retail:

  • Steady intake, fast obsolescence. Newborns arrive year-round, so the top of the ladder sells every week — but each cohort spends months, not seasons, in any given size.
  • Shrinking stages, shrinking spends. As children grow, purchases shift from multiples of basics (bibs, sleepers, bottles) to single durable items, and the customer buys less often per stage.
  • Gift dates punctuate the curve. Showers, births, and holidays create spikes on SKUs gift buyers favor — the small sizes and the photogenic items — independent of how many babies are actually at that stage.

The practical consequence: your buying calendar should run on replenishment cadence for stage basics, plus event windows for gift SKUs — not on a spring/fall fashion rhythm borrowed from adult apparel.

Size runs: shallow beats deep

Kids' sizing is a ladder of stages, not a matrix of fits. That's a gift for a small store, because a sleeper doesn't need twelve sizes — it needs four or five stages bought in the right proportion. The proportion is where the money lives.

Worked example with illustrative numbers — a 120-unit open-to-buy for one sleeper style across four stages:

Stage Share (illustrative) Units Who actually buys it
0–3M 35% 42 Gift buyers, registries, panic buyers, every baby passes through
3–6M 30% 36 Returning parents on a restock trip
6–12M 20% 24 Returning parents, second-time gifting
12–24M 15% 18 Established customers, usually fewer basics per visit

At $14 wholesale per unit (illustrative), that's 120 × 14 = $1,680 estimated committed to one style. The skew toward the top is deliberate and earned: gift buyers default to the smallest size because it's the safe choice, every baby transits 0–3M exactly once, and registry buyers purchase the whole early ladder at once. The bottom of the ladder is bought by established customers who already own last season's basics.

Two rules keep the allocation sound. First, check sell-through by stage at the end of each cycle — if 12–24M never sells through while 0–3M sells through twice, shift five points up the ladder next buy. Second, resist the temptation to carry every intermediate stage of every style; a size you stock but never sells through isn't assortment, it's slow motion dead stock, and the cleanup routine lives in the dead stock guide.

Safety lots: what the rules ask you to trace

Children's products carry obligations that adult goods don't. In the US, children's products manufactured after August 2009 must bear permanent tracking labels — a lot or batch number plus production date — so that a recall can be executed against specific batches rather than an entire model line (CPSC tracking-label requirements, accessed November 2026). The label on the product is the supplier's job; the traceability is yours.

Merchant practice that makes the requirement real:

  • Record the lot at receipt. When a PO arrives, note the batch codes printed on the cartons or hangtags against the PO line. A spreadsheet column per PO is the whole system at boutique scale.
  • Keep the chain SKU → PO → lot → quantity. The chain lets you answer the only two questions a recall asks: which lots did I receive, and which lots are still on my shelf versus already sold.
  • Screen what you stock. For goods aimed at under-threes, small-parts rules apply (CPSC small-parts guidance, accessed November 2026), and third-party certification programs such as JPMA certification (JPMA, accessed November 2026) are a reasonable stocking signal for nursery gear — not a substitute for your own supplier vetting, but a useful floor.

None of this is exotic. It's one column in a receiving log and one habit of writing the batch down before the carton goes to recycling — and it converts a recall notice from a crisis into an afternoon. Electronics retail runs the same traceability one level tighter — serial per unit instead of lot per batch — and the electronics store inventory guide shows that version.

The 20-minute recall drill

A recall is survivable if you can execute four steps fast: identify affected lots, quarantine shelf stock, list exposed customers, contact the supplier. Run this drill monthly on a rotating SKU until the answer to "can we do this?" is boring:

  • Pick one children's SKU at random
  • Find every PO for it in the last 12 months, with lot/batch codes and quantities received
  • Split the lots: still on the shelf versus sold (receiving records against sales history)
  • Note the supplier's recall/claim contact path for each affected lot
  • Time the drill — under 20 minutes passes; anything longer shows exactly which record is missing
  • Fix the missing record in the log, not in your memory

If step two stalls because PO history lives in email attachments, that's the finding — and it's also the argument for keeping POs in one place, which our purchase-order workflow guide covers in depth.

Registry and gift demand: velocity with spikes

Gift-driven SKUs break the smooth-velocity assumption in two directions. Within a week of a shower or a December gifting window, the favored sizes and items spike several times their baseline; the rest of the quarter, they behave like ordinary stock. Planning that ignores the spikes produces exactly the wrong errors: flat reordering that goes dark during gift season, and panic reordering afterward that pads the shelf with the wrong stages.

  • Buy gift SKUs on event windows. If showers cluster in spring locally, the 0–3M and registry bundles need depth entering April, not a flat monthly average.
  • Think in bundles. Registry buyers purchase sets — swaddle plus sleepers plus bottle set — so stock the bundle's components together; a bundle with one missing piece is the kayak-without-a-paddle problem.
  • Watch the returns line. Gift returns arrive in a predictable post-holiday lump and skew toward duplicate and wrong-size items. Your return policy shapes how much of that comes back as sellable stock; the sizing-specific version of this problem is covered in the clothing store inventory guide, and if you attach a small free gift to registry signups, its units follow the same planning math as any promo giveaway — the gift with purchase guide walks the sizing and cleanup.
  • Measure velocity per stage with spikes separated. Average velocity hides the pattern you actually buy against; look at the spike weeks and the quiet weeks as two different numbers.

What Shopify gives a baby boutique, plainly

As of November 2026, Shopify natively handles the retail side of this vertical well and the regulatory side not at all. Age-stage tags, collections per stage, and gift-ready bundling are standard platform work (Shopify Help Center, accessed November 2026). Native counts carry a planned date and no recurring schedule, so the boutique cadence is a calendar you own: a weekly count on fast-moving stage basics, a monthly pass on the slow tail — the count workflow that doesn't interrupt trading is covered in our Shopify counting walkthrough.

The real gap: there's no native lot tracking, so the SKU → PO → lot chain lives in your receiving log and PO records, exactly as the safety-lot section above describes. No app will conjure traceability from records you didn't keep — the log is the system.

Common questions

How many sizes should I stock per kids' style? Fewer than adult apparel: three to five stages per style is the workable range for a boutique. Allocate with a top-heavy skew — roughly 35/30/20/15 across a four-stage ladder (illustrative) — because gift buyers and every baby's path concentrate demand in the smallest sizes. Re-check the split against sell-through each cycle and shift points up or down.

What inventory records do children's product recalls require? A traceable chain: SKU to PO to lot or batch code to quantity, split into still-on-shelf versus sold. Children's products carry permanent tracking labels with batch codes and production dates under CPSC rules, so the codes exist on your goods — your job is recording them at receipt so a recall notice becomes an afternoon of quarantine and customer contact instead of a crisis.

Why do 0–3 month sizes outsell later stages? Three forces stack at the top of the ladder: every baby passes through it exactly once, gift buyers default to the smallest size as the safe choice, and registry purchases sweep the early ladder in one trip. Later stages sell only to established customers buying fewer basics, which is why the allocation example weights 0–3M at 35% and 12–24M at 15%.

How do I plan for registry and gift demand? Treat gift SKUs as spike inventory, not flat velocity: buy depth ahead of local shower seasons and December, stock bundle components together since registry buyers purchase sets, and expect a post-holiday returns lump skewed toward duplicates and wrong sizes. Reading spike weeks and quiet weeks as separate numbers beats any monthly average.

How often should a baby boutique count inventory? Weekly on fast-moving stage basics — sleepers, swaddles, bottles — plus a monthly pass on the slow tail and anything safety-relevant. Native counts carry a planned date; they do not recur, so the cadence is a calendar you own. Counts are also your shrinkage tripwire on small, high-value nursery gear.

Next step

Run the recall drill today on one SKU — every PO, every lot, shelf versus sold, timed. Twenty minutes or under and you've proved the traceability chain works; anything slower shows you the exact record to start keeping. Then pull sell-through by stage for your top sleeper and check whether the real split matches your allocation — if the bottom of the ladder never sells through, shift the points up and mark the adjustment before next buy, using the counting cadence in the inventory-counts guide.