Hello,

currently any change done to subscriptions using customize will result in causing the subscription to lock and need resyncing. The only two buttons to save customizations are "apply and lock" and "update and lock".

The change you make might affect just one area like the renewal date however the whole subscription is marked as locked. If you unlock and sync all customizations made through other areas of the subscription are removed, including custom php directives, php memory_limit, and other configuration settings that are important to keep so that the customer's subscription will keep their websites working.

As it currently stands, after first modification of the renewal date for example we end up having all subscriptions locked and unsynced therefore we can't automate bulk changes in subscription plans like increasing HDD space, or mailbox limits.

If we manually resync the subscriptions, we lose all customizations that are mission critical for the customers. So we either have to work through every subscription one by one adjusting or we have to work through every subscription and notice all specific directives that are important to the customer and then reimplement them after sync.

That's tedious,time consuming and prone to errors.

Simple example,
1. create a service plan using 256MB as memorylimit for php and assign it to a subscription
2. go to the subscription -> domain panel
3. click on php settings icon
4. add a php directive like memorylimit = 1G and save
4a. Go to subscription and click on customize
1. Change renewal date
2. Hit update and lock
3. Hit unlock and sync
The result is the directive memory_limit =1G is lost.
4b. Go to service plan and adjust mailboxes from e.g. 5 to 6
1. Sync plan with subscriptions
Result is the directive is lost.

This effectively kills any versatility in the service plans for mass changes and is potentially dangerous for the customers as it can cause things to break.

In my opinion at the very least each service plan tab as we define it

Resource
Permissions
Hosting Parameters
PHP Settings
Applications

should have a separate lock. That way when we change something in the PHP settings tab, only the php settings are marked as to need resyncing. When we change something in the resources, only resources will resync etc etc.

This would still be prone to errors when editing php settings of course but at least not when you're adjusting resources.
Ideally a list of all changes to each subscription if you decide to sync again should appear too and ask for confirmation. That way at least you can note what to fix after plesk breaks it.