POS server hosting Kenya

Keep every till in sync with one central back office

Tills should keep selling when the internet drops. The server they report to should never drop. Host your POS back office, sync API and eTIMS integration on a VPS with root access, so every shop pushes sales to one place and owners can check takings from their phone.

Size your server Ask on WhatsApp

Tills syncing to the server

6 tills

We suggest

VPS V3 KES 7,000/mo

Four cores absorb the burst when several branches reconnect and sync at once, and 320 GB of SSD stores years of line items. Its 16 GB of RAM handles MySQL-based POS and Odoo alike.

Order VPS V3

The till sells, the server keeps the books

In a supermarket or hardware shop, a till cannot stop because the internet did. That is why most serious POS setups in Kenya are offline-first: each till sells against a local copy of prices and stock, then pushes sales to a central server when the line returns. The server is where price changes, stock levels, cashier shifts and daily reports come together.

Keeping that central server on a desktop in the back office is common and fragile. A power cut, a failed hard disk or a router reboot cuts off every other branch, and the owner cannot check yesterday's takings from home. A VPS keeps the back office reachable from every shop and from the owner's phone, while the tills carry on locally.

POS back-ends are mostly database work: many small writes during trading, a burst of sync traffic when a branch reconnects, then heavy reports at closing. With root access you can tune MySQL or PostgreSQL for that pattern, expose a sync API over HTTPS, put tills on a private VPN, and run the integration that sends invoice data to KRA's eTIMS. We provide the server, operating system and login; your POS vendor or developer installs the software, and our support team is free to help with server questions.

The problem

POS headaches a central server solves

Tills drifting out of sync

A price change entered at head office never reaches the branch, so cashiers keep selling at the old price for days. With one always-online server, every till pulls the same price list and stock file as soon as it connects.

The whole chain on one back-office PC

If the computer under the manager's desk holds the master database, a blown power supply or ransomware infection stops reporting and stock control for every shop. Moving it off-site removes that single point of failure.

eTIMS invoices stuck in a queue

Sales made while a till or server is offline still need to reach KRA. When the central server is off at night or during outages, the backlog grows. A hosted server that stays online clears queued invoices as soon as tills reconnect.

Owners who cannot see today's sales

Shop owners travelling to suppliers or between branches want takings, voids and stock alerts on their phone. A back office on a VPS with HTTPS lets them log in from anywhere without opening the shop network to the internet.

What runs on it

POS systems that need a back-end server

Some POS systems use the server as a shared database, others as a sync and reporting hub. Both run well on a VPS.

Odoo Point of Sale

Browser-based POS that is part of Odoo, linked to inventory and accounting. It can keep ringing sales offline once a session is open and syncs when connected. The server runs Odoo on PostgreSQL, so give it enough RAM.

uniCenta oPOS

A free Java desktop POS for retail and hospitality. Multiple tills can share one central MySQL database, which you can host on a VPS and reach over a VPN rather than exposing the database port.

Chromis POS

A community fork of uniCenta with retail and restaurant features, also Java on MySQL. Branches can point at a shared database on the VPS for central stock and reporting.

Floreant POS

An open-source Java POS built for restaurants and bars, with kitchen tickets and table management. It ships with an embedded database but can use MySQL or PostgreSQL on a central server for multi-terminal setups.

Custom POS back-ends

Many Kenyan retailers run a POS built by a local developer: a Laravel or Node.js API, a browser or Android till that stores sales locally, and a sync endpoint. These need a database, queue workers and a public HTTPS address.

Sizing

Pick a server for your tills

Count every till or checkout lane that syncs with the server, across all your shops.

1–3 tills VPS V1 Enough for one shop on uniCenta, Chromis or a light custom API with a MySQL database. If you run Odoo POS, skip straight to VPS V2 for the memory.
4–15 tills VPS V3 Four cores absorb the burst when several branches reconnect and sync at once, and 320 GB of SSD stores years of line items. Its 16 GB of RAM handles MySQL-based POS and Odoo alike.
16–40 tills VPS V4 Six cores and 480 GB of SSD for a regional chain with many tills, closing reports across branches and an eTIMS integration running alongside the sync API.
41+ tills VPS V5 Ten cores and 40 GB of RAM for supermarket groups with dozens of lanes, a large product catalogue and reporting that would otherwise compete with live syncing.

