Theme store requirements

Use the following lists of requirements when creating your theme. All themes must meet the following requirements to be published on the Shopify Theme Store.

Learn about the theme review process and how to submit your theme to the Shopify Theme Store.

All themes must meet the following exclusivity requirements:

Themes listed on the Shopify Theme Store can only be sold through the Shopify Theme Store. Themes on the Theme Store must not sell on other marketplaces.

Themes on the Shopify Theme Store can't contain designer credits, such as a link to a theme developer's website, or any affiliate links in the theme files.

You can build a theme for the Shopify Theme Store using Dawn as a starting point. However, your theme needs to have components and art direction that make it substantively different from Dawn. This ensures that your theme provides added value for merchants.

The theme review team judges theme uniqueness based on many factors, including but not limited to:

  • Theme components: The templates, pages, and sections that are offered in the theme, the theme's features, the way blocks are used, metafield support, and the settings that are offered to merchants.
  • Art direction: The theme's typography, the use of color, and the design of standard theme components such as headers and footers.

All themes must support the following features:

Discounts - Display discount amounts for individual items and for entire orders in the cart, checkout, and order templates. Discounts must be supported on the Cart page.

Learn more about discounts.

Dynamic checkout buttons - Include Dynamic checkout buttons so that customers can quickly buy the product that they're viewing.

Dynamic checkout buttons must be supported on the following pages:

  • Product page
  • Cart page

Learn more about dynamic checkout.

Faceted search filtering - Use search filtering so that customers can filter on collection and search pages based on product availability, price, type, vendor, and variant options. You need to support faceted search filtering on collection pages and search pages.

Gift cards - Include a gift card template that renders the gift card page, which displays the gift card that's issued to a customer upon purchase.

Learn more about gift cards.

Images for social sharing - Add a page_image object for social sharing so that merchants can display a thumbnail image in their post when they share a link to their online store on social media, such as on Facebook or Pinterest.

Learn more about social media images.

Multi-currency - Merchants can enable selling in multiple currencies so that customers can checkout using their preferred currency.

Learn more about selling in multiple currencies.

Multi-language - Merchants can enable selling in multiple languages so that customers can browse the shop and checkout in their preferred language.

Learn more about selling in multiple languages.

Multi-level menus - Add nested menus so that merchants can create multi-level drop down menus.

Learn more about setting up drop down menus.

Newsletter forms - Add a newsletter signup so that merchants can collect customer email addresses to use in email marketing campaigns.

Learn more about newsletter signups.

Pickup availability - Add pickup availability to product pages so that merchants can display whether a product is available for local pickup without having to add the product to cart. Pickup availability must be supported on the Product page.

Learn more about pickup availability.

Product recommendations - Add a section to your product pages that displays an automatically-generated list of product recommendations. Displaying recommended products to customers makes it easier for them to discover new products, and can help to increase online store sales.

Learn more about product recommendations.

Product ratings - If you choose to include product rating elements in your theme, then these elements need to represent Product rating or Product rating count metafield values.

Rich product media - Add rich product media such as 3D models, embedded videos, and Vimeo or YouTube videos to a theme's Product page.

Search box or a link to search - Include a search template.

Selling plans - Merchants are able to create selling plans to offer subscriptions. Selected selling plans need to be shown to customers in the cart and on customer order pages.

Selling plans must be supported on the following pages:

  • Cart page
  • Customer page

Learn more about subscriptions.

Shop Pay Installments - Add a Shop Pay Installments banner on product.liquid to let customers know that they have the option to pay for their order using installments. Shop Pay Installments must be supported on the Product page.

Learn more about Shop Pay Installments.

Unit pricing - Merchants in some areas are required to show unit prices.

Unit pricing must be supported on the following pages:

  • Collection page
  • Product page
  • Cart page
  • Customer page

Learn more about how merchants can add unit prices to products in France and Germany.

Variant images - Enable themes to use variant images so that merchants can associate an image with a product variant.

Learn more about adding images to product variants.

Template support requirements

Themes must support the following templates and their formats:

theme.liquid (layout file)

404.json

article.json

blog.json

cart.json

collection.json

