Dependent Targets

Description

Some agreements make a rebate conditional on the customer reaching another target. Achievements let you configure this dependency without directly linking customer targets: one target range awards an achievement, and another can require it before generating a rebate.

How It Works

When a customer reaches a target range with an Achievement Code, running Generate Rebates calculates the rebate and records the achievement for that customer, along with the source target, period, and achievement date. The same achievement is not recorded more than once for the same context.

If a target range has Requirements, the customer must have earned all the listed achievements. If any are missing, the rebate is not generated, even if the range's amount and quantity conditions are met. The requirements are additional to the range's usual conditions.

The same achievement can be used as a requirement by multiple targets.

Configuration

1. In Achievement Codes, create the codes you need and provide a description for each.
2. On the target range that awards an achievement, select its Achievement Code.
3. On the dependent target range, add the required codes under Requirements. If you add more than one, the customer must have earned all of them.

You do not need to link customer targets directly. The dependency is defined by the achievement codes.

Example

In this configuration, Target B requires the achievement awarded by a range in Target A.

• Target A awards Achievement A when the customer reaches the range's minimum amount.
• Target B requires Achievement A.

When you generate rebates for the period, Target A is calculated before Target B:

• Adatum reaches Target A's minimum amount and earns Achievement A. Since Adatum also meets Target B's own conditions, the rebate for Target B is generated as well.
• Trey does not reach Target A's minimum amount, so Trey does not earn Achievement A. As a result, no rebate is generated for Target A or Target B, because Target B's requirement is not met.

If a target requires multiple achievements, the customer must earn all of them. Each achievement can be awarded by a different target.

Generating Rebates from a Customer Target

When you run Generate Rebates from a Customer Target, the system can identify the targets that award missing achievements and prompt you to calculate them first.

• Yes: calculates the targets that award the required achievements first, then calculates the requested target.
• No: continues without calculating them. The process is not canceled, but ranges whose requirements are not met do not generate rebates.

Automatic calculation resolves direct dependencies only. Targets calculated automatically do not look for further prerequisites. Circular dependencies do not cause endless loops.

Generating Rebates from a Customer Period

When you run the process from a Customer Period, targets without requirements are calculated first, followed by dependent targets. This allows the required achievements to be available when the dependent targets are evaluated.

Reviewing Recorded Achievements

You can review recorded achievements using Period Achievements on a Customer Period or Target Achievements on a Customer Target. Each action shows the achievements recorded for the selected period or target.

Use Cases

• Tiered incentive and milestone-based loyalty programs.
• Unlocking premium campaigns after customers meet prerequisite targets.
• Cross-product incentives between product families.
• Reusing one achievement as a requirement for multiple targets.

Limitations and Considerations

• All configured requirements must be met; reaching the amount or quantity thresholds does not replace them.
• Automatic calculation from a Customer Target resolves direct dependencies only, not multi-level chains.
• When calculating from a Customer Period, targets without requirements are processed first.
• An achievement becomes available after the customer reaches its awarding range and the rebates are calculated.
• The system can suggest prerequisite targets only when the targets that award the required achievements are configured correctly.