GRS Scope Certificate vs Transaction Certificate: Which One Proves the Recycled Content?

Buyers ask for "the GRS certificate" as if it were one thing, and the ambiguity costs them money. Two documents carry the same logo and the same standard name, but they answer different questions, they are issued at different moments, they are held by different parties, and only one of them covers the goods on a specific purchase order. Asking for the wrong one produces a file that looks complete and fails the first time a retailer or an enforcement authority reads it.

This page separates the two. It sets out what each document is scope of, which fields have to reconcile between them, how long each stays valid, what happens when they disagree, and the order in which a buyer should request them across enquiry, sampling and shipment. It is written for the person who has to decide whether a recycled content claim can go on a product, a listing or a tender response.

What Is a Scope Certificate Actually Scope Of?

A scope certificate is issued to a site after an audit. It says that the site has been assessed against the standard, that its processes for handling certified input have been found acceptable, and that it is permitted to trade in named product categories under the standard. It names the legal entity, the address, the certification body, the standard and its version, the certificate number, the issue date and the expiry date, and it lists the product categories and the process steps the site is allowed to perform.

What it does not do is talk about goods. There is no quantity on it, no buyer, no shipment, no percentage and no commercial invoice. It is a permission to operate inside the standard. A buyer who files a scope certificate and believes it proves that a shipment was recycled has filed the wrong artefact, and the gap will be found the moment somebody asks which document covers the specific purchase order.

The version number on the scope certificate matters more than buyers expect. Standards are revised, and a certificate issued against an earlier version may not answer the question a current customer is asking. Record the version next to the number, and re-read the version when a claim wording changes.

What Does a Transaction Certificate Move Down the Chain?

A transaction certificate is issued for one transaction: a named seller sold a named quantity of a named product, containing a stated certified fraction, to a named buyer, on or around a stated date. It carries the certificate number, the issuing body, both parties, the product description, the quantity, the claimed percentage, the shipment or invoice references, and the date range. It is the document that carries a claim from one party in the chain to the next.

It is also the document that expires in practice, even where it has no printed expiry. A transaction certificate is a record of an event, so it stays true forever as a record, but it only supports a claim for the goods it names. Buy another lot from the same mill and you need another certificate. Sell part of that lot onward and the onward sale needs its own certificate, issued by you, against the one you received.

Why Can a Valid Transaction Certificate Still Fail an Audit?

Because the certificate only certifies what was declared to the issuing body, and the declaration is made by the seller. The certificate can be genuine, correctly issued, and still describe goods that were not the goods shipped. Four failure modes account for most of it. The first is quantity mismatch: the certificate covers a larger lot than the one delivered, and the remainder is sold to a buyer with no claim. The second is product mismatch: the description on the certificate is a generic yarn or fabric category, and the finished bag contains more than that one input.

The third is date inversion: the certificate is dated after the goods were shipped, or the input was received before the seller held a valid scope certificate. The fourth is percentage rounding: the certificate states a percentage that is higher than the fraction the inputs can support once coatings, linings and trims are counted. None of these are forgeries. All of them are findings.

Which Fields Have to Reconcile Between the Two Documents?

Reconciliation is a mechanical exercise and it should be done as one. Put the scope certificate and the transaction certificate side by side and walk seven fields in a fixed order: the issuing body, the standard and version, the certificate numbers, the legal entity names, the product category, the process steps, and the dates. Each field is a comparison against something you already hold — the purchase order, the commercial invoice, the packing list, the transport document.

The field that fails most often is the product category. A scope certificate lists categories in the language of the standard, and a transaction certificate describes goods in the language of commerce. Where the two cannot be mapped without a leap, ask the seller to state the mapping in writing before the goods ship. A one-line email that says which scope category the transaction certificate draws on is worth more than any folder of certificates.

1. Issuing body

Named on both documents, and searchable in its own register

2. Standard and version

Same standard, same version, on both documents

3. Certificate numbers

Scope number recorded against the transaction certificate

4. Legal entities

Seller on the transaction certificate is the site on the scope certificate

5. Product category

Transaction product falls inside a listed scope category

6. Process steps

The step performed is inside the audited process list

7. Dates

Scope certificate valid on the transaction date; transaction dated with the shipment

Who Can Issue Each Document, and Who Cannot?

