Management and tracking system for containers with a refundable deposit and a method for managing and tracking of containers with a refundable deposit

Abstract

The object of the invention is a method for managing and tracking of containers (1) with a refundable deposit, wherein the method comprises the steps of: obtaining, by a local server (2), unique codes (3) assigned to individual containers (1), wherein the obtaining is based on receiving data from a distributor point (4), the data being indicative of the unique codes (3); activating, by the local server (2), each code (3) assigned to an individual container (1); receiving, by the local server (2), of codes (3) from a return point (5), the codes (3) being scanned from containers (1) by a return point scanning device (6) for scanning electronically readable codes (3); verifying for each code (3) received from the return point (5) whether the code (3) is activated; if the code (3) is activated, instructing the return point (5) to allow refunding of the refundable deposit of the container (1); and deactivating the code (3) of the container (1) by the local server (2). A management and tracking system for containers (1) with a refundable deposit comprises at least one local server (2) configured for implementing the described method.

Description

[0001] Management and tracking system for containers with a refundable deposit and a method for managing and tracking of containers with a refundable deposit

[0002] Field of the Invention

[0003] The invention relates to a system for managing containers with a refundable deposit and a method of handling such containers, in particular to ensure the proper return of the container and to prevent fraud in the payment of the refundable deposit.

[0004] Background of the Invention

[0005] In the current state of the art, Deposit Return Systems (DRS) are widely used as structured environmental management mechanisms in which consumers pay a small deposit when purchasing certain items, such as bottles or cans, wherein the deposit is refunded when the customer returns the empty container to a designated collection point. Many DRS use electronically readable identification codes on the returnable containers, wherein a remote server can authorize eligibility to return the container and pay the refundable deposit when the code is scanned at the collection point. Different types of codes can be used, wherein the codes can be unique for each container or the same for containers having the same characteristic (batch number, manufacturer, type of product, etc.).

[0006] Document W02020123660 A1 discloses a system and method for recycling validation of containers labelled with a unique code, wherein the codes are administered by a central server. Before placing the container into the collection bin, the user retrieves the code using a scanner of his mobile device which is in communication with the central server. The code status of the container can be valid or invalid, wherein the codes are also used to identify the collection bins, and the server uses an algorithm to authorize the correct assignment of the container code to the collection bin code. The main disadvantage of this system is that it does not solve the problem of paying the refundable deposit on the containers and preventing fraud. Similar system is described in document EP3903249 A1 , wherein the method further comprises a control check whether the location of the mobile device, used for scanning the code, is in the vicinity of the collection bin. A central server can approve the payment of the refund of the container if the container is genuine, i.e. if the code is scanned and processed by the central server for the first time. The disadvantage of such system is that it does not solve a problem of any fake new codes that can be easily sent to the central and approved for the refund.

[0007] Document WO202370195 A1 discloses a management system of returnable containers with unique codes, the system comprising servers managing information on containers that can be accessed by manufacturers, retailers, government institutions and users themselves, wherein the information include an amount of the refundable deposit, the number of life cycles of the container and addresses where the container can be returned. This document does not disclose any measure to effectively control the payments of the refundable deposit but rather a public monitoring system for tracking the life cycle of the containers.

[0008] The main disadvantage of the existing systems is that they do not sufficiently control all the requirements for the return of the container and / or the requirements for the deposit to be paid thus not preventing a fraudulent use of codes and unauthorized payments of the refundable deposits. In addition, the known management systems for handling the containers with the codes often use specialized and costly equipment at the collection point, e.g. reverse vending machines (RVM). In conclusion, there is no complex system that implements a reliable verification of each code to ensure that the refundable deposit is paid only if all the requirements of the DRS system for the refund are met.

[0009] Summary of the Invention

[0010] The above shortcomings are to some extent eliminated by a method for managing and tracking of containers with a refundable deposit, wherein the method comprises the steps of:

[0011] - obtaining, by a local server, unique codes assigned to individual containers, wherein the obtaining is based on receiving data from a distributor point, the data being indicative of the unique codes,

[0012] - activating, by the local server, each code assigned to an individual container if the code was obtained based on data received by the local server from a distributor point authorized to send data to the local server, - receiving, by the local server, of codes from a return point, the codes being scanned from containers by a return point scanning device for scanning electronically readable codes,

[0013] - verifying for each code received from the return point whether the code is activated,

[0014] - if the code is activated, instructing the return point to allow refunding of the refundable deposit of the container,

[0015] - deactivating the code of the container by the local server.

[0016] The main advantage of the method is that the containers are characterized by unique codes, wherein each code can be activated or deactivated, wherein the management and tracking of each container is based on this status of the code. The management of the code comprises a range of handling processes for the container, e.g. the return of the container, refundable deposit payment, the recycling or refilling of the container, etc. The tracking of the containers is based on monitoring of the numbers of the containers with activated and deactivated codes, the numbers of containers with paid refundable deposits, the number of potential fraud events etc. The local server or another authority responsible for handling the codes can therefore monitor the number of the containers available in the market (the containers with activated codes) or the number of the containers present in the warehouses, sent for recycling, refilling, landfilling, etc. (the containers with deactivated codes), the average lifespan of a container, the lifespan corresponding to the time between the code activation and deactivation etc.

[0017] The method can be performed by a management tracking system comprising a local server for managing the codes, wherein the local server communicates with a distributor point for placing the containers with unique codes to a market and with a return point for receiving the used containers.

[0018] A container is any type of receptable used for carrying alimentary or non-alimentary content, the container being assigned with a refundable deposit. In other words, the container is eligible to be returned at the return point in order to be recycled, reused or refilled, wherein the customer is paid a refundable deposit if all the requirements for reimbursement are met. Container refers specifically to a bottle or can, but it is not limited thereto, container may also be a crate, a box, a jar etc. Such containers may be made of various materials, e.g. plastic, glass, metal or mixed materials.

[0019] An electronically readable code may be a barcode, Data Matrix code, QR code, micro QR code, RFID tag, NFD tag or any other type of code that can be read by an optical or other scanning device. The electronically readable code may be applied to the individual container by printing, engraving, gluing, embossing, embedding in the material of the container, etc. The electronically readable code may be applied to any part of the container, preferably to the non-deformable part of the container which ensures that the code remains readable even if the container is crumpled. The electronically readable code may therefore be applied to the lid or the cap of the container, or to the bottom of the container.

[0020] The local server is the main component of the system, generally a computer server, that is responsible for managing of the electronically readable codes of the containers present on the local market, i.e. for storing the numeric codes or other digital representations of these electronically readable codes and additional information on these codes. The local server is responsible for receiving and storing information on the electronically readable codes, particularly information on the activated / deactivated status of the code, the status and the amount of the refundable deposit, and, optionally, about additional information on the container (material of the container, the reusability of the container, the number of cycles of use of the container etc.). The local market corresponds to a region where the management and tracking of containers with a refundable deposit is ensured by the local server. The local market can be a specific country, a specific area within the country, a group of countries, etc.

[0021] In particular cases, the status of the code can be indicated as other than only “activated” or “deactivated”, e.g. the code can be reusable and have a status of “ready for further use”. The status of the code can be indicated as “health-safety warning”. This status can be used for codes labelling containers which were found to contain health hazardous content, for example a beverage contaminated by bacteria etc. In some cases, the code can have multiple statuses, e.g. the code can be currently “deactivated” and simultaneously “ready for further use”, or “activated” and simultaneously “health-safety warning”.

[0022] The local server can be a part of a DRS (Deposit Refund System) of the local market, wherein the local server can be communicatively connected with a corresponding local DRS server of the local market, e.g. a specific country. The local DRS server is a standard server that manages the whole system of containers with the refundable deposit in the local market, the local DRS server being communicatively connected with a plurality of stakeholders of the DRS, e.g. with the national authorities, beverage producers, distributors, retailers, return points, recycling facilities etc. The local server and the local DRS server can be a single entity.

[0023] The distributor point can comprise a distributor point scanning device, and the return point can comprise a return point scanning device, wherein the scanning devices are configured to scan the electronically readable codes, wherein these scanning devices can be adapted to the type of the electronically readable code selected. The scanning device can be a device for optical reading of optical electronically readable codes. The scanning device may be a fixed device, e.g. a scanning camera, or a mobile device (handheld scanner, tablet, mobile phone), etc. The distributor point scanning device is a device used in the distributor point of the containers with corresponding electronically readable codes, wherein the distributor point is any entity or facility by which the containers are placed on the market or by which the containers are distributed within the local market. The distributor point is a facility, e.g. a logistics center that distributes containers within the local market for transport to individual points of sale. The distributor point may be a specific retailer of the containers (grocery store, supermarket etc.). The distributor can distribute the containers within one or more local markets.

[0024] In the first step of the method, the local server obtains unique codes assigned to individual containers, wherein the obtaining is based on receiving data from the distributor point. The data sent to the local server are indicative of the unique codes assigned to the containers. I.e., the data can but do not have to comprise the codes themselves; the data preferably at least allow the local server to obtain the codes from another source, such as a database distinct from the distributor point. The data can be for example numeric codes or other digital representation of the electronically readable codes assigned to the containers, wherein the electronically readable codes can be scanned by the distributor point scanning device and subsequently transformed into these numeric codes or into another digital representation.

[0025] Obtaining the codes by the local server is based on receiving the data from the distributor point, wherein receiving the data from the distributor point can be direct, i.e. the local server can communicate directly with the distributor point. Receiving the data from the distributor point can be indirect, wherein the local server can communicate with the distributor point via another facility external to the local server, e.g. via a central authority. The external facility can only forward the data from the distributor point to the local server. The external facility can process the data from the distributor point and then send the processed data to the local server.

[0026] When the local server receives the data directly from the distributor point, obtaining the codes by the local server can be further based on a verification that the distributor point is authorized to send the data to the local server, wherein the verification that the distributor point is authorized can be performed in one or more steps. One-step verification means that only an authorized distributor point can establish a communication with the local server, i.e. receiving data from the distributor point automatically means that the distributor point is authorized to send the data or the codes to the local server.

