K Khan
Aug 3, 2017
(1 votes)

Commerce 11 first look

  • Performance improvements for websites with a large number of promotions/campaigns while loading order totals and redemption numbers.
  • Price caching is not affected anymore by disabling CatalogCache configuration.
  • Simplified price selection if developers want to change the way prices with minimum amounts are returned without implementing the entire IPriceService interface.
  • Better loading of large of promotions/campaigns in the Marketing UI.
  • ProcessPayment Method of IPayment Plug In is returning PaymentProcessingResult with properties IsSuccessful, Message, and RedirectUrl.
  • ApplicationId has not required anymore in API. IApplicationContext will return only properties HasContentModelTypes(Indicates whether the current application has the IContent model types for catalog content available) and DisableVersionSync(Indicates whether the version sync is disabled.)
  • Merchandisers can sort items within a category in Catalog UI.
    Image sort.JPG
    When in Sort Mode,
    -Regular toolbar buttons will be disabled and cut/copy/paste option will disappear.
    -You cannot sort the View products view by column headers.
    -Sorting is for products only
    -Once you enable Sort mode, it remains enabled in other categories until you disable it.
  • As we expect, all these fields are now based on Discounted Price rather Extened Price

Related Topic:

Aug 03, 2017


K Khan
K Khan Aug 8, 2017 08:55 AM

IPriceOptimizer is a new interface that allows you to control the price optimization, this can be implemented instead of IPriceService.

namespace Mediachase.Commerce.Pricing

/// Optimizes prices on certain criterias.

public interface IPriceOptimizer
/// Optimizes a collection of prices, remove duplicated and unwanted prices.

/// The prices to optimized
/// A list of optimized prices.
IEnumerable OptimizePrices(IEnumerable prices);

public class HighestPriceOptimizer : IPriceOptimizer
public IEnumerable OptimizePrices(IEnumerable prices)
return prices.GroupBy(p => new { p.CatalogKey, p.MinQuantity, p.MarketId, p.ValidFrom, p.CustomerPricing, p.UnitPrice.Currency })
.Select(g => g.OrderByDescending(c => c.UnitPrice.Amount).First()).Select(p => new OptimizedPriceValue(p, null));

Reference: Price optimization

Please login to comment.
Latest blogs
Optimizely SendGrid SMTP host is deprecated

SendGrid is a services for sending email that is included in Optimizely DXP. Previously smtp.episerver.net was the recommended SMTP server to use,...

Tomas Hensrud Gulla | Dec 4, 2022 | Syndicated blog

Hosting Optimizely CMS 12 on Docker Engine

Since Optimizely CMS can now be deployed as a Docker container, here is a demonstration of building, running and scaling an Optimizely CMS 12 site ...

Stefan Holm Olsen | Dec 4, 2022 | Syndicated blog

How to use CacheTagHelper with content areas in Optimizely CMS 12

I might be going out on a limb here - if you have a better solution, feel very free to share it!  Upgrading your Optimizely web application from .N...

Andreas J | Dec 2, 2022

The 1001st Piece in your 1000 Piece Puzzle: .NET Default Interface Functions

I was recently working with a client who wanted a reasonably large subsystem added to Optimizely that would add automated management to their...

Greg J | Nov 28, 2022 | Syndicated blog