Skip to content

Capturing Customer Requirements for Products and Services Under ISO 9001

ISO 9001 Clause 8.2

This clause requires the organisation to determine its requirements for the products and services it provides.

What Does ISO 9001 Clause 8.2 Require?

Clause 8.2 of ISO 9001:2026 covers how the organisation determines, reviews and communicates the requirements for the products and services it provides. It has three sub-clauses covering customer communication, the determination of requirements, and the review of requirements before the organisation commits to supplying.

Clause 8.2.1 - Customer Communication

The organisation must have defined processes for communicating with customers about product and service information, handling enquiries and orders, obtaining customer feedback (including complaints), and handling or controlling customer property. Where relevant, the organisation must also have arrangements for dealing with contingency actions when required, and must provide customers with information about those contingency actions. That includes contingency actions related to disruption of the provision of products or services, which is the point where this clause meets the treatment of disruption as a risk under Clause 6.1.

Clause 8.2.2 - Determining Requirements

When determining requirements for products and services, the organisation must consider customer requirements (including delivery and post-delivery requirements), any requirements the organisation considers necessary (even if the customer has not stated them), statutory and regulatory requirements applicable to the products and services, and any applicable contractual obligations.

Clause 8.2.3 - Review of Requirements

Before committing to supply a product or service, the organisation must review the requirements to ensure it has the ability to meet them. This includes requirements specified by the customer, requirements not stated by the customer but necessary for intended use, statutory and regulatory requirements, and any contract or order requirements that differ from previously stated requirements.

Where requirements change after the commitment to supply has been made, the relevant documented information must be updated and the relevant people notified of the change.

The thing I focus on most for Clause 8.2 is how unstated requirements are being handled. Most organisations are fine on explicit customer requirements - they know what the customer asked for. Where they fall down is on the implied ones: legal standards, safety requirements, industry norms the customer would assume are being met. I'll ask the people handling enquiries and orders how they check those, and whether they would catch it if a customer asked for something the organisation couldn't legally or safely deliver. That conversation tells me a lot.

The review before committing to supply doesn't need to be elaborate. For routine, standard orders it can be as simple as a checklist confirmation. For complex or bespoke work it needs more - specific requirements captured, regulations checked, any contractual terms reviewed. What matters is that the review happens before the order is accepted, not after something goes wrong. The IMS1 Manual covers the enquiry and order process and provides a structured basis for evidencing that the review is taking place.

One area that often gets overlooked is changes to requirements after an order is confirmed. If a customer changes the specification mid-way through, that needs to be documented and communicated internally - otherwise you end up delivering to the original spec while the customer is expecting something different.

Clause 8.2.4 - Changes to Requirements for Products and Services

Where the requirements for a product or service change, the organisation must make sure the relevant documented information is amended, and that the people affected are made aware of the changed requirements. The standard extends that to relevant interested parties, so the duty to communicate a change is not limited to the people inside the organisation who have to act on it.

In practice that usually means the customer, but it can reach further where a change affects a subcontractor delivering part of the work, a regulator with an interest in the specification, or anyone else identified under Clause 4.2 whose requirements the quality management system is addressing.

If you are still working to ISO 9001:2015

ISO 9001:2026 was published on 16 September 2026 and replaces ISO 9001:2015. Two additions sit in this clause: customer communication now includes providing information about contingency actions, including those related to disruption of the provision of products or services, and changes to requirements must be communicated to relevant interested parties rather than only to the people inside the organisation.

The changes between the 2015 and 2026 editions are covered clause by clause.

Practical Compliance Guidance

To comply with Clause 8.2, the organisation needs a defined process for reviewing customer requirements before committing to supply, records of those reviews, and a clear approach to customer communication including handling of complaints and changes.

The alphaZ documents below support compliance with Clause 8.2.

alphaZ document How it supports Clause 8.2
ISO 9001 Management System Toolkit The complete toolkit including customer communication procedures, complaint handling and all supporting documents for managing product and service requirements.

Note - all the above files can be downloaded with an alphaZ subscription

Frequently Asked Questions

Do we need to review every order before accepting it?

The standard requires a review before committing to supply - but the depth of that review should be proportionate to the complexity and risk of the order. For routine, standard orders where requirements are well understood, a simple confirmation that capacity exists and standard terms apply is usually sufficient. For complex, bespoke or high-value orders, a more thorough review covering specific requirements, applicable regulations and any contractual terms is appropriate.

What counts as a customer requirement that the customer hasn't stated?

These are requirements that are implied by the intended use or application of the product or service - things the customer would expect without necessarily specifying them. For example, a customer ordering food products would expect them to comply with food safety legislation even if they haven't explicitly stated this. A customer ordering an electrical installation would expect it to comply with wiring regulations. Identifying these unstated but necessary requirements is part of the competence that an organisation brings to the supply relationship.

Further Resources