Notes for owners · Channel and customer growth
Growing out of products: planning repeat buying by a child's age
Babies outgrow sizes and stages in months, so record the child's age and the size bought at the first order, and ask about the next stage when the label says it is due, without guessing.
The GullySales team · Updated 17 Oct 2026 · 6 min read
On this page
Say a mother buys a 0 to 3 month vest set from you in February. By May the vests are folded in a drawer, the baby has outgrown them, and the mother is buying the 3 to 6 month size from whichever app she happened to open. Nobody told her you had it. She was not unhappy with you; she was never asked. Repeat buying in baby and kids' products follows the child's age, not the product's life. Record the age and the size at the first order, and you know when the next stage is due without guessing.
The age is the reorder date
Our post on encouraging repeat purchases times reminders by how long a product lasts, because a bag of coffee runs out. Baby products do not run out. They stop fitting, or the child moves on. A 0 to 3 month vest is too small at about three months whatever state it is in, and nobody needs a teether once the teeth are through.
That makes the timing easier than for a consumable. You do not have to wait months for your order history to show a pattern. The size label and the child's age already tell you.
What moves each product on
Draw this up for your own range, one row per category you sell. For a shop selling across baby categories it looks like this:
| What you sell | What moves the child on | What you can record | What to suggest next |
|---|---|---|---|
| Clothes | The age range on the size label | Size bought, child's age | The next size, a few weeks before the range ends |
| Nappies | Weight, not age | Size bought | Ask how the fit is; do not push the next size on age alone |
| Feeding | Bottle to cup, milk to solids | Item bought, age | Nothing until the parent mentions solids, then a first spoon or cup |
| Shoes | Crawling to walking | First-walker size bought | The next size, with a note to measure the foot first |
| Toys | Grasping, sitting, standing, walking | Age at purchase | A next-stage toy, offered as an idea |
| Car seats and strollers | The maker's weight and height limits | Model bought | One message when the maker's limit is near, if you know it |
Two rows say not to push on age. Nappies go by weight and babies differ. Weaning is decided between a parent and her paediatrician, not by your calendar. Ask; do not tell.
What to record, and how
You need very little, and less is safer. Make the questions optional, at checkout or in the first delivery message:
- Who is it for? My child, or a gift.
- The child's month and year of birth, or the due month. Not the full date.
- A first name or a label for the child, only if the parent wants messages addressed to one.
- The size bought, which your order already holds.
Then keep a register with one row per child, not per customer, because a customer with twins or a second baby has two clocks running. The columns: customer, child label, birth or due month, category, size bought, order date, next stage due, message sent, reply. A spreadsheet does it. A CRM does it better once you pass a few hundred children.
Two messages nobody should receive
Every baby customer list holds two traps.
Gifts first. Plenty of baby clothes are bought by aunts, friends and office colleagues for a naming ceremony or a baby shower. A next-size reminder sent to the colleague is noise. Keep gift buyers on a separate list, and contact them about occasions such as a first birthday only if they asked to hear from you.
The second trap is a due date. Our post on maternity products by stage explains why no automated sequence should count towards a birth. For a baby clothes store the rule is simpler: no age message goes out until a later order or a reply has confirmed the baby's birth month. Every message carries a one-tap way to stop.
For example: a baby clothes brand in Coimbatore
Imagine a Coimbatore brand selling cotton baby clothes online, with a couple of years of orders behind it. It decides to "do retention" and sends one discount offer on its 6 to 12 month range to everyone who bought anything six months earlier.
The replies show the mistake. Gift buyers ask why they are getting this. Several parents say their child is already in 12 to 18 months. The offer went to everyone on a guess.
So the brand drops the blanket discount. It adds the two questions at checkout and rebuilds its list by child and by size bought. Each parent now gets one message a few weeks before the end of the size range she bought:
The 0 to 3 month vests you ordered will be getting snug soon. Is she in 3 to 6 months now? Reply 1 to see the new size set, 2 if she is already in a bigger size, 3 to stop these messages.
A reply of 2 updates the register, so the next message is right. A 3 removes the child's row. Gift buyers hear nothing until the first birthday, and only if they said yes. In this made-up case only some parents answer, a few with a size the brand does not make, and the rest never reply, so the register stays partly guesswork.
When age-based messages are the wrong tool
If you sell one-time gear, a cot or a high chair, there is no next size. Send a care tip and leave it there. If your range stops at one age, there is nothing to offer when the child moves past it, and filling the gap with an unrelated product reads as spam. And if a parent has ignored two messages, stop. Parents who want you will come back to the shop.
What to do next
Open your orders and count the first orders for newborn or 0 to 3 month sizes. Then count how many of those customers ever bought the next size from you. The gap between the two numbers is the work. Baby clothing is one part of the wider online sale, which sits under e-commerce sales and marketing. If you want the register and the size messages set up for your range, customer retention strategy is the service, and tell us what you need is the first step.
