V5 Ultimate
Ultimate
PricingResourcesCompany
English (original)العربيةDeutschΕλληνικάEspañolFrançaisItalianoעברית日本語한국어NederlandsPolskiPortuguêsSvenska
Talk to us Log in Start free trial
Food & Beverage
  • Bakery & Confectionery
  • Food Processing
  • Ingredients & Dry Mixes
  • Sausage & Meat Products
  • Produce Packing
  • Pet Food & Pet Supplements
  • Dairy & Chilled Foods
  • Beverages & Liquid Manufacturing
  • Infant Formula
Pharma & Life Sciences
  • Radiopharmaceuticals
  • Pharmaceutical
  • Medical Devices
  • Veterinary Pharmaceuticals
  • Blood & Tissue
  • Diagnostics & IVD Kits
  • Reference Materials & Standards
  • OTC Topical Creams & Gels
Supplements & Personal Care
  • Dietary Supplements
  • Cosmetics & Personal Care
  • Cannabis & Hemp Manufacturing
  • Fragrances & Perfumery
  • Soaps & Personal Hygiene
  • Botanical Extracts & Essential Oils
Chemicals & Materials
  • Plastics & Resins
  • Agricultural Chemicals
  • Specialty & Industrial Chemicals
  • Printing Inks, Pigments & Construction Chemicals
  • Lubricants & Metalworking Fluids
  • Coatings, Adhesives & Sealants
Other Manufacturing
  • Consumer Products
  • Electronics & Electrical Assembly
  • Textiles & Nonwoven
  • Contract Manufacturing & Co-Packing
  • Packaging & Food-Contact Materials
  • Regulated Warehousing & Distribution
Explore all industries
  • Warehouse & TraceabilityReceive, store, pick and trace
  • Production & PlanningPlan jobs and guide production
  • Quality & LaboratoryTest, investigate and review
  • Documents & TrainingControl procedures and qualifications
  • Equipment & PerformanceMaintain assets and measure losses
  • Orders & IntegrationsConnect customers, suppliers and systems
  • Outputs & InsightsReports, KPIs and label design
Why V5? Product & Features
Why V5?Product & Features
  • Warehouse & TraceabilityReceive, store, pick and trace
  • Production & PlanningPlan jobs and guide production
  • Quality & LaboratoryTest, investigate and review
  • Documents & TrainingControl procedures and qualifications
  • Equipment & PerformanceMaintain assets and measure losses
  • Orders & IntegrationsConnect customers, suppliers and systems
  • Outputs & InsightsReports, KPIs and label design
Explore all industries
    • Bakery & Confectionery
    • Food Processing
    • Ingredients & Dry Mixes
    • Sausage & Meat Products
    • Produce Packing
    • Pet Food & Pet Supplements
    • Dairy & Chilled Foods
    • Beverages & Liquid Manufacturing
    • Infant Formula
    • Radiopharmaceuticals
    • Pharmaceutical
    • Medical Devices
    • Veterinary Pharmaceuticals
    • Blood & Tissue
    • Diagnostics & IVD Kits
    • Reference Materials & Standards
    • OTC Topical Creams & Gels
    • Dietary Supplements
    • Cosmetics & Personal Care
    • Cannabis & Hemp Manufacturing
    • Fragrances & Perfumery
    • Soaps & Personal Hygiene
    • Botanical Extracts & Essential Oils
    • Plastics & Resins
    • Agricultural Chemicals
    • Specialty & Industrial Chemicals
    • Printing Inks, Pigments & Construction Chemicals
    • Lubricants & Metalworking Fluids
    • Coatings, Adhesives & Sealants
    • Consumer Products
    • Electronics & Electrical Assembly
    • Textiles & Nonwoven
    • Contract Manufacturing & Co-Packing
    • Packaging & Food-Contact Materials
    • Regulated Warehousing & Distribution
PricingResourcesCompany
Start free trial Log in Talk to us
HomeGlossaryGAMP 5 Category 4
Compliance · The complete guide

GAMP 5 Category 4Good Automated Manufacturing Practice Category 4 (Configured Software)

In short