index.json

list-collections.json

page.json

password.json

product.json

search.json

gift_card.liquid

settings_schema.json (config file)

Section support requirements

All templates must support sections (JSON templates), with the exception of Customer Account pages, Gift Card pages, and Checkout, which don't need to support sections.

Themes must include a Custom Liquid section. The section needs to include a setting of type liquid, and should be available on all templates that support sections. The Custom Liquid section can act as an insertion point for certain types of apps.

Block and app block support requirements

Themes must support blocks for all or most elements on the main section of the product page. For example, elements such as product price, product vendor, and product description should each be individual blocks within the main product section. Refer to Dawn's main product section for an example of how these blocks should be implemented.

Themes must support app blocks (blocks of type @app) in the main product section and featured product section.

Optional: Consider introducing Custom Liquid blocks into certain sections. You should consider adding a Custom Liquid block anywhere you'd consider adding an app block, because the Custom Liquid block can act as an insertion point for certain types of apps. This block should include a setting of type liquid.

Learn more about best practices for sections and blocks.

Lighthouse performance and accessibility requirements

Themes must have a minimum average Lighthouse performance score of 60 across the theme's product, collection, and home page, for both desktop and mobile. Tests are run using a benchmark dataset.

Themes must have a minimum average Lighthouse accessibility score of 90 across the theme's product, collection, and home page, for both desktop and mobile. Tests are run using a benchmark dataset.

Testing the performance of your theme

You can quickly test the performance of your theme before you submit it to the Shopify Theme Store by running performance tests against a benchmark shop. If you want to test your theme before you submit it, then refer to these performance best practices.

Testing the accessibility of your theme

You can quickly test the accessibility of your theme before you submit it to the Shopify Theme Store by running accessibility tests against a benchmark shop. If you want to test your theme before you submit it, then refer to these accessibility best practices.

Layout page requirements

If payment method logos are output, then use payment_type_svg_tag to call in payment icons.

The <html> element must specify a lang attribute with lang="{{ request.locale.iso_code }}".

You must include the new Liquid routes object for generating dynamic URLs to your storefront. Instead of href=/ to link to the homepage, you can now use href="{{ routes.root_url }}". This ensures that your theme supports any changes that Shopify makes to the URL format, such as allowing a page to be available in multiple languages.

Product page requirements

The product page must contain the following product information:

  • product.title (not truncated)
  • variant.price
  • variant.unit_price
  • variant's compare-at price
  • product.description

All product images must be displayed and viewable. Different image ratios shouldn't break the layout.

Variant images must be shown when the associated variant is selected.

The product page must contain the following buying functions:

  • Variants that are split up into separate options for users to select.
  • The ability to select a quantity.
  • An Add to cart button (often disabled or replaced when a sold-out variant is selected).
  • A callback function to update the price, compare-at-price, and sold-out messages for the currently-selected variant.
  • The first available variant loads on a page.

The product page must support the following features:

  • Product recommendations
  • Rich product media
  • Dynamic checkout buttons
  • Pickup availability
  • Shop Pay Installments

Collection page requirements

Attributes of the collection object that must be outputted:

  • collection.title (not truncated)
  • collection.description
  • collection.image

Products must be listed in a grid or list, with the following attributes of the product object output:

  • product.title (not truncated and links to product.url)
  • product.price
  • product.images
  • variant.unit_price
  • At least one piece of media for a product

Product grid must not break because of product images of varying aspect ratios.

The Sale badge or product.compare_at_price_max is shown when appropriate.

Must provide the ability to sort the products inside collections.

Must display a message if a collection has no products in it.

If a product has variants with different prices, then use product.price_varies to show the price variation. For example, show the range between product.price_min and product.price_max.

Must use pagination or lazy loading.

Collection List page requirements

Attributes of the collection object that must be outputted:

  • collection.title (not truncated)

Must use collection.featured_image. If a collection image doesn't exist, then load the featured image of the first product in that collection instead.

Must use pagination or lazy loading.

Cart page requirements

Must display details of the line_item object, including:

  • line_item.title
  • line_item.unit_price
  • line_item.variant.title
  • line_item.image
  • line_item.price
  • line_item.quantity

