Why Product Specifications and Laboratory Results Need to Match

Product specifications and laboratory results need to align. Learn why methods, acceptance criteria, units and quality requirements must match for reliable decisions.

A laboratory result is only useful when you know what it is being compared against.

That sounds obvious, but mismatches between product specifications and laboratory results are more common than they should be.

A specification might say that an active ingredient must be between 95% and 105%. The laboratory may report a different unit, use another analytical method or apply a different acceptance criterion.

The result itself can be perfectly valid.

Yet the quality decision may still be unclear.

For regulated products, specifications define the tests and acceptance criteria used to determine whether a product meets its intended quality requirements. In pharmaceutical development, ICH Q6A explicitly defines specifications as a set of tests, analytical procedures and acceptance criteria. European Medicines Agency (EMA)

That is why the specification and the analytical result need to belong to the same quality system.


What is a product specification?

A product specification defines what a product is expected to meet.

Depending on the product, it can include:

  • identity
  • appearance
  • pH
  • viscosity
  • active ingredient content
  • purity
  • microbiological limits
  • contaminant limits
  • moisture
  • physical properties
  • stability-related parameters

Each parameter should have an appropriate test method and acceptance criterion.

For pharmaceutical products, EMA guidance links specifications directly to analytical procedures and acceptance criteria. European Medicines Agency (EMA)

The same basic quality principle is useful for other regulated products:

You need to know what you are testing, how you are testing it and what result is acceptable.


A laboratory result needs a reference point

Imagine a laboratory reports:

Vitamin C: 482 mg/L

Is that good?

There is no way to know without additional information.

If the specification is:

450–550 mg/L

the result passes.

If the specification is:

500–550 mg/L

it does not.

The laboratory has not changed.

The result has not changed.

Only the acceptance criterion is different.

That is why analytical results should always be interpreted against the correct, current specification.


The specification should come before the test

A common mistake is to send a product to the laboratory and decide what the result means afterwards.

A stronger approach is to define the specification first.

Before testing, establish:

What parameter are we measuring?

Which method will we use?

What is the acceptance range?

What happens if the result is outside that range?

This creates a clear decision framework before the data arrive.


Method and specification need to match

Two laboratories can analyse the same parameter and produce slightly different results.

That does not automatically mean one laboratory is wrong.

The analytical method can influence:

  • accuracy
  • precision
  • specificity
  • detection limits
  • quantification limits
  • sample preparation
  • reported units

EMA’s ICH Q2(R2) guidance covers validation of analytical procedures and considers characteristics such as accuracy, precision, specificity, detection limit, quantitation limit and range. European Medicines Agency (EMA)

Therefore, a specification should be linked to a method that is suitable for the parameter being controlled.


Units can create hidden problems

Consider a specification that states:

Heavy metals: ≤ 10 mg/kg

The laboratory reports:

Heavy metals: 8 µg/g

At first glance, the numbers look completely different.

They are actually equivalent because:

1 mg/kg = 1 µg/g

So 8 µg/g corresponds to 8 mg/kg.

The result passes.

Unit conversion is simple, but mistakes here can lead to incorrect quality decisions.

That is why specifications and laboratory reports should use clearly defined units.


The same substance can have different specifications

A limit is not necessarily universal.

The applicable acceptance criterion can depend on:

  • product category
  • intended use
  • dosage
  • target population
  • ingredient
  • regulatory requirements
  • analytical method

For example, a contaminant limit for a food product cannot simply be copied into a cosmetic specification.

The specification needs to reflect the actual product and applicable requirements.


Regulatory limits and internal specifications are not always identical

A company may choose to set an internal specification that is tighter than the legal limit.

For example:

Legal limit: ≤ 10 mg/kg

Internal specification: ≤ 5 mg/kg

A laboratory result of 7 mg/kg would therefore:

  • comply with the legal limit
  • fail the company’s internal specification

Both statements can be true.

This distinction is important because a regulatory limit and a quality specification serve different purposes.

The internal specification can provide an additional quality-control margin.


What happens when a result is close to the limit?

Suppose the specification is:

95–105%

and the laboratory reports:

95.1%

The result passes.

However, the proximity to the limit may justify additional attention depending on the product and measurement uncertainty.

The question becomes:

How confident are we that the measured value represents the true value?

Analytical uncertainty can be particularly relevant when decisions are made close to an acceptance limit.