[0027] Two-step verification means that any distributor point can establish a communication with the local server, whereupon the local server verifies, for example, a match of an identification data of the distributor point, with a set of identification data of authorized distributor points. If the identification data of the distributor point matches any of the identification data of authorized distributor points from the set of the authorized distributor points stored in the local server, the distributor point is authorized to send the codes, or the data indicative of the codes, to the local server. The step of authorization, i.e. “verifying that the distributor point is authorized to send the data indicative of the codes to the local server”, generally serves to ensure that only selected approved distributor points are allowed to communicate with the local server and cause the local server to activate the codes of the containers.

[0028] Analogous one-step or two-step verification can be performed when the local server receives the data indirectly from the distributor point via the external facility, wherein this verification can be performed by the external facility communicating with the distributor point. The local server can then receive the data indicative of the unique codes from the central authority, wherein the communication between the central authority and the local server is automatically regarded as a safe communication. In other words, the local server does not verify whether the central authority is authorized to send the data to the local server.

[0029] The data indicative of the codes can be sent to the local server or to the external facility from a control point of the distributor point, for example from a central computer of the distributor point. The data indicative of the codes can be obtained, by the central computer, from the electronically readably codes scanned by the distributor point scanning device being communicatively connected with the central computer. Preferably, the local server obtains the data indicative of the codes from the central computer of the distributor point. Preferably, the data indicative of the codes is transferred from the electronically readable codes by the distributor point scanning device after being scanned by the distributor point scanning device.

[0030] Obtaining the unique codes assigned to individual containers may comprise receiving data from the distributor point scanning device. Obtaining the unique codes from the distributor point can be performed using the distributor point scanning device, wherein the distributor point scanning device is used for scanning the electronically readable codes of the individual containers and subsequently converting or otherwise transforming the scanned electronically readable codes of the individual containers into unique codes of the individual containers. The unique codes of the individual containers may be in a form of numeric codes or any other digital records or representations, wherein these unique codes of the individual containers can then be sent to the local server or to the external facility. The codes can be sent to the local server or to the external facility directly from the distributor point scanning device, with the distributor point scanning device itself acting as the central computer of the distributor point and communicating with the local server. In this case, the verification process can be applied directly to the distributor point scanning device.

[0031] Obtaining the unique codes assigned to individual containers may comprise receiving data from the distributor point scanning device, wherein the distributor point scanning device is used for scanning an electronically readable code assigned to a package of containers, e.g. to a multipack or tray of containers, a pallet of containers, etc., and subsequently converting or otherwise transforming the scanned electronically readable code of the package into unique code of the package, wherein this unique code of the package can then be sent to the local server, wherein the scanned electronically readable code of the package and / or the unique code of the package obtained from the electronically readable code of the package carries information on the unique codes of the containers contained in the package. In this case, the local server obtains the unique codes assigned to individual containers indirectly, wherein the distributor point scanning device is used for scanning the electronically readable code of the package of the containers, rather than scanning the electronically readable codes of the individual containers themselves. The local server can obtain these data indicative of the codes from the central computer of the distributor point, or directly from the distributor point scanning device.

[0032] The step of activating, by the local server, each code assigned to the individual container, the code being received by the local server from the distributor point, means that the local server updates the status of the code in the database of the local server to “activated”. The digital representation of the electronically readable code can be stored in the database of the local server and comprise information about the status of the electronically readable code. The “activated” status of the code means that the electronically readable code can be scanned at the return point and the container labelled with this electronically readable code can be returned and / or refunded. The activation of the code can be done directly during receiving the data from the distributor point or from the external facility, i.e. the step of receiving of the data itself representing the activation of the codes. The step of activating the codes can comprise issuing an automatic instruction of the local server to issue an invoice for the containers assigned by activated codes. The invoice can be sent to any or multiple of the following: the beverage producer, the local DRS server, a production point of the containers with the codes, etc.

[0033] In other words, a code is activated if a container with this code (with its electronically readable representation) is already available on the market or sold to a customer etc., and the return points should thus be available to receive this container back and pay the refund. If a code is deactivated, the corresponding container is e.g., still at a warehouse somewhere and could not have been sold, or the code might not even have been applied to any container yet, or the container was already returned, etc. An attempt to get a refund for a deactivated code thus indicates an error, a fraud attempt, etc. The activated / deactivated status thus helps the method with making sure that a refund is paid only when it should be.

[0034] The step of receiving codes from the return point by the local server comprises the step of scanning codes from containers by the return point scanning device and subsequently sending the codes from the return point to the local server. The process of scanning of the electronically readable codes by the return point scanning device, wherein the scanning process involves transforming the scanned electronically readable codes into unique codes, and receiving the codes by the local server can be analogous to the process of obtaining the data from the distributor point and distributor point scanning device. The only difference can be that, at the return point, the electronically readable codes of individual containers can only be scanned directly from the individual containers and not from a package of containers.

[0035] The return point can comprise a control unit sending the codes to the local server, the control unit being communicatively connected with the return point scanning device. The codes can be sent to the local server directly from the return point scanning device, for example when the return point scanning device is a handheld scanner. The return point can comprise multiple return point scanning devices, wherein each of these return point scanning devices can be communicatively connected with the local server and / or with the control unit or any other component of the return point. One of these return point scanning devices can be a remote scanning device that is not located close to the other elements of the return point. The remote return point scanning device can be a smartphone of the user provided with an application and connection to the local server and / or connection to the other elements of the return point.

[0036] The step of verifying each code received from the return point to confirm if the code is activated means that the local server can, for example, check whether the code received from the return point matches to any record from a set of codes stored in the database of the local server. In other words, the step verifying for each code received from the return point can comprise verification whether the code exists. The local server can then also check the status of the code. If the code received from the return point matches one of the codes from the set of codes stored in the database of the local server, the local server may further check the status of the code in the database. The verification of the code can therefore comprise a verification of the presence of the received code in the database of the local server, and, if the received code is present in the database of the local server, a verification of the active status of that code in the database of the local server. The verification of the code can comprise a verification of the presence of the received code in a database of another facility external to the local server, for example in the database of the central authority that manages all the codes handled by one or more local servers.

[0037] If the electronically readable code scanned by the return point scanning device is verified as activated, e.g. if the digital record of the electronically readable code is stored in the database of the local server and the status of this code is activated, the return point is instructed to allow refunding of the refundable deposit of the container. The return point can also be instructed to allow receiving the container from which the activated electronically code was scanned by the return point scanning device. The container can be received in a collection receptacle of the return point, e.g. in a collection bin. In other words, the return point can enable the container handover into the collection bin only after the scanning and a successful verification that the code is activated. Alternatively, the container can be received first and directed to the collection bin, with the code being automatically scanned after the container has been received in the collection bin.

[0038] If the record of the electronically readable code scanned by the return point scanning device is existing and available to the local server, e.g. stored in the database of the local server or the central authority, but the status of this code is not activated, the return point can be instructed to disallow receiving the container from which the activated electronically code was scanned by the return point scanning device, and / or to disallow refunding of the refundable deposit of the container. Preferably, if the record of the electronically readable code scanned by the return point scanning device is available to the local server but the status of this code is “deactivated”, the return point is instructed to receive the container from which the activated electronically code was scanned by the return point scanning device but to disallow refunding of the refundable deposit of the container.

[0039] If the electronically readable code scanned by the return point scanning device is not verified as activated, i.e. if the digital record of the electronically readable code is not available or known to the local server and for example stored in the database of the local server or in the database of another facility external to the local server, the local server can generate an alert indicating an error, a fraud attempt etc. The alert can be sent to the return point and / or any other entity. The alert can be sent to the central authority, to the local DRS server or to any other component of the local DRS system.

[0040] The step of deactivating the code of the container by the local server, the code being received by the local server from the return point, means that the local server updates the status of the code in the database of the local server to “deactivated”. The digital representation of the electronically readable code stored in the database of the local server therefore comprises information about the status of the electronically readable code being “deactivated”. The “deactivated” status of the code means that the electronically readable code can be scanned at the return point, but that the container labelled with this electronically readable code cannot be returned and / or that the refundable deposit of this container cannot be paid. The “deactivated” status of the code can also mean that the electronically readable code can be scanned at the return point and the container labelled with this electronically readable code can be returned, but that the refundable deposit of this container cannot be paid.

[0041] The terms “activated” and “active” are used to describe the same status of the code, as well as the terms “deactivated” and “inactive”.

[0042] Preferably, if the code is activated, the method further comprises the step of instructing the return point to receive the container to which the activated code is assigned. This procedure is advantageous for receiving and subsequent handling of the containers at the return point, wherein only the containers that are approved for a handover at the particular return point can be stored at this return point and / or sent for recycling and / or for refilling. In other words, only those containers whose codes have been previously verified by the local server, can be handled by that return point. Preferably, if the code is activated, the method further or alternatively comprises a step of instructing the return point to send the container to a recycling facility. Preferably, if the code is activated, the method further or alternatively comprises a step of instructing the return point to send the container to a refilling facility.

[0043] In other words, if a specific code assigned to a specific container and received from a return point is activated, the local server can issue instructions (preferably to the return point, but possibly to another device / person / facility) for further manipulation with this specific container. The manipulation can especially include any or multiple of the following: receiving, recycling, cleaning, reusing, disposing other than recycling (e.g., landfilling, burning etc., if the container is not suitable for recycling). The return point can issue an instruction to print a confirmation of a successful return / refund process.

[0044] If, on the other hand, the code was not found to be activated (e.g., it is deactivated or does not exist at all), the method can alternatively or additionally include any or multiple of the following: issuing instructions for not receiving the container,

[0045] - issuing instructions for giving the container back to the person trying to return the container / to get the refund,

[0046] - issuing instructions for suspending the operation of the return point and / or the return point scanning device,

[0047] - issuing instructions for calling the staff of the return point,

[0048] - determining that an error occurred in some part of the method or of components implementing the method - in this way the method can serve as a diagnostic method for container-managing system or method and can be used to verify functionality and / or discover any faults,

[0049] - issuing reporting of an error to other components of the system (to the local DRS server, to the beverage producer, etc.).

[0050] If the code was found as not existing, the local server can determine a fraud by the user. This situation means that the user might have used a fake code and attempted to get a refund for a code of a container that is not eligible to be refunded. If the code was found as not existing, the return point can issue instructions for calling the staff of the return point.

