Skip to content

Rebate targeting

Rebate targeting surfaces live stepped and individual rebates that are close to a band boundary, so buyers can chase turnover that unlocks a better rate (an opportunity) or protect turnover that is at risk of dropping to a worse rate (a threat). It is read-only analysis built from the rebate index — nothing here changes a deal.

An element is an opportunity when projected spend sits in the upper part of its current band (a little more turnover reaches the next band) and a threat when it sits in the lower part (a small drop falls to the band below). These flags, along with the money at stake, the band floor/ceiling, and urgency scores, are computed when rebates are indexed, so targeting reflects the last rebate calculation, not a live one.

The targeting view

Targeting (/rebate/targetting, sidebar Financials → Rebate Targets, member or figures role) is a watchlist with two headline cards (Potential gain, At risk) that act as filters, plus filters for group vs individual rebates, watched deals, urgency, and category, and a sortable table with a band-progress bar per rebate and an Excel export.

Note the platform serves the non-versioned sidebar (includes/templates/layouts/sidebar.html), not the per-version copy; the gating above reflects the file actually loaded.

Clicking a rebate opens the target drill-down modal: current vs estimated position against the bands, a projected-spend chart (seasonal when the deal has seasonality data, otherwise linear), the band table, and rule-based insights (monthly target to unlock the gain, pace vs elapsed time, return per extra unit of spend, member-concentration risk, and a seasonality look-ahead).

Only stepped and individual rebates are targeted; growth rebates (groupgrowth/individualgrowth) are excluded.

How permissions apply

Targeting queries filter each rebate by its element permissions against the viewer's roles and by site; individual rebates are additionally scoped to the viewer's own company.

Why do targeting results change unexpectedly

  • An opportunity or threat appeared/disappeared — the rebate was recalculated after new turnover, moving projected spend within its bands; targeting follows the index.
  • Different users see different lists — element permissions and member scoping are applied server-side.
  • A rebate is absent entirely — it is a growth rebate (excluded), or its accrual period is not currently running.

What targeting is not

  • Not member target-setting — nothing here is editable; there is no save.
  • Not the rebate management dashboard — that tracks payments; targeting tracks proximity to band boundaries.
  • Not what-if analysis — that models membership changes across the portfolio.