GAMP 5 Category 4 covers configurable applications where business logic is implemented through controlled configuration rather than custom code, demanding risk-based validation, disciplined change control, and demonstrable data integrity aligned with Annex 11 and 21 CFR Part 11 expectations.

2,655 words · ~13 min read
On this page
  1. 01GAMP 5 Category 4: Configurable Applications
  2. 02Regulatory and technical basis
  3. 03Scope and applicability
  4. 04How Category 4 validation works in practice
  5. 05Configuration management and change control
  6. 06Data integrity and security for configurable systems
  7. 07Common pitfalls and misinterpretations
  8. 08How Category 4 relates to neighboring frameworks
  9. 09How V5 Ultimate supports Category 4 implementation
On this page · 9 sections
  1. 1GAMP 5 Category 4: Configurable Applications
  2. 2Regulatory and technical basis
  3. 3Scope and applicability
  4. 4How Category 4 validation works in practice
  5. 5Configuration management and change control
  6. 6Data integrity and security for configurable systems
  7. 7Common pitfalls and misinterpretations
  8. 8How Category 4 relates to neighboring frameworks
  9. 9How V5 Ultimate supports Category 4 implementation
AI · Explain it for MY operation

How does GAMP 5 Category 4 apply to your shop floor?

Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.

Your scale

01GAMP 5 Category 4: Configurable Applications

GAMP 5 Category 4 encompasses configurable applications whose core engine is supplied by a vendor, while the implementing organization defines business rules, workflows, forms, and reports by configuration. The underlying platform remains unchanged, but the configuration choices can create highly variable behavior that directly affects product quality and regulatory outcomes. This places Category 4 between off-the-shelf functionality and bespoke development in terms of validation effort.

Typical Category 4 examples include Manufacturing Execution Systems with electronic batch records, Quality Management System workflows, Laboratory Information Management Systems, and Warehouse Management Systems configured with master data, parameters, and rules to enforce compliant process execution. The key determinant is that business logic is realized through controlled configuration rather than custom compiled code.

GAMP guidance distinguishes Category 4 from neighboring categories to calibrate effort. Category 3 covers non-configured commercial software used essentially as delivered, and Category 5 covers custom-developed or heavily scripted solutions. Category 4 requires more than simple functional verification, because configuration choices implement requirements. It generally requires documented requirements, configuration specifications, traceability, and risk-based verification aligned to the configured behaviors.

When framing validation, organizations should consider not only feature risk but also the criticality of each configured pathway. Decisions such as enforced sequencing, double-checks, electronic signatures, and exception handling can materially change risk and the associated verification depth. Clear configuration governance keeps Category 4 manageable and auditable over time.

Positioning Among Categories

Category 4 sits between GAMP 5 Category 3 and GAMP 5 Category 5. Treat configuration as implementation of requirements and plan validation effort accordingly.

02Regulatory and technical basis

Regulators are technology-neutral but outcome-focused. EU GMP Annex 11 and FDA’s 21 CFR Part 11 require validated systems, reliable electronic records, and trustworthy electronic signatures. For configurable applications, that means the specific configured behaviors must be shown to meet intended use, be controlled under change, and preserve data integrity over the lifecycle. The validation burden scales with the impact of configuration on product quality, patient safety, and data reliability.

ICH Q9 provides the risk framework commonly applied to computerized systems. It promotes systematic risk identification, analysis, control, and review, pointing validation resources to critical configurations. In practice, risk-based validation for Category 4 ties user requirements and configuration specifications to verification activities, emphasizing scenarios where configuration enforces GMP controls, records critical data, or triggers electronic signatures.

Annex 15 on qualification and validation supports lifecycle thinking: plan, specify, verify, release, monitor, and maintain. For configurable systems, this lifecycle is anchored by governed configuration baselines, traceability from requirements to tests, and periodic review driven by risk and performance. Supplier assessment remains relevant, but it does not replace verification of the organization’s specific configuration.

Auditors often ask to see how configuration decisions were derived from user needs and risk assessments, and how subsequent changes were evaluated for impact. Maintaining a clear chain from requirement to configuration to test evidence is the most persuasive way to demonstrate compliance in this category.

