# Custom WHMCS Module Development

> Provisioning, registrar, addon and gateway modules written against the WHMCS module API, delivered as source or encoded.

Custom WHMCS modules built to a written spec: server provisioning, domain registrar, addon and gateway modules for WHMCS 8.13 LTS and PHP 8.1+.

- **Price:** $500 - $2,500
- **Billing:** One-time, fixed scope
- **Category:** Custom Development
- **Quote turnaround:** Fixed-price quote within 24 hours
- **Start a project:** https://whmcspilot.com/start-project
- **Details:** https://whmcspilot.com/services/whmcs-module-development
- **Last updated:** 2026-11-03

## Overview

Custom WHMCS module development is for the moment when no existing module connects WHMCS to the system you sell, or the ones on offer do not fit how your business runs. We write provisioning, registrar, addon and payment gateway modules against the official WHMCS module interfaces, so they keep working through WHMCS updates without core file edits. Most projects land between $500 and $2,500 at a fixed price agreed before coding starts.

## Signs you need a module, not another workaround

- Staff log in to a remote panel after every order to create the account by hand
- A spreadsheet tracks which customer holds which license key or server
- The vendor's WHMCS module has been abandoned and fails on PHP 8.1
- Suspensions for unpaid invoices only happen when someone remembers

## Module types and what each one does

### Provisioning (server) modules

These tie a WHMCS product to an outside platform: a hosting panel, cloud API, game server panel, VPN service, software license server or IPTV panel. A complete module implements CreateAccount, SuspendAccount, UnsuspendAccount, TerminateAccount, ChangePackage and ChangePassword, plus TestConnection for the server setup screen. Optional extras include a client-area tab with live data, single sign-on into the remote panel, admin buttons for one-off actions, and usage metrics that feed WHMCS usage billing.

### Registrar modules

For selling domains through a registrar WHMCS does not support. That covers register, transfer and renew; nameserver and contact updates; EPP code retrieval; availability checks for the domain search; and the Sync and TransferSync functions that keep expiry dates and transfer statuses correct in WHMCS.

### Addon modules

Self-contained features with their own admin page, client-area page, database tables and settings, such as an internal dashboard, a reseller tool or a paid customer feature. Addons can also ship hooks that react to WHMCS events like order acceptance or invoice payment.

### Payment gateway modules

Gateways have their own testing needs, so they are covered on the [payment gateway integration](/services/whmcs-payment-gateway-integration) page.

## How we write them

- PHP 8.1+ and WHMCS 8.13 LTS as the baseline, with your exact version tested if it differs
- Database access through the WHMCS Capsule layer, with tables created and upgraded by the module itself
- Each remote API call recorded with logModuleCall, so the module log shows request and response
- Client-area output in Smarty templates that inherit your theme, and language files for customer-facing text
- No changes to WHMCS core files, so updates cannot overwrite the work
- Failure handling written down: what the customer sees and what admins are told when the remote API is down
- Delivered as readable source code or ionCube-encoded, as stated in the quote

## Spec first, then code

Before any code, you get a short specification: which WHMCS events trigger which remote calls, what customers see, what admins can do, and how errors are handled. The fixed price and delivery date are based on that document. Changes after you approve it are quoted as add-ons, so the original price and date stay valid.

From you we need the remote system's API documentation and sandbox credentials, the list of products the module will power, and access to a staging WHMCS, or permission for us to set one up.

## Pricing by scope

ScopePriceAddon with a single admin page, or a provisioning module covering the core lifecycleFrom $500Provisioning with a client-area panel, SSO and upgrades, or a full registrar moduleFixed quote within the rangeSeveral connected parts: addon, provisioning module, hooks and admin reportsUp to $2,500Larger or open-ended buildsMilestone pricing, or 30 hours/month for $1,650

## Timeline

A simple module typically ships one to two weeks after the spec is approved; larger builds take three to five weeks. Slow sandbox access from the remote provider is the most frequent cause of delay, so we ask for credentials before kickoff.

## Testing before delivery

Every module function is exercised on staging against the real remote sandbox: a full order, suspension, unsuspension, upgrade, password change and termination for provisioning modules, or registration, transfer, renewal and sync for registrar modules. You receive the test checklist with the code, so your team can repeat it after future WHMCS updates.

## Before you commission one

Small changes to WHMCS behavior often need only a hook rather than a whole module; see [custom hooks development](/services/whmcs-hooks-development). Connecting WHMCS to a CRM or accounting tool, rather than provisioning a product, is [WHMCS API integration](/services/whmcs-api-integration). Browsing our [management modules](/modules/management) first may save you a build. When you are ready, describe the system you want connected on the [project form](/start-project).

## What's included

- Written specification approved before development starts
- Provisioning modules with create, suspend, unsuspend, terminate, change package and change password
- Registrar modules with register, transfer, renew, nameservers, EPP codes and sync
- Addon modules with admin pages, client-area pages and their own database tables
- Client-area tabs, single sign-on and admin custom buttons on request
- Usage metrics reported to WHMCS usage billing
- Every API call logged through logModuleCall
- Built for WHMCS 8.13 LTS and PHP 8.1+ with no core file edits
- Source code or ionCube-encoded delivery as agreed
- Test checklist delivered with the module

## Business outcomes

- Sell a product WHMCS could not automate before
- Price and delivery date are fixed against a document you approved
- WHMCS updates do not wipe out the work, since core files stay untouched
- Your team can troubleshoot from the module log instead of guessing
- Future developers can pick up the code with the spec and test checklist

## Frequently asked questions

### Will I receive the source code?

If the quote specifies open source delivery, yes, you get readable PHP you can modify. With ionCube-encoded delivery you receive the encoded module, and the quote states which applies.

### Will the module keep working after WHMCS updates?

It is built to, because it only uses documented module interfaces and leaves core files alone. Major WHMCS releases can still change behavior, so retest after big upgrades using the checklist we provide.

### Can you finish a module another developer started?

Often, yes. We read the existing code before quoting and tell you whether finishing or rewriting it is cheaper.

### Which WHMCS and PHP versions do you build for?

WHMCS 8.13 LTS on PHP 8.1 or newer by default. Older installs can be targeted on request, though upgrading first is usually the better investment.

### How are larger module projects paid?

Up to $5,000 it is half at kickoff and half on delivery. Above $5,000 the price is split into three milestones tied to working parts of the module.

### Can a custom module bill by usage?

Yes. Provisioning modules can report metrics such as bandwidth, disk or API calls to WHMCS usage billing, which then invoices per unit.