[0051] If the code was found as existing but deactivated, the local server can determine an error from within the management system. If the code scanned at the return point was found existing but deactivated, it might indicate that the container was placed on the local market (e.g. by the beverage producer or by the distributor point) without informing the local server of doing so, wherein this code had not been activated by the local server. The presence of existing but deactivated code on the market might be caused by a mistake during sending and activation of the code. The presence of existing but deactivated code on the market might be also caused by a fraud attempt of the beverage producer or the distributor point. The local server can report this error to the beverage producer / distributor point and / or send a fine to the beverage producer / distributor point for not declaring a real number of containers placed on the local market.

[0052] After scanning the code at the return point, irrespective of whether the code was found activated or deactivated, the return point can issue instructions for contacting a medical facility. These instructions can be issued in case that the code has been, e.g. by the producer, further labelled by the status of “health-safety warning”. The beverage producer can assign this status to the codes present in the database of the central server and / or the database of the local server based on the date of the batch production with a health hazardous content, wherein the date of the batch production is matched with the date of applying the codes to the containers or the date of packing the containers into the palette. The advantage of this status is that the system can quickly check the number of containers with “health-safety warning” status, i.e. how many of these containers are still available at the market (activated codes) or how many are still at the warehouse (deactivated codes).

[0053] For any of the above step(s) of providing instructions, the method can further comprise a subsequent step of following the instructions, e.g., some other component / system / person can do, what the local server instructs it to do, as a part of the method.

[0054] Preferably, the step of obtaining, by the local server, unique codes assigned to individual containers, comprises the steps of:

[0055] - receiving, from the distributor point, a code assigned to a package of individual containers, and

[0056] - obtaining the unique codes assigned to individual containers, the unique codes assigned to individual containers being associated with the code assigned to the package of individual containers.

[0057] A package of individual containers can be any form of packaging comprising a defined number of containers, e.g. a cardboard multipack of any number of beverage containers, a crate of any number of containers, a tray of any number of containers etc. The number of containers in each package is optional and depends on the preferences of the manufacturer, retailer, etc. A package may also be a pallet comprising several multipacks of containers, where each container in the multipack, each multipack in the pallet and each pallet can be labelled with an electronically readable code to ensure the traceability of each level of the packaging hierarchy (container, multipack, pallet). In another system, the electronically readable code may be labelled to the pallet only, wherein said electronically readable code is associated with a number of codes assigned to multipacks and / or containers contained in the pallet. Preferably, the code assigned to the package of individual containers is scanned from the package by the distributor point scanning device.

[0058] Preferably, the step of deactivating the code of the container by the local server is followed by a step of:

[0059] - sending, by the local server, of the deactivated code for application to a new container.

[0060] The term “sending of the deactivated code” covers several alternatives to indicate that the code itself can be applied to and used to identify a new container. Sending of the deactivated code for application to a new container can therefore mean either the direct sending of this code from the local server to any entity or authority that is responsible for assigning and / or applying this code to a new container, e.g. to a central authority that manages all the codes handled by one or more local servers, or to the production point that is used to physically apply the electronically readable codes to the containers etc. Sending the deactivated code for the application to a new container may also comprise a process of simply updating the record of the deactivated code in the database of the local server, the updated information of the record informing that the deactivated code can be used again, or sending and updating this information in another external facility of the system, etc. During or after the deactivation of the code, several parts of the digital record of the code can be archived or deleted, for example the information on the beverage producer or the EAN code of the product contained in the original container. The status of the code can be updated to “ready for further use”. Deleting of several parts of the digital record of the code can be done for example in the database of the local server, in the database of the central authority, or in the database of another external facility.

[0061] Preferably, the method further comprises the step of:

[0062] - receiving data, by the local server, about reusability of the container,

[0063] - wherein the sending, by the local server, of the deactivated code for application to a new container occurs only if the container is non-reusable.

[0064] The advantage of this subsequent step is that the code associated with a single reusable container can remain associated with that single container throughout several life cycles of the container. A reusable container is any type of container that can be reused, e.g. directly reused or cleaned, then refilled and fitted with a new lid. Reusable container is typically a glass bottle, a rigid plastic container, a plastic bottle crate, a stainless-steel container, or any other container that can be used several times before being recycled or discarded. The local server can obtain information about the reusability of each container in many ways. The data on the reusability of each container may be obtained directly from the code assigned to the returned container, i.e. this information is part of the code of the container, or from the information associated with each code, wherein the information may be stored in the digital record of the code in the database of the local server, in a database of the external facility, in a database of the central authority storing information from one or more local servers, etc. The local server may receive the data on the reusability of each container directly when obtaining the code of the reusable container, or upon a special request for this information.

[0065] For example, a newly manufactured reusable glass bottle can be labelled by a new unique electronically readable code, wherein at the moment of the first return process, the glass bottle is received at the return point, the refundable deposit is paid, and the code is then deactivated by the local server. The glass bottle can be then forwarded to a cleaning facility or directly to the production point, where the bottle is refilled and fitted with a new cap. After refilling, the glass bottle can be sent to the distributor point where, after scanning the electronically readable code by the distributor point scanning device, the code can simply be again activated by the local server. In the case of reusable containers, the electronically readable code is preferably applied to an integral and irreplaceable part of the container, e.g. to the bottom or the side of the container.

[0066] Preferably, the method uses unique electronically readable codes that are randomized. Randomization of unique electronically readable codes helps to maintain anonymity of each container with respect to other containers produced in the same batch, with respect to the contents of the container, with respect to the manufacturer of the container, etc. Randomization means that preferably all digits of the code are randomized. Digits of the code may be only partially randomized, e.g. that a certain digit or a series of digits, e.g. the first or the last series of digits, or other specific series of digits, contains digits common to several containers with the same characteristic. Digit(s) common to several containers may represent a material from which the container is made, the contents of the container, information on the reusability of the container, etc.

[0067] Preferably, the method uses codes comprising a series of digits, wherein the first digits of the series comprise digits of an EAN code. The inclusion of the EAN code in the series of digits of the code helps to reduce the number of codes that should be applied to a single container, wherein the electronically readable code used to manage and track the container may also be used to identify the product stored in the container. The inclusion of the EAN code into the series of digits of the code might be combined with randomization, wherein the first series of digits of the code comprise digits of the EAN code and the remaining series of the of digits of the code comprise a randomized combination of digits. The above shortcomings are to some extent eliminated by the management and tracking system for containers with the refundable deposit, wherein the system comprises at least one local server configured for implementing the above-described method. The local server is generally a computer server comprising all necessary hardware and software components to ensure the implementation of method for managing and tracking of containers with the refundable deposit. The local server can comprise a database for storing the information on the electronically readable codes assigned to containers, particularly information on the activated / deactivated status of the code, the status and amount of the refundable deposit, and, optionally, about additional information on the container (material of the container, reusability of the container, number of cycles of use of the container, production point of the container, beverage producer, etc.).

[0068] Preferably, the management and tracking system further comprises at least one distributor point, the distributor point comprising a distributor point scanning device for scanning electronically readable codes, wherein each distributor point is communicatively connected with at least one local server. The local server can be communicatively connected with the distributor point directly or indirectly via another external facility, e.g. via the central authority.

[0069] Communicative connection is any type of connection ensuring transmission of information between the components of the management and tracking system. The communicative connection can be a physical wired connection or preferably a wireless connection suitable for remote communication between the parts of the system. This connection can be provided by WiFi, radio signal, optical communication etc. The term “communicative connection” here comprises all essential hardware and software components to ensure such connection.

[0070] Preferably, the management and tracking system further comprises a central server communicatively connected with the local server, the central server comprising a module of the central server for generating unique codes and a database of the central server for storing the information on the codes assigned to containers.

[0071] The central server is generally a computer server external to the local server, wherein the central server can be considered as a higher authority over the local server. The central server comprises the module for generating unique electronically readable codes and the database for storing the information on the electronically readable codes assigned to containers. The database may store the information on each electronically readable code, e.g. in the form of a numerical code or any other digital record, and the information on the code and the container labelled with that code. The information on the code and the container comprises especially the information on the status of the code (activated, deactivated) or statuses of the code (activated, deactivated and other), the status and amount of the refundable deposit, the material of the container and information on the reusability of the container, including a possible maximum number of uses of the container etc.

[0072] Preferably, the management and tracking system comprises a total of at least two local servers, each local server being communicatively connected with the central server. Each local server is configured, independently of the other local servers, to obtain codes assigned to containers and further to activate and deactivate the obtained codes assigned to containers. Each code can preferably be activated only by the local server by which the code was obtained and only the local server, by which the code was activated, can preferably instruct a return point to receive the container from which the activated code was scanned and / or instruct the return point to allow refunding of the refundable deposit of the container.

[0073] The system comprising two or more local servers, each local server being communicatively connected to the central server, is advantageous for managing and tracking containers in two or more different regions (local markets) but operated by a central server as a central authority. The central server stores and manages all the codes from a number or from all of the local servers in one place, whereby a single code cannot be assigned to two different containers, each of the different containers being handled by a different local server. Local servers can manage the codes in different regions of the same country, wherein the central server is a national central authority. Local servers can manage the codes in different countries, wherein the central server is an international central authority.

[0074] The local server can, independently on the other local servers, obtain codes and de / activate codes assigned to containers. Before activation, the codes can be obtained for example from one or more distributor point scanning devices, directly or indirectly via another device or facility, wherein each code can be obtained from one distributor point scanning device. The indirect acquisition of codes by the local server can be performed via a control system of the distributor, the control system gathering data from one or more distributor points (distributor point scanning devices). Before deactivation, the codes can be obtained from one or more return point scanning devices, directly or indirectly via another device or facility, wherein each code can be obtained from one return point and corresponding return point scanning device.

[0075] Each code can be activated only by the same local server by which it was obtained, wherein each code can be activated by either only one local server, or simultaneously by several local servers by which the code was obtained. Each code can therefore be obtained by several servers at the same time, the code being activated simultaneously in several regions, each of these local servers activating the code in the local market (region) covered by a given local server. In other words, each code can be activated multiple times at the same time, with each activation held by a different local server operating on a specific local market (region). This means that several regions, e.g. countries, represented by the local servers, can agree on interoperability between these regions, wherein one code can be activated simultaneously by each local server in a given region, wherein the refundable deposit can be paid and / or the container can be returned in any one of these regions. The code can be deactivated by any one of the local servers by which the code was previously activated. Several regions can also agree on the amount of the refundable deposit so that any return point, associated with any one of the local servers, can be instructed, by the local server communicatively connected with the return point, to allow refunding of the refundable deposit.