The cart.total_price must be visible.

Must include a checkout button that submits the cart form.

Must refresh all line items when the quantity is updated to ensure the total updates correctly.

Must provide the ability to change the quantity of each line item.

The cart page must support the following features:

  • Cart notes
  • Selling plans
  • Automatic discount codes
  • Dynamic checkout buttons

Page requirements

Must include:

  • page.title
  • page.content

Must include an alternate template for a contact form.

Blog page requirements

Attributes of the blog object must output the blog.title.

Each article must display the following information:

  • article.title
  • article.image
  • article.excerpt_or_content not article.content

Must use pagination or lazy loading.

Article page requirements

An article must display the following information:

  • article.title
  • article.comments
  • article.published_at (but not article.created_at)

Comments must be paginated.

Comments workflow must function without moderation, and all success or error messages must be properly output.

Search page requirements

Must return a message if there are no search results.

The object_type must be used when displaying search results.

Pagination or lazy loading.

404 page requirements

Must have a clear message stating that the page wasn't found.

Must have options for how to proceed, such as a search bar or a link to the homepage.

Gift Card page requirements

Must support Apple Wallet.

Must show a gift card code.

Must show a QR code. The minimum size required is 120px x 120px.

Must include the logo or shop.name.

Customer page requirements

Must display details of the line_item object, including:

  • line_item.unit_price

The customer page must support the following features:

  • Selling plans

Password page requirements

Must include the following information:

All themes must meet the following functional requirements:

All RTE-generated content must be consistent (such as h1-h6, blockquotes, ul, ol) across all templates. Styling of RTE content is consistent with those of blog articles, product descriptions, and collection descriptions.

The following actions must be functional at all times - even when JavaScript is disabled:

  • Navigate through the main menu and any submenus
  • Adjust the inputs in the product form
  • Navigate to the cart page
  • Access the checkout

Any link in the code that points to one of Shopify's domains can take multiple attributes, but must include a rel=nofollow as one of them.

Assets must link using protocol independent URLs (no hard defined http or https).

The appropriate licenses must be obtained for all third party plugins and images.

Themes must not include functionality that is dependent on a third-party app.

Desktop browser requirements

A theme's layout, browsing experience, and purchasing actions must support the following desktop browsers and releases:

Safari - latest two releases for Mac

Chrome - latest three releases for Mac and PC

Firefox - latest three releases for Mac and PC

Edge - latest two releases for PC

Mobile browser requirements

A theme's layout must meet the following mobile browser layout requirements:

Themes must be mobile responsive.

A theme's layout, browsing experience, and purchasing actions must support the following mobile browsers and releases:

Mobile Safari - latest two releases for iOS

Chrome Mobile - latest three releases for Android and iOS

Samsung Internet - latest two releases for Android

Webviews and other application requirements

Themes must support browsing and purchasing actions when rendered in webviews for the following applications:

Instagram - latest release for Android and iOS

Facebook - latest release for Android and iOS

Pinterest - latest release for Android and iOS

All themes must meet the following asset requirements:

Themes must not use Sass, or include .scss or .scss.liquid files. Instead, use only native CSS, and write or compile your stylesheets into .css or .css.liquid files.

Themes must not include minified .css or .js files. Shopify automatically minifies theme CSS and JavaScript when these files are requested by the storefront.

All themes must meet the following SEO requirements:

Themes must contain the code snippet for Title, Meta Description, and Duplicate Content from the SEO for Theme Designers.

Themes must include Google's rich product snippets. To test your structured data, use Google's Structured Data Testing Tool.

Themes must not include a robots.txt.liquid template.

Learn more about SEO best practices.

All themes must meet the following accessibility requirements:

All parts of a page must be keyboard accessible, including dropdown navigation.

When navigating with the keyboard, focusable elements must feature a visible focus state.

Images must have the alt attribute.

Form inputs must have labels with for attributes, including form labels in the theme settings.

Themes must be built with valid HTML.

Themes must output image.alt for all product images. Learn more about image.alt.

