A Rainforest Alliance-related claim cannot be supported by a generic supplier certificate alone. Review the participating organization, farm or supply-chain activity, applicable standard, crop or product scope, traceability records, license status, and the exact wording proposed for the product page. This reference explains an evidence structure; it does not state that any product is certified or will pass a platform review.

Boundary first: Rainforest Alliance certification documents address the program’s sustainability, supply-chain, traceability, and claim evidence. Marketplace policies, import requirements, product-safety laws, and other label programs must be checked separately.

1. Confirm the applicable program and scope

Current Rainforest Alliance materials include the Sustainable Agriculture Standard and its Supply Chain Requirements. The Regenerative Agriculture Standard has its own applicable documents. The correct document set depends on the certificate holder’s program, scope, crops, sites, and supply-chain activities; it cannot be inferred from a product name or a general sustainability phrase.

Create one scope record for each relevant line: organization or site, role, crop or product, locations, certificate or endorsement reference, applicable standard version, and the precise page claim under consideration. A brand or seller should not turn a supplier’s certification scope into a certification claim for its own company or every SKU.

2. Build the supply-chain evidence record

The supply-chain certification process starts with registration and submission of a certification scope. Depending on the risk assessment, an organization may follow an audit route or a low-risk endorsement route. The evidence should explain the organization’s activities, sites, crops or products, supply-chain role, and relationship to the applicable requirements.

Traceability is a separate evidence line. Organize purchases and sales, volumes, lot or product identifiers, suppliers and customers, processing or conversion information, and the supporting invoices, orders, transport records, and inventory records. The permitted traceability model and required control point depend on the current Supply Chain Requirements, Traceability Annex, and platform instructions; do not apply one generic “certificate plus batch sheet” model to every product.

Retain the license or license agreement, certificate or endorsement, scope changes, audit or remote-review evidence, corrective-action records, and materials relevant to trademark or label use. Legal entity, site, product scope, and dates should agree across the files. If they do not, mark the item for review instead of filling the gap by inference.

3. Keep product-page wording within the evidence

State the object and scope of the claim. A page may identify the relevant crop, product, or supply-chain record and point to the certificate holder, scope, and supporting documents. It should not turn “a supplier participates in the program” into “all products from this brand are certified,” or turn one transaction record into an organization-wide or SKU-wide claim.

“Certified,” “endorsed,” “licensed to trade,” and “permitted to use a trademark” are different facts. The public process materials describe registration, scope submission, risk assessment, and an audit or endorsement path before the relevant certificate, endorsement, or license services are available. Product-page wording still needs to be checked against the actual scope, transaction record, and trademark policy.

Do not add unsupported claims such as guaranteed platform approval, customs release, automatic delisting, fixed fines, fixed review periods, or universal market coverage. Rainforest Alliance documents do not replace import law, marketplace rules, product-safety requirements, or the evidence for another certification program.

4. Pre-publication evidence questions

  • Object: Does the page refer to a farm, supply-chain organization, supplier, brand, product, or lot?
  • Scope: Do the crop, product, site, activity, and certificate holder match the page object?
  • Version: Are the current applicable standard, supply-chain, traceability, and trademark documents being used?
  • Transactions: Can purchases, sales, volumes, lots, and conversions be connected to the product or claim?
  • Wording: Has “documentation exists” been overstated as “certified,” or one scope expanded to every SKU?
  • External rules: Have marketplace, import, labeling, and other regulatory requirements been checked as separate matters?

Sources: Current Rainforest Alliance Certification Standard; Certification and Auditing Rules for Supply Chain v1.1; Certification Process and Timelines; Traceability Annex v1.4; Supply Chain Certification Guide for Companies.