Working with the EPiServer 7.5 Commerce API

With the introduction of EPiServer 7.5, EPiServer Commerce provides a content provider that can serve any catalog content as IContent. This means that it is possible to work with catalog content using the same techniques as working with CMS content.

Read moreand view code samples by visiting the blog post on our company blog:
http://geta.no/blogg/working-with-the-episerver-7.5-commerce-api/

Oct 07, 2014

Comments

Eric Oct 7, 2014 04:32 PM

Nice, but could you please turn of the popup when refering from World ;)

Mari Jørgensen Oct 7, 2014 05:33 PM

Good point, Eric. I will see if it´s an easy fix for that.

Petter Klang Oct 8, 2014 10:49 AM

Visitor groups perhaps? ;)

error Please login to comment.

Surviving a Dirty Feed. Part 3: Error Handling and Event Batching

Committing a 250,000-row Optimizely catalog import row by row, returning a per-row failure report, and coalescing catalog events into one per batch.

Stanisław Szołkowski | Oct 16, 2026 |

Building UI Extensions for Optimizely SaaS CMS

Introduction Developers have been extending the functionality of Optimizely PaaS CMS for years using addons built in C# and deployed as NuGet...

Mark Stott | Oct 15, 2026

Cheapskate AI Translator: Because Translation Should Not Require a Second Mortgage

There is a particular kind of software project that begins with a detailed architecture document, a product roadmap, and a carefully assembled...

Linh Doan Cuu | Oct 15, 2026

Computed Fields in CMS 13 Content Contracts with Optimizely Graph

Content Contracts in Optimizely CMS 13 allow different content types to share a common structure when querying Optimizely Graph. But what if the...

Mardy | Oct 14, 2026

See all blogs