Srivari Healthcare is an authorised dealer for healthcare equipment in Chennai, delivering and installing products from brands including GE, Praxair, Fisher & Paykel, Welch Allyn and AirSep — CPAP and BiPAP machines, non-invasive ventilation, oxygen concentrators and face masks — for doctors, hospitals, healthcare units and international clients.
The business runs on a mix of outright sale and rental of the same equipment, which is exactly the case a spreadsheet handles worst.
Businesses running Odoo with OdooBots
Srivari Healthcare runs equipment trading, rental, purchasing and sales on one customised Odoo system instead of a set of Excel workbooks. Inventory and warehouse hold the equipment, purchase requisitions and RFQs run through Odoo rather than through email, sales and contacts carry the customer and their history, and rental equipment is tracked as a managed asset rather than as a note against an invoice.
Equipment that is sometimes sold and sometimes rented is one of the clearest arguments for a single database: in a spreadsheet the same serial number ends up on two sheets that disagree, and nobody notices until a customer asks where their machine is.
Taken from the project itself rather than from a capability list.
ERP for inventory, warehouse, purchasing, sales and contacts, including rental equipment, purchase requisitions and customer history.
Odoo ERP implementation with customisation
Chennai, India
See every Odoo implementation case study, or the full Odoo ERP implementation service.
The database was a set of Excel sheets. Finding anything meant navigating from worksheet to worksheet, and as the business grew the record-keeping grew with it rather than getting easier.
Products, customers, purchases and stock were kept in Excel. Moving between worksheets to answer a single question was routine, and the answer was only as current as the last person to save the file.
The same facts were typed more than once because no two sheets shared a record. That is a cost that grows exactly in step with the business.
Looking up what a customer had bought before meant searching files rather than opening a record — which matters when the customer is a hospital asking about a machine they already have.
Equipment on rent needed tracking as equipment, not as a line on an invoice: which unit, with whom, and since when.
Every one of these problems was tolerable at the size the business started at. None of them was tolerable at the size it reached, which is the usual reason an ERP project starts.
The implementation covered inventory, warehouse, purchasing, sales and contacts, because the problem was not any one of those — it was that they were five separate files.
Equipment, spares and consumables held as real stock with locations, so what the system says is on the shelf is what is on the shelf. See Odoo Inventory.
Purchase requisitions and RFQs run inside Odoo, so a purchase begins from a recorded requirement and ends against a received quantity. See Odoo Purchase.
RFQ and invoice generation automated to the way this business actually buys and bills, rather than to a default that would have been edited every time.
Sales orders and customers on the same database as stock, so a quotation is written against equipment that exists. See Odoo Sales.
Doctors, hospitals, healthcare units and export customers as one contact list with their own history attached, instead of a shared address book.
Rental of equipment handled as part of the same system as sale, with the apps integrated rather than a separate rental file kept alongside.
Equipment, customers, purchases and rentals sit in one place. A question about a customer is answered from their record rather than from a search across workbooks, and stock figures come from the system that moved the stock.
products, customers, purchases, stock and rentals on one database rather than across Excel workbooks.
generated to this business’s requirement rather than typed each time.
sales, purchase and inventory reported from the same data.
the same equipment handled either way, with the apps integrated.
available when the customer is on the phone, not after the call.
What the client reports back, in their terms. We publish no percentages here because the project did not measure any, and a number we cannot stand behind is worth less than one we can.
The spreadsheets were replaced rather than supplemented. That is the change the business asked for, and the one the rest depends on.
Entering the same fact twice stopped being part of the process, which is where the time spent on data entry had been going.
Consolidated sales, purchase and inventory reporting, generated rather than assembled.
A complete rental management route for the equipment, integrated with the apps that hold the stock and the customer.
Purchase history retrieved from a record instead of a file search — the difference between answering a hospital now and calling them back.
The record-keeping no longer gets harder as the business gets bigger, which was the reason for starting.
What this implementation used, written up properly.
What Odoo covers in healthcare, and where it needs work.
Buying and selling the same goods, with stock as the centre of the business.
Stock, locations and the moves that keep the figure honest.
Requisitions, RFQs and receipts against the order.
Custom modules built to survive version upgrades.
How an implementation is run, phased and quoted.
If you are running trading, rental or equipment service out of spreadsheets, the first question is whether configuration alone can carry it. We will tell you before quoting, and the diagnosis call is free.
