1Why there is no standard price.
No regulation or regulator publishes a price for laboratory software. What the regulations fix is the work a regulated laboratory must do around any system it uses for GMP records. In the EU, Annex 11 says “the application should be validated; IT infrastructure should be qualified”, and applies to all computerised systems used in GMP-regulated activities.¹ In the US, 21 CFR 211.68 requires computer systems used in manufacture to be routinely checked under a written programme, with controlled changes, checked input and output, and secure backups.²
The extent of that work is not fixed either. Annex 11 bases “the extent of validation and data integrity controls” on a justified and documented risk assessment.¹ The MHRA says validation effort “increases with complexity and risk”, determined by software functionality, configuration, the opportunity for user intervention and the data lifecycle.³ FDA’s 2003 Part 11 guidance records concerns that some interpretations of Part 11 would “significantly increase the costs of compliance to an extent that was not contemplated”. FDA responded by interpreting the scope of Part 11 narrowly, exercising enforcement discretion over some of its requirements and recommending that validation be based on a justified and documented risk assessment.⁴
2What you pay for.
A quote that only prices the software leaves out most of the work below. Every line after the first is required by a regulation or set out in regulators’ guidance.
| Cost | Why it is needed | Source |
|---|---|---|
| Licence or subscription, and hosting | The software and, for a cloud service, the provider’s infrastructure, under an agreement that sets each party’s responsibilities | Annex 11 3.1; MHRA 6.20 |
| User requirements | Required functions, based on a documented risk assessment and GMP impact, traceable through the lifecycle | Annex 11 4.4 |
| Supplier assessment | The supplier’s competence and reliability, with an audit if the risk assessment calls for one | Annex 11 3.2 and 4.5 |
| Configuration and validation | Validation for your intended use, workflow by workflow; vendor testing alone is not enough | Annex 11 4; FDA DI question 3⁵; MHRA 6.19 |
| Instrument and system interfaces | Built-in checks on data exchanged with other systems; input and output checked for accuracy | Annex 11 5; 211.68(b) |
| Data migration | Checks that data are not altered in value or meaning when moved to the new system | Annex 11 4.8; MHRA 6.8 |
| Training | Everyone who develops, maintains or uses the system trained for their tasks | 21 CFR 11.10(i)⁶; 211.25 |
| Change control | Every change to the system or its configuration made under a defined procedure | Annex 11 10 |
| Periodic evaluation | Regular confirmation that the system remains validated and compliant | Annex 11 11 |
| Backup, continuity and archiving | Regular backups with restores checked, tested continuity arrangements, and archived data that stay readable | Annex 11 7.2, 16 and 17; 211.68(b) |
| Retention and exit | Records retrievable for their whole retention period, whichever system holds them by then | 211.180; EU GMP 4.11 and 4.12 |
Data migration and retention reach beyond the project itself. The MHRA warns that “the challenges of migrating data are often underestimated, particularly regarding maintaining the full meaning of the migrated records”.³ And retention periods run for years: batch records are kept at least a year after the batch expires under 211.180, and in the EU for one year after expiry or at least five years after QP certification, whichever is longer, with raw data supporting a marketing authorisation kept while the authorisation remains in force.⁷⁸
3What makes validation cost more or less.
Risk sets the depth of testing. FDA’s computer software assurance guidance, written for medical device manufacturers and issued on 3 February 2026, describes a “least-burdensome approach, where the burden of validation is no more than necessary to address the risk”. It allows unscripted testing for features that are not high process risk, using the developer’s existing validation work as a starting point, and recording evidence with system logs and audit trails rather than “paper documentation, screenshots, or duplicating results”.⁹ Annex 11 asks drug manufacturers for the same kind of risk-based judgement.¹
What the laboratory builds on top of the product matters too. For bespoke or customised systems, Annex 11 expects a process for the formal assessment and reporting of quality and performance measures for every lifecycle stage.¹ It defines such a system as one “individually designed to suit a specific business process”.¹ FDA’s device guidance gives a spreadsheet example: using its basic input functions to record readings may need nothing beyond the developer’s own work and the initial installation and configuration, while custom formulas used directly in production may need further validation by the manufacturer.⁹ Simple instruments need less: the MHRA says equipment with no configurable software and no electronic data retention, such as pH meters and balances, may only need calibration, while complex systems need validation for their intended purpose.³
4What to ask for in a quote.
Ask each supplier to price the same scope, and ask for the evidence you will rely on. Annex 11 expects documentation supplied with commercial products to be reviewed against your user requirements, and the supplier’s quality system and audit information to be available to inspectors on request.¹ For a hosted service, the MHRA expects the contract to give timely access to data, including metadata and audit trails, to define responsibilities for archiving and continued readability, to allow the system to be restored to its validated state, and to include tested business continuity arrangements.³ Pricing those terms, and the cost of leaving, before signing makes quotes comparable over the life of the records rather than the first year.
5How it runs in Seal.
In Seal you start with one release test, incoming-inspection workflow or stability study: agree its intended use, representative data and acceptance criteria, and connect one source; once the scope is agreed and the inputs received, Seal prepares a first working process and its validation pack to evaluate within 48 hours. Production timing then depends on scope, interfaces, migration and your release requirements, as the LIMS blueprint sets out.
After go-live, each configuration change keeps its requirements, specifications, verification results and approval together, and runs its selected acceptance tests before your team releases it. The LIMS comparison lists what to check when choosing, and the comparison with LabWare sets out, from LabWare’s own pages, what a change after go-live involves there.
References
- 1EudraLex Volume 4, Annex 11: Computerised Systems, European Commission, in operation from 30 June 2011. https:/
/ health. ec. europa. eu/ system/ files/ 2016- 11/ annex11_ 01- 2011_ en_ 0. pdf (read 6 November 2026) - 221 CFR 211.68, Automatic, mechanical, and electronic equipment, eCFR. https:/
/ www. ecfr. gov/ current/ title- 21/ section- 211. 68 (read 6 November 2026) - 3‘GXP’ Data Integrity Guidance and Definitions, Revision 1, MHRA, March 2018, sections 4.3, 6.8, 6.19 and 6.20. https:/
/ assets. publishing. service. gov. uk/ media/ 5aa2b9ede5274a3e391e37f3/ MHRA_ GxP_ data_ integrity_ guide_ March_ edited_ Final. pdf (read 6 November 2026) - 4Guidance for Industry: Part 11, Electronic Records; Electronic Signatures, Scope and Application, FDA, August 2003, sections II and III. https:/
/ www. fda. gov/ media/ 75414/ download (read 6 November 2026) - 5Data Integrity and Compliance With Drug CGMP: Questions and Answers, Guidance for Industry, FDA, December 2018, question 3. https:/
/ www. fda. gov/ media/ 119267/ download (read 6 November 2026) - 621 CFR 11.10, Controls for closed systems, eCFR. https:/
/ www. ecfr. gov/ current/ title- 21/ section- 11. 10 (read 6 November 2026) - 721 CFR Part 211, Current Good Manufacturing Practice for Finished Pharmaceuticals, sections 211.25 and 211.180, eCFR. https:/
/ www. ecfr. gov/ current/ title- 21/ chapter- I/ subchapter- C/ part- 211 (read 6 November 2026) - 8EudraLex Volume 4, Chapter 4: Documentation, European Commission, in operation from 30 June 2011, sections 4.11 and 4.12. https:/
/ health. ec. europa. eu/ system/ files/ 2016- 11/ chapter4_ 01- 2011_ en_ 0. pdf (read 6 November 2026) - 9Computer Software Assurance for Production and Quality Management System Software, Guidance for Industry and FDA Staff, FDA, 3 February 2026, sections V, V.A.1 and V.A.4 to V.A.6. https:/
/ www. fda. gov/ regulatory- information/ search- fda- guidance- documents/ computer- software- assurance- production- and- quality- management- system- software (read 6 November 2026)
AQuestions and answers
Is a cloud LIMS cheaper to validate?
Hosting moves some work to the provider but not the responsibility. You still validate the system for your intended use, and the agreement has to cover access to data and audit trails, archiving, restoring the validated state and business continuity. The provider’s testing and certifications can reduce your own testing where your assessment shows they cover it.
What does a LIMS cost after go-live?
Ongoing costs come from change control for every configuration change and upgrade, periodic evaluation of the validated state, audit trail review, backup and restore checks, training for new staff, support, and keeping archived records readable for their full retention period, which can outlast the system itself.
Why is data migration so expensive?
Because the migrated data must keep their value and meaning, with their metadata, and the migration has to be validated to show it. The MHRA warns that the work is often underestimated, particularly in keeping the full meaning of the migrated records.
Does customising a LIMS increase the cost?
Usually. Annex 11 expects a bespoke or customised system to have its quality and performance formally assessed at every lifecycle stage, and custom code has to go through change control whenever it or the product beneath it changes. FDA’s device guidance makes the same distinction for a spreadsheet: its basic functions may need little beyond the supplier’s work and installation, while custom formulas used in production may need more validation.
How do you compare quotes from different suppliers?
Ask each supplier to price the same scope: users and environments, configuration, instrument and system interfaces, migration, validation deliverables, training, support and upgrades, hosting and exit. Then compare the total cost over the time you must keep the records, not only the first year.