[0076] Each code can be deactivated only by the local server by which the code was activated, wherein each code can be deactivated by only one local server. This means that if the code was activated by several local servers and one of these local servers instructed the return point to receive the container and then deactivated the code, the other local servers can be informed about the deactivation so that any other local server cannot further manage this code as activated code. Any other local server thus cannot instruct the return point to receive the container again, activated code can be deactivated only once. Preferably, the local server, by which the code was deactivated, sends information on the deactivation to the central server managing all the codes from all the local servers, wherein the central server sends information on the deactivation to the other local servers that had activated this code. This step prevents frauds in container return process and multiple refunds of refundable deposits in different regions covered by different local servers. The local server may send information on the deactivation to the other local servers directly.

[0077] Each code can be also activated and then deactivated by only one specific local server. This premise ensures that all actions associated with the container, particularly the sale of the container, the activation of the code, the return of the container, the collection of the container, the refund of the refundable deposit on the container and the deactivation of the code, take place within the same region, the actions being covered by one local server.

[0078] Preferably, each of the local servers is communicatively connectable with at least one distributor point and with at least one return point, wherein the local servers are configured such that at least one local server is connectable with a specific return point. Return point is a facility which can be instructed, by the local server, to pay the refundable deposit and / or to receive the container. The return point can comprise various elements in order to facilitate collection of the used container and send the code of the container to the local server.

[0079] Preferably, the management and tracking system further comprises a production point for applying the unique codes to the containers, wherein the production point is communicatively connected with the central server. The production point is a facility responsible for physically producing and labeling the codes on the containers, the production point may also comprise a production facility to produce the containers themselves and / or the contents of the containers. In other words, the production point may be a detached facility producing only the containers or parts of the containers with the electronically readable codes, wherein the containers or parts of the containers with the electronically readable codes are then send to a particular manufacturer of the alimentary or non-alimentary content of the containers. The production point may be a particular manufacturer that produces the alimentary or non-alimentary content, and also directly producing the containers or parts of the containers with the electronically readable codes.

[0080] Preferably, the management and tracking system further comprises at least one return point communicatively connected with at least one local server, wherein each return point comprises a return point scanning device. Each local server is communicatively connected with at least one return point or with a network of return points designated to receive the containers. Each return point comprises the return point scanning device for direct scanning of the electronically readable code of the containers. One return point can therefore communicate with more local servers.

[0081] Preferably, the management and tracking system comprises at least one return point communicatively connected with only one local server. This arrangement is advantageous for a precise management and tracking of the containers available in a given local market, since all containers received at return points are controlled by only one local server as a single authority.

[0082] Preferably, at least one return point comprises a control unit, a collection bin for receiving containers, a receiving opening for inserting containers into the collection bin, a closure for closing the receiving opening and an actuator for driving a closing and opening movement of the closure, wherein the control unit is connected with the return point scanning device and the actuator is controlled by the control unit of the return point. The control unit is configured to receive information on the electronically readable codes scanned by the return point scanning device and to communicate with the local server, the control device can therefore comprise a communication unit.

[0083] Based on the information from the local server, the control unit of the return point is instructed to receive the container, i.e. to allow a user to insert the container into the collection bin via the receiving opening. Preferably, the control unit is instructed to receive the container only after a verification from the local server that the scanned electronically readable code is active (the code was previously activated by the local server), and that the container is eligible to be returned. If the scanned electronically readable code is active and verified, the control unit is configured to move the actuator of the closure in order to open the receiving opening and allow the container to be inserted into the collection bin. If the scanned electronically readable code is not active and verified, the control unit is configured to move the actuator of the closure in order to close the receiving opening and prevent the container from being inserted into the collection bin.

[0084] The control unit, the return point scanning device and the receiving opening with the closure and the actuator may be located directly on the collection bin, the collection bin being a free-standing collection bin located outdoor or indoor of a return point, e.g. in a supermarket o other retail facility. In another aspect, the return point may be located in a special place of the retail facility, the control unit and the return point scanning device being physically separated from the collection bin, e.g. by a wall in which the receiving opening is made. The collection bin can be therefore hidden behind the wall and not available to the user, the closure and the actuator can also be located on the back of the wall.

[0085] The return point can comprise two or more receiving openings for receiving containers from a different material, e.g. one receiving opening for plastic containers and one receiving opening for metal containers. If the code comprises information about the material of the container, the code can be scanned by the return point scanning device, wherein the control unit of the return point selectively opens only one receiving opening suitable to accept the containers of the particular material.

[0086] Preferably, return point further comprises one or any combination of components comprising a display, a voucher printer and a monitoring system for monitoring the content of the collection bin, the display, the voucher printer and the monitoring system being communicatively connected with the control unit of the return point. The display is used to directly inform the user about the progress of the return process, i.e. about the verification of the code by the local server, about the amount of the refundable deposit etc. or about any errors that can occur during the return process. The display can be an integral part of the return point scanning device.

[0087] The control unit is also configured to refund the refundable deposit of the container to the user. The return point may therefore comprise a voucher printer. The voucher printer can be used especially in the retail facility, the voucher printer being used to print a bill that can be exchanged for cash money at the cash desk of the retail facility. The return point may further comprise a module for communication with a banking system, said module allowing the refund of the refundable deposit directly by transferring the corresponding amount to the user's or any other bank account. It is also advantageous if the return point comprises an input device for communication between the user and the control device, the input device can be a touch display, a keyboard, etc., wherein the user can select a means to obtain the refundable deposit.

[0088] The monitoring system is used to control the content of the collection bin. Monitoring system can be an intelligent monitoring system, e.g. a camera with an intelligent software based on Al methods, wherein the monitoring system can visually control the handover of the container and the travelling path of the container from the receiving opening to the collection bin. Monitoring system can further identify a fill level of the collection bin or analyze the contents of the collection bin and identify foreign bodies or contaminants that do not belong into the collection bin. The return point can comprise only one of said components (the display device, the voucher printer, or the monitoring system) or any combination of these components.

[0089] Description of the Drawings

[0090] The summary of the invention is further explained by examples of its embodiments, which are described using the accompanying drawings, in which:

[0091] Fig. 1 A Shows an overall scheme of the management and tracking system of the containers with a refundable deposit and selected steps of the method for managing and tracking of the containers.

[0092] Fig. 1 B Shows simplified overall scheme of the management and tracking system of the containers with a refundable deposit.

[0093] Fig. 2A Shows the first section of the production line of the beverage producer, the first section comprising two arrays of code scanners, an array of barcode printers and an array of barcode scanners.

[0094] Fig. 2B Shows the first second section of the production line of the beverage producer, the first section comprising a pallet barcode scanner.

[0095] Fig. 3 Shows a smart return point.

[0096] Fig. 4 Shows a return process of the containers with a refundable deposit.

[0097] Fig. 5 Shows simplified overall scheme of the management and tracking system of the containers with a refundable deposit with a direct connection of the distributor point and the local server. Embodiments of the Invention

[0098] The invention will be further explained by examples of its implementations with reference to the corresponding drawings. One example implementation is an embodiment of a system for managing and tracking containers 1 with a refundable deposit, which is schematically shown in Fig. 1 A and Fig. 1 B.

[0099] The management and tracking system according to the first embodiment is applied to containers 1, in particular bottles or cans for beverages, that are each labelled with a unique electronically readable Data Matrix code 3 placed on the top of the container 1. (on the cap or lid). Placing the codes 3 on the cap or lid makes them easy to read by scanning devices and prevents damage of the codes 3 after compression of the container 1. In this embodiment, the bottles or cans for beverages are disposable, i.e. they are recycled after each cycle of their use and not used repeatedly.

[0100] The structure and characteristics of each Data Matrix Code 3 are as follows:

[0101] - a numeric code 3 with a length of up to 23 digits (digits 0 to 9),

[0102] - the code 3 can fit into 64-bit integer if the length is lower or equal to 19 digits,

[0103] - digit positions 23 and 22 refer to a corresponding central server 8 (Certification Authority ID, two digits),

[0104] - positions 21 to 17 refer to reserved zeros (five digits reserved for a possible future usage),

[0105] - position 16 refers to the material of the container 1 (one digit)

[0106] - positions 15 to 2 refer to a unique identifier of the container (fourteen digits)

[0107] - position 1 refers to the checksum of the code 3, i.e. to the amount of the refundable deposit (the amount of the refundable deposit is placed at the end for convenience, ease of calculation and future proofing).

[0108] The system comprises a central server 8, a production point 9, a plurality of beverage producers 17, a plurality of distributor points 4, a plurality of local servers 2 and a plurality of return points 5. The central server 8 is a central authority responsible for generating the unique numeric codes 3 and it is communicatively connected with the production point 9, wherein the production point 9 is a manufacturing plant that produces the caps / lids for the containers 1, and also directly applies the unique numeric codes 3 in the form of Data Matrix codes 3, generated by the central server s, to the caps / lids. Production point 9 is communicatively connected with a plurality of beverage producers 17 (for simplicity, only one beverage producer 17 is shown in Fig. 1A and Fig. 1 B) and each beverage producer 17 is communicatively connected with a plurality of distributor points 4, wherein the distributor points 4 are located at different regions, the different regions corresponding to different local markets operated by different local servers 2.

[0109] In the first embodiment, each local server 2 is responsible for code 3 management in a specific country, wherein each local server 2 is also communicatively connected with a corresponding local DRS server 26 of the specific country. The local DRS server 26 is a standard server managing the whole system of the containers 1 with the refundable deposit in the specific country, the local DRS server 26 being communicatively connected with the beverage producers 17. Each of the distributor points 4 is communicatively connected with only one local server 2, wherein the connection is indirect via the central server 8. Similarly, the return points 5 are located at different regions operated by different local servers 2, wherein each of the return points 5 is communicatively connected with only one local server 2 and this connection is direct.

