Closed (won't fix)
Project:
Commerce Recurring Framework
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
19 Jan 2018 at 10:50 UTC
Updated:
4 Feb 2021 at 14:59 UTC
Jump to comment: Most recent
Comments
Comment #2
bojanz commentedRetitling for clarity. We'd definitely want to limit the change to variations of the same product, that's how plans are implemented.
Comment #3
jeff veit commentedThis seems like a good place to discuss subscription changes.
I think Joachim's example is one possible sub change. Others include any change to the form admin/commerce/subscriptions/{id}/edit.
I don't think that most changes here are well handled atm.
An alternative that I can imagine to handle plan changes is to end a subscription and to have an immediate follow-on subscription. You'd want a link between the two, I imagine, so that subs admins can find the history of current subscriptions.
If a plan requires extra information then the fields that hold that information may need filling, and they don't appear on the the form listed above. Nor is there any way for an admin to fill them, except via the sales process.
There is also the issue of allowing users to make changes. I think which changes are permissible is a business decision and needs custom interface. Is this right?
Comment #4
jeff veit commentedComment #5
amateescu commentedHere's the first step for ensuring that subscription updates are properly reflected in their current draft order: #3192755: Updating the payment method of a subscription is not reflected in its current recurring order
Comment #6
recidive commentedI think this is more appropriate than changing products of an active subscription. This can be a custom project commerce_recurring_upgrade.
I've marked #3192515: Allow users to upgrade their membership plan after their current plans billing cycle completes as "won't fix" and will do the same to this one.