basic button buy buyer changes chef code contact cool copy correct create customer data doesn explain feature field form generate hundreds including manage manually passed point process products purchase questions return selling software sort system text transaction user version view

Hello, I'm thinking about using E-Junkie for selling software products.

Is there a way to make sure that serial numbers cannot be used on two computers (or more)?
For a software that might be a critical aspect, as sometimes people tend to buy just one license and install it on hundreds of machines in a company.

I'm thinking of something like WPA or Adobe's activation system for example, of course it doesn't need to be that fully featured and heavily protected. I mean I'm not looking for the ultimate bulletproof solution (I know there's no such thing), I'm just thinking about something basic that "keeps honest people honest".

Do you want the buyer to enter some sort of hardware key before purchase based on which you want to generate the code?

If I'm reading your mind correctly, this means that the creation of the hardware key would be up to me, the user would have to copy it from the software and paste it in the activation form and get the final key.
Correct?

If the answer is yes, I have two more questions:
1 - does E-Junkie provide some way to do collect the hardware key on its own?
2 - what happens if the buyer changes some hardware, reinstalls the software and the hardware fingerprint has changed? I mean from an E-Junkie / Administrative point of view.

threesixty3dIf I'm reading your mind correctly, this means that the creation of the hardware key would be up to me, the user would have to copy it from the software and paste it in the activation form and get the final key.
Correct?

Correct.

threesixty3ddoes E-Junkie provide some way to do collect the hardware key on its own?

I am not sure if I understand the question, but I'll explain the process. We have a feature called "variations" which lets you create a text entry field with the purchase button. That's where the user will need to enter the hardware key they get from your demo version. This will be passed to you with other transaction data and you'll return us the reg. key which we'll pass on to the buyer.

threesixty3dwhat happens if the buyer changes some hardware, reinstalls the software and the hardware fingerprint has changed? I mean from an E-Junkie / Administrative point of view.

They will contact you and you'll have to re-issue the key manually.

The "variations" text field sounds cool.

Actually it would be super-cool if E-Junkie could manage the whole process, including the creation of the hardware fingerprint, but I understand it might be hard without forcing the user to install some sort of active-x, which would be too invasive.

Anyways ... good job Chef, you have a new customer! :)