The Create application product wizard creates a WHMCS product tied to one application and defines its hosting package, installation behaviour, prices and customer tools. The current application-product workflow uses cPanel with WP Toolkit or Softaculous. Prepare a working server and an active sample account before starting.
IN THIS ARTICLE
01 Complete the product wizard
- Open App Hosting, select App products, then choose Create application product.
- At Application, choose the server group or single server under Accounts are created on. Select Managed WordPress or an application from the server catalogue. Use Show all when the application is outside the initial popular list.
- At Product, enter the name and customer descriptions. Review welcome email, tax, visibility, stock and featured-product choices.
- At Group, select the intended WHMCS product group or create an appropriate group. This affects where customers find the plan.
- At Provisioning, choose the hosting package, feature list where applicable and setup trigger. Resolve each Server check, including every server in a selected group.
- At Domain, decide how the site domain and installation path will be supplied. Avoid a default path that would overwrite an existing website.
- At Pricing, enable the intended currencies and billing cycles, then review recurring and setup charges. Verify any calculated values before saving.
- At App setup, configure automatic installation, failure handling, site count, customer installation permission, HTTPS, language and PHP policy. Review WordPress-specific choices only for WordPress products.
- At Customer tools, choose a starting profile and inspect every enabled tool. At Review, check the full configuration and select Create product.
02 Decide how installation failures affect orders
Install it with the account controls automatic application setup. Hold the order if setup fails changes whether incomplete application setup should block successful provisioning. Choose these together. A plan advertised as ready to use should not silently deliver an empty account after an application failure.
Use a conservative website limit and decide whether Customers can add and delete websites. Staging copies recognised by the installer do not count in the same way as normal installations, so explain both plan limits and staging scope clearly.
03 Verify before accepting live orders
Keep the product hidden while placing a test order. Verify account creation, application installation, the welcome message, client-area layout, customer tools and the price shown on the order and invoice. If a server group is used, test that every eligible server has the selected package and application available.
Inspect the resulting service in the application account list. A browser timeout does not prove installation failed; refresh its state before retrying. Use Continue setup for an existing created account when appropriate. Use WHMCS Create for a pending service whose hosting account has not yet been created.
Common questions
Can different servers in one group use different packages?
The selected provisioning configuration must be usable wherever WHMCS can place the order. Resolve the wizard's checks for every eligible server or separate incompatible servers into a different placement group. A successful catalogue lookup on the sample account does not establish that another server has the same installer and package.
Does a product description enable a tool?
No. Descriptions explain the offer, while application policy, customer tools and provider capabilities control delivery. Compare the final review with the public description so features such as email, Terminal or staging are advertised only when the product can supply them.