An international EPR partner has 40 companies to onboard in Czechia. Its own system already holds their company details and contact information. A larger online retailer has a different problem. Its warehouse and sales systems hold thousands of dispatch records, but someone still has to prepare an export each quarter. Both teams can use an agreed API connection to send the records they already hold to the Kodo Portal and see what needs attention.
An API lets two systems exchange information directly. Kodo offers tailored integrations on request. We agree which records your system sends, what it can read back and how your team will handle exceptions. You can start with company onboarding or recurring reporting data and expand the connection when the workflow is ready.
Onboard a group of clients from your own system
A partner can send a batch of companies with the client ID from its own system, the legal name, country, VAT or registration number, and contact details. A preview can flag potential duplicates, conflicts or incomplete entries before the partner confirms the import. We agree how company IDs are matched so that a later update reaches the existing record.
The same connection can send registry extracts, signed mandates and other agreed documents to the relevant company. Your system can then ask what is still missing for each client and use that answer to guide the person who can resolve it.
Here is how three fictional companies might look after the same onboarding batch.
| Company | What the integration could return | What happens next |
|---|---|---|
| Northbay Home | The registered address is missing. | The partner completes the address in its system and sends the update. |
| Fieldline Retail | The company details are complete. The signed mandate is still outstanding. | The producer signs it. The partner sends the file to the same company record. |
| Aldergate Supply | The agreed fields and files are in place. Kodo review is pending. | Kodo checks the case and confirms the scope and price separately. |
The partner can work from its own system and see the same agreed case information in the Kodo Portal. We can also include messages and updates linked to a specific company, so a question about a mandate stays with the right case. Client invitations are handled as a separate step in the agreed workflow. See how partners work in the Kodo Portal.
The demo shows the partner’s client list, an EKO-KOM registration draft and the client’s quarterly reporting screen.
Kodo Partner Portal demo showing the client list, EKO-KOM registration and quarterly packaging reports
Send reporting data directly from a larger client’s systems
For a larger producer or retailer, we can connect the systems that already hold the reporting evidence. An e-commerce platform might provide orders and product IDs. A warehouse system might provide actual dispatches and destinations. An ERP or product catalogue might provide packaging components, materials and unit weights. The connection can bring the agreed records together without someone rebuilding the same spreadsheet each quarter.
Imagine an online retailer sends its Czech dispatch records every week. For one product, it sends the number of units shipped and the packaging reference recorded by the warehouse. The packaging catalogue has a weight for the retail box, but the shipping carton weight is missing. The retailer’s team can see which packaging reference needs evidence and send the supplier specification against that record. Kodo can then review the weight against the shipments it affects.
The retailer can use its own connection to send records and documents automatically. The producer confirms the source figures, and Kodo handles review and reporting within the agreed service. This gives both teams a chance to resolve questions during the quarter, when the people who know the shipments and packaging are easier to reach. Read how Kodo uses client records in Czech packaging reporting.
See what is ready and who acts next
A successful transfer tells your team that Kodo received the agreed data or file. The case status can then tell you whether a required field is missing, a file is outstanding, or Kodo has the information it needs for review. The response can also show the next action and who owns it.
For onboarding, the case can show separately when the documents are ready for review, when Kodo has confirmed the price, and when EKO-KOM has accepted the registration. For reporting, we agree how to identify the period, handle revised records and show the result of Kodo’s review. The technical documentation illustrates how an integration can return missing details, outstanding documents and the next action. Read the Kodo Partner API documentation.
Start with one workflow and sample records
Tell us which system holds your data, how many companies or records you expect to send, and what your team needs to see back. We will agree the fields, documents, access and update frequency with your technical team. We can then test a small batch or a sample reporting period, including a missing field and a revised record, before enabling the agreed workflow.
If you coordinate several producers, start with the partner workspace and its walkthroughs. If your own sales or warehouse systems hold the reporting data, tell us where those records are created and how you share them today. Explore the Kodo partner programme · Discuss an integration with Kodo.