Enom domain module retrieve base prices when TLDs are synced - Solved

[Panormitis]

Hello,

I have an Enom reseller account.

I started using Enom domain module and I noticed when I try to sync the TLD prices, the prices retrieved are the base "my cost" prices, not the retail domain prices I have set for the customers, which I find odd.

I managed to fix it so I just wanted to share my solution in case anybody finds it useful.

Open file <blesta_dir>/components/modules/enom/enom.php for editing.
  Find: PE_GetProductPrice
  Replace with: PE_GetRetailPrice
  
There should be 3 instances, on lines 185, 193 amd 198.
Save the file, clear Blesta's cache directory and enjoy!

I really think this should have been fixed by Blesta developers. Domain prices should be synced to the retail prices, not the base ones.

[Paul]

The prices fetched are supposed to be your cost, then they are run through the markup settings to increase the price by the desired amount, see screenshot.

[Panormitis]

I understand that, but I don't think it's practical. When the time comes for Enom's domain renewal notices (Enom is obliged by ICANN to send them on my customers) won't the domain notices list the renewal/retail price I have set on my Enom reseller account?

This is what the customer will pay, not "my cost" price. It looks a lot cleaner to me to fetch the retail prices to sync everything perfectly, than fetching "my cost" prices and rely on markup to make profit.

[Paul]

1 hour ago, Panormitis said:

I understand that, but I don't think it's practical. When the time comes for Enom's domain renewal notices (Enom is obliged by ICANN to send them on my customers) won't the domain notices list the renewal/retail price I have set on my Enom reseller account?

This is what the customer will pay, not "my cost" price. It looks a lot cleaner to me to fetch the retail prices to sync everything perfectly, than fetching "my cost" prices and rely on markup to make profit.

Blesta can send those notices so that you can disable them in Enom. Many registrar modules only include the cost, not a price you set in their panel. If we used the price you set in Enom  for Enom, then 1) Everyone would have to set a price there and 2) it would not work the same as other registrars who do not have a retail price, but only a wholesale price.

It is better to let Blesta do the price markup, or just set your TLD prices manually to the same value you have set for retail prices in Enom. If you want to make a modification to your module, and keep your markup at 0% for new/renew/transfer, you are welcome to do that, it's just not a change we would make to the module as it would be inconsistent with other integrations.

[Panormitis]

I have asked Enom support about this and their support agent explicitly said they are obliged to send renewal domain notices, no mater what, but at least they will show to the customers the retail prices I have set.

This is why I want to sync the correct prices, for transparency.

[Paul]

Blesta can send up to 3 domain renewal notices, ICANN requires at least 2. If you have these enabled in Blesta you can disable these notices at the registrar. The registrar may want to know more about when you are sending the notices and what the content of the notices are. If you wan to rely on Enom sending these out, then you will want to disable these notices in Blesta so that the client doesn't receive extra notices. Since it is an ICANN requirement, Enom will want to know that you are using software like Blesta that sends out these notices before disabling on their side.

[Panormitis]

I know Blesta can do it.

What I'm saying is that Enom support said they will send notices too, no matter what. I can't disable Enom notices, they are obligatory.

The only thing I can do is at least make the prices match, for transparency.

Otherwise my customers will receive renewal notices with different prices.

EDIT: I can tell them "Don't send notices yourself, I have a billing software that does", but they didn't give me that option. The way they said it, implies I don't have that option.

[Paul]

I'm pretty certain there are folks that handle the notices on their own and have it disabled with Enom, so maybe you didn't speak with the right support agent. These are required by ICANN, so you must demonstrate that you are able to send them. It makes sense that they would be hesitant to disable without proof. Unfortunately I couldn't find anything in their documentation about it.

[Panormitis]

I can ask another support agent again.

In the meantime, I do prefer the module to retrieve the retail prices for everything (even if that seems odd). I suppose the API call names aren’t going anywhere anytime soon, so even if the module gets updated, I’ll just change PE_GetProductPrice to PE_GetRetailPrice.

I would be very surprised if I’m the only one who prefers this. An option in the module settings, to choose between PE_GetProductPrice and PE_GetRetailPrice could be a nice idea though.