WHMCS addon for.ro domain registry / auction operations

Overview

A WHMCS addon module for managing .ro domain registry / auction operations inside a hosting-and-billing platform. It extends WHMCS with both client- and admin-facing interfaces and ties into the platform’s hook system to automate domain workflows.

Why It Exists

WHMCS is the billing and automation hub many registrars and hosts run on, but .ro registry specifics, and domain-auction handling, aren’t covered out of the box. This module bridges that gap so domain operations live inside the same platform that handles clients, invoicing and provisioning.

What We Built

A WHMCS addon module (navdomains.php) following the official addon SDK structure: config/activation definitions, an admin output area and a client area, with module functions namespaced by the module name. A lib/Client layer (a ClientDispatcher under a WHMCS\Module\Addon\NavDomains\Client namespace) routes client-area requests, a hooks.php registers WHMCS hooks for billing/automation events, and a templates/ directory holds the module’s views. Database access uses WHMCS’s bundled Laravel Capsule (WHMCS\Database\Capsule).

Technologies & Approach

Built natively on the WHMCS addon-module API so it inherits the platform’s auth, billing, client management and hook lifecycle rather than re-implementing them. Capsule (Illuminate Database) provides query access to the WHMCS schema; the client dispatcher and templates keep request handling and presentation cleanly separated.

Outcome / Impact

A registry/auction tooling module embedded directly in a WHMCS deployment, giving staff and clients domain-management surfaces within their existing billing platform. It captures early registry/registrar integration work on a mainstream hosting-automation stack.

Capabilities Demonstrated

• WHMCS addon module development (admin + client areas, config, activation)
• Hook-based automation within a billing/provisioning platform
• Registry/registrar domain workflows for the .ro ccTLD
• Clean dispatcher/template separation using the WHMCS SDK conventions