Answers from our docs and articlesesc to close
Try asking
Create an accountSign up

Theme Store readiness on every pull request

Ten Theme Store requirements a file can show, checked on every theme pull request with no model, and what is still left to Shopify's manual review.

Key takeaways

  • Auditor's Theme Store readiness checks ten requirements a theme's files can show, such as the required templates, app blocks in the product sections and no Sass or minified files, on every review.
  • The check run lists all ten as passing or failing for the whole theme, and a file the pull request changes that fails one gets a finding. No model is called, so it costs nothing.
  • Requirements that need judgement, such as alt text, keyboard access and fonts through font_picker, are in a ruleset template of twelve rules that starts in dry run.
  • Shopify's review still decides the rest: uniqueness, Lighthouse scores, browser support, demo stores, presets and documentation.

A theme submitted to the Shopify Theme Store is reviewed by people at Shopify against a long list of requirements, and one that misses any of them is sent back to be fixed and resubmitted. Updates go through review too, and a theme that passed in spring can drift out of line over a summer of pull requests: a template deleted in a refactor, a minified library that wasn't a third-party one, a new product section without app blocks.

Most of those slips are visible in the files. So Auditor checks them on every pull request, while the change is still small and its author still remembers why they made it.

The ten checks, and the requirement each one maps to

Theme Store readiness reads the whole theme at the pull request's head. Each row below is one check, with the line of Shopify's Theme Store requirements it comes from, as that page read on October 23, 2026. The section numbers are the page's own on that date.

CheckPasses whenShopify's requirement
Required fileslayout/theme.liquid, config/settings_data.json, config/settings_schema.json, templates/gift_card.liquid and the JSON templates 404, article, blog, cart, collection, index, list-collections, page, page.contact, password, product and search all existSection 5: the theme must support these templates, and all templates except customer account pages must be JSON templates
App blocksThe main section of templates/product.json, and sections/featured-product.liquid if there is one, list { "type": "@app" } in their blocksSection 5: app blocks in the main product section and the featured product section
lang<html> in layout/theme.liquid has a lang attributeSection 7: "The <html> element must specify a lang attribute."
Section groupsThe layout renders the header and footer with {% sections %}Section 5: header and footer sections rendered within section groups
No SassNo .scss or .scss.liquid filesSection 10: no Sass
No minified filesNo .min.js or .min.css, and no stylesheet or script in assets/ with a line over 2,000 charactersSection 10: no minified CSS or JavaScript, except ES6 and third-party libraries
Files not allowedNo config/markets.json or templates/robots.txt.liquidSection 5 says not to submit config/markets.json; section 11 rules out robots.txt.liquid
Custom LiquidSome section has a setting of type liquidSection 5: the theme must include a Custom Liquid section
theme_infoThe settings schema has a theme_info groupSection 14: "Must have a theme_info section."
FaviconThe settings schema has an image_picker setting with favicon in its idSection 14: "Must have a favicon setting."

The minified check is the loosest. Shopify allows third-party libraries, and a file can't say who wrote it, so a minified file is a Low finding to look at, not a failure to fix. Every other finding is Medium.

What a review shows

The check run gets a checklist for the whole theme, headed with a count such as "9 of 10 checks pass". Each failing check names what failed: the missing template, the section without an @app block, the Sass file.

Findings go only on files the pull request changes, so a pull request that edits the cart drawer isn't buried in comments about a minified file that has been in the theme for a year. That file stays on the checklist instead. In practice:

  • A missing required file gets a finding only when this pull request removes it.
  • A product section without app blocks gets one when the pull request edits that section, placed on its {% schema %} line.
  • A Sass, minified or disallowed file gets one when the pull request adds or changes it.
  • Custom Liquid has no file to point at, so it shows only on the checklist.

For the lang check, the fix the finding suggests is the one most themes use:

<html lang="{{ request.locale.iso_code }}">

