Package v20.16 - 26 February 2026
On this page
This release adds a Custom Shipping Provider option, fixes several sync and installation issues, improves the Console Media Manager performance, and provides a new support tool for purging accumulated change event records.
Enhancements
Custom shipping provider option Merchants can now select “Custom” as a shipping provider type, in addition to the existing pre-built integrations (Australia Post, Sendle, StarTrack, Bringg). This allows businesses to configure shipping with providers not natively supported by StoreConnect.
Purge change events support tool A new batch job is available for support teams to bulk-delete accumulated Change Event records. In organizations where millions of change events have built up over time, the existing daily cleanup (which removes processed events older than 10 days) may not be sufficient. Contact StoreConnect support for more information.
Console media manager performance improvements The Console Media Manager now loads faster and handles permissions more efficiently. Unnecessary data lookups have been removed, and folder-level permissions (create, delete, update) are now managed consistently across all media components. Button styles across media-related dialogs have also been made more consistent.
Deprecated Fields
No fields were deprecated in this release.
Fixed Bugs
Tax group sync Tax group-related records (Product Tax Groups, Tax Groups, and Tax-Tax Groups) were not generating change events for StoreConnect Sync, meaning changes to these records were not being synchronized between Salesforce and the web store. These triggers have been updated to properly support sync.
Content block scheduled flows Scheduled flows that update Content Block Children records were failing with a query exception. This was caused by the system running the query in a restricted mode that did not support the custom object type. The query has been updated to run in the correct mode, resolving the error for scheduled flow operations.
Package installation errors with permission sets Some organizations experienced errors during package installation due to issues with standard permission set handling. The permission set processing has been improved to handle individual permission failures gracefully without blocking the entire installation, and to avoid runtime exceptions when building permission maps during 2GP (second-generation package) installs.