Shockingly, there is no function (i.e., button) for an admin to process an early renewal for a manually-paid user. There is a “process,” but it is far from user-friendly.
For users who pay online, there is a front-end option that does just this. But any effort to process an early renewal on the back-end…does not extend the renewal date?? This behavior is even described in the doc, but why wouldn’t you want the date to move? There must be some specific use cases for that nonsense. If I’m renewing a subscription, of course I want the renewal date to extend!
Recap: if an admin wants to process an early renewal for a customer (the offline part I mentioned actually isn’t even relevant), then the order is either marked paid (because it was paid offline) or the user can log in and pay it online. The end result is an expiration/renewal date that moves a full increment forward (this last part doesn’t happen, oddly enough).
For example, let’s say we have an annual membership that renews on 8/15/2025. The user pays on 7/23/2025, so the admin goes in, triggers early renewal, marks the renewal order as paid, and the user now has a subscription good through 8/15/2026. Easy! (Yeah, well, it doesn’t exist. It should, though, shouldn’t it…?)
Thanks for hearing me out.
Open
Last updated: September 8, 2025
Log in to comment on this feature request.
I totally agree about these features as they are essential for a smoother user experience!
Edit by https://solitaired.io a day ago