Product managers requested to make a brand new product available for the initial sale by...

To make a brand-new product sellable and fulfillable, the sprint scope must include the commercial Product Model and the decomposition relationships that translate the sold item into the technical products required by downstream fulfillment. Those two elements establish both the CPQ-facing catalog definition and the Order Management fulfillment mapping. The recommended configuration follows the native Communications Cloud responsibility boundary: catalog and CPQ determine the commercial request, while Order Management, OmniStudio, or the relevant platform service performs the downstream processing required by the use case. A MACD-specific orchestration process is not inherently required for the initial sale, and a Guided Selling OmniScript is optional UX rather than the minimum capability needed to make the product orderable and decomposable. Avoiding duplicate logic is important because repeated rules across catalog, integration, and orchestration layers quickly become inconsistent as products evolve. The selected approach keeps the authoritative data in the correct object model, supports later lifecycle operations, and minimizes additional processing or manual intervention. It should be implemented declaratively wherever the platform feature can express the requirement, with customization reserved only for behavior that genuinely falls outside the supported framework.

Study Guide Reference:Product onboarding; Enterprise Product Catalog; Product Model; decomposition relationships; fulfillment readiness.