FOR INTERNATIONAL EPR PARTNERS

Your clients, a clear Czech EPR workflow.

Keep your client relationship and international coordination. Kodo can take the agreed local role in Czechia, with a shared process for onboarding, documents, packaging data and questions.

A defined role for each producer · A shared view of progress · No repeated email chains

A LOOK INSIDE THE PORTAL

See the partner view in action.

This silent walkthrough has on-screen captions. It shows how a partner can work with several Czech EPR clients from one account.

Partner portal walkthrough · captions in English · sound not required

THE PRODUCER VIEW

A simple place for each client to provide what is needed.

The client workspace keeps company details, requests and documents together. The producer can provide its source records while the partner follows progress.

Client portal walkthrough · captions in English · sound not required

ONE PROCESS, DISTINCT RESPONSIBILITIES

The handover stays clear.

01

Your team

Manages the wider client relationship and coordinates the international programme. You can add clients, follow their progress and raise questions with Kodo.

02

Kodo in Czechia

Reviews each producer's Czech situation, agrees the local scope, handles the authorised-representative work where appointed and manages the relevant EKO-KOM process.

03

Each producer

Confirms its company details and supplies accurate packaging and Czech sales records. Each appointment and applicable agreement is handled for that producer separately.

BUILT FOR MORE THAN ONE CLIENT

A useful workspace for the work between teams.

Client overview

See the clients linked to your partner account and open each client's current details.

Individual onboarding

Add a client, choose its portal language and send an invitation when the contact is ready.

Documents and questions

View client-submitted information and files; send client-specific notes to Kodo without changing the producer's records.

Bulk onboarding by CSV

Send a structured client list through the partner workspace. Kodo reviews it and arranges the import with you.

An agreed API connection

If volumes justify it, we can define an API exchange for agreed client and reporting data. Scope, security and validation are designed together; it is not an open self-service API.

A separate client workspace

Each producer has its own secure place to provide forms, packaging information and supporting documents.

HOW WE WOULD START

Start with a workable division of tasks.

01

Agree roles and data

We map who speaks to the producer, which data your team collects and which checks Kodo must complete locally.

02

Set up the first producers

Create clients individually or send a CSV for an agreed bulk import. Each producer is reviewed separately.

03

Appoint and onboard

Where representation is needed, the producer appoints Kodo in writing and the applicable EKO-KOM agreement is completed for that producer.

04

Review and report

The producer provides source figures; Kodo reviews the Czech packaging data, resolves questions and handles agreed reporting and correspondence.

Technology supports the process; it does not replace the checks.

Portal access or an API connection does not itself appoint a representative, register a producer or validate the source data. We agree the commercial scope and responsibilities before onboarding starts.

LET'S DEFINE A PRACTICAL WORKFLOW

Tell us how you currently support Czech clients.

A short outline of client volume, registration steps and available data is enough to start. We can then suggest a sensible pilot and the right level of portal or API integration.

Technology stack

We choose technology to fit the goal of each project

We are not tied to a single vendor. For each project, we select suitable AI models, automation and infrastructure, then connect them into one practical solution.

AI, automation and infrastructure

  • GoogleGoogle
  • ChatGPTChatGPT
  • ClaudeClaude
  • DeepSeekDeepSeek
  • LM StudioLM Studio
  • GitHubGitHub
  • n8nn8n
  • ObsidianObsidian
  • VercelVercel
  • CloudflareCloudflare
  • HetznerHetzner
  • MetaMeta

Hardware and AI servers

  • NVIDIANVIDIA
  • AMDAMD
  • ASUSASUS
  • LenovoLenovo
  • HPHP