This guide is for resellers who administer their own WHMCS installation. A WHMCS product defines what a customer can order; its cPanel module settings connect that product to a real WHM package and an eligible server.
IN THIS ARTICLE
Check access and requirements
First connect the reseller’s WHM server in WHMCS and create the intended WHM package. Confirm the reseller has permission and capacity to create the package’s accounts. Use a restricted staging installation for tests that must remain private. A hidden product is removed from normal catalogue listings but can still be ordered through a direct link, so hiding alone does not prevent customer orders.
01 Add a cPanel hosting product to your own WHMCS
- In the WHMCS administration area, open System Settings > Products/Services. Create or select the product group, then create a Shared Hosting product.
- Set its name, pricing, tax and billing behaviour deliberately. In Module Settings, choose cPanel and the server group that contains the correct reseller connection.
- Select the exact WHM Package Name, including a reseller prefix if WHM uses one. Do not invent a package name or assume a similarly named package on another server is equivalent.
- Choose when account creation should run. Keep automation controlled during testing, then save and place a test order using a domain you control.
- Inspect the created hosting account and the service’s assigned server before making the product visible. Verify the resulting limits and access, not just the order confirmation.
02 Example: match the ordered product to the actual WHM package
Suppose WHM lists a package named reseller_business on the server assigned to your reseller account. In the WHMCS product, choose the cPanel module, select the server group containing that account and use the exact package name returned by WHM. The public product can have a friendly name such as Business Hosting; it does not have to be identical to the technical package name.
Place one controlled test order and compare the resulting WHM account package and limits with the product definition.
Expected result: the service lands on the correct server and receives the intended package instead of a similarly named package owned by another reseller.
Confirm the expected result
A successful test should create one intended account with the right package, produce usable login access and leave a clear service record in WHMCS.
What should I check when WHMCS cannot create the hosting account?
If provisioning fails, read the module error and Module Log with secrets redacted. Check API permissions, server-group membership, package ownership and capacity. Avoid repeated Create calls when WHM may already contain an account; reconcile the existing service first.
Related articles
Sources and further reading
For visibility behaviour, see WHMCS: Hide or Retire Products.