Include eligible domains and addons in a hosting renewal

Renew together can put an eligible registered domain and service addons on the hosting renewal invoice. Configure it only after reviewing ownership, billing periods and registrar behaviour. A website's domain name is not automatically a domain registration managed by your WHMCS installation.

01 Configure the product policy

  1. Open Hosting Renewals and Products & policies, then edit the intended product.
  2. Under Domains & addons, enable Allow domain renewal if customers may include an eligible registered domain.
  3. Use Force domain renewal only when including that eligible domain is an intentional product policy. It also enables the corresponding allow option.
  4. Enable Allow addons renewal if eligible active addons may share the invoice. Review Force addons renewal separately.
  5. Save and open a test service with representative domain and addon records.
  6. Review the complete quote, including each item, its amount and renewal period, before confirming.

02 Check what is eligible

Confirm the domain belongs to the same intended customer and is registered through the relevant WHMCS domain record. Verify the registrar module, registration status and supported renewal period. Externally registered domains do not become renewable through WHMCS merely because they point at the hosting service.

Review addon status and billing configuration. A one-time, cancelled or otherwise ineligible addon should not be assumed to follow the same recurring renewal behaviour as the hosting plan.

03 Understand the safety checks

The module reads eligible items again before issuing the invoice and before extending their dates. If an item changed after the customer reviewed it, the workflow can require staff review instead of processing stale assumptions. Investigate that condition against the current records.

Payment and registrar renewal are separate events. Verify that a paid combined invoice produces the expected domain action and resulting expiry date. Do not mark a registrar failure as resolved solely because the invoice shows paid.

What happens when a combined renewal meets an existing unpaid invoice?

Cycle changes that replace an unpaid renewal invoice are restricted. The supplied workflow allows the relevant replacement only under specific conditions, including Mail In Payment and no active payment subscription. Other payment, credit or invoice conditions can require support review.

Compare the old and proposed totals and check for applied funds before cancelling or replacing anything. An external subscription can continue independently of an invoice change.

04 Verify the final result

After settlement, check the service's next due date, each included addon's date, the domain's registrar expiry and the renewal operation status. Preserve the individual error details when only part of a combined operation needs attention.

Sources and further reading

  • 0 Users Found This Useful
  • hosting-suite, domains-dns
Was this answer helpful?

Related Articles

Configure Hosting Suite access rules and verify effective permissions

Hosting Suite access rules add module-specific restrictions to the permissions already granted...

Configure free AI allowances and service usage limits

Free AI allowances and purchased AI credits are different controls. The free allowance permits...

Set safe operating expectations for AI changes and Undo

The Engineers can inspect supported information and propose changes through available tools....

Price paid AI credits and check the protected minimum

Paid AI credits convert model usage into a service balance customers can buy through WHMCS....

Reconcile AI credit purchases, invoices and refunds

AI credit purchases create WHMCS invoices and add credits after successful payment. Use the...