October 2026 release notes for Merchandising.

One object-level validation run can now cover up to 20 tables of a solution, under a single run_id, and its alerts cover the whole run: one email per person and one webhook event per channel, with results grouped by table. See Run validations on demand.

A schema upgrade now needs only solutionName and newAppVersion. The API reads the app and the version the solution is on from the solution itself, so appName and previousAppVersion are no longer part of the request; requests that still send them keep working.

With dryRun set to true, the API returns the tables and columns the upgrade would add without applying them. An upgrade to the version the solution is already on is now rejected with 400 Bad Request. See Upgrade a rolled-out schema to a new version.

Object-level validation alerts can now be sent to an HTTPS endpoint you operate, as one signed JSON event per validation run. A webhook channel is registered through /api/v2/alert-configs like a Slack or email channel, keeps its secret in an external credential, and can choose which outcomes notify it, passing checks included. See Webhook alerts.