Approvals and segregation of duties
Configurable approval chains by document type, dual approval by two different supervisors for high-value actions, and exception reporting on segregation of duties.
Large businesses
Retail technology built for the governance and scale of large businesses
At scale, retail technology has to satisfy finance, IT, audit and operations at once. SalesLife is built so that every control is explicit: who can do what, what posts to the ERP, where the data lives and what happens when something fails.
Controls your auditors will look for
A complete audit trail
Overrides, voids, refunds, discounts and master-data changes are logged, and every posting to the ERP carries an audit reference.
Biometric and device security
Fingerprint or face approval for sensitive actions, templates held in the device's secure hardware, and till lock on idle.
Identity you already manage
Sign-in to SalesLife Central with Microsoft Entra ID, with roles for administrators, finance, operations and merchandising, and users scoped to their branches.
Integration without exposure
- Tills never hold ERP credentials and never call the ERP directly
- SalesLife Central validates, stages and posts to Dynamics 365 Business Central or SAP Business One, and a retry never creates a duplicate
- A queue of held documents with the reason for each, and a log of every call with redacted bodies
- Daily journals built from end-of-day batches, balanced per branch-day and reconciled to the ERP's acknowledgements
- Alerts by e-mail or signed webhook into your own monitoring
Scale and resilience
| Concern | How SalesLife handles it |
|---|---|
| Many branches | Master data flows from head office to every branch, and a head-office dashboard rolls up sales, tenders, labour, shrinkage and alerts. |
| A common version | Tills install from a signed package, with a policy that the fleet runs one version. |
| Outages | Branches keep selling offline, and queued pushes replay and are de-duplicated on reconnect. |
| Disaster recovery | Branch databases back up incrementally to SalesLife Central, and can be restored from it. |
| Data location | Run on a SalesLife-hosted stack, or in your own Azure subscription with your own database and Key Vault. |
| Compliance | KRA eTIMS signing in the sale, with a fiscal monitor and an escalation queue for breaches of the signing window. |
FAQ
Common questions
Can SalesLife run in our own Azure subscription?
Yes. A dedicated installation can run in your tenant, with your own database and Key Vault, and your own identity.
How is access controlled?
Through Microsoft Entra ID sign-in, role-based permissions, branch scope, supervisor and dual approval, and optional biometric approval at the till.
What does the audit trail cover?
Security overrides, master-data changes, approvals and every ERP posting, with request and response logs retained for a set period.
How do you avoid duplicate postings?
Every push is idempotent, so a replay after an outage is recognised and ignored.
Can we integrate with our monitoring tools?
Critical alerts can be sent by e-mail or by a signed webhook to your own systems.
Keep exploring
See SalesLife on your products, your branches and your ERP.
Book a live demo with a SalesLife retail specialist, or email hello@saleslife.com.