Skip to main content
  • Time — 10 minutes
  • Difficulty — Beginner
What You’ll Learn: A clear picture of the scope and impact of migrating to Cart 2.0, covering data compatibility, URL continuity, payment flow changes, and any UI-level adjustments needed, so your team can plan the migration with confidence and minimal disruption. Prerequisites:
  • An active Upmind account currently running Cart 1.0.
  • Basic familiarity with your existing storefront setup, product catalogue, and checkout configuration.
  • A read-through of Understanding Cart 2.0 to understand what’s new in Cart 2.0 before assessing the migration scope.
Migrating to Cart 2.0 does not change your products, pricing, billing logic, customers, or payment providers. The core commerce layer remains the same. What improves is the presentation layer, configurability, and long-term flexibility. For most teams, migration is straightforward and managed with Upmind’s guidance. There is no need to rebuild your product catalogue or reconfigure billing from scratch. The goal is to modernise the checkout experience without introducing risk.

​
Feature comparison – Cart 1.0 vs Cart 2.0

AreaCart 1.0Cart 2.0
Visual designFunctional, fixed layoutsLighter UI, improved typography, flexible layouts.
CustomizationLimited, code-heavyMetadata-driven, granular control.
ThemingBasic overridesToken-based, scalable theming.
Headless supportNoneNative composables + XState.
State handlingImplicitExplicit, deterministic flows.
ResponsivenessGoodRefined mobile-first behavior.
ExtensibilityTight couplingModular by design.

​
Data compatibility

Core commerce data remains fully compatible between Cart 1.0 and Cart 2.0. This includes:
  • Products and product options.
  • Pricing models and billing terms.
  • Subscriptions and customer records.
  • Orders, invoices, and historical data.
What changes is how this data is presented and controlled, not the underlying data itself. Migration primarily involves mapping existing products and behaviour into Cart 2.0’s metadata-driven layout and configuration model.

​
URL and SEO considerations

Core cart and checkout routes remain unchanged between Cart 1.0 and Cart 2.0, so redirects are not required by default. Cart 2.0 continues to support clean, predictable URLs. During migration, teams should verify that:
  • Existing checkout URLs and deep links continue to resolve correctly.
  • Domain configuration and product ordering paths behave as expected.
  • Indexed catalogue or checkout pages remain accessible where applicable.
A common and safe approach is to keep Cart 1.0 live during testing, validate Cart 2.0 behaviour in production, and then switch traffic without introducing URL changes.

​
Payment flows

Payment logic remains consistent across both versions, ensuring continuity in how transactions are processed and settled. What improves in Cart 2.0:
  • Clearer transitions between checkout steps.
  • Better handling of loading, processing, and intermediate states.
  • More flexible placement of payment actions within the UI.
  • Improved support for both hosted and redirected payment methods.
Payment providers, credentials, settlement behaviour, and reconciliation remain unchanged.

​
Customisations that need rewriting

Most core commerce behaviour carries over unchanged, but some UI-level assumptions may need adjustment. Typical areas to review include:
  • Layout or presentation logic that was previously implicit in Cart 1.0.
  • Any Cart 1.0 specific UI patterns that do not map directly to metadata-driven configuration.
  • Custom flows that depended on less explicit step boundaries.
These changes are usually one-time adjustments that unlock easier iteration and safer evolution going forward.