Managing Versions

A Version is a complete checkout configuration: template, flags, props, theme, messages, and the components and functions deployed to it. This page is the reference for the Versions area of the Admin. The concepts page explains why you would want more than one.

​

The versions list

Open Versions in the store sidebar. Each card shows the name, when it was last updated, and three badges: Default (only on the default version), Active or Inactive, and the template. Click a card to open the version. Every store needs exactly one version that is both active and default: that is the one shoppers get, and the checkout needs it to render.

​

Creating a version

Create Version asks for a Name, a Template (Default, Grocery or Sales, see Templates) and whether it starts Active. A new version is never the default; you promote it later from its General Configuration tab. The template also selects which set of default texts the checkout loads, so switching templates can change wording you overrode in the Messages tab.

​

Duplicating a version

Open the card’s actions menu and choose Duplicate. The copy is named <name> (copy), is created inactive and not default, and carries over the template, theme, props, messages, and every component and function of the source. Components reuse the builds already deployed, so nothing is rebuilt. The live storefront is not affected until you activate the copy. This is the fastest way to branch an experiment off the version in production.

​

The version page

View version opens the checkout on this version in a new tab. It only works for an active version; an inactive one falls back to the store’s default. The ID next to the name is the version id the CLI accepts in ollie.json and create-ollie-shop --version-id, and the value of the ?version_id= query parameter.

​

General Configuration

Changes are saved with the Save button at the bottom. Only the fields of this tab are written; the Props, Theme and Messages tabs keep their values.

​

Props Configuration

Custom props (steps, font, form config, your own keys) and the flag groups. See Checkout Flags, Extra Checkout Steps, Fonts and Form Fields. The tab has a UI view and a JSON view; both save with Save Changes.

​

Theme Configuration

The design tokens of the version. See Theme Design Tokens.

​

Messages Configuration

Text overrides and translations. See Translations.

​

Deleting a version

Delete Version in the Danger Zone removes the version and, with it, every component and function deployed to it. It asks for confirmation and cannot be undone. Only organization owners and admins can delete versions.

​

Related

• Versions: the concept, and how to open a specific version with ?version_id=
• Managing Components in the Admin: the records that live inside a version