LOADING THE FEED ▮
NICHE OF ONE
--:--
← The Feed

Your Download Link Is Part of What You Sold

/A digital product is more than the file on your laptop. Match the promised contents, checkout, and delivered copy before you send buyers to it.

Post to X Email it
// from the shelf The Simple-Fix PDF Engine Turn what you already know into a PDF that sells while you sleep. $7 →

TL;DR: The buyer didn’t purchase the file sitting on your laptop. They bought the copy your checkout promises to deliver. Make sure those are the same thing.

Everything looks finished on your laptop. The PDF exports, the spreadsheet opens, the ZIP is sitting right there. Then a buyer clicks your button and gets the old workbook. You have a support ticket now.

Somebody pays. The link breaks.

The download page opens empty.

They get the old workbook. Hell, now you’ve sold yourself a support ticket.

The buyer paid for the promise, not your folder structure

They paid for the promise on the page and the files that arrive after checkout. Your folder structure, database row, and export history are invisible to them. The delivery is the receipt.

What’s on the page? If it promises eighteen parts, write all eighteen down. Give each one a filename. Record the file size and checksum. Keep one package file if that’s what the buyer receives. Then compare your list against the copy in storage. Simple. Boring. The kind of boring that saves your ass.

Call it paperwork if you want. When the sales page promises eighteen pieces and checkout points to one stale PDF, the spreadsheet doesn’t care how finished you felt. Neither does the buyer. This list catches that mess before it costs you an afternoon.

How do you know the stored copy is the right one?

What’s in the buyer’s hand? Compare the delivered copy with the approved master by size and hash. Same filename proves nothing. Two files can wear the same name and contain different guts. A hash gives you a cheap way to tell.

The practical list is short:

  • Write down the included items and the master filename.
  • Save the master’s byte size and SHA-256 checksum.
  • Check the file attached to the product record.
  • Compare its size and checksum with the master.
  • Make sure the paid link points to the product and price you mean.

Two identical-looking file cards compared by different fingerprint patterns

That last one matters. A checkout can work and point at the wrong product. The right file can sit outside the buyer’s library. Every piece has to line up. Can you prove they do?

What should you check before you announce it?

Open the public checkout. Read the amount, currency, quantity, product name. Then check that the Rook record accepts that exact link and price. Unknown links should fail closed. The return page shouldn’t grant access by itself. Fulfillment follows the signed payment event. Don’t guess.

After that, the expensive proof is a real order. The email arrives. The buyer’s library opens. The downloaded bytes match the approved master. If you can’t afford to buy your own product to test it, don’t pretend a green unit test proved the whole path. Until you can verify the buyer’s experience, keep the announcement staged.

A checksum protects the file. A good offer protects the buyer’s time before they click. The Make and Sell Small Things guide covers the product side of this job: what to promise before the download link has to keep that promise.

Frequently asked questions

Is a checksum necessary for a small digital product?

It takes seconds to record and compare. It is useful whenever a buyer pays for a specific file and you might replace that file later.

Should a bundle arrive as one ZIP or many separate downloads?

Pick the format that matches the promise. One ZIP is easier to maintain; separate files can be easier to browse. Whichever you choose, list the contents and verify the exact files the buyer receives.

Does a successful payment prove delivery works?

No. Payment proves the charge went through. You still need to verify the receipt, access link, and downloaded file.

If your next release needs a clearer promise before the download arrives, read Make and Sell Small Things.

// comments
Full search on OneSearch: the network, the ring, and the open web →esc closes · ↑↓ move · ↵ opens