1C for laboratories: what it covers — and what you still have to build
1C already runs accounting and the warehouse. Leadership asks: extend it to the lab — why buy a separate system? You open a stock 1C configuration and see there is no sample tracking, no test protocols, no link to instruments. What next — look for industry solutions on the 1C:Enterprise 8 platform, commission a customization, or implement a separate LIMS? Below we walk through each option: what 1C covers for a laboratory out of the box, where custom development begins, and when two systems with data exchange are more practical.
Why laboratories look at 1C at all
1C already serves the enterprise financial contour. Leadership reasons soundly: licences are paid, the server is set up, users are trained, ITS support works. Why proliferate software if the 1C:Enterprise 8 platform already handles materials accounting, order management, and reporting?
Then someone opens a stock configuration and sees there is no sample registration, no test-method management, no link to laboratory equipment. 1C Accounting counts money. 1C ERP and “Comprehensive Automation” run warehouse, production, and sales. But none of these 1C configurations describe the full sample cycle from intake to issuing a protocol.
When Excel stops being enough
Lab automation becomes a necessity, not a wish. Sample volume grows, the number of laboratory studies rises every quarter, and Excel journals tangle in file versions. Manual data handling leads to errors: someone overwrote a formula, someone deleted a row. Change history cannot be restored, and an ISO/IEC 17025 auditor asks specifically about data traceability and protection of values against unauthorized edits.
Another scenario: accreditation is approaching. You need statistical reports on test results, confirmation of workstation competence, electronic capture of every analysis type. Paper journals and scattered spreadsheets do not deliver that.
Why 1C is the first choice
For a company where 1C for the laboratory looks like a natural extension of the current business contour, the arguments are strong. No extra 1C licence delivery. No retraining staff on another system. Reusing the already configured interaction of 1C with accounting, warehouse, and sales saves time. Reagent accounting fits the 1C warehouse module. Total cost of ownership, at first glance, looks lower.
But registering laboratory test results, calculating measurement uncertainty, automatic data transfer from analyzers, quality control with control charts — none of that exists in stock 1C solutions. Even industry 1C products such as “1C:Medicine. Clinical Laboratory” target medical organizations and clinical diagnostics for patients, not a testing laboratory. A 1C software product for industrial testing will have to be built from scratch or found among niche solutions from 1C partners.
The main goal of this piece is to draw the boundary. If you are only starting to think about automation, it makes sense to understand where to begin before you order a consultation from a 1C franchisee.
What 1C covers out of the box
Now — what 1C programs for laboratories cover without a single line of extra code.
Reagents and consumables accounting
Any laboratory consumes reagents, reference standards, and equipment consumables. Warehouse accounting in 1C:Trade Management or in the 1C ERP block covers receipt registration, write-off on use, and stock control. Lot accounting lets you track each reagent’s expiry date. 1C itself highlights items whose certificate is about to expire.
Procurement and supply
Purchase requests, approvals, delivery tracking — a standard 1C process. For each consumable type you can set a minimum stock level, and 1C will form the demand automatically. Supplier contacts, order history, prices of previous lots — all stored in one 1C database.
Accounting and reporting
1C:Accounting is the most mature product in the 1C line. Bookkeeping and tax accounting, electronic reporting, invoices and closing documents. A laboratory that sells services commercially gets a ready 1C solution for invoicing, contracts, and acts of completed work.
HR and payroll
1C:ZUP handles HR: hiring, termination, work schedules, payroll with hazardous-duty factors, and personal data processing under the organization’s confidentiality policy. User count scales from a few people to hundreds. Data is protected by 1C’s built-in access rights system.
A single enterprise contour
1C’s main strength is an information system that links the laboratory to the rest of the business. 1C comprehensive automation unites warehouse, accounting, HR, and production. Cost analysis on reagents feeds management reports immediately. Data exchange between different 1C configurations is supported in near real time.
But if you overlay this list on real laboratory processes — sample registration, test journals, protocol generation — it becomes obvious: none of that exists in stock 1C configurations. And this is where customization territory begins.
What 1C lacks for laboratory work
The 1C:Enterprise 8 platform was designed around money, goods, and people. A water sample or a product specimen belongs to another universe.
No concept of “sample” or “method”
1C has no sample directory, no sample registration tied to a sampling point, no “test method” entity. Test management is not built into 1C’s architecture. The laboratory tries to run samples through a “Goods receipt” document — and hits a wall: there is nowhere to attach laboratory results, and nothing to build protocols from.
Uncertainty calculation and statistical reports
ISO/IEC 17025 requires assessing the uncertainty of every measurement. No product in the 1C line calculates that out of the box. Building statistical reports for internal quality control and indicator analysis also has to happen outside the 1C platform.
Traceability and instrument connectivity
Edit traceability is an accreditation requirement. The standard 1C registration journal records user actions, but not in the format an assessor expects. Transferring data from laboratory equipment — chromatographs, spectrometers, analyzers — needs drivers and parsers. The 1C platform does not support that without deep customization. Keeping electronic journals tied to instrument signals is a job for a specialized LIMS.
Industry solutions on the 1C platform
1C partners build industry solutions for specific laboratory types. Before celebrating, it is worth understanding the boundaries.
What is on the market
Most 1C solutions cluster around medicine. “1C:Medicine. Clinical Laboratory” covers sample registration, analyzer interaction, reporting for clinical laboratories, and patient service. Outside medical organizations the choice shrinks sharply. Testing, environmental, or construction laboratories — for these activity areas ready-made 1C products are almost absent. Among known niche solutions you may find products from Altey and other developers, but each has its own functional package.
Risks vendors stay quiet about
The main vulnerability is dependency on the developer. When 1C updates the platform, the partner must adapt their 1C product. If the company has three people on staff, updates slip by months. Worse: the developer leaves the market, and the system becomes unmaintained legacy. News of such projects shutting down appears regularly, and the laboratory is left with code nobody can support.
When an industry 1C solution is justified
This option makes sense when the laboratory fits the product profile exactly and the developer is stable. For a clinical laboratory where a standard test set covers the main service volume, industry solutions on 1C can be a reasonable choice. But if the laboratory runs dozens of methods and must keep electronic traceability for accreditation, a standard partner 1C product will not reach the required level.
Customizing a stock 1C configuration: hidden costs
When a ready 1C solution does not fit, the temptation is to “finish” the stock configuration. On paper it is logical: accounting and warehouse work — just add “a bit of laboratory.” In practice it is a project with an unpredictable price.
What you have to build from scratch
You need new 1C directories: samples, methods, equipment. You need registers for results, quality-control journals, client-request registration documents. Using individual rights settings, forms, and print layouts for every object multiplies effort many times over.
Updates as an endless conflict
Every stock 1C update risks breaking customizations. The developer must manually compare changes and test how new code interacts with the old. Support costs for a customized 1C configuration over three years often exceed the initial spend twofold.
Contractor lock-in
The 1C franchisee who wrote the code knows the solution architecture. If they leave, a new developer inherits foreign code without documentation. Understanding it takes months. Responsibility blurs: the 1C vendor supports stock functionality; partners own the customizations. When something breaks at the seam, the laboratory waits, and staff bypass the system — returning to Excel.
Customizing 1C is not a death sentence. But you should calculate five-year cost of ownership. Often that sum makes “1C for finance + a separate laboratory information system” the better deal.
Pairing 1C with a separate laboratory system
Many teams reach this conclusion after trying to fit laboratory processes inside 1C.
How it works in practice
1C stays where it is strong: materials accounting, procurement, accounting reports, payroll. Sample registration, the full cycle from intake to results, quality control — all live in a LIMS. Data-exchange technology: 1C sends counterparty directories and nomenclature; the LIMS returns acts of completed services and statistical reports. Setup is done via REST API or a file bus. Automatic near-real-time sync is supported by both systems.
Why this works better than customizing 1C
1C updates do not touch laboratory code — it lives in another system. The laboratory gets an interface built for its scenarios: automatic result registration from analyzers, journals, protocol generation. 1C support goes through ITS; laboratory support goes through the LIMS development team. Responsibility zones stay clear. Each system’s software evolves independently.
An example is the Spektrokhim case, where 1C covers the financial contour and the LIMS runs sample analysis and test history. For public and commercial laboratories in Russia, this option is currently the most realistic. Two systems with data exchange are more reliable than one in which half the functions rest on crutches.
Frequently asked questions
Can you pass ISO/IEC 17025 accreditation while working in 1C?
On its own, a 1C product does not grant accreditation. Assessors evaluate data management and change traceability. If the 1C configuration implements electronic sample registration, edit history, and protocol generation — the system can meet the requirements. But stock 1C solutions cannot do that, so without customization or a 1C–LIMS pairing you will not pass accreditation.
How much does customizing 1C for a laboratory cost?
Price depends on the number of test types, the number of workstation computers, and the equipment mix. Request an analysis of the current process from a contractor — you will get an estimate tied to a concrete task list. Information on estimation approaches is available on the sites of specialized 1C integrators.
What if the 1C franchisee does not understand laboratory processes?
That is the main reason implementations stall. A 1C franchisee configures accounting but does not understand control charts and internal quality-control activities. The way out: look for 1C partners with laboratory-service automation experience, or bring in a domain consultant — a project manager who works alongside the developer.
How do you organize data exchange between 1C and a LIMS?
The standard option is exchange via REST API or XML/JSON files. 1C sends supply and invoice data; the LIMS returns test results. Exchange can be set up in several days to a couple of weeks. Exchange services and an implementation example are in the Spektrokhim case. Customizing the set of transferred fields is discussed with the project manager.
Conclusions and a first step
1C for a laboratory covers the financial and warehouse contour: reagent accounting, bookkeeping, 1C:ZUP, procurement reporting. But test management, sample registration, journals, product quality control, instrument interaction — none of that exists in stock 1C configurations.
Customizing a stock 1C configuration is possible, but support costs grow with every update. Pairing 1C with a separate laboratory system is often more practical: 1C remains the source of financial data, and the LIMS runs the full sample cycle. Two systems with exchange scale without 1C platform limits. Access and personal-data policies are configured per system. 1C is built for enterprise resource accounting; a LIMS is built for laboratory tasks and process control. Studying sample flow and getting data from instrument images and signals helps with the choice.
A concrete first step
Before you order a consultation, list ten key laboratory processes: from receiving a sample to issuing results. Mark which ones run in Excel, on paper, or “by word of mouth.” That becomes the basis of a technical request. Contacts and a description of laboratory-system design services are on the WAPP site. More on where to start is in a separate article.