GENESIZE — DIGITAL PRODUCT SALES DIAGNOSTIC WORKSHEET Finished product · One bottleneck · One next step Use alongside “Why Your Digital Product Isn’t Selling”: https://genesize.io/blog/why-your-digital-product-isnt-selling This is a planning worksheet, not proof of a completed payment, a statistical experiment or a promise of sales. Use aggregate notes, not customer details, passwords or private access links. Keep the original record for later review. 1. CHECK THE BUYING AND DELIVERY PATH Product and public sales link: ________________________________________________________________________ Price, currency and payment type (for example: $19 USD, one-time): ________________________________________________________________________ Exact edition / version being checked: ________________________________________________________________________ Check date and time zone: ________________________________________________________________________ Mode: [ ] Live customer activity [ ] Sandbox / simulated test Who is it for, and what task does it help finish? ________________________________________________________________________ Intended live page and edition: [ ] Available and correct [ ] Blocked / unavailable [ ] Unclear — needs checking [ ] Not checked Payment setup for this offer: [ ] Provider setup currently ready [ ] Known setup blocker [ ] Not required: fixed free offer [ ] Unknown / not checked What did you actually observe? When? ________________________________________________________________________ ________________________________________________________________________ Exact delivered file / resource: [ ] Opened the expected file or resource [ ] Response / download prompt only [ ] Known access / file problem [ ] Unknown / not checked Receipt evidence, if checked: [ ] Provider accepted only [ ] Inbox arrival personally confirmed [ ] Known receipt / access-link issue [ ] Not checked Edition, device and delivery evidence observed: ________________________________________________________________________ ________________________________________________________________________ A ready provider status is setup evidence, not proof of a completed payment. A simulated buyer test makes no real payment. A delivery response or download prompt does not establish that the file opened. Provider acceptance does not establish inbox arrival. Record these checks separately. One confirmed buying or delivery blocker to fix first — or “none confirmed”: ________________________________________________________________________ ________________________________________________________________________ Payment-to-delivery guide: https://genesize.io/blog/deliver-digital-downloads-after-stripe-payment 2. CHECK WHAT IS KNOWN AND WHAT IS MISSING Reports / sources used: ________________________________________________________________________ Product, edition, channel and mode covered: ________________________________________________________________________ A blank or unavailable measurement is not a verified zero. Keep QA, free claims and sandbox activity out of real paid-sales counts. Write the actual date range shown by each report; do not assume they all use the same window. MEASURED VISITS Distinct consented browser sessions recorded on the native product page. Sessions are not unique people. Privacy choices can hide activity. Count, only if known: __________ State: [ ] Unknown / missing [ ] Verified zero in this scope [ ] Measured count [ ] Partial coverage Actual date range and time zone: _________________________________________ CHECKOUT STARTS Checkouts created in the report’s stated product/edition scope. Record whether the report pins one edition. Starts can remain unpaid or expire. Count, only if known: __________ State: [ ] Unknown / missing [ ] Verified zero in this scope [ ] Measured count [ ] Partial coverage Checkout-created window and time zone: __________________________________ PAID-DATE SALES Positive orders with a verified paid date in the stated window. Their checkouts may have started earlier. A report may retain later refunds or disputes; record its status policy. Exclude QA and free activity. Count, only if known: __________ State: [ ] Unknown / missing [ ] Verified zero in this scope [ ] Measured count [ ] Partial coverage Paid-date window, time zone and status policy: ___________________________ DO NOT DIVIDE THESE THREE COUNTS BLINDLY. Different date bases, cutoffs, channels and editions do not form one matched funnel. Use a specifically matched, mature cohort if a report provides one. A paid-date total is not necessarily retained revenue. An incomplete checkout alone does not prove a payment error. What is unknown, incomplete or too small to judge? ________________________________________________________________________ ________________________________________________________________________ What did suitable buyers actually ask or find unclear? ________________________________________________________________________ ________________________________________________________________________ FICTIONAL $19 PDF EXAMPLE — NOT A CUSTOMER RESULT A creator has a finished $19 USD client-kickoff PDF. The expected file opens in a simulated buyer test, but the creator has not checked real payment execution or verified visitor measurement. Useful next step: record those unknowns, verify the available setup evidence, and share one relevant sample where promotion is welcome. “The price is wrong” is not supported by that evidence. This example supplies no measured sales outcome. Missing measurement is not zero demand; small counts are not a verdict. Finding first suitable buyers: https://genesize.io/blog/how-to-sell-digital-products-without-an-audience 3. CHOOSE ONE BOTTLENECK AND ONE CHANGE My current bottleneck — choose one: [ ] A confirmed buying or delivery blocker [ ] Missing or immature measurement [ ] Too little suitable, measured reach to judge [ ] A specific promise, sample or offer question [ ] A buyer-experience concern to investigate [ ] Still unknown — gather one missing fact first Evidence for this choice, including what it cannot prove: ________________________________________________________________________ ________________________________________________________________________ One change or check I will make: ________________________________________________________________________ ________________________________________________________________________ Exact next action / where I will do it: ________________________________________________________________________ ________________________________________________________________________ What will stay the same during the review? ________________________________________________________________________ Evidence I need next — and what may remain unknown: ________________________________________________________________________ New published edition / observed change date: ________________________________________________________________________ Next review date and time zone: ________________________________________________________________________ Seven-day window ends, if applicable: ________________________________________________________________________ Checkout outcomes mature 24 hours later: ________________________________________________________________________ IF USING GENESIZE “TRACK THIS IMPROVEMENT” Tracking a saved draft does not publish it. Its actual matching publication anchors equal seven-day edition windows; allow 24 more hours for checkout outcomes. These are CHECKOUT-CREATED COHORTS WITH PAYMENT WITHIN 24 HOURS, not the paid-date sales total above. Earlier availability before publication observations began is unknown and cannot be backfilled. Short coverage, unrelated changes or unpublishing can prevent a valid comparison. Sparse activity cannot establish a winner. These dates are unrelated to a Search Console reporting baseline. Use a separate worksheet for a later change rather than rewriting the original record. Sales-page example: https://genesize.io/blog/digital-product-sales-page-examples Launch checklist: https://genesize.io/blog/digital-product-launch-checklist Full diagnostic guide: https://genesize.io/blog/why-your-digital-product-isnt-selling © 2026 Genesize. This worksheet is an editorial planning aid.