Feature request: per-subscription cancellation notice period ("cancel by" date)

[mjarkas97]

Thank You and all Contributors out there for making it possible to have such a cool app.

The Problem:

In some countries depending on the subscription, one may need to cancel it 2-12 Weeks before the cancellation date.

So having the following entries:

1. Renew Date: 01.03.2027 -> Cancellation should be at 2 week earlier: 15.02.2027 (ignore Feb. has fewer days ...)
2. Renew Date: 01.03.2027 -> Cancellation should be at 4 week earlier: 01.02.2027
3. Renew Date: 01.03.2027 -> Cancellation should be at 8 weeks earlier: 01.01.2027

i would like to be informed/reminded to cancel a subscription before the corresponding date has passed.

Workaround:

Cancellation Date:
The cancellation date wouldn't work because cancellation reminders only fire for subscriptions that were already cancelled. So cancellation reminders only fire for subscriptions that were already cancelled — it's "heads up, access ends soon," not "remember to cancel."

Renewal Reminder Windows:
The windows are a single global setting, so they can't differ per subscription — one contract can't get 14 days lead while another gets 56. The workaround is to set the union of all needed periods (e.g. 56,28,14,7,1) and put the notice period in the subscription Name, since Name is the only field that appears in the notification. Disadvantage: every subscription fires every window, which is noisy for monthly ones, and the Name has to carry data that belongs in a field.

Per-subscription notice period (proposal):
A per-subscription field like cancellation_notice_days (default 0, so existing behaviour is unchanged), used to derive cancel_by = renewal_date - notice_days, with reminders driven off that date instead of the renewal date. Disadvantage: new field plus a migration, and the reminder logic has to key its de-duplication off the derived date rather than the renewal date.

[bscott]

@mjarkas97 Great suggestion. I'll definitely work on this and see if we can get something that's able to make to fit the need in the next release, which should be this weekend.

[bscott]

This shipped in v0.6.5. Each subscription now has a Cancellation Notice (days) field (0–365, default 0 = unchanged behavior). When set, renewal reminders count down to the cancel-by deadline (renewal date minus the notice period) with "Cancel by" wording across email, Pushover, Telegram, and webhooks — matching your examples, e.g. a 01.03.2027 renewal with 4 weeks notice reminds toward 01.02.2027. The deadline also shows in the subscription list, the calendar, and the iCal feed, and if a deadline slips past, reminders fall back to the renewal date so nothing goes quiet. Thanks for the detailed writeup — it made the design straightforward.

[mjarkas97]

Thank You very much, i was also table to test it. It worked as expected.

I found this diagram very helpful for understanding how the different dates relate to one another.