Selling Templates
From your app to the storefront
Preview reference: The whole seller journey in one page: what you'll set up, in what order, and why each step exists.
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.
These reference pages describe the seller catalog, exact-version artifacts, orders, and ledger model. They do not establish a working purchase, refund, payout, or installation journey. Marketplace financial and installation workflows remain release-gated; the model below is not confirmation that those actions are available in your deployment.
The journey, end to end
- Become a seller — open your storefront and connect payouts. One-time setup.
- Prepare the work — get the template to a published, validated version in your own account, with the licensing rules satisfied. What “ready” means.
- Register the artifact — snapshot that exact version into your seller catalog, fingerprint and all. From this moment, what you sell is frozen and provable.
- Create the product and offer — listing page, semantic version with release notes, then a priced offer. Products, versions, and offers.
- Activate — the offer goes live once its checklist passes: published version, active seller, at least one active price.
- Get paid and iterate — sales credit your ledger, eligible funds can be sent through Stripe Connect, and Stripe controls the connected account's payout timing; new versions ship without breaking existing buyers. Getting paid and after launch.
Everything on this path is permission-gated and audited like the rest of the platform: store actions require the marketplace store permission on your team role, payouts require the payout permission, and every step lands in your account's audit log.
What you can sell
The same pipeline handles several product types — templates, individual pages, modules, bundles that install components in order, Harness Packs, integrations, and appliances. This section uses templates as the running example; where another type differs, the page says so.
Capability review: 2026-10-20. See current features and setup requirements, the generated API Map and first-class module inventory.