A specification should therefore be supported by an appropriate analytical method and a realistic understanding of measurement variability. ICH Q6A specifically notes that expected analytical and manufacturing variability should be considered when establishing acceptance criteria. European Medicines Agency (EMA)


A specification should reflect real manufacturing variability

Specifications should not be chosen arbitrarily.

Imagine a product naturally produces active-content results between:

98% and 102%

during normal manufacturing.

Setting the specification at:

99.9–100.1%

might create repeated failures even though the process is performing consistently.

The opposite problem is also possible.

A specification that is too broad may allow meaningful quality changes to pass unnoticed.

Good specifications therefore need to balance:

product requirements

regulatory expectations

analytical capability

and normal manufacturing variability.


Specifications can change during product development

A product specification is not necessarily fixed from the first prototype.

During development, companies may learn more about:

  • formulation behaviour
  • stability
  • manufacturing variability
  • analytical performance
  • degradation
  • critical quality attributes

The specification can then be refined where appropriate.

For pharmaceuticals, EMA guidance notes that specifications should be justified using development data, relevant standards, batch data and stability results. European Medicines Agency (EMA)

This is one reason why quality and analytical teams should work closely with R&D.


What happens when the laboratory uses a different method?

This situation deserves attention.

Suppose your internal specification was developed around HPLC method A.

The external laboratory uses HPLC method B.

Both methods may be scientifically appropriate.

However, the results may not be directly interchangeable without demonstrating comparability.

Differences in sample preparation, calibration or selectivity can influence the reported value.

Before comparing the result with the specification, confirm:

  • method identity
  • method suitability
  • units
  • calculation basis
  • reporting format
  • acceptance criteria

That simple check can prevent a misleading pass or fail decision.


Microbiology needs the same logic

The principle also applies to microbiological testing.

A specification might state:

Total aerobic microbial count: ≤ 100 CFU/g

The laboratory could report:

70 CFU/g

That appears straightforward.

However, microbiological specifications can involve specific organisms, different limits and defined test methods.

A product might therefore pass one microbiological parameter while failing another.

The testing programme needs to reflect the actual specification.


Cosmetics provide a useful example

For cosmetic products, relevant physical and chemical specifications can include parameters such as:

  • physical state
  • colour
  • odour
  • pH
  • viscosity

European Commission guidance also notes that relevant physicochemical parameters should be controlled for finished cosmetic products, with the criteria, methods and batch results documented. Public Health

The EU Cosmetics Regulation also requires the Cosmetic Product Safety Report to include physical and chemical characteristics, stability and microbiological quality information. Public Health

That means the specification, analytical method and resulting data need to remain consistent with the actual product.


A cosmetic example

Imagine a face cream has an internal specification of:

pH: 5.0–6.0 at 25°C

A laboratory reports:

pH: 6.2

The result is clear.

It does not meet the specification.

But what if the laboratory measured the sample at 20°C while the specification is defined at 25°C?

Now the result needs further evaluation.

The issue is not necessarily the laboratory.

The issue is that the test conditions do not match the specification.


Food products need the same discipline

For food and supplements, specifications can cover:

  • nutrient content
  • active ingredients
  • contaminants
  • microbiological parameters
  • moisture
  • physical characteristics

The laboratory result should be interpreted against the correct product specification and applicable regulatory requirements.

For example, a nutrient value can support a label declaration, but the analytical result must be obtained using a suitable method and interpreted in the correct context.

A number without a defined specification is just a number.


Supplier specifications can create another mismatch

Raw materials often arrive with supplier specifications.

Your finished product has its own specifications.

Those two systems should not be confused.

A supplier may specify:

Raw material purity ≥99%

while your finished product specification may require:

Active content 95–105%

The supplier result supports raw-material control.

It does not automatically demonstrate that the finished product meets its own specification.

That distinction becomes especially important when processing can affect the final composition.


Specifications should connect the entire quality chain

A strong quality system creates a logical chain:

Raw material specification

↓

Manufacturing controls

↓

Finished-product specification

↓

Analytical method

↓

Laboratory result

↓

Quality decision

Each stage should connect to the next.

If the links are unclear, quality decisions become harder to defend.


What if the specification changes after testing?

This is a serious issue.

Imagine a batch is tested against:

Specification A: 90–110%

The result is:

108%

The batch passes.

Later, the company changes the specification to:

95–105%

The same laboratory result now fails.

That does not mean the laboratory result changed.

It means the acceptance criterion changed.

Specifications should therefore be controlled through document and change-control processes.

