You can now apply Store assignment changes to a Category and all of its descendant Categories in a single update action. This makes it easier to convert a global Category subtree into a Store-scoped one, or the other way around, without updating each Category individually.

This feature is currently in public beta.

These actions are only available on the general Category endpoints and are rejected on the in-Store endpoints. The API records the request and responds with 202 Accepted and a StoreSettingOngoing Warning. A background process then applies the change to the Category and all of its descendant Categories, so the change is eventually consistent. The Category in the response still has its previous Stores. While the background process runs, Store updates, Change Parent actions, and Create Category requests with a parent in the affected subtree fail and should be retried. The actions are limited to Categories with at most 1000 descendant Categories.