Guidance Anchors

Apply ICH Q9 principles via the ICH Q9 quality risk management readiness approach, align lifecycle controls with Annex 15, and demonstrate data integrity per Annex 11 and 21 CFR Part 11.

03Scope and applicability

Category 4 is widely applicable across regulated manufacturing where configurable platforms orchestrate execution and capture regulated records. The hallmark is a flexible engine that can be parameterized to enforce required behavior without changing source code. This includes how batches are progressed, how checks are enforced, and how deviations are captured and resolved within the system.

In manufacturing, MES platforms commonly implement electronic batch records with configured steps, data collections, exceptions, and approvals. In quality, QMS tools configure change control, CAPA, and supplier oversight workflows. In laboratories, LIMS systems configure specifications, methods, result entry, and review flows. Warehousing often configures material status, quarantine, sampling, and lot tracking with controlled rules and roles.

The calibration of effort depends on process risk and data criticality, not product sector alone. For example, a configuration that gates batch release decisions demands stronger verification and security controls than one that formats a non-critical report. Supplier qualification, platform testing, and certification are helpful, but they do not eliminate the need to verify what you configured for your intended use.

When scoping a Category 4 project, document boundaries explicitly: what will be configured, what integrations will be relied on, which records will be official, and how exceptions and rework will be handled. Clear boundaries reduce scope creep and keep the validation set proportionate to risk.

Typical Category 4 Platforms

Common Category 4 examples include MES with electronic batch record workflows, and LIMS with configured specifications and review cycles.

04How Category 4 validation works in practice

Validation for Category 4 demonstrates that configured behaviors fulfill intended use and manage risks to product quality and data integrity. Begin with clear, testable user requirements that describe what the business needs the system to do. Translate those into configuration specifications that precisely define parameters, rules, workflows, data fields, and security settings.

Risk assessment focuses on failure modes arising from configuration choices and from interactions with other systems. This guides verification intensity and objective evidence selection. Testing should combine positive and negative scenarios, role-based checks, and boundary conditions for calculations and limits. Traceability from requirement through configuration artifact to executed test is essential for audit transparency.

Because configuration is the implementation, change control must be integrated with test evidence and approval gates. Release only what is baselined, peer-reviewed, and traceable. Maintain parameter catalogs and environment management so that configuration states in development, test, and production remain consistent and reconcilable.

  1. Define and approve user requirements, emphasizing intended use and risk-critical behaviors.
  2. Draft configuration specifications mapping requirements to parameters, forms, workflows, roles, and records.
  3. Perform supplier assessment and leverage vendor documentation for platform-level controls.
  4. Plan risk-based verification, selecting test types and depth aligned to criticality and failure modes.
  5. Establish traceability linking requirements, configuration items, test cases, and results.
  6. Execute testing in a controlled test environment, capture objective evidence, and manage deviations.
  7. Baseline, approve, and release configuration to production under formal change control and training.
Efficient Evidence

Use a review-by-exception strategy for low-risk functions and deeper tests where risk dictates. See the paperless validation playbook and review by exception for pragmatic approaches.

05Configuration management and change control

Robust configuration management is the control backbone for Category 4. Treat every parameter set, workflow, form, and report as a configuration item with a unique identifier, version, and owner. Document each item’s purpose, related requirements, and security context. Maintain a configuration baseline that reflects the production state, and ensure development and test environments are synchronized and independently controlled.

Change control should evaluate impact on validated state, product quality, and data integrity. Risk-screen changes, require peer review for logic-heavy updates, and verify not only the changed item but also dependent rules and integrations. Migrations must be scripted or procedurally controlled, with pre- and post-deployment checks that confirm completeness and consistency. Back-out plans protect continuity when a change introduces unintended effects.

Segregation of duties prevents conflicts: configuration designers should not unilaterally approve or release changes, and testers should be independent of authors. Access control and audit trails must capture who changed what, when, and why. Training records should demonstrate that users understand changes affecting their roles, especially where electronic signatures or critical calculations are involved.

