Product database

Product Database

Central register of returnable packaging within the system – a comprehensive record of EAN codes, material specifications and product statuses.

Book an Appointment Find out more

The foundation of the entire system’s correctness

The product database forms the basis of the deposit-refund scheme, ensuring the consistency and accuracy of packaging data throughout all processes – from registration, through collection, to settlement.

Each package is defined and validated before being released for use, which reduces the risk of operational and financial errors and supports compliance with regulatory requirements. The interface, available in Polish and English, makes it easier for users from different organisations to work with the system.

Packaging labels

Technical and material specifications.
Data used by all modules.
Central product register.

Data validation

Automatic validation of EAN codes.
Verification of product parameters.
Check for uniqueness in the database.

Life-cycle management

Statuses: New, Published, Withdrawn.
Publishing and withdrawing products.
Change control at every stage.

Data entry

Form.
CSV import.
API integration with ERP systems.

Integrations

RVM systems – all suppliers.
Manufacturers’ ERP systems.

Change history

History of all modifications.
Information about the author of the changes.
Data available for audit purposes.

The process

How does it work?

Introduction of the packaging

The manufacturer adds packaging details via a form, CSV import or API integration with their own ERP system.
Data validation

The system checks the EAN code, material specifications and the uniqueness of the packaging against a central database.
Creating a product page

The package is assigned a ‘draft’ status, which allows data to be added and edited prior to publication.
Packaging publication

Once approved, the product is published and becomes available to all associated modules on the platform.
Updates, history and audit

Changes to the package leaflet are automatically made available across all processes. Each modification is recorded, along with details of the author and the scope of the changes.