What happens to my data if the internet goes down mid-sale?

Nothing is lost. KituBox ERP is offline-first by design - invoices, ledger entries and stock movements are recorded locally the instant they happen, then sync to the cloud (and to other devices on the same network via mesh sync) once a connection is available.

Does KituBox ERP handle KRA eTIMS compliance?

Yes - every invoice tracks its eTIMS signature status natively, starting in a pending-offline state until the Control Unit signs it. The VAT summary report flags exactly which invoices are still eTIMS-pending, so you always know your real compliance position.

Can two branches sell the same item offline without overselling stock?

Yes - stock changes are recorded as deltas rather than direct decrements, and those deltas merge deterministically once devices sync, so concurrent offline sales reconcile correctly instead of conflicting.

KituBox Product

KituBox ERP

The ledger core: invoices, stock and compliance in one book

The system of record behind the till - quotes become invoices, invoices become a real audit trail, and stock reconciles safely even when two branches sell offline at the same time.

Launch ERP

Offline→ Syncing→ Synced to cloud

erp.kitubox.co.ke

What's Inside

Built for How It Actually Gets Used

An audit trail, not just a spreadsheet

Invoices are append-only - a correction is a new document, never a silent edit.

Corrections are issued as credit notes referencing the original invoice, satisfying the KRA audit trail
Quotes, invoices, delivery notes, purchase orders and vendor bills as distinct, printable documents
Chart of accounts and a ledger dashboard summarising invoices, amounts due and sync state at a glance

Stock that can't double-sell

Two offline tills selling the same SKU at the same time is the scenario this was built to survive.

Base stock quantity is immutable except by confirmed cloud sync
Local sales and restocks append to a pending-deltas ledger instead of decrementing directly
Deltas sum deterministically on merge, so concurrent offline sales reconcile without conflict

Procurement, the other direction

Purchase orders and vendor bills close the loop from supplier to shelf.

Purchase orders tracked through to received stock
Vendor bills and a vendor catalogue with KRA PIN and payment terms
Item and customer catalogues shared across quotes, invoices and delivery notes

Money in, reconciled

M-Pesa and bank movements match against the ledger instead of living in a separate app.

Dedicated M-Pesa reconciliation screen against bank/ledger entries
Reports screen including a VAT summary that flags exactly which invoices are still eTIMS-pending
eTIMS fields live directly on the invoice, starting in a pending-offline state until signed

Syncs the way the POS does

The same mesh-and-cloud sync engine as the rest of the suite, visible in real time.

Peer-to-peer mesh status panel for device-to-device sync on the same premises
Cloud sync panel with a live pulse indicator for connection state

Localized for Kenya

Not a Global Template With KES Swapped In

KRA PIN fields, county and town data, M-Pesa as a first-class payment method, and statutory numbers (NSSF, SHIF, Housing Levy, NITA) are part of the data model, not an add-on - because KituBox ERP was built for Kenyan compliance from the first schema.

Browse All Screenshots