Business POS guides / Duka / kiosk / Branch records
PRACTICAL POS GUIDE · KENYABranch records for duka / kiosk POS in Kenya
This guide to branch records for duka / kiosk explains the daily checks. Keep duka / kiosk branch quantities separate when recording sales. A sale of Bread roll at the second branch should change that branch’s records, not the main shop’s count.
Branch records for duka / kiosk: choose the location before checkout
Prioritise a short, recognisable list of the most frequently sold packets and pieces. A small pack and a family pack need different names and barcodes.
Two-branch example
| Location | Opening Bread roll units | Sold here | Remaining |
|---|---|---|---|
| Main shop | 12 | 0 | 12 |
| Second branch | 5 | 2 | 3 |
This example records two units sold at the second branch. The total remaining across both locations is 15, but the owner still needs to know that only three are at the second branch. A combined total does not make stock available in either location automatically.
Check branch and till reports together
- Select the intended branch and named till before selling.
- Use sample records to sell one known product at the second branch.
- Check the branch quantity, receipt and till record after that sale.
- Compare reports for the same business type, branch and date range.
- Keep separate independent customers in separate installations and databases.
Sharing does not remove conflict risk
Shared workspace synchronisation needs connectivity. Shared offline writes are owner-only; staff require connectivity. Independent offline devices do not reserve the same stock for each other. Rehearse the supported device-sharing workflow before two counters sell the last unit.
Transfers are a separate requirement
The worked example does not claim an inter-branch transfer, dispatch or transit-stock system. Moving a physical item between branches needs a supported documented process. Do not model the movement as a customer sale just to make a branch total appear correct.
Installation scope
The US.99 one-off launch software licence covers one business installation including its branches and tills. Hosting, devices, installation and support are separate costs. This scope does not create self-service SaaS accounts or automatically deploy another merchant.
Product fit for this business
Use defined whole units and packs. The software is not a complete specialist ERP or double-entry accounting system.
All amounts and product movements on this page are illustrative. The public demo uses sample records. Use an isolated test installation for rehearsal and replace sample prices and counts before real trading.
Try the workflow before choosing your setup
The launch software licence is US.99 once for one business installation, including its branches and tills. Hardware, installation, hosting, support and future upgrades have separate terms. These planning guides do not activate a licence or deploy an installation.