What changed from Vero
Vero2 changes the theme's styling controls and adds product and layout workflows. This guide compares Vero 1.8.3 with Vero2 2.0.0. Check your installed theme version and preview the features your store uses before publishing.
Features with dedicated Vero2 instructions
| Area | Vero | Vero2 |
|---|---|---|
| Color configuration | Color schemes | A global color palette with component and block overrides |
| Typography | Existing desktop typography settings | Additional mobile sizes and global eyebrow typography controls |
| Buttons | Existing colors and button treatments | Separate movement and color effects, timing, magnetic travel, and sizing overrides |
| Layout blocks | Existing sections and builder blocks | Additional columns, statistics, service cards, overlay cards, and image collage compositions |
| Interaction feedback | Existing component feedback | Selection feedback, optional sliding indicators, section entrances, and illustrated empty states |
| Drawers | Existing drawer components | Updated shared drawer infrastructure and direct drawer color controls |
| Hat Lab | Existing guided hat configuration | Additional opt-in styling controls and updated pagination styling |
| Standalone patches | Existing Patch Preview | An opt-in guided Patch builder product template with size, backing, fee, and review steps |
Use Colors and styling, Typography and layout blocks, Buttons and interaction effects, and Drawers and navigation for setup.
Shared features and documentation exceptions
Bulk Order, product fields, accessory selection, Design Gallery, Patch Preview, engraving/apparel previews, minimum quantities, catalog mode, and quote requests remain in both themes. Do not assume a feature is exclusive to Vero2 simply because it appears in recent Vero2 release notes; fixes and preview controls can be shared across both versions.
Vero2 Team Stores support shared passwords and a chosen hub display order. Follow the Team Stores setup guide with the Vero2 slug setup below, then preview access and store ordering before publishing.
Color scheme instructions in existing multi-brand guides require special review because Vero2 uses a different color system. Rebuild brand styling in the theme editor rather than transferring scheme IDs.
Team Store slug setup
Updated Vero2 2.0.0 no longer need a separate slug field for new Team Store entries. Password access uses the entry's built-in metaobject handle when the legacy slug is blank or absent.
For new stores:
- Omit the custom
slugfield, or leave it blank if the definition already includes it. - Select a
landing_pageorlanding_collectionreference for the hub destination. Thecollectionreference alias is also supported. - Keep the built-in metaobject handle stable for password stores. Changing it resets saved unlocks when no legacy slug is populated.
For existing stores, turn off Required on the custom slug field after installing an updated build. Keep populated slug values unchanged: Vero2 continues to use them for saved password unlocks and legacy page or collection lookups. Existing URL destinations also continue to work. Do not delete the field while stores depend on those values.
This replaces the shared guide's required-slug instruction for updated Vero2 builds. The Vero instructions are unchanged. Verify the hub destination and password access on your unpublished theme before publishing.
Brand domains and front/back artwork
Vero2 can apply a Brand from the visitor’s hostname and send the homepage to its landing page while keeping that hostname. This requires Shopify alias domains and explicit Brand mappings. Follow Brand domains.
Vero2 also offers an optional separate back-artwork upload, front/back gallery previews, separate order attachments, and a linked back-design charge. This is not available in Vero 1.8.3. Follow Second-side apparel artwork.