424 command network
⌘ K / Ctrl K

Command hints

Quick routes
↑↓ select Enter openEsc close

Vero2 release notes

These notes track Vero2 features and fixes separately from upstream Horizon releases. The first public release is Vero2 2.0.0. Earlier invitation-only builds used beta version numbers, including 2.0.1; those entries below are historical and do not indicate a newer public release.

Vero2 2.0.0 — First public release

  • A refreshed foundation: updated styling, a global palette, mobile typography, expanded customization, and more flexible section and block layouts.
  • Live Preview: Patch, Engraving, and Apparel previews, with product-specific positioning controls and optional sample artwork. The guided Patch Builder provides an additional opt-in ordering workflow.
  • Included with Vero: no additional theme charge for new or existing customers, under the same licensing rules. Vero2 is recommended for new stores; Vero 1 remains supported and available on request for compatibility needs. Both versions continue receiving support and important fixes.
  • Public documentation: setup guides, migration help, and troubleshooting are now available without an invitation password.
  • An optional new theme version: moving from Vero 1 requires manually rebuilding theme configuration and layouts. Settings and customizations do not automatically transfer. See Moving from Vero to Vero2.

Vero and Vero2 share the same major features. Installing Vero2 is not required to keep using your existing Vero features. Feature availability and setup details can differ by version; follow the guides for your installed theme.

Earlier invitation-only build history

October 20, 2026 — Team Store setup build update

The theme version remains 2.0.1. This change is included in updated store builds without a separate public version release.

  • Simpler Team Store setup: new entries can leave the custom slug blank or omit the field. Password access uses the entry's built-in metaobject handle automatically. Select a linked page or collection for the hub destination.
  • Existing stores keep working: populated legacy slugs continue to identify saved password unlocks and provide fallback page or collection links. Keep those values in place while stores rely on them.

See Vero2 Team Store slug setup before changing an existing definition.

October 19, 2026 — Apparel preview build update

The theme version remains 2.0.1. These changes are included in updated store builds without a separate public version release.

  • Front or Back for the first upload: offer the included print on either side. Only the optional second-side checkbox selects its configured add-on fee.
  • Color-specific back photos: match custom color names with tags such as heather-storm-apparel-back. Sizes need no separate tags or duplicate photos. Matching back photos can remain available with variant-image hiding enabled, including strict mode.
  • Matching Front/Back controls: the first-print and preview-side controls share variant-button styling and selection animation. The default checkbox wording is “Add a separate design to the other side”; merchant wording remains editable and is displayed as saved.
  • Reliable product and color selection: the page product controls tag eligibility and product metafields even when a fee product is selected. Vero2 color changes update the back preview and keep the chosen side visible.
  • Clear order attachments: the order records the first print side and labels the second upload and mockup for its physical Front or Back side.

See Second-side apparel artwork and gallery filtering setup.

October 17, 2026 — Store build update

The theme version remains 2.0.1. These additions are included in current store builds without a separate public version release.

  • Sample preview artwork: choose an optional example image in Apparel preview or Engraving preview. It stays until a valid customer upload loads and returns when the customer removes their upload. Samples never satisfy required-artwork validation, enable paid back designs, or attach to orders. Apparel samples use the front preview only. Leave the setting blank to keep existing behavior.

See Sample artwork setup.

Vero 2.0.1 beta — October 4, 2026

More reliable product choices

  • Designs selected on one product no longer become the selection for a different product or design-picker block.
  • Gallery links return the chosen design to the intended product, including patch designers placed outside the usual product-form area.
  • Conditional fields correctly treat unchecked checkboxes as unselected. Patch designers can also follow another property: hidden designers stop requiring artwork and adding patch charges. See Conditional patch designers.
  • Fee and minimum-quantity mappings handle entries entered on separate lines more consistently. See Design selections and conditional options.

Recently added to the beta

  • Separate front and back artwork: customers can opt into a back design, upload its original file, and switch between matching front/back photos. Optional charges can apply per garment or once per customized cart line. See Setup instructions.
  • Brand domains: a mapped alias domain chooses the brand across the storefront and can open its landing page without switching hostnames. See Brand-domain setup.
  • Consistent option buttons: radio-style custom selects can match your product variant buttons when enabled.

These options start disabled and require configuration. Preview each workflow, its order attachments, and linked charges before publishing.

October 2 2026

Product fields

Radio-style custom selects can now match the theme’s product variant buttons. Turn on Match product variant buttons in the block to use the configured button shape, colors, and selection effects.

Documentation baseline

The Vero2 beta docs cover the palette system, mobile typography, additional layout blocks, button effects, interaction feedback, drawers, Hat Lab styling, migration, and the guided Patch Builder. Shared Vero features link to existing guides with Vero2 exceptions identified.

September 30 2026

Cart fee linkage

Custom fee lines track their parent cart items. Verify quantity updates and removal when multiple configurations of the same product are in the cart.

Upstream Horizon update

This update includes Horizon 4.2.0 improvements to right-to-left languages and cart updates after using the browser's Back button. Preview your catalog, quote requests, customizations, and add-on charges before publishing.

September 29 2026

Hat Lab inputs

Hat Lab retains normal component input styling, including custom-select border radius and focus glow controls.

Preview cleanup

Guided and standard patch designers share cleanup controls. Cleanup affects the preview image; the original customer upload remains the production artwork.

September 27 2026

Guided patch ordering

Added the opt-in Patch builder product template with standalone preview, artwork-first controls, material choices, recommended shape dimensions, custom sizing, backing choices, linked charges, quantity estimates, and order review.

Template installation does not assign it to products. Review material selections, configure charge products, and enable the 424Discounts data bridge when using tier estimates. See Guided Patch Builder.

Hat Lab styling

Added opt-in block styling controls to Hat Lab. Review existing colors and field treatments before enabling additional appearance changes.

September 26 2026

Image galleries

Added featured-grid and heading options to the image gallery. Check existing gallery layouts after changing the featured arrangement.

Earlier beta features

The current beta also includes the global palette/component color system, mobile typography and eyebrow controls, additional layout compositions, independent button movement/color effects, modern surface options, interaction feedback, and updated drawer components. See the linked setup guides for the controls available in your installed beta build.

Before updating a store

Keep an unpublished preview and test your ordering flows, uploads, fee linkage, navigation, languages, and app integrations. Read Moving from Vero to Vero2 and Setup notes and troubleshooting before publishing.