What to request from a non-EU tyre manufacturer
A practical manufacturer request pack: output batches, rubber input allocation, processor links, plot coverage, supporting records and change controls.
Test an ability, not a promise
A manufacturer may answer “yes” when asked whether it is preparing for EUDR. That response does not reveal whether it can support your particular product flow. The more useful test is whether it can produce an example of the evidence relationship you need.
Start with one representative tyre family and production period. Explain the importing entity and the records you already have. Ask for a named evidence owner rather than routing every question through the sales contact.
Five questions that expose the operating dependencies
- Who owns the upstream evidence? Identify the team or person who can obtain information from natural-rubber suppliers and processors.
- How are inputs linked to output? Ask how a manufacturing batch or controlled production period relates to natural-rubber lots or sourcing sets.
- What origin information exists? Request a sample showing identifiers, production locations and relevant periods, subject to agreed confidentiality arrangements.
- How are changes controlled? Ask what happens when the processor, sourcing pool or material input changes.
- How are exceptions escalated? Identify who can investigate an unexplained or incomplete record.
Request a small, representative evidence pack
The sample should demonstrate a relationship between product output, relevant material input and origin information. It need not be a full disclosure of every commercial record during an initial conversation. Agree the purpose and access arrangements before sensitive files are shared.
Ask the manufacturer to explain the sample in its own terms. This often reveals whether the records are part of a working process or were assembled once to answer a customer questionnaire.
A seven-part manufacturer request pack
| Ask for | Useful response | Failure it exposes |
|---|---|---|
| Identity and technical owner | Factory/legal name, production site and upstream contact | Distributor sales contact has no access to origin records |
| Output boundary | SKU/family, batch/period and commercial cross-reference | Catalogue response does not cover selected output |
| Relevant material | Specification and Hevea rubber identification | Blend composition is asserted without current applicability |
| Output-to-input link | Allocation/consumption method, contributing lots and carry-over | Natural rubber cannot be related to the selected batch |
| Processor / sourcing set | Lot references reconciled to suppliers and sourcing registers | Factory country mistaken for production origin |
| Plots and support | Identifiers, version, period, origin mapping and relevant production evidence | Coordinates exist without coverage |
| Changes and exceptions | Notice triggers, corrections and escalation owner | A one-time pack silently reused for new sourcing |
These are operating requests, not a database structure prescribed by law. Article 9 establishes required information; the template helps obtain it for a defined product flow.
Copyable first request
Subject: Evidence relationship for [family / batch / period]
We are reviewing [one purchasing/import flow] for [EU importing legal entity]. Please nominate the production/origin-evidence owner.
Please provide or explain the records connecting our goods to the output batch, the relevant natural-rubber input lots, processor/supplier and sourcing-set references, production plots and periods, and supporting production evidence.
For each file identify its source, version, covered product/lot/period and limits. Explain mixing, candidate input sets and stock carry-over. State absent records explicitly.
If confidentiality restricts access, propose arrangements that let our responsible reviewer obtain sufficient information. Identify sourcing-change and corrected-file notices. This request seeks evidence relationships rather than a generic certificate.
Three responses need different next actions
Records exist; access is restricted: resolve purpose, recipients, confidentiality and retrieval. Do not assume access is impossible, or that restrictions remove information requirements.
Records are partial: request the exact missing relationship or period. Preserve the initial response so limitations remain attributable.
Records were never retained: assess whether future collection and controls can be established. Reformatting or software cannot reconstruct unknown origin.
A factory supplies a policy, plot list and tyre specification. The next request is the output-to-input allocation and input-to-sourcing-set map for B-A17. Asking for “more EUDR documents” would not explain what is missing.
Close the issue through review
Track the request, reply, evidence version, unresolved point and closure rationale. “Supplier replied” is a task status; it is not an operator approval. Agree notice triggers for changed processor, origin set, allocation method, production period and relevant concerns.
Do not submit sensitive supplier records through the public enquiry form. Evidence sharing is a separate agreed step. The sample diagnostic report illustrates bounded requests and owner/action criteria without promising upstream cooperation.
Know what is ready.
Know what is missing.
A focused diagnostic before you commit to a recurring operating model.