Gumroad Product Checklist: What to Verify Before Promotion

1. Verify the actual attached file

• Correct product name.
• Intended ZIP filename.
• Non-zero file size.
• No old candidate or internal marker.
• No unrelated product or brand context.
• No accidental cross-product file.

If you operate more than one product or storefront, be extra careful. A correct-looking page can still be connected to the wrong seller workspace or file.

2. Confirm the public product page is available

• The public URL loads.
• The title is correct.
• The product is not marked unavailable.
• The price and description are intentional.
• The call-to-action is clear.
• The page does not show old draft language.

Use an unauthenticated browser or private window where possible. Do not rely only on the logged-in seller view.

3. Review buyer expectations

• What exactly is included?
• Is this a template, checklist, guide, software tool, or service?
• What format is delivered?
• Is it editable?
• Is it beginner-friendly?
• What support is included?
• What is not included?

If the product is a starter kit, say that clearly. Do not imply managed service, promised outcomes, or official platform partnership.

4. Prepare support and refund wording

• How to contact support.
• What to include in a file/access issue.
• Expected response scope.
• Refund review boundaries.
• Sensitive information buyers should not send.

Example: If you have trouble accessing the download, contact support with the purchase email and a short description of the issue. Please do not send passwords, card details, or unrelated private information.

5. Check trust pages around the product

• Homepage CTA points to the intended product.
• Contact page uses the correct support identity.
• Privacy page does not overpromise.
• Terms page matches the product type.
• Refund/support notes are consistent with the seller platform.

6. Avoid overclaiming before traffic arrives

• Do not say “works in every case.”
• Do not say “prevents all launch issues.”
• Do not say “compliance ready.”
• Do not say “official partner.”
• Do not say “automatic support.”
• Do not say “no refund risk.”

Better wording is practical: “pre-promotion checklist,” “helps reduce common setup mistakes,” “support/refund wording starters,” and “buyer-access QA notes.”

7. Keep a short promotion preflight

• Public site status.
• Product page status.
• Attached file status.
• Support mailbox status.
• Refund/support macro readiness.
• No unrelated brand/store context.
• No private owner identity exposure.