Panel & Tooling
WHMCS: the cron job that runs a hosting business
Everything automatic about a hosting company happens in one scheduled task, and almost every strange billing fault traces back to it.
The short answer
WHMCS is the billing and automation platform most of the hosting trade runs on: orders, payments, invoicing, provisioning, suspension, termination and support tickets in one application, with an API connection down to WHM.
Its heartbeat is a scheduled task. The cron run is what generates invoices, sends reminders, charges cards, suspends the overdue and terminates the abandoned — which is why a silent cron produces a business that looks fine and quietly stops billing anyone.
A standalone WHMCS licence is sold separately, and our reseller accounts are ready to wire straight into it.
By the HostingFast team · Reviewed 12 August 2026
0
Terms defined here
100+
Typical read time
Real
English, no hand-waving
Free
Engineers on shift
The loop it closes is commercial rather than technical. An order arrives, payment is taken, WHMCS calls WHM over the API to create the account, the welcome email goes out, and the next invoice is scheduled — all without anyone being awake. Every step of that is a module doing one job with a log entry behind it.
For anyone operating it, the useful mental model is a queue of dated actions rather than a website. Invoices due tomorrow, reminders due today, suspensions overdue by three days: the cron walks that list once per run and acts on whatever has come due.
What the cron actually does each run
Generates invoices for services approaching renewal, sends the reminder sequence, attempts payment on stored methods, applies late fees, suspends accounts past the grace period, terminates the long-abandoned, prunes logs and fires whatever hooks you have added. Miss a day and none of that happens; miss a week and the recovery is manual.
Check it the way you would check any scheduled job: look at the last successful run timestamp in the admin area, and set an external alert if it goes stale. A billing system whose cron failed silently is the most expensive kind of quiet outage there is.
The provisioning path, and where it breaks
WHMCS holds the products; WHM holds the accounts. On a successful order, WHMCS calls the server module with a package name and the client details, and WHM creates the cPanel account. Two things account for most failures: an API credential that has expired, and a package name in WHMCS that does not match the one defined in WHM.
Test the whole path end to end before your first real customer, using a free order or a zero-value invoice. The time to discover that provisioning is broken is not 2am on the day someone pays you.
When it is worth running at all
Roughly when billing admin starts costing an hour or two a month, which for most people arrives around ten clients. Below that, manual invoicing copes. Above it, the licence pays for itself in renewals that would otherwise have been missed and in the evenings you get back.
There is a second threshold worth naming: the point at which you need clients to serve themselves. A client area where somebody can pay an invoice, open a ticket and see their own services removes a whole category of interruption from your week.
How it fits with what we sell
Our reseller plans give you WHM with private nameservers, per-client limits and daily backups, ready to wire into WHMCS over the API. A standalone WHMCS licence is sold separately if you do not already hold one, and reseller pricing is a plan fee plus a charge per active user.
Read WHM for the tier WHMCS talks to, Cron Job for the mechanism underneath the automation, and Reseller Hosting for the accounts it will be provisioning.
Automation is a scheduled task, so watch the task
Every automatic thing a hosting business does happens inside one cron run. This entry describes what that run performs, how to confirm it is happening, and which two misconfigurations cause most provisioning failures.
Reseller accounts here are ready to wire straight into WHMCS, and a standalone licence is sold separately.
- What each cron run performs
- The two provisioning failures
- Monitor the last successful run
- Around ten clients is the threshold
Why HostingFast
Standard on every plan
WHM ready for the API
Reseller accounts are set up to be driven by billing software rather than administered by hand.
A standalone licence, sold separately
Buy one if you do not already hold a licence, so the billing layer stays a known monthly line.
Private nameservers
Provisioned accounts land on delegation carrying your own domain rather than ours.
Per-client limits you define
The package your billing system references is one you wrote, with resource limits you chose.
Daily backups across the estate
Every account your automation creates is backed up daily, without another moving part to configure.
Support for you and your clients
Engineers on shift at any hour behind your first line, with a one-hour target when a site is down.
Quick Start
From order to online
- 1
Match package names on both sides
The product in WHMCS must reference a package that exists in WHM, spelled identically. That mismatch causes most first-day provisioning failures.
- 2
Place a test order end to end
Order, pay, provision, welcome email, first invoice. Watch each step complete before a paying customer runs it for you.
- 3
Alert on a stale cron
Check the last successful run timestamp, then monitor it externally. A silent scheduler is an outage that bills nobody and tells no one.
Built In
Loaded onto every plan
- WHM on every reseller tier, ready for API provisioning
- Private nameservers carrying your own brand
- Packages and per-client limits you define yourself
- Overselling enabled from day one
- Softaculous inside every account you create
- Free SSL on every site you host
- Daily backups across every client account
- Imunify360 shielding every client site
- No setup fee on reseller orders
- 24/7 support behind you and your clients
Frequently Asked
What people ask us most often
What happens if the WHMCS cron stops running?
Everything automatic stops silently. No invoices are generated, no reminders are sent, no cards are charged, nothing is suspended and nothing is terminated. The admin area still works perfectly, which is what makes it dangerous: the failure looks like an unusually quiet month until somebody checks the last successful run.
Why did an order take payment but never provision the account?
Nine times out of ten it is one of two things: expired or incorrect API credentials for the server, or a package name in the WHMCS product that does not match the package defined in WHM. Both are visible in the module log, and both are worth testing before your first real order.
At what point is billing software worth the licence?
When manual invoicing costs you an hour or two a month, which usually arrives around ten clients, or when clients start needing to serve themselves. Below that threshold a spreadsheet and a payment link genuinely cope; above it the missed renewals cost more than the licence.
Does WHMCS handle support tickets as well as billing?
Yes, and the value is the linkage rather than the ticket system itself. A message arrives already attached to the client, their services and their invoice history, so nobody has to ask which account it refers to. Plenty of resellers run the entire client relationship from that one screen.
Keep reading
cPanel
The per-account panel your provisioning creates, and what your clients will actually be using.
WHM (WebHost Manager)
The server-level tier your billing system drives over the API, and where its limits are written.
Best WHMCS Hosting
WHMCS hosting compared on the things that matter once automation is running your renewals.
VPS Hosting
KVM virtual servers with root access, DDoS filtering and a flat monthly price.
Domain Names
Register and transfer names, with the first year included on an annual hosting plan.
Changing hosts? Run through our checklist first.
A straightforward sequence for a switch your visitors never feel: which files move first, how to shift email across without losing a single message, the right moment to repoint DNS, and the two mistakes behind almost all the downtime we get asked to rescue.
Let the cron do the admin.
Reseller accounts ready to wire into WHMCS over the API, with private nameservers and a standalone licence available if you need one.
View VPS Hosting plans