World is now on Opti ID! Learn more

PuneetGarg
Dec 3, 2024
  50
(0 votes)

Shared optimizely cart between non-optimizley front end site

E-commerce ecosystems often demand a seamless shopping experience where users can shop across multiple sites using a single cart. Sharing a cart between an Optimizely site and a non-Optimizely site can be a challenge, but it's achievable with the right strategy. Here's a guide on how to set this up.

Overview

The goal is to enable users to share their cart and product information seamlessly across platforms. We achieve this by creating APIs that interact with the cart and product information. I've not added API's here.This implementation covers two scenarios:

  1. Logged-In Users
  2. Anonymous Users

1. Handling Logged-In Users

For logged-in users, leveraging their SSOID ensures that their context, including customer information and cart data, is consistent across sites. The SSOID is passed in the request header from the front end to the API.

 

Implementation Steps

  1. Capture SSOID from Header
    Use the Request.Headers to extract the userId (SSOID) in the backend.

    Request.Headers.TryGetValue("userId", out var ssoId);
    
  2. Fetch Customer Contact
    Using the SSOID, retrieve the logged-in user's context and cart data.
    private static CustomerContact GetCustomer(string ssoId)
    {
        var currentContact = CustomerContext.Current.CurrentContact;
        if (string.IsNullOrEmpty(ssoId))
            return currentContact;
    
        currentContact = CustomerContext.Current.GetContactByUserId($"String:{ssoId}");
        return currentContact;
    }
    
  3. Sync Cart DataWith the CustomerContact object, the cart data can be fetched and synced between the sites.

Key Notes

  • Ensure that the SSOID is securely transmitted in the header.
  • Proper error handling is crucial to avoid unexpected failures if the SSOID is missing or invalid.

 

2. Handling Anonymous Users

Anonymous users lack a consistent SSOID, but their session can still be tracked using a cookie (EPiServer_Commerce_AnonymousId).

Implementation Steps

  1. Capture Anonymous ID from Cookies
    Extract the cookie value that stores the anonymous user ID.

     Request.Cookies.TryGetValue("EPiServer_Commerce_AnonymousId", out var cookieValue); 
    Use Anonymous Cart
    With the cookieValue, fetch the anonymous user's cart from the backend.
  2. Share Cart Across Sites
    Sync the cart data between the sites using the retrieved anonymous user ID.

Key Notes

  • Cookies must be configured for cross-domain access if the sites are hosted on different domains.
  • Ensure proper handling of cookie expiration and invalidation scenarios.

 

API Design

Below is a high-level example of how the API endpoints could look:

Get Cart for Logged-In User

Endpoint: GET /api/cart/loggedin

Header:   userId: <SSOID>

Get Cart for Anonymous User

Endpoint: GET /api/cart/anonymous
Cookie:

EPiServer_Commerce_AnonymousId=<cookieValue>
 

Response Example

Both endpoints would return the cart in a standardized format, e.g.:

{
    "items": [
        {
            "productId": "12345",
            "name": "Product A",
            "quantity": 2,
            "price": 50.0
        },
        {
            "productId": "67890",
            "name": "Product B",
            "quantity": 1,
            "price": 25.0
        }
    ],
    "total": 125.0
}
 

Conclusion

By leveraging SSOID for logged-in users and cookies for anonymous users, we ensure a seamless shopping experience across sites. With a robust API that interacts with the cart and product information, users can enjoy a unified cart system, enhancing user satisfaction and driving conversions.

 

Note:- This is the work only when all sites share the same top main domain.

Dec 03, 2024

Comments

Please login to comment.
Latest blogs
Make Global Assets Site- and Language-Aware at Indexing Time

I had a support case the other day with a question around search on global assets on a multisite. This is the result of that investigation. This co...

dada | Jun 26, 2025

The remote server returned an error: (400) Bad Request – when configuring Azure Storage for an older Optimizely CMS site

How to fix a strange issue that occurred when I moved editor-uploaded files for some old Optimizely CMS 11 solutions to Azure Storage.

Tomas Hensrud Gulla | Jun 26, 2025 |

Enable Opal AI for your Optimizely products

Learn how to enable Opal AI, and meet your infinite workforce.

Tomas Hensrud Gulla | Jun 25, 2025 |

Deploying to Optimizely Frontend Hosting: A Practical Guide

Optimizely Frontend Hosting is a cloud-based solution for deploying headless frontend applications - currently supporting only Next.js projects. It...

Szymon Uryga | Jun 25, 2025

World on Opti ID

We're excited to announce that world.optimizely.com is now integrated with Opti ID! What does this mean for you? New Users:  You can now log in wit...

Patrick Lam | Jun 22, 2025

Avoid Scandinavian Letters in File Names in Optimizely CMS

Discover how Scandinavian letters in file names can break media in Optimizely CMS—and learn a simple code fix to automatically sanitize uploads for...

Henning Sjørbotten | Jun 19, 2025 |