Module LabQC Pro EN: Difference between revisions

From Dolibarr ERP CRM Wiki
Jump to navigation Jump to search
(→‎QC Specifications: Added LabQC Pro documentation images and completed module documentation.)
No edit summary
 
(9 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{DISPLAYTITLE:Module LabQC Pro}}
{{DISPLAYTITLE:Module LabQC Pro}}


=LabQC Pro=
'''LabQC Pro''' is a quality-control module for Dolibarr that manages product-specific analytical specifications, QC tests linked to batches/lots, inspection and sampling information, automatic PASS/FAIL evaluation, finalization, audit history and controlled PDF reporting.


'''LabQC Pro''' is a laboratory quality control module for Dolibarr designed to manage product-specific QC specifications, analytical testing, automatic PASS / FAIL evaluation, result approval and locking, audit trail, Certificate of Analysis (CoA), and Out of Specification (OOS) reports.
The module is intended for laboratories, manufacturers and organizations performing incoming-goods, in-process or pre-shipment quality inspections. It can operate independently or with optional '''BatchSafe Pro''' and '''CAPA & Deviation Manager''' integrations.


The module can work independently or optionally integrate with '''BatchSafe Pro''' for automatic batch/lot quality-status synchronization.
'''Current version: 1.1.1'''


==Information==
[[File:00_Cover_LabQC_Pro.png|600px|center|LabQC Pro – Quality Control Management for Dolibarr]]


*'''Module name:''' LabQC Pro
==Overview==
*'''Current version:''' 1.0.40
*'''Author:''' Vasile Panciuc
*'''Publisher:''' PanciucSoft
*'''License:''' GNU GPL v3 or later
*'''Support:''' support@panciucsoft.com
*'''Dolibarr compatibility declared on DoliStore:''' V18 - V23
*'''Validated clean installation:''' Dolibarr 23.0.3
*'''Languages:''' English, Romanian
*'''BatchSafe Pro:''' Optional


==Introduction==
'''Typical workflow:'''


LabQC Pro provides a structured quality control workflow directly inside Dolibarr.
QC Specification → QC Test → Inspection Details → Analytical Results → Automatic PASS/FAIL → Finalization and Locking → CoA or OOS Report


The typical workflow is:
===Main features===


'''QC Specification → QC Test → Analytical Results → Automatic PASS / FAIL → Finalization & Locking → CoA or OOS Report'''
*Product-specific QC specifications and version references
*Analytical methods, numeric limits, text criteria and mandatory parameters
*QC tests linked to existing Dolibarr products and batches/lots
*Batch quantity and inspected quantity fields
*Manually entered AQL value, inspection type and third-party reference
*Automatic PASS/FAIL evaluation of analytical results
*Role-based permissions and controlled finalization
*Read-only results and inspection information after finalization
*Audit Trail recording tracked changes, including old and new values
*Certificate of Analysis (CoA) for finalized PASS tests
*OOS / QC Test Report for finalized FAIL tests
*Optional BatchSafe Pro and CAPA & Deviation Manager integrations
*Responsive desktop and mobile layouts
*Interface and PDF translations in English, Romanian, French, German and Spanish


The module is suitable for organizations that manage products by batch or lot and need traceable laboratory quality-control records.
==What's new in version 1.1.1==


[[File:LabQC Pro Overview.png|frameless|900x900px]]
Version '''1.1.1''' extends QC tests with inspection and sampling information and adds three new languages.


*'''Batch quantity (parts)''' — the total quantity of parts in the batch subject to inspection
*'''Quantity inspected (parts)''' — the number of parts actually checked, which may be lower than the batch quantity
*'''AQL value (manual)''' — an optional value recorded for inspection traceability
*'''Third-party reference''' — a manually entered supplier order, customer order or other external reference
*'''Inspection type''' — for example, incoming inspection or pre-shipment inspection
*Inspection fields included in the QC test record, Audit Trail changes and CoA/OOS PDFs
*Inspection information becomes read-only after test finalization
*French, German and Spanish translations, in addition to English and Romanian
*Improvements to multilingual PDF headings, special characters, page layout and footer


