Menu and taxes
Create realistic categories, prices, taxes, modifiers, addons, discounts, and common order combinations.
FAQ
FloPOS FAQ
Use these answers to quickly understand FloPOS before you spend time installing or comparing it with other restaurant POS systems.
How to think about this
Start with the restaurant workflow, not a feature checklist.
A restaurant POS affects order accuracy, staff training, payment flow, printer reliability, kitchen communication, reporting, and how managers recover from mistakes. The right question is not “does it have many features?” but “does it make daily service easier and safer?”
Ask whether staff can complete common tasks quickly, whether your hardware works, whether your data can be backed up, who fixes problems during service, and what happens when the internet is unreliable.
FloCafe fit
FloCafe is best evaluated as an open-source restaurant POS foundation. It is most relevant when source access, local control, and freedom from license fees matter.
Evaluation checklist
Test it like a live restaurant system.
Before relying on any POS, run the exact workflows your staff will use during service.
Hardware
Test receipt printers, kitchen printers, screens, scanners, cash drawers, and the network they depend on.
Operations
Confirm staff roles, backups, restore process, update plan, and how issues will be reported through GitHub.
Where FloCafe fits
Useful when ownership and transparency matter.
Public project materials describe workflows for dine-in, takeaway, delivery, table management, modifiers and addons, multiple payment methods, invoice generation, KDS, KOT printing, kitchen stations, ESC/POS thermal printing, barcode lookup, staff roles, customer data, loyalty, WhatsApp e-billing, backup history, optional Google Drive backups, multilingual UI support, SQLite, Electron, Next.js, TypeScript, and WebSocket updates.
MITLicense
3.12.22Latest FloCafe release
GitHubSource code
SQLiteLocal data
Related resources
Continue evaluating FloCafe.
Installation guide
Review setup paths and what to test before deployment.
Read installationDownload
Get releases, store links, and source setup options.
Download FloCafeSecurity
Plan access control, backups, updates, and device safety.
Read security guideOffline recovery
Separate local ordering, payment authorization, printing, and restore testing before live service.
Read offline POS guideFAQ
Common questions
What is FloCafe?
FloCafe is a free, MIT-licensed restaurant POS for ordering, tables, menus, taxes, discounts, staff access, kitchen display, KOT and receipt printing, reports, backups, loyalty, and local data storage.
Does FloCafe work without the internet?
Core POS data and restaurant operations use the local SQLite database. Test your exact order, printer, payment, backup, and recovery workflows offline because external payment terminals, cloud services, integrations, and remote access can still require connectivity.
Does FloCafe send anything to the cloud?
New installations may register a store support profile and send anonymous telemetry or store diagnostics. Settings provides controls to stop cloud services and anonymous telemetry without touching local POS data. Cloud order events require their own explicit switch.
How do I get help from inside FloCafe?
Open Help & Support from the sidebar to report a bug, printer, account, or tax problem, request a feature, and preview the diagnostic payload before sending. Requests use an offline outbox, retry when connectivity returns, and show a support code after FloAdmin confirms delivery.
What printer hardware does FloCafe support?
FloCafe supports ESC/POS receipt and kitchen printing over network and operating-system print queues. Use Test Print before live service; recent releases show the underlying network, Windows, CUPS, USB, or driver error and provide Help → Open Logs Folder for troubleshooting.
Are payments built into FloCafe?
FloCafe records cash and other payment methods, including split payments, but it does not bundle a managed card-processing contract. Confirm your external terminal or integration workflow, refunds, cash change, and end-of-day reconciliation before deployment.
How do updates and backups work?
Install packaged releases from the supported stores or GitHub Releases and test each update away from live service. Keep regular local backups, test the restore process, and never delete the production database while troubleshooting an update.
Can I delete cloud data without deleting restaurant data?
Owners can request deletion of store-linked cloud data from Settings using the Master PIN and typed confirmation. The reviewed request stops cloud activity while preserving local orders, bills, products, customers, and database backups.
What should I verify before deployment?
Test the exact release, menu, taxes, printers, roles, backups, and workflow in your own restaurant environment before live service.
No sales call. No card.
Continue evaluating FloCafe
Install it, load a real menu, and run a full service before you trust it with a Friday night.