[0110] The following section describes details of the elements of the management and tracking system according to the first embodiment (the simplified scheme of the main components of the system is shown in Fig. 1 B).

[0111] The central server 8 corresponds to the ID authority, which is responsible for generating of the Data Matrix codes 3 and managing the database of codes 3 and related information. The central server 8 comprises a module 31 of the central server with a database 32 of the central server that stores the list of generated Data Matrix codes 3 and all the necessary information on each of the codes 3, namely the status of the code 3 (activated / deactivated), the information that the Data Matrix code 3 was deactivated after the refundable deposit has been paid, and optionally the territory (country) of the local server 2 after the Data Matrix code 3 has been activated by this local server 2.

[0112] The database 32 of the central server also stores information on a multipack 7 barcode 24 or a pallet 25 barcode 24 of the associated Data Matrix codes 3 of the individual containers 1 contained in the multipack 7 and the pallet 25. The database 32 of the central server also stores the information on the beverage producer 17 of the product contained in the container 1. and the information on the EAN code for the product stored in the container 1 labelled with the Data Matrix code 3, wherein the information will be obtained from the production line during the scanning of the codes 3 and the multipacks 7 of the containers 1 (the production line is described below). The EAN code information is important for containers 1 with different refundable deposit amounts in different countries, operated by different local servers 2. The database further stores the information on the material of the container 1 associated with each code 3. The central server 8 generally serves as a source of information on the codes 3 for the local servers 2.

[0113] The production line of the beverage producer 17 according to the first embodiment is shown in Fig. 2A and Fig. 2B. (The manufacture of the caps / lids and the application of the Data Matrix codes 3 to the caps / lids takes place primarily at the caps / lids production point 9, or in specific cases such as a can beverage production the Data Matrix codes 3 can be applied during the beverage production; the manufacture and the application of the Data Matrix codes 3 is not shown in the picture). The production line is provided with two computers, i.e. a primary computer 18 and a secondary computer , the two computers being in communicative connection with all other components of the production line. The other components are arranged along the transport direction of the containers 1 through the production line and these components comprise:

[0114] - a primary array 20 of code scanners for scanning the Data Matrix codes 3 on the caps / lids,

[0115] - a backup (control) array 20 of code scanners for scanning the Data Matrix codes 3 on the caps / lids,

[0116] - an array 21 of barcode printers for applying the barcodes 24 on the multipacks 7,

[0117] - a primary array 22 of barcode scanners for scanning the barcodes 24 on the multipacks 7 and

[0118] - a backup (control) array 22 of barcode 24 scanners for scanning the barcodes 24 on the multipacks 7.

[0119] The components above are listed in the order in which they are arranged along on the production line in Fig. 2A, the production line being set up to handle the containers 1 in rows of six (these rows are numbered N, N+1 , N+2 etc.) and to handle the multipacks 7 in rows of three. The components of the production line in Fig. 2B further comprise a pallet 25 barcode 24 printer for printing and applying the barcodes 24 on the pallets 25 (pallet 25 barcode 24 printer is not shown in the picture) and finally a pallet barcode scanner 23. The secondary computer 19 serves as a control computer and backup information store in the event of primary computer 18 failure.

[0120] The distributor point 4 is a point within the distribution network operated by the beverage producer 17, namely a warehouse within the distribution network operated by the beverage producer 17. The distributor point 4 comprises a central computer and a distributor point scanning device 28 for scanning the electronically readable Data Matrix codes 3, the distributor point scanning device 28 being communicatively connected with the central computer. The distributor point 4 is communicatively connected with the beverage producer 17 via the central computer of the distributor point 4. In the first embodiment, the distributor point scanning device 28 is a handheld scanner in a wireless communication with the central computer, wherein the distributor point scanning device 28 is used for scanning the barcodes 24 of the pallets 25 received from the beverage producer 7.

[0121] Scanned pallet 25 barcode 24 contains information on multipack 7 barcodes 24 packed in the pallet 25 and the information on the Data Matrix codes 3 of the individual containers 1 contained in that multipack 7 and the pallet 25. The particular Data Matrix codes 3 and a corresponding pallet 25 barcode 24 are associated automatically, wherein not all the Data Matrix codes 3 and / or the corresponding containers 1 eventually will be made available for sale due to a defect detected after the scanning of the Data Matrix codes 3 but before the packaging of the containers 1 into the pallet 25. In order to cover possible faults or defective pieces, e.g. defective containers 1 or defective Data Matrix codes 3 in the pallet 25, the pallet 25 barcode 24 is associated with the number of the Data Matrix codes 3 corresponding to the pallet 25 and additionally with 1 % of the Data Matrix codes 3 corresponding to the previous pallet 25 and with 1 % of the Data Matrix codes 3 corresponding to the following pallet 25. Some Data Matrix codes 3 (the Data Matrix codes 3 corresponding to the initial or final series of the containers 1 in each pallet 25) are therefore associated with two pallet 25 barcodes 24 corresponding to two consecutive pallets 25 produced at the production line.

[0122] The central computer of the distributor point 4 is further communicatively connected with the central server 8, wherein the central server 8 stores the data relations between the code 3, the multipack 7 and the pallet 25. In the first embodiment, the distributor point 4 is communicatively connected with the local server 2 indirectly via the central server s, which is shown in Fig. 1 B, wherein both the distribution point 4 and the corresponding local server 2 can communicate only with the central server 8, but they cannot communicate with each other directly.

[0123] The local server 2 is communicatively connected with plurality of the distributor points 4 via the central server 8. The local server 2 is configured to receive (via the central server 8) the codes 3 of the individual containers 1 from the central computer of the distributor points 4, to receive the codes 3 of the individual containers 1 from the return point 5, to activate and deactivate the Data Matrix codes 3 and further to send the information on an updated (activated / deactivated) status of each Data Matrix code 3 assigned to an individual container 1. to the central server s. The local server 2 comprises a module with a database that stores the information on the active / inactive status of the Data Matrix codes 3 and the amount and status of the refundable deposit. In the first embodiment, the information about the refundable deposit is stored only by the local server 2.

[0124] The local server 2 is also communicatively connected with a plurality of return points 5, wherein the local server 2 is configured to receive the codes 3 of the individual containers 1 from the return point 5. In this embodiment the return point 5 comprises a return point scanning device 6 and a control unit 29, wherein the return point 5 is communicatively connected with the local server 2 via the control unit 29 of the return point 5. The return point 5 is shown in Fig. 3 and comprises a complex and fixedly installed device comprising the scanning device with a touch display device 14, an integrated voucher printer 16 and the control unit 29, wherein the control unit 29 is in a wireless remote communication with the central server 8. The control unit 29 is configured to allow the refundable deposit (of the container 1) to be paid according to the preferences of the user. The refundable deposit may be paid by means of a discount voucher; the voucher being redeemed at the cash desk of the retailer operating the return point 5. The control unit 29 is further communicatively connected with the banking system, allowing the refundable deposit to be paid to the users selected bank account of the user or donated to charity.

[0125] The return point 5 also comprises a smart receiving opening 12 closable with a closure 13 which is interconnected with the control unit 29 of the return point s. The smart receiving opening 12 is installed in the wall and comprises a light indicator that can emit a different color and thus indicate whether the user is supposed to insert the container ! or not. The color of the light is chosen between green and red depending on the approval of the code 3 of the container ! by the central server s, after scanning the Data Matrix code 3 by the return point scanning device 6 and sending the code 3 to that central server 8 to a approve the status of the code 3 (eligibility to be returned and pay the deposit).

[0126] The return point 5 further comprises a collection bin 1 1 located behind the wall of the return point 5, the collection bin 11 thus being hidden and not visible / accessible to the user of the return point 5. The collection bin 11 is further provided with a smart monitoring system 15 for monitoring the travelling path of the containers 1 between the receiving opening 12 and the collection bin 11 and for monitoring the content of the collection bin 1 1 . The monitoring system 1.5 is communicatively connected with the control unit 29 of the return point s, and it comprises a camera with an analytical module using an Al software. Based on the visual recordings of the travelling path of the containers 1 to the collection bin Ij., recorded by the camera, the analytical module is primarily configured to detect and confirm that the container 1_ has been thrown into the collection bin 11 . The receiving opening 12 further comprises a back-up control mechanism of the container ! handover, said mechanism comprising an optical gate using an array of infrared beams in order to detect and confirm that the container ! has been thrown into the collection bin 11 . The back-up control mechanism controls the container ! handover in the event of failure of the smart monitoring system 15.

[0127] Based on the visual recordings of the collection bin 1_1_, recorded by the camera, the analytical module is further configured to detect the level of fullness of the collection bin 1 1 and to recognize any foreign matter thrown into the collection bin 11 . The analytical module of the monitoring system 15 is used to generate alerts for the control unit 29 of the return point 5, the alerts carrying information about a need to clean the collection bin 1 1 from the foreign matter and about a need to discard the content of the full collection bin Ij.. The back side of the receiving opening 12 is further provided with a silencer 10 to dampen the movement of the container into the collection bin 1 1. The following section describes detailed steps of exemplary method for managing and tracking of containers 1 with a refundable deposit.

[0128] In the first step, the beverage producer 17 sends a request to the production point 9 to produce a batch of the required number of caps / lids for containers 1 of products with a specific EAN code (step 101 ).

[0129] In the next step, the production point 9 sends a request to the central server 8 to generate a batch of the required number of unique Data Matrix codes 3 for containers 1 of products with a specific EAN code (step 102).

[0130] In the next step, the central server 8 generates a batch of the required number of unique Data Matrix codes 3 for containers 1 of products with a specific EAN code (step 103), sends the batch of generated unique Data Matrix codes 3 to the production point 9 (step 104) and stores the information on the generated unique Data Matrix codes 3 with a specific EAN code for the product contained in these containers 1, the information being stored in the database 32 of the central server.

[0131] In the next step, the production point 9 produces the required number of caps / lids and applies the unique Data Matrix codes 3 received from the central server 8 to the caps / lids (step 105). The Data Matrix codes 3 are laser engraved or pre-printed on the caps / lids of the containers 1.

[0132] In the next step, the production point 9 sends the caps / lids with the corresponding unique Data Matrix codes 3 to the beverage producer 17 (step 106).

