Point of Sale
This course covers the Point of Sale module in Quickenerp. Learn how to set up POS shops, manage product displays, process customer orders, handle payments, close sessions, run multi-shop offline sync, and analyze sales.
| Responsible | System |
|---|---|
| Last Update | 07/21/2026 |
| Completion Time | 2 days 12 hours |
| Members | 1 |
Running Branches That Can't Always Reach Head Office
For retailers with multiple physical branches where the internet connection to head office is unreliable, Quickenerp supports a dual-role architecture: one central database holds real accounting and inventory, while each branch runs its own local Quickenerp instance that keeps working — selling, printing receipts, deducting local stock — even with no connection at all, then syncs to the centre whenever it can.
The Two Roles
| Role | What It Does |
|---|---|
| Server | The central Quickenerp — owns consolidated accounting and inventory across all branches. Receives pushed orders from every local branch and is the source of truth for products, prices, and master data that branches pull down. |
| Local | A shop-floor instance — runs its own POS shop(s) and warehouse fully offline-capable, queues completed sales, and periodically pushes them to the central server while pulling master-data updates back down. |
The role is set once per installation in Settings > Point of Sale > Instance Role (Server or Local) — this is a one-time architectural choice per database, not something switched day-to-day.
What Actually Syncs
- Push (Local → Server): completed POS orders queue in an Outbox and are sent in batches (default 200 records per request — lower this on slow links) at a configurable Push Interval (default every 5 minutes).
- Pull (Server → Local): product/price/master-data updates come down at a configurable Pull Interval (default every 5 minutes).
- Every sync attempt is recorded in the Sync Log, and anything that fails to reconcile automatically (e.g. a numbering collision) surfaces in the server's Conflicts view for manual review rather than silently being dropped.
Counter Mapping
Each local POS shop is linked to a specific POS shop on the server via a Counter Map entry (Point of Sale > Configuration > Counter Maps on the server), so orders from "Branch 2 – Till 1" always land against the correct corresponding shop record centrally, not mixed in with other branches.
POS Overview
View allRunning Branches That Can't Always Reach Head Office
For retailers with multiple physical branches where the internet connection to head office is unreliable, Quickenerp supports a dual-role architecture: one central database holds real accounting and inventory, while each branch runs its own local Quickenerp instance that keeps working — selling, printing receipts, deducting local stock — even with no connection at all, then syncs to the centre whenever it can.
The Two Roles
| Role | What It Does |
|---|---|
| Server | The central Quickenerp — owns consolidated accounting and inventory across all branches. Receives pushed orders from every local branch and is the source of truth for products, prices, and master data that branches pull down. |
| Local | A shop-floor instance — runs its own POS shop(s) and warehouse fully offline-capable, queues completed sales, and periodically pushes them to the central server while pulling master-data updates back down. |
The role is set once per installation in Settings > Point of Sale > Instance Role (Server or Local) — this is a one-time architectural choice per database, not something switched day-to-day.
What Actually Syncs
- Push (Local → Server): completed POS orders queue in an Outbox and are sent in batches (default 200 records per request — lower this on slow links) at a configurable Push Interval (default every 5 minutes).
- Pull (Server → Local): product/price/master-data updates come down at a configurable Pull Interval (default every 5 minutes).
- Every sync attempt is recorded in the Sync Log, and anything that fails to reconcile automatically (e.g. a numbering collision) surfaces in the server's Conflicts view for manual review rather than silently being dropped.
Counter Mapping
Each local POS shop is linked to a specific POS shop on the server via a Counter Map entry (Point of Sale > Configuration > Counter Maps on the server), so orders from "Branch 2 – Till 1" always land against the correct corresponding shop record centrally, not mixed in with other branches.
The POS Module
The Point of Sale module provides a tablet-friendly POS interface for retail operations. It works online and offline (cached orders sync when reconnected). Integrates with Inventory (stock deduction), Accounting (sales journal), and CRM (customer tracking).
Core Concepts
| Concept | Model | Description |
|---|---|---|
| POS Shop | pos.config | Configuration of a physical POS location. Includes product list, payment methods, receipt printer. |
| POS Session | pos.session | A work shift. Opens with a cash float, closes with reconciliation. |
| POS Order | pos.order | An order placed at the POS. Creates a sales order and invoice. |
| Payment Method | pos.payment.method | Cash, Card, Mobile, etc. Each maps to a journal in Accounting. |
Accessing POS
- Go to Point of Sale from the main dashboard.
- Click New Session to open a POS session on a connected tablet/browser.
- Set up shops in Configuration > POS Shops.
POS Shop Configuration
Go to Point of Sale > Configuration > POS Shops.
Creating a POS Shop
- Click Create.
- Shop Name – e.g. "Main Street Store".
- Currency – Local currency.
- Available Products – Select all products or specific categories.
- Payment Methods – Cash, Bank Card, Mobile Wallet.
- Journal – The Sales journal where POS orders are posted.
- Receipt Printer – Network printer or ePOS Print.
- Iface – Which screen layout (default, restaurant, bar).
- Set Barcode Scanner if using a hardware scanner.
- Set Customer Display if using a second screen.
Available Product Settings
- Sale Product Search Limit – How many products load initially.
- Show Product Images – Display product images in the POS grid.
- Category Display – As a grid or list.
- Featured Products – Highlight specific items.
Opening a Session
- Click New Session for the shop.
- Enter Opening Cash (cash float).
- The POS interface opens in a new tab.
- Start selling.
Closing a Session
At end of day:
- Click Close Session in the POS interface.
- Enter actual cash counted.
- Quickenerp shows expected vs actual difference.
- Confirm closure. The session posts all orders to Accounting.
Restaurant & Bar Mode
When Iface is set to Restaurant or Bar, the POS gains a floor plan editor (tables, seats), the ability to split a bill across multiple guests, course-by-course order firing to the kitchen, and a bill-printing step separate from final payment — useful for table service rather than a straight retail checkout.