A scope certificate is issued by a certification body accredited to certify against the standard, after an on-site audit. It cannot be issued by the site itself, by a trading intermediary, or by a laboratory. A transaction certificate is issued by the seller, or by the seller through the certification body, once the seller holds a valid scope certificate covering the product and the process step. A party with no scope certificate cannot issue a transaction certificate, and a transaction certificate issued by an uncertified party is not a certificate at all.

This is why the question to ask at enquiry stage is not "do you have the certificate" but "which certification body issued your scope certificate, and what is the number". The answer tells you whether the chain can be closed at all. Where the party you are buying bags from has no scope certificate of its own, it can still buy certified fabric and receive a transaction certificate for it, but it cannot issue one to you; you receive the fabric certificate and you build your claim on it, with your own purchase records bridging the gap.

What Does a Scope Certificate Not Cover?

Three things buyers routinely assume are covered, and none of them are. Substances: a recycled input standard does not test the article for restricted substances, and a certificate under it says nothing about the presence of any particular chemical. A separate restricted-substance declaration or a test report to the relevant standard is a different document with a different owner. Social compliance: an audit for a materials standard is not a labour audit, and the two are conducted by different bodies against different criteria.

Performance: a recycled input standard says nothing about tensile strength, abrasion resistance, colour fastness or seam behaviour. Those are engineering questions and they are answered by test reports to ISO or ASTM methods, not by a chain-of-custody document. A file that contains certificates and no test reports is a compliance file, not a specification file, and a bag can pass the first and fail the second.

How Long Does Each Document Stay Valid?

A scope certificate carries an expiry date, usually tied to an audit cycle, and the site has to be re-audited before it lapses. A transaction certificate has no expiry as a record, but it is only usable for the goods it names. The practical discipline is therefore different: the scope certificate needs a calendar with a renewal lead time, and the transaction certificate needs an index that ties each one to an invoice, a packing list and a production lot.

Ask for the expiry date of every scope certificate in the chain, not only the one you hold. A transaction certificate issued by a seller whose scope certificate expired the following week is still a valid record, but it tells you the seller was outside the standard when the next lot was sold, and that is a finding on the next lot, not on this one.

How Do You Check a Certificate Against the Issuer Register?

Most certification bodies maintain a public or customer-facing register searchable by certificate number. The check takes a few minutes and it is the single highest-value verification step available to a buyer: it distinguishes a genuine certificate from a genuine-looking one, and it shows the current status — valid, expired, suspended or withdrawn — which a paper copy never shows. Record the date you checked and what the register said, because a status can change between the check and the shipment.

Where a register is not public, ask the issuing body directly, in writing, with the certificate number. A legitimate certificate holder has no reason to object, and the objection itself is information. Where the check shows a status other than valid, stop the claim rather than the shipment: the goods can usually still be sold, but not with the recycled content statement attached to them.

What Should Be Requested at Enquiry, Sampling and Shipment?

Three requests, at three gates, each small enough that nobody objects. At enquiry: the scope certificate number of the fabric source, the issuing body, and the standard version, plus a statement of whether the party quoting can issue a transaction certificate. At sampling: a copy of the current scope certificate for each site that will touch certified input, and a sample transaction certificate from a recent lot of the same fabric so the product description can be reviewed before the bulk order.

At shipment: the transaction certificate for the specific lot, tied to the commercial invoice and the packing list, with the quantity reconciled against the delivered quantity. Where the delivered quantity is smaller than the quantity on the certificate, ask for a split record or a fresh certificate for the balance. That one discipline — quantity matching per lot — prevents most downstream findings.

What Happens When the Two Documents Disagree?

Disagreements are common and most of them are clerical: a product description in commercial language that does not obviously map to the standard category, a quantity in a different unit, a date a few days either side of the shipment. Resolve them in writing, at the time, with the certification body copied where the mapping is in doubt. A resolved mismatch recorded on the day is evidence of a controlled process; the same mismatch found eighteen months later reads as concealment.

Where the disagreement is substantive — the quantity on the certificate cannot support the quantity shipped, or the percentage cannot support the claim once non-certified components are counted — the remedy is to reduce the claim, not to find another certificate. Print a lower number, or print no number, and keep the sale. A claim that has been reduced once is defensible; a claim that has been defended with a second document rarely is.

Frequently Asked Questions

People Also Ask