[0133] In the next step, the beverage producer 17 applies the caps / lids to close the containers 1, and records and stores the information on the codes in the primary computer 18 and in the secondary computer 19 (step 107, the step 107 comprising a series of sub-steps 107a to 107d which are described below). The beverage producer 17 then packs the containers 1 with the unique Data Matrix codes 3 into packages (multipacks 7 or trays) of individual containers 1 and packs the multipacks 7 into pallets 25, wherein each multipack 7 and each pallet 25 is labelled with a unique barcode 24 (step 108). The barcodes 24 are generated by the beverage producer 17 and are used preferably for its internal use. Process of managing the codes 3 within the control system of the production line according to Fig. 2A and Fig. 2B comprises the steps of:

[0134] - scanning the rows of the containers 1 with the primary array 20 of code scanners and subsequently with the backup (control) array 20 of code scanners and sending these codes 3 to the primary computer 18 and to the secondary computer 19 (step 107a),

[0135] - associating the containers 1 into multipacks 7 of individual containers 1, - generating, by the primary computer 18, a unique multipack 7 barcode 24, and associating the codes 3 scanned by the primary array 20 of code scanners and by the backup (control) array 20 of code scanners, with the unique multipack 7 barcode 24 (step 107b),

[0136] - printing the unique multipack 7 barcodes 24 and applying the barcodes 24 on the multipacks 7,

[0137] - scanning the rows of the multipacks 7 barcodes 24 by the array 22 of barcode scanners (step 107c),

[0138] - packing the multipacks 7 into the pallet 25,

[0139] - generating, by the primary computer 8, a unique pallet 25 barcode 24, and associating the multipack 7 barcodes 24 scanned by the array 22 of barcode scanners, with the unique pallet 25 barcode 24,

[0140] - printing the unique pallet 25 barcode 24 and applying the barcode 24 on the pallet 25,

[0141] - scanning the pallet 25 barcode 24 by the pallet barcode scanner 23 (step 107d).

[0142] The information from the pallet barcodes 24 associated with the corresponding multipack 7 barcode 24 and the information of multipack 7 barcodes 24 associated with the corresponding Data Matrix codes 3 of the individual containers 1 are communicated and stored in both the primary computer 18 and the secondary computer 19. Storing the information in both the primary computer 18 and the secondary computer 19 serves as a dual control mechanism.

[0143] This scanning is done to identify the Data Matrix codes 3 of the containers 1 packed into multipacks 7 which are then given another unique internal producer logistics barcode 24. This internal producer logistics barcode 24 links the batch of unique codes of the containers 1 in the multipack 7 in the internal system of the producer. Analogous procedure is applied for identifying pallets 25 with a plurality of multipacks 7 or containers 1, wherein each pallet 25 carries a unique barcode 24 as well. All the information on the multipack 7 barcode 24 and pallet 25 barcode 24 and the associated Data Matrix codes 3 of the individual containers 1 contained in that multipack 7 and the pallet 25 are also sent to the central server 8 and stored in the database 32 of the central server.

[0144] In the next step, each pallet 25 produced by the beverage producer 17 is transported to the distributor point 4 (step 108). At the distributor point 4, the pallet 25 barcodes 24 are scanned by the distributor point scanning device 28 and sent to the central computer of the distributor point 4. Subsequently in the next step, the pallet 25 barcodes 24 are sent to the central server 8, wherein the central server s stores the information on the linkage between each pallet 25 barcode 24 and the associated multipacks 7 barcodes 24 and the associated Data Matrix codes 3 of the individual containers 1 in the pallets 25. In this exemplary method, the distributor point 4 sends the pallet 25 barcodes 24 to the central server 8 which means that the distributor point 4 is authorized to send the pallet 25 barcodes 24 to the central server 8. In other words, after the pallet 25 barcodes 24 are sent from the distributor point 4, the central server s receives the pallet 25 barcodes 24 and does not perform any further verification as to whether the distributor point 4 is authorized to send them. In the next step, the codes 3 of the individual containers 1 contained in the pallet 25 are sent to the local server 2 for the activation (step 109).

[0145] Similarly to the verification of the distributor point 4, the central server 8 sends the codes 3 of the individual containers 1 to the local server 2, wherein the central server 8 is a trustworthy entity and it is thus not required to be authorized by the local server 2. The local server 2 thus receives the codes 3 and does not perform any further verification as to whether the central server 8 is authorized to send them.

[0146] In the next step, the local server 2 activates the received codes 3 of the containers 1, i.e. amends the status of the codes 3 in the database of the local server 2 to “activated”, which means that the containers 1 are now eligible to be returned and refunded at any of the return points 5 being in communication with this local server 2. The local server 2 then sends the information on the updated status of the codes 3 to the central server 8 (step 1 10). The central server 8 then registers the codes 3, in the database 32 of the central server, as active ones, and sends the information on the activation to the other local servers 2 by which the code 3 is intended to be kept as active (the container 1 can be returned in any of the regions operated by these local servers 2). The local server 2 also sends the information on the number of the codes 3 and the updated status of the codes 3 to the local DRS server 26 of the country (step 1 11 ).

[0147] In the next step, automatically with the activation of the codes 3, the local DRS server 26 sends an invoice to the beverage producer 17 for the number of the containers 1 with the activated codes 3 placed on the local market operated by this local DRS server 26 (step 1 12a). Once the containers 1 with the activated codes 3 have been placed on the market, the local DRS server 26 charges the beverage producer 17 an industry fee for each of the products (containers 1) placed on the market. The amount of the industrial fees depends on the material and / or the size of the container T These industrial fees are used to fund the entire DRS system. The local DRS server 26 further sends a list of products (containers 1) with associated EAN codes to the return point 5 (step 1 12b). This list shows the containers 1 with associated EAN codes that can be accepted in this local market, i.e. by all local return points 5 of this local market connected with the local server 2.

[0148] After these steps, the container 1 with the activated code 3 can be purchased and used by consumers and the Data Matrix code 3 is not tracked until the Data Matrix code 3 is scanned again, in particular until the Data Matrix code 3 is scanned at the return point 5. In the next step, the container 1 with the Data Matrix code is brought by the user to the return point 5 and processed by the return point 5 (step 1 13). The return process of the step 1 13 comprises a series of sub-steps 113a to 1 13g shown in Fig. 4. Firstly, the code 3 is scanned by the return point scanning device 6 of the return point 5 (step 113a) (sub-steps 1 13b to 113g are described below). The code 3 is then, by the control unit 29 of the return point s, sent to the verification by the local server 2 interconnected with the return point s (step 1 14). The local server 2 then performs the verification of the code 3 (step 1 15), i.e. compares the received code 3 with the list of codes 3 stored in the database of the local server 2. If the received code 3 matches to a record from the list, the local server 2 also verifies that the status of the code 3 in the database is “activated”. If the received code 3 corresponds to the record in the database of the local server 2 and the code 3 status is “activated”, the code 3 is thus verified. The verification of the code 3 means that the code 3 is eligible to be returned and that the refundable deposit can be paid to the user standing at the return point 5.

[0149] The local server 2 subsequently amends the status of the received Data Matrix code 3, in the database of the local server 2, from “activated” to “deactivated”, and the information on the verification is then sent back to the control unit 29 of the return point 5. Analogously to the step 110, the local server 2 further sends the information on the updated “deactivated” status of the code 3 to the central server 8.

[0150] The information on the verification of the code 3 is shown in the display device 14 of the return point in order to inform the user that the return process of the container 1 is allowed. The control unit 29 of the return point s controls the container 1 handover (step 1 13b), wherein the control unit 29 sends a command to the actuator 30 of the closure 13 of the receiving opening 12 so that the closure 13 is raised, and the receiving opening 12 is open for insertion of the container 1_. The user inserts the container ! into the receiving opening 12 and then the control unit 29 sends a command to the actuator 30 of the closure 13 of the receiving opening so that the closure 13 is lowered, and the receiving opening 12 is closed. When the container ! is thrown into the receiving opening 12 and into the collection bin 1_1_, both the container ! and the collection bin 11 are being monitored by the smart monitoring system 15 (step 1 13b). The user can then scan a plurality of other codes 3 of the containers 1 (step 113 c).

[0151] The scanning of the codes 3 from the containers ! and the monitoring of the handover of the containers ! (steps 1 13b and 113c) run concurrently and independently of sending the codes 3 to the local server 2 and verification of the codes 3 (steps 114 and 1 15). Several steps 115 shown in Fig. 4, referring to the verification of the code 3, represent the verification of each individual code 3 scanned by the return point scanning device 6. After the container 1 has been successfully thrown into the collection bin 1 1 via the receiving opening 2, so that the Data Matrix code 3 of this container 1 cannot be scanned again, the user is informed by the display device 14 that the return process of the container has been successful, wherein the user is prompted to select the option for preferred means of payment of the refundable deposit (step 1 13d). The user can tap on the touch display device 14 and choose to print the discount voucher to be redeemed at the cash desk of the retailer. In this case, the control unit 29 sends a command to the integrated voucher printer 16 to print the discount voucher (step 1 13e). The user can select the bank transfer of the amount of the refundable deposit to his bank account or to charity. The voucher printer 16 is then instructed, by the control unit 29, to print a transfer receipt.

[0152] In case the collection bin 1 1 is full, or any other problem is detected by the monitoring system 15 (step 1 13f), the analytical module of the monitoring system 15 generates an alert reported to the control unit 29 of the return point 5, wherein this alert is also shown in the display device 14. Based on the alert generated by the monitoring system 15, the control unit 29 is responsible for managing the transport of the containers 1 collected in the collection bin 1 1 to a recycling facility (step 1 13g).

[0153] Successful return process at the return point 5 is then reported, by the control unit 29 of the return point 5, to the local server 2 and then to the local DRS server 26 (step 1 16). The reports generally contain information on the printed vouchers, the number of returned containers 1, fullness of the collection bin 1 1 at the return point 5 etc.