No model is called, so the checks cost nothing, and they run with either review depth. A repository whose theme comes out of a build step is skipped, because the files in its pull requests aren't the theme Shopify would receive. The theme is found as layout/theme.liquid next to config/settings_schema.json, at the root or in a folder.

What Theme Check already covers

Some requirements are already enforced by Shopify's Theme Check, so readiness leaves them to it: a label on every setting, URLs built from the routes object rather than written out, assets linked without a hard-coded http or https, and leaving content_for_header alone. Thorough reviews run Theme Check on a theme, with your own .theme-check.yml, and post its offenses on the lines the pull request added. If you run Standard reviews, run Theme Check in your own CI to cover these.

The judgement calls: a ruleset template

Many requirements can't be read from a file list. Whether an image needs alt text depends on the image, and whether a menu works from the keyboard depends on its script. For these, start a team ruleset from Theme Store template under Team rulesets on the Auditor page. It holds twelve rules, checked by the rules pass with a model:

  • Alt text on images, labels on form fields, a visible focus state and keyboard access (Shopify's accessibility section).
  • rel="nofollow" on links to Shopify's domains.
  • Payment icons from shop.enabled_payment_types, in full color.
  • Header and footer menus that default to main-menu and footer.
  • Fonts from font_picker with a default, with bold, italic and bold italic loaded through font_modify, and no custom fonts.
  • A foreground color setting for every background color setting, with colors as color settings.
  • The product page's parts as blocks.
  • No designer credits, affiliate links or dependencies on an app.
  • Settings text in American English.

Like every new team ruleset it starts in dry run: findings are recorded on the ruleset's page and not posted. Run it for a week or two, read what it found, edit or delete the rules that don't fit your theme, then switch it to enforced. Set Applies to to your theme repositories, so the rules never run on anything else.

What no check covers

Plenty of the requirements are about the theme as a product, and only Shopify's reviewers decide them. Neither the file checks nor the ruleset touch these:

  • Uniqueness. The theme must be fundamentally different from others in the Theme Store, including your own. Shopify's Skeleton theme is the only approved base, and themes built on or derived from Dawn or Horizon aren't eligible.
  • Lighthouse scores. An average performance score of at least 60 and accessibility of at least 90, across the home, product and collection pages on desktop and mobile.
  • Browser support. The listed desktop and mobile browsers, and the Instagram, Facebook and Pinterest webviews.
  • Color contrast. 4.5:1 for body text, and at least four colors in the color system.
  • Demo stores. At least one for every preset, with test payments, no apps, and real content rather than Lorem Ipsum.
  • Presets and naming. One preset named after the theme, and templates showing each preset.
  • Documentation and support. Public theme documentation and a support contact form.

Passing all ten checks means the theme hasn't slipped on the requirements its files can show. It doesn't mean the theme will be approved.

Turning it on

Theme Store readiness is off by default, since most theme repositories are custom themes for one store. Turn on Theme Store readiness in a theme repository's overrides on the Auditor page, and its next review adds the checklist. To see where the theme stands before then, open a small pull request and read the check run.

Frequently asked questions

Does Theme Store readiness cost anything?

No. The ten file checks call no model, so nothing is billed for them. The Theme Store ruleset template's rules run in the rules pass, which is billed as inference like the rest of the review.

Will passing these checks get my theme approved?

No. They cover the requirements a theme's files can show. Shopify's reviewers also judge uniqueness, Lighthouse scores, browser support, demo stores, presets, documentation and design, and no check covers those.

Why didn't a failing check comment on my pull request?

Findings go only on files the pull request changes. A failure elsewhere in the theme, such as a minified file added long ago, shows on the check run's checklist instead.

Does it work on a theme that is built from source?

No. When a repository's theme comes out of a build step, the files in its pull requests aren't the theme Shopify receives, so the readiness checks are skipped.

One bill for your apps, your models and your reviews.

Host apps and functions next to your model traffic. Routing picks each turn's model by your quality floor, and Auditor reviews every pull request against your own rules.