Text color contrast ratio must be 4.5:1 for main body content. For text larger than 18pt, and non-text elements such as borders and icons, the color contrast ratio must to be 3:1.

Keyboard focus order must match the DOM order. Focus is expected to move top-bottom, left-right.

Touch targets must have a minimum space of 44 by 44 CSS pixels in areas that are relative. The minimum space doesn't apply to inline body text.

Headings h1-h6 must be visually different from each other.

Learn more about accessibility best practices.

All themes must meet the following requirements for social media:

Must have a set of social media icons to choose from.

Must contain Open Graph and Twitter card tags.

Social media placeholder text must be left empty.

When building Shopify free themes, and assessing themes from our Theme Store partners, a detailed rubric is used to review the design and UX components of the theme. This ensures that the theme is confidently addressing vital areas such as art direction, consistency, typography, layout, and customer UX.

Learn more about design best practices.

Use the following rubric as a guide to better design your custom theme builds.

Art direction

Your theme should have a clear and consistent visual appeal which conveys a message to its target demographic.

Score Description
Meets requirements
  • The design is intentional, well thought out, and follows a logical pattern.
  • Icon sets are consistent and well designed.
  • Logo is well designed and scales effectively to multiple sizes.
  • Color system is robust and easy to customize without harming the aesthetic or legibility of isolated components. There is a good level of flexibility for merchants to customize their color palette without the task being overly complex.
Improvement needed
  • Instances of inconsistency.
  • Images aren't as high quality as they could be.
  • Logo resolution isn't up to preferred standards.
  • Icons lack consistency or don't match the overall design of the theme.
  • The theme's color system could be simplified further.
Critical improvement needed
  • Several inconsistencies make the design decisions seem unintentional.
  • Poor image quality.
  • Logo resolution isn't up to preferred standards.
  • Icons aren't consistent or don't match the overall design of the theme.
  • The theme's color system is too complex, rigid, or difficult to customize without harming the legibility and visual balance.

Layout

Your theme should have a good flow of content, hierarchy, balance, contrast, white space, responsiveness, grid, and alignment.

Score Description
Meets requirements
  • Provides a clear path for navigation between pages and emphasizes the most important elements of the store.
  • Balanced and well-defined grid.
  • White space is thoughtfully applied.
  • All elements adhere to a grid.
  • All unrelated elements are easily distinguished from each other.
  • Clear hierarchy for how primary and secondary information is displayed.
  • Design patterns scale in a way that makes sense across small and large screens.
Improvement needed
  • Unbalanced grid.
  • Too much or too little white space is used.
  • Only some elements adhere to a grid.
  • Elements are easily confused with each other.
  • Unclear hierarchy for displaying primary and secondary information.
  • Design patterns don't scale correctly across small and large screens.
Critical improvement needed
  • Elements are placed outside the grid in a way that affects scaling to smaller screen formats.
  • Content is unbalanced and disproportionate.
  • Whitespace is used in excess or is lacking to a degree that disrupts flow.

Consistency

Your theme design elements should be consistent across all pages.

Score Description
Meets requirements
  • Consistency across spacing, icon style, image quality, typography, and color.
Improvement needed
  • Inconsistency across one or more sections, spacing, icon style, image quality, typography, or color.
Critical improvement needed
  • Critical inconsistency across one or more sections, spacing, icon style, image quality, typography, or color.

Accessibility

Accessibility encompasses the inclusion of implementations such as (but not limited to) keyboard navigation, screen reader compatibility, high contrast coloration, and thoughtful font selection to provide users with alternative means of navigating a system with comprehensive ease.

Score Description
Meets requirements
  • Color contrast between elements is clearly defined.
  • Touch targets are clearly defined and not in conflict with each other.
  • Inputs are easily identifiable.
  • Excludes the use of justified text as default.
Improvement needed
  • Purchase flow is unclear or complex.
  • Product options aren't very obvious or visible.
  • Inputs aren't easily identifiable.
  • Some friction within the customer experience when shopping for a product/service.
Critical improvement needed
  • Purchase flow is very unclear or overly complex.
  • Product options aren't obvious or visible.
  • Inputs aren't identifiable.
  • High friction within the customer experience when shopping for a product/service.

