A product may involve separate material, packaging, supply-chain, or market claims. Having several certificates does not mean that every certificate supports every sentence on a product page. A more reliable review starts by defining each claim and then matching it to the product, responsible entity, scope, version, and target market actually covered by the evidence.

1. Separate certificates, regulatory files, and page claims

Certificates, test reports, supply-chain records, and regulatory files serve different purposes. A certificate may describe the status of a named entity, product, facility, process, or scope under a particular standard. A test report records a sample, method, test items, and results. Purchase, production, and transaction records document material or batch movement. Regulatory files describe requirements for a particular market. None of these document types automatically substitutes for another.

If a page says that a product contains recycled material, that a material is certified, or that packaging has a specific environmental attribute, define whether the claim concerns the product, a component, packaging, a material, an organisation, or a supply-chain process. The FTC Green Guides state that environmental marketing claims need appropriate substantiation and caution against broad, unqualified environmental-benefit claims. See the FTC Green Guides.

2. Align product, entity, scope, and market

Build a row-by-row evidence register. Each row should represent one SKU, model, formulation, or clearly defined product version and record:

  • Product identity: SKU, model, formulation, material composition, packaging version, and change history;
  • Responsible entity: certificate holder, manufacturer, importer, brand owner, or page-claim owner as shown in the relevant file;
  • Certificate scope: covered product category, facility, material, process, transaction, or supply-chain stage;
  • Target market: the country or region where the claim will appear and its relevant label, language, evidence, or channel requirements;
  • Page sentence: the exact wording proposed and the file that supports it.

Supplier files can be a starting point, but the file name alone does not establish applicability. Check the certificate number, named entity, scope, product or site description, issuing body, and current document status. If a point cannot be confirmed, keep it as an open verification item rather than presenting it as a conclusion.

3. Map each file to a specific claim

Use three columns: claim, evidence, and limits. The claim column states the fact the page intends to communicate. The evidence column identifies the source file, version, and relevant location. The limits column states what the file does not establish. For example, a material record may support the composition of a documented batch without supporting an environmental claim for the entire product or all packaging. An organisation-level management document does not automatically establish the same attribute for every SKU.

Environmental wording needs particular care. The FTC’s public summary explains that broad “green” or “eco-friendly” claims are difficult to substantiate; a general claim should be clearly and prominently qualified to a specific environmental benefit, with relevant trade-offs considered. See the FTC Environmental Claims Summary.

4. Review changes and language before release

Before saving a page, check that the images, model, material, packaging, labels, and copy refer to the same product version. Confirm that the Chinese and English versions describe the same claim object and limitations. Remove wording that turns “documented” or “subject to verification” into approval, guaranteed acceptance, or another outcome promise. If the product, supplier, material, process, packaging, or target market changes, reassess whether the original evidence still covers the current claim.

External wording should remain verifiable, qualified, and traceable. 绿色方舟（深圳）认证有限公司 can help organise a product, evidence-file, and page-sentence review, but applicability still depends on the product facts, document scope, and target-market requirements.

Pre-release checklist

  • Is the claim object clear: product, component, packaging, material, organisation, or process?
  • Do the entity, product identity, scope, and version in the file match the page?
  • Have the target market and page channel been reviewed separately rather than copied across markets?
  • Does every visible claim have a corresponding file and stated limitation?
  • Have unsupported outcomes, fixed timelines, and broad environmental conclusions been removed or marked for verification?