How should a chemical supplier track a customer's specification?

What do you need before you track customer specifications?

Before you track customer specifications, you need one shared log per customer, the current technical data sheet (TDS) and recent certificates of analysis (CoA) for each product the customer buys, and a named reviewer who can sign off. A spreadsheet or a document system both work; what matters is that every specification has a row and every row has the same fields.

Set these fields in the customer specification log: customer, product, specification title and number, revision identifier, revision date, date received, how it arrived, who received it, review status, reviewer, review date and the revision it replaces. Keep the file exactly as received next to the row, and never overwrite it with a later copy.

Collect your own reference documents too. A TDS states typical values, and some makers say outright that typical values "are not intended for use in preparing specifications" (Dow, 2025). Your internal release specification, the limits a lot must meet before it ships, is the document to compare against the customer's limits. If you are ISO 9001 certified, note that ISO 9001:2026 replaced the 2015 edition on 16 September 2026 (ISO/TC 176, 2026), so the clause numbers your auditor quotes may change at transition.

How does a customer specification reach a chemical supplier?

A customer specification reaches a chemical supplier through one of five routes: attached to a request for quotation, cited by number in a purchase order, downloaded from a customer supplier portal, attached to a quality agreement, or sent by a customer engineer in an email. Step 1 is to log the route the moment the document arrives.

The route matters because each one fails in a different way. A purchase order that says "per specification X, latest revision" changes your obligation without sending you a new document. A portal copy can be replaced by the customer overnight. An email attachment sits in one person's inbox and never reaches the log.

Log the date received, the route, the sender and the document identifier exactly as printed. If a purchase order cites a specification or revision you do not hold, request the document before you confirm the order, and record the request date. If the specification cites a test standard, record the edition the customer names, because a later edition can change the method. A specification that arrives with no identifier at all gets one from you: customer name, title and date received, flagged as unconfirmed until the customer confirms it in writing.

How do you know a customer specification has been revised?

You know a customer specification has been revised when its revision identifier or revision date differs from the one in your log, so step 2 is to record both for every copy you receive. Compare them each time the specification is cited, not only when a new file arrives.

Watch four signals. The cover page shows a new revision letter, number or date. The change history table lists a new entry. A purchase order or forecast cites a revision you do not hold. A portal or customer quality notice announces a change. Any one of them means the current review no longer covers the requirement.

When a revision arrives, mark the old copy "superseded" with the date and keep it, since past shipments were made against it. Then start a new review. ISO 9001:2026 clause 8.2.4 requires relevant documented information to be updated and communicated to the relevant interested parties when requirements change (Advisera, 2026). For a chemical supplier, that means production, quality control, purchasing of raw materials and the account owner all see the new revision before the next lot ships. Where a customer cites "latest revision" with no number, ask them to confirm the current revision at a fixed interval, such as each quarter (illustrative).

What should a specification review record show?

A specification review record should show which revision was reviewed, who reviewed it and when, what each requirement means for your product, and what was decided, so step 3 is to keep one signed record per revision. ISO 9001:2026 clause 8.2.3.2 requires documented information, as applicable, as evidence of review results and any new or changed requirements (Advisera, 2026).

Include these items in the review record:

1. Specification number, revision identifier and revision date.

2. Products and grades the specification covers.

3. Each property with the customer limit and test method, and your result: can meet, cannot meet, or needs clarification.

4. Packaging, labeling, documentation and change-notification requirements, which often sit outside the property table.

5. Deviations or clarifications agreed with the customer, with the customer's written confirmation.

6. Decision: accept, accept with deviation, or decline.

7. Reviewer name, role, signature and date.

8. Date the result was sent to the customer.

Keep the record next to the specification copy it reviews. A review that cannot be traced to a revision number proves nothing when the customer audits you or a lot is rejected.

How do you compare a customer specification with your TDS and CoA?

To compare a customer specification with your TDS and CoA, step 4 is to put each property on its own row and check the customer limit against your release limit, your test method and your recent CoA results. A limit that sits inside your TDS typical value is not enough, because typical values are not specifications (Dow, 2025).

Check the release limit first. If a customer allows 0.10% water and your release limit is 0.15% (illustrative), a lot can pass your CoA and still fail the customer. Then check the test method: the same property measured by a different method can give a different result, so record the method the customer names next to the one your laboratory uses. Then check recent CoA results, not only limits. ICH Q7, written for active pharmaceutical ingredients, says a CoA should list each test with its acceptance limits and numerical results (ICH, 2000), which is what makes this comparison possible.

Settle the rounding rule before the first dispute. ASTM E29-22 applies only when the specification states the absolute or the rounding method (ASTM International, 2022). For petroleum products and other homogeneous products, ISO 4259-2:2026, which replaced the 2017 edition on 9 June 2026, sets how to decide conformance when supplier and receiver results conflict (EVS, 2026).

How do you check a customer specification record is complete?

You check a customer specification record is complete by running six checks against each row of the log, and fixing any failure before the next order under that specification. The table below decides whether a record can be relied on for release and what to do when it cannot.

The check that most often fails is the fourth: a product can meet its own release limits on every lot and still miss a tighter customer limit. Run it on the last several lots each time a revision arrives.

Run the full set of customer specification checks at three points: when a new specification or revision arrives, before the first order under it, and after any change to your own release specification, raw material or test method. A change on your side can break a record that passed the day before. Record the date of each check run and who ran it in the log, so an auditor or a new account owner can see that the record was current when each lot shipped.

Who should own customer specification records when a rep leaves?

The company, not the sales representative, should own customer specification records, with one named role, usually quality or technical service, accountable for the log and the account representative responsible for routing new documents into it. Records kept in a personal inbox or laptop leave with the person.

Set the ownership rules before anyone leaves. Store every specification, review record and customer confirmation in the shared customer record. Name the log owner and a deputy. Make the account representative's handover list every open review, every revision requested but not received, and every agreed deviation, with the documents attached. A sales handover document for when a technical rep leaves can carry this list so the next person starts from the record, not from memory.

In Lubinpla, customer specifications and review records can be kept as customer documents by document type, and the Dataroom view shows the TDS and CoA sent to the same customer; there is no revision date field, so the revision goes in the file name or a note. Whatever system you use, check after each handover that the new owner can find the current revision of every specification for that customer.