Hi everyone,
We are considering using SOM (Sales and Order Management) to build an internal Lead-to-Cash process.
Our product master is planned to be centered on Product Offering / Product Specification. In our business, the downstream process changes depending on the product type (e.g., vendor fulfillment/hand-off, license provisioning, cloud account/contract association, renewal management, etc.).
We have the following product types:
In-house products/services
Resale: physical goods
Resale: licenses (e.g., annual renewals)
Resale: cloud resale (usage-based / monthly billing, etc.)
Questions:
Are there any OOTB (standard) fields/attributes around Product Offering / Product Specification that can be used as a “key” to drive this kind of branching?
(e.g., in-house vs resale, delivery type such as physical/license/cloud, etc.)
If there is no suitable OOTB option, what is the recommended approach in practice (from an operations + upgradeability perspective)?
Define it as a Characteristic (on Product Spec/Offering), or
Add a custom field on Product Offering (or related objects)
Any pointers to relevant documentation or implementation examples would be greatly appreciated. Thank you!
