Product Management

Customer budget management gives you as an agency and your industry customers a live overview of the budget status. A distinction is made between allocated, used, planned and still available budget. The customer budget shows the costs from your customer’s perspective and does not have to correspond exactly to the actual costs. An average value is often used here, which you can freely define for each project and event type.

The budget is evaluated in the number of events and optionally with an amount in your standard currency and updated live. The amount that reduces the customer budget when events are carried out depends on your definition. You can evaluate each event type differently depending on the project. This allows you to manage the budget very flexibly.

If activated on the respective project, customer budget management transparently displays all event bookings for customers (e.g. industry) as well as agencies, thus creating live controlling.

Depending on the event type, the budget can be automatically updated in different ways when it is used up (e.g. when an event is held). This means that events can be valued differently, as different costs are incurred depending on the type of event and the number of people involved.

Budgets are always mapped in EMPPLAN on a calendar year basis as standard and can be booked on a brand-specific basis and limited to individual projects or to event types that can be used across projects.

Budgets are automatically mapped according to the respective territory structure of the customer brand. The budget status of users at channel level (e.g. overall sales manager) and users at territory level (e.g. sales representatives) can be displayed segmented according to allocated, used, planned and still available budget.

With commission rules for promoters, you can define variable shares in sales or other promotional successes. In EMPPLAN, there is a commissions section for this purpose at product group and product level. Rule-based remuneration rates for reported transactions can be stored there. Promoters or sales representatives can see what effect this has on their event remuneration directly when reporting their key performance indicators, as EMPPLAN calculates this live on the basis of rules that have been created.

Any number of rules can be created for this purpose. You can define all rules for commissions historically correctly, even retroactively if required. This ensures that the correct rule is always applied from a specific date or in certain periods.

The following data can be defined for commissions at product group level:

• Name (no longer used)
• from date (this commission rule applies from this date)
• Team (if defined, the rule only applies restrictively to a certain group, a so-called team of users)
• from number (e.g. can be used for remuneration but a certain target achievement or/and graduated commissions)
• Location (restrictive, if defined, so that the rule only applies to the defined locations)
• can break through top stop (if the break-through feature is activated, the commission for this product can exceed the maximum remuneration per event specified on the project)
• apply further rules (enable the ability to combine rules, e.g. to implement tiered commission models)
• Commission per unit
• Commission type (standard currency or absolute commission, % of gross sales price, % of net sales price)

With commission rules for promoters, you can define variable shares in sales or other promotional successes. In EMPPLAN, there is a commissions section for this purpose at product group and product level.

Rule-based remuneration rates for reported transactions can be stored there. Promoters or sales representatives can see what effect this has on their event remuneration directly when reporting their key performance indicators, as EMPPLAN calculates this live on the basis of rules that have been created.

Any number of rules can be created for this purpose. You can define all rules for commissions historically correctly, even retroactively if required. This ensures that the correct rule is always applied from a specific date or in certain periods.

At product level, in addition to the (standard) commissions for promoters, there are also so-called promotion commissions. The difference lies in the data that can be stored and in the priority of the rule execution:

• Promotional comm issions are prioritized for execution instead of commissions.
• Promotional comm issions can be provided with a to date (end date of the promotion) and can therefore be limited in time.

The following dates can be defined for commissions at product level:

• Name (no longer used)
• from date (this commission rule applies from this date)
• until date (for promotional commissions: this commission rule applies until this date)
• Team (if defined, the rule only applies restrictively to a certain group, a so-called team of users)
• from number (e.g. can be used for remuneration but a certain target achievement and/or graduated commissions)
• Location (restrictive, if defined, so that the rule only applies to the defined locations)
• can break through top stop (if the break-through feature is activated, the commission for this product can exceed the maximum remuneration per event specified on the project)
• apply further rules (enable the ability to combine rules, e.g. to implement tiered commission models)
• Commission per unit
• Commission type (standard currency or absolute commission, % of gross sales price, % of net sales price)