IT systems · Practical guide

Sage X3: testing quality status and inventory release

In Sage X3, Q identifies stock under quality control. Configured rules determine which movements or uses are permitted. A transfer inside quarantine may be intended while issue to production must be prevented. Test the action that actually succeeds or fails.

Table of contents

At a glance

Does status Q in Sage X3 automatically prevent all stock withdrawals?

No. Sage’s X3 documentation explains that management rules determine whether stock with status Q or R can be allocated or withdrawn. Test the intended blocking behaviour in your actual configuration. Include elevated privileges and alternative ways of changing the status.

Scope and Applicability

The basis is the publicly available Sage-X3 V12 Help document for Quality Control. Our own release and configuration status remains decisive. The article addresses the impact of the inventory status, not the technical suitability of an analytical testing method.

Sources: [1]

Separate status designation and actual use

Sage X3 records inventory as A for accepted stock, Q for quality control, and R for rejected stock. A general blocking effect cannot be inferred from this. The manufacturer's guide explicitly states that Q- and R-stock are assigned and even issued according to defined rules. Therefore, for validation, the specific allowed or prohibited movement must be considered.

Capture product category, location, inventory rules, sub-status, and user permissions. Also assess privileged capabilities; the manufacturer's guide describes a stock administrator context with enhanced inventory manipulation. A test conducted solely with a standard user cannot cover this exception. Document who requires such rights and how their usage is controlled.

Formulate the technical requirement for each critical process. For example, Q stock should not enter a specific production step while a controlled movement is allowed for examination. This rule is a separate process decision. It is not only demonstrated by setting the letter Q.

Sources: [1] [2]

Build a status matrix for each movement and role

Select the actually relevant movements: Inbound, Assignment, Withdrawal, internal movement, return, or dispatch. Describe for each status which action is permitted. Add user role and, if applicable, location. The combination makes visible where the same batch may be handled differently.

Consider open activities. A status change may occur even after an order has already been prepared. Verify that the selected rule is re-evaluated at the correct point. A positive test on a newly created order does not automatically validate the handling of an ongoing process.

Internal work aid: Develop a status matrix for each movement and role.
Background from our own exampleActionExpected Regulation
A-Inventory Defined routine issue Permissible under appropriate additional conditions
Q-Stock Critical Production Use As specified by the customer, limited
Q-Stock Controlled movement for investigation Only to the extent explicitly specified
R-Stock Standard distribution Not permitted by own specification
Preferred user Status or movement to be changed Exception authority and traceability verified

Sources: [1]

Example and inspection table: Q-stock during sampling step

A company expects that Q-stock should block a specific withdrawal step. However, the configured rule does not enforce this restriction. The interface correctly displays Q, and the status comparison confirms the expected state. The technical negative test reveals that the intended control has not been implemented. This gap arises due to configuration; the example does not indicate a defect in Sage X3 and is not a completed product test.

Prepare two comparable batches with A and Q using the same generic user and the same designated sampling procedure. The internal target rule permits A and restricts Q. Document product, location, quantity, status, role, and actual result. The expected response shall be defined prior to execution.

Subsequently, verify the privileged role and an open assignment. If an exception is permitted, it must be clearly justified within the procedure. A technically possible administrative action is not automatically invalid and may not be treated as an ordinary, invisible process. After configuration correction, both authorized and unauthorized cases shall be re-evaluated.

Capture the underlying product category and site rule jointly with the movement. If the intended effect fails, differentiate between status value, active rule, and user authorization. After a correction, the permitted work must continue to function.

Own work aid: Status impact based on action and authorization
Test caseActionExpected evidence
Positive case Issue stock from A The permitted workflow succeeds
Negative case Withdraw Q-remaining from the critical step Own containment rule applies
Exception Perform a designated special movement Only authorized exception scope
Open task Status after preparation change The current status is considered at the relevant point.
Preferred access Edit with special rights Authority and actual actions traceable
After correction Rerun the matrix again No unexplained adverse effect on authorized work

Sources: [1]

Quality inspection, status change and attributes integration

The manufacturer support document describes configuration-dependent workflows between quality records and status changes. Assess which outcomes prepare a decision and who is authorized to actually set the status. A fully completed form does not automatically demonstrate a reasonable evaluation of the result.

Consider modifications to batch attributes outside the actual quality control step, where such changes are feasible for implementation. A expiry date or relevant additional field may influence future use. Therefore, verify not only the main screen but also the actual accessible pathways to the critical data object.

