Count the second orders that arrive with nobody at a desk. Grow that share first.
Your day-4 "how to use it" email is doing the insert's job, late. The customer opened the box a day earlier. They found the product and a packing slip, guessed at the routine and started judging. A first order that gets used wrong, or not at all, rarely becomes a second. The fix sits inside the box, and it works whether or not anyone is at a desk that week.
If your post-purchase flow is a thank-you and a discount code on day three, that's a campaign on a timer. It sends a code before the customer has used the product. It also teaches them to wait for the next one.
Grow Structural Share before any other repeat number. It's the share of last month's second orders produced by subscription, flows or unprompted reorders: the orders that arrive with the team on holiday. A repeat rate built on campaigns follows your calendar, and it stops when the calendar does.
A campaign is a thing you send. Structure is a thing that runs.
Measure it with the holiday test. Pull every second order from last month. Tag each one by what produced it: a subscription shipment, a triggered flow, an unprompted reorder with no send attributed, or a campaign. The first three arrive with the team away. Only the campaign needed someone at a desk. Tagging a month takes an afternoon if your attribution fields are clean, a few days if not.
Take an invented brand whose second orders last month split 75% campaign, 15% flow, 5% subscription and 5% unprompted reorder. Its Structural Share is 25%, so three of every four repeat orders depend on someone building a send. Push the share past half. Put it on The Monday Scorecard, because it shows whether the program runs without you.
Everything that reaches a new customer before your first marketing email counts toward Structural Share, because none of it waits for anyone to press send. Start with whether the product works for them. A customer who used it wrong blames the product, so no reorder reminder wins them back. That makes efficacy and usage the first lever, ahead of any message you write.
The same logic runs through returns and stock. A refund ends the relationship; an exchange keeps the customer and tells you what went wrong. A reminder for a product you can't ship does harm, because the customer clicks, finds nothing, and learns to skip the next reminder. Both failures happen in systems no campaign report reads: the returns portal, the inventory feed, the helpdesk.
Keep order and shipping confirmations about the order. The subscription offer, the loyalty pitch and the product recommendation go in marketing mail, which only reaches people who can receive it.
For example, take an invented consumable whose customers reorder at a median of 45 days. The usage message runs off delivery. The reorder touches run off the order date, at ¾, 1× and 1⅓ of the interval.
Any purchase exits the flow, and an active subscription suppresses it. No discount appears before the interval, because a code this early teaches customers who would have paid full price to wait for one.
Subject: Getting started with your [product]
Use it [how and when]. Results usually show in [weeks], so give it that long.
Not working by then? Reply to this email and a person will help.
Flows never go on the campaign calendar. Once a flow lives there, someone pauses it for a sale or edits it for a launch. After that it runs only while that person remembers it. The calendar stops when the team does, so anything on it fails the holiday test. Give flows their own owner and a monthly check against the order file, and keep the calendar for campaigns.
Tag last month's second orders by source. If subscription, flows and unprompted reorders already produce most of them, the structure is built. Spend your time on offers and the back file.
This is one chapter of The Second Order, which is free and readable in full on a single page with no form in front of it.