A claim is the end of a process
Compostability is a tested, certified property of one specific product from one specific producer. It is never a property of bamboo as a material, and never a sentence a buyer can add to packaging by intent. That is why the buyer's journey to certified products starts with a structural question rather than a technical one: does the item you want already carry a certificate whose scope matches it, or does the certification need to be created? The two paths run differently, cost differently in time, and end at the same place: a document, held by the product and the certifier, that a public lookup can verify. The scheme-by-scheme detail sits in the certifications explainer; this note is the process around it.
Door one: source against existing certificates
The fast path is matching your program to items whose certificates already exist. The work is verification, and it is a lookup, not a conversation: obtain the certificate document from the workshop, read the scheme, the certificate number, the holder, the product scope and the validity dates, then check the reference on the scheme's public listing. The schemes a North American or European buyer meets are BPI certification, ASTM D6400 as the US standard specification, EN 13432 as the European standard, and the TUV OK Compost and OK Compost HOME schemes with their separate industrial and home scopes. Three mismatches recur in practice: the certificate covers a neighboring product line rather than the quoted item, the license was renewed under a different number, and the holder differs from the company sending the quote. Each is resolvable, and each is exactly the kind of thing to find during sourcing rather than after the print run.
Door two: scope a new certification with the workshop
When the item is new, or an existing certificate does not cover it, the second door is a certification path scoped with the workshop before bulk. The sequence is stable across schemes: choose the scheme by market, because the US and European systems are separate and a buyer serving both keeps two files; confirm with the workshop that the product as specified can be tested against the referenced standard; agree the scope, meaning the exact item configuration that will be tested; run the testing; and wait for the certificate to issue to the product and its producer. The timeline is set by the scheme and the testing laboratory, so it is scoped per program rather than guessed, and it sits on the program calendar in front of bulk production. The desk's role is scoping and sequencing: matching the claim to the right door, and keeping the testing path out of the production window's way.
The two paths, side by side
| Dimension | Existing certificate | New certification |
|---|---|---|
| Speed to a claim | Fastest; verify and quote | A testing path sits before bulk |
| Item freedom | Limited to items already certified | Any item the workshop can make and test |
| Scope check | Confirm the certificate covers the exact item | Scope follows the tested configuration |
| Who holds it | The product and certifier, at the producer | The same, once issued |
| Calendar impact | Minimal, verification only | Adds a phase before production |
| Fit | Stock programs, fixed launch dates | Novel items, claims the range lacks |
Verification is a lookup anyone can repeat
Every certification scheme maintains a public listing, which changes the character of trust in this category: a claim does not need a relationship to be checked, only a number. That is why the desk writes certificate references into quotations and program files, so an auditor, a municipal reviewer or a retailer's onboarding team can reproduce the check independently. It is also why verification is repeated at bulk, not just at quotation: renewals change numbers, scopes shift between product generations, and a reference that verified in spring should be confirmed again before the container books. A lookup takes minutes, and it is the difference between a claim you can defend and a claim you can only repeat.
Until the paper exists
Programs on the second door still ship, and the honest interim language is made of bamboo, with the certification question answered by the document when it arrives. What a program does not do in the interim is print a compostable claim without its referenced documents behind it, or lean on unqualified green phrasing that claim rules such as the FTC Green Guides exist to police. The interim wording is not a downgrade; it is a claim that matches the file, and packaging built around it converts to the certified wording with a print run rather than a rebrand. The claim rules are mapped on the compliance page, and the additive question that often rides along, PFAS documentation where programs require it, is covered in the PFAS note.
Working both doors at once
Larger disposable programs often run the two doors in parallel, SKU by SKU, and there is nothing inconsistent about it. The volume items, usually forks and spoons, source against existing references and carry the certified wording from the first print run. A novel item the range lacks, a distinctive plate diameter or a custom kit format, enters through the second door, ships with the interim made-of-bamboo wording, and converts to the certified wording when its testing path completes. The discipline that keeps this honest is per-SKU claim control: the packaging file tracks which wording each item is allowed to carry, so a certified line's claim is never accidentally extended to the item still in testing. Buyers who run this mixed mode get range breadth and claim integrity at the same time, which is the combination the category usually forces them to choose between.
Sequencing the path with the program calendar
The path decision belongs at the brief, because it is the one decision that restructures the calendar. A program on the first door runs verification alongside sampling and reaches bulk inside the ordinary reference windows; a program on the second door adds a phase in front of production, so the launch date is set by the testing path rather than by the 30 to 45 day production window. Neither path changes the order minimum; what changes is time, and testing and certification are quoted as program line items, never as fixed figures. The calendar mechanics sit on the MOQ and lead time page. When you know which claims your packaging must make, send the claims list and the desk returns the path, the item matches and the verification references in writing.