Skip to main content

The Renewal Calendar

WHMCS vs manual billing — Your spreadsheet is not a billing system. It is a renewal calendar with no alarms.

Client billing currently runs on a spreadsheet and a good memory, and the risk is not the invoice you send late — it is the client domain whose expiry date was never in the spreadsheet at all, and which nobody is watching this week.

The short answer

Stay manual while the list is under about ten clients, then move to WHMCS, since recovered renewals alone tend to cover the licence and reseller plans here include one — and note that the renewals worth recovering most are the domain ones, because those have a registry clock behind them rather than a polite reminder.

Below: the two clocks a reseller is actually running, what happens on a name that slips past the second one, and which parts of the job automation genuinely takes away.

By the Hosting & Domains team · Reviewed 24 August 2026

99.9%

Uptime we aim at

24/7

People, not queues

Free

Certificate, every plan

NVMe

Disks, all tiers

This brief is for resellers whose client billing currently runs on a spreadsheet and a good memory. It treats billing as calendar management, because for anybody holding client domains that is precisely what it is.

Renewal dates are where reseller revenue quietly disappears. Manual systems miss them more often than owners believe, and the first automated billing run routinely turns up invoices that should have gone out months ago.

One of these two mistakes is recoverable

Send a hosting invoice a month late and you have an awkward email to write. Nothing has been lost that a conversation cannot repair.

Miss a domain renewal and the registry takes over. Expiry is followed by a grace period of around thirty days at the ordinary renewal price, then redemption at several times that, then public auction. Every stage costs more and is less certain than the renewal that would have avoided it.

So the two lines on your spreadsheet are not equivalent, even though they look identical. One is a receivable. The other is an asset with a countdown on it, usually somebody else's asset, held in your account.

Two clocks that do not agree

Your billing cycle and the registry's expiry date drift apart the moment anything unusual happens — a mid-term transfer in that added a year, a name bought for two years while the hosting is annual, a client who paid late once.

Once they have drifted, an invoice going out on your cycle is no longer evidence that the name is safe. That is the specific failure this whole decision is about, and it is invisible in a spreadsheet because a spreadsheet holds whatever you last typed into it.

The only reliable version reads the expiry date from the registrar rather than from your own records, and flags the difference. Automation earns its licence here, before it has issued a single invoice.

What automation actually takes off your desk

The whole lifecycle: signup, provisioning, invoice generation, card capture, dunning, suspension of overdue accounts and termination of cancelled ones, with a customer portal and ticket desk besides. You set the rules once and they are applied at three in the morning unasked.

For domains specifically, the part that matters is the sequence of reminders that runs whether or not you are having a busy month, and the record of expiry dates that does not depend on anybody remembering to update a cell.

What it does not do is decide policy. Whether you auto-renew client names by default, and who is the registrant, are still your decisions — automation only makes them happen on time.

The verdict, unhedged

Staying manual while the list is under about ten clients, then moving to WHMCS, since recovered renewals alone tend to cover the licence and reseller plans here include one.

In concrete terms that is our WHMCS License option: one flat rate carrying the essentials (SSL, migration, copies, mail) this market prefers to bill separately, with in-place upgrades ready when the work picks up.

Mailboxes at your own name are part of the plan — mail is included, not sold back to you at the checkout.

Check every word of this yourself. Ask any supplier how expiry dates are surfaced, whether auto-renew is on by default, and how quickly an auth code is issued when a client leaves. Those three answers tell you what your calendar will look like.

The company is Azaanex Inc., federally incorporated in Canada, on the public register.

Then let real use decide. Two working weeks inside the money-back window beats every review roundup ever written, and note that reseller plans carry seven days rather than thirty.

A reseller running an entire hosting brand out of one account

Why we can afford to answer straight

We sell the licence and we hold the names, so the advice is not disinterested. It is, however, the advice we would give a reseller who bought neither: watch the expiry dates first and the invoices second.

Hosted somewhere else already? We move the whole site at no charge, usually within 24 hours, and it goes on answering visitors throughout.

  • Expiry dates read from the registrar, not a spreadsheet
  • Auto-renew as a toggle, on or off, your call
  • Auth codes issued on request when a client leaves
  • Renewal figures published, not footnoted

Why Hosting & Domains

Standard on every plan

A refund without an argument

If we are not the fit, leaving is one request rather than a negotiation — which is why we invite the test.

Expiry dates you can actually see

Every name in the account with its real registry date shown, rather than the date somebody last typed into a cell.

One rate, published in the open

What you order at is what you renew at — the only comparison that counts is one we win by default.

The verdict, turned into an order

The WHMCS License plan is this page's conclusion in product form — one rate, essentials inside, upgradeable in place.

Auto-renew under your control

A toggle in the account rather than a phone call, so you set the default policy for client names and it stays set.

Support you can test before paying

Put a hard question to us before you pay — how a host behaves pre-sale is the best it will ever treat you.

Quick Start

Order placed to site online

  1. 1

    Separate names from services in the ledger

    Two columns, two risk profiles. A late invoice is a conversation; a lapsed registration runs grace, redemption and auction whether or not you meant it.

  2. 2

    Reconcile against the registrar, not your notes

    Pull the real expiry dates and compare them with your billing cycle. The gaps you find are the case for automation, already quantified.

  3. 3

    Set the auto-renew policy once, in writing

    On or off by default, and who the registrant is. Decide it as policy rather than case by case, then let the system apply it at three in the morning.

Built In

Fitted to every plan

  • Registry expiry dates shown against every name in the account
  • Auto-renew as a toggle, with no telephone call to change it
  • Auth codes issued on request, with no retention script
  • A renewal figure identical to the one you registered at
  • cPanel, which is what most of the industry already runs
  • 99.9% uptime as the target, watched around the clock
  • Webmail in the browser plus IMAP, POP and SMTP for any client
  • WordPress and 400+ further applications installed in one click
  • Staging copies for trying a change before it goes live
  • Free SSL on every plan, reissued before the old one lapses

Frequently Asked

Questions we field again and again

Why is a missed domain renewal worse than a missed invoice?

Because a registry is enforcing it rather than a person. Grace runs about thirty days at the ordinary price, redemption after that costs several times more, and once the name reaches auction anybody may take it. No conversation reverses that.

How do my billing dates drift from the real expiry dates?

A transfer in that added a year, a two-year registration against annual hosting, or one client who paid late. After any of those, an invoice going out on your cycle is no longer evidence the name is safe.

Should I auto-renew client domains by default?

In most books, yes, with the policy written down and the client told. The alternative is relying on a reminder reaching somebody who is on holiday. Decide it as policy once rather than name by name.

What happens to client names if I stop reselling?

They move. Lift the lock, issue the auth code, and let each client transfer to the registrar of their choosing — most endings add a full extra year to the term when the transfer lands, so nobody loses time in the process.

Keep reading

  • WHMCS License

    Automate billing, provisioning and renewals for hosting and domain clients of your own.

  • Ecommerce Hosting

    Quick, well-defended foundations for online stores on any platform.

Changing provider? Work through this checklist beforehand.

A straightforward running order for a migration your visitors never spot: which files travel first, how to bring the mail across without dropping a single message, the right moment to repoint DNS, and the two errors that sit behind almost every outage we get called in to fix.

You get the checklist, followed now and then by a note on keeping a site responsive. Unsubscribe whenever you want; the privacy policy covers the rest.

Automate the calendar, not just the invoice.

Real expiry dates in the account, auto-renew you control, and auth codes issued the day a client asks.

View WHMCS License plans