August 2026 release
8 min
Release: 5.2.2608.613+sts
The following is a list of the release's bug fixes and enhancements. Some bug fixes may address existing support articles. A comprehensive list is at the bottom of this page.
The August 2026 release is now available for developers to download and work with locally or to request deployments.
Release highlights
Stability & Performance
- Nightly Maintenance Reliability – Large sites with high transaction volume can now run nightly cleanup jobs without hitting memory limits. Integration logs, abandoned carts, email messages, and quotes are cleared efficiently using set-based SQL deletes that scale with your data.
- Request Timeout Protection – Long-running requests caused by slow or unresponsive external services are now automatically cancelled, freeing server resources before they compound into broader performance degradation.
- Smarter Server-Side Rendering – Spire no longer wastes server resources completing renders for users who have already navigated away or disconnected. This reduces unnecessary load during high-traffic periods and improves overall responsiveness.
New Features
- WebMCP storefront tools – Make your Spire storefront agent-ready and save buyers from clicking through complex B2B catalogs line-by-line. Configured Commerce now supports WebMCP for Spire, giving AI shopping agents direct, structured access to three capabilities: reading cart and session context, searching products, and adding, updating, or removing cart lines. Agents like Gemini in Chrome can build routine, multi-line orders in a single sentence on a shopper's behalf, using your existing pricing, promotions, and B2B entitlements - cutting order time to seconds and making you the easiest vendor to buy from.
- Exclude products from promotions – Protect margin on the products you can't afford to discount. Promotion rules and discount results now accept an exclusion list, so you can run aggressive site-wide offers while carving out low-margin SKUs, MAP-restricted items, or new releases – no more choosing between a broad promotion and a profitable one. See Promotion rule type descriptionsPromotion rule type descriptions and Promotion result type descriptionsPromotion result type descriptions.
- Restriction Group Creator – Set up customer and product restrictions in minutes, not hours. An Opal agent walks admins through creating a restriction group in plain conversation, removing the configuration expertise that used to gate this work and freeing your team from ticket-driven setup requests. See Restriction Group Creation agentRestriction Group Creation agent.
- VMI label print options – Give stockroom staff everything they need on the label itself. Printed labels can now carry minimum and maximum quantities plus bin location, so replenishment decisions happen at the shelf-fewer stockouts, less overstock, and faster put-away without a lookup in the system. See Set up and manage productsSet up and manage products.
Breaking changes
Low risk
- Added GetOrderSubTotal(CustomerOrder, List<Guid>) and GetOrderSubtotalWithOrderDiscounts(CustomerOrder, List<Guid>) methods to the Insite.Core.Plugins.EntityUtilities.ICustomerOrderUtilities interface. Custom implementations of this interface must be updated to include these new methods.
Enhancements
- Added a WebMCP layer to the Spire storefront that exposes commerce capabilities to in-browser AI agents as structured, callable tools, letting an agent read session and cart context, search products with account-specific pricing, and add, update, or remove cart lines through the storefront's existing business logic.
- Added an optional Exclude Products field to qualifying promotion rule and discount result types, letting administrators keep specific products from counting toward qualification or receiving a discount while the rest of the order stays eligible; leaving the field empty preserves existing behavior. See Promotion rule type descriptionsPromotion rule type descriptions and Promotion result type descriptionsPromotion result type descriptions.
- Added OpenAPI document generation and a Swagger UI to the .NET Core Admin, Storefront, and Integration APIs, giving developers interactive, up-to-date API references when working in non-production environments. See Get started with Configured Commerce REST APIsGet started with Configured Commerce REST APIs.
- Released the Restriction Group Creator, an Opal agent that creates product restriction groups in Configured Commerce through a step-by-step wizard. This helps you define customer and product restrictions accurately without hand-building API requests. See Restriction Group Creation agentRestriction Group Creation agent.
- Added optional Minimum Quantity, Maximum Quantity, and Bin Location fields to the Vendor Managed Inventory (VMI) label print options, so users can include reorder thresholds and bin locations on printed product labels.
- Added a timestamp with a copy link to the storefront unhandled-error popup, so shoppers can quickly share the exact time an error occurred with site support for faster troubleshooting.
- Added a Reference ID block to the storefront error modal that shows the Cloudflare Ray ID and Datadog Trace ID for a failed request, so shoppers can share these identifiers with support and speed up error investigation.
- Added an integration job that rewrites stored UserFiles image URLs to their Optimizely Digital Asset Management (DAM) equivalents after assets are migrated, so sites using DAM as their storage provider serve media from DAM without manual database edits.
- Updated .NET Core application logging to honor the developer setting that controls whether logs are written to the database, which lets administrators disable database log storage and rely on other log sinks.
- Updated the Search service admin interface to the latest Optimizely branding, giving administrators a look and feel consistent with the rest of the platform.
- Changed the Spreedly Environment Key and Environment Name payment settings to be global rather than per-website, preventing checkout failures caused by mismatched environment values across websites on the same commerce instance. Existing website-specific values can no longer be added or edited in the Admin Console and must be changed with a custom SQL script. See Configure Payment Service.
- Deprecated the IsEncrypted option on SettingsFieldAttribute; it remains available for backward compatibility, but Optimizely code now stores these settings in the Vault, and custom or partner code should migrate to an alternative. See Create custom settings.
- Payment gateway integrations can now retain a gateway-specific token captured during the authorization or sale request instead of having it overwritten when the payment profile is stored afterward, by setting the new SkipStorePaymentProfile flag. See Override payment gateway settings.
- Improved security.
Bug fixes
- Fixed blank pages in the ElasticSearch application logs viewer in the Admin Console when navigating to the last pages of results.
- Fixed the issue where the email address and username of an externally managed user (such as an Opti ID single sign-on user) could be edited from Console Users in the Admin Console; these fields are now read-only and return The email and username of external users cannot be changed.
- Fixed the issue where the Is Translatable, Is Required, Can View, and Can Edit values reset to their defaults after saving a new custom property in the Admin Console Application Dictionary.
- Fixed the issue where the administration console failed to load after upgrading a .NET Core (Linux) instance.
- Fixed the issue where the product list in the Assign Products modal lost its ERP Number sort order when the modal was reopened.
- Fixed the debug tools icon intermittently disappearing from the Admin Console when signing in through single sign-on (SSO), which required a page refresh to restore it.
- Fixed the issue where the start and end date fields were read-only when creating or editing a merchandising control, preventing users from opening the calendar to add or change dates.
- Fixed the issue where editing a serving control in Commerce Search v3 did not populate the previously saved control details.
- Fixed the issue where the Id column could not be added to a list's displayed columns in the admin console; it was not saved to the Display group and reverted to Available.
- Fixed the issue where editing a serving configuration in Commerce Search v3 did not populate the previously saved configuration details.
- *Fixed the issue where Opti ID users could not sign in to the Admin Console when another account shared their email.
- *Fixed the issue where the administration console failed to load after upgrading to a .NET Core (Linux) instance.
- *Fixed the issue where product detail pages returned Page Not Found instead of redirecting to the Sign In page when Sign In Required was enabled.
- *Fixed the issue where a Spire production build failed when a dependency package was missing its license file.
- *Fixed the issue where uploading a larger image (about 30 MB or more) to the Media Library failed on .NET Core storefronts.
- *Fixed the issue where asynchronous widgets did not receive their default field values on cloud-hosted sites.
- *Fixed the issue where Rebuild Index could fail to complete on Commerce Search v2 and v3, leaving the product, category, or content index incomplete.
- *Fixed the issue where a search index rebuild failed during content indexing on .NET Framework 4.8 sites.
- *Fixed the issue where category navigation links and menu items intermittently displayed Cache_Item_Empty instead of the category name.
- *Fixed the issue where a real-time Order Submit job stayed In Progress indefinitely when the integration connector threw an exception. The job now ends with a Failure status.
- *Fixed the issue where Spire logs were flooded with Failed to load font css errors for Google Fonts requests that actually succeeded.
- *Fixed the issue where buttons in the Search micro-frontend (MFE) did not match the updated Optimizely branding.
- *Fixed the issue where custom front-end packages did not work in local Spire development after the move to pnpm.
- *Fixed the issue where Spire server-side rendering sent duplicate request headers differing only in case, breaking requests behind Cloudflare.
- *Fixed the issue where completing PunchOut checkout on .NET Core storefronts returned JSON instead of redirecting to the procurement site.
- *Fixed the issue where server-side rendering logged a spurious setSessionCookies called with empty cookies warning on every cookie-less request.
- *Fixed the issue where menus, filters, radio buttons, and version history still used the old styling in the Spire CMS.
- *Fixed the issue where concurrent integration jobs failed intermittently, stayed stuck InProgress, and dropped off their recurring schedule.
- *Fixed the issue where Asynchronous JavaScript and XML (AJAX) requests to a redirected URL returned a 500 error.
- *Fixed the issue where the DeactivateInactiveUsers job timed out on sites with large order volumes.
- *Fixed the issue where the storefront Create User modal ignored Translation Dictionary entries for role names.
- *Fixed an issue where bearer-token-only sessions (such as from a mobile app) appeared signed out and showed Sign in for pricing after the browser cookie was cleared.
- *Fixed an issue where a malformed or empty PayFlow Pro (TokenEx) gateway response was recorded as a successful transaction even though the payment failed.
- *Fixed an issue where client-disconnect exceptions were logged as Error on the Admin Console's Application Logs page; these now log as Debug so they no longer appear during normal operation.
- *Fixed an issue where the application displayed a generic error page instead of the custom error page when handling certain exceptions.