​
What are Versions?

Why should all checkouts look identical? The shopping experience for groceries shouldn’t be the same as buying a single t-shirt. Versions enable you to create multiple variations of your checkout experience, each optimized for different scenarios.

Every store begins with a default Version, and you can create unlimited additional versions to customize your checkout experience.

​
Use Cases for Versions

  • A/B Testing: Compare different layouts and features to optimize conversion
  • Customer Segmentation: Tailor experiences for different user types
  • Product Categories: Customize checkout flow based on items in cart
  • Seasonal Campaigns: Create special experiences for holidays or events
  • Development: Test new features safely before going live
Components and Functions are always associated with a specific Version

​
Version Navigation

​
URL Parameter Method

Add the version ID as a query parameter to your checkout URL:

yourstore.com/checkout/cart?version_id=02c047a8-f109-4998-a258-0ef40d258ca3

This automatically sets a cookie (ollieshop_store_version_id) in the user’s browser to maintain the version throughout their session.

​
Programmatic Assignment

You can also assign versions programmatically based on:

  • User attributes
  • Cart contents
  • Geographic location
  • Traffic source

​
Managing Components and Functions

When creating components or functions, you must associate them with a version to make them active. This allows you to:

  • Test new features in specific versions
  • Roll out changes gradually
  • Maintain different configurations per version

​
Best Practices

  1. Start Simple: Begin with your default version and gradually add variations
  2. Test Thoroughly: Always test new versions before directing traffic to them
  3. Monitor Performance: Track conversion rates and user behavior across versions
  4. Document Changes: Keep track of what makes each version unique