Documentation discipline keeps audits straightforward. Keep a living catalog of configuration items, associated requirements, and traceability to executed tests. Link change requests to risk assessments and evidence, and ensure your configuration baseline is always reconstructable from the record.

Avoid this common gap

Do not treat vendor screenshots or marketing summaries as configuration specifications. Author your own controlled specifications and manage them with document control to preserve the validated state.

06Data integrity and security for configurable systems

Configurable applications must produce records that are attributable, legible, contemporaneous, original, and accurate throughout their lifecycle. Because configuration defines how and when data are captured, reviewed, and changed, data integrity is achieved by design and verified by evidence. Focus controls where configuration influences identity, sequence, calculations, limits, and approvals.

Security baselines should define roles, privileges, and segregation of duties to prevent unauthorized changes to configuration or data. Electronic signatures must be uniquely linked to individuals, with multi-factor controls where risk warrants. Time synchronization, audit trail protection, and validated interfaces ensure records remain trustworthy as they traverse systems.

Lifecycle controls extend beyond go-live. Periodic review should assess access, exception trends, interface reliability, and audit trail health. Backup, restore, and disaster recovery must be tested to verify that both application data and configuration baselines can be recovered without compromising record integrity or traceability.

When mapping controls to risk, align higher assurance to steps that directly affect release decisions, critical calculations, or identity and traceability. Use technical controls where feasible, and document procedural mitigations where technology cannot fully enforce the requirement.

  • Role-based access with least privilege and enforced separation of configuration and execution roles.
  • Tamper-evident audit trails for both data and configuration, with secure time stamps and review procedures.
  • Electronic signatures uniquely bound to individuals with appropriate authentication and meaning of signature.
  • Validated interfaces with reconciliation checks and error handling for inbound and outbound data flows.
  • Automated enforcement of limits, calculations, and step sequencing where risk is significant.
  • Periodic review of exceptions, overrides, and audit trail events with documented follow-up.
Design for Integrity

Bake controls into configuration rather than relying solely on procedures. Start from data integrity by design principles and calibrate with MHRA and Annex 11 expectations.

07Common pitfalls and misinterpretations

Category 4 is frequently underestimated because teams conflate “no custom code” with “minimal validation.” In reality, configuration can implement complex logic comparable to custom development, and it must be specified, verified, and controlled with equal rigor. The most persistent issues trace back to weak requirements, undocumented configuration choices, and inadequate traceability.

Another trap is over-reliance on vendor claims or generic test scripts. Supplier assurance is necessary, but it does not validate your unique configuration for intended use. Likewise, organizations sometimes test only happy paths and skip negative or boundary conditions where configuration often fails silently.

Integration risk is often overlooked. Configurable systems frequently exchange data with ERP, laboratory instruments, historians, or label printers. Interface mappings and error handling must be verified under realistic loads, including retries, partial failures, and data format mismatches. Change control must include interface contracts and environment parity checks.

Finally, configuration and master data are sometimes mixed in governance. Parameters that implement logic belong under configuration control, whereas operational master data can follow business data governance, with appropriate checks and approvals. Clarity on these boundaries supports sustainable compliance.

  • Treating configuration as self-evident and skipping written specifications and traceability.
  • Using vendor demo scripts as test evidence rather than risk-based, requirement-linked tests.
  • Ignoring negative tests and role-based authorization scenarios for critical steps.
  • Failing to control interfaces and data transformations that alter record meaning or context.
  • Confusing configuration with master data, leading to inconsistent governance and review.
  • Underappreciating design control style discipline for logic-heavy configurations aligned to 21 CFR 820.

08How Category 4 relates to neighboring frameworks

GAMP 5 places Category 4 between commercial software used essentially as delivered and custom-built solutions. The validation approach borrows from both neighbors: leverage supplier assurance and standard platform testing where appropriate, but specify and verify configured logic as if it were an implementation of requirements. This hybrid posture keeps effort proportionate and defensible.

Annex 15’s validation lifecycle and ICH Q9’s risk management are the primary anchors for planning and justification. In manufacturing contexts, process validation concepts reinforce the need for ongoing verification: monitor exceptions, rejections, and review comments to confirm that configured controls remain effective. When configuration begins to include scripts or bespoke extensions, the scope migrates toward Category 5 practices.

