For: brand owners, suppliers, and compliance teams maintaining Amazon ASIN records, third-party files, or environmental claims.

A listing claim should answer four questions: which product does it describe, which file supports it, which party is responsible, and where does the wording stop? This guide provides a product-level record for finding mismatches before a file is uploaded or a listing is changed. It does not promise platform acceptance, a Climate Pledge Friendly badge, sales performance, or a certification outcome.

1. Fix the ASIN scope first

Record the ASIN, model or variation, packaging version, marketplace, target market, brand owner, manufacturer, and importer or responsible economic operator. Then describe the relevant materials, formulation, function, dimensions, and components. If a file covers only a model, batch, package, or component, keep that limitation in the record; do not extend it to a brand or all SKUs.

Separate legal or market-access requirements, platform documentation requirements, and a buyer’s private standard. Their scope, evidence format, and decision-maker may differ. A supplier certificate does not automatically satisfy another market or platform requirement.

2. Keep a claim–evidence–party record

Create one row for each customer-facing sentence and retain:

  • Exact wording: the title, bullets, description, image text, and structured attributes.
  • Claim subject: the whole product, a material, packaging, a process, or a company-level practice.
  • Evidence: certificates, test reports, technical files, supplier declarations, purchasing or batch records, including version, date, and issuer.
  • Coverage: model, variation, batch, market, material, and validity limits; mark unknown fields as open items.
  • Responsible parties: the relationship between the brand, manufacturer, importer, certificate holder, and signatory.

Trace each sentence back to its file, then trace the file back to the current ASIN. Mark a row as aligned only when the product, party, scope, and version correspond. Having a certificate is not, by itself, an alignment conclusion.

3. Separate platform records from third-party certification

Amazon’s public Climate Pledge Friendly guidance describes a program that works with third-party certifications to highlight sustainability features of individual products. It also calls for clear and accurate advertising information, appropriate substantiation for environmental claims, and limits use of the CPF mark to eligible products rather than generic brand creative. Actual eligibility, submission paths, and display should be checked in the current Seller Central or Vendor Central account and the certifier’s documents.

Record separately whether the third-party file is valid and covers the product, whether Amazon lists the certification or path, whether a submission was made, and whether the badge is actually displayed. Do not turn “submitted” or “self-assessed as eligible” into “approved,” and do not treat a package or component file as proof for the whole product.

4. Six document checks

  1. Do names, addresses, and authorisations match the current sales arrangement?
  2. Does the model, ASIN, variation, BOM, or material scope cover the product shown?
  3. Do the method, standard version, key parameters, and sample description support the wording?
  4. Are issue date, validity, report version, and revisions traceable?
  5. Are supplier files connected to purchase, batch, delivery, or material records rather than stored as isolated attachments?
  6. Does the listing use broad words such as “all,” “zero,” “non-toxic,” “eco-friendly,” or “sustainable” beyond what the evidence supports?

Test reports, certificates, and supply-chain records answer different questions; file count does not prove completeness. For environmental claims, state the material, percentage, lifecycle boundary, or comparison object where the evidence supports it, and retain the method and data. If those limits are unknown, keep the item as an internal open question instead of publishing it as a customer-facing claim.

5. Human review before a listing change

  1. Read the current ASIN title, bullets, description, image text, and attributes and copy the exact wording under review.
  2. Check each sentence against the product, party, scope, date, and method in the file; remove or narrow anything that does not match.
  3. Confirm that voluntary programs, platform labels, and legal duties are not presented as the same thing.
  4. Save the file version, source link, review date, open items, and owner without overwriting historical records.
  5. Ask a reviewer familiar with the target market to perform a second customer-facing read before any platform action.

Sources and limits

This reference draws on Amazon’s Climate Pledge Friendly Creative Guidelines and the U.S. FTC environmental marketing guidance. Platform interfaces, certification lists, market rules, and document requirements can change; verify them against the applicable official page and current account records. 绿色方舟（深圳）认证有限公司 can help organise product–file–listing records but does not replace Amazon, a certifier, a laboratory, or a regulator in making a decision.