NexoPOS 4 is a free point of sale system build using Laravel, TailwindCSS, Vue and other open-source resources. This POS System focuses on utilities and functionalities to offer for most businesses all the tools they need to manage better their store. NexoPOS 4.x include a responsive and beautiful dashboard that ease the interaction either on a smartphone, tables or desktops.
We're frequently discussing about the future of the app (while waiting discussion are allowed). You can join the WhatsApp group where tips are shared on NexoPOS 4.x.
- Address : https://v4.nexopos.com
- Username : demouser
- Password : 123456
All the documentation for NexoPOS 4.x can be found on My NexoPOS. That includes :
1 - The support on NexoPOS 4.x only applies to the information provided by the users while creating an issue. This means we won't either do the installation on your server or check an issue on your server. You're therefore invited not to post your server information while creating an issue. We'll use your explanations to reproduce your issue and therefore to solve it.
2 - If you would like to have a dedicated support. Consider registering as a member to My NexoPOS platform.
NexoPOS 4.x RC-1 (Release Candidate) is scheduled for 15th December 2020. During that time, we're proceeding further test and creating documentation to cover most of the features on NexoPOS 4.x.
Here we list the knowns issues and the way around. Not everyone is likely to face these issues as it depends on the used enviroment.
- Error After Database Details (using
php artisan serve) If you're serving the project usingphp artisan serve, after setting up the database credentails and having them validated, you migth stop on an infinite loading page.
This is caused because during the database setup, the ".env" is updated which cause Laravel to restart the development server and therefore invalidate your session. The way around, is just to refresh the page and you'll end up on the application details section.
Do you plan to contribute? That's awesome. We don't have that much developer on it, so we're open to any type of contributions. If you're a developper, you'll start by forking the project and deploying that locally for further tests. If you just have some ideas, consider posting that as an issue. We'll review the ideas and decide to implement it.