Domain Management Package Setup

[lanquest]

Hi Fellow WHMCS Users,

 

We are new users to WHMCS but have migrated from MB recently. The areas we are pointing out here, we know can be configured and have been configured in the MB application. What we are looking for, are suggestions in how we can maintain or improve the way we have currently setup this package within the WHMCS system.

 

We have a client who has purchased one of our Domain Management Packages.

 

The domains for this package have all been transferred to our ENOM account, pointing to our nameservers and should cost £25 per year. THe domains are to be billed once per year, every year unless the client chooses not to renew 30 days before they are due to billed.

 

We have set this up by creating a Product/Package/Service, which for the moment let's say has no price or cost associated to it.

 

Since we have already transferred approx 230 of their domains into our ENOM account and already have those domains active within our WHM/CPanel. We are manually entering these domains as transfers using the instructions you have provided.

Manual Existing Domain Entry document - http://wiki.whmcs.com/Importing_Data#Manual_Existing_Domain_Entry.

 

During this process we have noticed that the standard domain costs are being show at the same rate as a Standard domain package. Although this doesn't matter for now as we are manually adding the domains to the client account and can amend this later.

 

Our questions and concerns are as follows

 

1. As mentioned, the client is charged £25 per year for each top TLD domain, regardless of whether the domain is a 1 or 2 year min domain. We have manually adjusted the domains registrations and entered 1 year to the Registration Period field. £25.00 to the First Payment Amount field and £25.00 to the Recurring Amount field.

 

Once the domains have synchronised the Registration, Expiry and Next Due Dates with the domains on our ENOM account, when does the WHMCS system bill the client if we changed just the Next Due Date? Will they all be billed on separate invoices?

 

How would you advise us to setup the billing account so that all the domains are billied once per year for all the domains at the same time and date?..

 

The client in question is Client Id: 33

 

2. Once we hand over the account to the client. It seems that we have one major problem when or if they want to purchase a domain. The client would not see the cost the domains at the price for that package/service they are on.

 

3. There are various buttons available to the client when they log into their client area. Can the following buttons be hidden or removed on a per client or product/service? We have only highlighted the ones we are most concerned about.

 

My Domains - View Details

From this screen the client can see the following buttons. Renew Domain & Register Nameservers. Can these be hidden?

 

Renew Domain screen - shows the domain prices again at the standard hosting package rate.

 

Register Nameservers - the clients domains are on our nameservers. Would registering a nameserver on the ENOM system work?

 

What we are looking for, are suggestions in how we can maintain this package in the way it was intended.

 

Many thanks

[chickendippers]

3. Yes, simply remove the buttons from the appropriate template file. In this case clientareadomaindetails.tpl

[lanquest]

I had created a support ticket in relation to this thread and received the following response.

 

Domain billing is based on the next due date so clients will be invoiced for that date when due. If multiple domains are due on the same date, they will be put on a single invoice.

 

You can remove any buttons you don't want clients seeing on the domains management page from the template file clientareadomaindetails.tpl

 

Custom pricing for domains based on a package a user has is not possible.

 

But there is one problem. It seems that the cron refreshes the Next Due Date under the client domain tab.

Also the Next Due Date and the Expiry Dates are the same. Sure enough I changed the Next Due Date on over 200 domains and then the cron came along and changed them

 

I'm beginning to thing this was not it's purpose for the Next Due Date to be the domains Next Due Date/ Expiry date.

 

I hope someone can help as the invoices will be created on that date. I just had an invoice created for over £1600 before the cron as the Next Due Date were the same.

 

So it confirms that what the support ticket reply said was correct. But I believe the cron is changing the Next Due Date field thinking it is the Expiry date. Surly it should default to the Registration Period set for that domain but also left for manual intervention.

[lanquest]

I hope this helps someone else out there.

 

Here's is the answer

So simple

 

It's a setting you can turn on/off. You have told WHMCS to sync the next due date in Config > Domain Registrars > Enom > SyncNextDueDate. If you no longer want that, just untick the box again and save then it will just sync the expiry date.

 

SyncNextDueDate Tick this box if you want the expiry date sync script to update the expiry and next due dates (cron must be configured)

 

Thanks Matt.