Build catalog items - in production!

[Harsh33]

With its first release in Quebec, Catalog Builder has already started being positioned as a game changer. Most of the customers we've spoken to are either already using it, or have an active roadmap to roll it out. While democratization of the catalog is the ultimate goal and we'd love business users to use it themselves, here are some use cases that customers are actively using Catalog Builder for:

• Developers
• Use its easy interface to manage variable layouts
• Use the multi-channel previews to make sure the item looks and feels consumer grade
• Product owners/process owners
• Use it to come up with a basic skeleton of the item themselves 
• Use it as a requirements gathering tool (with the item almost done in the requirements phase, it is then passed on to the developers to add the magic for complex use cases)
• Business users
• Make basic edits to item themselves (name, short description, choices etc). Templates ensure that they can only do what the admins have allowed them to

So what's missing in the Quebec version?

While the first version had templates to apply guard rails to the development process, it missed the following features to allow this to be used directly in production

• A submission flow: To allow for approvals, checks and other processes before the item (or update) is made live
• An easy and controlled fulfillment process authoring experience

How does the Rome version of Catalog Builder solve for this?

• You can define your own submission flow to ensure the item goes through all the checks and balances before going live
• Fulfillment flows can be authored in Catalog Builder using simple steps. Since this is a data driven method of defining the sequence, it it low risk and can safely be done in production

With the Rome version, Catalog Builder moves a step further in its vision to make catalog maintenance a delightful experience!