---
title: The Promise and the Proof in Sustainability
description: Sourcing evidence describes the type, not your goods. How the Promise and the Proof work for recycled content and PPWR, and which systems hold what.
---

[Skip to content](https://support.syncforce.com/knowledge/the-promise-and-the-proof-in-sustainability#main-content)

[![Syncforce\_logo\_tagline](https://support.syncforce.com/hs-fs/hubfs/Syncforce_logo_tagline.webp?width=480&height=72&name=Syncforce_logo_tagline.webp)](https://www.syncforce.com/)

Open main navigation

Close main navigation

 Hello. How can we help you?

- There are no suggestions because the search field is empty.

1. [Home](https://support.syncforce.com/knowledge?hsLang=en)
2. [Industry & Regulatory Knowledge](https://support.syncforce.com/knowledge/industry-regulatory-knowledge?hsLang=en)
3. [Packaging & PPWR](https://support.syncforce.com/knowledge/industry-regulatory-knowledge?hsLang=en#packaging-ppwr)

# The Promise and the Proof in Sustainability

## How sustainability data works from sourcing to goods receipt, and why evidence means two different things.

### The problem this article solves

Almost every week we see the same confusion in packaging and sustainability projects. Someone asks for the evidence behind a recycled content claim, and gets a lab report. The report is real, the supplier is reliable, and the number is correct. But the report describes a sample that was tested months ago, not the material that arrived on your site last week.

Both documents are called evidence. They answer different questions, they are collected at different moments, they live in different systems, and only one of them says anything about the goods you actually received.

We separate them as **the Promise** and **the Proof**.

### The two layers

|  | The Promise | The Proof |
| --- | --- | --- |
| **When** | Sourcing, before goods receipt | Goods receipt and beyond |
| **About** | The type of material or component | The batch you actually received |
| **Answers** | What will this component be? | What did we actually get? |
| **Granularity** | Per article or per specification | Per batch or per delivery |
| **Typical evidence** | Lab report on an earlier or similar sample, supplier certificate | Certificate of Analysis for this batch, incoming inspection, transaction certificate |
| **Who owns it** | Sourcing, technical packaging, product data | Quality assurance, goods receipt |

The Promise is what you commit to. The Proof is what you verify. You need both, and you cannot substitute one for the other.

### The Promise

The Promise is built during sourcing, before any goods arrive. It has four parts.

#### 1. Specification Requirement

What you demand. For example: this bottle must contain at least 30 percent post consumer recycled content, and the certification must be valid for the plant that produces it.

This is your requirement, written by you. It is independent of any particular supplier, which is what allows you to compare offers and to re-source later without losing the requirement.

#### 2. Supplier Value

What the supplier claims. For example: 32 percent post consumer recycled content.

This is their statement, stored as their statement. Keeping it separate from your requirement is what lets you see, automatically, when a supplier value no longer meets a requirement that has changed.

#### 3. Evidence, phase one

The documents behind the supplier value. A lab report, a material declaration, a certificate under a chain of custody scheme.

This is where most of the confusion starts, so it is worth being blunt about it. At sourcing, this evidence almost always describes an earlier or a similar sample, not your material. The supplier produces that component all year, for many customers. What you hold is evidence about the **type**, not about your goods.

That is not a weakness. Type evidence is the correct evidence for a promise. It only becomes a problem when someone treats it as proof of what was delivered.

#### 4. Declared Value

What you promise onward, to your own customers.

The declared value is derived from the specification requirement, the supplier value and the evidence behind it. It is the number that leaves your company. It appears on specification sheets, in customer data exchange, in tenders, and eventually in regulatory documentation.

### The Proof

The Proof starts at goods receipt, in your role as filler, converter or brand manufacturer. It is about the physical goods that arrived.

Three questions matter here, and none of them can be answered by the sourcing file.

**Does the evidence cover the plant that made these goods?** A supplier declaration or certificate is issued to a specific site. A supplier with four plants can ship you material from the plant that is not in scope.

**Does the production window fall inside the certificate validity?** A certificate that expired before your batch was produced does not cover your batch, even if it was valid when you placed the order.

**Is this delivery linked to the certified material?** For recycled content under a chain of custody scheme, this is the transaction certificate. Without it you have a certified supplier, not certified material.

On top of these, there is the verification you do yourself: incoming inspection, sample testing, and any check against the agreed specification.

The key difference is granularity. The Promise is per article. The Proof is per batch.

### Where this sits in the packaging data model

The Promise is built at the bottom of the structure and consolidated upward.

- **Packaging Component.** The physical item as procured. Here you hold the specification requirement, the supplier value and the sourcing evidence, per supplier.
- **Packaging Master.** The group of components sharing material composition, ink system and geometry. Compliance evidence that depends only on these properties belongs here, so it is collected once instead of once per artwork variant.
- **Packaging Unit and Packaging System.** The assembly. System level values such as total recycled content share, weight and empty space are calculated here, from the parts.
- **Sales Unit.** The finished good with its GTIN. This is what your customer buys, and therefore the level at which your promise is published.

![SU \_ Packaging Component to System](https://support.syncforce.com/hs-fs/hubfs/SU%20_%20Packaging%20Component%20to%20System.png?width=670&height=377&name=SU%20_%20Packaging%20Component%20to%20System.png)

That last step is the one that is often missing. Your trade customers, so distributors, wholesalers, retailers and private label partners, do not buy a component. They buy a sales unit. The declared values they receive have to be consolidated from the component level up to the sales unit, with every number traceable back to the specification requirement, the supplier value and the evidence that supports it.

The Proof does not consolidate in the same way. A batch result belongs to a delivery of one component. It is used to confirm or to challenge the promise, not to replace it.

### Which systems do what

| System | Role | What it holds |
| --- | --- | --- |
| **PIM and PLM** | The Promise | Specification requirements, supplier values, sourcing evidence, declared values consolidated to packaging unit and sales unit, and the data published to customers |
| **LIMS** | The Proof | Sample registration, test methods, results against specification limits, Certificates of Analysis per batch |
| **QMS** | Around both | Document control, supplier approval, non site specific certificates, deviations and corrective actions |
| **ERP quality module** | The Proof at intake | Inspection lots at goods receipt, release or block decisions, quality certificates linked to the delivery |
| **Chain of custody platform** | The Proof of origin | Transaction certificates, mass balance accounting for certified material |

Note what this table shows. The Promise and the Proof live in different systems, owned by different departments, with different update cycles. That is not wrong, and consolidating everything into one system is not the answer. What is missing in most companies is the link between them: a declared value that can be traced to the evidence that supports it, and a batch result that can be matched back to the declared value it is supposed to confirm.

### Common mistakes

**Treating a sourcing lab report as proof of delivered goods.** It describes the type. Say so in the way you label and store it.

**Storing the supplier value as if it were your own requirement.** When your requirement changes, you then have no way to find the components that no longer meet it.

**Collecting evidence per artwork variant.** If the evidence depends on material, ink system and geometry only, it belongs on the Packaging Master. Collecting it per component multiplies the work by the number of decor variants, which can be hundreds.

**Publishing a declared value with no traceable basis.** If a customer or an auditor asks where a number comes from, the answer has to be a path, not a person.

**Asking for proof at audit time rather than at order time.** Certificate validity, plant scope and transaction certificates are cheap to request with the order and expensive to reconstruct a year later.

### Summary

The Promise is what you commit to, built at sourcing, per article, supported by evidence about the type. The Proof is what you verify, starting at goods receipt, per batch, supported by evidence about your goods.

Regulations such as PPWR raise the bar on both. Recycled content in particular now needs a chain of custody that holds up, which means the Proof layer has to be designed rather than improvised.

Promise first, then proof. Keep them separate, keep them linked, and make sure every number you publish can be traced back to both.

- [Industry & Regulatory Knowledge](https://support.syncforce.com/knowledge/industry-regulatory-knowledge?hsLang=en#main-content)

    - [Product Portfolio](https://support.syncforce.com/knowledge/industry-regulatory-knowledge?hsLang=en#product-portfolio)
    - [Packaging & PPWR](https://support.syncforce.com/knowledge/industry-regulatory-knowledge?hsLang=en#packaging-ppwr)
    - [GS1 & GDSN](https://support.syncforce.com/knowledge/industry-regulatory-knowledge?hsLang=en#gs1-gdsn)
    - [Food & Label Information](https://support.syncforce.com/knowledge/industry-regulatory-knowledge?hsLang=en#food-label-information)
    - [EPR & Sustainability Data](https://support.syncforce.com/knowledge/industry-regulatory-knowledge?hsLang=en#epr-sustainability-data)
    - [Product Identification & GTIN](https://support.syncforce.com/knowledge/industry-regulatory-knowledge?hsLang=en#product-identification-gtin)
    - [PIM & Data Architecture](https://support.syncforce.com/knowledge/industry-regulatory-knowledge?hsLang=en#pim-data-architecture)
- [Product Data Management](https://support.syncforce.com/knowledge/product-data-management?hsLang=en#main-content)

    - [Packaging Data Management](https://support.syncforce.com/knowledge/product-data-management?hsLang=en#packaging-data-management)
    - [Product data imports](https://support.syncforce.com/knowledge/product-data-management?hsLang=en#product-data-imports)
    - [PDM setup and config](https://support.syncforce.com/knowledge/product-data-management?hsLang=en#pdm-setup-and-config)
- [Digital Asset Management](https://support.syncforce.com/knowledge/digital-asset-management?hsLang=en#main-content)

    - [FileConvert](https://support.syncforce.com/knowledge/digital-asset-management?hsLang=en#fileconvert)
- [Project Portfolio Management](https://support.syncforce.com/knowledge/project-portfolio-management?hsLang=en#main-content)

    - [Team & Planning](https://support.syncforce.com/knowledge/project-portfolio-management?hsLang=en#team-planning)
    - [Proofing & Approval](https://support.syncforce.com/knowledge/project-portfolio-management?hsLang=en#proofing-approval)
    - [Budget & Spend Management](https://support.syncforce.com/knowledge/project-portfolio-management?hsLang=en#budget-spend-management)
    - [Resource Management](https://support.syncforce.com/knowledge/project-portfolio-management?hsLang=en#resource-management)
    - [To Do (task & actions)](https://support.syncforce.com/knowledge/project-portfolio-management?hsLang=en#to-do-task-actions)
    - [Project definition](https://support.syncforce.com/knowledge/project-portfolio-management?hsLang=en#project-definition)
- [Product Catalog](https://support.syncforce.com/knowledge/product-catalog?hsLang=en)
- [Media Library](https://support.syncforce.com/knowledge/media-library?hsLang=en)
- [Product Data Syndication](https://support.syncforce.com/knowledge/product-data-syndication?hsLang=en#main-content)

    - [GS1-GDSN](https://support.syncforce.com/knowledge/product-data-syndication?hsLang=en#gs1-gdsn)
    - [DataPorts](https://support.syncforce.com/knowledge/product-data-syndication?hsLang=en#dataports)
    - [PS in Foodservice](https://support.syncforce.com/knowledge/product-data-syndication?hsLang=en#ps-in-foodservice)
    - [REST API](https://support.syncforce.com/knowledge/product-data-syndication?hsLang=en#rest-api)
- [Document Automation](https://support.syncforce.com/knowledge/document-automation?hsLang=en)
- [Exports & reports](https://support.syncforce.com/knowledge/exports-reports?hsLang=en)
- [Business Network Management](https://support.syncforce.com/knowledge/business-network-management?hsLang=en#main-content)

    - [Single Sign-On](https://support.syncforce.com/knowledge/business-network-management?hsLang=en#single-sign-on)
- [Services & Support](https://support.syncforce.com/knowledge/services-support?hsLang=en)
- [Partner Support](https://support.syncforce.com/knowledge/partner-support?hsLang=en)
- [General setup](https://support.syncforce.com/knowledge/general-setup?hsLang=en)
- [Campaign management](https://support.syncforce.com/knowledge/campaign-management?hsLang=en)
- [General](https://support.syncforce.com/knowledge/general?hsLang=en)

[![Chill listening crop-3](https://support.syncforce.com/hs-fs/hubfs/SyncForce_plus_1024-2.png?width=105&height=24&name=SyncForce_plus_1024-2.png "Chill listening crop-3")](https://www.syncforce.com/)

Copyright © 2026, SyncForce