Catalog Search now supports search rules in rule groups so merchandisers can boost, bury, pin, hide, rewrite, or filter results when a shopper query or browse listing matches a trigger.

What's New?

• Search rule groups - Named containers for query-time merchandising rules
• Search rules - Exact, contains, and browse triggers with boost/bury, pin, hide, query rewrite, and rule filter actions
• Profile rule_groups - Attach ordered rule group IDs to a search profile to activate the rules engine
• Ordering controls - execution_order within a group and stop_after_match across the profile pipeline
• matched_rules on search results - See which rule and rule group IDs matched a full search (not autocomplete)

What's Changed?

• Always-on profile boosts remain available for every search on a profile; search rules apply only when a trigger matches
• Autocomplete does not evaluate search rules

For details see:

• Using Search Rules
• Setting Up Catalog Search
• Search Rule Groups API
• Search Rules API

Use Indexed Fields to list every field in the search index — including numeric, boolean, and date fields — with flags for how each field can be used.

What's New?

• GET /pcm/catalogs/search/indexed-fields - Returns all exposed indexed fields of every type
• searchable and filterable flags - See whether a field can be used as a full-text query field and in filter expressions
• Guide coverage - List Indexed Fields in Setting Up Catalog Search, with links from filtering, faceting, and sorting guides

What's Changed?

• GET /pcm/catalogs/searchable-fields is deprecated - Prefer Indexed Fields. Searchable Fields returns only text query fields and does not cover fields needed for filtering and sorting
• Searchable Fields remains available for existing integrations; migrate to Indexed Fields for complete schema discovery

For details see:

• List Indexed Fields
• Indexed Fields API
• Setting Up Catalog Search

To make price books and product configurations consistent with recent updates to product pages, we have released a redesigned user interface for these areas in Commerce Manager.

What's New?

• New price book UI - The price book list design has been updated. Within the price books editor, the pricing table has been refreshed, and products are added to it from a searchable slide-in sheet. Currencies can be shown and hidden with the column selector on the product list. The price modifiers UI has also been updated, and can be accessed via a new tab within the editor.
• Templates & attributes - Templates and attributes are now a single page, with attributes created and edited inline under their owning template
• Variations - A dedicated list and editor, with variation options managed in slide-in sheets
• Product relationships - Previously "Custom relationships", now with its own list and editor view

As of July 22, 2026, filtering orders using the with_tax and without_tax attributes on the GET /v2/orders endpoint is deprecated. This capability will be removed on October 19, 2026.

What's Changed?

• Deprecated as of July 22, 2026 - Requests to GET /v2/orders?filter= using the with_tax and without_tax attributes continue to work during the deprecation period, but we recommend removing any dependency on these filters now
• Removed on October 19, 2026 - After this date, requests to GET /v2/orders?filter= filtered using the with_tax and without_tax attributes will return an error

For details see:

• Get all Orders

Catalog rules can optionally include a search profile so shopper search follows the same segment as catalog and pricing — without hard-coding search_profile in your storefront.

What's New?

• Optional search_profile_slug on catalog rules - Attach a search profile when configuring the rule for an account, customer, channel, or context tag
• Automatic profile on shopper search - Matching shopper search and multi-search use that profile for filters, ranking, and related search behavior; a valid rule slug takes precedence over the search_profile query parameter
• EP-Search-Profile response header - See which profile was applied (SYSTEMS_DEFAULT_PROFILE when the built-in default is used)
• Price and assortment together - Use the same rule for price books and searchable assortment (for example a reseller-only category filter on the profile)

What's Changed?

• Shopper search profile resolution - Catalog rule slug (when valid) → search_profile query parameter → tenant default → built-in default
• Admin search unchanged - Explicit catalog/release search does not apply catalog rule profiles
• Safe fallthrough - An invalid or stale rule slug does not fail the search; Catalog Search falls through to the next resolution source

For details see:

• How a search profile is chosen
• Price Segmentation — product assortment
• Catalog Search API
• Setting Up Catalog Search

As of July 8, 2026, the advanced promotion usage filtering enabled by passing the EP-Public-Search-Type: cm_search header to the GET /v2/promotions endpoint is deprecated. This capability will be removed on October 6, 2026.

What's Changed?

