cristan / stampos

The best bar software for where you know your customers

StamPOS

This is a bar system designed for venues where you know your customers. It has the following goals:

• So user friendly, that the most atechnical person in your group can still order a drink
• Drastically reduce the amount of money your customers owe you
• Automate the administrative tasks of running a bar as much as possible

User friendly

Click on your name, click on the products you want to order, press "Confirm" and you're all set. It can't get much more user friendly than this.

Reduces the amount your customers owe you

In most systems, people start with 0 debt to the bar, and with every drink, this increases. Then after a while, people pay their debt and they have 0 again. This means that in any point in time, the bar is owed quite a bit of money.

In StamPOS, this works differently: people are expected to have credit with the bar. When they run out, they will be blocked, they can only order during the same weekend, but that's it. They could just pay their bill, but that means they can only order for 1 weekend again. It's handier for your customers to wire more money than they actually owe, so they can order for more than just 1 weekend.

In the off chance a customer hasn't paid, but bar personell still wants to allow ordering for him/her, there's an unblock functionality.

Automates administrative tasks

The following is automated:

• Sending an e-mail to all applicable users with their balance with the bar
• Determine which users have paid and which amount (using an export of internet banking)
• Sending a weekly e-mail to the owner of the bar with a backup of the database and a list of all users and their balance

Installing

• Download and install Tomcat 8. For most convenience, set the port number to 80
• Download the latest version of StamPOS, rename it to ROOT.war and deploy it to Tomcat. You can do this by placing it in /webapps in the Tomcat installation directory, or by using the built-in manager.
• Go to localhost to see your installation :)

stampos's Issues

Don't allow debit for specific users

You're bound to run in to customers where paying is really troublesome. For this, you should be able to indicate they can't have any credit.

For this you'll need 2 features

Indicating that a user can't have any credit
This should be a regular boolean property of a customer.

Disallow ordering when applicable
After determining whether the user can order at all, we should now check if the user is allowed to have a debit, and when he/she doesn't, we should disable any products which would make this user have a credit below €0. This needs to be done every time a user is selected, a product is added or a product is deleted.

Checking server side
To prevent hacking attempts, we should not only check client side, but server side as well. If a user like this creates a transaction which would cause her/him to have a debit, the server should return an error.

Allow a password for users

Use more modern code

The current code is based of grails 2 and the project is created by Groovy/Grails Tools Suite. Especially the latter is an issue because this hasn't been maintained in years and the official download link is now dead.

Grails 3 would be a great option since it's build on top off Spring Boot, so IDE support should probably be fine. You could even get it to work with Kotlin although the main advantage of this route would mostly be that you don't need to rewrite that much of the code.

Another option is to skip Grails altogether, and just make a Kotlin Spring (boot) project. You'll miss out on the nice features to persist items in the database, so you'll have to manually do the hibernate work (or use some other method to persist data).