Linux At the Point of Sale 264
NegativeK writes "I work at a local comic and games shop, and I've been kicking around what it would take to implement a barcode scanner and more detailed inventory control. Currently, the setup is a low-tech register that tracks general areas of sales: new comics, ccgs, Games Workshop, rpgs, etc. Requirements include FOSS on Linux, the ability to use a cheap scanner, datamining, and output in a useful format (perhaps OpenOffice spreadsheet). The idea hasn't been pitched to the shop owner yet, so ease of use is probably more important than anything — but breaking out the programming books to work on parts isn't out of the question for me. Assuming the actual register stays, what resources are out there for a barcode/inventory implementation?"
iBookshelf would work (Score:2, Interesting)
The pieces are all there. (Score:5, Interesting)
The pieces to implement any sort of reasonable retail POS setup using FOSS are all available.
There are two things that it sounds like you're going to have problems with though:
The last time I looked into this specific problem the nicest looking piece of software for my requirements was L'âne [l-ane.net], but you'll want to actually do the research yourself (try searching on Freshmeat [freshmeat.net] and Sourceforge [sourceforge.net] at minimum).
Yeah, we know about sourceforge and freshmeat!!!!! (Score:5, Interesting)
Really, the noise-ratio of SourceForge is amazing, given that everyone and their mother can upload projects. When someone posts in slashdot is to know things that have *worked* and are working currently for other people. Sure, there are thousands of books about dating on amazon, but if you wanted one, you would go ask some people (not in slashdot of course
If you are going to recommend to look on SF or FM, then please consider just looking at the next story on slashdot... you really do not add anything useful to the conversation.
And to the parent, sorry it is nothing personal, but most of the posts I read at the time of my reply are among the same lines. I am also interested in the original question, but as I said before, I am looking for *experiences* from another people using such software rather than only a list of all the "Yet_Another_P0S I_started_for_school_homework.sf.net"
Not much of a problem (Score:5, Interesting)
That is where the works... integrating with the rest of the business software.
I have written an html/cgi Point-Of-Sale for my wife's hot sauce retail shop [sammcgees.com]. Works excellent and is integrated with a custom and much larger web store builder, order manager, and inventory control. This is the hard part and consists of several thousands of lines of perl code.
As far as bar code reading you just use a wedge or y cable and it acts just like keyboard input. A little javascript to ensure which form field is the active/default field and you are away. Input can come from a bar code scan or keyboard input for those items which are not bar coded.
Same mechanisms on vendor order receive for inventory maintenance.
Re:Book on this topic (Score:5, Interesting)
Ian W.
Excellent advice, but let me add... (Score:5, Interesting)
I wasted a lot of time on that system, and should have just bought an off-the shelf product. But.
In actual point of fact, the data mined by using the scanner was useless. The reason for this is simple: the manager of a small store who spends a good part of their lives inside will already know what needs to be done, whats selling and whats not. There is little insight gained from the data you gather.
And.
It degrades the customer experience in subtle ways. First off, it makes the transaction just a little bit slower. This irritates customers. Next, it adds a level of distraction to the employees whey they have to pay attention to so fine a level of technical detail; the added 'cognitive load' of using and keeping the system up to date fatigues them and makes them more system oriented and less customer oriented.
In short: this sort of fine level of tracking is net negative to a small retail business.
Re:Jeff Albertson (Score:5, Interesting)
Quite. Konzum, the largest Croatian supermarket chain, runs all POSs on Red Hat.
The owner of the chain saved millions on Windows licences alone.
I don't like the store, but I was mightily impressed when I first saw the Red Hat login screen on their POS.
I considered it quite uncommonly sensible business practice, at least for Croatian standards.
POS is a tough problem isn't it? (Score:3, Interesting)
I mean, all the pieces are easy, but it is hard to get right.
I could have been more clear (Score:3, Interesting)
For a tiny business with 2 cash registers, 1M records in a year is a *lot* more than one would likely expect. Generally at that point you may want to start thinking about the possibility of table partitioning, partial indexes, and the like. It also means that when you run complex reports, it might be a good idea to run them off a replica so you don't tie up the main server.
Otherwise you can introduce performance issues into your point of sale system which is a big no-no.
You are right-- it is not a lot of data on the enterprise scale, but it is enough to make the design a bit harder for even a small isntallation, and it introduces scalability issues in larger deployments if you aren't careful.
Re:Buy something off the shelf (Score:3, Interesting)
I am in the same boat with an in-law. He owns a small mini-mart. I am trying to find any solution that will work. Neither Quickbooks POS nor Microsoft RMS are anywhere near prime time for a grocery store.