Area: Episerver Commerce
Applies to versions: Commerce 12.1 and higher

Customer Service Representative UI - Beta

A new user interface (UI) is being developed to manage orders as a replacement for Commerce Manager. While the new UI is not yet fully featured, you can use it "as is" now. To do so, follow these steps.

  1. The user must have access to beta features. Read this for more information.
  2. The user must be part of the CommerceAdmins or CustomerServiceRepresentatives group. The former group grants access to all parts of the Commerce UI, while the latter group grants access to just the Order Management UI.
  3. You must turn on the CustomerServiceUI feature switch. Read this for more information.
  4. Verify that the NuGet package EPiServer.Commerce.UI.CustomerService is installed. Depending on your site (upgraded from earlier version, new installation, etc.), the package might be installed, or an explicit installation may be required.

Once all steps are completed, a new menu item, Order management, appears under Commerce on the global menu.


Use that menu item to access the Order Management UI.
* Since this feature is still in beta, the screen is subject to change.
* The CSR UI, currently in BETA, does not work properly with the Service API. This will be fixed in a future Commerce version.

Extending the search result display

When adding a new line item to a cart or an order, a user finds the correct one by searching for it. If a product has many variants, Epi helps the user select the correct one by displaying variant-specific information (e.g., size or color) for each search hit. However, those properties differ from site to site. Episerver does a "best guess" by inspecting content types.

If you want more control over what is shown, use the EPiServer.Commerce.Catalog.IEntryInformation interface. By implementing IEntryInformation, and replacing our default implementation, you can customize which properties are displayed. The interface has just one method, which returns a dictionary. That dictionary should contain the names of properties to show, as well as a string representation of their value, suitable to be shown to the user.

Fix for "Customer is undefined" error (New in Commerce 13.9.0)

If a customer service representative (CSR)  opens this UI screen in two separate tabs, then logs out of the first tab and opens any cart or order on the second tab, the following error appears.


To replace this error message with a user-friendly one ("Your session has expired"), add the following code to the Global.asax.cs file:

protected void Application_EndRequest()
    if (Context.Response.StatusCode == 302
        && (Context.User == null || !Context.User.Identity.IsAuthenticated)
        && Context.Request.Path.ToString().ToLower().Contains("/api/"))
        Context.Response.StatusCode = 401;
Do you find this information helpful? Please log in to provide feedback.

Last updated: Oct 22, 2018