Multi-Level Promotion Planning (MLPP)
Use multi-level promotion planning (MLPP) to create promotions at higher levels in the customer hierarchy and push them, at once, to planning customers.
Required Editions
Available in: Lightning Experience Available in: Enterprise and Unlimited Editions where Consumer Goods Cloud is enabled |
Use this feature to:
- Create a promotion for multiple account entities at the same time. For example, to save time and data entry effort, the key account manager (KAM) who manages the Tesco account can plan a promotion for two account entities (Tesco and One Stop) simultaneously.
- Create a promotion for multiple regions or banners of an account. For example, the KAM can plan a promotion for two of their regions or banners (Region A and Region B) at the same time.
- Create a brand promotion for multiple account entities simultaneously. For example, the brand manager who manages the Lopples brand can plan a promotion for all accounts of the Kroger South-East region that the respective account managers can execute later.
- Create a category promotion for multiple account entities simultaneously. For example, the category manager who manages the snacks category can plan a promotion for all accounts of the Kroger South-East region that the respective account managers can execute later.
Multi-level promotion planning involves:
- Creating a pushable promotion anchored to customers at the higher non-planning levels of the customer hierarchy.
- Pushing the parent promotion to create child promotions for customers that are hierarchically under the anchor of the parent promotion.
- Reviewing KPIs of individual child promotions as well as aggregated values at the parent promotion level.
- Adjusting the attributes of the parent promotion and synchronizing the adjustments to child promotions.
It is applicable only for those pushable promotions that are based on a template with these configurations:
- The push process flow option is set to Distribute and Calculate.
- At least one child promotion relevant KPI is added to the promotion template hierarchy.
- The Distribution Type (Customer Hierarchy) of the corresponding KPI definition is set to Metric, Copy, or Equal.
The process is dependent on the value of the Distribution type (Customer Hierarchy) field of the corresponding KPI definition. For instance, if this field is set to Copy, the system copies the value from the parent promotion to the child promotions in this manner:
| When a value is entered at the | Copy it to the |
|---|---|
| Total level of a promotion KPI | KPI total level of all child promotions of the selected customers. |
| Tactic level of a promotion tactic KPI |
tactic total level of all the child promotions of the selected customers. However, the system does not distribute this value to the copied child promotions of the selected customers if tactics are not copied during the push process. Also, values are not copied to the child promotions of the selected customers if the child promotion templates do not have the relevant tactic. |
| Product level |
specific product of all the child promotions of the selected customers. Copy this value to the specific product of all the child promotions. However, the system does not distribute the value to the child promotion if the particular product is not available in the child promotion. |
| Product group level |
specific product group of the child promotions in which the particular product group is present and has at least one product of this product group. For tactic-specific KPIs, the child promotion of the selected customer includes a tactic that promotes at least one product of the product group. For tactic-agnostic KPIs, the child promotion of the selected customer promotes at least one product of the product group. |
If the Distribution Type (Customer Hierarchy) = Equal, the system equally distributes the value from the parent promotion to all the child promotions of the selected customers.
If the Distribution Type (Customer Hierarchy) = Metric, the system distributes the value according to the metric KPI from the parent promotion to all the selected child promotions. In this case, the metrics of child promotion KPIs are written at all levels. To prevent errors, ensure that the object and time scopes of the base KPI and the resultant metric KPI are the same for the parent promotion.
Each time the parent promotion KPI value is modified, the system redistributes this value from the parent promotion to the child promotions only when the user performs a repush.
When distributing values from the parent promotion KPIs to the child promotion KPIs, the system applies rounding precision to the total values in the this manner.
If the Distribution Type (Customer Hierarchy) = Metric, Equal, or Copy and rounding precision ≠ None, the system:
- Determines the rounding precision for the parent promotion KPI.
- Rounds the value of the first child promotion KPI to the decimal place specified in rounding precision.
- Calculates the carry over by subtracting the rounded value from the current value.
- Calculates the next child promotion KPI by adding the carry over (obtained in the previous step) to its current value.
- Rounds the child promotion KPI to the decimal place specified in rounding precision.
- Repeats all these steps for each child promotion KPI until the values are rounded to the specified value.
