Mari Jørgensen
Oct 7, 2014
visibility 4417
star star star star star star
(2 votes)

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
Eric Oct 7, 2014 04:32 PM

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

Mari Jørgensen
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
Petter Klang Oct 8, 2014 10:49 AM

Visitor groups perhaps? ;)

error Please login to comment.
Latest blogs
Add more scheduled job settings from the Optimizely CMS 12 admin UI -- with OptiScheduledJob.ExtraParameters

  Optimizely (EPiServer) CMS 12 ships a great scheduled-jobs framework, but it has one frustrating gap: a job has nowhere to store its own...

Binh Nguyen Thi | Jun 25, 2026

Automated Search & Navigation to Graph Migration with Claude Code

A Claude Code plugin that scans your S&N codebase, applies Graph SDK transformations, and validates the result. Install once, run one command. CMS ...

Connor Fortin | Jun 24, 2026

Migrating from Find to Graph: Lessons Learned from a Real CMS 13 Project

While migrating a search solution from Optimizely Search & Navigation (Find) to Optimizely Graph in CMS 13, I encountered several issues that were...

Binh Nguyen Thi | Jun 24, 2026

Optimizely: Upgrade Opti-ID and .NET 10 in CMS 12

Many Optimizely customers are planning their roadmap around a future migration to Optimizely CMS 13. As a result, upgrades such as Opti ID adoption...

Madhu | Jun 23, 2026 |