Feature Requests
Share ideas, discuss and vote on requests from other users in community
 
This object is in archive! 

Exclude free domains from 'Sync Domain Due Dates'

Tyler shared this idea 7 years ago
Under Consideration

The 'Sync Domain Due Dates' with expiration date is a great idea, however domains that are free (that come with their hosting package) can't use this feature, obviously.

Therefore, people who have free domain names aren't able to use this feature. You should be able to use this feature and check that it shouldn't affect 'free domains'

Comments (8)

photo
1

Hi there, can you please explain why it shouldn't affect free domains?

photo
1

cenourinha wrote:

Hi there, can you please explain why it shouldn't affect free domains?
Free domains have to have the same due date as hosting packages, or else they won't be renewed.

Therefore if someone's domain doesn't expire until May of 2013, but has a hosting package expire on April of 2013, if you synced up due dates, it wouldn't renew.

We have both free domains + paid domains. I think charging someone to renew every year is silly, especially if their domain doesn't expire so I'd like to sync those due dates with the correct expiration date, but also leave our 'free domain customers' alone, so their domains continue to renew on the hosting renewal date.

photo
1

are free names not associated by their domain name rather than their due date?

photo
2

I am also under the impression that free domains have to have the same due date as their hosting counterpart. This was in the documentation.

Therefore this needs to be addressed as all free domain users will get their domains synced and then charged in the subsequent year everytime the cron runs unless you elected to sync manually.

photo
1

Correct, free domains need to have the same date as the hosting product so if you have free domains on your system, you can't use the 'sync domain due dates' feature.

photo
1

truth is truth though - if a domain truly expires on such-snd-such a date, WHMCS absolutely HAS to show this fact. If you need to bill on a due date that is different from an expiration date, so be it - set the due date different than expiration. But please let's not muddy up the facts...

I am sure that there are numerous situations for many users where a change like this would open legal issues with clients, cause other integration issues, etc.

photo
1

I second this.

My use case: In order for free domains (with hosting) to work properly, they have to be combined into a single invoice. However, setting "Sync Due Date X Days in Advance", creates a separate invoice, only for the free domain first. That results in the domain getting renewed immediately (since the $0 invoice is considered paid). If the client then decides not to pay for the hosting plan, then you're stuck with the renewal cost.

So, yes, while setting the due date in advance is a cool idea, it creates potential financial troubles for the reseller. I think bypassing the "advance due date" feature for free domains could solve this.

ALTERNATIVELY, the advance due date should affect BOTH the hosting and the associated domain.

photo
1

I second this.

My use case: In order for free domains (with hosting) to work properly, they have to be combined into a single invoice. However, setting "Sync Due Date X Days in Advance", creates a separate invoice, only for the free domain first. That results in the domain getting renewed immediately (since the $0 invoice is considered paid). If the client then decides not to pay for the hosting plan, then you're stuck with the renewal cost.

So, yes, while setting the due date in advance is a cool idea, it creates potential financial troubles for the reseller. I think bypassing the "advance due date" feature for free domains could solve this.

ALTERNATIVELY, the advance due date should affect BOTH the hosting and the associated domain.