Cafes and coffee shops
Good fit for fast counters, simple menus, repeat orders, takeaway billing, and receipt printing.
Free open-source restaurant POS
A restaurant POS you can inspect, run, and improve.
FloPOS is built for restaurants that want more control than a closed subscription POS allows. Use it to evaluate a self-hosted workflow for billing, table service, menu management, kitchen display, receipt printing, staff access, and local data.
MIT licensev1.7.1 release8 GitHub stars4 forksWindows / macOS / Linux
Service viewKitchen online
Dine-in tableOpen ticket, modifiers, kitchen status
PreparingTakeaway counterFast billing, receipt print, payment
NewBack officeMenu, staff, stock signals, local data
ManageSQLiteLocal data
KDSLive tickets
ESC/POSReceipts
Who it fits
Useful for operators who want control and developers who need a real POS base.
FloPOS is not trying to hide complexity behind a sales pitch. A restaurant POS touches money, staff permissions, printers, taxes, and customer service. This site should help you understand what FloPOS can do today, what you must test, and where open source changes the tradeoffs.
Restaurants and QSRs
Evaluate it for dine-in tables, open tickets, order modifiers, kitchen routing, and service flow.
Bakeries and food trucks
Useful when the priority is reliable local billing, clear menus, and avoiding monthly software fees.
Developers and sysadmins
Review the code, test builds, inspect data storage, and adapt the system for specific restaurant needs.
What FloPOS covers
Core restaurant POS workflows, explained clearly.
These are the product areas to test before deployment. The copy is intentionally practical: verify every workflow with your own menu, hardware, and staff process.
Order and billing workflow
Create dine-in, takeaway, and delivery orders with menu search, modifiers, addons, discounts, and multiple payment methods. The goal is fast billing without forcing staff through unnecessary screens.
Table and ticket control
Track open tables and active tickets so servers, cashiers, and kitchen staff can see what is still in progress during service.
Kitchen Display System
Route orders to a kitchen screen using real-time updates. This helps teams reduce missed tickets and coordinate preparation without relying only on paper receipts.
Receipt and kitchen printing
Use ESC/POS thermal printers over common connection types. Always test your exact printer model, paper size, and network setup before live service.
Menu management
Maintain categories, products, variants, addons, toppings, and prices from one place so the POS reflects the menu your staff actually sells.
Staff access
Create staff accounts for operational roles such as owner, admin, and kitchen workflows. Good permissions reduce mistakes and protect sensitive settings.
Local SQLite data
FloPOS uses local SQLite storage, which is simple to run and easy to back up. Operators still need a backup routine before using it in production.
Stock awareness
Use low-stock signals to catch critical item shortages early. For advanced recipe costing or purchasing workflows, validate current project support first.
Desktop deployment
Run FloPOS on Windows, macOS, and Linux using releases, store builds, or source builds depending on your technical comfort level.
Why open source matters
You should know what runs your restaurant.
Closed POS platforms can be convenient, especially when they include payments, support, and managed hosting. The tradeoff is dependency. FloPOS gives restaurants and developers a different path: public source code, MIT licensing, local data, and a project history that can be reviewed on GitHub.
That transparency does not remove operational responsibility. You still need backups, printer testing, access control, and an update plan. The benefit is that those decisions are visible and controllable.
MITOpen-source license
8GitHub stars
4Forks
v1.7.1Latest release
Evaluate safely
Do these before using any POS in production.
Run a test menu
Create real categories, products, modifiers, taxes, and discounts. Staff should be able to complete common orders without guessing.
Read docsTest your hardware
Check receipt printers, kitchen printers, cash drawer behavior, barcode scanners, and network stability before a live shift.
Install guidePlan backups
Local data is useful only if it is protected. Decide who backs up the database, where backups go, and how restore testing works.
Security guideStart here
Choose the next page based on what you need.
Download FloPOS
Get the latest release, store links, and source-code options.
DownloadInstall it
Review setup paths for operators and developers before testing.
InstallationUnderstand free POS
Learn what “free” really means: no license fee, but real hardware and operations work.
Free POS guideEvaluate FloPOS with your actual restaurant workflow
Download the latest release, run a test menu, connect your printer, and review the source code before using any POS in live service.
FAQ
Common questions
What is FloPOS?
FloPOS is a free, open-source restaurant POS system for cafes, restaurants, bakeries, food trucks, cloud kitchens, and similar food businesses. It is designed around core restaurant workflows such as billing, tables, menus, kitchen tickets, receipt printing, and staff access.
Why is FloPOS free?
FloPOS is released under the MIT license. That means restaurants and developers can inspect the code, run it without license fees, and adapt it within the terms of the license. Hardware, setup time, hosting, backups, and support are still real operational costs.
Where is the source code?
The source code is hosted on GitHub at github.com/FreeOpenSourcePOS/FloCafe. Use GitHub to review releases, report issues, fork the project, or contribute improvements.
Should I use FloPOS in live service immediately?
No POS should be deployed blindly. Test your menu, taxes, printers, cash drawer, staff roles, backups, and end-of-day workflow before using FloPOS with real customers.