Neighboring categories also help with right-sizing documentation. Category 3-level functions may be verified with basic user acceptance tests, while logic-intensive Category 4 features demand detailed specifications and negative testing. If a workflow is extended with custom code modules or complex scripts, adopt Category 5-level design, code review, and unit testing requirements for that portion.

Auditors expect coherent justification when a system spans categories. Make the category assignment at the function level where needed, and present a matrix that shows verification depth aligned to risk and implementation type. This transparency prevents over- or under-testing and reduces remediation during inspections.

Right-Size by Function

A single platform may contain Category 3, 4, and 5 functions. Assign category and verification depth function-by-function to keep effort aligned to risk and implementation.

AspectCategory 3 (Non-configured)Category 4 (Configurable)Category 5 (Custom)
Typical examplesCOTS viewer, basic reportingMES workflows, QMS CAPA, LIMS methodsCustom calculators, bespoke modules
Implementation mechanismUsed as deliveredBusiness logic via parameters and rulesSource code or complex scripts
Documentation emphasisUser requirements, basic UATRequirements, configuration specs, traceabilityDesign specs, code review, unit tests, traceability
Testing focusFit for intended useRisk-based, role and negative testsComponent, integration, and system tests
Change controlRelease notes and impact checkFormal change control with baseline managementFull SDLC change control

09How V5 Ultimate supports Category 4 implementation

V5 Ultimate treats configuration as a first-class, governed asset. Requirements, configuration items, and tests are linked, versioned, and released together so that traceability from intended use to evidence is always clear. Configuration catalogs, baselines, and environment promotion workflows keep development, test, and production aligned and reconstructable.

For execution systems, V5 enforces role-based access, electronic signatures, and secure audit trails that cover both data and configuration events. Exception capture, review by exception, and analytics provide ongoing verification that configured controls are operating as intended. Interfaces are validated with reconciliation checks and monitored for reliability.

In regulated operations, closing the compliance loop at execution matters. V5’s configuration governance spans MES, QMS, EBR and eDHR, LIMS, WMS, and Maintenance so that the system of record reflects the approved configuration and the executed evidence without fragmentation. This reduces inspection preparation and supports rapid, controlled change.

Organizations can implement proportionate, risk-based validation with reusable templates, test libraries, and automated traceability. The platform’s audit-ready exports, electronic signatures, and aligned configuration and data backups support Annex 11 and Part 11 expectations while keeping total validation effort sustainable.

Built-in Controls for Category 4

V5 provides governed configuration catalogs, linked requirements and tests, role-based approvals, secure audit trails, and environment promotion controls. Features such as step sequence enforcement, traceability, and audit readiness keep your Category 4 systems validated and inspection-ready.

Frequently asked questions

Q.What defines a GAMP 5 Category 4 system?+

A Category 4 system is a configurable application where business logic is implemented via controlled configuration rather than custom code. Validation must demonstrate that the chosen configuration fulfills intended use and preserves data integrity.

Q.How does Category 4 differ from Category 3 and Category 5?+

Category 3 is used essentially as delivered with minimal configuration, while Category 5 involves custom code or complex scripting. Category 4 sits between them, requiring specifications and risk-based testing for configured logic.

Q.Do vendor test reports replace my validation for Category 4?+

No. Supplier documentation supports platform assurance but does not validate your specific configuration. You must specify, verify, and control your configuration aligned to intended use and risk.

Q.What evidence is most critical for audits of Category 4 systems?+

Auditors look for clear traceability from user requirements to configuration specifications and executed tests, robust change control records, and data integrity controls including secure audit trails and role-based access.

Q.When should negative testing be performed?+

Negative and boundary tests are essential when configuration enforces limits, calculations, sequence controls, or approvals. They reveal failure modes that are not visible in positive-only testing.

Q.How often should Category 4 configurations be reviewed post go-live?+

Perform periodic reviews based on risk, typically annually or triggered by significant changes. Assess access rights, exceptions, interface health, and audit trail activity to confirm controls remain effective.

