Skip to content
Tutorials Center
My learning

Topics

Lesson 51 of 61 ยท Publishing and Maintenance

Theme Store Requirements and Selling a Theme

Plan a theme for the Shopify Theme Store: presets, documentation, support, performance and accessibility bars, licensing and pricing, plus a self-review checklist.

Most themes are built for one store. A few are built for thousands: they are listed in the Shopify Theme Store, installed by merchants who never talk to you before buying, and judged on how they behave with every kind of catalog. That is a different job. A client theme can assume the client's logo, products and language. A store theme must work with none of those assumptions.

This lesson explains what selling a theme involves, how the review works, which quality bars you must clear, and how to check your own work before you submit. It builds on Theme Check, Linting and Testing, Accessibility in Themes and Theme Performance and Core Web Vitals.

Theme Store rules change. Numbers such as score thresholds, price ranges, revenue share and the count of required presets are set by Shopify and updated over time. This lesson teaches the shape of the requirements and the reasons behind them. Always read the current requirements in the Partner Dashboard before you plan a release. Nothing here runs on this site: the submission steps are read-only, and the TryIt is a JavaScript stand-in that scores a made-up theme against a made-up checklist.

Two ways to sell a theme

You can sell a theme in two ways. Which one you pick changes almost everything else.

  • The Shopify Theme Store. Shopify lists, reviews and distributes your theme. Merchants buy it in the admin and Shopify handles billing. You get exposure and trust, and you accept a review process and a revenue share.
  • Your own channel. You sell a download or a private link on your own site or a marketplace. You set the rules and keep more of the money, but you need your own audience, billing, license enforcement and support desk.

Many developers start with custom client work, grow a reusable base, and only then submit to the Theme Store. The rest of this lesson is about the Theme Store because its requirements are the strictest, and a theme that satisfies them is a good theme anywhere.

How the process works

At a high level, the path from idea to listing looks like this:

flowchart LR
    A["Build the theme<br/>with presets"] --> B["Self-review<br/>checks and audits"]
    B --> C["Submit in the<br/>Partner Dashboard"]
    C --> D["Shopify review"]
    D -->|changes requested| E["Fix and resubmit"]
    E --> D
    D -->|approved| F["Listed in the<br/>Theme Store"]
    F --> G["Support and<br/>updates"]

Review is a loop. Most themes go around it at least once, so build time for fixes into your plan.

You submit from your Partner account (see Setting Up: Dev Store, Partner Account and Shopify CLI). You provide the theme package, listing text, screenshots and a demo store per preset. Reviewers then open your theme in real stores and test it against Shopify's published requirements. If they find problems, you get written feedback and you resubmit.

What reviewers look at

The requirements fall into a few groups. The details move, but the groups are stable.

Merchant experience. The theme must use the Online Store 2.0 model: JSON templates, sections on every page where that makes sense, and sensible settings in the editor. Every visible string must be editable or translatable, never hard-coded. A merchant must be able to build a good page without touching code. This is covered by The Theme Editor and How Merchants Use Your Theme and JSON Templates and Online Store 2.0.

Presets. A preset (also called a style) is a saved set of settings that changes the look of the same theme. A store theme usually ships several presets that look clearly different from each other, each with its own demo store. Presets are not a color swap: reviewers want different layouts, typography or section choices, so merchants see real variety. Presets are described in Global Theme Settings: settings_schema.json and settings_data.json.

Performance. Shopify measures themes with Lighthouse on key pages, such as the home, product and collection pages, and sets a minimum score. Beyond the number, reviewers look for the usual causes of slowness: render-blocking scripts, unsized images and heavy third-party libraries.

Accessibility. The theme must be usable with a keyboard and a screen reader, with enough contrast, visible focus and proper landmarks and headings. Reviewers test this by hand and with automated tools.

Code quality. The theme must pass Theme Check with no errors, use render instead of include, load assets from the theme instead of remote servers where required, and avoid deprecated features.

