Enscale - WHMCS Module - Upgrades, Downgrades & Billing
On this page
When a customer changes their plan or add-ons, it flows through WHMCS's standard upgrade process — which keeps your retail invoicing correct and charges you only the wholesale difference.
How a change is billed
The customer changes their package or configurable options (or uses an "Upgrade" button) in your WHMCS.
WHMCS invoices them for the change at your retail prices, as usual.
On payment, the module applies the change with us and charges your credit for the wholesale difference.
Proration
Upgrades charge only the prorated extra for the remaining days of the current period; full price applies from the next renewal.
Downgrades aren't refunded for the current period — they simply re-price future renewals lower.
Proration uses the actual calendar period, so it's accurate across different month lengths.
If your credit can't cover an upgrade's prorated charge, the change is blocked before it's applied — top up and retry.
Storage & resource changes (Cloud Servers)
Disk and add-on storage can be increased via an upgrade; the data volume is resized in place.
Storage reductions aren't processed automatically (to protect data) — contact us if a customer needs to shrink storage.
Additional IPs and licences adjust to match the new configuration.
Route plan/resource changes through WHMCS's upgrade flow — not by hand-editing a service. That's what keeps your customer's invoice and your wholesale charge in step. The in-panel "Upgrade" buttons already point there (and you can hide them — see Cloud Server controls).
If something doesn't fully apply
The spec change always takes effect first; occasionally a paid add-on (e.g. extra storage on a busy server) needs a moment or manual attention. When that happens it's flagged to Brixly's team rather than silently charged — you don't need to chase it.
Was this article helpful?