How designer-created personal SKUs work
Learn how personal SKUs stay visible only to their creator until they are approved into the organisation catalogue.
Designers (not just catalogue managers) can create their own SKUs and SKU groups. These are flagged as designer-owned at creation and are deliberately NOT added to the org or business-unit catalogue: the create flow skips the inventory mapping step for them. They surface only through the personal-groups listing, which filters by both the creating user and the designer-owned flag - so another designer in the same team will not see a colleague's personal SKUs, which is expected behaviour, not a bug. Only the creator can delete their personal SKU or group; anyone else gets ONLY_SKU_CREATOR_CAN_DEPRICATE_SKU (or ONLY_SKU_GROUP_CREATOR_CAN_DEPRICATE_SKU_GROUP). Deletion just hides the item from the creator's lists; designs already using it keep working. To make a personal SKU available to the whole team, it must go through the approval flow: once approved, the SKU and its group are converted to normal org-owned items and added to the business-unit catalogue, after which they behave like any other catalogue SKU. Common tickets this explains: 'my teammate cannot find the SKU I made' (it is personal - needs approval), and 'I cannot delete this SKU' (they are not its creator).
Designers can create their own furniture items and publish them to the catalogue.
The item becomes available to others once it is approved into the organisation catalogue.