Two frameworks, two questions
Wooden kitchenware crossing the Atlantic meets two food-contact frameworks that ask different questions of the same spoon. The United States asks whether the article is clean and whether the finish sits within its food-contact framework. Germany, whose framework EU buyers often borrow as a benchmark, approaches food contact through a stricter regime and, in practice, through test reports. Neither is difficult for a well-run wooden utensil program. They reward different paperwork, and buyers who understand the difference early build one file that serves both markets.
The FDA side in one paragraph
For the United States, the expectation is that wood food-contact articles are clean, and that finishes fall within the food-contact framework gathered in the 21 CFR 174-186 range. In practice that means a documented finish system, usually mineral oil or a food-contact blend, plus the production hygiene that keeps the article clean to the carton. The paperwork is largely your own file: the spec sheet naming the finish, the documentation behind it and the QC record. Our note on FDA expectations walks that file item by item.
The LFGB side in one paragraph
The German LFGB framework is the stricter food-contact regime that EU buyers commonly request evidence against, often well beyond Germany's borders, because it has become a shorthand for careful food-contact work across Europe. For a wooden utensil program the practical expression is test reports: where reports are held, they are named and confirmed per program, and where they are not, the buyer and the desk agree on what evidence the program will carry instead. The desk never presents a report it has not seen, and buyers treat any report as a per-program fact to verify rather than a standing certificate.
What the European framework rewards is the same discipline the American side rewards: a boring, documented, oil-based finish on a clean, sound article. The difference is that the European file tends to include laboratory paper, and the scope of that paper is a decision to make with your compliance adviser before sampling, not after the cartons ship.
Side by side
| Dimension | FDA, United States | LFGB, Germany and EU requests |
|---|---|---|
| Central question | Is the article clean; is the finish within the framework | Does evidence show the finished article suits food contact |
| Typical evidence | Spec sheet, finish documentation, QC record | Test reports where held, confirmed per program |
| Finish standard in practice | Food-contact oil named on the spec sheet | Same oil discipline, plus laboratory paper on request |
| Who confirms the position | The buyer's compliance adviser | The buyer's compliance adviser |
| Planning principle | Build the file before entry | Agree report scope before sampling |
Selling into both markets
Brands that ship to the United States and Europe do not maintain two products; they maintain one product and one file with two tabs. The finish system is identical, because a documented oil finish serves both regimes. The declaration facts at US entry come from the same species and origin information the European paperwork references. The only genuinely per-market decision is the evidence package: which reports, if any, the European side will see. That is decided once with your adviser and then repeated per program. Plan to the stricter of the two and the other comes free.
Timing matters as much as content. Report scope is agreed before sampling, because the answer shapes what the workshop finishes and how it documents the run. A scope agreed after bulk production is not a scope; it is an autopsy.
Wholesale buyers increasingly hand you their requirements in writing during onboarding, and the asks differ by market in exactly this way. Our wholesale page describes how those requests flow into a program.
What to request from the workshop
The request list is short, and it should be written. First, the finish system named on the spec sheet, identical for both markets. Second, any test reports held against the finish system or the finished article, supplied as documents rather than summaries, with dates and scope visible. Third, the QC record for the order, since both frameworks lean on the article being clean. Where a report does not exist, say so plainly in the program file and let the buyer's adviser position around the gap. A missing report discovered early is a plan; the same report discovered late is a problem.
What paperwork cannot fix
Neither framework forgives a product that behaves badly in the kitchen. A film finish that chips, a surface that splinters after a few washes, or care instructions nobody follows will generate returns and reviews no report can offset. The physical quality work, sanding through successively finer grits, moisture control before packing, food-oil coverage checks, is the layer the paperwork sits on. Our quality control page describes that layer, and the sanding detail is expanded in its own note.
Reading a report when you get one
Buyers who receive LFGB-style reports for the first time tend to over-read or under-read them. Over-reading: treating a report on one finish batch as a lifetime certificate for the program. Under-reading: filing it without checking that the tested article, the finish system and the dates correspond to your order. The correct read sits between: a report is evidence about the system and batch it names, it is confirmed per program, and its scope is a question for your adviser. Ask the desk to line the report up against the spec sheet and the answer is usually visible on one page.
When a US-only program meets an LFGB request
It happens more than buyers expect: a program planned for the United States meets a European marketplace, a buyer with EU distribution, or a retailer whose vendor forms borrow the German framework as their standard. The program does not need rebuilding. The finish system already satisfies the oil discipline both sides respect; what changes is the evidence tab. This is precisely why the file is built with tabs rather than as a single market document, and why the desk asks for destination markets even on programs that swear they are domestic only.
The reverse crossing is friendlier: a program built to the European evidence habit lands in the United States with its paperwork already done and its declaration facts in hand. When in doubt, build to the stricter side. Storage space for documents is the only thing it costs.
What to send the desk
Send both destination markets and the program timeline. The desk will structure the file with per-market tabs, list which reports are realistically available for the finish system, and flag what belongs with your adviser. Start a quote, and read the testing ladder itself in our testing options note.