Blog posts by sunil

Blog posts by sunil2025-12-22T15:03:20.0000000Zhttps://world.optimizely.com/blogs/sunil/ Optimizely World Handling Multiple Carts in a Single Sales Agent Session in Optimizely CommerceIn assisted-commerce, call-center, and B2B scenarios, a Sales Agent often needs to work on behalf of multiple customers within a single authenticated session. A typical requirement looks like this: <ul> <li> A Sales Agent logs in once (via OKTA) </li> <li> Uses Select Customer to choose a customer </li> <li> Manages a cart for that customer </li> <li> Switches to another customer </li> </ul> Returns to the previous customer and continues where they left off. Out of the box, Optimizely Commerce assumes one active cart per user, which makes this scenario non-trivial. This blog explains a clean, scalable pattern for supporting multiple customer carts within a single Sales Agent session in Optimizely Commerce 14. <h3>Challenges</h3> By default, a cart in Optimizely Commerce is associated with: <ul> <li> <code style="display: inline;">CustomerId</code> </li> <li> Market </li> <li> Cart name </li> </ul> In assisted-sales scenarios: <ul> <li> The logged-in user is the Sales Agent </li> <li> The actual shopper is the selected customer </li> <li> The Sales Agent must manage multiple carts, one per customer </li> </ul>   <h3>Design Principle (which I used)</h3> <blockquote> Treat the Sales Agent as an operator, not the cart owner. </blockquote> <ul> <li> Sales Agent identity remains constant </li> <li> Each customer has their own persisted cart </li> <li> Customer context switching is explicit </li> <li> Only one cart is active in the UI at a time </li> </ul>   <img src="/link/5b8a3667fea6429187b1692b3ff28568.aspx" width="1352" height="901" />   So to achive this requirement I created a Endpoint which will accepts customer Id's for Active Customer & Selected Customer, so based on the customer Id's system will switch/choose the correct cart and make that cart as primary cart.   <h3>Input Model for Customer Context Switching</h3> Customer switching is driven by a simple and explicit input model: <pre class="language-csharp"><code>public class CustomerCartDetailsInputModel { [DataMember(Name = "activeCustomerId")] public string ActiveCustomerId { get; set; } [DataMember(Name = "selectedCustomerId")] public string SelectedCustomerId { get; set; } } </code></pre> Purpose: <ul> <li> <code style="display: inline;">ActiveCustomerId</code> → customer whose cart is currently active </li> <li> <code style="display: inline;">SelectedCustomerId</code> → customer chosen via Select Customer </li> </ul> This avoids implicit session behavior and keeps cart ownership clear.   <h3>Customer Cart Switching Endpoint</h3> Whenever a Sales Agent clicks Select Customer, the frontend calls a single endpoint: <pre class="language-csharp"><code>[HttpPost] public async Task<JsonResult> Post( [FromBody] CustomerCartDetailsInputModel inputModel) { return new JsonHttpStatusResult<CartGetViewModel>( await _customerCartService.UpdateCustomerCartAsync(inputModel), SerializerSettings.JsonDefault); } </code></pre> This endpoint acts as the single source of truth for: <ul> <li> Persisting the active customer’s cart </li> <li> Loading or creating the selected customer’s cart </li> <li> Switching the active cart context </li> </ul>   <h2>High-Level Switching Flow </h2> <ol> <li> Resolve Sales Agent identity </li> <li> Load or create the Sales Agent context cart </li> <li> Persist the active customer’s cart </li> <li> Load or create the selected customer’s cart </li> <li> Copy the selected customer cart into the Sales Agent context </li> <li> Mark the selected customer as active </li> </ol>   <h3>Simplified Cart Switching Logic (Core Pattern)</h3> Below is a cleaned-up version of the core logic, focused only on multi-cart handling: <pre class="language-csharp"><code>public async Task<CartGetViewModel> UpdateCustomerCartAsync( CustomerCartDetailsInputModel inputModel) { var salesAgentId = GetSalesAgentId(); // Load or create Sales Agent context cart var agentCart = _orderRepository.LoadOrCreateCart<ICart>( salesAgentId, OrderNames.Default); // Ensure identifiers exist if (string.IsNullOrEmpty(inputModel.ActiveCustomerId)) inputModel.ActiveCustomerId = Guid.NewGuid().ToString(); if (string.IsNullOrEmpty(inputModel.SelectedCustomerId)) inputModel.SelectedCustomerId = Guid.NewGuid().ToString(); Guid.TryParse(inputModel.ActiveCustomerId, out var activeCustomerId); Guid.TryParse(inputModel.SelectedCustomerId, out var selectedCustomerId); // Persist active customer cart if (activeCustomerId != Guid.Empty) { var activeCustomerCart = _orderRepository.LoadCart<ICart>(activeCustomerId, OrderNames.Default) ?? _orderRepository.Create<ICart>(activeCustomerId, OrderNames.Default); activeCustomerCart.CopyFrom(agentCart, _orderGroupFactory); activeCustomerCart.CustomerId = activeCustomerId; _cartRepository.SaveCart(activeCustomerCart); } // Load or create selected customer cart var selectedCustomerCart = _orderRepository.LoadCart<ICart>(selectedCustomerId, OrderNames.Default) ?? _orderRepository.Create<ICart>(selectedCustomerId, OrderNames.Default); selectedCustomerCart.CustomerId = selectedCustomerId; // Switch active context agentCart.CopyFrom(selectedCustomerCart, _orderGroupFactory); agentCart.CustomerId = salesAgentId; _cartRepository.SaveCart(agentCart); // Save Cart return new CartGetViewModel { Cart = await BuildCartViewModel(agentCart), // Generate View Model of Cart CartCustomerId = selectedCustomerId.ToString() }; } </code></pre> <h3>Understanding the <code style="display: inline;">CopyFrom</code> Method</h3> <code style="display: inline;">CopyFrom</code> is a core Optimizely Commerce API used to deep-copy an entire cart structure from one order group to another. <pre class="language-csharp"><code>targetCart.CopyFrom(sourceCart, _orderGroupFactory); </code></pre> <h3>What <code style="display: inline;">CopyFrom</code> Does</h3> <ul> <li> Copies line items, shipments, payments, and addresses </li> <li> Copies custom properties </li> <li> Recreates all entities using <code style="display: inline;">IOrderGroupFactory</code> </li> </ul>   <h3>Why <code style="display: inline;">CopyFrom</code> Is Essential Here</h3> In multi-cart scenarios: <ul> <li> Customer carts must remain isolated </li> <li> The Sales Agent context cart must fully switch state </li> <li> Partial updates are unsafe </li> </ul> <code style="display: inline;">CopyFrom</code> guarantees a clean cart switch without data leakage.   By separating Sales Agent identity from customer cart ownership and using an explicit Select Customer flow, you can build a scalable assisted-commerce experience on Optimizely Commerce  without fighting the platform. Below is the output of design: <img src="/link/0f70c6f69b884ff8a771ae77652cc051.aspx" />   2025-12-22T15:03:20.0000000Z

