Enable Hosting Suite renewals on a compatible WHMCS installation

1. Confirm your installed WHMCS version, Hosting Suite version and current vendor support arrangements. Check all relevant compatibility requirements before changing either platform.
2. Back up the WHMCS database and application files and verify that your normal cron and payment processing are healthy.
3. Choose a small recurring test product with clear pricing and no unresolved billing exceptions.
4. Enable the Renewal engine, then open Hosting Renewals and Products & policies.
5. Open the test product and enable its renewal configuration. Review the allowed cycles, customer controls, reminders and domain or addon options before saving.
6. Open eligible test services and inspect Renewal studio to confirm their billing ownership and settings.

Active and suspended recurring services on an enabled product can connect when opened or during normal cron processing. Connecting does not automatically change their individual automatic-renewal preference.

A service with an unpaid native WHMCS invoice or a pending cancellation request is deferred until that condition is resolved. Do not cancel an invoice simply to force connection without checking what it represents and whether payment or credit has already been applied.

Review a customer renewal quote and confirm its period, total, tax and future due date. Issue a controlled invoice and verify that it appears in WHMCS with the expected ownership. Complete a test payment through an appropriate test arrangement and check that the renewal settles once.

Confirm the next due date, billing cycle and any eligible domain or addon effects after settlement. Creating an invoice is not the same as receiving payment, and turning automatic renewal on is not a guarantee that a gateway will collect funds.

Enable additional products only after the test proves the expected behaviour. Monitor open renewals, payment failures and service connection errors in the renewal administration screens.

Before deactivation or a platform change, use the supported billing handoff procedure for connected services. Simply switching off a feature does not resolve open invoices, recurring discounts or ownership of future billing. Keep an internal record of which system invoices each service throughout the transition.

For each test service, record its original due date, current cycle, recurring amount and invoice ownership. Compare those values with the issued quote and the final paid settlement. Include at least one service whose automatic-renewal preference is off so your team can see that connection and preference are separate.

Keep a deferred service with an unresolved native invoice out of the first rollout until its normal billing is reconciled. Do not accelerate deployment by deleting that history. When the product passes testing, document the approved policy and the person responsible for daily review of exceptions. This gives support a concrete reference when a customer later questions a renewal amount or date.

• Configure renewal permissions and billing cycles for a product
• Investigate and repair a renewal that needs review
• Return a service from Hosting Suite renewals to WHMCS billing
• Configure and verify the WHMCS cron for Hosting Suite

• WHMCS billing logic
• WHMCS: setting up the system cron