SaaS Theme Platform overview

SaaS Theme Platform

A SaaS theme changes how a merchant's storefront looks. It does not change how the store works: checkout, payments, stock, customer accounts and order handling stay on tested platform code.

Themes are declarative

A theme package contains only data and styles:

• theme.json (the manifest), JSON templates, and section and block schemas;
• theme settings and their defaults;
• Arabic and English locale strings;
• CSS that follows the CSS policy, plus images and fonts.

No theme JavaScript, server code or template language runs anywhere, including during the build. Each section and block names a platform render primitive (for example banner, product-grid, heading), and the platform renders it. This is what keeps a third-party theme from reading customer data, changing prices or injecting scripts into checkout.

What merchants control

Merchants install a theme from the marketplace and preview it on their own store before publishing. In Store Studio they can reorder, add, hide and configure sections and blocks, and change theme settings. Their changes are stored separately from your package, so they carry over when they update to a newer version of your theme.

Nodes you place with static: true cannot be removed or moved; nodes with locked: true are also read-only and always visible. Use them sparingly, for things such as a header or footer.

From package to marketplace

1. Create a publisher account and a theme in the Developer Portal (Themes), or use an existing account where you hold a role.
2. Scaffold and develop locally with the `saas theme` CLI.
3. Run saas theme check, then saas theme push <theme-id>. The platform extracts the package safely, runs Theme Check and compiles the CSS. Every version records the SHA-256 of its source and of its built artifact.
4. Submit the version for review. Automated review runs first, then a SaaS reviewer approves, requests changes or rejects it.
5. Release the approved version. Merchants see it in the marketplace, and existing installations are offered the update.

Current limits

• Third-party themes are behind a rollout gate. Until it opens, only first-party themes can be installed.
• Paid themes (one-time purchase) run on a test payment provider only; no real money moves yet. See pricing and earnings.
• App blocks from installed apps (@app) are behind a rollout gate. See app blocks.
• saas theme dev (live preview against a development store) is not available yet. Use the merchant preview after pushing.

Next steps

• Package format
• Sections, blocks and settings
• Theme Check and CSS policy
• CLI, review and release