• Deprecated as of July 8, 2026 - Requests to GET /v2/promotions with the EP-Public-Search-Type: cm_search header continue to work during the deprecation period, but we recommend removing any dependency on this header now
• Removed on October 6, 2026 - After this date, the EP-Public-Search-Type: cm_search header and its advanced usage filter attributes (such as promo_name, promo_status, code_code, order_id, and order_customer_email) are no longer supported on this endpoint
• Standard filtering is unaffected - Filtering promotions with eq(code,...) on GET /v2/promotions continues to work as before

For details see:

• Get all Promotions
• Promotions Standard Introduction

We've made it easier to review subscriptions and invoices in Commerce Manager, with quicker access to details, clearer invoice context, and a smoother browsing experience.

What's New?

• Stripe payment ID in invoices - The invoices table now displays the associated Stripe payment ID, so you can quickly reconcile payments
• Subscription details in a sheet - Subscription details now open in a side sheet instead of a separate page, showing a focused version of the Subscriber view scoped to a single subscription and its invoices
• Richer subscription sheet - The sheet now includes subscriber details, a link to the subscriber, and that subscription's invoices in one place
• Clearer invoice context - In the Subscriber panel, each invoice now shows which subscription it belongs to via a subscription link/column and on the "last invoice" card
• Pagination fix - Fixed a bug where invoice pagination would reset when closing the sheet

For details see:

• Viewing Invoices
• Managing Active Subscriptions

Shipping and billing addresses on orders and shipping groups now support a line_3 field, giving merchants a third address line for complex address requirements.

What's New?

• line_3 on order shipping address - The shipping_address object on orders now accepts and returns a line_3 field
• line_3 on order billing address - The billing_address object on orders now also supports line_3
• Shipping groups support - line_3 is available when creating and updating shipping groups on both carts and orders

For details see:

• Checkout
• Create a Shipping Group for an Order

Search hits now return a breakdown of how their text relevance score was derived, giving merchandisers a window into ranking decisions for debugging and relevance tuning.

What's New?

• text_match_info on each hit - Every hit includes the overall relevance score plus additional signals such as best_field_score, best_field_weight, fields_matched, tokens_matched, num_tokens_dropped, and typo_prefix_score
• Diagnose ranking - Use these signals to understand why one product ranks above another, or to build custom relative metrics for relevance evaluation
• Internal ranking signals, not display metrics - Scores are not normalized to a 0–100 scale and are only comparable within the same result set, so they are intended for debugging rather than shopper-facing "match %" display

For details see:

• Search

MINOR Synonym tuning settings on search profiles

Search profiles now expose a dedicated synonym_settings object so you can control how synonym matches are ranked and resolved at search time, independent of typo tolerance settings.

What's New?

• Demote synonym matches - Set demote_synonym_match to rank results matched via a synonym below direct (non-synonym) matches
• Prefix synonym resolution - Set synonym_resolution_allowed_on_prefix to allow incomplete (prefix) query tokens to resolve to synonyms at every token position
• Typo-tolerant synonym resolution - Set number_of_typos_allowed_when_resolving_synonyms (0, 1, or 2) so misspelled terms can still trigger a synonym expansion; this setting has moved here from typo tolerance

For details see:

• Search Profiles

MINOR Faceting on date fields

Date fields can now be used as facets, so users can filter results by dates such as when a product was created or last updated. Faceting is supported on both core date fields and custom (flow) date fields.

What's New?

• Custom date field faceting - Date-typed custom fields are now facetable, joining the existing string, integer, float, and boolean facet types
• Core date field faceting - Enable faceting on built-in date fields such as created_at and updated_at by setting facetable in core_field_overrides
• Re-index required - A re-index is required for the change to take effect

For details see:

• Indexable Fields

We've completely redesigned the Product Editor in Commerce Manager, making it faster and easier to manage your catalog with greater clarity and less friction.

What's New?

