a product of Khosha Systems
India has around 1.5 lakh mobile and consumer-electronics retailers. They put a phone in every hand, and most of them run the counter on a paper register and a spreadsheet. We built them an operating system. This is the reasoning behind it, and what it took.
retaileros.in is where the product is sold. This page is about why it exists.
IMEI & serial lifecycleEvery unit, from purchase to service
lakh retailers
Mobile and consumer-electronics counters across India, from metro malls to a single shop in a small town.
Khosha Systems estimate, 2026.
The phone is the essential tool of modern India. It is the bank, the ticket, the classroom, the shopfront and the ID card. Almost nobody buys one from a factory. They buy it from a counter near home, from someone who sets it up, moves their chats across, sells the case, handles the exchange and takes the repair when the screen cracks.
Those counters are mostly independent: a family, a few staff, one or two stores, a WhatsApp number and a notebook. They serve the whole country, and the software industry had served almost everyone but them.
Bangalorewhere RetailerOS is built
A handset is not a SKU. Two identical boxes are two different devices with two IMEIs, two warranties and two histories. Generic billing software treats them as a quantity, so evenings go on matching IMEIs to invoices by hand, and the mismatch is found at the audit, months later.
Before: The IMEI typed into a notes field, or written in the register.
Samsung, Vivo, Oppo, LG and the banks run cashback, exchange bonuses and target slabs that change by product and by week. The margin on a handset often sits in the scheme rather than the price. Tracked in Excel and reconciled on a Sunday, claims are missed and the money stays with the distributor.
Before: A scheme sheet, a target the floor cannot see, a claim filed late.
Billing at an electronics counter means HSN codes, CGST and SGST, an exchange value, a scheme line and a payment split across UPI and cash, while a customer waits and the next one is at the door. The bill then has to reach the customer, who will ask for it again on WhatsApp in six months.
Before: A printed slip, a photo of it, a search through old chats.
Once there are two counters, the owner is phoning each one at closing time: what sold, what is in stock, whether the discount was approved. Stock sits in one branch while the customer stands in the other.
Before: Separate books per store, assembled by hand at the end of the month.
The problem was never that retailers refuse software. It was that software had never been written in the shape of their day.
Four things now exist together that did not ten years ago. They are the reason a counter can be run from a phone, by the retailer, without an IT team.
The retailer’s own phone is a scanner, a camera and a terminal. Software for the counter should run there first, not on a desktop in the back room.
Customers already live there. A bill that lands on WhatsApp is never lost and never asked for twice.
UPI, HSN codes and structured invoices turned the bill into a record rather than a slip of paper. Software can finally do the arithmetic.
One live ledger across every store, and models that draft a festival creative from a sentence. What once needed an IT team is now a subscription.
Beneath a counter that bills in about thirty seconds there is a system that has to be right every time. The engineering, in the order a device meets it.
Scanned in by IMEI or serial against a purchase order; the supplier is on the record.
InventoryHeld per store, with low-stock and dead-stock flags and a reorder point.
StoresIMEI captured per line, GST computed, the scheme applied, payment split.
Sales DeskPrinted on thermal and sent on WhatsApp in the same step.
WhatsAppThe scheme sale becomes a claim with product, IMEI, scheme and amount.
SchemesRepair job cards and warranty sit on the unit’s own history.
RepairsWhat RetailerOS does the moment a sale is rung up, without anyone asking.
0.4 seconds from payment to the fifth update. Nobody at the counter has to ask.
Every unit is a first-class record from the day it is scanned in: supplier, purchase order, store, the sale it went out on, the customer, the warranty window and any repair that follows. Search an IMEI and you get the chain of custody, whichever branch handled it.
The Sales Desk is built for the fastest billing hand at the counter: scan, sell, print thermal, send on WhatsApp. HSN codes are pre-loaded, CGST and SGST are computed as the bill builds, exchange and scheme lines sit on the same invoice, and payment can be split across UPI, cash, card and khaata.
Each store keeps its own stock, cash register, staff and invoice numbering, and the owner sees all of them together. Head office moves stock between branches, approves a discount request raised at a counter, and compares stores on sales trends, staff leaderboards and scheme returns.
A counter has no IT team and no fibre line. RetailerOS is built to run on the retailer’s own phone and on a slow 2G connection, with every screen available in Hindi and three more languages, set per staff member. The same system puts the store online for its customers, with brands, categories and stock counts drawn from the live ledger.
The store’s own online shop, served from the same stock ledger.
The scheduled work runs itself: a receipt on WhatsApp at payment, a repair status when it changes, a follow-up sequence after a sale, a reminder before a warranty ends. KAI, Khosha’s AI product, works alongside these systems. In RetailerOS it shows up where a counter needs it: describe an offer in plain words and the Marketing module generates the banner or post, ready to share on WhatsApp.
A scheme is money a brand or a bank pays the retailer for selling a particular product in a particular window: a cashback, an exchange bonus, an instant discount, a bonus for crossing a target slab. Dozens run at once, they change weekly, and the margin on a handset is often in the scheme rather than the price.
Claiming one needs the product, the IMEI or serial, the scheme and the amount, for every eligible sale. Done by hand, that is a spreadsheet reconciled at quarter end, and whatever is missed stays with the brand.
Khosha Systems builds operating systems for real industries: Real Desk for real-estate sales, Passage for immigration practices, Liquor OS for liquor retail. RetailerOS is the one we run end to end, from the first line of code to the support line on WhatsApp.
That makes it our proof. When we say we study the layers of a business and then build software in the shape of its day, RetailerOS is where anyone can check the claim: twenty-three modules on one login, built around how an electronics counter actually works, used by retailers every day.
Every method we bring to a client engagement was tested here first: the layer-by-layer study, mobile-first engineering, a single live ledger, WhatsApp as the delivery channel, and KAI working inside a real workflow.
Built for Indiaretaileros.in has the modules, the solutions by store type and a counter you can set up today. This page was the why. That one is the what.
We're a team of six engineers, designers and strategists building systems together. Every business has layers, and every engagement has taught us how they connect. We engineer software that outlives the people who built it. If something here sounds like your business, we'd be glad to talk it through.
