Operating notes / Operating model

EUDR for tyre importers: the operating model behind the paperwork

A practical model for connecting the importing entity, tyre classification, manufacturer evidence and shipment review before an EUDR decision.

Begin with a product flow, not a folder

A tyre importer may have a supplier declaration, several spreadsheets of production plots and a customs invoice. Those records answer different questions. The operating model must explain how they relate to the same goods.

Start with one representative import flow: one importing entity, a defined tyre family, a manufacturer, a manufacturing period or batch, and a shipment or purchasing record. Treat this as a test of the process before extending it to the entire range.

Resolve scope and role first

The current Annex I includes ex 4011, new pneumatic tyres of rubber. Assess the actual product and natural-rubber content. The September 2026 Annex I amendment removed other rubber entries and narrowed 4012 to tyre treads. A general label such as “rubber goods” is too broad for a scope decision.

Identify who places the relevant product on the EU market. The December 2025 amendment distinguishes operators, downstream operators and traders. Buying already-placed goods inside the EU and directly importing goods from a non-EU manufacturer are not interchangeable operating situations. Document the contractual and physical flow before assigning obligations.

Build five connected records

  1. Entity and role record: importing legal entity, responsible people, product classification and the basis for the role assessment.
  2. Product record: SKU family, specification, manufacturer and relevant material composition.
  3. Input and origin record: the manufacturer’s link from production output to natural-rubber inputs and their upstream evidence.
  4. Movement record: purchasing, shipment and batch references that identify the assessed goods.
  5. Review record: evidence considered, unresolved issues, mitigation, conclusion and approval.

The identifiers connecting these records matter more than whether they live in a spreadsheet or a specialist platform. A file named “supplier-compliant.pdf” does not establish which batch it supports.

A working gate for each relationship

Choose one representative purchasing or import flow before rolling out the process across the catalogue. Record the legal entity, actual products, classification basis, relevant Hevea brasiliensis rubber and role/date assumptions. Direct imports should not inherit a downstream customer’s workflow without a role check.

GateRecord to retrieveWhat it does not prove alone
Goods → outputInvoice / packing list reconciled to production batchNatural-rubber origin
Output → relevant inputAllocation or consumption records; carry-over explanationProduction legality or deforestation-free origin
Input → sourcing setProcessor dispatch and sourcing registerCoverage of a different input lot
Sourcing set → plotsAttributable mapping and production periodThe operator’s risk conclusion

A material specification may identify a blend without identifying the relevant input lots. A commercial SKU may repeat while those lots change. Request the manufacturer’s actual allocation method rather than imposing an identifier the factory does not use.

Fictional operating example / not a customer case study

SH-EX41 resolves to output B-A17. Plot set PS-07 exists. The missing route is B-A17 → input lots NR-11/NR-12 → sourcing set SS-07 → PS-07. Operations requests allocation records; procurement secures technical-owner access; the designated operator reviewer assesses the explanation and remaining gaps.

Separate work completion from a decision

Received, geometry checked, relationship reviewed and decision approved are distinct events. An inconclusive reply does not close the evidence issue because the supplier replied on time. Define closure criteria and escalation for each material blocker.

For the next container, check batch, production period, input supplier, processor, sourcing set, origin file and known concerns. Identical supplier and SKU names do not establish unchanged material. A reusable supplier identity record and a batch-specific allocation serve different purposes.

Confirm scope, date and DDS responsibilities first

The 2026 scope guide distinguishes ex 4011 new tyres, the narrowed tyre-tread entry and deleted rubber entries. The newly added-product date does not give existing new-tyre products a blanket 2027 delay.

Amended Articles 2, 4, 5 and 38 distinguish actor duties and the conditions for eligible micro/small deferral. Operators generally undertake due diligence and submit a DDS, subject to the specific primary-operator provisions. Downstream operators and traders have different information/record duties; “every actor files a DDS” is inaccurate.

Article 6 requires an EU-established authorised representative and a written mandate. Dubai-established ENCODE INFO - FZCO does not become that representative through a support agreement. MarketPass by Encode helps operate the process; the operator retains regulatory responsibility and its final decision.

Inspect the 12-page illustrative report to see how the route, inventory, blockers and action plan fit together before selecting a recurring model.

Start with the evidence you have

Know what is ready.
Know what is missing.

A focused diagnostic before you commit to a recurring operating model.

Assess your EUDR readiness