Connect the records.
Make the next step clear.

01 / Establish fit

The readiness form captures your importing entity, products, source countries and current approach. An initial conversation clarifies whether the diagnostic is appropriate. We do not ask for confidential evidence through the public website.

02 / Agree the diagnostic

We identify one representative import flow, the relevant SKU families and up to two supplier chains. You nominate the internal owner and confirm access to the records needed for the review.

03 / Follow the evidence backwards

We start with the shipment or purchasing flow, then examine its relationship to the relevant product, material inputs, suppliers and production origin. The route depends on the goods and supply structure. For our natural-rubber and tyre workflow, this connects manufacturing batches, rubber inputs, processors and production plots. Each link is recorded as supported, unresolved or outside the agreed review.

This is not a requirement to disclose your whole supply chain on the first call. It is a method for deciding which evidence is needed and who can supply it.

04 / Make gaps actionable

A useful gap register names the missing information, affected flow, owner and next action. “Ask supplier for EUDR compliance” is too broad. “Confirm which input lots fed production batch B and provide the related origin mapping” is a request someone can answer.

05 / Review with management

The written report and readout distinguish what is supported from what remains uncertain. We recommend an operating model and explain what would need to be resolved before it could work.

06 / Operate the agreed routine

If you proceed, we agree recurring responsibilities, review gates, evidence-sharing arrangements and escalation rules. New suppliers, altered product composition and changed origin information are handled as changes to the record.

Where submission fits

Evidence collection and review come before the applicable due-diligence statement. We support preparation and the agreed hand-off into the EU Information System. MarketPass does not claim a live direct submission API integration. Article 6 requires an EU-established authorised representative and a written mandate. ENCODE INFO - FZCO is established in Dubai; operational support does not itself appoint MarketPass as that representative. The operator retains responsibility.

Submitting a statement is not a substitute for the underlying due diligence, nor is a reference number regulatory certification.