==Main features==
'''Important:''' Recording an AQL value does '''not''' automatically calculate an ISO 2859 sampling plan, sample size, acceptance number or AQL-based lot acceptance/rejection decision. LabQC Pro's automatic PASS/FAIL evaluation applies to the analytical criteria configured for the QC test.


*Product-specific QC specifications
==Dashboard==
*Specification version management
*Analytical parameters and acceptance criteria
*Numeric and text-based laboratory results
*Mandatory analytical parameters
*QC tests linked to existing Dolibarr product batches / lots
*Automatic PASS / FAIL evaluation
*Finalization and permanent result locking
*Laboratory Analyst and QC Manager permission workflow
*Immutable Audit Trail
*Previous and new value tracking
*User and timestamp history
*Certificate of Analysis generation for PASS tests
*OOS / QC Test Report generation for FAIL tests
*Tested by / Approved by information
*Approval date and signature fields
*Responsive desktop and mobile interface
*English and Romanian interface
*Optional BatchSafe Pro integration


==User roles==
The Dashboard presents counts for specifications, all QC tests, PASS tests, FAIL/OOS tests and tests in progress. It provides shortcuts for the main quality-control workflow.


===Lab Analyst===
[[File:01_Dashboard.png|600px|center|LabQC Pro dashboard and QC workflow]]


The Laboratory Analyst can:
==QC Specifications==
 
*Create QC tests
*Select the product, specification and real Dolibarr lot
*Enter analytical results
*Save and recalculate results
*Trigger automatic PASS / FAIL evaluation
 
The Laboratory Analyst should not finalize or approve QC tests unless the corresponding permission is granted.


===QC Manager===
A QC specification defines the analytical requirements for a Dolibarr product. Each specification has a reference, label, version and status, and can contain multiple analytical parameters.


The QC Manager can:
[[File:02_QC_Specifications.png|600px|center|QC specifications overview]]


*Review analytical results
===Specification details===
*Review PASS / FAIL verdicts
*Finalize and lock QC tests
*Approve the final QC decision
*Review the Audit Trail
*Generate CoA or OOS reports


==QC Specifications==
The specification record identifies the product and version to which the analytical acceptance criteria apply.


A QC Specification defines the analytical requirements for a product.
[[File:03_Specification_Details.png|600px|center|QC specification record]]


Each specification may contain:
===Analytical parameters===


*Product
Each parameter can define the name, method, criterion type, acceptance limits or target text, unit and mandatory status.
*Reference
*Label
*Version
*Status
*Description
*Analytical parameters


Each analytical parameter may define:
[[File:04_Analytical_Parameters.png|600px|center|Analytical parameters and acceptance criteria]]


*Parameter name
Example (illustrative values only):
*Analytical method
*Acceptance criterion
*Mandatory status
 
Example:


{| class="wikitable"
{| class="wikitable"
Line 109: Line 80:
!Mandatory
!Mandatory
|-
|-
|Assay
|Assay||HPLC||98–102 %||Yes
|HPLC
|98 - 102 %
|Yes
|-
|-
|Appearance
|Appearance||Visual||White tablets||Yes
|Visual
|-
|White tablets
|pH||Potentiometric||5–7||Yes
|Yes
|}
|}


[[File:LabQC Pro QC Specifications.png|frameless|850x850px]]
The organization must establish, approve and maintain the methods and criteria applicable to its products.
 


==QC Tests==
==QC Tests==


A QC Test is linked to:
QC tests are linked to a product, its QC specification and an existing Dolibarr batch/lot. A QC test may also contain a reference, test date and notes.
 
*A Dolibarr product
*A QC specification
*An existing Dolibarr batch / lot
*A test date
*Analytical results
 
The module retrieves existing Dolibarr product lots, which helps maintain traceability between laboratory testing and physical stock.


==Automatic PASS / FAIL evaluation==
[[File:05_QC_Tests.png|600px|center|QC test creation and test list]]


LabQC Pro evaluates entered analytical results against the approved specification.
===Inspection details (new in 1.1.1)===


Example:
The QC Test form and record include the following optional inspection fields:


