Automated or assisted
- Imports
- Normalisation
- Mapping suggestions
- Gap detection
- Reminders
- Draft reports
Platform
One managed workflow for EPR for packaging, batteries, EEE/WEEE and textiles
Bring sales data, product-stream information, documents, deadlines and country-specific work into one coordinated process.
One account across your markets
You work in a single client account. The number of countries in that account follows the contract, not a separate login per market.
-
Company data once
Establishment, legal identity and packaging model are entered once and reused across the markets in your scope.
-
Countries in the same account
Markets, services and filing status sit together. You do not rebuild a process for each country.
-
Scope follows the contract
Available services depend on the contracted scope and on each country’s operational status. A subscription does not include every market or every service by default.
Sales and EPR product data
Source data lands in the same account so specialists can review one structured set, not a folder of parallel files.
-
Excel and CSV
Import sales and packaging files into the account for mapping and review.
-
Ecommerce and ERP connections
Direct shop and ERP integrations are planned. They are not available in this release.
Coming later -
Products and SKUs
Keep a catalogue of products and SKUs that can be reused across markets.
-
Components, materials and weights
Describe packaging components once, then map them to national categories during review.
-
Missing-data highlights
Gaps such as unmapped SKUs or missing weights are flagged before a pack is prepared.
AI-assisted data mapping
AI structures records and may propose a preliminary view. It does not change your legal status, approve a declaration or submit a filing.
-
Normalisation
Imported values are cleaned into a consistent working format.
-
Duplicate detection
Repeated SKUs or overlapping rows are highlighted for a specialist to resolve.
-
Suggested mappings
Category mappings are proposed with an explanation a reviewer can inspect.
-
Missing data
Gaps that limit a suggestion are listed with the proposal.
-
Sources and confidence
Each suggestion keeps the source value, suggested value, confidence and rule version.
-
No automatic decision
AI does not finalise an obligation and does not file. A specialist reviews the result first.
Specialist review
People confirm the working conclusion. The same person does not prepare and approve a sensitive declaration alone.
-
Internal review
An internal case manager prepares the pack. A separate reviewer checks the data and the proposed conclusion.
-
Client clarifications
If source data is incomplete or ambiguous, the client is asked to clarify before the pack moves on.
-
Country partner where required
A country partner is assigned only where the contracted service needs local execution. That assignment is not an authorised-representative appointment.
-
Client approval where required
The client approves the pack when the process requires it. Approval can sit with different roles, not only an internal agent.
-
Four-eyes principle
Sensitive declarations keep prepared-by, reviewed-by, approved-by and submitted-by records, each with a timestamp.
Country coordination
EPR Connect coordinates the following, where included in the contracted service scope.
-
Registrations
Producer-register and scheme onboarding steps for markets in scope.
-
Contracts and mandates
Contractual documents and mandates needed for the agreed work.
-
Reporting
Preparation of country-specific reports from the reviewed data set.
-
Filings
Submission or coordinated submission after the required approvals.
-
Rectificatives
Corrections are versioned. Closed declarations are not silently overwritten.
-
Renewals
The same account carries the next reporting period and renewal work.
Documents and audit trail
Declarations and documents receive versions or rectificatives. They are not overwritten in place.
-
Source documents
Imports, contracts and evidence stay attached to the period they belong to.
-
Data version
Each pack is bound to the data and rule version used to prepare it.
-
Prepared by
The person who assembled the pack is recorded.
-
Reviewed by
The person who performed the independent review is recorded.
-
Proof of submission
A filing keeps evidence that it was sent or coordinated.
-
Acceptance status
Submitted is not the same as accepted by the authority or scheme.
-
History and rectificatives
Later corrections create a new version or a rectificative, with a full audit trail.
Ongoing compliance workflow
The client journey keeps every stage distinct, from assessment and contract to declaration and filing evidence.
Available workflow
-
1
Initial assessment
-
2
Proposal and contract
-
3
Dossier validated
-
4
Packaging data uploaded
-
5
Specialist review
-
6
Declaration approved
-
7
Filed and evidence saved
Submitted does not automatically mean accepted.
Automated vs reviewed
Automation may propose. Confirmation, approval and filing stay with people.
Specialist or client decision
- Obligation assessment
- Data approval
- Declaration approval
- Authorised representative appointment
- Filing instruction
- Correction approval