pre-sales question for HikaSerial

Hi,

I sell an add-package X for a program named Y using HikaShop on my website. For some time I've been looking for a better way to tie activations my software to HikaShop orders and HikaSerial looks interesting. Before I buy it I would like to confirm that it can support my workflow.

The licencing works like this. Each Y installation has a 6-char seat number, and each X licence allows the user to upgrade the facilities of a particular Y seat. Experience has shown that it is more convenient to make this assignment during the installation of X on Y, because often the person buying hasn't decided exactly which workstation(s) in their office will upgraded.

So right now my installer script tells my site the seat number and my site returns a licence file that locks my software to that seat. This allows activations to be monitored per registered user but not restricted. There is no tie-up between activation and a paid-up order. This is mildly unsatisfactory although in practice there are very few problems.

Ideally I would like each licence purchased to deliver a unique token that can be exchanged for one and only one licence file per seat. Hope I've explained this well - my question is can HikaSerial help do this? and how?

Conrad

Sounds interesting but I'm still not quite clear about how this is going to work. The major issue with HikaShop is that for example if someone buys 2 licences this order appears as one line in the database with quantity 2, so you cannot allocate a seat number to the order since there may be more than one. And the seat number is allocated typically during installation not at the time of purchase.

If I decide to buy HikaSerial are you willing to assist in implementing the solution?