Open Source Point of Sale is a web based point of sale system. The main features are:
- Stock management (Items and Kits)
- VAT, customer and multi tiers taxation
- Sale register with transactions logging
- Quotation and invoicing
- Expenses logging
- Receipt and invoice printing and/or emailing
- Barcode generation and printing
- Suppliers and Customers database
- Multiuser with permission control
- Reporting on sales, orders, expenses, inventory status
- Restaurant tables
- Messaging (SMS)
- Selectable Boostrap (Bootswatch) based UI theme
- Mailchimp integration
- reCAPTCHA to protect login page from brute force attacks
- GDPR ready
The software is written in PHP language, it uses MySQL (or MariaDB) as data storage back-end and has a simple but intuitive user interface.
The latest 3.x version is a complete overhaul of the original software. It is now based on Bootstrap 3 using Bootswatch themes, and still uses CodeIgniter 3 as framework. It also has improved functionality and security.
Deployed to a Cloud it's a SaaS (Software as a Service) solution.
A demo version of the latest master version can be found on our Demo server. This is a containerized install which will be reinitialized when new functionality is added to the code repository.
- username: admin
- password: pointofsale
Please refrain from creating issues about installation issues before reading the FAQ and going through existing github issues. We have a build pipeline that checks the sanity of our latest repository commit and in case the application itself is broken then our build will be as well.
This application can be setup in many different ways and we only support the ones described in the INSTALL file linked below.
Read the INSTALL.md in our repository.
Open Source Point of Sale is licensed under MIT terms with an important addition:
The footer signature "You are using Open Source Point Of Sale" with version, hash and link to the original distribution of the code MUST BE RETAINED, MUST BE VISIBLE IN EVERY PAGE and CANNOT BE MODIFIED.
Also worth noting:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
For more details please read the file LICENSE.
It's important to understand that althought you are free to use the software the copyright stays and the license agreement applies in all cases. Therefore any actions like:
- Removing LICENSE and any license files is prohibited
- Authoring the footer notice replacing it with your own or even worse claiming the copyright is absolutely prohibited
- Claiming full ownership of the code is prohibited
In short you are free to use the software but you cannot claim any property on it.
Any person or company found breaching the license agreement will have a bunch of monkeys at the door ready to destroy their servers.
Keep the Machine Running
If you like the project, and you are making money out of it in some form, then consider buying us a coffee so we can keep adding features.
To help us with OSPOS translations please use Weblate website here and sign up. After registering you can subscribe to different languages and you will be notified once a new translation is added.
Please also read the wiki page here to find our Translations Guideline.
Only with the help of the community we can keep language translations up to date.
If you are taking a release candidate code please make sure you always run the latest database upgrade script and you took the latest code from master. Please DO NOT post issues if you have not done those step.
Bug reports must follow this schema:
- Ospos version string with git commit hash (see ospos footer)
- OS name and version running your Web Server (e.g. CentOS 6.9, Ubuntu 16.4, Windows 10)
- Web Server name and version (e.g. Apache 2.2, Apache 2.4, Nginx 1.12, Nginx 1.13)
- Database name and version (e.g. MySQL 5.5, MySQL 5.6, MySQL 5.7, MariaDB 10.0, MariaDB 10.1, MariaDB 10.2)
- PHP version (e.g. 5.6, 7.0, 7.1, 7.2)
- Language selected in OSPOS (e.g. English, Spanish)
- Any configuration of OSPOS that you changed
- Exact steps to reproduce the issue (test case)
- Optionally some screenshots to illustrate each step
If above information is not provided in full, your issue will be tagged as pending. If missing information is not provided within a week we will close your issue.
If you are seeing the message system folder missing, then you have cloned the source using git and you need to run a build first. Check INSTALL.md for instructions or download latest zip file from bintray instead.
If at login time you read "The installation is not correct, check your php.ini file.", please check the error_log in public folder to understand what's wrong and make sure you read the INSTALL.md. To know how to enable error_log, please read the comment in issue 1770.
If you installed your OSPOS under a web server subdir, please edit public/.htaccess and go to the lines with comment
if in web rootand
if in subdir comment above line, uncomment below one and replace <OSPOS path> with your pathand follow the instruction on the second comment line. If you face more issues please read issue #920 for more help.
Apache server configurations are SysAdmin issues and not strictly related to OSPOS. Please make sure you first can show a "hello world" html page before pointing to OSPOS public directory. Make sure .htaccess is correctly configured.
If the avatar pictures are not shown in Items or at Item save time you get an error, please make sure your public and subdirs are assigned to the correct owner and the access permission is set to 755.
If you install ospos in docker behind a proxy that performs ssloffloading, you can enable the url generated to be https instead of http, by activating the environment variable FORCE_HTTPS = 1.
If you have suhosin installed and face an issue with CSRF, please make sure you read issue #1492.
|Many thanks to JetBrains for providing a free license of IntelliJ IDEA to kindly support the development of OSPOS||Many thanks to Travis CI for providing a free continuous integration service for open source projects.|