Checklist
- Configure the cPanel server under WHMCS server settings.
- Use the correct hostname, IP, API credentials, and SSL connection.
- Create a server group if multiple servers are used.
- Set the product module to cPanel.
- Match the WHM package name exactly.
- Choose automatic setup timing based on fraud and payment policy.
- Test ordering, invoice payment, account creation, suspension, unsuspension, and termination.
Good practice
Use a test product before selling publicly. Keep module logs private because they can contain sensitive operational details.
Detailed setup notes
WHMCS provisioning depends on the server module, product module settings, server credentials, package name, and automation cron. For cPanel products, the package name in WHMCS must match the WHM package name.
Test cases
- New order pending.
- Invoice paid.
- Account created.
- Welcome email sent.
- Service suspended for nonpayment.
- Service unsuspended after payment.
- Package upgrade/downgrade.
- Termination on a test account only.
Logs to review
Use the WHMCS module log during testing, then disable it when done because logs can contain sensitive API details.
Reference links
- WHMCS cPanel Server Module: https://docs.whmcs.com/8-13/provisioning-modules/cpanel/
Reseller operations
Resellers should keep packages simple, document support boundaries, monitor usage, and avoid selling more than they can support. Clear onboarding and fast escalation to the upstream provider are part of the product.
Quick support handoff
If this article does not solve the issue, open a support ticket with the domain, service name, exact error, time the problem started, and what changed recently.