{| class="wikitable"
{| class="wikitable"
!Parameter
!Field
!Specification
!Purpose
!Result
!Example
!Verdict
|-
|'''Batch quantity (parts)'''||Total number of parts in the inspected batch||5000
|-
|'''Quantity inspected (parts)'''||Actual number of inspected parts||100
|-
|'''AQL value (manual)'''||Records the AQL value selected before inspection||0.65
|-
|-
|Assay
|'''Third-party reference'''||Supplier/customer order or other external identifier||PO-2026-00125
|98 - 102 %
|100 %
|PASS
|-
|-
|Appearance
|'''Inspection type'''||Context of inspection||Incoming inspection
|White tablets
|White tablets
|PASS
|}
|}


If one or more mandatory analytical parameters fail, the final QC test status becomes '''FAIL'''.
The inspected quantity cannot exceed the batch quantity when both values are supplied. While a QC test remains open, authorized users can update inspection information; tracked changes are recorded in the Audit Trail. After finalization, these fields are displayed as read-only.
 
[[File:11_Inspection_Details.png|600px|center|LabQC Pro 1.1.1 inspection details with batch quantity, inspected quantity, AQL, third-party reference and inspection type]]
 
'''AQL note:''' This field is for manual documentation only. AQL-based sampling-plan calculations and AQL acceptance/rejection decisions are not performed by the module.
 
===Analytical results and PASS/FAIL evaluation===
 
For each analytical parameter, the user enters a numeric or text result as appropriate. LabQC Pro compares results with the applicable specification:


==Finalization and result locking==
*'''PASS''' — the required results meet the configured acceptance criteria.
*'''FAIL / OOS''' — at least one required result is outside the configured criteria.
*'''Incomplete''' — required results are missing; the test cannot be finalized yet.


After results are reviewed, an authorized QC Manager can finalize the QC test.
[[File:07_Analytical_Results.png|600px|center|Analytical results and individual verdicts]]


Finalization:
===Finalization and locking===


*Records the approving user
An authorized user with finalization rights reviews a completed QC test and finalizes the decision. Finalization records the responsible user and time and locks results and inspection details in the normal application workflow.
*Records the approval date and time
*Stores the final PASS or FAIL decision
*Locks laboratory results against further modification
*Creates an Audit Trail event


Once finalized, analytical results become read-only.
For finalized FAIL/OOS tests, an optional linked CAPA/deviation action can be available when CAPA & Deviation Manager is installed.


==Certificate of Analysis==
[[File:06_QC_Finalization_CAPA.png|600px|center|QC finalization and CAPA/deviation follow-up]]


A finalized PASS test can generate a '''Certificate of Analysis (CoA)'''.
==Certificates of Analysis and OOS Reports==


The generated PDF contains:
LabQC Pro generates controlled PDF reports for finalized tests:


*Product
*'''Certificate of Analysis (CoA):''' finalized PASS tests
*Batch / Lot
*'''OOS / QC Test Report:''' finalized FAIL tests
*QC specification
*Test date
*Final QC status
*Overall result
*Analytical parameters
*Methods
*Specifications
*Results
*Verdicts
*Tested by
*Approved by
*Approval date
*Signature field


The final decision is displayed as '''Approved'''.
The reports show product and lot identification, selected QC specification, analytical results and verdicts, final decision, traceability and approval information. Starting with version 1.1.1, they also include inspection details when recorded.


[[File:08_Certificates_OOS.png|600px|center|CoA and OOS report selection]]


==OOS / QC Test Report==
===CoA with inspection details (version 1.1.1)===


A finalized FAIL test can generate an '''OOS / QC Test Report'''.
The following CoA example displays batch quantity, inspected quantity, manually entered AQL, third-party reference and inspection type together with analytical results and approval information.


The report identifies failed analytical parameters and displays:
[[File:12_CoA_Inspection_Details.png|600px|center|Certificate of Analysis with inspection and sampling information in LabQC Pro 1.1.1]]


*Final QC status: FAIL
===CoA and OOS examples===
*Overall result: Out of Specification (OOS)
*Failed analytical results
*Final decision: Rejected
*Tested by
*Approved by
*Approval date
*Signature field


[[File:LabQC Pro Certificates Reports.png|frameless|850x850px]]
[[File:10_CoA_OOS_PDF_Examples.png|600px|center|Examples of CoA and OOS PDF reports]]
 
The approval information reflects the finalized QC record and does not represent a cryptographic electronic signature.


==Audit Trail==
==Audit Trail==


