As all of you probably know there are two built-in ways to route to catalog items in Episerver Commerce: The hierarchical route composed of the catalog/category/entry hierarchy and the "SEO" route which uses a single url segment, which for obvious...

TL;DR: A bug in ASPNET memory monitoring prevents the cache monitoring / scavenging tread from running if the memory usage in the host at the time of application startup happens to be in a specific range in relation to the configured cache...

Update 2017-11-08 I have found the root cause for this buggy behavior, and have posted details and better workarounds in another blog post . Original post TL;DR default settings for cache memory usage don't work well with the recently launched...

TL;DR: Episerver Commerce 11.1 contains improved caching strategies for Catalog Content allowing site implementations to make better use of the available memory. Caching in the Catalog APIs Episerver Commerce uses a Content Provider to make catalo...

This is a follow up post to Planned Breaking Changes in Commerce 2017 , which promised an update on the scope of the release. We now have the scope set, and are closing on dev complete for the included features. It is very close to what we planned...