[0154] If the code 3 received from the return point 5 does not match to any record from the list of the database of the local server 2, the code 3 is thus not verified, and this information is then sent back to the control unit 29 of the return point 5. The information on the failure to verify the code 3 is displayed on the display device 14 of the return point in order to inform the user that the return of the container is not allowed. The control unit 29 sends a command to the actuator 30 of the closure 13 of the receiving opening 12 to keep the closure 13 down and close the receiving opening 2. The same procedure is applied if the code 3 received from the return point 5 does not correspond to a record in the list of the database of the local server 2 but if the code 3 status is “deactivated”. This means that the code 3 has previously been scanned by the return point scanning device 6 from another return point s where the refundable deposit has already been paid. This is probably a case of refundable deposit fraud, where the fraud event is then reported, by the control unit 29 of the return point 5, to the local server 2 and to the local DRS server 26 (step 1 17). The local DRS server 26 then collects the information obtained from all return points 5 of the local market operated by this local DRS server 26 in order to monitor numbers of returned containers 1, refunded containers 1, unreturned containers 1, fraud events, etc. (step 1 18).

[0155] The return point 5 also reports the information on the return process to the return point vendor 27 (step 1 19). The return point vendor 27 is an authority that provides the return points 5 and all the necessary equipment of the return points 5, the return point vendor 27 is therefore communicatively connected with a plurality of return points 5 (for simplicity, only one return point 5 is shown in Fig. 1 A) and it is responsible for configuring the operations and providing the service and maintenance of the return points 5 (step 120).

[0156] After the successful return process of the disposable container 1 at the return point 5, the disposable (non-reusable) container 1 is directed to the recycling facility, and it cannot be used again. After the code 3 has been deactivated in the database 32 of the central server and the local server 2, the central server 8 amends the record of this code 3 in the database by archiving the part of the record carrying the information on the material of the container 1 (position 16, one digit of the code 3), the EAN code, the multipack 7 barcode 24, the pallet 25 barcode 24 and the producer of the product contained in the disposable container 1 associated with this code 3. After archiving the metadata of the code 3, it is possible to use this code 3 for applying to a new container 1 since there is no linkage to the information on the previous container T

[0157] The following section describes the second embodiment of the management and tracking system of containers 1 with a refundable deposit. In this embodiment, the container 1_ is reusable, which means that when the container 1 is returned, refunded, and the associated Data Matrix code 3 is deactivated, the container 1. is not recycled but cleaned and refilled, with the possibility of the original Data Matrix code 3 being reactivated for the same container 1_. This embodiment is particularly suitable for the glass containers 1, rigid plastic containers 1 or metal containers 1.

[0158] In this embodiment, the Data Matrix code 3 carries information about the material and also about the reusability of the container 1.. This information is stored in the database of the local server 2 and in the database 32 of the central server, this information being part of the record of the particular code 3 in the database. The life cycle of such reusable container 1 is the same as in the first exemplary embodiment and it differs only at the end of each cycle after the container 1 has been successfully returned at the return point 5.

[0159] After the successful return process of the reusable container 1 at the return point 5, the reusable container 1 is directed to a cleaning facility, wherein the associated code 3 remains linked with the original container T After the code 3 has been deactivated in the database 32 of the central server and the database of the local server 2, the central server 8 amends the record of this code 3 in the database by amending the status of the code 3 to a status “ready for further use”. In parallel, the central server 8 archives only that part of the record which contains the link between the code 3 and the information on the EAN code, the package ? barcode 24, the pallet 25 barcode 24 and the producer of the product contained in this reusable container ! associated with this code 3. The information on the unique identifier (position 15 to 2, fourteen digits of the code 3), on the central server 8 which has generated the code 3 (positions 23 and 22, two digits of the code 3), and on the material and reusability of the container ! assigned to the code 3 (position 16, one digit of the code 3), remain a part of the digital record of the code 3.

[0160] The system and the method of the first embodiment and the second embodiment can be combined into a complex system, wherein the central server 8 and the production point 9 produce multiple types of differently structured Data Matrix codes 3 corresponding to different types of both reusable and non-reusable containers !. Based on the material and reusability of each container ! scanned at the return point 5, the return point 5 communicates with the local server 2, wherein the local server 2 and the central server 8 manages the code 3 accordingly by archiving the relevant part of the code 3.

[0161] Another embodiment is a local server 2 which is configured, by having a processor and programmed instructions, for obtaining unique codes 3 directly from an authorized distributor point 4 and activating them, and later receiving codes 3 from return point(s) 5. If a received code 3 is activated, the local server 2 sends instructions to the corresponding return point 5, to pay a deposit, and deactivates the code 3. Details of the individual functions of this local server 2 can be as described above in the first embodiment of the system and the method.

[0162] The following section describes the alternative embodiments of the management and tracking system of the containers ! with the refundable deposit and the alternatives in the method for managing and tracking of containers ! with the refundable deposit.

[0163] In an alternative embodiment, the unique code 3 of the container ! comprises a series of digits representing the EAN code of the product contained in the container T The digits of the EAN code can occupy any positions of the numeric unique code 3, e.g. the first series of the digits of the code 3, the first series of the digits of the code 3, etc. The unique code 3 can be represented by different digital representations other than the Data Matrix code 3, e.g. by a barcode 24, an RFID code 3, an NFC code 3, etc. Instead of barcodes 24, any other type of the electronically readable code 3 can be used to identify the multipack 7 and / or the pallet 25. In an alternative embodiment, the management and tracking system can comprise two or more central servers 8, each central server s comprising the features described in the first exemplary embodiment. The advantage of a plurality of the central servers 8 is that one central server s can manage the operation of a plurality of local servers 2 in a larger region, e.g. in a continent, wherein a number of continents are covered by a number of central servers 8.

[0164] In an alternative embodiment, the production point 9 might be centralized together with the central server 8. In other words, the production point 9 and the central server 8 may be parts of a single facility.

[0165] In an alternative embodiment, the production line of the beverage producer 17 can comprise only the primary computer 1.8, wherein the secondary computer 1.9, i.e. a control computer and backup information store in the event of primary computer 18 failure, can be omitted. In another embodiment, the secondary computer 19 is installed only for the initial phase of the operation of the production line of the beverage producer 17, wherein the secondary computer 19 is then deinstalled once the high-quality standards and control of the production line of the beverage producer 17 are achieved.

[0166] In an alternative embodiment, the multipack barcode 24 printer and the multipack barcode scanner 23 (before packing of the multipacks 7 into the pallet 25) of the production line of the beverage producer 17 can be omitted and the number of multipacks 7 can be calculated from the information in the primary computer 18 and the secondary computer 9, taking into account a known number of multipacks 7 after the scanning.

[0167] In an alternative embodiment, the local server 2 can receive, directly from the distributor point 4, the scanned pallet 25 barcodes 24 and the multipack 7 barcodes 24 comprising the information on the Data Matrix codes 3 of the individual containers 1 contained in the pallet 25 and in the multipack 7, whereby the local server 2 automatically activates all the Data Matrix codes 3 of these containers T A scheme of a system with a possible direct communication between the distributor point 4 and the corresponding local server 2 is shown in Fig. 5. Both the distributor point 4 and the corresponding local server 2 are connected with the central server 8 as well.

[0168] In an alternative embodiment, the distributor point 4 can be centralized together with the beverage producer 17, wherein the sending of the codes 3 for activation by the local server 2 is done by the beverage producer 7. In this embodiment, the primary computer 18 of the beverage producer 17 corresponds to the central computer of the distributor point 4.

[0169] In an alternative embodiment and a special case, the codes 3 of the containers 1 can be firstly activated after being scanned at the return point 5. This alternative is suitable for embodiments using the pallet 25 barcodes 24 and the multipack 7 barcodes 24, wherein the information on the codes 3 of the individual containers 1 contained in the corresponding package is lost. In this case, at least the pallet 25 barcode 24 distributed in the region operated by a corresponding local server 2 is known by the local server 2 since this barcode 24 has been scanned by the distributor point scanning device 28 and it was sent to the local server 2. When a code 3 of an individual container 1 from this pallet 25 is scanned at the return point 5, the local server 2 verifies if the code 3 corresponds to the pallet 25 barcode 24. Further, the local server 2 verifies if this pallet 25 barcode 24 and all the codes 3 associated with this pallet 25 barcode 24 have been previously received by the central server s, or even by the local server 2, i.e. if the codes 3 were intended for activation. If the pallet 25 barcode 24, associated with this code 3 of the container 1., has been received by the central server 8 and / or or by the local server 2, the local server 2 activates the code 3 of the container 1 immediately after receiving the container 1 at the return point 5 and instructs the return point 5 to pay the refundable deposit. This embodiment is not covered by the claims of the patent.

[0170] This embodiment with a late activation of the code 3 after scanning the container 1 at the return point 5 is advantageous in systems comprising two or more local servers 2, wherein the process of scanning the deactivated codes 3 can be used to diagnose an error in activation in particular regions, e.g. that the codes 3 have been activated by the first local server 2 and intended to be sold in a market A, wherein in fact the containers 1 with these codes 3 are predominantly being returned and scanned at the return points 5 in a market B operated by the second local server 2. This situation suggests that the distributor point 4 or the beverage producer 17 has sent the pallet 25 into a wrong region. The second local server 2 can receive all the containers 1 with these late activated codes 3, pay the refundable deposit to the users and then issue an invoice for the containers 1 to the first local server 2.

[0171] In an alternative embodiment, the local servers 2 of the countries can cooperate and share the information on the activation and / or deactivation of the code 3 and cooperate in the payment of the refundable deposit. In this alternative embodiment, the system comprises a first local server 2 and a second local server 2, the first local server 2 being communicatively connected with the second local server 2 and the code 3 being activated by one of the first local server 2 and the second local server 2. The code 3 can be activated by the first local server 2, wherein the first local server 2 then informs the second local server 2 of the activation of the code 3 and the code 3 has an active status in both the first local server 2 and the second local server 2. When the code 3 is scanned by the return point scanning device s, the return point 5 being communicatively connected with the second local server 2, the second local server 2 deactivates the code 3 and enables payment of the refundable deposit. The second local server 2 then informs the first local server 2 of the completed return process and the deactivation, wherein the first local server 2 then transfers the amount of the refundable deposit to the second local server 2 (the second local server 2 has previously paid this amount to the user at the time of the return of the container and can issue an invoice for the first local server 2).

