Skip to content
MultiPOSRetail operations

Pricing

Pay for branches, not for the parts that should never have been optional

Row-level tenant isolation, the immutable audit log and the transactional stock ledger are in every plan. Upgrades buy you more of the business, not more of the safety.

  • Single branch

    One shop, one register, the full operational core.

    KES 4,900

    per branch / month

    Start free trial
    • Point of sale and register control
    • Inventory with immutable stock ledger
    • Customers, credit limits and receivables
    • M-Pesa STK push and payment methods
    • Sales history, receipts and CSV export
    • Up to 5 staff accounts
  • Most chosen

    Multi-branch

    Several branches under one ledger, with the buying side included.

    KES 12,900

    per business / month

    Request a demo
    • Everything in Single branch
    • Unlimited branches, warehouses and stock locations
    • Procurement: suppliers, RFQs, purchase orders, goods receiving
    • Quotations and sales orders with reservations and prepayments
    • Collection cases, promises to pay and reminder rules
    • Multi-currency with dated exchange rates
    • PDF and XLSX reporting
    • Unlimited staff accounts and custom roles
  • Self-hosted

    Your cluster, your database, your compliance boundary.

    Talk to us

    annual licence

    Contact sales
    • Everything in Multi-branch
    • Cluster deployment with immutable, promoted image tags
    • Isolated platform control plane with mandatory TOTP
    • eTIMS configuration support
    • Document vault with malware scanning
    • Priority support and onboarding
  • Prices exclude VAT. Billed monthly, cancel any time.
  • Every plan includes the immutable audit log and row-level tenant isolation — those are not upsells.
  • Self-hosted deployments run the same images as the managed service.

Questions

Common questions

Anything not covered here, ask us directly — we answer with specifics.

Can one person run several businesses from one login?

Yes. Accounts are global and hold membership in multiple isolated businesses. You sign in once, switch business from the app, and carry a separate role in each. The data behind them stays isolated at the database level.

What happens when the network drops mid-sale?

Checkout submission is idempotent. A retried submission resolves to the same sale rather than a duplicate, and the sale, its payments, inventory balances and stock ledger entries are written in a single transaction — so you never end up with a payment recorded against stock that never moved.

How is one business kept out of another's data?

Row-level security is forced on tenant tables, and the application runtime connects as a role that cannot bypass it. Tenant context is set per transaction. Isolation is a property of the database rather than a convention the application code has to remember.

Do you support credit customers and collections?

Customers carry credit limits and payment terms. Receivables track due dates with oldest-sale allocation, and overdue accounts can be worked as branch-owned collection cases with promises to pay, disputes, and configurable reminder rules.

Is stock tracked by batch, serial or expiry?

Optionally, yes — captured at goods receiving alongside supplier delivery-note references, accepted and rejected quantities and rejection reasons.

Can we self-host?

Yes. The whole stack runs in containers locally, and production cluster configuration is maintained in a separate deployment repository with immutable, promoted image tags. We share the full platform detail with self-hosting customers on request.

Not sure which

Tell us how many branches and we will tell you the number

No quote form that takes three days. Describe the operation and we will price it on the call.