You replaced the file. Now send the email to everyone who bought.

The updated version has been sitting in your downloads folder for three weeks. You fixed the two things people kept mentioning, added the section you meant to include the first time, and then stopped, because uploading it felt like admitting the old one had problems. Meanwhile everyone who bought it is still using the version with the problems, and none of them know a better one exists.

Why updates stay invisible

Selling a file usually means the file is gone the moment it is sold. It lives in someone's downloads folder, out of your reach, frozen at whatever state it was in that afternoon. So most creators stop improving what they have already sold and pour their effort into the next product instead, which is how people end up with nine mediocre products rather than three good ones.

When the file is delivered through a private order page the buyer can return to, that constraint disappears. Replace the file and every past buyer's page now serves the new one. It is a genuinely useful arrangement, and it creates a new problem in the same breath: nobody checks a page they have already used. The improvement exists and nobody experiences it.

The honest difficulty here is not technical. It is that you have to decide the new version is better for everyone, not just for new buyers, because everyone is who gets it. If your version two drops a format some people relied on, those people lose something they paid for. That is a real editorial responsibility, and it is the reason the callout further down exists.

Shipping version two, two ways

The usual workaround is to list the new version as a separate product, which forces you into an awkward decision about whether to charge your existing customers again.

The update, and the email that goes with it

Do these in order. The email is written last, because until the file is live the email is a promise rather than a delivery.

1. 1Save the outgoing version somewhere safe with a date in the filename. This is your archive, and it is the only copy of it that will exist.
2. 2Open the product in your dashboard and replace the file with the new version.
3. 3Open your own order page as a buyer would and download it, to confirm the file that arrives is the one you meant to send.
4. 4Write down what changed, in three bullet points, in the language a buyer would use rather than a changelog voice.
5. 5Write the email. Subject line names the product and says it has been updated. No cleverness required.
6. 6First line: they already own this, and the new version is waiting on the same page they used before.
7. 7Middle: the three bullets, and one sentence on why you made the change.
8. 8Last line: tell them to open the order page from their original confirmation. If they have lost it, tell them to reply and you will help.
9. 9Send it to past buyers of that product only. This is the whole point, and sending it to your entire list wastes the goodwill.

What an update email is worth

Suppose a template pack has sold 214 times over a year at £24. Those 214 names are already sitting in your customer list with a lifetime value against each one. There is nothing to sell those 214 people — they own it. So an update email looks, on a spreadsheet, like a message with no revenue attached to it. That is exactly why it works. It is the rare email from a creator that asks for nothing, and readers can feel the difference in the first sentence.

The return shows up sideways. Some of those 214 open the pack again and remember why they liked it. A few forward the email to someone who then buys. A few reply with the thing they wish it did next, which is your version three brief, delivered free. And when you do eventually launch something with a price on it, you are writing to people who heard from you last month with good news rather than people who last heard from you at checkout. None of that is guaranteed, but it is a far better position than silence.

The mistake most people make

They batch. Six months of small fixes wait for a version two big enough to justify an announcement, and by then half the buyers have moved on. Ship the fix the week you make it, and let the email be small too. The other version of the mistake is the opposite: emailing 200 people because you corrected a spelling error on page four. The test is simple — would a buyer be glad you interrupted them? If the answer is no, upload the file and say nothing. You can always mention accumulated small fixes in the next email that has a real reason to exist. Sending broadcasts from inside store.fan is part of the Pro plan, and it is worth knowing that before you build a habit around it.

An updated file that nobody knows about is a favour you did in private. Twenty minutes and a short email turns the same work into a reason for two hundred people to think well of you this week. The upload is the easy half.