The documents a program should produce
Buyers rarely need more meetings; they need the right paper at the right moment. A well-run bamboo program generates a compact file, and the desk's job is to make sure each document exists before it is needed rather than after. The list below is what a standard program produces, in the order you meet it.
| Document | What it is | When you receive it |
|---|---|---|
| Spec sheet | Item, material system, dimensions, finish, packaging, per line | With the written quotation |
| Material declarations | Named finish and adhesive systems with workshop papers | With the quotation for durable lines |
| Certificate reference file | Compostability references verified on scheme lookups | Before production, for claim-bearing programs |
| Lacey Act data sheet | Species, country of harvest, quantity for the entry | Before first shipment, for your broker |
| Care cards | Program-specific care instructions for durable ware | Approved with packaging proofs |
| Inspection reports | Results against agreed checks and AQL levels, with photos | With the shipment papers |
The compliance page explains the claims half of this file in depth; this page is about delivery of the documents themselves.
Spec sheets and material declarations
The spec sheet is the contract of record for the object. It names the item, the material system, dimensions and tolerances, the finish where one applies, branding positions and the packaging build. Material declarations attach the workshop's own papers for finishes and adhesives, which is what turns a laminated panel from an assertion into a documented system. Retailers and marketplaces increasingly ask for exactly these two documents at onboarding; having them in the file from the first quotation means onboarding is a forwarding exercise, not a scramble.
Certificate references and Lacey Act data
Certificate reference files collect the compostability references for claim-bearing programs, each one verified on its scheme's public lookup before it enters the file, so an auditor or a municipal reviewer can reproduce the check. Lacey Act data support is quieter but just as practical: bamboo is a plant product, and formal US entries under HTSUS Chapter 44 require a declaration with species, country of harvest and quantity, filed by the importer of record through CBP's ABI system. The desk prepares those fields from the program file in the format brokers ask for; the broker confirms current APHIS requirements, because implementation details evolve. The Lacey Act guide and the US importing guide cover the entry basics.
Inspection reports, delivered
Inspection reports are produced against the checks and AQL levels agreed in your program, and they are returned together with the shipment papers, not on request afterward. Each report states what was checked, what was found, and whether the lot passed against the agreed limits, with photographs of representative items and any defects. Reading your first report with the desk line by line is part of onboarding, because a report you can interpret is the difference between evidence and wallpaper. The quality control page explains the checks behind the lines.
Keeping the file usable
A program file is only support if it can be searched in a crisis, so two habits keep it usable. Version everything: a spec sheet without a version and date is how a revised item silently ships against old paperwork, so every document carries both, and superseded versions are marked as such. Name documents by program and line, not by month, so a broker or a retailer's onboarding portal receives files that explain themselves. The same discipline powers the after-delivery process below: a claim is answered in hours when the lot reference opens a folder where everything is dated, and in weeks when it opens a memory. Buyers inheriting a program from a previous supplier can ask the desk to rebuild the file from the goods themselves, which starts with a spec reconstruction and a fresh golden sample, and costs far less than the disputes it prevents.
After delivery: when something is wrong
Issues after delivery are handled against the file, not against memory. The process is short: you report the issue with lot and carton references; the claim is compared against the golden sample, the spec sheet and the inspection report; and the outcome, replacement, credit or a corrective action at the workshop, is agreed in writing with a date. Because the golden sample and the reports exist for every program, most disputes resolve on the documents rather than on persistence. What the desk does not do is argue a good shipment into a bad one or the reverse; the file decides, which is exactly why the file is built that way.
Reorders, timed against your calendar
Reorders re-run against the program file, so they skip the discovery work: spec, golden sample, certificate references and packaging proofs all stand. What stays live is the calendar, because bulk production sits inside the typical 30 to 45 day reference window after sample confirmation and seasons do not move. Reorder quantities frequently differ from first orders, and because the file stands, only the quantity, the date and any artwork changes need writing. The desk tracks reorder dates per program and flags the ordering cut-off ahead of your season, which is most of the value of a desk relationship over time. The reorder planning guide covers the season patterns, and the MOQ and lead time page holds the reference ranges the calendar is built on.
Anything on this page can be requested before you are a customer: ask for the document list for your program type, and it comes back with the quotation. Send a brief, or write to the desk through the contact page.