Universal containers want to include Product A every time they sell the bundle B.

The requirement is entirely a bundle-cardinality requirement. Setting the default quantity to 1 automatically includes the child when the bundle is configured, setting the minimum to 0 allows the user to remove it, and setting the maximum to 1 prevents a quantity greater than one. This expresses the commercial behavior declaratively on the bundle relationship without adding unnecessary rule processing. This approach is preferable because it uses the platform feature designed for the exact lifecycle stage involved, rather than forcing the requirement into a neighboring layer. A minimum of 1 would make the child mandatory and eliminate the opt-out requirement. Recommendation rules only suggest a product, and an Auto Add rule does not by itself enforce the complete minimum, maximum, and default quantity behavior. In Communications Cloud, that separation materially affects maintainability, performance, and the accuracy of future MACD or order-processing behavior. The solution should therefore preserve parent-child and inventory dependencies, use standard qualification or orchestration semantics, and ensure that downstream systems receive only the information relevant to their responsibility. The same design also simplifies regression testing because the business rule is expressed in one authoritative place and can be validated independently from unrelated product or integration behavior.

Study Guide Reference:Enterprise Product Catalog; bundle cardinalities; child products; default/minimum/maximum quantity.