Use the supported WHMCS service-change workflow when a customer needs a different Droplet plan or more attached storage. Review the resource change independently from the resulting billing price or package label.

Check the target before offering it

A plan resize needs the server to power off; the module handles the power sequence. Allow for downtime that depends on the operation rather than promising a fixed short interruption. Arrange maintenance and take an appropriate backup before proceeding. DigitalOcean’s resize documentation explains the provider constraints, including that a Droplet disk cannot be reduced.

Review the target plan’s availability in the existing region and its disk requirement. Do not offer a smaller-disk target as a routine downgrade. Additional storage can grow through the module but cannot be reduced in place; the guest filesystem may need the server administrator to extend it before applications use the added capacity.

Configure supported changes

1. Review the product’s Upgrades configuration and the target products/options you intend to allow.
2. Enable Configurable Options on that tab if customers should change the exposed plan and extras.
3. Check the source and target module settings and server group before accepting an upgrade request.
4. Use WHMCS’s normal Upgrade/Downgrade flow for the intended service change.

Do not assume that editing the offering’s default plan resized existing servers. Check the affected service and its module operation.

Follow the result

Read Activity during the change and allow the existing request to finish. After completion, confirm the actual plan, memory, disk and running state, then check the application. Newly added storage can need a finishing job after the server is running.

If backups or a dedicated IP were bought as part of the change, check those separately rather than treating the main plan label as proof that every extra finished.

If the change is refused or uncertain

Read the specific reason: a smaller disk, unavailable plan, provider permission or unfinished prior operation needs diagnosis. Do not delete and recreate a live server to bypass a refused resize. Compare the billed offering, original operation result and actual server state before deciding whether another action is appropriate.

See the PD DigitalOcean Droplets WHMCS guide for related tasks, or explore the module.