LabQC Pro includes an immutable Audit Trail for important QC events.
LabQC Pro records key QC events including test creation, analytical result modifications, inspection detail changes, status changes and finalization. Entries may include the timestamp, user, QC test, object, action, previous value, new value and note.


Recorded events include:
[[File:09_Audit_Trail.png|600px|center|Audit Trail showing recorded QC changes]]


*QC test creation
The application Audit Trail supports traceability. Database permissions, backups, retention controls and regulatory validation remain the responsibility of the organization using the module.
*Result updates
*Status changes
*Test finalization


Each event can record:
==User roles and permissions==


*Date and time
Typical role assignments are:
*QC test reference
*Action
*Object
*User
*Previous value
*New value
*Note


The Audit Trail is available on both desktop and mobile layouts.
*'''Laboratory Analyst:''' create QC tests, enter and update results while open, review the automatic verdict.
*'''QC Manager:''' review results, finalize/lock tests, review the Audit Trail and generate CoA/OOS reports.
*'''Specification administrator/authorized QC user:''' maintain QC specifications and parameters according to local procedures.


[[File:LabQC Pro Audit Trail.png|frameless|850x850px]]
Permissions must be configured in Dolibarr for the actual responsibilities and internal procedures of the organization.


==BatchSafe Pro integration==
==Optional integrations==


BatchSafe Pro integration is optional.
===BatchSafe Pro===


When BatchSafe Pro is installed and enabled, LabQC Pro can automatically synchronize lot quality status.
When BatchSafe Pro is enabled, QC outcomes can influence batch/lot quality status. Depending on the configuration and safeguards, a new test may put a lot under inspection, finalized PASS may support release and finalized FAIL/OOS may lead to rejection.


Typical workflow:
Existing manual holds, recalls or restrictions must not be treated as automatically cleared merely because another QC test passes. The displayed lot state may also reflect a different QC test for the same lot.


{| class="wikitable"
BatchSafe Pro is optional; LabQC Pro works without it.
!LabQC event
 
!BatchSafe Pro status
===CAPA & Deviation Manager===
|-
 
|QC test opened
When the optional CAPA & Deviation Manager module is installed, a finalized FAIL/OOS test can be linked to a deviation record for investigation and follow-up. Relevant QC test, product, batch/lot and specification information can be used to prefill the deviation.
|Under inspection
|-
|QC test in progress
|Under inspection
|-
|Finalized PASS
|Released
|-
|Finalized FAIL / OOS
|Rejected
|}


LabQC Pro also works normally when BatchSafe Pro is not installed or is disabled.
The integration is optional.


==Installation==
==Languages==


#Download the LabQC Pro ZIP package.
Version 1.1.1 provides interface and PDF translations in:
#In Dolibarr, go to '''Home → Setup → Modules/Applications'''.
#Use the external module deployment function.
#Upload the LabQC Pro ZIP package.
#Activate '''LabQC Pro'''.
#Configure user permissions.
#Ensure Products, Stock and Lot / Serial management are enabled if lot-based QC is required.


The module has also been validated on a clean Dolibarr 23.0.3 installation.
*English (EN)
*Romanian (RO)
*French (FR)
*German (DE)
*Spanish (ES)


==Basic configuration==
Names of products, analytical parameters and user-entered notes are stored as user data and are not automatically translated.


Before creating QC tests:
==Requirements and compatibility==


#Create or select a Dolibarr product.
*Dolibarr V18–V24 (declared product compatibility range)
#Enable lot / serial management for the product.
*PHP 7.4 or later (declared minimum)
#Create a warehouse.
*Dolibarr Products and Stock modules
#Add stock using a real lot number.
*Lot/Serial management for workflows that use existing batches/lots
#Create a QC Specification for the product.
#Add analytical parameters.
#Create a QC Test and select the existing lot.


==Mobile support==
'''Compatibility note:''' The current functionality and the 1.1.1 multilingual PDF reports were tested on Dolibarr 24.0.0. Not every earlier declared Dolibarr release, hosting environment or upgrade scenario has been comprehensively retested.


LabQC Pro includes responsive layouts for:
==Installation and update==


*Dashboard
===New installation===
*QC Specifications
*QC Tests
*Analytical result entry
*Finalized test review
*Certificates / OOS
*Audit Trail