Customer UX

Your theme should provide a clear purchase flow through the collection, product, and cart pages.

Score Description
Meets requirements
  • Purchase flow is clear and unobstructed.
  • Product options are obvious and visible.
  • Inputs are easily identifiable.
  • A frictionless customer experience when shopping for a product/service.
  • Products are recommend for customers.
  • Theme provides brand awareness (Blogs, etc.).
  • Customers can:
    • Navigate the merchant's site with ease.
    • Search meaningfully for desired products (Discovery).
    • Interact with products/services (Featured content/collections/product pages).
    • Add/change/remove products with a comprehensive cart system (cart modal/page).
    • Proceed to checkout in a clear path.
Improvement needed
  • The theme settings are too complex.
  • Risk of the merchant becoming confused or frustrated.
Critical improvement needed
  • Overly complex theme settings.
  • High risk of the merchant becoming confused or frustrated.

Merchant UX

Your theme should have clear and simple options for merchants to customize the look and feel of their shop.

Score Description
Meets requirements
  • A good balance between opinionated theme settings and flexibility.
  • Designed with the merchant experience in mind.
Improvement needed
  • Little balance between opinionated theme settings and flexibility.
  • Rarely designed with the merchant experience in mind.
Critical improvement needed
  • No balance between opinionated theme settings and flexibility.
  • Not designed with the merchant experience in mind.

Basic requirements

All theme settings must adhere to the style and terminology requirements.

Must have a favicon setting.

Logo upload must work with images of different aspect ratios (for example, landscape vs. portrait).

All settings must have a label.

Must have a theme_info section.

Style requirements

Write section, preset, and category names in sentence case. Only capitalize the first word and proper nouns (like 'Facebook').

Use descriptive setting names for multi-option settings or sections of different variations. Avoid using numbered options or section titles.

Use this Don't use this

Logo position on large screens

  • Middle left
  • Top left
  • Top center

Logo position on large screens

  • Position 1
  • Position 2
  • Position 3

Theme sections

  • Collage
  • Image banner
  • Image with text

Theme sections

  • Image 1
  • Image 2
  • Image 3

Use American English.

Use this Don't use this
canceled cancelled
catalog catalogue
center, centered centre, centred
color colour
customize customise
dialog dialogue
gray grey
organize organise

Don't use ampersands ( & ).

Use declarative statements instead of questions.

Use this Don't use this
Use a custom logo Use a custom logo?

The subject of each section (like 'slideshow') is stated only once in the heading. Avoid subject repetition, such as 'slideshow', 'slideshow color', and 'slideshow image'.

Use active voice.

All buttons and actions must start with a verb.

All technical specifications follow these formats:

Technical specification Format Example
Image size [numeral] x [numeral]px (required/recommended) 64 x 64px required
Image size with format [numeral] x [numeral]px [.format] (required/recommended) 1200 x 300px .jpg recommended
Word / character count [numeral] words (max) 32 words max
Text format Use basic HTML to format text

Terminology requirements

Use the following Shopify terminology throughout your theme:

Use this Don’t use this
home page homepage
top bar meta-nav, search bar
bottom bar below footer, legal
slideshow slider
checkout
(when naming settings)
check out
heading title
subheading sub-heading
body text main text
signup sign-up, sign up
favicon shortcut icon, website icon
sidebar side bar
button label button name
social media
(when naming sections or settings)
social, social sharing
social media icons social media buttons
navigation
(to refer to all navigational elements)
menus, menu
main menu
(to refer to primary navigational element)
navigation, menu
secondary menu
(to refer to secondary navigational element)
navigation, menu
footer menu
(to refer to a menu located in the footer)
navigation, menu
cart type
(with "drawer", "page", and/or "modal" options)
Ajax, Ajaxify, Ajax cart
.png PNG, png, .PNG
use
(for actionable options that include a next step, such as uploading a file)
show, enable
show
(for options that allow the merchant to show or hide a basic element)
use, enable
enable
(for options related to apps or plugins, or something that will significantly modify the theme layout)
use, show

Section name guidelines

