K Khan
Aug 3, 2017
  2829
(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
    IOrderGroupCalculator.GetSubTotal
    DefaultOrderGroupCalculator.GetSubTotal
    DefaultOrderGroupCalculator.CalculateSubTotal
    IOrderFormCalculator.GetSubTotal
    DefaultOrderFormCalculator.GetSubTotal
    DefaultOrderFormCalculator.CalculateSubTotal
    IShippingCalculator.GetShippingItemsTotal
    DefaultShippingCalculator.GetShippingItemsTotal
    DefaultShippingCalculator.CalculateShippingItemsTotal

Related Topic:

Aug 03, 2017

Comments

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
Announcing new library: SettingsManager

When you run .net app, there have been a few ways to store settings. Those can be set via appSettings.json, or via Azure Portal AppService...

Quan Mai | Apr 30, 2026

From Prompting to Production: Optimizely Opal University Cohort and the Future of Agentic MarTech

Most organizations today are still playing with AI. They experiment with prompts, test ideas in isolated chats, and occasionally automate a task or...

Augusto Davalos | Apr 28, 2026

Six Compelling Reasons for Upgrading to CMS 13

Most software updates ask you to keep up. Optimizely CMS 13 asks something different — it asks whether your digital strategy is built for a world...

Muhammad Talha | Apr 28, 2026

Optimizely CMS 13 breaking changes: GetContentTypePropertyDisplayName

When upgrading from CMS 12 to 13, resolving property display names may not work as before. Here’s what changed.

Tomas Hensrud Gulla | Apr 27, 2026 |