No problem, no harm done!
Regarding your suggestion, in layman’s terms, that would be a license lockdown per domain verifiable via API, right? Trying to understand your suggestion better, so that I know who to approach about it for further input/contribution to this discussion.
p.s: that flag for staff reply really works wonders. I missed this thread when you first posted it…
Regarding your suggestion, in layman’s terms, that would be a license lockdown per domain verifiable via API, right?
A while ago there was a WordPress version of the popular HTML template “Porto” that I believe had a URL & License Code lockdown system on their page builder, which was met with quite a strong backlash from their buyers judging from the comments section of the theme.
I think that a “lockdown” system may produce its own set of problems, but definitely an Envato supported method of registering a URL to a license key would be very interesting indeed.
Bigger picture thinking in terms of support, we could then add a site URL input option to ticket systems, alongside the current license key input. We can then cross reference these 2 items against the purchase and of course, handle that information as needed. In my case, should the 2 not match an error would popup directing the buyer to the licenses page (amongst other details)
Overall it would add a small amount of time to a buyers download / support process, but would certainly help us more easily keep track of the URLs a license code is a associated with.
If the site URL data was structured so that a change in URL is also recorded, then even better, then it’s clear to see that a change from test.domain.com to www.domain.com is warranted, but domain.com to another-domain.com would not be.
I had a similar situation and Envato refused to provide license count of a user:
Unfortunately, I wouldn’t be able to specifically provide that information. Additionally it would be impossible for me to give an exact answer because the user may have multiple accounts in which they have purchased this item.My best advise would be to remind the buyer of the license terms and ask them to provide you with a license certificate for each website in which they have installed your item.
Thanks for clearing that up, Tom. Yeah, I had my doubts about the lockdown concept… I’ll bring this thread up in our meeting today, and see where it goes from there
L.E: fuelthemes, that is specifically where my concerns about linking between item purchase codes and a specific domain come into play, keeping our privacy rules in mind
Also, just edited the title to something less specific, in the hopes that it would act less as a billboard sign reading “DO NOT LOOK WHERE I’M POINTING”
I’ve encountered the same issue a lot as well. I’ve also found that many customers aren’t aware (or claim to be unaware) of the single site restriction.
Addressing the issue of buyer awareness, one way to help people understand the critical point is to contrast it with something else. Here’s where multi-use licenses would kill two birds with one stone.
1 Site - $55 5 Sites - $200
(the volume discount percentage here is just as an example)
When you select “1 Site” or “5 Sites”, the text below changes accordingly.
By forcing the customer to explicitly select “1 Site” or “5 Sites”, they are immediately made aware of the licensing restriction.
You could do the same thing with a “Quantity” input where you could select the number of items to add to a cart, and adjust the price accordingly. A discount isn’t even necessary for this to work, if that’s not something that the community would be receptive to at this point.
Fact of the matter is that many customers don’t read the product description, let alone licensing terms, so this type of thing is one of the few ways to ensure it’s seen and understood by every customer. And while I think it’s the customer’s responsibility to be aware of what they’re purchasing, if we can do a better job presenting the information it would save a lot of headaches
I’d also suggest that the text “1 Site” is both more attention grabbing and more immediately understandable than the text “Use, by you or one client, in a single end product….”. Even that simple sentence requires more parsing than some customers are willing to take the time to consider A numeral (1) gets the point across more effectively and leaves little room for misunderstanding.
This is an interesting topic, and the best solution is definitely to increase the buyer’s license awareness, as most buyers want to do things legally – I have had buyers ask me if they need to buy another license to use the theme on a separate domain.
Sevenspark’s proposal is an excellent potential solution, as that is definitely the most appropriate place to explicitly tell buyers about the license rules. And it’s how most software is sold online elsewhere “1 domain/5 domains/unlimited domains”. Good job Sevenspark! (although 5 sites x $55 would be $275 )
Good job Sevenspark! (although 5 sites x $55 would be $275 )
Thanks – I can, in fact, multiply. As I mentioned in my post, that would be indicative of a volume licensing discount, which is also a common way to sell licenses. There’s not much point in a 5-use license if costs the same as 5 single-use licenses
It does raise a good point that this could be made more obvious however. The notice “Save 27%!” next to the 5 Site option would entice customers to the volume discount.
Though volume discounts are another topic entirely, so I wouldn’t want the conversation to turn into whether that’s a good idea and what an appropriate percentage would be, as it wouldn’t affect the strategy above.
@Sevenspark I was only kidding It would be great to encourage multi-purchases and raise awareness over the licenses at the same time.
We originally setup an api which when our theme was installed it prompted for the activation of the url so else the theme would not load without it.
But this caused more issues than anything because believe it or not most of the buyers are putting these themes on servers which do not accept cURL or any such things.
The amount of times we had a bad email and bad rating because of it was unbelievable so we took that out of our themes.
I do not think there is a way of actually stopping someone from putting it on multiple domains unless you have a lock down on domain usage.
BUYERS REFUSING URLS
Its only a small amount but I have noticed that most of the buyers who ask for the most support are the ones who are unwilling to offer domain names/links to websites so we can check it first hand.
Instead they simply send screenshots and videos of the problem which half of the time we need to delve in to see what is happening and what the user has done to cause the issue.
You know that these people who do not provide links are most likely using multiple domains, you cant refuse support incase they are not, what can you do?
Having a license count means nothing really because it still does not stop the multiple domain usage.
I would make it more clear and instead of having just 2 licenses I would have multiple.
- Single Domain License
- Developer License (which just multiplies when user states how many domains it will be on).
- Developers Distribution License (which is for things like plugins within themes etc etc).
This way its a little more clear, but it still will not stop it, just help against it.