Point of Sale

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

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 Shop Configuration

Go to Point of Sale > Configuration > POS Shops.

Creating a POS Shop

1. Click Create.
2. Shop Name – e.g. "Main Street Store".
3. Currency – Local currency.
4. Available Products – Select all products or specific categories.
5. Payment Methods – Cash, Bank Card, Mobile Wallet.
6. Journal – The Sales journal where POS orders are posted.
7. Receipt Printer – Network printer or ePOS Print.
8. Iface – Which screen layout (default, restaurant, bar).
9. Set Barcode Scanner if using a hardware scanner.
10. 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

1. Click New Session for the shop.
2. Enter Opening Cash (cash float).
3. The POS interface opens in a new tab.
4. Start selling.

Closing a Session

At end of day:

1. Click Close Session in the POS interface.
2. Enter actual cash counted.
3. Quickenerp shows expected vs actual difference.
4. 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.

POS Reporting

POS Analysis

Go to Point of Sale > Reporting > POS Analysis. Pivot with:

• Dimensions: Product, Category, POS Shop, Customer, Payment Method, Session.
• Measures: Quantity, Price, Total, Profit, Number of Orders.
• Filters: Date Range, Shop, Cashier.

Session Reports

Open a closed session: see total sales by payment method, product breakdown, cash difference. Export session PDF for records.

Key Metrics

• Average Order Value – Total / Order Count.
• Items Per Order – Cross-sell effectiveness.
• Cash Difference – Variance between system and actual cash.
• Peak Hours – When most sales occur.

Multi-Branch Consolidated Reporting

On the central server, POS Analysis naturally covers every branch once their orders have synced, letting you compare shops side by side. Use the Sync Log/Conflicts views alongside this — a branch with unusually low reported sales is sometimes actually a sync delay, not a real sales dip.