A starting point only: real load depends on how many line items you ring per hour, how often tills sync and how heavy your closing reports are, and Odoo needs more RAM than Java POS systems.

VPS V1

KES 2,000/mo

1 Core
1 GB RAM
40 GB NVMe
1 TB transfer

Order V1

VPS V2

KES 5,000/mo

2 Cores
8 GB RAM
160 GB SSD
8 TB transfer

Order V2

VPS V3

KES 7,000/mo

4 Cores
16 GB RAM
320 GB SSD
16 TB transfer

Order V3

VPS V4

KES 15,000/mo

6 Cores
24 GB RAM
480 GB SSD
24 TB transfer

Order V4

VPS V5

KES 20,000/mo

10 Cores
40 GB RAM
800 GB SSD
40 TB transfer

Order V5

Before you go live

POS server setup checklist

0 of 8 done. Tick them off as you go.

Give the back office and sync API their own hostname, such as pos.yourshop.co.ke, with an HTTPS certificate.
If tills talk to MySQL directly, as uniCenta and Chromis do, connect them through a WireGuard VPN instead of opening port 3306 to the internet.
Set the server time zone to Africa/Nairobi and enable time sync so receipts, shifts and Z-reports line up.
Rehearse an outage: disconnect a till, ring a few sales, reconnect and confirm each sale appears once on the server.
Confirm queued eTIMS invoices are transmitted after a branch comes back online, and alert someone if the queue grows.
Back up the database nightly and before every bulk price or stock import, and keep copies off the server.
Separate cashier, supervisor and administrator roles so voids, refunds and price overrides need the right login.
Schedule heavy reports and stock valuation after closing time so they do not slow down tills during trading.

Built for Kenya

POS realities in Kenyan retail

eTIMS is part of every sale

KRA expects tax invoices to be issued through eTIMS, and businesses with their own POS or ERP can integrate system to system. Hosting that integration on an always-online server, rather than a till or office PC, keeps invoice data flowing even when one shop loses power.

M-Pesa at the counter

Customers pay to your Till or Paybill number, and Safaricom's Daraja API can notify your server of each payment at a callback URL. A VPS with HTTPS gives the POS a place to receive those confirmations and match them to sales.

Power cuts and patchy links

Tills on a UPS can keep selling through an outage, but a server in the same building goes dark with everything else. An off-site server waits for each branch to reconnect, whatever happens at any single location.

Questions

POS & Retail: your questions, answered

Will my POS keep working if the shop internet goes down?

It depends on how the POS is built. Offline-first systems, including Odoo POS once a session is open and most modern custom POS apps, keep selling and sync later. Tills that read a remote database directly will stop. Ask your vendor which model you have before moving the server off-site.

Can I connect my M-Pesa Till number to my POS?

Yes, through Safaricom's Daraja API. The C2B API sends a confirmation for each payment to a URL on your server, which your POS uses to mark the sale paid. You need a publicly reachable HTTPS address for that URL, which a VPS with a domain provides.

How does a POS connect to KRA eTIMS?

KRA offers system-to-system integration for businesses whose POS or ERP generates invoices, as well as simpler options for small traders. Your POS vendor or integrator handles the technical connection. A VPS gives the integration a stable, always-online home so invoices are not delayed by office outages.

Is it safe to open my POS database to the internet?

No. Exposing MySQL or PostgreSQL ports invites password-guessing attacks. Keep the database bound to the server or a private VPN such as WireGuard, and let tills connect through that tunnel or through an HTTPS API. Our support team can advise on firewall rules.

How many shops can share one POS server?

Many, as long as the server is sized for total tills and transaction volume rather than shop count. A few small shops fit on VPS V1 or V3; a chain with dozens of lanes and heavy reports belongs on VPS V4 or V5. Watch CPU during morning sync and evening closing.

Which plan should I choose for Odoo POS in one supermarket?

Start with VPS V2. Odoo runs several Python workers and PostgreSQL, and 8 GB of RAM handles a supermarket's tills, inventory and accounting comfortably. VPS V1 is too small for Odoo; move to VPS V3 for more cores and 16 GB of RAM as you add branches.

Also on VPS Hosting

Ready to host your pos & retail?

Plans from KES 2,000 a month, paid by M-Pesa or card.

Size your server