Sell on Android POS
Bring item selection, payment recording, stock updates and receipt handling into one merchant workflow.
Designed for Kenya eTIMS workflows
A country workflow for connecting everyday Android POS operations with eTIMS processes, clear invoice status and local deployment support.
Country profile
KenyaFiscal workflow
eTIMS
Integration paths
VSCU or OSCU
Receipt outcome
QR receipt
Delivery model
Local support
Deployment requirements
Every Kenya deployment still requires confirmation of the applicable integration, approval, device and support requirements. This page does not claim KRA approval or certification.
Connect the sales workflow to eTIMS follow-up.
The product path begins with simple selling and makes fiscal processing, offline status and receipt outcomes easier to follow.
Follow the appropriate eTIMS path
Plan a VSCU or OSCU workflow according to the merchant system and confirmed integration route.
Produce a clear QR receipt
Handle the expected invoice structure and QR receipt outcome within the confirmed fiscal workflow.
Keep offline work visible
Save eligible work locally, show pending status and follow the approved retry or support path when connectivity returns.
Plan the full local delivery path.
A Kenya rollout needs merchant qualification, a confirmed fiscal route, tested devices and an accountable local support process.
- 01
Confirm the merchant
Review the business, locations, invoice volume and current selling process.
- 02
Confirm the fiscal route
Validate the applicable eTIMS, VSCU or OSCU path before promising a deployment.
- 03
Validate hardware and printing
Check the Android device, printer, network conditions and receipt workflow.
- 04
Validate with local support
Train operators, observe sync status and keep escalation context close to the merchant.
Ongoing rule support, not a one-time setup.
Sales experience across multiple countries informs a repeatable process for reviewing requirements, updating country rules, validating product behaviour and guiding local delivery. Exact integrations and deployment scope are confirmed for each customer.
Local support context
Keep the merchant, partner and product team connected.
Deployment guidance should capture device setup, invoice status, offline retries and escalation details so issues can be reviewed with the right context.
Discuss a Kenya deployment with the right scope.
Bring your merchant workflow, eTIMS path, devices and local delivery needs to the conversation.