Each section in a theme needs a name. Section names appear in the section picker and in the sidebar listing the sections in a template.

Section example

Section names should relate to the section's function, for example Header, Product list, Slideshow, or Image gallery.

Refer to Shopify's theme terminology list to make sure that you name sections using the right Shopify terms.

Suggested section names

  • Header
  • Featured products
  • Featured collections
  • Slideshow
  • Image gallery
  • Logo list
  • Newsletter
  • Map
  • Blog posts
  • Testimonials
  • Footer

Preset name guidelines

Section presets are predefined configurations of sections that merchants start with when adding content.

Section preset example

Preset names should relate to the type of content in the preset, for example Image and text, Map, Columns, or Blog articles.

Refer to Shopify's theme terminology list to make sure that you name presets using the right Shopify terms.

Content placeholders

If your preset features images, videos, or icons, then you should display placeholder content so the merchant can get a better idea of how the content looks before they add their own media.

In your presets, use the following content placeholders:

Type of content Placeholder
Images that aren't products or collections
Adjacent images without margins
Image icon
Lists of logos Logo icon
Slideshows
Images with overlaid text
Full-width images
Lifestyle image
Videos Default YouTube video ID

Font pickers must have the following settings:

The font_picker setting type is declared in settings_schema.json.

A default font is loaded. For example, default: work_sans_n6.

The CSS file loads bold, italic, and bold-italic variants for each font using the font_modify filter.

Learn more about setting fonts.

A minimum of 4 colors are required.

All background color settings must include a corresponding foreground color setting.

Learn more about color system best practices.

All themes must meet the following image requirements:

Images must adopt a responsive image strategy. Small images such as icons are excepted.

Images must load only as they are needed to minimize the number of images loaded initially per page.

Theme and theme style naming requirements

Theme names must be distinct from Shopify products. You can't use the same name as, or similar to, Shopify products, events, or branded content. For example, don't name your theme Shopify, Unite, or Polaris.

Theme names must be distinct from company names. You can’t include the name of your company or Shopify Partner account in your theme name. Your Partner account name is displayed automatically on the theme listing page.

Theme names must be distinct from websites, ecommerce platforms, and SEO-related benefits. For example, don't name your theme Slideshow, Performance, Mobile, or Sales.

Theme names must be distinct from industries and collections in the Theme Store. For example, don't name your theme Fashion, Electronics, or Jewelry.

Theme names must contain 14 characters or fewer.

Theme name guidelines

Use the following guidelines to help you choose the right name for your theme:

  • Summarize, or allude to, the purpose of the theme.
  • Give the merchant an idea of what to expect when using the theme, the core ideas behind the theme, and the theme's target demographic.
  • Use a noun for the name. Nouns are more suitable for creating product names that stick, have identity, and create a lasting impression. A noun can better define the focus of the theme, and offer a better understanding of the shopping experience being offered.
  • Use a name that's easy to spell and pronounce. This will help merchants with recall and search.
  • Work across different dialects. Since some words and phrases can have different meanings in different regions, you should consult with an idiom dictionary.
  • Use a name that's different from theme names on different platforms.

Theme style name guidelines

Use the following guidelines to help you choose the right name for your theme style:

  • Reflect the design and aesthetics of the theme style.
  • Use an adjective for the theme style name. Adjectives are great for describing colours, fonts, and design.
  • Compliment the theme name, not compete against it. Merchants often mistake theme styles for theme names, which causes confusion when they contact support to request help with their themes.
  • Use a common thread to connect multiple style names for one theme.

Increasing clarity and discoverability

For clarity and discoverability, consider the following guidelines when naming your theme and theme style:

  • Don't use trendy names. Trends fade, and theme names should transcend trends.
  • Don't use unusual spellings. Not only are unusual spellings more difficult to remember, but they’re also more susceptible to autocorrect errors, and they limit discoverability by merchants.
  • Don't use lengthy names. Even if you’re trying to be descriptive, creating a long name can hurt a merchant’s ability to remember what your theme is called.
  • Don't use the same name as a theme on a different platform.
  • Don't use the same name for both the theme and the theme style.

To build your demo store, you can use a Shopify development store free of charge.

