David Bowen
Mar 5, 2012
  4525
(4 votes)

EPiServer Acquires Business of e-Commerce Solution Provider, Mediachase

You may have already seen the news about our recent acquisition. This is great news for both EPiServer and Mediachase. It will allow us to advance the EPiServer Commerce product at a faster pace and quickly meet market demands.

 

EPiServer Commerce will become more aligned with the developer and user experiences of the CMS product. The user interface will become consistent with the CMS product, improving the usability. The developer API for Commerce will adopt approaches consistent with the CMS product, making development more straightforward.

 

As well as improving the product experience, more features will be added to meet the demands of a changing market. EPiServer Commerce will be an even more compelling offer for businesses around the world selling through digital channels.

 

Read what Bob (our VP of Product Management and Global Marketing) has to say about the acquisition here:

http://www.episerver.com/About-Us/Our-blogs/E-commerce/Welcome-aboard-Mediachase-team-/

 

Read more about the acquisition here:

http://www.episerver.com/About-Us/Press-Room/Press-Releases/EPiServer-Acquires-Business-of-e-Commerce-Solution-Provider-Mediachase-/

Mar 05, 2012

Comments

Frederik Vig
Frederik Vig Mar 5, 2012 03:27 PM

Could you elaborate a little on what API changes you're planning and how this will affect existing EPiServer Commerce solutions? Will we need to do a migration from existing solutions to the new once it comes out, like with EPiServer 4 to CMS 5?

Mar 7, 2012 05:06 PM

I can't elaborate on any API changes at the moment. I can say that we will minimise any breaking changes between releases and new versions will incorporate upgrade processes. So the process should be more like CMS 5 to 6.

Please login to comment.
Latest blogs
Plug-in manager is back in CMS 12

Plug-in manager is back in the UI, what is it and how can i use it?

Luc Gosso (MVP) | Oct 6, 2022 | Syndicated blog

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

Content Delivery API – The Case of the Duplicate API Refresh Token

Creating a custom refresh provider to resolve the issues with duplicate tokens in the DXC The post Content Delivery API – The Case of the Duplicate...

David Lewis | Sep 29, 2022 | Syndicated blog