Sells through the outage
Cash sales, cash tender, credit-account sales and local stock lookup continue when the network drops. Sales sit on a local branch database, and failed pushes queue in an outbox and replay on reconnect.
SalesLife runs your tills, stock, procurement and finance in one platform. Cashiers keep selling through outages, M-Pesa and KRA eTIMS are built in, and every sale reaches your ERP through SalesLife HQ with a full audit trail.
SalesLife is built for African multi-branch operators: offline-first at the till, orchestrated through SalesLife HQ, and connected to the ERP, fiscal and payment systems you already depend on.
Cash sales, cash tender, credit-account sales and local stock lookup continue when the network drops. Sales sit on a local branch database, and failed pushes queue in an outbox and replay on reconnect.
M-Pesa STK Push and C2B, Airtel Money, card terminals (Pesapal, EazzyPay), cash, gift cards and loyalty points, with split tender in one transaction.
Sales and refunds are signed through a local VSCU agent, with the fiscal QR stored on the document. Unsigned invoices queue offline and are retried automatically.
SalesLife HQ validates, stages and posts to Dynamics 365 Business Central or SAP Business One idempotently. Branch tills never hold ERP credentials.
Twenty-two functional modules in six areas, from the first scan at the till to the posted ledger entry in your ERP.
Cash sale, self-checkout, returns and documents.
Purchase orders, receiving, transfers and production.
Receivables, payables, tax and settlements.
HQ sync, ERP, fiscal, payments and partners.
Reports, dashboards and local-first AI.
Access control, approvals and audit.
Six everyday journeys, from the first scan at the till to the posted entry in your ERP. Choose one to follow it step by step.
From the till to the ledger, with fiscal signing and sync in step.
Scan items, apply promotions and loyalty, with supervisor gates on discounts and price overrides.
Cash, card, M-Pesa STK or Airtel Money, alone or split across tenders.
The sale is signed through the local VSCU agent and the fiscal QR is stored. If it cannot be signed, it queues and retries.
Print it, or send it by SMS, WhatsApp or email.
The branch pushes the sale to HQ, which validates and stages it. Failed pushes wait in the outbox.
HQ posts to Dynamics 365 Business Central or SAP Business One once, with audit references.
Branch procurement, reconciled to your ERP through HQ.
Create a supplier purchase order. Reorder suggestions come from rules and the replenishment agent.
Approval chains per document type, with dual approval for high-value actions.
Receive against the PO, in full or in part, with batch or serial capture. Stock posts to the warehouse.
Three-way match of PO, goods receipt and supplier invoice, with a variance queue to resolve.
Pay posted invoices with a method and reference. AP ageing stays current.
PO publish, receipt confirmation and AP invoice posting flow to Business Central or SAP Business One.
Till close, reconciliation and ledger posting without a month-end scramble.
Count each tender, record the variance and sign the cashier out.
Session sales, tender mix and VAT totals in one report.
Financial close batches are reviewed before they go up.
Match M-Pesa paybill payments, Safaricom settlement files and bank or PesaLink settlements.
End-of-day financial batches and till-close events are pushed to HQ.
HQ posts the day to the ERP, and the month-end POS-to-ERP report confirms they match.
Controlled at the till, correct in stock and in the ledger.
Look up the original receipt, choose the lines being returned and record a reason code.
A no-receipt return needs a supervisor, and high-value actions can need two.
Refund the tender, or exchange for new items in one transaction.
Where required, a fiscal credit note is signed for the refund.
Returned items go back into stock, or are adjusted for damage.
Refunds and credit memos are pushed to HQ and posted to the ERP.
Cashiers keep selling, and everything catches up when the connection returns.
Cash sales, cash tender, credit-account sales and local stock lookup continue on the branch database.
M-Pesa STK and card terminals wait for the connection. Cash and credit carry on.
Unsigned invoices wait in the offline queue.
Pushes to HQ that fail are queued locally, with retry.
Retries start and fiscal signing resumes.
The outbox replays to HQ and on to the ERP. A screen resolves any master-data conflicts.
From a customer's phone to your branch, with loyalty at the till.
Live catalogue, prices and promotions match the till.
Pay now with M-Pesa, or pay at pickup.
The order posts through HQ to the branch fulfilment queue, with no re-keying.
The branch fulfils pickup or delivery from its queue.
Push notifications confirm payment and pickup readiness.
The member scans the till card to earn and redeem points at the register.
Branch tills never call your ERP directly. SalesLife HQ validates every document, stages it, and posts it idempotently to Dynamics 365 Business Central or SAP Business One, so a retry never double-posts.
| Flow | SAP Business One | Dynamics 365 Business Central |
|---|---|---|
| Master data | Items, business partners, price lists and warehouses via HQ pull workers | Items, customers and vendors via HQ |
| Sales | A/R invoices, incoming payments and inventory issues from POS sales | Cash sale push and order pull via HQ |
| Procurement | PO publish, GRN to goods receipt PO, AP invoice posting | Purchase documents via HQ staging |
| Production | Work order and production posting for food-scale and kitting | Assembly orders via HQ |
| Reconciliation | Month-end POS-to-ERP report, idempotent posting with audit refs | Integration mapping workbook |
A whitelabeled mobile commerce app that extends your operation beyond the till. Each client gets a fully branded app, with logo, colours, stores and membership programme, on the same engine that runs your POS, HQ and ERP.
Screens shown are from a demonstration tenant. Production apps carry each client's logo, colours and membership programme name.
Inference runs on the till PC or a branch appliance, so customer data does not need to leave the store. AI is off by default, and agents propose while people approve.
Suggests reorder quantities from sell-through velocity, reorder points and days of cover, with a plain-language rationale.
Flags refund spikes, void rates, discount abuse, till shortages and cashier concentration, with a ranked factor list.
Ask questions in plain English about sales, top products, low stock and refunds. Read-only tools, it never writes.
Margin-erosion alerts and basket promotion ideas. Never writes prices on its own.
Explains eTIMS queue failures, prioritises retries and summarises withholding tax.
Guides enrolment, shows tier progress and explains redemption rules.
On reconnect, prioritises conflict resolution and outbox replay.
In-app help for cashiers, searched from your local procedures pack.
The same platform adapts to the way each sector sells, stocks and settles.
Fast lanes, self-checkout and a queue-busting handheld for the busy floor. Loyalty, gift cards and delivery partners sit beside branch procurement and cycle counts, with every sale posted to your ERP.
Weighed items integrate with scale hardware. Sold PLUs net inventory through automatic work orders and recipe BOMs, ideal for supermarkets, butcheries and deli counters.
Batch inventory with first-expiry-first-out picking and expiry filters, serial traceability, and SMART member card lookup with hospital claim files captured at the till.
Product variants and barcodes, lay-by with instalment schedules, gift cards with partial redemption, loyalty tiers, and online orders with pickup and delivery queues.
Credit-account sales with limit checks at the till, quotations that convert to sales orders or invoices, AR ageing and statements, and a full purchase-to-pay cycle with three-way match.
KRA eTIMS signing happens inside the sale through a local VSCU agent. The fiscal QR payload is stored on the document, and nothing is lost if the signer is briefly unreachable.
One Windows package, one first-run wizard, and a branch server model that keeps every till in step.
Deploy the MSIX package with a Demo or Production profile. The first-run wizard sets the database, till code, currency, HQ URL and an optional AI endpoint.
Link the branch to SalesLife HQ, map the ERP posting, and set your payment and eTIMS details. Master data pulls down to every till.
Till 1 hosts the branch PostgreSQL database and extra tills discover it and register. Fleet-wide, every till runs the same version.
Short, honest videos from our YouTube channel: who uses SalesLife, and what a retailer says after going live.
Share these with your finance, IT and operations teams. Both are free to download.
Every module in detail: sales and till, procurement, finance and tax, HQ sync, SAP B1 and Dynamics 365 BC integration, AI agents, security and deployment.
Download the guideThe four customer journeys, how the app connects to POS, HQ and ERP, and how whitelabel deployment works for each retail banner.
Download the brochureGuides to the topics retailers search for most: tax compliance, payments, ERP integration, offline trading and more.
Through SalesLife HQ. Branch tills sync to HQ, and HQ validates, stages and posts documents to your ERP with idempotent workers. The till never holds ERP credentials and never calls the ERP directly. Business Central and SAP Business One each have their own mapping for master data, sales, procurement and production.
Cash sales, cash tender, credit-account sales and local stock lookup continue on the branch database. Things that need the network, such as M-Pesa STK push, card terminals, HQ sync and cloud fiscal signing, pause until connectivity returns. Failed pushes queue in an outbox and replay on reconnect, and unsigned eTIMS invoices queue and retry.
Yes. Sales and refunds are signed through a local VSCU agent following the KRA specification, and the fiscal QR payload is stored on the document. There is an offline queue, an escalation path for SLA breaches, and a simulator mode for testing without a live VSCU.
Cash, card terminals (Pesapal, EazzyPay and a generic gateway), M-Pesa STK Push and C2B, Airtel Money STK, bank transfer, vouchers, instalments, gift cards and loyalty points, in split tender if needed. Settlement reconciliation covers M-Pesa, bank and PesaLink.
SalesLife POS is a Windows application, packaged as MSIX, for Windows 10 and 11 tills. It supports live food-scale weight, a second-monitor customer display, a self-checkout lane and a queue-busting handheld companion on the same PC. Share your hardware list and we will confirm it during scoping.
No. AI is disabled by default and runs local-first on the till PC or a branch appliance, so customer data does not need to leave the store. It never blocks checkout, background runs wait until the till is idle, and agents only propose. Actions like price changes and write-offs need human approval.
Yes. The SalesLife Customer App is whitelabeled per retail banner with your logo, colours, stores and membership programme. It shares master data and loyalty with the till through HQ, and orders arrive in the branch fulfilment queue.
Tills install from a signed MSIX package. A first-run wizard sets the database, till code, currency and HQ URL. One till hosts the branch database, other tills discover it, and every till in the fleet runs the same version. Encrypted backups and an operations-health view are built in.
Tell us about your business. A SalesLife retail specialist will walk you through the till, checkout, M-Pesa, eTIMS and HQ sync in a live environment, and show the Customer App configured with your logo and stores.