Demo store requirements

All themes must include at least one demo store.

Each preset requires a demo store. You can use up to 5 demo stores for each theme.

Each demo store has the Bogus Gateway enabled, and all other checkout options disabled.

All demo store pages must use authentic text content. Don't use Lorem Ipsum or onboarding text. Don't include profanities.

The powered_by_link link can't be altered and must contain only powered_by_link.

Affiliate linking isn't allowed.

Any link in the code that points to one of Shopify's domains must include a rel="nofollow" attribute.

To avoid potential merchant confusion, demo stores can only showcase elements and functionality that are built into the theme. For example:

  • Don't use embedded text or buttons in images, except for the text on physical products, infographics, badges, or instagram images.
  • Don't use animated gif images.
  • Don't use apps. In some cases, special consideration applies to Shopify’s product reviews and free translations apps. If you're showcasing multi-language options using translation apps, then all content must be translated.

Demo store recommendations

When designing your demo store, consider the following recommendations to help you showcase the full potential of your theme. The following recommendations aren't mandatory requirements that need to be met for submission.

  • Ensure that the proper rights have been acquired for all images and content. If you’re looking for a good source of royalty free images, try Shopify Burst.
  • Identify the source of any product images used in the product description.
  • Use the latest version of your theme in your demo store.
  • Incorporate built-in Shopify features to showcase the power and capabilities of your theme.
  • Illustrate the versatility and variability of your theme, by including examples such as a product that's on sale, a sold-out product or variant, a product with multiple variants, and a gift card product.

Documentation and contact form requirements

You must provide theme documentation and a public support contact form.

You must have your theme documentation and contact form ready before launching your theme.

You must link your documentation and contact form to your theme listing page in the Shopify Theme Store.

Merchant-facing theme documentation

You need to keep your documentation up to date as changes occur within Shopify and you update your theme. As you support merchants using your theme, be sure to identify any gaps in your theme documentation and make updates as necessary.

Your theme documentation should include an FAQ section and any other relevant information that you feel could help address potential support questions that merchants might have.

Clear support policy

Consider specifying your support policy in your theme documentation. As a theme partner, you must support bug fixes and answer any merchant questions regarding your theme. You might want to provide additional services to merchants such as customizations, app-integrations, and help with theme updates, but you can't include these services in the cost of your theme.

Clarity on custom code tutorials

If you offer custom coding tutorials in your documentation, then specify whether the custom tutorials are supported. Also, include a warning to merchants in your tutorials that they should duplicate their theme before editing their code, and include a suggestion that merchants hire a Shopify Expert for help.

Contact Forms

Your contact form lets merchants contact you. You should include your contact form in your theme documentation. If you use a modal for your contact form, then make sure that it's mobile friendly and linkable from the Theme Store. Try to avoid fields that ask merchants about budget, phone numbers, project type, or other unnecessary questions. You can have a form outlining your agency work on a separate page, but the contact form that you link to from the Theme Store should comply with the following guidelines.

Field Guideline
(First and Last) Name Field
Email Address Field
Store URL Field Include an example URL for clarity, such as http://www.storename.myshopify.com.
Description of Problem Field This should be a text-area field.
File Upload Function Allow merchants to highlight their issues with images.
Auto-responder Function The auto-responder is triggered when the contact form is submitted to reduce the amount of merchants contacting Shopify and Theme Partners asking if their support requests have been received.
Theme Name Provide the theme name if you offer multiple themes.
Subject If you include this field, then it should auto populate the email subject line.

Merchant-support requirements

Estimating the support workload

Being a theme partner is a full-time job, and supporting merchants who use your theme is a large part of that. All of our current theme partners have dedicated support teams working for them. If you become a theme partner, then you’ll need to consider how to balance theme partner work with any other jobs that you're currently doing. New theme partners typically underestimate the amount of time that they'll need to allocate to support.

"Merchant support is by far the most challenging part of being a theme partner"

-- Archetype themes

To understand how much effort is required to support a theme, Shopify merchants currently generate thousands of support tickets each month for the paid themes in the Shopify Theme Store, and support requests continue to grow as more merchants join the platform.