[0172] In an alternative embodiment, the system comprises a first local server 2 and a second local server 2, both the first local server 2 and the second local server 2 being communicatively connected with one common distributor point 4 and one common return point s. The common distributor point 4 sends the code 3 scanned by the distributor point scanning device 28 to both the first local server 2 and the second local server 2, wherein both the first local server 2 and the second local server 2 activate the code 3 in their territories, wherein the first local server 2 is designated as an authority responsible for payment of the refundable deposit. When the code 3 is scanned by the return point scanning device 6 of the common return point being communicatively connected with both the first local server 2 and the second local server 2, the common return point s sends the code 3 to both the first local server 2 and the second local server 2, wherein both the first local server 2 and the second local server 2 deactivate the code 3 in their territories and the first local server 2 also enables the payment of the refundable deposit to the user. The common distributor point 4 can send the code 3 to the local servers 2 directly or indirectly, e.g. via a common central server 8 communicatively connected with both of the local servers 2.

[0173] In an alternative embodiment, the return point 5 further comprises at least one mobile scanning and display device of the user that is wirelessly connected with the local server 2. This mobile scanning device is, for example, the user's own smartphone equipped with a mobile application provided by the local server 2. The user scans the codes 3 of the containers 1 immediately after using the containers 1, typically after drinking the beverage contained in the container 1_. After scanning a number of codes 3 from the containers 1, the information about the scanned codes 3 is sent to the local server 2. The user then receives a digital voucher via the application interface, where a digital voucher can be shared by multiple users, typically a number of family members living in a household who return the containers 1 together.

[0174] One of the users then travels with the containers 1 with already scanned codes 3 to the return point 5 and uses the return point scanning device 6 to scan the digital voucher instead of scanning the individual codes 3 of the containers 1. The digital voucher contains the information on the number of containers 1 and the monitoring system 15 is then configured to check that the number of the containers 1 thrown into the receiving opening 12 and into the collection bin 1 1 corresponds to the number of the containers 1 on the digital voucher. The control unit 29 of the return point s is then instructed to pay the refundable deposit for the containers 1 up to the maximum number of containers 1 on the digital voucher, even if the user has thrown more containers 1 into the receiving opening 2. The other steps of the return process remain the same as in the first embodiment. This embodiment therefore comprises a return point 5 with one return point scanning device 6 at the return point 5 and a plurality of remote return point scanning devices 6 owned by the users. Scanning the codes 3 of the containers 1 in advance before getting to the return point 5 allows to speed up the container 1. return process and reduce queues at the return point 5 when the user returns a large number of containers 1, wherein the smart monitoring system 5 automatically counts the containers 1 thrown into the collection bin 1 1 .

[0175] Industrial applicability

[0176] Above-described invention can be used for any system and management of any returnable articles with or without refundable deposit.

[0177] List of Reference Numerals

[0178] 1 - container 18 - primary computer

[0179] 2 - local server 19 - secondary computer

[0180] 3 - code 20 - array of code scanners

[0181] 4 - distributor point 21 - array of barcode printers

[0182] 5 - return point 22 - array of barcode scanners

[0183] 6 - return point scanning device 23 - pallet barcode scanner

[0184] 7 - multipack 24 - barcode

[0185] 8 - central server 25 - pallet

[0186] 9 - production point 26 - local DRS server

[0187] 10 - silencer 27 - return point vendor

[0188] 11 - collection bin 28 - distributor point scanning

[0189] 12 - receiving opening device

[0190] 13 - closure 29 - control unit

[0191] 14 - display 30 - actuator

[0192] 15 - monitoring system 31 - module of the central server

[0193] 16 - voucher printer 32 - database of the central server

[0194] 17 - beverage producer

[0195] 101 - sending a request for caps / lids production to the production point

[0196] 102 - sending a request for the unique codes generation to the central server

[0197] 103 - generating of unique codes by the central server

[0198] 104 - sending the unique codes to the production point

[0199] 105 - producing of the caps / lids with the unique codes by the production point

[0200] 106 - sending the caps / lids to the beverage producer

[0201] 107 - applying the caps / lids to close the containers, recording and storing the information on the unique codes

[0202] 107a scanning the rows of the containers with the primary array of code scanners and with the backup (control) array of code scanners and sending these codes to the primary computer and to the secondary computer 07b generating a unique multipack barcode and associating the codes scanned by the primary array of code scanners and by the backup (control) array of code scanners, with the unique multipack barcode 07c scanning the rows of the multipack barcodes by the array of barcode scanners 07d scanning the pallet barcode by the pallet barcode scanner 08 - labelling a pallet with a unique pallet barcode 09 - activation of the code by the local server 10 - sending information about an updated status of the code 11 - sending information on the number of the codes and the updated status of the codes to the local DRS server 12 - sending an invoice to the beverage producer from the local DRS server 12a sending an invoice to the beverage producer from the local DRS server 12b sending a list of products (containers) with associated EAN codes from the local DRS server to the return point 13 - processing the code and the container at the return point 13a scanning the code by the return point scanning device 13b controlling of the container handover by the control unit of the return point and by the smart monitoring system 13c scanning a plurality of other codes of the containers 13d selecting the option for preferred means of payment of the refundable deposit 13e printing a discount voucher or a transfer receipt 13f monitoring of the collection bin 13g transporting of the containers collected in the collection bin to a recycling facility14 - sending the code to the verification by the local server 15 - verification of the code by the local server 16 - reporting of the information on the return process at the return point to the local DRS server 17 - reporting fraud to the local DRS server 18 - collection of information obtained from return points and monitoring of numbers of returned containers, unreturned containers and fraud events8 19 - reporting the information on the return process to the return point vendor 20 - configurating the operations of the return points by the return point vendor

Claims

CLAIMS1. A method for managing and tracking of containers (1) with a refundable deposit characterized in that the method comprises the steps of:- obtaining, by a local server (2), unique codes (3) assigned to individual containers (1), wherein the obtaining is based on receiving data from a distributor point (4), the data being indicative of the unique codes (3),- activating, by the local server (2), each code (3) assigned to an individual container (1 ),- receiving, by the local server (2), of codes (3) from a return point (5), the codes (3) being scanned from containers (1) by a return point scanning device (6) for scanning electronically readable codes (3),- verifying for each code (3) received from the return point (5) whether the code (3) is activated,- if the code (3) is activated, instructing the return point (5) to allow refunding of the refundable deposit of the container (1), and- deactivating the code (3) of the container (1 ) by the local server (2).

2. Method according to claim 1 characterized in that if the code (3) is activated, the method further comprises a step of instructing the return point (5) to receive the container (1) to which the activated code (3) is assigned.

3. Method according to any one of claims 1 to 2 characterized in that the step of obtaining, by the local server (1), unique codes (3) assigned to individual containers (1 ), comprises the steps of:- receiving, from the distributor point (4), data indicative of a code (3) assigned to a package of individual containers (1 ), and- obtaining the unique codes (3) assigned to individual containers (1), the unique codes (3) assigned to individual containers (1) being associated with the code (3) assigned to the package of individual containers (1).

4. Method according to any one of claims 1 to 3 characterized in that the step of deactivating the code (3) of the container (1) by the local server (2) is followed by a step of:- sending, by the local server (2), of the deactivated code (3) for application to a new container (1).

5. Method according to claim 4 characterized in that the method further comprises a step of:- receiving data, by the local server (2), about reusability of the container (1 ),- wherein the sending, by the local server (2), of the deactivated code (3) for application to a new container (1 ) occurs only if the container (1 ) is non-reusable.

6. Method according to any one of claims 1 to 5 characterized in that the unique electronically readable codes (3) are randomized.

7. A management and tracking system for containers (1 ) with a refundable deposit characterized in that the system comprises at least one local server (2) configured for implementing the method according to any one of claims 1 to 6.

8. Management and tracking system according to claim 7 characterized in that it further comprises at least one distributor point (4), the distributor point (4) comprising a distributor point scanning device (28) for scanning electronically readable codes (3), wherein each distributor point (4) is communicatively connected with at least one local server (2).

9. Management and tracking system according to claims 7 to 8 characterized in that it further comprises a central server (8) communicatively connected with the local server (2), the central server (8) comprising a module (31 ) of the central server for generating unique codes (3) and a database (32) of the central server for storing the information on the codes (3) assigned to containers (1 ).

10. The management and tracking system according to claim 9 characterized in that it comprises a total of at least two local servers (2), each local server (2) being communicatively connected with the central server (8), wherein each local server (2) is configured, independently of the other local servers (2), to obtain codes (3) assigned to containers (1 ) and further to activate and deactivate the obtained codes (3) assigned to containers (1 ), wherein each code (3) can be activated only by the local server (2) by which the code (3) was obtained and only the local server (2) by which the code (3) was activated can instruct a return point (5) to receive the container (1 ) from which the activated code (3) was scanned and / or instruct the return point (5) to allow refunding of the refundable deposit of the container (1 ).1 1 . The management and tracking system according claim 10 characterized in that each of the local servers (2) is communicatively connectable with at least one distributor point (4) and with at least one return point (5), wherein the local servers (2) are configured such that at least one local server (2) is connectable with a specific return point (5).

12. The management and tracking system according to any one of claims 9 to 11 characterized in that it further comprises a production point (9) for applying the unique codes (3) to the containers (1), wherein the production point (9) is communicatively connected with the central server (8).

13. Management and tracking system according to any one of claims 7 to 12 characterized in that it further comprises at least one return point (5) communicatively connected with at least one local server (2), wherein each return point (5) comprises a return point scanning device (6).

14. The management system according to claim 13 characterized in that at least one return point (5) comprises a control unit (29), a collection bin (11) for receiving containers (1 ), a receiving opening (12) for inserting containers (1 ) into the collection bin (11), a closure (13) for closing the receiving opening (12) and an actuator (30) for driving a closing and opening movement of the closure (13), wherein the control unit (29) is connected with the return point scanning device (6) and the actuator (30) is controlled by the control unit (29) of the return point (5).

15. The management system according to claim 14 characterized in that the return point (5) further comprises one or any combination of components comprising a display (14), a voucher printer (16) and a monitoring system (15) for monitoring the content of the collection bin (11 ), the display (14), the voucher printer (16) and the monitoring system (15) being communicatively connected with the control unit (29) of the return point (5).

Images