Commerce 15 and CMS 13: Optimizely’s Next Step Toward AI-Powered, Graph-First Commerce

Optimizely is preparing to release Commerce 15 in mid-May 2026, positioning this as a foundational shift—not just an upgrade. The direction is clear: move from fragmented tooling and isolated AI features toward a graph-first, AI-embedded commerce platform where search, content, and operations are unified.

The headline changes are not cosmetic. Visual Builder replaces legacy editing paradigms, OptiGraph becomes the default search and data layer, and Opal evolves from a set of tools into a core operational interface for commerce teams. At the same time, the upgrade path introduces real architectural considerations—especially for organizations still dependent on Find, legacy APIs, or external service layers.

For decision-makers, the implication is straightforward: Commerce 15 is where Optimizely is investing future innovation, particularly around AI agents and automation. The question is less “should we upgrade?” and more “how do we prepare to adopt a fundamentally different operating model?”

Market Context: Commerce Is Moving from Systems to Systems of Intelligence

Modern commerce platforms are no longer judged solely on catalog management, checkout performance, or integration flexibility. The competitive frontier has shifted toward:

• Speed of content and campaign execution
• Search and discovery quality (increasingly semantic and AI-driven)
• Operational efficiency for merchandisers and marketers
• Embedded intelligence across workflows

What’s often missed is that most commerce stacks still operate as systems of record, not systems of intelligence. Data exists—but it isn’t continuously activated.

Commerce 15 reflects a broader industry trend:

moving from “tools that support workflows” to “platforms that participate in workflows.”

The Optimizely Perspective: Commerce 15 as a Graph-First, AI-Embedded Platform

Commerce 15 is being framed as a modern, AI-powered, graph-first commerce platform

Three structural shifts define this positioning:

1. Graph as the foundation (not an add-on)

OptiGraph replaces Find as the default search and data layer, enabling unified indexing across CMS, commerce, DAM, and CMP.

2. AI embedded into workflows

Opal is no longer a side feature. It becomes part of day-to-day commerce operations, from product management to promotions.

3. Experience creation without developer bottlenecks

Visual Builder and integrated tooling shift control toward business users—particularly merchandisers.

This combination is what makes Commerce 15 feel less like a version upgrade and more like a platform reset.

What’s New (and Why It Matters)

Visual Builder: Merchandiser-Led Experience Creation

Visual Builder replaces the traditional on-page editor and is now embedded directly into commerce workflows.

• Build PDPs, category pages, and promotions visually
• Access all blocks, templates, and components in one interface
• Reduce dependency on developer tickets

The practical impact is significant:

• Faster campaign launches
• Lower backlog pressure on engineering
• More experimentation at the merchandising level

Or, as framed in April 28th Optimizely session Introduction to Commerce 15:

“Visual Builder gives your developers their time back.”

External Content: Breaking Down System Silos

Commerce 15 introduces stronger support for pulling data from external systems (ERP, PIM, etc.) into CMS.

• Centralized product and content management
• Reduced need for custom integration layers
• Single UI for merchandisers

This is less about convenience and more about operational coherence.
When product data, content, and customer context live together, personalization and campaign execution become materially easier.

Embedded DAM: Content Operations at Scale

The embedded DAM brings:

• AI-powered tagging
• Automated renditions
• Integrated asset workflows

For SKU-heavy organizations, this addresses a persistent bottleneck: managing media at scale without introducing content chaos.

CMP-to-CMS Publishing: Closing the Campaign Gap

Campaign workflows now connect directly to CMS:

• Content moves from planning to publishing without manual handoffs
• Templates and previews streamline execution
• Alignment between marketing and web teams improves

This is a subtle but important shift—reducing the friction between strategy and execution.

OptiGraph: The Shift from Search Engine to Experience Layer

OptiGraph replaces Find as the default search and navigation engine.

Key capabilities include:

• Unified indexing across platforms
• Semantic, intent-aware search
• Support for AI-driven context (Opal)

“Graph is now acting as the de facto experience/discovery layer and internal search provider instead of Find.” 

