OrigamiPOS runs fully local, syncing seamlessly to the cloud. Even if the internet goes down, your registers keep selling, your kitchen keeps cooking, and your printers keep printing.
A minor internet hiccup can paralyze your entire store. With standard cloud POS systems, you lose sales, upset customers, and lose vital business data when your connection drops.
No internet = No database access. Orders fail, printers freeze, kitchen is blind, and transactions are blocked.
A local PostgreSQL database runs independently at the branch. Sync worker handles the cloud integration automatically in the background.
See how the register, kitchen, printing, and cloud sync work together in one flow. Switch offline mode to watch local operations keep running.
OrigamiPOS blends local reliability with cloud control so operators can grow without changing the core workflow.
Keep taking orders and syncing later when connectivity returns.
Turn every order into a clear, timed ticket for the kitchen.
Route receipts and kitchen tickets through a predictable local print path.
Staff log in with a PIN, and roles decide who can void, refund, close the day or change settings.
With cloud hosting, manage menus and prices for every branch from one place, and compare sales across branches.
Track stock movement and keep transfers visible across locations.
Front of house, kitchen and back office tools, served by the same branch server.
The admin dashboard has sales, staff, payroll, void, refund, tax and cash drawer reports, most with CSV and PDF export. The till prints the X-report, Z-report, voids and refunds, sales by item and sales by staff.
Record the float, pay-ins, pay-outs and drops, count the drawer at close and print the Z-report. An optional blind close-out hides the expected cash until the count is recorded.
Staff clock in and out at the till. The payroll report multiplies each person's clocked hours by their hourly rate.
A role without checkout gets a table-side screen: pick a table, add items, send to the kitchen. With an extra permission, waiters can go back into open takeaway and delivery orders to add a round.
Take dine-in, takeaway and delivery orders, with a queue number for takeaway. A line already sent to the kitchen can be switched to takeaway. Preorders are booked for a later time and stay off the kitchen display until they are due.
When an admin enables the bilingual setting, staff can switch the till to Arabic, with a right-to-left layout, for login, order taking and checkout; some labels stay in English. Menu items and categories can carry Arabic names for staff and for guests ordering by QR.
Set a tax rate, choose tax-inclusive or tax-exclusive prices, and print your tax number and a sequential tax invoice number on receipts. QR code on receipts in the ZATCA phase 1 format; phase 2 (Fatoora) is not supported. The QR code is printed when the Saudi Arabia tax region and a VAT number are set.
A QR code on the receipt opens a short feedback form, and the customer display can ask for a rating after payment. Answers appear in the Customer Feedback report.
A customer display at the till shows the order and the amount due. Signage screens show the menu board, featured items and the numbers of orders that are ready, with optional voice announcements.
A simple view of how the platform behaves when networks fail, branch operations scale, or menus change.
| Situation | Typical cloud POS | Legacy desktop POS | OrigamiPOS stack |
|---|---|---|---|
| Internet connection drops | Sales stop and the kitchen loses visibility. | Local-only or server-dependent setups can still be fragile. | Branch keeps selling and syncing resumes later. |
| Primary register fails | Usually unaffected, but all work depends on the provider. | Entire store can stall until the local server is fixed. | Independent branch data keeps operations moving. |
| Menu and pricing updates | Central updates are easy, but the system must stay online. | Often requires manual changes on each site. | Push once centrally, pull safely into every branch. |
| Thermal receipt printing | Can be delayed by browser print flows. | Vendor-locked or hard to maintain at scale. | Local agent prints directly with minimal friction. |
Start with a single branch or roll out across many locations using the same platform core.
A reliable local deployment for operators who want resilient day-to-day selling.
For operators who need central control, reporting, and location-aware management.
Files you can import and export, reports you can download, and the order channels and payments OrigamiPOS records today.
The branch server backs up its database on a schedule, can copy backups to offsite storage, and System Health warns when the last backup is too old.
Import and export inventory, customer and supplier lists as CSV files, and export the menu.
Download reports as CSV or PDF for your accountant or your own spreadsheets.
Add the delivery apps you use as order channels. Staff pick the channel when they enter the order, items can have a different price per channel, and the sales report splits sales by channel.
Guests ordering by QR can pay by bank transfer and attach a screenshot. Staff check it at the till and mark it settled or rejected.
Currency, tax region and the till's language (English, Arabic or both) are set per organisation.
Clear answers to technical and operational questions about the OrigamiPOS platform.