Slashdot Mirror


Restaurant POS Systems?

glamslam asks: "As the newly appointed technology director at a large restaurant chain, I've been given the task of evaluating and implementing a Point of Sale (POS) system. The main goal is to save costs on deployment across hundreds of restaurants. Another goal is to find a solution that is flexible enough to adapt to our unique operational model. Most of the vendors' products I have seen are based on Windows. I prefer the openness, flexibility, and cost-savings of Linux, yet I do not want to build the system from the ground up. Has anyone been involved in POS projects and managed to put Linux into the mix?" Are there any features that restaurants need that your traditional POS system may not include?

6 of 60 comments (clear)

  1. Just use standard web technology by perljon · · Score: 2, Interesting

    Use standard web technology. That way, it doesn't matter which server/client you use. You can use a PDA for the client, or a cell phone, or whatever...

    Run it over some SSL on an internal only network. Put a desktop as the end machine, and lock it down to only launch the POS client.

    PC hardware is cheap, web serving is a known science, and the technology is proven stable. Use standard ethernet network.

    --
    This isn't the sig you are looking for... Carry on...
  2. Don't make Wagamama's mistake. by chrestomanci · · Score: 3, Interesting

    Wagamama is a chain of Japanese restaurants in London and other places.

    The waitresses use iPaqs fitted with wireless cards to take your order. (Very efficiently I might add).

    The was a rumour circulating a few months ago, that a group of costumers saw this, and hacked their network using a laptop they had, the proceeded to order and eat a three course meal for each of them, while only paying for a soda each.

    I don't know if it is true, but considering the usual record for corporate deployment of wireless technology, it sounds plausible.

  3. eCentra by dagnabit · · Score: 2, Interesting

    Check out eCentra - their ViewPoint POS is a Java-based system that runs on Linux.

  4. Make a wish list and let the provider customize by Beltza · · Score: 2, Interesting

    (Important note: I work for a POS software company, and my opinion is therefore certainly biased!)

    I think that the very first thing you should do is create a big wish list about the functionality you want, and indicate the priority of all your wishes. You're telling that you prefer a Linux based system, but most certainly you'll have to give up functionality for this wish. Look specifically at the back-office, since most POS systems offer all the basics.

    I think that the flexibility of the application will not be a problem in an installation of this size. My experience is that vendors are willing make customisations to get big clients like you. At least, the company I work for works that way.

    Finally a shameless link to our software: www.icg.es/eng/.

  5. Tough find by God_Retired · · Score: 2, Interesting

    I work for a small sized retail chain (16 stores). We use RetailPro which is just a piece of shit. Every 6-8 months I look for alternatives. Linux would of course be ideal. But for this size, there just aren't a lot of options, regardless of OS. Bigger chains have the resources to roll their own. You may want to look into that. As someone mentioned, front ends are pretty much the same, it's the back office, and transaction polling that you have to look at. I think that it would be fairly trivial to write up a couple scripts and/or rsync to maintain customer data across stores, and whatever other data you would need. I have neither the skill not the time (mostly not the time) to do it myself.

    1. Re:Tough find by God_Retired · · Score: 2, Interesting

      We're still stuck with the crap DOS version. It is the final version, we are planning on upgrading to the windows version in Jan. The rounding problem still makes our accountants do flips. Polling goes either from the remote to the main, or over TCP/IP. Still get errors in processing the polled files.

      It seems to me that it would be pretty basic to put a frontend on an SQL query that would let anyone pull up the reports that we do now. Shit, how complicated is a retail system?

      As far as the language of choice, I don't know. I had a little interaction with RTI years ago, but they weren't able to do what I wanted.

      If you know of something comparable, kick down. I've seen a couple, but they seemed so similiar I couldn't justify the costs of moving all our data over. I'd love to get rid of RPro.