Developers · Overview
Build themes for WhizzyCommerce
A theme is JSON and CSS, checked by the same code that installs it. You build it with the editor you like, test it on a shop that never expires, and send it for review. Merchants buy it at our checkout, and you earn 70% of every sale.
The programme
What you get, and what we ask
WhizzyCommerce is a hosted shop platform. Its theme catalogue is open to outside developers by invitation. You bring the design and keep supporting it. We bring the rest.
| We provide | You provide |
|---|---|
| A showcase for every theme, a shop of its own with a sample catalogue, that never expires | An original theme, with assets you have the right to use |
| A theme workspace, a browser editor, a CLI and a Claude connector | Your own editor, and your own AI plan if you use one |
| Automated checks, screenshots and a human review | A changelog with every version |
| Checkout, tax, licences and updates to merchants' shops | Replies to merchants' support threads within two business days |
| 70% of the price before tax, paid twice a month | Your tax details and a bank account |
Rules we keep
Four principles
These decide most questions before they come up. If something on our side ever contradicts one of them, tell us.
We host tools, not models
Every AI call you make runs on your own Claude plan or your own Anthropic API key. We provide the connector, the files and the checks. WhizzyCommerce never runs AI on its own key for developers.
One source of truth for a theme
Your theme's files live on our side, in a workspace. The browser editor, the CLI and Claude all read and write the same files, so there is nothing to merge between them.
Staff hold the publish button
You submit. Automated checks run first, then a person approves. Nothing reaches a merchant's shop unreviewed, including an update to a theme that is already listed.
Money you can explain
Every sale writes one ledger line you can see. A balance is the sum of those lines, and a payout settles lines, so you can always reconcile what you were paid.
In order
From application to payout
Everything happens at app.whizzycommerce.com, in the Developer area beside Your shops. You never need shell access to our servers.
Apply
DevelopersApply to build themes
Name or company, country, a portfolio link and the kind of theme you plan. Staff approve each application.Accept the agreement and set up payouts
DevelopersAgreement, DevelopersPayouts
Read and accept the developer agreement, then add your tax details and bank account.Start a theme workspace
DevelopersThemes
From the reference theme, from a blank theme, or from a zip you already have.Build with your tool
Browser editor, CLI or Claude
All three work on the same files. See Tools.Prepare the listing
DevelopersThemes
Name, description, category, price and support email. Screenshots are taken for you.Submit
whizzy-theme submitChecks run in about a minute. They either block with reasons, or queue the version for a person.Review
DevelopersThemes
A reviewer approves the version or sends notes. You see the notes on screen, by email and in Claude.Listed
A first version goes on the marketplace. An update reaches shops on an older version as an update notice.Sell and support
DevelopersSupport, DevelopersStats
Merchants buy and install your theme, and reach you through support threads we host.Get paid
DevelopersEarnings
Earnings are rolled up twice a month and paid out a few business days after each period closes, or on request. See Getting paid.
Fit
Who it is for
Web developers and small studios who design shops for a living. You need to know HTML and CSS well. You do not need to know React, a build tool or our internals.
| Good fit | Probably not |
|---|---|
| You design storefronts and want to sell a design more than once | You need JavaScript in the theme. A theme ships none, in any form |
| You like plain CSS over design tokens | You want Tailwind or a CSS framework inside the theme |
| You will answer merchants' questions about your theme | You want to sell once and never hear about it again |
| You already work with an AI assistant, or want to | You expect us to pay for your AI use |
Read next
The guides
Each guide stands on its own. Read them in order the first time.
| Guide | What it answers |
|---|---|
| Getting started | From an approved account to a submitted theme in about fifteen minutes |
| Tools | The browser editor, the CLI with CI, and Claude through the connector |
| Theme format | Folders, theme.json, sections, templates, CSS rules and performance |
| Releases and review | Versioning, the automatic checks, what reviewers look at |
| Getting paid | The split of a sale, payout periods, why sales are final, and tax |
| Marketplace | Listings, ratings, support duty, stats and pricing rules |
| Questions | Ownership, selling elsewhere, teams and transfers |
| Theme reference | Every node, component, data source and token, generated from the validator |