Jump to content

Auto Renewal Setting


pjs32

Recommended Posts

Hi,

Good to see this feature - however if a client decides not to renew AFTER the renewal invoice has been generated -what happens? ie. invoice has been generated then client decides he does not want to renew and so presses the disable auto-renew button - what happens to the outstanding invoice?

Thanks

Link to comment
Share on other sites

  • 2 months later...
  • WHMCS CEO

The auto renewal setting when enabled stops any future invoices for a domain, but if one has already generated you would need to cancel that invoice if the user has a credit card on file to prevent it being charged.

 

Matt

Link to comment
Share on other sites

Thinking about it - that could be a bit dangerous.

 

I can see a situation where a customer gets the invoice, then thinks "oh I don't want it" - I'll remove the auto-renew. Then of course, we don't know about it and bill them anyway (plus renew the domain).

 

Perhaps some sort of a warning should be given if the invoice has already been raised, or even the option to cancel the invoice if they turn off autorenew (done automatically of course :))

Link to comment
Share on other sites

If this discussion is related to auto renew at a registrar (like eNom), then I agree with Ben regarding this change being somehow handled automatically via WHMCS. If not, admin should move it to a new thread as either a bug or feature request.

 

If a customer makes a change to the registrar auto renew setting after an invoice has been generated, how would I (as admin) know this? WHMCS should recognize that an outstanding invoice exists for this domain and either alert an admin or just cancel the invoice to avoid actually charging the customer and also renewing the domain name.

 

Optionally, the customer could be warned at the time they make the change that an outstanding invoice exists and updating this setting does not automatically cancel the outstanding invoice without further action on their part. They should be told to open a ticket or some other automatic process within WHMCS should take over to generate one for them based on the specifics of the situation.

 

As a last resort, before any renewal instructions are transmitted to the registrar, if the "auto renew" option is disabled then nothing for the affected domain should be sent. Better to err on the side of not renewing than to renew and have upset and charged customers.

Link to comment
Share on other sites

  • 3 months later...

Hi,

Sorry for bringing up an old post however this disable autorenew feature is causing me huge problems - the problem being that the client disables auto- renew for a domain when a invoice has already been raised -the invoice is then paid on the due date,the domain is renewed and the client is not then happy as he says he 'disabled auto renew' and wants a refund.

 

Is there a workaround for this?

 

Is it possible to pay WHMCS to make a custom script that deletes the invoice if the client disables auto-renew?

 

Thanks

Link to comment
Share on other sites

Is it possible to pay WHMCS to make a custom script that deletes the invoice if the client disables auto-renew?

Yes, raise a tickets for "sales" from within your WHMCS - we've had a number of "mods" done - all very cost effective and reasonably quick.

 

However before you do that ...

 

this disable autorenew feature is causing me huge problems - the problem being that the client disables auto- renew for a domain when a invoice has already been raised -the invoice is then paid on the due date,the domain is renewed and the client is not then happy as he says he 'disabled auto renew' and wants a refund.

 

Yes, no, and sort of :)

 

Lets call the existing "switch" allow to expire rather than auto-renew for a moment ...

 

If a client of admin sets the "allow to expire" flag, then *creation* of the invoice is suppressed - this is correct :)

 

Sadly it continues to remind the user about the domain expiry being imminent - this is wrong/a bug :(

 

If the invoice already exists *at the point the flag is set* (or more specifically the invoice *item* exists as it could be on an invoice with many other things) then the setting of the flag should remove that invoice item (if using pro-formas) or add a 2nd item/invoice/credit-note to cancel the invoice (if not using pro-formas)

- this is the feature missing at the moment

 

Having "allow to expire" set does and should not prevent *manual* renewal of the domain:

If the user (or admin) subsequently requests a renewal by clicking the button, the system correctly generates a renewal invoice - this is also correct, however it should also then reset the allow-to-expire flag, as

1. otherwise its then very confusing the the client

2. it would allow them to come back and switch the expiry back on (and this cancelling the new invoice)

3. it helps with reporting - as you *are* analysing patterns, trends etc aren't you ;)

 

The domain tld definitions really need a couple more fields ...

- an "adjustment" to how many days (in addition to the overall settings) that you should advise clients of pending renewal/expiry/invoice generation etc - as many ccTLDs *MUST* be renewed well in advance - can be done by having a days field to "auto-adjust" the expiry date - so a "days" value of 2 will mean the expiry date is set to registration date + period registered for - 2) - this will stop the current problems with es,de,eu and domains which get "deleted" by the registry the night before expiry

 

- a switch for "adds year on transfer" as many do not add any time on transfers to another registrar

 

- a switch for "perpetual regitrations" as not all tld's can be auto-renewed

 

- a "restricted renewal period" setting, as not all domains can be renewed at any time - .uk for example has to be less than 180 days before expiry - which will "leave off" the manual renew button from the client domains area pages

 

- a "auto cancel invoice on expiry" option (probably a number of days) as not all domains can be renewed after expiry-date, and with many reaching or exceeding expiry needs different API calls and a higher fee

Link to comment
Share on other sites

Thinking about it - that could be a bit dangerous.

 

I can see a situation where a customer gets the invoice, then thinks "oh I don't want it" - I'll remove the auto-renew. Then of course, we don't know about it and bill them anyway (plus renew the domain).

 

Perhaps some sort of a warning should be given if the invoice has already been raised, or even the option to cancel the invoice if they turn off autorenew (done automatically of course :))

 

You are right... Maybe a unselect auto-renew can 'void' invoice.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated