I'm a computer science student in my third year and work part time as an analytics engineer. My sister runs a cafe with her husband, and she manages all the paperwork and training related to their current POS system, which she often complains about. She has experience with various systems and suggested we create a new POS system focused specifically on restaurants and cafes. The advantage is that we can test it in her cafe and use feedback from her contacts in the industry for improvements. I know it won't be easy due to regulations, and I'm looking for advice on the feasibility of this project and any experiences others might have with POS systems.
11 Answers
I would advise against it. Liability can become a significant burden, especially if your system ever gets hacked. The backlash from clients could be severe.
Isn't it ironic that POS can mean 'point of sale' and also a less flattering term? Just thought I'd throw that in!
Having built and maintained POS systems before, I can say these are not easy solo projects. Still, it could be a great learning experience, just don't rely on it for daily operations right away.
Approach this project carefully. Competing against established companies requires resources and expertise to tackle both technical and legal challenges. Many developers don't venture into sales because it’s a different skill set altogether.
Absolutely! Regulatory compliance like SOX will be a big challenge for sure.
From my experience, working at a company that specializes in restaurant POS, be prepared for the intricacies of payment processing. Finding a reliable processor is crucial since regulations can get complicated, and you'll want to handle authorization requests carefully to avoid issues like double charges.
I would be cautious about relying on your own POS system at first. If there’s a glitch and you can't process payments, that could really hurt your sister's business. Make sure to run both systems simultaneously for a while until you're completely confident in yours.
We wouldn’t depend on it right from the start. We're aware of the various regulations here in Germany and plan to trial it alongside the current system for adjustments.
The complexity of restaurant POS systems is immense. Consider focusing on a niche and being specific about your features. Competing with major players is tough, even for a small team.
Studying the code of existing restaurant POS systems can be a great starting point. Check out Floreant POS, originally designed for Denny's, and UniCenta oPOS. They offer a lot of insights into what makes a good restaurant POS system. Here are the links: [Floreant POS](https://github.com/fat-tire/floreantpos) and [UniCenta](https://github.com/herbiehp/unicenta).
Thank you so much! This is really helpful!
You should definitely explore options like NCR Aloha, which is designed for restaurants. They provide guides on achieving PCI compliance, although you may need your own firewall. Remember, developing something unique is great for learning, but often existing systems can save you headaches.
Absolutely, compliance is key. Make sure you understand PCI and SOC2 regulations before diving in!
This is a solid project idea if you can get genuine feedback from users. However, many side projects like this face reality checks. The fun part is coding, but support issues can be a huge pain, especially during busy times.
I completely understand that! Support is definitely a concern, and we know we’ll face challenges along the way.
Go for it! I once developed POS software because I saw a market need. Testing it in your sister’s cafe is a unique advantage, allowing for real-world feedback and adjustments. Wishing you the best of luck with it!
I appreciate your concern, but I'm committed to moving forward!