Complete checkout configurations that let you test, deploy, and manage different checkout experiences safely
Why must all checkouts look the same? How come the purchase experience in a Grocer is almost identical to shopping for a T-Shirt? If I’m purchasing one product, should the checkout be the same as when I’m buying five? Should the Cashback component only be displayed on the last step of checkout, or if we have a component on the cart page there is a chance we increase conversion rates?Stop being stuck with one checkout design forever. Versions let you create, test, and deploy different checkout experiences without affecting your live store until you’re ready.
Versions are complete, independent checkout configurations. Since you can assign a template to a version, you can make versions completely different from one another.
Pro Tip: You can change versions using a query string paramenter ?version_id={version_id}
This will only work in “development”, meaning that you can only change versions via a query string
when using: