Release notes: August 26th 2026 grade

Inriver is moving towards more incremental, smaller releases to better and faster accommodate our customers. With smaller, more frequent releases, Inriver will be able to increase the quality and transparency of the releases and identify and mitigate any erroneous behavior that may be caused by the release much faster. 

NB! To receive notifications when new release notes are published, please ensure you follow this page by clicking the "follow" button above.  

Brand Store v2

Improvements

Indexed Search for faster store search and filtering 

Brand Store now offers Indexed Search as an option for store search and filtering. Instead of resolving search data live on every query, the store pre-builds a search index in the background — so results return quickly and consistently no matter how large the catalog or how many searchable fields are configured. The index is refreshed automatically when data changes in the PIM, but with some delay, keeping it in sync with catalog changes without manual upkeep.

Store Admins can turn Indexed Search on or off per store in the Basic step of store configuration. When enabled, search and filtering run against the pre-built index; when disabled, the store falls back to real-time search, which always reflects the latest data but can be slower on large, richly configured catalogs.

Note: Indexed Search is best suited to large stores with many searchable fields, where live search performance has historically degraded. Smaller stores may see little difference either way.

Who benefits: Store Admins managing large or richly configured catalogs, and their Store Users, who get fast, consistent search regardless of catalog size.

Access: Brand Store — Store configuration, Basic step.

Data filtering in PDF templates 

PDF templates can now declare exactly which entity type(s) they need, so the PDF generation pipeline only retrieves and passes through the data those templates actually use. 
For large data structures with many links, useful for data exports or the Product Detail Page but mostly irrelevant to a given PDF layout, this cuts payload size and speeds up catalog generation.

To use it, add a meta tag to the template head specifying a comma-separated list of entity types, e.g. <meta name="inriver-data" content="Product,Resource">. Matching is case-insensitive and whitespace-tolerant. Templates without the tag are unaffected — behavior stays exactly as today. Unknown entity types, empty values, or duplicate tags are ignored with a logged warning rather than failing generation.

Note: Only the first inriver-data tag is honored if a template contains more than one.

Who benefits: Anyone building or maintaining PDF templates for large, link-heavy data structures, who wants faster catalog generation without over-fetching data the template doesn't use.
Access: Brand Store — Store Admin — Template configuration

Syndicate Advance

Improvements

What's new
Users can now chain multiple functions together on a single field mapping in the Syndicate Advance Mapping UI — no more limiting a field to one transformation function at a time.

Why it matters
Previously, if a mapping needed more than one transformation — for example, applying concatenate, then to upper, then constant to fill in a default — users had to either accept a workaround, request custom dev support, or leave the data non-compliant with retailer requirements. Function stacking removes that ceiling.

Field mapping showing two stacked functions — "choose language" → "coalesce" — on a single mapping row.

Key benefits

• Handles complex retailer requirements natively — many retailer specs require multi-step transformations (e.g., concatenate + to upper + constant) that a single function can't cover alone
• Extensible with custom functions — clients can layer their own custom functions on top of the standard set for fully tailored logic
• Reduces dependency on custom code/dev tickets — SI partners and clients can solve more mapping complexity themselves in the UI, cutting implementation turnaround time
• Fewer workarounds and manual data patches outside the platform
• Faster pilot/rollout cycles — this has been a common onboarding bottleneck
• Directly addresses long-standing SI partner feedback

Who this is for
Implementation partners and internal teams configuring field mappings for retailer syndication channels (Amazon, Walmart, Home Depot, bol.com, etc.).