This allows laboratory and QC users to review or enter information from mobile devices.
#Download the LabQC Pro ZIP package from DoliStore.
#Upload/deploy the external module through the Dolibarr module installation procedure.
#Enable LabQC Pro and configure the required user permissions.
#Ensure the necessary Products, Stock and Lot/Serial features are active.
#Create a QC Specification and its analytical parameters.
#Create a QC Test linked to a product and an existing batch/lot.
#Enter inspection details (optional) and analytical results.
#Review the calculated verdict, finalize with an authorized account and generate the CoA or OOS report.


[[File:LabQC Pro Mobile.png|frameless|850x850px]]
===Updating from an earlier version===


==Support==
Back up the Dolibarr database and module files before deploying the new package. The module retains identifier '''207603'''. Existing QC tests without inspection details can remain without values in the new optional fields.


For support, installation questions or bug reports:
After updating, verify existing specifications and tests, user rights, an open QC test and both report types. A staging upgrade is recommended for regulated or production environments.


'''Email:''' support@panciucsoft.com
==Example use cases==


'''Publisher:''' PanciucSoft
*Incoming inspection of goods received from a supplier
*Production or batch laboratory quality control
*Pre-shipment inspection before delivery to a customer
*Laboratory tests with numeric and text acceptance criteria
*Documentation of lot quantity and inspected sample size
*Follow-up of out-of-specification results via an optional CAPA workflow


==License==
==Support and license==


LabQC Pro is distributed under the '''GNU General Public License version 3 or later (GPL-3.0-or-later)'''.
'''Developer:''' PanciucSoft


==Regulatory notice==
'''Support:''' [mailto:support@panciucsoft.com support@panciucsoft.com]


