A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More

PuneetGarg
Dec 3, 2024
  89
(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
A day in the life of an Optimizely OMVP: Learning Optimizely Just Got Easier: Introducing the Optimizely Learning Centre

On the back of my last post about the Opti Graph Learning Centre, I am now happy to announce a revamped interactive learning platform that makes...

Graham Carr | Jan 31, 2026

Scheduled job for deleting content types and all related content

In my previous blog post which was about getting an overview of your sites content https://world.optimizely.com/blogs/Per-Nergard/Dates/2026/1/sche...

Per Nergård (MVP) | Jan 30, 2026

Working With Applications in Optimizely CMS 13

💡 Note:  The following content has been written based on Optimizely CMS 13 Preview 2 and may not accurately reflect the final release version. As...

Mark Stott | Jan 30, 2026

Experimentation at Speed Using Optimizely Opal and Web Experimentation

If you are working in experimentation, you will know that speed matters. The quicker you can go from idea to implementation, the faster you can...

Minesh Shah (Netcel) | Jan 30, 2026

How to run Optimizely CMS on VS Code Dev Containers

VS Code Dev Containers is an extension that allows you to use a Docker container as a full-featured development environment. Instead of installing...

Daniel Halse | Jan 30, 2026

A day in the life of an Optimizely OMVP: Introducing Optimizely Graph Learning Centre Beta: Master GraphQL for Content Delivery

GraphQL is transforming how developers query and deliver content from Optimizely CMS. But let's be honest—there's a learning curve. Between...

Graham Carr | Jan 30, 2026