Q.Can one system span multiple GAMP categories?+

Yes. Assign the category at the function level. A platform can include Category 3 reporting, Category 4 workflows, and Category 5 scripted extensions, each validated with proportionate controls.

Primary sources

  • ISPE GAMP guidance
  • EU GMP EudraLex Annex 11
  • 21 CFR Part 11 (Electronic Records, Electronic Signatures)
  • ICH Q9 Quality Risk Management
  • PIC/S GMP resources
  • MHRA data integrity guidance
  • FDA medical devices: software and validation resources
  • ISO 13485 medical devices quality management
  • EUR-Lex: EU law access

Further reading

  • GAMP 5
    Understand the overall GAMP 5 framework and lifecycle for computerized system compliance.
  • GAMP 5 Category 3
    See how non-configured commercial software is validated with proportionate effort.
  • GAMP 5 Category 5
    Learn what changes when systems are custom-coded or heavily scripted.
  • EU GMP Annex 11
    Review the EU expectations for computerized systems and electronic records.
  • 21 CFR Part 11
    Read the FDA rule governing electronic records and electronic signatures.
  • Risk-based validation
    Explore how to scale validation activities based on impact and criticality.
  • ICH Q9 Quality Risk Management Readiness
    Apply ICH Q9 principles to computerized systems and validation planning.
  • Paperless Validation Playbook
    Modernize validation with digital traceability and proportionate evidence.
  • Electronic Batch Record
    Understand EBR concepts, controls, and inspection expectations.
  • MES
    Learn how MES platforms orchestrate manufacturing and support compliance.
Software that covers GAMP 5 Category 4
V5 Ultimate for CSV / CSA
Requirements traceability, test evidence, change impact and periodic review in one place. Your QA approves the validation; IQ/OQ…
V5 Ultimate Pharma 4.0 Platform
Connected execution, quality and lab records with AI-assisted drafting for CAPA and deviations, reviewed and signed by people, on…
V5 Ultimate (21 CFR Part 11)
V5 Ultimate gives FDA-regulated manufacturers bound e-signatures, an audit trail, authority checks and printed-copy controls. An…
V5 Ultimate (Validation Management)
V5 Ultimate helps life-science sites manage Computer System Validation (CSV) and Computer Software Assurance (CSA) work: linked…
Talk to us about GAMP 5 Category 4

Want to see how GAMP 5 Category 4 could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.

Start free
Back to glossary
Where this term comes up
PharmaceuticalMedical DevicesRadiopharmaDietary SupplementsCosmetics
Inside V5
  • → eBMR / eDHR — the batch record fills in as the work is done.
  • → 21 CFR Part 11 — signatures and audit history your team can validate.
Example reports
V5Ultimate

Sample report

Electronic Batch Manufacturing Record (eBMR)

Plan & make

Electronic Batch Manufacturing Record (eBMR)View on screen or print
V5Ultimate

Sample report

Electronic Device History Record (eDHR)

Plan & make

Electronic Device History Record (eDHR)View on screen or print
V5Ultimate

Sample report

Compliance Readiness Assessment

Quality system

Compliance Readiness AssessmentView on screen or print
V5Ultimate

Sample report

Validation Support Pack

Quality system

Validation Support PackView on screen or print
→ All example reports
Regulatory anchors
  • ISPE GAMP 5 (2nd Ed.)
  • EU GMP Annex 11
  • 21 CFR Part 11
  • ISA-95
Related terms
  • → GAMP 5
  • → CSV
  • → CSA
  • → EU Annex 11
  • → 21 CFR Part 11
  • → IQ / OQ / PQ
  • → MES

Next Step

Try V5 with your own records, or ask a question first. Ask V5 opens with an editable question; nothing is sent until you choose to.

Start your free trial Browse All Features

Showing the site for the United States. Local spelling, dates and prices are applied automatically; change the language at the top of the page.

V5 Ultimate
Ultimate

Warehouse, quality and manufacturing software for regulated operations.

ProductIndustriesPricingResourcesSecurity & TrustCompanyLegal Centre

© S.G. Systems, LLC