On August 27, 2026, Optimizely released version 5.2.2608.613+sts, its latest short-term support release for Configured Commerce. This release adds WebMCP storefront tools that give in-browser AI agents structured access to cart and catalog operations, product exclusions for promotions, an Opal agent that walks administrators through building restriction groups, expanded VMI label printing, and a deep set of stability and performance fixes. It also introduces a breaking change for teams with custom implementations of the ICustomerOrderUtilities interface.
Here is my read on what matters, and where you should pay attention before you plan your next deployment.
New AI and Promotion Capabilities
The headline addition is WebMCP support for Spire. WebMCP is a protocol that lets in-browser AI agents, such as Gemini in Chrome, call structured tools exposed by a web application. Configured Commerce now exposes three of them: reading cart and session context, searching products, and adding, updating, or removing cart lines. The agent operates against your existing pricing, promotions, and B2B entitlements, so a buyer can describe a routine multi-line reorder in plain language and have the cart built correctly. For distributors whose customers place the same forty-line order every month, that is a real reduction in friction. This is opt-in infrastructure rather than a behavior change, but you should confirm it fits your client's security posture before enabling it.
The second addition is smaller and will get used more often. Promotion rules and discount results now accept an "Exclude Products" list, so you can carve MAP-restricted items, low-margin SKUs, or newly released products out of a broad promotion. Anyone who has built custom pipeline logic to protect a handful of SKUs from a site-wide sale can retire that code.
What Changed for Configured Commerce Administrators?
A new Opal agent called the Restriction Group Creator guides administrators through defining customer and product restriction groups conversationally, rather than through direct API requests. Restriction groups are one of the areas where clients most often need hand-holding after go-live, so this is worth adding to your training and handoff materials.
Printed VMI labels can now carry Minimum Quantity, Maximum Quantity, and Bin Location, which gives warehouse staff the context to make replenishment decisions at the shelf. On the support side, the storefront error modal now surfaces a timestamp along with the Cloudflare Ray ID and Datadog Trace ID, so a user reporting an error can hand you something that correlates directly to a request in your monitoring stack. Order history records are also now properly read-only in the Admin Console on .NET Core sites, and the email and username of externally managed users such as Opti ID accounts can no longer be edited.
One configuration change deserves attention before you upgrade. The Spreedly "Environment Key" and "Environment Name" settings moved from per-website to global. If you run a multi-site implementation on Spreedly, verify those values post-migration.
What Performance Improvements Are Included?
Three stability items lead the release, and all three target problems that only appear on mature, high-volume sites. The nightly maintenance job now clears integration logs, abandoned carts, email messages, and quotes using set-based SQL deletes, which resolves the out-of-memory failures that large sites hit when working through a big backlog. Request timeout middleware now cancels long-running requests when an external service stops responding, which matters for any implementation with real-time pricing or ERP calls that can hang and exhaust threads. Spire also aborts server-side rendering when the requesting client disconnects, so peak-traffic capacity is not spent rendering pages for visitors who already left.
For development teams, OpenAPI document generation and Swagger UI are now available for the .NET Core Admin, Storefront, and Integration APIs in non-production environments, which makes exploring endpoints considerably faster than reading documentation for every call. The DAM Asset URL Migration job is also new, rewriting stored UserFiles image URLs to their Optimizely DAM equivalents after a migration.
The hotfix list is long and worth reading in full. The items I would flag are Opti ID users failing to sign in when another account shared their email, product detail pages returning Page Not Found instead of redirecting to Sign In when Sign In Required was enabled, Rebuild Index failures leaving Commerce Search v2 and v3 indexes incomplete, and concurrent integration jobs getting stuck In Progress and dropping off their recurring schedules. Each of those generates a support ticket within a week of go-live.
How I Would Approach This Upgrade
Start with the breaking change, because it will stop your build. Two methods, GetOrderSubTotal and GetOrderSubtotalWithOrderDiscounts, were added to the ICustomerOrderUtilities interface. If you carry a custom implementation, it will not compile until you add them. The fix is mechanical, but it needs to happen before anything else.
From there, prioritize a regression pass over payments if you run Spreedly, given the global settings change, and over your sign-in and catalog restriction flows, given the hotfixes in that area. Validate any custom promotion configurations against the new exclusion logic. I would also note that settings encryption through IsEncrypted on SettingsFieldAttribute is now deprecated in favor of the Vault, so if you have custom settings using it, start planning that migration rather than waiting for it to become urgent.
WebMCP and the Restriction Group Creator both deserve a deliberate conversation with your client rather than a quiet default. Neither requires immediate action, but both change what the platform is capable of, and that is worth a decision.
See the full patch notes here: August 2026 release notes.