Which steps are necessary to create a configurable product that can be used in a subscription order? Note: There are 3 correct answers to this question.

Question

Options

• AFlag product as configurable
• BDefine variant prices
• CDefine class and characteristics
• DDefine values for contract duration Assign class to the product

• A
  77% (36)
• D
  23% (11)

Explanation

Creating a configurable product for subscription orders requires three foundational steps: flagging the product as configurable (A) activates the configuration engine so the system treats it differently from standard products; defining class and characteristics (C) establishes the configurable attributes (e.g., color, storage size) that customers can select; and defining variant prices (B) ensures each possible configuration combination has a valid price, which is essential for generating accurate subscription pricing.

Option D is incorrect because defining contract duration values pertains to subscription contract settings - not to the product configuration setup itself - and assigning a class to the product is already encompassed within option C (you define the class and then associate it with the product as part of that same process).

Memory tip: Think of it as "Flag → Classify → Price" - you must first tell the system the product is configurable, then describe what can be configured, then value each option. Contract duration belongs to the subscription contract, not the product catalog.

No community discussion yet for this question.