Take the community feedback survey now.

Surjit Bharath
Aug 4, 2022
  2440
(2 votes)

Merging carts when customer logs in on Commerce 14

In Commerce 13 and below, we had out of the box default behaviour that when a customer logs in, their cart, wishlist and any orders they made during their anonymous state will get merged into their customer contact associated with their principal object. This is done via a httpmodule where an authentication event would be raised and the IProfileMigrator would get called executing the said actions.

Unfortunately in the current version of Commerce 14 (v14.5.0 at the time of this post) does not include the middleware to hook up the IProfileMigrator and do this automatically as it did with its previous versions.

For the example middleware code please go here: https://www.hiddenfoundry.com/thoughts/merging-carts-when-logging-in-from-an-anonymous-state-in-commerce-14/

Aug 04, 2022

Comments

Johannes Mols
Johannes Mols Jun 6, 2023 09:32 AM

Hi, thank you for the blog post, it helped a lot. The code snippet isn't fully working though regarding the service locator and getting the anonymous ID as a feature. Not sure if that's due to the updated in Commerce (running v14.11.0) or because it's incomplete.

For me, the anonymous ID is also removed as soon as the user is authenticated. A workaround I found is to get the ID from the cookie that the anonymous ID middleware sets. This isn't deleted upon logging in.

Here is the middleware that is working for me:

public class AnonymousCartMigrationMiddleware
{
	private readonly RequestDelegate _next;
	private readonly IOrderRepository _orderRepository;
	private readonly ICurrentMarket _currentMarket;
	private readonly IProfileMigrator _profileMigrator;

	public AnonymousCartMigrationMiddleware(
		RequestDelegate next,
		IOrderRepository orderRepository,
		ICurrentMarket currentMarket,
		IProfileMigrator profileMigrator)
	{
		_next = next;
		_orderRepository = orderRepository;
		_currentMarket = currentMarket;
		_profileMigrator = profileMigrator;
	}

	public async Task Invoke(HttpContext context)
	{
		if (context.User.Identity is { IsAuthenticated: true } && !string.IsNullOrEmpty(context.User.Identity?.Name))
		{
			var justLoggedIn = CustomContext.Current.IsFirstLoadAfterLogin;

			// Not using "context.Request.HttpContext.Features.Get<IAnonymousIdFeature>()?.AnonymousId" because it is removed at this point. The cookie, however, is not deleted (see AnonymousIdMiddleware).
			context.Request.Cookies.TryGetValue("EPiServer_Commerce_AnonymousId", out var anonymousId);

			if (justLoggedIn && !string.IsNullOrWhiteSpace(anonymousId) && Guid.TryParse(anonymousId, out var anonymousGuid))
			{
				var cart = _orderRepository.LoadCart<ICart>(anonymousGuid, "Default", _currentMarket);
				if (cart != null && cart.GetAllLineItems().Any())
				{
					_profileMigrator.MigrateCarts(anonymousGuid);
					_profileMigrator.MigrateOrders(anonymousGuid);
					_profileMigrator.MigrateWishlists(anonymousGuid);
				}

				// Add it back in so that the application can process it as normal.
				context.Session.SetString(SessionKeys.JustLoggedIn, "true");
			}
		}

		await _next(context);
	}
}

public static class AnonymousCartMigrationMiddlewareExtensions
{
	public static IApplicationBuilder UseAnonymousCartMigration(this IApplicationBuilder app)
	{
		return app.UseMiddleware<AnonymousCartMigrationMiddleware>();
	}
}

The CustomContext is an implementation that handles session info. When we process a login, we store a value in the user session that flags it as the first load after log-in. This is used elsewhere in the application. Accessing this property removes the session key, which is why I add it back in after running the migration. This prevents multiple requests from triggering the migration simulatenously.

Hope this helps someone.

Surjit Bharath
Surjit Bharath Jun 6, 2023 04:14 PM

Thanks for the comment. Sorry the initial attempt didn't work. I've just tried it on the latest version of Commerce 14.12 on a fresh Foundation instance and it was working just fine.

Just make sure you call your middleware after:

app.AnonymousId();

app.UseAuthentication();

app.UseAuthorization();

Johannes Mols
Johannes Mols Jun 9, 2023 06:18 AM

Hi, yes it seems I had the UseAnonymousId middleware after the two. Moving it to the front makes it work :) Maybe you'll want to add that line to your blog post in the last code snippet.

The syntax to get the Id seems to also have changed slightly from your snippet. This works: 

context.Request.HttpContext.Features.Get<IAnonymousIdFeature>()?.AnonymousId

Praful Jangid
Praful Jangid Oct 3, 2024 03:42 PM

Surjit Bharath,

You deserve 5 star for this post. Thanks for saving our life.

Please login to comment.
Latest blogs
Trigger DXP Warmup Locally to Catch Bugs & Performance Issues Early

Here’s our documentation on warmup in DXP : 🔗 https://docs.developers.optimizely.com/digital-experience-platform/docs/warming-up-sites What I didn...

dada | Sep 29, 2025

Creating Opal Tools for Stott Robots Handler

This summer, the Netcel Development team and I took part in Optimizely’s Opal Hackathon. The challenge from Optimizely was to extend Opal’s abiliti...

Mark Stott | Sep 28, 2025

Integrating Commerce Search v3 (Vertex AI) with Optimizely Configured Commerce

Introduction This blog provides a technical guide for integrating Commerce Search v3, which leverages Google Cloud's Vertex AI Search, into an...

Vaibhav | Sep 27, 2025

A day in the life of an Optimizely MVP - Opti Graph Extensions add-on v1.0.0 released

I am pleased to announce that the official v1.0.0 of the Opti Graph Extensions add-on has now been released and is generally available. Refer to my...

Graham Carr | Sep 25, 2025