Aloha Connect

[Alohastage]

I am trying to find out some specifics with the new Aloha Connect. It is the replacement for the COM interface in Table Service 6.2. We have new locations that have recently purchased TS 6.2.

We use a 3rd party solution that has historically accessed the COM interface but they now state that we need to purchase an Aloha Connect license from our reseller to continue using their software. Does anyone know what ballpark price were talkin' about here? This is quite a racket as now were forced to fork over even more money to Radiant to use 3rd party software that has worked with TS 6.1 and below for years!

 

[posknowitall]

Just load 6.1. No need to fork over any more money

 

[Alohastage]

Thanks for the reply. I hadn't considered downgrading as an option. I hope the following questions are not something I should already know.

Can I use our current license on a previous version?

Where would I obtain the 6.1 CD?

Is this somewhat easy? Would I end up paying the same people to downgrade us so I don't have to purchase Aloha Connect from them?

Lastly, the selling point to us on using 6.2 was that "Before you know it 6.1 won't be PCI compliant." Is this realistic? This feels like a shake-down. And before you know it, they're coming back for more!

 

[SwampGas]

Aloha Connect is just the new name for the COM object controls. The licensing works on how many devices will be connecting through COMS and also tightens some of the controls on the COM object to alleviate some issues where the COM object SDK was being abused outside of the scope of the SDK and was a support issue.

If you have previously license COM, you still have it in the new version. -It doesn't matter if you are table service or quick service, it's still the same.

The updates to the COM interface have provided our custom written apps much better communication and control to the Aloha application. The COM interface is much better.


Do you really know what PCI is and what it involves? If you do less than 100 million dollars in credit card transactions per year, then you are not level 1 and also not under the same requirements as someone that is a lower level of PCI such as level 2 or 3. Being level 1 PCI, I could write a book on all the audits and requirements we are tested for with PCI. Aloha v6.5 will have some additional features that will help with PCI compliancy as the regulations on PCI are always expanding.

For example, if you have ALT-X ability, you are NOT PCI compliant. If you show an expiration date on any customer receipts, you are not PCI compliant. If you store credit card track data, or full credit card numbers un-encrypted for any amount of time, you are not PCI compliant.

Aloha is PCI compliant for what they need to provide. You have options to set that also defines how compliant you are (Tender settings showing credit card numbers or expiration dates, password settings, etc).

Radiant also has a PCI compliancy newsletter that should be available from your reseller (Or directly from your Radiant rep if you are working directly with Radiant). The newsletters will give you a good insight of what PCI is and what the Aloha product does for PCI, and offers best practices for most people.


Whoever gave you the line, "Before you know it...." should be shot. Yes, PCI compliancy is changing, but most of the people that need to really worry about PCI are always under maintenance anyway and keep their systems updated and have IT staffs and auditors for testing, and the mom-and-pop joints are a much lower level of PCI and their requirements are not as strict -Though they should be aware and try to avoid exposure.