This matters because search is no longer just about retrieval—it’s about interpretation and relevance in context.

Opal: From Feature to Operating Model

The most strategic change in Commerce 15 is how AI is positioned.

Available now:

• Opal Chat for content and optimization
• Product catalog translations
• Promotions agent
• Data-fetching tools via Graph

Expected next:

• Product catalog management agent (bulk operations)
• Expanded Opal Chat for commerce workflows
• Google AI Search (leveraging vector-based retrieval)

The narrative is clear:

AI is moving from isolated capabilities into embedded commerce workflows.

In practice, this means:

• Merchandisers can generate and optimize content in context
• Promotions can be created via natural language
• Catalog operations can be automated at scale

Commerce 14 vs Commerce 15: A Strategic Decision Point

One of the more important signals from the announcement:

• Commerce 14 will receive limited future out-of-the-box agent support
• Commerce 15 becomes the primary platform for all future AI innovation

This creates a clear fork in the road:

• Stay on Commerce 14 → maintain stability, rely on custom solutions
• Move to Commerce 15 → access future Opal agents and platform capabilities

For most organizations, this isn’t just a technical upgrade—it’s a roadmap decision.

What Merchants and Teams Gain

For Merchandisers

• Greater autonomy (Visual Builder, Opal agents)
• Faster campaign execution
• Less reliance on dev cycles

For Marketing Teams

• Direct CMP-to-CMS workflows
• Better alignment between planning and publishing
• Improved personalization potential

For Engineering

• Reduced content-related workload
• Opportunity to focus on higher-value architecture and integrations

For Leadership

• Faster time-to-market
• Improved operational efficiency
• Platform aligned with AI-driven future capabilities

Migration Reality: What You Need to Plan For

This is where many organizations underestimate the effort.

1. Find → OptiGraph Migration

This is not optional.

• Search logic must be re-implemented
• Indexing strategies must be redesigned
• Category and content rendering may need refactoring

2. API and Architecture Changes

• Deprecated APIs require review
• Content Delivery APIs are migration-only (not future-facing)
• New development must align with a Graph-first approach

3. OptiID Becomes Mandatory

OptiID is required for:

• Content Manager
• DAM
• Opal
• Connect Platform

Organizations not already using it must plan for identity and access transitions.

4. Service API Timing

• Not available at launch (mid-May)
• Expected later in Q2 2026

If your implementation depends on Service API or PIM connectors, timing your upgrade becomes critical.

Risks and Trade-offs (Pragmatic View)

Even with a strong platform direction, there are real considerations:

• Migration complexity (especially search and indexing)
• Dependency alignment (Service API, connectors)
• Organizational readiness (AI adoption, workflow changes)
• Learning curve for new tooling (Graph, Opal, Visual Builder)

That said, these are not unusual for a major platform evolution—they’re the cost of moving to a more modern architecture.

What’s Often Missed

Most discussions will focus on features. The more interesting shift is operational:

Commerce 15 is designed to make merchandisers more self-sufficient and AI part of daily execution, not strategy decks.

That changes:

• How teams work
• How fast they move
• How value is created

Conclusion: A Platform Shift Worth Planning For Now

Commerce 15 represents a decisive move by Optimizely:

• From search engine → experience graph
• From tools → embedded intelligence
• From developer-led workflows → merchandiser-led execution

For decision-makers, the takeaway is not just “this is a new version.”

It’s this:

Commerce 15 defines where Optimizely is going—and where your commerce capabilities can go if you align early.

Next Steps for Leaders

1. Assess your current dependencies
   • Find usage
   • Service API reliance
   • Identity model (OptiID readiness)
2. Engage your implementation partner early
   • Review upgrade complexity
   • Validate timelines against Q2 dependencies
3. Explore preview packages
   • Understand Graph and Visual Builder in practice
   • Evaluate Opal use cases relevant to your business
4. Align internal teams
   • Prepare merchandisers for new workflows
   • Define governance for AI usage (human-in-the-loop, approvals, auditing)