When a product page refers to a sustainability attribute or Climate Pledge Friendly (CPF), one certificate should not be treated as proof for every product in a catalogue. Build one review record that connects the supplier’s certified scope, shipment or batch evidence, the live SKU, and the exact wording used on the page. Mark which conclusions are supported by documents and which still require confirmation from the certification body or platform.
Scope evidence and transaction evidence answer different questions
Scope Certificate (SC): This normally identifies the certified entity’s approved product categories, activities, and covered facilities under the applicable standard. It answers, “What is this entity certified or approved to handle?” It does not by itself prove that every shipment or every listed product is certified.
Transaction Certificate (TC): This is issued by the relevant certification body under the applicable scheme’s rules for identified certified goods or transactions. It commonly records the products, parties, quantities or weights, and shipment details. GOTS and Textile Exchange materials distinguish an SC from a TC for specific goods; whether a TC is required, who requests it, and which fields apply must be checked against the current standard and certification-body procedure.
SCs, TCs, purchase orders, invoices, shipping records, and product specifications should support one another. They are not interchangeable. A TC also does not, by itself, prove a complete chain of custody, brand authorization, or approval of a particular page claim by Amazon.
Build a product-level evidence map
For each live SKU, retain at least: SKU or ASIN, product name and version, material composition, manufacturer or supplier, applicable scheme, SC reference and status, TC reference or other batch record, purchasing and shipping evidence, and the exact sustainability wording used on the page.
Check four links: product name and model; material and composition; supplier, facility, and certified scope; and batch, quantity, date, invoice, and shipment records. Recheck the evidence when a product version, material, manufacturing site, or supplier changes. Do not silently carry an older record into a new SKU or shipment.
Common mismatches and wording limits
Typical mismatches include a certificate covering a different material or model, a supplier name that does not match the shipping party, a TC whose product or quantity cannot be reconciled to the order, or wording that expands evidence for one batch or scope into a claim about an entire product line.
Use language that stays inside the documents, such as “the supplier record identifies this SKU as…” or “this point requires confirmation from the platform or certification body.” Do not turn a standard name into a government-approval statement, use generic “recycled” or “organic” wording as a substitute for a named scheme, or merge platform eligibility, third-party certification, and product-law compliance. Check Amazon’s current program page or account requirements for the applicable CPF path.
A review order before submission or renewal
First identify the target market, program path, and exact claim on the page. Then obtain the current SC, applicable TC or batch record, and product specification from the supplier. Map the SKU, material, supplier, quantity, and dates. Check certificate status, issuing body, and authenticity, and record the date of each check. Put unsupported points in a confirmation list before changing the page.
The purpose of this ledger is to make the relationship between product, documents, and wording reviewable. It is not an Amazon decision, a certification result, or a promise of eligibility or approval.
Source basis reviewed: GOTS explanations of Scope and Transaction Certificates; Textile Exchange public materials on GRS/RCS transaction evidence and supply-chain traceability; and Amazon’s public explanation of Climate Pledge Friendly qualification paths. Standards, certification procedures, and platform requirements can change, so confirm the current source before submission.
