What blood bank software costs in India, and what drives the figure
We do not publish a starting price, and this page explains why rather than burying it. What it does give you is the whole cost structure: the five variables every vendor in this category prices on, the seven line items that are usually left out of the first number you are shown, and how to compare two quotes that are not measuring the same thing. Written so you can build a three-year budget before you speak to anybody, including us.
Why there is no price on this page
Because a single figure would be wrong for almost everybody who read it. The same software, at a two-licence trust running four hundred bags a month with three analysers and camp collection, and at a single-licence charitable centre issuing whole blood, is not the same amount of work to implement and is not the same amount of system. Publishing one number means publishing the higher one and losing the smaller centre, or publishing the lower one and quoting past it in every real conversation. Both are worse than saying so.
There is a second reason, and it is the more honest one: a list price in this category is almost never what anybody pays. What actually determines your invoice is how many licences you hold, how many bags pass the counter, which modules you switch on, how much history has to be migrated, and how much training the floor needs. A headline figure prices none of that, which is why aggregator listings that publish one for us are quoting a number we did not give them.
What we will do is quote inside one working day of a call, itemised, with year two and year three stated on the same page as year one. If you need a figure for a budget line before that call, tell us your licence count and monthly bag volume and we will give you a range in writing.
The five variables every vendor prices on
Have these five answers ready and any vendor in the category can quote you properly. Without them you will be quoted a tier and corrected later.
Licences and centres
How many blood bank licences you hold, and how many physical storage centres sit under them. This is the primary unit of pricing across the category, because a second licence means a second set of registers, a second inspector and separate statutory reporting.
Bags a month
Monthly collection and issue volume, which is a proxy for both the load on the system and the size of your team. A district hospital blood bank and a thalassaemia day-care can hold the same licence and differ by an order of magnitude here.
Modules switched on
Component preparation, analyser interfacing, camp management on tablets, billing and processing charges, ABHA donor identity, an API to a hospital system. A centre that issues whole blood and reports monthly needs a fraction of what a component-preparing NABH aspirant needs.
History to migrate
Years of donor records, deferrals and stock in spreadsheets or a legacy desktop package. Migration is the single most variable line in any quote, because the cost is set by how consistent your existing data is, which nobody can assess from a brochure.
Training and go-live
How many staff across how many shifts, and whether they are moving from paper or from another system. Moving from paper takes longer and is where an under-priced implementation quietly fails: the software goes live and the registers keep being written by hand alongside it.
And the one nobody mentions
Your analyser models. Interfacing a grouping or TTI analyser is either supported already, or a development item with a timeline. Ask before contract, because “we can integrate that” and “that is integrated” are a quarter apart.
Four ways this category charges, and how they diverge by year three
Two quotes built on different models are not comparable at the headline. Normalise both to a three-year total before you put them side by side.
One-time perpetual licence
You buy the software once, usually with an annual maintenance contract at a percentage of licence value from year two. Attractive as capital expenditure and to a committee that prefers to own. What to check: whether the AMC is optional in practice or in name only, whether a statutory format change arrives inside it or as a paid upgrade, and who owns the server, its backups and its eventual replacement. The three-year total is licence plus two AMCs plus hardware, and it is frequently the higher of the four.
Annual subscription per centre
A recurring fee covering the software, hosting, updates and support, priced by licence and usually banded by volume. Predictable, and it puts the vendor on the hook for the statutory changes. What to check: what the renewal escalation is, whether the band you are quoted has a bag ceiling you will cross, and what happens on the day you stop paying, specifically in what format and how quickly you get your records out. This is how RAKT is priced.
Per named user
Charged by login. The headline looks lowest of the four and diverges fastest, because a blood bank running three shifts needs more accounts than it has terminals, and the cost of adding the night technician becomes a decision somebody makes on a Tuesday. It also creates a direct incentive to share credentials, which destroys the audit trail an NABH assessor will ask to see. If you are quoted per user, count the accounts you actually need across every shift and re-ask.
Per bag or per record
Usage-based, scaling with collections. Genuinely fair for a small or seasonal centre and the hardest of the four to budget, because the invoice moves with a camp season you cannot forecast precisely. What to check: whether the meter counts bags collected, components prepared or units issued, since component preparation multiplies one collection into three or four billable records, and whether there is a cap.
Seven line items missing from the first number you are shown
Ask for each of these in writing before contract. Every one of them has arrived as a surprise at a blood centre we have since migrated.
- Migration of existing data. Sometimes bundled, often quoted per record or per year of history, occasionally declined entirely, which means your donor base restarts at go-live and you lose the deferral history that keeps donors safe.
- Training, and re-training. The initial sessions are usually included. Ask what a new technician costs to train in month eight, because blood bank staff turn over and an untrained user is how a system reverts to paper.
- Hardware. Label printers, barcode scanners, a tablet for camps, sometimes a server and a UPS. Not software cost, always project cost, and routinely absent from the comparison sheet.
- Annual maintenance or renewal escalation. On a perpetual licence, the AMC percentage and what it covers. On a subscription, the renewal increase. Get the number for year three, not the assurance that it is nominal.
- Statutory and eRaktKosh changes. Formats change. Ask whether a change is absorbed or billed as customisation, and get the answer in the contract rather than on the call.
- Integration work. Analysers, a hospital information system, an SMS or WhatsApp provider, a payment gateway. Each is either already supported or a scoped item with a price and a date.
- Exit. What it costs and how long it takes to get a complete export in a format you can open. Schedule F retention obligations outlast every software contract you will sign, so this is a compliance line, not a hypothetical.
A quote that names all seven is usually the more expensive-looking one and the cheaper one to own. Two quotes where only one of them names them are not comparable, and the gap is almost never in the buyer’s favour.
Per centre, by what you run, quoted after we have seen it
RAKT is an annual subscription per blood centre. The figure is set by the five drivers above: licences and centres, monthly bag volume, the modules you switch on, the history to migrate and the training the floor needs. It includes hosting, continuous updates, statutory and eRaktKosh format changes, and support from the people who implemented you rather than a separate helpdesk. There is no per-user charge, deliberately: charging by login makes a blood bank ration accounts across shifts and share credentials, and a shared credential is the end of the audit trail an assessor asks for.
What is quoted separately, because it is genuinely variable and pretending otherwise would mean padding everybody’s subscription to cover the worst case: migration of existing history, and hardware such as label printers and camp tablets. Both are itemised in the same document as the subscription, with year two and year three stated.
Data export is not a chargeable item and never will be. Your registers are subject to statutory retention, and a vendor who can invoice you for access to your own compliance records has a hold over you that no blood centre should agree to.
Cost questions we get asked
How much does blood bank software cost in India?
The honest answer is that it depends on five things and that any single figure you find online is either one vendor’s highest tier or an aggregator’s estimate. Cost is set by how many licences and centres you run, monthly bag volume, which modules you switch on, how much history has to be migrated, and how much training the floor needs. Build a three-year total including migration, hardware, renewal escalation and exit before comparing two quotes.
Why will you not publish a starting price?
Because one figure would be wrong for nearly everyone reading it. A two-licence trust running four hundred bags a month with three analysers and camp collection is a different amount of system from a single-licence centre issuing whole blood, and publishing one number means either losing the smaller centre or quoting past the figure in every real conversation. We quote itemised, inside one working day of a call, with years two and three stated.
Is a one-time licence cheaper than a subscription?
It looks cheaper at the headline and frequently is not by year three. Add the annual maintenance contract, the server and its replacement, backups somebody has to verify, and paid upgrades when a statutory or eRaktKosh format changes. Normalise both options to a three-year total including hardware. Perpetual licensing genuinely wins where connectivity is unreliable and you already have on-site IT.
What is usually excluded from a blood bank software quote?
Most often: migration of your existing donor and stock history, training staff hired after go-live, hardware such as label printers and camp tablets, the year-three renewal figure, absorbing statutory format changes, integration with your specific analyser models, and the cost and format of a full data export if you leave. Ask for all seven in writing before contract.
Do you charge per user?
No. RAKT is priced per blood centre, and named accounts are unlimited within it. Per-user pricing pushes a blood bank running three shifts to ration logins and share credentials, and a shared credential means no action can be attributed to a person, which is precisely the evidence an NABH assessor asks to see.
Is there a free or trial version?
There is no self-serve free tier, because a blood bank management system that has not been configured to your registers, components and state return format would not tell you anything useful about it. What we do instead is run the demo on your own workflow, using your register formats, your analyser models and your state return, then give you a scripted trial account afterwards if you want the floor to try it.
Does the price include eRaktKosh integration?
Yes, eRaktKosh submission is part of the subscription rather than an add-on, and so is absorbing schema changes when the national format moves. It is worth asking every vendor this specifically: an integration billed as customisation each time the format changes becomes an annual line item nobody budgeted.
Tell us your licence count and monthly bags
That is enough for a written range before you spend time on a demo. A full itemised quote, with years two and three, follows one call.