Blog post

Implementing Custom Line Item Pricing in Optimizely Commerce 14In many enterprise commerce implementations, business users often need the flexibility to override product pricing at the cart level - especially during customer service operations, B2B negotiations, or manual order creation. Recently, I had a client requirement where the Super Admin (a special CMS/Commerce role) needed the ability to modify the price of each line item directly from the Cart page. For Example: If the default price of a product is $1000, a Super Admin should be able to change it to $900, $850, or any custom value - even if this price is not defined in the price lists. This custom pricing must also continue to work correctly with: <ul> <li> The promotions engine </li> <li> Tax calculations </li> <li> Recalculation workflows </li> <li> Order totals </li> </ul> To meet this requirement cleanly and safely, we needed a way to override PlacedPrice at the line item level in a way that stays aligned with Commerce’s pricing pipeline. This blog explains the correct, Commerce-native way to implement custom line-item pricing.   <h3>Use a Custom Price Processor</h3> To implement custom pricing properly, we must plug into Commerce’s pricing pipeline via <code style="display: inline;">IPlacedPriceProcessor</code> 1 - Store the Custom Price on the Line Item When a Super Admin updates the price on the cart page: <pre class="language-csharp"><code>lineItem.Properties["SuperAdminCustomPrice"] = customPrice.ToString(); // SuperAdminCustomPrice is meta field _cartRepository.SaveCart(cart); </code></pre> This property persists with the cart/item. 2 - Implement the Custom Price Processor <pre class="language-csharp"><code>[ServiceConfiguration(typeof(IPlacedPriceProcessor))] public class SuperAdminPriceProcessor : DefaultPlacedPriceProcessor { public override void ApplyPlacedPrice( IOrderGroup orderGroup, IOrderForm orderForm, ILineItem lineItem, IMarket market) { // Allow Commerce to set its default price base.ApplyPlacedPrice(orderGroup, orderForm, lineItem, market); // Check for Super Admin’s custom price if (!lineItem.Properties.ContainsKey("SuperAdminCustomPrice")) { return; } if (decimal.TryParse( lineItem.Properties["SuperAdminCustomPrice"].ToString(), out var customPrice)) { // Save original Commerce price for audit/rollback lineItem.Properties["OriginalPlacedPrice"] = lineItem.PlacedPrice; // Apply custom override lineItem.PlacedPrice = customPrice; } } } </code></pre>   3 - How It Looks in the UI Your “Edit Price” option on the cart page simply updates the custom property: <pre class="language-csharp"><code>if (User.IsInRole("SuperAdmin")) { lineItem.Properties["SuperAdminCustomPrice"] = newPrice; } </code></pre>   This was exactly what the client needed: A clean, production-safe way for Super Admins to override line item prices without breaking any Commerce functionality.   Thanks, Sunil Kumar  2025-11-28T15:08:51.0000000Z

