Selling Templates
Managing products after launch
Preview reference: Shipping new versions, honoring existing buyers, refunds, and retiring products well.
The seller journey described here is not an available production workflow. Paid checkout, refunds, payouts, and installation or upgrade require release acceptance. The material below is a preview reference, not instructions to perform financial tests or enable background workers.
Shipping improvements
Register the improved artifact version, add it to the product with release notes, and attach an offer. Because sold versions are frozen snapshots, existing buyers are never surprised: what they installed keeps working exactly as bought, and adopting your new version is their choice — delivered through the same block-level upgrade flow they use for any template, so their customizations survive your improvements.
Release notes are marketing to your existing buyers. A clear “what's new and why you'd want it” converts installed-base into upgrade revenue — and into reviews.
Refunds and disputes
Refunds are recorded against the original order and reverse the matching credit in your ledger. The maturity window on funds exists precisely so most refunds resolve before money moves. Fast, generous support through your storefront's support email is the cheapest dispute prevention there is.
Retiring a product
Retiring stops new sales; it does not reach into buyers' apps. Anyone who bought remains entitled to what they bought. Retire the listing, keep supporting existing buyers through the support channel, and the storefront reputation you built carries to your next product.
Capability review: 2026-10-20. See current features and setup requirements, the generated API Map and first-class module inventory.