Localization. Locale files must exist and be complete for at least the languages Shopify requires, with strings pulled through the t filter (see Translations, Markets and Localization).

Documentation and support. You must publish documentation and provide a way for merchants to get help. This is as real a requirement as the code.

Documentation and support are part of the product

Merchants who buy a theme from a catalog cannot ask you what a setting does. Good documentation answers the questions before they are asked:

  • Getting started. Install, choose a preset, add a logo, build a home page.
  • Reference for each section. What each setting does, with a screenshot.
  • Recipes. How to build a size chart page, a lookbook, a sale banner.
  • Troubleshooting. Common problems and their fixes.
  • Changelog. What changed in each version, so merchants know whether to update.

Support means a visible channel (email or a help center), a stated response time you can actually keep, and clear limits: what you will fix (bugs in your theme) and what you will not (custom work, third-party apps). Plan for support as a recurring cost. A theme with a thousand merchants produces a steady flow of questions even when the code is good.

Licensing and pricing

When you list a theme, Shopify sells it for you. Merchants usually pay a one-time license fee per store, and the theme then belongs to that store. Shopify chooses from allowed price points and keeps a share of each sale; the exact numbers are in the current Partner terms, and I will not quote figures that may be stale. Think about three things:

  1. Price versus support. A higher price pays for support time. If you set a low price and promise fast support to thousands of merchants, you will lose money.
  2. Updates. Merchants expect bug fixes and compatibility updates. They also expect not to lose their customizations. Your update story is covered in Maintaining Themes: Updates and API Versions.
  3. Exclusivity and reuse. Read the terms about what you may reuse from client work and what you may sell elsewhere, and make sure no client owns code you plan to resell.

Be careful with third-party code. Libraries must have licenses that allow redistribution inside a commercial theme, and you should keep a list of what you bundle and under which license.

A self-review you can run

Before you submit, check your theme against your own list. The stand-in below does that for a made-up theme. It is not Shopify's review tool, and it checks only what you tell it; its value is the habit of writing requirements as data you can run on every release.

JS A self-review checklist scorer

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The point is the structure: each requirement is a named check with a visible result, so nothing hides behind "I think it is fine".

Stand-in: how presets differ

Presets are easiest to understand when you see two of them next to each other. This stand-in applies two preset settings objects to one tiny template and prints the resulting CSS variables. Real presets are stored in config/settings_data.json and applied by the theme editor; the code below only imitates the result.

JS Two presets, one theme

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Two presets that differ in five of five settings are a real difference to the shopper. Two presets that differ only in the accent color are not, and a reviewer will say so.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Why is a Theme Store theme harder to build than a theme for one client?

    A store theme meets products, content and languages you have never seen, and merchants cannot ask you what to do, so settings, translations and documentation must carry the load.
  2. 2. What should two presets of a store theme differ in?

    Presets are saved sets of settings meant to give clearly different looks. A color swap alone does not give merchants a real choice.
  3. 3. Why does this lesson avoid quoting exact score thresholds and revenue shares?

    Requirements and terms are updated over time. Plan from the current published documents, not from a number remembered from a tutorial.
  4. 4. Which of these is part of the product you are selling?

    Merchants buy a working result. Without documentation and support, even good code produces refunds and bad reviews.

Summary

  • You can sell through the Shopify Theme Store (review, distribution, revenue share) or through your own channel (more control, more work).
  • Review is a loop: submit, receive feedback, fix, resubmit.
  • Requirements cover merchant experience, presets, performance, accessibility, code quality, localization, documentation and support. Read the current numbers in the Partner Dashboard.
  • Presets must look different, not just recolor the same page.
  • Documentation, support and a changelog are part of the product, and support is a recurring cost to price in.
  • Keep a list of bundled third-party code and its licenses.
  • Turn your requirements into a checklist you can run before every release.

Next, learn how to bring an older theme up to this standard in Migrating Legacy Themes to Online Store 2.0.