LabQC Pro provides software workflow features for laboratory quality control.
'''Website:''' [https://panciucsoft.com panciucsoft.com]


Validation, qualification, electronic-signature requirements, data-retention rules and suitability for GMP, GLP, GxP, ISO, pharmaceutical, medical or other regulated use remain the responsibility of the organization deploying the module.
'''License:''' GNU GPL v3 or later


==See also==
'''Current documented release:''' LabQC Pro 1.1.1


*[[Dolibarr]]
==Regulatory notice==


[[Category:Complementary modules]]
LabQC Pro provides tools to support laboratory and manufacturing quality-control workflows. The software has not been independently certified as compliant with GMP, GLP, GxP, FDA 21 CFR Part 11 or ISO 2859. Organizations are responsible for their system validation, standard operating procedures, electronic-signature controls where required, and applicable regulatory compliance.

Latest revision as of 02:37, 30 October 2026


LabQC Pro is a quality-control module for Dolibarr that manages product-specific analytical specifications, QC tests linked to batches/lots, inspection and sampling information, automatic PASS/FAIL evaluation, finalization, audit history and controlled PDF reporting.

The module is intended for laboratories, manufacturers and organizations performing incoming-goods, in-process or pre-shipment quality inspections. It can operate independently or with optional BatchSafe Pro and CAPA & Deviation Manager integrations.

Current version: 1.1.1

LabQC Pro – Quality Control Management for Dolibarr

Overview

Typical workflow:

QC Specification → QC Test → Inspection Details → Analytical Results → Automatic PASS/FAIL → Finalization and Locking → CoA or OOS Report

Main features

  • Product-specific QC specifications and version references
  • Analytical methods, numeric limits, text criteria and mandatory parameters
  • QC tests linked to existing Dolibarr products and batches/lots
  • Batch quantity and inspected quantity fields
  • Manually entered AQL value, inspection type and third-party reference
  • Automatic PASS/FAIL evaluation of analytical results
  • Role-based permissions and controlled finalization
  • Read-only results and inspection information after finalization
  • Audit Trail recording tracked changes, including old and new values
  • Certificate of Analysis (CoA) for finalized PASS tests
  • OOS / QC Test Report for finalized FAIL tests
  • Optional BatchSafe Pro and CAPA & Deviation Manager integrations
  • Responsive desktop and mobile layouts
  • Interface and PDF translations in English, Romanian, French, German and Spanish

What's new in version 1.1.1

Version 1.1.1 extends QC tests with inspection and sampling information and adds three new languages.

  • Batch quantity (parts) — the total quantity of parts in the batch subject to inspection
  • Quantity inspected (parts) — the number of parts actually checked, which may be lower than the batch quantity
  • AQL value (manual) — an optional value recorded for inspection traceability
  • Third-party reference — a manually entered supplier order, customer order or other external reference
  • Inspection type — for example, incoming inspection or pre-shipment inspection
  • Inspection fields included in the QC test record, Audit Trail changes and CoA/OOS PDFs
  • Inspection information becomes read-only after test finalization
  • French, German and Spanish translations, in addition to English and Romanian
  • Improvements to multilingual PDF headings, special characters, page layout and footer

Important: Recording an AQL value does not automatically calculate an ISO 2859 sampling plan, sample size, acceptance number or AQL-based lot acceptance/rejection decision. LabQC Pro's automatic PASS/FAIL evaluation applies to the analytical criteria configured for the QC test.

Dashboard

The Dashboard presents counts for specifications, all QC tests, PASS tests, FAIL/OOS tests and tests in progress. It provides shortcuts for the main quality-control workflow.

LabQC Pro dashboard and QC workflow

QC Specifications

A QC specification defines the analytical requirements for a Dolibarr product. Each specification has a reference, label, version and status, and can contain multiple analytical parameters.

QC specifications overview

Specification details

The specification record identifies the product and version to which the analytical acceptance criteria apply.

QC specification record

Analytical parameters

Each parameter can define the name, method, criterion type, acceptance limits or target text, unit and mandatory status.

Analytical parameters and acceptance criteria

Example (illustrative values only):

Parameter Method Acceptance criterion Mandatory
Assay HPLC 98–102 % Yes
Appearance Visual White tablets Yes
pH Potentiometric 5–7 Yes

The organization must establish, approve and maintain the methods and criteria applicable to its products.

QC Tests

QC tests are linked to a product, its QC specification and an existing Dolibarr batch/lot. A QC test may also contain a reference, test date and notes.

QC test creation and test list

Inspection details (new in 1.1.1)

The QC Test form and record include the following optional inspection fields:

Field Purpose Example
Batch quantity (parts) Total number of parts in the inspected batch 5000
Quantity inspected (parts) Actual number of inspected parts 100
AQL value (manual) Records the AQL value selected before inspection 0.65
Third-party reference Supplier/customer order or other external identifier PO-2026-00125
Inspection type Context of inspection Incoming inspection

The inspected quantity cannot exceed the batch quantity when both values are supplied. While a QC test remains open, authorized users can update inspection information; tracked changes are recorded in the Audit Trail. After finalization, these fields are displayed as read-only.

LabQC Pro 1.1.1 inspection details with batch quantity, inspected quantity, AQL, third-party reference and inspection type

AQL note: This field is for manual documentation only. AQL-based sampling-plan calculations and AQL acceptance/rejection decisions are not performed by the module.

Analytical results and PASS/FAIL evaluation

For each analytical parameter, the user enters a numeric or text result as appropriate. LabQC Pro compares results with the applicable specification:

  • PASS — the required results meet the configured acceptance criteria.
  • FAIL / OOS — at least one required result is outside the configured criteria.
  • Incomplete — required results are missing; the test cannot be finalized yet.
Analytical results and individual verdicts

Finalization and locking

An authorized user with finalization rights reviews a completed QC test and finalizes the decision. Finalization records the responsible user and time and locks results and inspection details in the normal application workflow.

For finalized FAIL/OOS tests, an optional linked CAPA/deviation action can be available when CAPA & Deviation Manager is installed.

QC finalization and CAPA/deviation follow-up

Certificates of Analysis and OOS Reports

LabQC Pro generates controlled PDF reports for finalized tests:

  • Certificate of Analysis (CoA): finalized PASS tests
  • OOS / QC Test Report: finalized FAIL tests

The reports show product and lot identification, selected QC specification, analytical results and verdicts, final decision, traceability and approval information. Starting with version 1.1.1, they also include inspection details when recorded.

CoA and OOS report selection

CoA with inspection details (version 1.1.1)

The following CoA example displays batch quantity, inspected quantity, manually entered AQL, third-party reference and inspection type together with analytical results and approval information.

Certificate of Analysis with inspection and sampling information in LabQC Pro 1.1.1

CoA and OOS examples

Examples of CoA and OOS PDF reports

The approval information reflects the finalized QC record and does not represent a cryptographic electronic signature.

Audit Trail

LabQC Pro records key QC events including test creation, analytical result modifications, inspection detail changes, status changes and finalization. Entries may include the timestamp, user, QC test, object, action, previous value, new value and note.

Audit Trail showing recorded QC changes

The application Audit Trail supports traceability. Database permissions, backups, retention controls and regulatory validation remain the responsibility of the organization using the module.

User roles and permissions

Typical role assignments are:

  • Laboratory Analyst: create QC tests, enter and update results while open, review the automatic verdict.
  • QC Manager: review results, finalize/lock tests, review the Audit Trail and generate CoA/OOS reports.
  • Specification administrator/authorized QC user: maintain QC specifications and parameters according to local procedures.

Permissions must be configured in Dolibarr for the actual responsibilities and internal procedures of the organization.

Optional integrations

BatchSafe Pro

When BatchSafe Pro is enabled, QC outcomes can influence batch/lot quality status. Depending on the configuration and safeguards, a new test may put a lot under inspection, finalized PASS may support release and finalized FAIL/OOS may lead to rejection.

Existing manual holds, recalls or restrictions must not be treated as automatically cleared merely because another QC test passes. The displayed lot state may also reflect a different QC test for the same lot.

BatchSafe Pro is optional; LabQC Pro works without it.

CAPA & Deviation Manager

When the optional CAPA & Deviation Manager module is installed, a finalized FAIL/OOS test can be linked to a deviation record for investigation and follow-up. Relevant QC test, product, batch/lot and specification information can be used to prefill the deviation.

The integration is optional.

Languages

Version 1.1.1 provides interface and PDF translations in:

  • English (EN)
  • Romanian (RO)
  • French (FR)
  • German (DE)
  • Spanish (ES)

Names of products, analytical parameters and user-entered notes are stored as user data and are not automatically translated.

Requirements and compatibility

  • Dolibarr V18–V24 (declared product compatibility range)
  • PHP 7.4 or later (declared minimum)
  • Dolibarr Products and Stock modules
  • Lot/Serial management for workflows that use existing batches/lots

Compatibility note: The current functionality and the 1.1.1 multilingual PDF reports were tested on Dolibarr 24.0.0. Not every earlier declared Dolibarr release, hosting environment or upgrade scenario has been comprehensively retested.

Installation and update

New installation

  1. Download the LabQC Pro ZIP package from DoliStore.
  2. Upload/deploy the external module through the Dolibarr module installation procedure.
  3. Enable LabQC Pro and configure the required user permissions.
  4. Ensure the necessary Products, Stock and Lot/Serial features are active.
  5. Create a QC Specification and its analytical parameters.
  6. Create a QC Test linked to a product and an existing batch/lot.
  7. Enter inspection details (optional) and analytical results.
  8. Review the calculated verdict, finalize with an authorized account and generate the CoA or OOS report.

Updating from an earlier version

Back up the Dolibarr database and module files before deploying the new package. The module retains identifier 207603. Existing QC tests without inspection details can remain without values in the new optional fields.

After updating, verify existing specifications and tests, user rights, an open QC test and both report types. A staging upgrade is recommended for regulated or production environments.

Example use cases

  • Incoming inspection of goods received from a supplier
  • Production or batch laboratory quality control
  • Pre-shipment inspection before delivery to a customer
  • Laboratory tests with numeric and text acceptance criteria
  • Documentation of lot quantity and inspected sample size
  • Follow-up of out-of-specification results via an optional CAPA workflow

Support and license

Developer: PanciucSoft

Support: support@panciucsoft.com

Website: panciucsoft.com

License: GNU GPL v3 or later

Current documented release: LabQC Pro 1.1.1

Regulatory notice

LabQC Pro provides tools to support laboratory and manufacturing quality-control workflows. The software has not been independently certified as compliant with GMP, GLP, GxP, FDA 21 CFR Part 11 or ISO 2859. Organizations are responsible for their system validation, standard operating procedures, electronic-signature controls where required, and applicable regulatory compliance.