Every category has a clock. Find yours before you set a single delay. A replenishment brand's clock runs in days to runout, and most lapse rules are written for brands like that. A season, a billing month and a wardrobe keep time differently.

Gobi Heat sells heated apparel, and its year is decided in about ten weeks of cold. Its email and SMS earned $1.6M in a single winter season, platform-reported. A customer who bought a heated jacket in December is not lapsed in March. They are wearing it.

At 3Commas, in subscription software, the second order is the second month. At UNTUCKit, in menswear basics, the second order is a second color of the same shirt. Nothing runs out. If yours doesn't run in days, a lapse rule borrowed from another category will fire at the wrong time.

Count lapse in drops

A 90-day winback in a category that drops every six weeks fires after about two releases, which is arbitrary for someone who buys every other drop and hostile to someone who buys once a season. Count the gaps between each customer's purchases in releases, and call someone lapsed past the 75th-percentile gap. Pull it from your own order file, the way you'd pull the Kept Interval, but count in drops.

Then rewrite the winback against the new definition. Someone who skipped two collections needs to hear what changed in the line. A discount on a collection that no longer exists gives them nothing to buy.

A seasonal brand counts in seasons and asks what share of a cohort comes back in season two. Its off-season mail keeps the brand present without asking for a purchase. Its pre-season mail goes out with the first cold week in the customer's region, not on a fixed date.

Protect last season's proven sellers from each new drop. Every drop arrives with people inside the company pushing it, and the item that sold for two seasons has nobody arguing for it. Before the drop lands, set a floor on spend, email placement and site space for proven sellers. Newness then earns its way up from a test budget.

The weeks between releases

The gap between drops is where customers drift, and most programs fill it with silence or a discount. A between-drops bridge is a small, fixed set of messages that hold the customer without selling something that doesn't exist yet. Send restocks in their size, styling for what they already own and the making of the next drop. Let customers opt into a reminder for the next release date.

Offer early access instead of a discount. Where the best sizes sell out, first access is worth more than a percentage off, and it costs no margin. Give it first to the people who asked for the reminder.

Most of the bridge depends on size and fit data, which describes the body and survives the catalog turning over. Capture it with a fit finder before purchase and a fit check after delivery. Write return reasons to the profile when someone says an item ran small. Store each as an event and a profile property, so a restock alert only goes to people it fits.

In a drop, the product sells the first order. On a celebrity apparel launch, where I worked on commerce infrastructure and merchandise strategy on contract, Shopify reported $821K in sales across 5,820 orders in launch week. Demand was never the constraint. What a drop brand controls is what it captures from each launch buyer: a size, a fit note and an opt-in for the next date.

Short peaks

Seasonal and drop brands pack the year into a few weeks. Punkcase, a phone-accessories brand, earned $1M+ over one Black Friday and Cyber Monday, platform-reported. A peak like that is won in the three months before it: sending reputation warmed on a steady cadence, segments tested, flows fixed and the early-access list told a date.

During the peak, send in waves hours apart, not days. In a four-day window, a day-long gap between waves spends a quarter of the peak waiting. The sizes a late wave promotes may already be gone. Plan the peak as a data project that starts three months early and a sending project that lasts four days.

Four clocks, side by side

The system stays the same across those columns: cohorts by entry month, a branch on first product, one offer at a time. What changes is the clock and what counts as a return, so a lapse rule copied from another column fires on the wrong day.

Find your column and fill its four cells from your own file. If the clock row can't be filled from your order export, pull that number first, before the next email goes out.

Do this

• Find your column in the table. Write your clock in its unit: days, drops, seasons or billing months. Set your lapse rule in that unit before the next release.