ENKodo in Practice

A shared Czech EPR workspace for international partners

Kodo has added a partner workspace for teams coordinating Czech packaging EPR across several clients, with individual onboarding, a route for CSV client lists and API integration by agreement.

P

Predrag Pavič

Author

Share:

International EPR work often involves more than one company and more than one team. An adviser may manage the wider client relationship, while a local representative handles the Czech requirements. When company details, packaging files and questions are scattered across email threads, even a straightforward onboarding can become difficult to follow.

We have added a Czech EPR partner workspace to make that handover clearer. It gives an international partner one place to follow its linked clients, while each producer has a separate space to provide its own information. The public page includes short, silent walkthroughs of both views.

One partner account, separate client work

A partner can add a client, choose the language used in the client portal and send an invitation when the contact is ready. The client can then provide company details, packaging information and supporting documents in its own workspace. Agreements and formal documents remain in English.

The partner can follow the clients linked to its account, see the relevant information they have supplied and leave notes for Kodo. A general message area is available for questions that concern the wider partnership. Client-specific questions belong with that client's record, so they do not get lost in a general conversation.

Access is organised by role. The partner's view is for coordination, not for silently changing the producer's submitted records. The producer remains responsible for confirming its own company and source data.

Partner Portal EPRPartner Portal

What if there are many clients?

Adding clients one by one may be sensible for a first pilot. For a larger group, the partner can send a structured CSV client list through the workspace. Kodo reviews the file and agrees the import process with the partner; uploading a list does not automatically register those producers or send invitations to them.

Where recurring volume makes manual exchange impractical, we can also assess an API connection for agreed client or reporting data. That requires a defined data format, permissions, validation and a test using the partner's real workflow. It is a scoped integration, not an open self-service API or a promise that every existing system can be connected immediately.

Client Portal EPRClient Portal

The local EPR work still happens for each producer

The portal helps teams exchange information, but it does not appoint a representative or complete an EKO-KOM registration by itself. We first check the producer's sales route and packaging obligations. Where Kodo is to act as Czech authorised representative, the appointment and applicable EKO-KOM process are handled separately for that producer under an agreed written arrangement.

The producer supplies accurate packaging and Czech sales records. Kodo reviews the Czech figures, resolves questions and handles the agreed reporting and correspondence. The international partner can keep the broader client relationship and coordinate the work across countries.

A practical way to start

If your team supports several companies selling into Czechia, we can begin with a small pilot: agree who collects which information, add the first producers and see whether individual onboarding, a reviewed CSV import or a tailored integration fits the volume. There is no need to design an API before the basic responsibilities are clear.

See the partner workspace and both video walkthroughs, or contact Kodo with a short outline of your clients and current process. We can then discuss a sensible division of the Czech work.

A plan or an idea?

Working on a specific project? Talk to us.

Whether you are entering the Czech market or improving your local marketing, website, automation or AI setup, tell us what you need. We will suggest a practical next step.

Contact Kodo

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