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
Display Child Pages in Content Delivery API Response

The below example will implement an instance of IContentConverterProvider to customise the serialisation of PageData and output child pages in the...

Minesh Shah (Netcel) | Oct 4, 2022

Bring the Report Center back in Optimizely CMS 12

The Report Center has been a part of Optimizely CMS since its first debut in version 5R2 in 2008, but in CMS 12, it's removed! Don't despair! Make...

Tomas Hensrud Gulla | Oct 4, 2022 | Syndicated blog

Customizing Property Lists in Optimizely CMS

Generic property lists is a cool editorial feature that has gained a lot of popularity - in spite of still being unsupported (officially). But if y...

Allan Thraen | Oct 2, 2022 | Syndicated blog

Optimizely names Luminary Senior Developer, Ynze Nunnink, OMVP

Luminary Senior Developer and Optimizely Lead, Ynze Nunnink has secured the coveted position of Optimizely MVP. Earning a Platinum badge for his...

Ynze | Oct 2, 2022 | Syndicated blog