Best Practice question: One catalog item, three different configurations?

[ILYA STEIN]

I am building automations that allow our users to provision a single piece of software. There are three different configurations available, which the user selects from a dropdown on the form. A single order may include one, two, or all three of these configurations. I am looking for recommendations on how to organize these orders in the most user-friendly way. I am considering making this an order guide where the user will select applicable configurations, so that the catalog item appears pre-configured for each selection (i.e., with a tab with pre-selected value, for each selected configuration). This feels a little cumbersome, but I think I can make it work. However, I wanted to hear what others would do in such scenario.

[DrewW]

I would say that just using a var that allows you to pick multiple configurations and then have the flow/workflow sort it out would be the best option.  But I think you also need to understand how its going to get tracked in your SAM process and how you are doing your reporting.  Meaning if the user picks all three config options counted as 3 separate instances/installs or is it just one?  If you need it to show up on reports three times you may need to go with three diff cat items.

[ILYA STEIN]

The workflow will be driven by the configuration selector for sure. For reporting purposes, I should be able to retrieve each RITM's purpose based on the selection variable, so that's not an issue. I guess for my Proof of Value / Phase 1 I will try to keep things simple and do an order guide or just a cart with up to three RITMs in it. I am still open to hear what others did in similar situations.