For partial quantities, a clear assignment is essential. A quality decision cannot be transferred to another inventory or a different quantity without detection. Select a test with partitioning or multiple inventory lines if this is part of the process. The validation evidence links the result, the decision, and the actual affected quantity.

Sources: [1] [2]

Verify interfaces and changes appropriately.

When an external warehouse or another system is involved, monitor status and tracking information across system boundaries. Correctly transmitted messages do not necessarily demonstrate proper recipient impact. Evaluate appropriate error, delay, and retry scenarios. The required blocking effect remains a characteristic of the entire selected workflow.

Changes to product category, inventory rules, user status, or user permissions may affect the matrix. Therefore, evaluate configuration changes even in the absence of a new software version. A static program version is not evidence of unchanged scientific efficacy. Establish the linkage between the approved regulatory version and the test.

Provide the status matrix, relevant exceptions, and point of contact to the functional and IT departments. A subsequent finding should be traceable to clarify whether the status, rule, role, or interface was affected. This does not automatically eliminate all errors, but it establishes a viable foundation for targeted investigation and improvement.

Sources: [1]

Next steps

  • Define allowed movements per status and role.
  • Capture relevant regulations, locations, and special rights.
  • Test batch retrieval, transfer, and status updates with counterexamples.
  • Investigate deviations and approve the active configuration.
Further reading:

Project experience and collaboration

Test whether the hold prevents the specific material movement

With Warehouse and Quality, we agree which movements your X3 configuration should allow for stock statuses A, Q and R. IT identifies relevant product categories, sites and assigned permissions. An internal transfer may be allowed while a particular withdrawal must remain blocked. If behaviour differs from expectation, we investigate the rule, role and open transaction separately. After correction, we also test that required permitted work remains possible.

Frequently asked questions about Quality status in Sage X3

Does A automatically constitute a regulatory batch release?

No. A technical inventory status must be linked to the technical release process. The required decision and responsibility are not thereby replaced.

Sources: [1] [2]

Must every product category be verified?

Assess whether different rules exist. Representative tests require a justified similarity; divergent rules must not be combined without evaluation.

Sources: [1] [2]

Are intermediate statuses problematic?

Understatus can reflect professional differences, but must be appropriately considered in selection, movement, and release rules. Assess their actual impact on product- and site-specific regulations. A clear designation alone does not confirm the intended blocking effect.

Sources: [1] [2]

Does Q in Sage X3 always indicate a technical lock?

No. The documented impact depends in part on the configured inventory rules. Review the specific movements in accordance with the assigned roles. A visible status confirms only the labeling. The desired restriction must be validated within the actually relevant business process, including justified exceptions and open activities.

Sources: [1] [2]

Can a stock administrator move Q-quantity inventory despite being authorized?

The Sage-V12 Help document outlines additional capabilities for the Stock Administrator regarding inventory management. Therefore, verify actual movements even with such special privileges and local rules. A business-justified exception must be granted limited authorization and demonstrate clear and traceable usage. A successful test of the standard role does not automatically cover this access.

Sources: [2] [1]

Why must the same status be verified across multiple movements?

Since the effect of configured rules and the specific process depends on them, an allowed internal movement is not automatically an allowable release. Define relevant actions and verify their actual response. The status name alone does not confirm universal blocking effect.

What do we do in the case of an administrative exception?

State the purpose, authority, and requirement for traceability. Assess which technical data or movements may be modified. A business necessity may justify such changes, but it must not be ambiguously considered a routine operational practice. The evaluation shall be based on actual usage and potential impact.

Sources and review date

The sources provide the technical foundation. Tables, checklists, and examples are derived methodological tools, not verbatim regulatory requirements. Manufacturer information must be referenced to the specific version and configuration in use.

  1. European Commission: EU GMP Annex 11, Computerised Systems (2011)Current version as per EudraLex inventory as of 14.10.2026. Application, risks, operation, and data lifecycle; specific testing proposals are derived independently.
  2. Sage X3: Quality ControlSupplier source for product functionalities. Availability and behavior depend on version, edition, license, and configuration; no general compliance certification.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Verify status rules in Sage X3 selectively

At a critical inventory movement, we consider with your team product category, local rules, and user rights. The key factor is the observed impact on authorized and unauthorized use.

  • Computer system validation →

    Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

Send a project enquiry Customer testimonials →