## Summary of the issue
For a custom field with "Can Edit on Profile: YES" and "Populate Data From Previous Subscription: YES":
### Recurring plans
- Current behavior: When a recurring subscription auto-renews, the new subscription record's fields are auto-populated using data from the user's previous subscription of that plan (not the current profile data).
- Problem with "Synchronize Data: NO": If the user updates their profile (e.g. Organization Name, Department), the change is not reflected in the next auto-renewal — the renewal still uses the old data from the previous subscription.
- Problem with "Synchronize Data: YES": If the user updates their profile, the change overwrites all of the user's past subscription records as well. In our use case, we consider it inappropriate to retroactively overwrite historical subscription data with the profile data current at a later date — we want past subscription records to remain a snapshot of what was true when that subscription was created.
### Non-recurring plans
- Current behavior: When a user manually renews (re-purchases) the same plan, the form is auto-populated using data from the previous subscription.
- Problem with "Synchronize Data: NO": If the user updates their profile, the change is correctly reflected when subscribing to a new/different plan, but not when renewing the same plan — the user has to manually re-enter/correct the fields on the renewal form themselves.
- Problem with "Synchronize Data: YES": Same concern as above — it overwrites all past subscription records, which is not appropriate for our use case.
## Feature request
We'd like to request an additional option, specifically for custom fields where both "Can Edit on Profile: YES" and "Populate Data From Previous Subscription: YES" are set (since this is the only case where this choice would be meaningful — if "Can Edit on Profile" is NO, the user can't change the field via profile at all, and if "Populate Data From Previous Subscription" is NO, there's no auto-populate to begin with):
Add an option to choose the data source used to auto-populate the renewal/new subscription form:
- Source A (current behavior): Use the snapshot of data from the user's previous subscription of that plan.
- Source B (requested):
Use the user's current profile data at the time the new subscription record is created.
Importantly, in either case, existing/past subscription records would remain completely untouched — this is independent from "Synchronize Data," which retroactively overwrites historical records. This request is only about which data source is used to populate a newly created subscription record going forward.
This would let us keep "Synchronize Data: NO" (to preserve historical snapshots) while still ensuring that renewals — both recurring and non-recurring — reflect the user's current profile data instead of stale data from a previous subscription.
I hope it makes sense.
Would this be something you could consider adding in a future update?
Thank you very much for your continued support.
rikao
Topic Author
