The automation that changes the numbers for a baby and children’s store is age-based: you know the child’s stage, so you can predict what the parent needs next and email it before they go looking. A newborn’s parent buys different things at three months, at nine months, at two years — and that timeline is stable enough to automate. Layer replenishment on top for the consumables (diapers, wipes, formula) and size-up prompts for clothing and shoes, and you’ve built a system that follows a customer through years of purchases instead of hoping they remember you. This guide covers how to set that up, what to send when, and how to keep it from feeling creepy.
The advantage most baby stores never use
Most ecommerce email reacts to behavior — someone browsed, someone abandoned a cart. Baby retail gives you something rarer: a predictable calendar.
If you know a child’s birth month, you know roughly when the parent moves from newborn sizes to 3–6 months, when solid-food gear becomes relevant, when the first shoes matter, when potty training arrives. None of that depends on the parent browsing. It depends on time passing, which happens on its own. A store that captures a due date or birth date at signup can send the right category at the right week for years — and most don’t ask, so most can’t.
That’s the leak. Not a broken cart flow, but a whole predictable revenue stream left un-automated because nobody collected one date.
Why more ads and more discounts don’t fix it
Parents are a fast-churning audience by nature. The problem you’re solving keeps changing — the newborn you acquired is a toddler in eighteen months, and the products that made you relevant have expired.
Throwing more ad spend at the top of the funnel just refills a leaking bucket. You pay to acquire a parent, sell them a swaddle and a bouncer, and then go quiet exactly when their needs are evolving fastest. When the toddler-bed moment comes, they Google it and buy from whoever shows up — often not you, because you never told them you sold it. A discount doesn’t fix that either; it just trains price-sensitive shoppers to wait. The fix is staying relevant as the child grows, and that’s a timing problem, not a budget problem.
Where the money actually leaks
Three places, in rough order of size.
First, the stage transitions. A parent who bought newborn gear and never hears from you again about the six-month essentials is a lost repeat customer you already paid to acquire. Multiply one missed transition by every customer and it dwarfs your abandoned-cart recovery.
Second, consumables bought elsewhere. Diapers, wipes, and formula get reordered constantly. If you’re not the one reminding them, a subscription service or a supermarket is. Every reorder you don’t prompt is margin walking to a competitor on a schedule you could have owned.
Third, the outgrown-size gap. Kids’ clothing and shoes get outgrown on a predictable curve. A quick illustrative example: a parent buys size 74 baby clothes; three to four months later that child needs 80. An automated “time to size up?” prompt at that interval catches a purchase the parent was going to make regardless — the only question is from whom.
🥇 Get more revenue from the traffic you already have.
The flows to build, in order
Build the age engine first, then the reactive flows around it.
1. Age- and stage-based lifecycle flow
This is the core. Collect birth date or due date at signup, then trigger emails at the developmental milestones your catalog serves: newborn essentials, weaning gear, first shoes, toddler safety, potty training. Each email carries the products relevant to that exact stage. The delay isn’t hours — it’s weeks and months, driven by the date you captured. This is the single most valuable build for the category, and it’s the backbone of a real retention system; the wider framing is in how to build a customer retention system for ecommerce.
2. Replenishment for consumables
For diapers, wipes, and formula, set a repeat-purchase reminder timed to a typical pack’s duration. If someone buys a two-week supply, a reminder around day ten to twelve lands right as they’re running low. This mechanic is shared with any store selling things that run out — the deeper version is in email automation for consumable product stores.
3. Size-up prompts for apparel and footwear
Trigger off the last apparel size bought plus a typical growth interval, then suggest the next size up in categories they’ve purchased before. It reads as helpful because it is.
4. The usual reactive flows, tuned for gifting
Welcome, browse abandonment, and abandoned cart still matter — but remember a big share of baby purchases are gifts from grandparents and friends who aren’t the parent and won’t come back on the same lifecycle. Segment gift buyers out of the age engine so you don’t email a grandmother about weaning gear she’ll never need.
What to automate, concretely
The stage flow is where people get vague, so here it is spelled out:
- Trigger: a contact’s stored child birth/due date reaches a milestone offset (for example, birth date + 5 months → weaning stage).
- Segment: parents only; exclude one-off gift buyers and anyone who’s already bought deep into that stage.
- Timing: milestone-driven, sent a week or two ahead of the need so it arrives before they shop, not after.
- Channel: email for the browsing-heavy stage guides; SMS only for time-sensitive things like a low-stock size or a fast reorder.
- Content: the two or three categories that define that stage, with a short, genuinely useful line — parents are drowning in “must-have” lists, so be the calm one.
- Goal: a return purchase in the new stage, measured as revenue per recipient and repeat-purchase rate.
Which metrics matter
Watch the numbers that reveal whether you’re holding customers across stages, rather than judging one send at a time.
- Repeat-purchase rate and time between orders — the honest test of whether the lifecycle flow is working.
- Revenue per recipient on each stage email, so you can cut the milestones that don’t land.
- Replenishment reorder rate on consumables.
- Second-purchase rate overall — turning a one-time gift or newborn buyer into a returning parent is where the growth is, and it’s worth studying alongside how to use email automation to increase customer lifetime value.
One caution: this data has a shelf life. A child ages out. If your stage flow keeps emailing a “newborn” whose birth date is now two years old, your relevance — and your deliverability — decay. Build the flow so contacts graduate through stages and eventually exit.
Where Omnisend fits
You can run all of this in most serious email tools. I use Omnisend in my own stores after testing it against Klaviyo, and the pieces this category leans on — storing a custom date field per contact, triggering flows off that date with long month-scale delays, and populating product blocks by category — were straightforward to set up, with email and SMS in the same place for the reorder reminders that benefit from a text.
The honest limits: the whole age engine depends on collecting the birth or due date cleanly at signup, so your form design does the real work; a bad or thin catalog won’t be saved by good timing; and you have to maintain the stage logic so nobody gets stuck emailing the wrong age forever. Omnisend is an affiliate partner of Shopimation; I recommend it from daily use, and its free tier is enough to build and test the first stage flow before you scale.
Your next step
Add one field to your signup form this week — due date or birth date — because every automation above depends on it and you can’t backfill it later. Then build a single stage transition (newborn to the next milestone) end to end and watch the repeat-purchase rate on it. If a large share of your orders are gifts, read email automation for subscription box stores for how recurring-need thinking can turn one-off gifting into a standing relationship.
