Skip to Content
In this topic
POS Overview
Shop & Session Setup
Using the POS Interface
Multi-Shop Offline Sync
Reporting & Analysis

How Multi-Shop Offline Sync Works

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

RoleWhat It Does
ServerThe 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.
LocalA 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.

Rating
0 0

Commenting is not enabled on this course.

This documentation is updated continuously. Some features described here may be renamed, deprecated, or still being finalized.