Sales Force Automation for Sri Lankan FMCG and pharma distribution.
Vendix is an SFA system built by a team in Colombo for the way distribution actually works here: routes that lose signal, sales through a distributor network rather than a single warehouse, cheque cycles that decide the next order, and field teams who would rather work in Sinhala or Tamil than in English.
Why imported SFA tools struggle here
Sri Lankan distribution is not a smaller version of a European or North American market. Four differences break tools that were designed elsewhere, and each one is a design decision in Vendix rather than a configuration workaround.
Coverage drops the moment a route leaves town
Most SFA tools assume a live connection. On an up-country or coastal route that assumption fails several times a day, and a rep who cannot save an order stops using the app and goes back to a notebook.
Vendix is offline-first by design, not as a fallback mode. The app reads and writes locally and syncs in order when signal returns.
How the Android app worksDistribution runs through distributors, not a single warehouse
Imported tools model one company selling to one set of outlets. Here the chain runs through distributors with their own vans, stock and operators, and head office needs to see through that layer without owning it.
Distributors, their operators, warehouses and stock are modelled directly, so sell-in and sell-out are both visible and reps can span more than one distributor.
Multi-tenant architecturePayment is a cycle, not an event
Cash, cheques, credit terms and ageing decide whether the next order should even be taken. A tool that treats an invoice as paid on issue reports revenue that has not arrived.
Cheques carry status through to clearing and an outlet balance moves when money clears, not when a promise is made. The rep sees the real position before the next order.
How transactions are processedHead office needs Monday numbers on Monday
Reporting that depends on someone exporting spreadsheets is always a week behind, and the week it matters most is the week nobody has time to export.
Reporting runs off its own analytics database that refreshes on a schedule, so a manager opens a report rather than requesting one.
Reporting and analyticsYour reps work in their own language
Vendix ships in English, Sinhala and Tamil, and each user chooses their own. A rep in Jaffna works in Tamil, a rep in Matara works in Sinhala, and head office reporting stays in English, from the same data on the same day. The Android app and the web portal are both translated, not just the login screen.
Portuguese and Arabic ship too, so a group operating beyond Sri Lanka does not need a second platform.
Rupees and Colombo time, everywhere
Currency and timezone are tenant settings, applied consistently across the portal, the Android app, exports and the AI assistant. Amounts show in Rs. and timestamps sit in Asia/Colombo, so an evening sale in Kandy is dated that evening rather than being pushed to the next day by a server clock in another region. It sounds small until a month-end total lands in the wrong month.
Common questions
Does Vendix work when reps lose mobile coverage?
Yes. The Android app is offline-first: every screen reads from an on-device database, never directly from the network. A rep can take orders, record collections and close visits with no signal at all. Work queues locally and syncs in creation order when coverage returns, so nothing is lost and nothing arrives out of sequence.
Is the interface available in Sinhala and Tamil?
Yes. Vendix ships in English, Sinhala and Tamil, alongside Portuguese and Arabic. Each user picks their own language, so a rep can work in Sinhala or Tamil while head office reporting stays in English. Both the web portal and the Android app are translated.
Does it handle rupee amounts and local dates correctly?
Yes. Currency symbol and timezone are per-tenant settings. Sri Lankan tenants run on Rs. and Asia/Colombo, so a sale recorded at 6 p.m. in Kandy is dated that evening, not pushed to the next day by a server clock sitting in another timezone.
Can it manage a distributor network rather than only our own reps?
Yes. Distributors are first-class in the model, with their own operators, warehouses and stock. You can see sell-in and sell-out across the network, and reps can be mapped to more than one distributor where territories overlap.
How do you handle cheque payments and credit?
Collections record cash and cheques separately, cheques carry their own status through to clearing, and outlet outstanding balances move only when a payment actually clears. Credit limits and ageing are visible to the rep before they take the next order.
How long does implementation take?
It depends on how clean your master data is rather than on the software. Talk to us about your product list, outlet base and distributor structure and we will give you an honest estimate rather than a brochure number.
See it on your own routes
Thirty minutes, using a slice of your own product list and route plan rather than a generic sandbox. Tell us how your distribution is structured and we will show you the parts that matter to it.