IMScollect
ISO 9001

ISO 9001, clause 8.2: Clarifying customer requirements

Title in the standard: “Requirements for products and services”

Do you know what the customer wants before you commit, and can you actually deliver it? Clause 8.2 of ISO 9001 as seen from the audit.

Philipp Kappe

Philipp Kappe

Founder of IMScollect

Updated 15 November 2026

What it is about

Clause 8.2 governs the start of every order: what exactly is to be delivered, under which conditions, and can the organisation do it at all? The standard prescribes no particular form, but it does require a reliable clarification before the organisation commits to the customer, that is before the quotation, the order confirmation or the signature on the contract.

The clause has four parts. Customer communication (8.2.1) covers information on products and services, enquiries, orders and changes to them, feedback and complaints, the handling of customer property and, where needed, arrangements for emergencies. Determining the requirements (8.2.2) is about what the customer explicitly asks for, what laws prescribe and what the organisation sets for itself. The review (8.2.3) takes place before the commitment and also resolves differences between quotation and order. If requirements change later (8.2.4), the documents are updated and the people concerned are informed.

In the audit, 8.2 is where a real order begins its path through the system. Many later findings in production, release or complaints can be traced back to a question that was not asked here. That is why auditors like to follow an order from enquiry to delivery and look particularly closely at the beginning. How things continue in operational planning is described in 8.1.

What the auditor checks

  • “Show me the review of this order before it was confirmed.”

    Whether the review took place before the commitment and not afterwards, and who carried it out. A date after the order confirmation, or no trace at all, shows that the organisation committed without reviewing. The form is free: a field in the ERP system, a note on the order or a checklist is enough, provided it can be traced.

  • “What was in the enquiry, what in the quotation and what in the purchase order, and where did you resolve the differences?”

    Whether differences between quotation and order were recognised and clarified with the customer, for example an earlier delivery date, a different quantity or a new drawing revision.

  • “Which requirements did the customer not state that you still have to meet?”

    Whether the organisation knows the intended use and derives requirements from it, including statutory ones on substances, labelling or safety. Anyone who only works through the lines of the purchase order misses this level.

  • “How did you know you could meet the deadline?”

    The ability to meet the requirements: capacity, material, competence, measuring equipment. An order review that only looks at price and payment terms does not answer this question.

  • “The customer changed something after ordering. How did production and purchasing find out?”

    Whether changes reach the places that need them and whether the documents were updated. Comparing what sales knows with what is written on the order in the workshop is revealing.

  • “How do telephone orders or orders through your web shop pass through the review?”

    Whether there is a way to confirm the requirements before acceptance for orders without a written purchase order. For catalogue goods in a web shop, the review can lie in the product information and terms; the organisation should be able to explain why that is enough.

Which evidence convinces

  • The recorded review per order or per type of order

    The standard requires the results of the review and any new requirements to be retained. A note with date, name and result on the order confirmation is often enough.

  • Quotation, purchase order and order confirmation side by side

    Comparing the three versions shows the auditor whether differences were recognised and resolved. A confirmation that quietly departs from the quotation stands out immediately.

  • Defined review points for the order review

    A short list of what is checked before every commitment makes the review repeatable and independent of who happens to be working in sales.

  • The trail of a change

    An amended order with a new revision, a date and evidence that production, purchasing or dispatch were informed. That demonstrates 8.2.4 on a real case.

  • Defined channels for enquiries, feedback and complaints

    Who receives them and where they go. They link 8.2 with customer satisfaction in [9.1](/en/standard-chapters/9-1-monitoring-and-measurement) and with [nonconforming outputs](/en/standard-chapters/9001-8-7-nonconforming-outputs).

Typical nonconformities

  1. Review after the commitment

    The order confirmation goes out and the technical clarification follows later or not at all. If the review is missing for individual orders, that is a minor nonconformity. If the organisation has no review before commitment at all, the requirement is not met: a major nonconformity.

  2. Differences between quotation and order unresolved

    The customer orders to a newer drawing revision or with a shorter lead time, and nobody noticed. This often only becomes visible as a complaint.

  3. Only explicit requirements considered

    Statutory obligations relating to the product, or requirements arising from the intended use, are missing from the review, for example rules on substances, labelling or accompanying documents that the customer takes for granted.

  4. Changes do not reach the workshop

    Sales has confirmed the change, but production is still working from the old order. That is a gap between 8.2.4 and the control of production in [8.5](/en/standard-chapters/9001-8-5-production).

  5. Reviewed but not recorded

    Everyone assures you that every order is reviewed, but only in their heads. Without a record, the audit can show neither that the review took place nor what came of it.

  6. Call-offs under framework contracts not reviewed

    The framework contract was reviewed once, the individual call-offs no longer, although quantities, dates or revisions have changed.

Differences by standard

ISO 9001ISO 9001

Clause 8.2 exists in this form only in ISO 9001; in ISO 14001 and ISO/IEC 27001 the number 8.2 carries other topics, namely emergency preparedness and the information security risk assessment. The 2026 edition keeps the structure of 8.2 and adds to customer communication: where needed, it also includes information for emergencies and disruptions, for example how the customer learns that a delivery will not arrive as planned because of an outage. If an organisation promises its customer requirements on environmental protection or information security, they belong in the review at this point.

How IMScollect covers it

In IMScollect, the order review sits in the customer requirements area. For each order you record the customer, the review date and the person reviewing, and work through six review points: the customer’s requirements including delivery and post-delivery activities, requirements not stated but necessary, your own specifications, statutory and regulatory requirements, the resolved differences from the quotation and the ability to meet everything. A note can be added to each point.

The result is accepted, accepted with reservation or rejected; the customer’s confirmation and any newly added requirements are recorded as well. You attach evidence such as the purchase order as a document or file, and later changes appear in the entry’s history. The list shows at a glance where review points are open or an order was accepted only with reservation.

Try it yourself, no call needed.Prefer a walkthrough? Book a guided demo →

Frequently asked questions

Does every order have to be reviewed individually?▾

The review takes place before you commit to supplying. For similar orders, such as catalogue goods or call-offs under a reviewed framework contract, the review can lie in defined rules and does not have to be written down anew each time. If quantity, date or revision changes, it is reviewed again.

What applies to verbal or telephone orders?▾

They too are confirmed before acceptance. The form is free, for example a short confirmation by email or a note in the order system. What matters is that it can later be traced what was agreed.

Which records does clause 8.2 require?▾

The results of the review and, where applicable, new requirements for the product or service. If requirements change, the documents concerned are amended. The standard does not prescribe a particular form.

Can clause 8.2 be excluded?▾

In practice, no. Every organisation that supplies products or services to customers has to clarify their requirements. Only what genuinely does not occur can be excluded, and the justification belongs in the scope.

Further reading and viewing

Philipp Kappe

Philipp Kappe

Founder of IMScollect

Philipp builds IMScollect. TÜV-certified auditor with a background in governance, risk and compliance, more than 200 audits conducted and supported.

This page explains in our own words and does not replace the text of the standard. You can obtain the standards from ISO(opens in a new window) or from your national standards body. Clause numbers and titles follow ISO 9001:2026, ISO 14001:2026 and ISO/IEC 27001:2022.