MyDukaan
Smart retail.
Better business.
Product EngineeringDigital SolutionsCustom Software
We build softwarethat holds up onthe shop floor.
SRR Enterprises is a product engineering practice. We build and run three of our own products — retail ERP, device financing, and scheme intelligence — for the high-volume, low-margin reality of Indian retail. We build custom software for clients to the same standard.
- 3
- Products Built
- 100%
- Client Focus
- Modern Tech
- Future Ready
- End-to-End
- Product Development
Who we are
We don't start from a feature list. We start from the counter, the ledger and the device in someone's hand.
Every product we own came out of the same method: find a specific, unglamorous operational problem in Indian retail or retail finance, build a focused system around it, and keep expanding from real field use rather than from a template.
That's why our retail ERP tracks individual IMEIs and calculates GST on the margin for a used device. Why our financing platform keeps enforcing when the phone has no network. Why our scheme engine reads a circular that arrived as a photograph on WhatsApp. None of those are features you arrive at from a whiteboard.
The same practice builds custom software for clients. Same engineers, same standard, same insistence on understanding the operation before writing the schema.
What we build
Capabilities we can point at a shipped product for.
Each of these is something our own products already do in production. Nothing on this list is aspirational.
Product engineering, 0 → 1
We take a business problem and turn it into working software — from the first conversation all the way to something your team actually uses every day.
Where we've done it
This is exactly how we built all three of our own products, from scratch.
Our products
Three products we own, in production.
We build focused, practical software for real business problems — running a retail store, financing and protecting a device, helping a retailer claim what a brand scheme actually owes them. These are three of our own products, built and used in production. They show the kind of software we build for our clients.
Retail ERP
MyDukaan
One retail ERP for every kind of shop.
A multi-branch retail ERP that brings billing, stock, purchase and accounts into a single system — built to work for any retail vertical, from mobile stores to pharmacies to grocery outlets, with unit-level IMEI/serial tracking where it matters most.
- Multi-branch billing, purchase and accounts
- IMEI / serial-level stock tracking
- GST-compliant used-device resale
- Structured import from your old system
- Keyboard-driven billing screens
- Mobile dashboard for owners
Explore MyDukaanWeb + Mobile
Actual product screenshot
Why it matters. MyDukaan replaces spreadsheets and disconnected billing tools with one connected system, reducing manual errors and giving owners real, current visibility across every branch.
Device financing
EMI Book
Finance the device. Keep the control.
EMI Book lets retailers offer device financing with real teeth: a financed phone's access can be remotely restricted or restored based on EMI status, with on-device schedules, offline enforcement and automated due-date reminders — reducing the risk of financing a device to a customer.
- Remote access control tied to EMI status
- On-device EMI schedule with paid/due tracking
- Enforcement that works offline
- Automated due-date reminders and auto-restriction
- Built-in customer KYC verification
- Multi-language on-device experience
Explore EMI BookWeb console + Android
Actual product screenshot
Why it matters. EMI Book turns device financing from a trust-based risk into a manageable, enforceable process — protecting the retailer's investment while keeping the customer informed at every step.
Scheme intelligence
Scheme Kya Hai
Know exactly what your scheme is worth.
Scheme Kya Hai turns brand scheme circulars into calculated, claimable earnings — tracking inventory device by device so a retailer can see exactly what they've earned, from a single IMEI all the way up to a total brand-level claim.
- AI-powered scheme extraction from circulars
- Per-IMEI, per-model, per-brand earnings
- Price-protection tracking for price drops
- Net Landing Cost calculation
- Independent retailers and multi-store chains
- Mobile-first, with an admin panel
Explore Scheme Kya HaiMobile app + Admin panel
Actual product screenshot
Why it matters. Scheme Kya Hai replaces guesswork with a clear, itemised earnings record — helping retailers claim what they're actually owed and helping brands see genuine, trackable scheme performance.
How we work
Five steps, and the first one isn't code.
This isn't a methodology we bought. It's the sequence that produced all three products on this page.
- 01
Understand the operation
We start at the counter, not the requirements document. What does a day actually look like, where does it break, and what is the person working around right now?
- 02
Model the domain honestly
The schema is the product. We model the real entities — a branch, an IMEI, a slab, a due date — before designing a single screen, because the wrong model costs years.
- 03
Build a focused core
A narrow system that does the essential job completely, rather than a broad one that does everything approximately. Vertical behaviour goes in as opt-in modules, not hard-coded assumptions.
- 04
Prove it in the field
Software for retail is judged at 8pm on a busy Saturday with a queue at the counter. We validate against real businesses under real conditions, including bad ones — no network, no patience.
- 05
Extend from real use
Every product we own grew from what the field asked for next. IMEI tracking, margin-scheme GST, offline enforcement, per-device earnings — all of it came from use, not from a roadmap workshop.
Engineering capability
What our systems do, not which logos we own.
A framework list tells you nothing about whether software will hold. These are the properties our platforms actually have.
01
Interfaces
- Browser-based billing and admin consoles
- Native Android device software
- Retailer-facing mobile applications
- Keyboard-first, high-frequency data entry
- Multi-language on-device screens
- Printable, compliance-shaped PDF documents
02
Platform
- Large, versioned REST API surfaces
- API gateway with token-based access control
- Multi-tenant data scoping
- Role-based access control
- Platform-admin roles separated from tenant roles
- Configuration-driven tenant onboarding
03
Data
- Migration-controlled relational schemas
- Unit-level (IMEI / serial) traceability
- Structured legacy import with dry-run preview
- Calculation results persisted for audit
- Document lifecycle and approval states
- Automatic accounting posting rules
04
Intelligence
- AI extraction from PDFs and images
- Structured output from unstructured circulars
- Dedicated calculation engines, isolated from CRUD
- Slab, target-group and variant-level rule evaluation
- Deep-to-top rollups: device → model → brand
- AI-assisted workflows inside the ERP
05
Automation
- Scheduled due-date and overdue processing
- Automated reminder and notification pipelines
- Push-based device command channel
- Offline-capable, on-device rule evaluation
- Draft → review → publish validation gates
- Inactivity and exception detection
06
Integration
- Third-party identity / KYC verification
- Cloud-hosted deployment
- Device registration and licence approval
- Distributor and multi-level account hierarchies
- Companion mobile endpoints for dashboards
- Document-level export and print pipelines
We describe our stack at this level publicly on purpose. Exact versions, service topology and internal endpoints are the kind of detail that helps an attacker more than it helps a client — we'll go as deep as you need under NDA.
Why work with us
Four reasons, each of which we can show you.
We own products, not just tickets
Three systems in production that we designed, built, shipped and still run. We've lived with our own decisions long enough to have opinions about them.
Domain depth you can't fake
Margin-scheme GST on a used handset. IMEI-level stock. Scheme slabs that vary by colour. This is knowledge earned from the sector, not read from a spec.
Built for bad conditions
Our device software enforces its rules with no network at all. We assume the connection drops, the phone is old and nobody has time to read an error message.
We take switching seriously
A system nobody can migrate onto is a system nobody adopts. We build import paths with previews because the first day matters as much as the hundredth.
The people
A small practice. The people who design it are the people who build it.
Every product on this page was taken from problem to production by the same group — no handoff between a design team and a delivery team, no layer of account management between you and the person writing the code.
Questions
Before you write to us.
01What kind of software do you build?
Operational systems: the software a business runs on rather than the software it markets with. Retail ERP, financing platforms, calculation engines, device software, admin consoles and the APIs behind them.
02Do you build custom software for clients, or only your own products?
Both. The three products on this page are ours — built, shipped and run in-house. The same practice takes on client work, and those engagements are covered by confidentiality, which is why you won't find client names here.
03Can you handle design and engineering end to end?
Yes. Each of our products was taken from problem definition through domain modelling, interface design, backend, mobile and deployment by the same team.
04What technologies do you work with?
Web applications, native Android, versioned REST APIs behind gateways with role-based access control, migration-controlled relational databases, AI-assisted document pipelines, scheduled job infrastructure and cloud deployment. We describe our stack at this level publicly by policy.
05We already run an older system. Can we move?
That's a problem we've solved for ourselves. MyDukaan ships structured import for catalogue and records with a dry-run preview, specifically because the cost of leaving an old ERP is what stops most businesses from switching.
06How does a project usually start?
With a conversation about the operation, not the technology. We want to understand what a working day looks like and where it currently breaks. If we don't think we're the right people to build it, we'll say so.
Have a system that needs building?
Tell us about the operation you're trying to run. We'll tell you honestly whether we're the right people to build it.
Contact
Tell us what you're trying to run.
Not a brief, not a spec. Just the operation, and where it currently breaks.
We read every message ourselves. Expect a reply from an engineer, not a sales sequence.