Some customers work with Distributors who require different SKU codes depending on specific product configurations. These variations typically relate to factors such as package type or environment. For example, in Keepit, the original SKU may change based on the selected package type. In AvePoint, it may depend on the environment.

To handle these scenarios effectively, you can dynamically modify or extend the SKU using proposal attributes that concatenate additional data to the base SKU.

How to Configure SKU Extensions

First, create playbook questions that return the relevant extension values based on user selections. For instance:

• A question for package type that outputs a specific string (e.g., -ADV or -STD).

• A similar question for duration if your SKU structure varies based on contract length.

These questions should return values that can be appended to the base SKU.

How to Build the Final SKU Using a Proposal Attribute

In the proposal attribute, use a concatenation formula to combine the base SKU with the dynamic values from the playbook questions. For example:
BaseSKU & "-" & PackageExtension & "-" & DurationExtension

This formula pulls the original SKU and appends the appropriate suffixes, resulting in a full Distributor-ready SKU.
 

How the Final Output Looks

 

Assuming the base SKU is ABC123, the package extension is PRO, and the duration extension is 12M, the final SKU in the proposal will be:

ABC123-PRO-12M

This method ensures each SKU is formatted as expected by the Distributor, without requiring SKU duplication or manual editing.