The WHMCS domain-sync task checks supported registrar modules for current registration and transfer information. Use it to keep billing records aligned with the registrar, while reviewing whether automatic due-date changes suit your billing policy.
IN THIS ARTICLE
01 Configure synchronisation
- Confirm that the domain's assigned registrar module supports synchronisation and has working credentials.
- Open Automation Settings and enable Domain Sync.
- Review the expiry-sync and pending-transfer frequencies.
- Decide whether Sync Next Due Date should update billing dates. If enabled, set its days-before-expiry offset to the approved collection lead time; automatic sync can preserve an intentionally earlier billing date.
- Consider Domain Sync Notify Only when first reviewing an existing portfolio. Inspect the proposed changes before allowing updates.
- Confirm that the system cron runs and review the resulting domain-sync report.
02 Interpret the result
For supported active domains, sync compares the registrar's expiry information with WHMCS. Pending registrations and transfers can move to an active state when the provider confirms completion. The exact transfer-failure and transferred-away behavior depends on the registrar module.
Portfolio checks occur in batches. A large account may need multiple normal runs before every active domain has been revisited. Do not repeatedly force the task merely because one recently changed domain has not appeared in the first report.
What should I check when registrar and WHMCS domain records differ?
Compare the domain at the actual registrar account with the WHMCS domain record. Check the assigned module, domain spelling, credentials and provider API response. An unsupported-sync error requires a supported module or a manual reconciliation process, not a change to the domain's expiry date without evidence.
If a domain was renewed manually at the registrar, review both its expiry date and the customer's paid-through billing arrangement. Aligning the expiry date does not itself establish that the customer paid for the added term.
03 Keep renewal monitoring independent
Review upcoming expiries and failed sync reports routinely. A successful cron invocation does not prove every registrar responded. Retain unresolved domains in an operational worklist until their registry and billing states are understood.