• Side-by-side editor - The editor opens alongside your product list, so you can select and switch between products without losing your place or disrupting your workflow
• Preserved search & filter criteria - Active search and filter settings are retained as you navigate between products, making bulk review and updates far more efficient
• Global saving - Changes are automatically queued as you work across sections; save everything at once with a single button, or discard to revert to the last saved state
• Streamlined section navigation - Product sections are organized into four clear areas: Product Details, Categorization, Pricing, and Inventory
• Variation navigator - For products with variations, switch between them using the variation selector or expand the product list table to navigate child products directly
• Reorganized layout - The most relevant fields are prioritized up front, less frequently updated fields are read-only by default, and empty fields are hidden to reduce clutter, with a secondary view available when needed
• Integrated custom attributes - Attribute templates are built directly into the Product Details tab, with inline value updates, expand/collapse via the toolbar, and a toggle to hide empty fields
• Improved categorization - Assign products to hierarchies, nodes, or tags with ease, using a secondary pane to search, select multiple nodes at once, and remove them with a single click
• Redesigned pricing tables - Pricing is displayed in a structured table with inline value entry, currency visibility toggles, and tax inclusion mode controls; volume and sale pricing options appear only when in use
• Unified inventory experience - Inventory is organized by location for a clearer view of stock levels, with multi-location support and quantity management consistent with the broader inventory section in Commerce Manager

Explore the new experience today in the Products section of Commerce Manager

On September 14, 2026, we will remove the per_application value for the consume_unit field when creating promotion codes for Rule Promotions.

What's Changed?

• consume_unit: per_application removed on September 14, 2026 - After this date, new promotion codes for a Rule Promotion can no longer be created with per_application; set consume_unit to per_checkout or omit the field to use the default
• Existing codes are retained - Promotion codes already created with consume_unit: per_application continue to work as configured
• Rule Promotions only - This change applies only to Rule Promotions. Promotion codes for standard (V1) Promotions are not affected

For details see:

• Create Promotion Codes
• Creating Promotion Codes in Commerce Manager

A store can now enable both Custom Discounts and Rule Promotions at the same time without the system rejecting either at the store configuration level.

What's New?

• Simultaneous store-level configuration - Custom Discounts and Rule Promotions can both be enabled in a store's configuration without conflict
• Per-cart exclusion preserved - A single cart applies only one promotion system at a time — Custom Discounts or Rule Promotions, never both.

For details see:

• Cart settings

You can now define groups of equivalent or related terms so shoppers find products regardless of the exact wording they use.

What's New?

• Manage synonym sets - Create, list, retrieve, update, and delete named synonym sets, scoped to an organization or a store
• Multi-way and one-way synonyms - Treat terms as fully equivalent (sneakers, trainers, running shoes) or map a root term (fruit) to its synonyms (apple, mango, peach) in one direction only
• Attach to search profiles - Reference synonym sets from a search profile's synonym_sets attribute so they apply at search time, with locale and symbol-indexing options per item

For details see:

• Synonym Sets
• Search Profiles

MINOR Stopword Sets for Catalog Search

Define sets of common, low-value words (such as "the", "a", "an", "is") to ignore during search so results stay relevant and free of noise.

What's New?

• Manage stopword sets - Create, list, retrieve, update, and delete stopword sets, scoped to an organization or a store
• Per-locale sets - Maintain one stopword set per locale, with a default set for unspecified locales
• Asynchronous sync - Track each set's sync status (pending_sync, synced, sync_failed) directly in API responses

For details see:

• Stopword Sets

MINOR Handling typographical errors (misspellings) and prefix matching for search profiles

Search profiles now expose fine-grained control over how forgiving and predictive matching is, both at the profile level and per field.

What's New?

• Typo tolerance - Configure typo correction with number of typos (misspellings), length thresholds, token-dropping behavior, split/join handling, and synonym typo resolution
• Prefix matching - Treat the last query token as a prefix so results appear as shoppers type (for example, "red app" matches "red apple"), with a profile-level default and per-field overrides
• Per-field overrides - Override num_typos and prefix on individual fields in your field weight configuration

For details see:

• Search Profiles

MINOR Stemming and tokenization controls for indexable fields

Indexable Fields can now fine-tune how text is analyzed, improving recall for descriptive content and giving you control over how terms containing special characters are indexed.

What's New?

• Stemming - Enable Snowball stemming per field so a search for "running" also matches "run" or "runs" on both custom and core fields
• Token separators and symbols to index - Control how text is split into tokens and which special characters are preserved, at the collection level or per field
• Core field overrides - Apply stemming, tokenization, and sorting settings to built-in fields like name, description, and sku using core_field_overrides

