How to retire a stale bundle without losing the month's revenue

The signs are always the same. The bundle still sells, but slowly. Two of the files reference a version of something that no longer exists. You wince slightly every time somebody buys it, and you have started explaining in the delivery email which parts to ignore. It has stopped being a product and started being a liability with a price tag.

Why creators leave dead bundles up for years

The first reason is that it still makes money. A few sales a month is not nothing, and removing it feels like voluntarily reducing your income. The second reason is guilt about the people who bought it — a fear that closing the product somehow strands them.

The third reason is the real one: retiring something properly requires a plan, and building a plan requires deciding what replaces it. It is easier to leave the listing up and quietly hope nobody notices the outdated section. So the bundle rots in public, on the same page as your best work, teaching every new visitor what your standards are. Storefront and product pages are statically rendered and sit in your sitemap, which is excellent for the products you are proud of and unhelpful for the one you are not — see how the storefront is built if you want to picture where it sits.

The genuinely difficult part is timing. Close too early and you lose a month of income you had counted on. Close with no notice and you lose the last surge of sales that a deadline reliably produces. Neither problem is hard to solve, but both need to be solved in advance rather than on the day.

Quiet deletion versus a planned retirement

Most product retirements happen at 11pm with a delete button and a small feeling of relief. Compare that with the version where the closing is the campaign.

The fourteen-day retirement, step by step

This is the sequence in the store.fan dashboard. It assumes you have decided what the replacement is; if you have not, that decision is step zero and everything else waits for it.

1. 1Day one. Publish the replacement product, even in a plain first version. Traffic needs a destination before the old page starts pointing at one.
2. 2Day one. Replace the most out-of-date file inside the old bundle. Because replacing a file updates it for everyone who has already bought, this quietly repairs your back catalogue at the same time.
3. 3Day two. Edit the bundle description to name the closing date in the first line. Not "soon" — a date.
4. 4Day two. On Pro, set a countdown campaign on the bundle so the deadline is visible rather than described.
5. 5Day three. Post the announcement to your membership or community feed and pin it, so the people closest to you hear it first.
6. 6Day seven. On Pro, email the customer list. The people who bought your other work are the likeliest final buyers, and their lifetime value is already in the list if you want to segment by it.
7. 7Day thirteen. Send the last reminder and say plainly what happens to existing buyers, which is nothing.
8. 8Day fifteen. Unpublish the bundle, and check that the replacement is sitting where the old one was in your layout.

What the last fortnight tends to look like

Take a bundle priced at £45 that has settled into roughly four sales a month. Over the previous quarter that is about £540. In a retirement fortnight, the deadline pulls forward everyone who had been meaning to buy it, and it is not unusual for a closing window to do several months of ordinary sales in two weeks. Suppose it manages twelve sales — £540 in a fortnight, and then the product is gone and so is the wincing.

The part that matters more is what happens next month. If the replacement went live on day one and inherited the attention, the month after the closure is not a hole. If you retired first and built second, it is. Watch the two products side by side in per-product analytics across the transition, including traffic source, because that tells you whether the old links are still sending people and whether they are landing anywhere useful. None of these figures are a forecast — your audience, price and history decide the real ones.

The mistake most people make

The mistake is apologising. Retirement announcements that read like confessions — "this is a bit outdated, sorry, I am taking it down" — turn a routine business decision into a reason to doubt you. The product had a life, it did its job, and something better is taking its place. Say that. Then say the date, say what existing buyers keep, and stop. A closing note is three sentences long. If you want to see how the pieces you are moving between actually work, the feature overview is a better use of the next ten minutes than a fourth draft of the apology.

Every product you sell is a statement about the standard of your work. Retiring one on your own terms, with a date and a replacement, is not a loss of income — it is usually the best fortnight that product will ever have, followed by a shop you are willing to send strangers to.