Blog post

Delete Multiple Variants From Product & CatalogIn EpiServer sometimes you need to Delete Multiple Variants from a Catalog and Product. We can do that by using CatalogSystem. Here I am going to show you how we can remove the Variants from Product & Catalog. We may have two things: <ul> <li>Delete Variants by Product</li> <li>Delete all Variants under Catalog</li> </ul> To perform this we will pull all the catalog items first then we will look product nodes under it then variants and remove those. Delete Variants by Products: <pre class="language-csharp"><code>public void DeleteVariantsByProduct(ContentReference productContentReference) { var children = _contentRepository.GetChildren<CatalogContentBase>(productContentReference); foreach (var child in children) { if (child.GetType().BaseType == typeof(VariationContent)) { try { // Delete _catalogSystem.DeleteCatalogEntry(child.ContentLink.ID, true); } catch (Exception exception) { // Log Exception } } } }</code></pre> I created a Variant Service Class where you can find the two Methods for Delete Variants by Product and Delete all Variants under Catalog. <pre class="language-csharp"><code>using EPiServer; using EPiServer.Commerce.Catalog.ContentTypes; using EPiServer.Core; using Mediachase.Commerce.Catalog; using System; namespace DemoCommerce { public class VariantService { private readonly ICatalogSystem _catalogSystem; private readonly IContentRepository _contentRepository; private readonly ReferenceConverter _referenceConverter; public VariantService( ICatalogSystem catalogSystem, IContentRepository contentRepository, ReferenceConverter referenceConverter) { _catalogSystem = catalogSystem ?? throw new ArgumentNullException(nameof(catalogSystem)); _contentRepository = contentRepository ?? throw new ArgumentNullException(nameof(contentRepository)); _referenceConverter = referenceConverter ?? throw new ArgumentNullException(nameof(referenceConverter)); } public void DeleteVariantsByProduct(ContentReference productContentReference) { var children = _contentRepository.GetChildren<CatalogContentBase>(productContentReference); foreach (var child in children) { if (child.GetType().BaseType == typeof(VariationContent)) { try { // Delete _catalogSystem.DeleteCatalogEntry(child.ContentLink.ID, true); } catch (Exception exception) { // Log Exception } } } } public void DeleteAllVariants() { // Get Catalog Node Items var catalogItems = _contentRepository.GetChildren<CatalogContent>(_referenceConverter.GetRootLink()); foreach (var catalogItem in catalogItems) { //Loop through all catalog items var nodes = _contentRepository.GetChildren<CatalogContentBase>(catalogItem.ContentLink); foreach (var node in nodes) { DeleteCatalogEntries(node); } } } private void DeleteCatalogEntries(CatalogContentBase node) { var children = _contentRepository.GetChildren<CatalogContentBase>(node.ContentLink); foreach (var child in children) { switch (child.ContentType) { case CatalogContentType.CatalogNode: DeleteCatalogEntries(child); break; case CatalogContentType.CatalogEntry: if (child.GetType().BaseType == typeof(VariationContent)) { try { // Delete _catalogSystem.DeleteCatalogEntry(child.ContentLink.ID, true); } catch (Exception exception) { // Log Exception } } break; } } } } } </code></pre> Thanks & Regards Sunil2021-02-28T16:57:08.0000000Z

Blog post