For details see:

• Indexable Fields

We're planning to introduce some minor changes to the way pagination works on some endpoints on or after 1st September 2026. We do not expect these changes to cause problems with existing customer implementations in most cases but are announcing in advance as there is a slim possibility that this may be a breaking change for some.

The following endpoints will be affected:

GET /pcm/products
GET /pcm/products/{productID}/children
GET /pcm/products/{productID}/nodes
GET /pcm/products/{productID}/custom-relationships
GET /pcm/products/{productID}/custom-relationships/{customRelationshipSlug}/products
GET /pcm/hierarchies
GET /pcm/hierarchies/nodes
GET /pcm/hierarchies/{hierarchyID}/nodes
GET /pcm/hierarchies/{hierarchyID}/children
GET /pcm/hierarchies/{hierarchyID}/nodes/{nodeID}/children
GET /pcm/hierarchies/{hierarchyID}/nodes/{nodeID}/products
GET /pcm/custom-relationships

For more details see: Product Pagination

What's New?

• You can now gate a cart_discount action behind a cart total threshold using the condition field. For example, you can create tiered cart_total discounts using multiple cart_total conditions in a single promotion.

For details see:

• Promotions Builder API Overview

Merchandisers and integrators can now attach flexible string metadata to products in two visibility tiers—catalog-visible shopper attributes and admin-only attributes—using the same model already established for hierarchy nodes.

What's New?

Extended the PIM product model with shopper_attributes and admin_attributes: optional maps of string keys to string values, validated consistently with nodes (including limits on the number of keys and on name and value length).

Product APIs support creating, updating, and reading these fields on products; persisted data is stored on the product document for downstream catalog and administration flows.

Product lifecycle events for create and update now include shopper and admin custom attributes where applicable, so downstream consumers can react without an extra round trip.

CSV export can emit custom attribute columns using the shopper_attributes. and admin_attributes. prefixes; selective exports use columns.include with either explicit keys or a per-type wildcard (shopper_attributes.* / admin_attributes.*), with validation that prevents combining a wildcard and individual columns for the same attribute type in one request.

CSV import understands the same column naming, so bulk workflows can round-trip attribute data alongside core product fields.

For variant matrices, new child products inherit the base product’s shopper and admin attributes at build time; rebuild reconciles parent keys onto matched existing children so shared parent metadata stays aligned while child-specific keys remain unless the parent removes them.

This release brings product custom attributes in line with hierarchy behavior and reduces the need for parallel systems or workarounds for storefront versus internal metadata.

For details see:

• Custom attributes on products

Shipping Groups now support flows, enabling clients to add custom data fields to shipping group objects.

What's New?

• Custom fields for Shipping Groups - Extend cart and order shipping groups with custom data fields using flows

For details see:

• Cart Shipping Groups
• Extend a Resource

You can now target cart items based on their custom attributes when creating promotions in Promotions Builder.

What's New?

• Custom attributes on cart items - Specify custom attributes to be added to cart items for use in promotional targeting.
• Custom attribute targeting - Create promotion conditions that target cart items by their custom attributes, enabling more precise promotional rules.

For details see:

• How to create promotion with item custom attribute
• Cart Items
• Promotions Builder API

You can now control how cart items with the same SKU but different inventory locations are handled. When the separate_items_by_location setting is enabled, items with the same SKU are kept as separate line items based on their location instead of being merged.

What's New?

• Location-based item separation - Enable or disable location-based item separation by setting separate_items_by_location to true or false. When enabled, cart items with the same SKU but different inventory locations are kept as separate line items instead of being merged.

  • Can be set at the store level or for individual carts with the setting: "item_settings": { "separate_items_by_location": true }. By default, it is false.

• For details see:

• Carts settings API

• Multi location inventories

• Cart item with location API

You can now set a maximum quantity limit across all eligible items in a promotion. This new Maximum discounted quantities across all eligible items option allows you to cap the total number of units that receive a discount.

What's New?

• Cross-item unit cap - Set a total unit limit that applies across all eligible SKUs, not per-SKU

For details see:

• Creating an Item Discount with Max Units Limitation Guide
• Rule Promotions API