In pharmaceuticals, changes to approved specifications can have regulatory implications and may require appropriate approval. European Medicines Agency (EMA)


Never change the specification to make a result pass

This should be obvious.

Yet when an unexpected result appears, there can be pressure to adjust the acceptance range.

That is the wrong approach.

If a batch does not meet the established specification, investigate:

  • analytical error
  • sampling
  • laboratory method
  • manufacturing variation
  • raw-material variation
  • product stability

Only after proper investigation should the specification itself be reconsidered.

A specification should describe what quality the product is expected to have, not what a particular batch happened to achieve.


What if the laboratory result looks wrong?

Do not immediately change the specification.

First investigate the result.

Possible questions include:

Was the correct sample tested?

Was the correct method used?

Was the sample handled correctly?

Were calculations performed correctly?

Was the instrument suitable and calibrated?

Is there evidence of a manufacturing deviation?

Is the result consistent with previous batches?

This creates a structured approach to out-of-specification results.


Trend data are also valuable

One result tells you about one batch.

Several results can tell you about the process.

Imagine active content results over ten batches:

101 → 100 → 101 → 100 → 99 → 99 → 98 → 98 → 97 → 96

Every batch may still meet the specification.

However, the trend suggests something is changing.

That could justify an investigation before the product actually fails.

Specifications therefore work best when combined with ongoing trend analysis.


Testing should support quality decisions

The purpose of analytical testing is not simply to generate laboratory reports.

The data should help answer questions such as:

  • Can this batch be released?
  • Does the raw material meet its specification?
  • Is the process under control?
  • Has stability changed?
  • Is a formulation change acceptable?
  • Does the product remain within specification?

This is why analytical testing and quality management should not operate in isolation.


What makes a good specification?

A useful product specification should be:

Clear

The parameter and acceptance criterion are unambiguous.

Measurable

A suitable analytical method exists.

Relevant

The parameter actually matters for product quality or compliance.

Justified

The acceptance range has a scientific and regulatory basis.

Current

It reflects the product and applicable requirements.

Controlled

Changes are documented and approved appropriately.

This creates a specification that can actually support quality decisions.


What makes a useful laboratory result?

The laboratory report should provide enough information to interpret the result correctly.

Depending on the analysis, that can include:

  • sample identification
  • batch number
  • test parameter
  • analytical method
  • result
  • unit
  • detection or quantification limit where relevant
  • test date
  • acceptance criterion where applicable

For pharmaceutical quality documentation, EMA guidance emphasises clear links between specifications and the analytical procedures used for testing. European Medicines Agency (EMA)

Without that context, even an accurate result can be difficult to use.


A simple quality-control checklist

Before accepting a laboratory result, check:

1. Correct product?
Does the sample match the intended batch?

2. Correct specification?
Is the current approved version being used?

3. Correct parameter?
Are you measuring exactly what the specification requires?

4. Correct method?
Does the method match the defined analytical procedure?

5. Correct unit?
Are the result and specification expressed on the same basis?

6. Correct conditions?
Were temperature, sample preparation and other relevant conditions appropriate?

7. Correct limit?
Is the acceptance criterion current and applicable?

8. Correct conclusion?
Does the result actually support the release or quality decision?

This takes little time and can prevent major misunderstandings.


The goal is consistency

The strongest quality systems create consistency between:

what you say the product should be

and

what the laboratory measures.

The specification defines the target.

The analytical method measures the relevant property.

The laboratory result provides the evidence.

Quality management then uses that evidence to make a decision.

When those elements match, the system becomes much easier to manage.


The Makrolife approach

Makrolife combines analytical testing with quality and regulatory support across product categories including food, supplements, cosmetics and pharmaceuticals.

That means laboratory testing can be planned around the actual question the company needs to answer.

For example:

What should we test?

Which method is appropriate?

What acceptance criterion should apply?

How should the result be interpreted?

Does the result support the product specification?

Those questions are connected.

The laboratory result is only as useful as the quality framework around it.


The bottom line

A product specification and a laboratory result should never exist as two separate pieces of information.

The specification defines what acceptable quality means.

The analytical method defines how that quality is measured.

The laboratory result shows what was actually found.

Only when those three elements align can the result support a meaningful quality decision.

So before asking whether a laboratory result is good or bad, ask:

Good or bad compared with what?

That reference point is the product specification.

And when the specification, method and result all match, analytical data become much more than numbers. They become evidence that the product is under control.