Dashboard Support for Tiered Discounts with a Single Code

[noah-jacksonn]

Feature request

Is your feature request related to a problem?

Yes. Right now, a single discount code in Polar applies the same percentage across all attached products/plans.

In my case, I have one affiliate code (e.g. DIXON) that is meant to give: • 50% off for the first 2 months on monthly plans • A smaller discount (e.g. 15%) on annual plans

Today, if I attach that code to both monthly and annual products, it just applies the same percentage to both. That either over-discounts annual plans (e.g. 50% off the entire year) or forces me to create multiple separate codes, which is tedious for affiliates and customers.

Describe the solution you'd like

I’d like Polar to support tiered discount logic per billing frequency (or per product) under a single code.

Concretely: • I define one public-facing code, e.g. DIXON • In the dashboard, I can configure different rules for that code by plan / billing frequency, for example: • Monthly plan: 50% off for first 2 billing cycles • Annual plan: 15% off first year • When a customer enters DIXON at checkout, Polar automatically applies the correct underlying discount based on whether the selected plan is monthly or annual, and shows the correct percentage in the embedded checkout.

This keeps a single, memorable code for affiliates, while giving creators control over how aggressive discounts are on different plan frequencies.

Ideally this is all configurable at the dashboard level, without having to build custom routing logic ourselves.

Describe alternatives you've considered

As suggested, I could add a frontend layer that: • Collects the user’s code • Checks which plan (monthly vs annual) they selected • Calls create-checkout-session with the appropriate internal discount code per product This is workable, but: • It adds engineering complexity just to replicate logic that feels like it belongs in Polar • The discount behavior isn’t visible/manageable from the dashboard for non-technical teammates • It’s easy to misconfigure and hard to audit at scale

Additional context

•	My use case is affiliate / influencer codes where one simple code is part of the marketing (e.g. “Use code DIXON for a discount”).
•	Users buy directly through my app on this page with embedded Polar checkout:

https://app.harmonyappai.com/membership • The desired behavior is: one user-entered code, different discount logic by plan frequency, fully visible and editable in the Polar dashboard.