> This page is for Developer.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.bigcommerce.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.bigcommerce.com/_mcp/server.

# Theme Update Process

> **Note**
>
> This is archived documentation for the legacy Blueprint theme framework. For current storefront documentation, see [Stencil](/developer/docs/storefront/stencil/getting-started) or [Catalyst](/developer/docs/storefront/catalyst/getting-started).

Here is how BigCommerce and our partners collaborate to integrate a partner's theme changes/updates into the BigCommerce Theme Marketplace (which merchants also know as our "theme store"):

## Prerequisites

Integrating a partner's theme changes requires these preconditions:

* Partner has an existing theme in the BigCommerce Theme Marketplace.

* BigCommerce sets up a Theme Development store (or converts an existing regular store) and applies the theme. All theme files will automatically be copied into the WebDAV `/template/` directory.

> **Note**
>
> **Template Path Abstracted**
> The Theme Development store resolves the %%GLOBAL\_TPL\_PATH%% variable into /template/. Therefore, assets will be pulled from the /template/ directory, which is accessible via WebDAV or via the BigCommerce control panel.

## Update Process

#### Switch on Theme Development mode

The partner switches on Theme Development mode, by using:
`http://<STORE>/admin/index.php?ToDo=viewTemplates&dev=enable`.

#### Request theme switch

The partner asks BigCommerce to switch a theme. (Partners currently cannot switch it directly, because it's a paid theme.)

> **Note**
>
> This step will wipe out all files in the /template/ directory and copy in the latest version of the integrated theme.

#### Pull changes from GitHub fork

The partner pulls changes from BigCommerce's GitHub fork, to get the most recent version onto their local machine as well.

#### Make changes

The partner makes appropriate changes to CSS/HTML files.

#### Commit and open pull request

The partner commits their changes into the feature branch, and opens a pull request against the BigCommerce fork.

> **Note**
>
> If BigCommerce made conflicting changes (which should happen only when resolving urgent issues), the partner might need to rebase changes (using git rebase master) in order to resolve the conflicts.

#### Email Git URL

Partner [emails](mailto:themestore@bigcommerce.com) their Git URL to the BigCommerce Theme Marketplace.

#### Integration

BigCommerce integrates changes into BigCommerce Themes.

## Other Requirements

* Partners must not change the repository's directory structure or directory names.
* Files should have permission 644 (`rw-r--r--`).
* Directories should have permission 755 (`drwxr-x-r-x`).