Optimizely CMS: retail publishing in 2026
Compare Optimizely CMS editions for retail content. Keep approved product guidance separate from experiments, commerce and partner services.
- Published
- Last updated
Optimizely CMS suits retailers that need managed publishing workflows and a development team to connect content with their storefront. Start with the CMS edition and version. An older Episerver installation, CMS 12, CMS 13 and CMS (SaaS) carry different implementation responsibilities.
A product guide can explain how to choose a jacket while commerce supplies its price and available sizes. Keeping those responsibilities separate also protects the approved answer when a campaign changes the page’s presentation.
Identify the CMS product and version
Identify whether the proposal covers the versioned .NET CMS or the separately documented CMS (SaaS). The name Optimizely alone doesn’t identify the software you’ll operate.
Episerver rebranded as Optimizely in 2021. That explains historical Episerver CMS references, but the name doesn’t establish an installation’s version or upgrade path. Record the installed packages and extensions before treating an old implementation proposal as a current specification. The company’s rebrand announcement establishes the naming relationship.
CMS 12 has its own development and publishing documentation. Existing implementations can have server-rendered pages or a separately built front end using the Content Delivery API. That API needs installation and configuration within the solution. Its presence in the documentation doesn’t mean every CMS 12 site already exposes the same content.
CMS 13 changes the technical decision. It runs on .NET 10 and centres content delivery on Optimizely Graph. Traditional ASP.NET MVC rendering remains supported, so a move to CMS 13 doesn’t automatically require replacing every server-rendered page. Its system requirements define the runtime and database requirements.
The CMS 13 developer overview identifies Opti ID and Graph as platform components. It also states that Search & Navigation implementations are no longer supported. An estate using that search product needs a replacement search implementation when moving to CMS 13. Graph or a third-party provider can supply site search.
CMS (SaaS) is a headless service with Visual Builder for authoring, a configuration API and Graph for retrieving content. A separate front end renders the customer experience. Optimizely manages platform releases through deployment rings. Your team still owns the front-end implementation and its connections, as the SaaS overview explains.
Treat CMS support, runtime support and extension compatibility as separate entries in an upgrade scope. A supported runtime doesn’t establish that an old payment connector or custom editor extension works with the target CMS.
Separate publishing from commerce and experiments
Give each retail fact an owning system, then define how the page obtains it. CMS content, commerce data and experiment configuration can appear together without becoming one editable record.
| Retail item | Owning responsibility | What the page consumes |
|---|---|---|
| Jacket buying guide | Content team’s approved CMS entry | Advice, images and links to relevant products |
| Jacket catalogue record | Commerce or product information system | Product identifier, attributes and sellable options |
| Price and stock | Commerce and inventory connections | The current values for the customer’s market |
| Layout experiment | Experiment configuration and measured variant | Which approved presentation the customer sees |
| Returns policy | The retailer’s approved policy record | The applicable rules and their exceptions |
Optimizely’s CMS 12 product guide distinguishes CMS publishing from Commerce Connect’s products, discounts and orders. A CMS subscription proposal must identify the commerce products and connections it includes. The same applies to experimentation services and their commercial terms.
Choose delivery around the actual storefront. CMS 12 documents on-page editing with client-side rendering, including configuration for separate edit and delivery hosts. CMS (SaaS) documents application-level preview URLs and tokens. Preview is a connection your implementation must support, including the right content version and language.
CMS 13 includes content variations with separate publication histories. The ability to publish a variation is different from defining an experiment’s audience, measurement and stopping rules. Assign those decisions to the experiment owner. Keep the approved policy text shared wherever a layout test uses it.
Preserve the approved answer through changes
Publish policy changes through approval, then update every customer-answer source that consumes the policy. A new page in the CMS doesn’t by itself prove that a cached storefront or connected answer service has received it.
Consider a fictional retailer replacing its change-of-mind returns instructions. The policy owner approves the wording and exceptions. An editor changes the policy entry while the previously published version remains the customer reference. In CMS 12, a configured approval sequence requires review before publication. The sequence and permissions must cover the policy and any shared assets involved.
After approval, the publisher releases the new policy. The integration owner checks the published response consumed by the storefront, then refreshes any cached or indexed copy used for customer answers. Compare the answer with the approved entry, including exceptions and the policy link. Keep draft and preview content outside the customer-answer source.
Suppose a simultaneous experiment moves the returns explanation above the product recommendations. Both layouts must show the same approved rules. CMS 13’s content variation documentation explains that Graph queries can select variations. An answer-source query therefore needs an explicit policy about which variation it retrieves. A presentation test must not accidentally make a campaign variation the store’s general returns authority.
When withdrawing a buying guide, check more than its navigation entry. Remove it from the answer source and search index, then check direct requests and links from category pages. Where a replacement exists, update those references. A retained copy must not continue recommending a discontinued policy or product.
Keep a small acceptance record for each release. It needs the approved content version, the published page and the version received by the answer service. Include the result of a representative policy question. That record gives the content team a way to distinguish a publishing mistake from a stale downstream copy.
Choose implementation and maintenance responsibilities
Choose an implementation partner by the edition and work it must maintain. A team experienced with an older Episerver CMS estate needs relevant CMS 13 or SaaS delivery experience for the proposed change.
Start with Optimizely’s official partner discovery page. Assess a partner against the required migration and integrations, with named responsibility for ongoing updates. Directory presence identifies a supplier to assess. It doesn’t define the scope of that supplier’s maintenance agreement.
Separate the CMS supplier’s service from the partner’s work in the proposal. The partner can build content types, connect catalogue data and implement preview. It can also configure approval workflows and maintain the storefront. Those implementation services need their own deliverables, support hours and handover documentation.
Optimizely’s plans page describes individually packaged plans. Budget for the identified CMS package alongside implementation, connected services and ongoing operation. A versioned CMS project needs ownership of package upgrades and compatibility checks. A SaaS project still needs front-end maintenance and release acceptance as the platform changes.
Before selecting a proposal, name the person who can repair a failed policy publication across the whole chain. The agreement must cover the CMS release, content delivery and the customer-answer source, with a recovery procedure for each. That responsibility matters as much as the initial page build when customers rely on the published answer.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.