Most digital products are sold like tap water: always on, bought whenever. A drop is the opposite. The product exists for a window — a holiday collection, a numbered edition, a collaboration that ends Sunday — and then it is gone. Sellers love drops because a deadline concentrates attention. What they underestimate is that a deadline also concentrates delivery: every buyer arrives in the same few days, downloads at the same moment, and writes for help at the same time.
This is a runbook, not a launch plan. It assumes your product and your audience already exist, and it works backwards from the moment the window opens.
T-minus 14 days: decide what "limited" actually means
A drop needs a limit, and the limit needs to be true. There are three honest kinds:
Time-limited. Available until a stated date and time, then sales close. The cleanest drop, and the easiest to honour: the buy link simply stops selling.
Quantity-limited. A stated number of copies, editions, or seats. Honest only if the counter is real — if copy 101 can be bought after you announced 100, the limit was theatre, and buyers who paid a scarcity premium will remember.
Version-limited. This edition will be replaced and never sold again in this form — a 2026 planner, a sample pack tied to a specific collaboration, a course cohort's materials. The file may evolve, but this version retires.
Pick one, state it in one sentence, and write down — now, not later — what happens at the end: does the product disappear, become a different product, or return at a higher price? Every messy drop ending traces back to a seller improvising this answer while buyers were asking. Decide support here too: a drop compresses a month of questions into a weekend, so fix in advance who answers, how fast, and for how long after close.
T-minus 7 days: freeze the file
The single most damaging drop habit is editing the product during the window. A typo fix on day two sounds harmless; in practice it means early buyers hold version one, later buyers hold version two, nobody knows which is which, and your support answers stop matching what half your buyers see.
So: freeze the file a week out. Later changes wait for a single planned update, delivered to every buyer at once after the window closes. Name the frozen file like it will be searched for months later — product, edition, version — because a seasonal buyer's downloads folder is a graveyard of files called "final" and "new".
Test the frozen file the way a buyer will meet it: on a phone, on a slow connection, from the actual delivery email, not from your own cloud folder. If the file is very large, split it into parts — core and bonuses — so a failed download is a small retry, not a restart.
T-minus 3 days: set delivery for a rush, not a trickle
Delivery settings that suit evergreen sales are usually wrong for a drop, in both directions.
Expiry should outlast the window, comfortably. If sales close Sunday, a link that expires Monday manufactures emergencies. Buyers purchase in the rush and download when life allows — the following weekend, not the same hour. Give the link weeks, or no expiry, and let the sales window be the scarce thing, not access to what was already bought.
Limits should assume real life. A buyer will download to a phone, then a laptop, then again after a device change. Set limits generously before you open; raising them mid-drop for a queue of frustrated buyers is the drop equivalent of restocking a sold-out sign.
Keys, if your product uses them, should be issued per paid order — automatically. Hand-issuing anything during a drop does not scale: one missed email becomes a buyer who paid for a limited edition they cannot open. The scarcity is in the selling window; activation should be boring and instant.
Do a full test purchase now, with a real card, and keep the receipts. That test is your baseline when someone writes mid-drop saying delivery never arrived — you will know what "arrived" normally looks like, and how long it takes.
T-minus 1 day: write the ending before the beginning
Draft three messages before you open, while you are calm:
- The closing reminder. One message, near the end, stating plainly when sales close and what happens after. No false extensions, no surprise second window. If you later extend the drop, say why, once — an unexplained extension teaches buyers that your deadlines are negotiable, and the next drop's countdown will be ignored.
- The "you bought it, here's how to keep it" message. Sent just after close to every buyer: where to download, how long the link lasts, how to get a fresh link if it expires, and where the file should be backed up. Seasonal buyers are the buyers most likely to return months later — at the next season — looking for a file they half-remember buying. This message is what they will search their inbox for.
- The sold-out / closed page text. The buy link's job after close is to say the window has ended, whether a waitlist or a next edition exists, and — critically — that existing buyers' access is unaffected. Half the panic mail after a drop closes comes from buyers who clicked their old link, saw a closed page, and assumed their purchase had vanished with the offer.
During the window: sell, don't tinker
Your job list is short: watch the first hour's deliveries like a hawk (that is when a broken link reveals itself, while you can still fix it for everyone), answer delivery problems before sales questions, and change nothing structural. No price experiments, no file swaps, no "improved" editions mid-window — every mid-drop change splits buyers into before and after groups who will compare notes.
Watch for the deadline-edge buyer, whose payment may complete after your planned close. Decide your rule now — a payment completed within a short grace period counts — and apply it uniformly.
T-plus 1 to 7 days: close cleanly
Closing is an operation, not an announcement. Turn off sales at the stated time, publish the closed page, send the "here's how to keep it" message, and deliver any promised post-drop update to all buyers at once, under their existing access.
Keep support open at drop intensity for a few more days: the buyer who bought Friday and first downloads the following Thursday is normal, not negligent. Then write the post-mortem while you remember it — how many sold, when the rush peaked, which delivery question repeated. Next season's drop should start from notes, not memory.
The honest limits of the drop model
Drops are not free urgency. A window only works if your audience trusts it is real — the first drop is the hardest, and a quietly extended deadline is the most expensive lesson. Drops also punish thin catalogues: if the seasonal edition is your only product, closing it closes your whole shop. Many sellers do best with a hybrid — an evergreen core product, plus seasonal editions that come and go honestly. And scarcity amplifies existing demand; it does not manufacture it. If a product did not sell evergreen, test the product before blaming the absence of a countdown.
Closing note: this runbook comes from the team behind FileFreight, a new and small delivery tool for digital downloads — payments go through your own Stripe account, each buyer gets a personal expiring download link, PDFs are stamped per buyer on first download, and license keys are issued per paid order with refunds revoking access automatically; Pro is $19/month at 0% per-sale fees, and the free plan takes 5%. Honest caveats: it is not a merchant of record and does not handle sales tax or VAT for you, there is no automatic importer (the first 20 sellers get a free white-glove migration), it is not a Shopify app, and it is delivery-only with no marketplace discovery. A drop run well is mostly decisions made early — any tool that ties delivery to the paid order will serve it; the countdown discipline above is the part that matters.
Top comments (0)