System and method for inventory management and object authentication

Abstract

The present disclosure provides a system and a method for inventory management and object authentication The system 100 includes one or more user devices 120a-n configured to receive one or more input data provided by the user. The input data includes user data, object data and label requests. The system 100 includes one or more data repositories 160 and a server 140 configured to receive the input data from the user device 120a-n, register new user by storing in the data repository 160 and authenticate existing users, receive label requests from the user device 120a-n, route label requests to one designated region, schedule appointment with field agents, authenticators and conservators, generate one or more labels with code, dispatch the generated label to the at least one designated region and monitor and track usage of the label.

Description

SYSTEM AND METHOD FOR INVENTORY MANAGEMENT AND OBJECT AUTHENTICATIONTECHNICAL FIELDThe present disclosure in general relates to a unique coding system for inventory management and authentication of objects. In particular, the present disclosure relates to a system and method for inventory management and object authentication.BACKGROUND

[0001] This section is intended to provide information relating to the technical field and thus, any approach or functionality described below should not be assumed to be qualified as prior art merely by its inclusion in this section.

[0002] Inventory management is a strategic step of overseeing and controlling the flow of goods and materials. It contains everything from ordering and storing inventory to tracking its movement. Inventory management in the context of art collections involves systematic organization, tracking, and maintenance of artworks. Museums, galleries, private collectors, and art institutions employ inventory management practices to ensure the preservation, documentation, and accessibility of their collections. This includes cataloging each piece with detailed information such as artist, title, medium, dimensions, acquisition date, location and condition.

[0003] Authentication of objects, particularly in the context of, collectibles is a step aimed at verifying the origin and authenticity of a piece.

[0004] Conventionally, labels are used for identification but have no functionality in connecting any object to a digital record or for determining authenticity of an object. Lack of authenticity is a centuries-old problem especially in the field of art and collectibles. Conventionally, there is no possibility of cataloging art and collectibles due to the absence of a global unique identification number in the field of art and collectibles, which ultimately results in an increase of forgeries and fakes. Further, the lack of trust in the process results in a restricted market in this field. Moreover, due to the lack of a consolidated platform, no price reference checks or comparisons can be made.

[0005] In managing objects in sectors such as collectibles, authenticity is of utmost importance. When authenticity is in question, whether due to counterfeit items or fraudulentclaims, it undermines the entire market ecosystem. To overcome the negative effects of a lack of authenticity, authentication steps must be emphasized upon.

[0006] Thus, a heretofore unaddressed need exists in the industry to address the aforementioned deficiencies and inadequacies.SUMMARY

[0007] This section is provided to introduce certain objects and aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.

[0008] It is an object of the present disclosure to provide a system and a method for inventory management and authentication of objects.

[0009] Another object of the present disclosure is to provide labels that are configured to establish a physical link between an object / artwork and its corresponding digital data.

[0010] Yet another object of the present disclosure is to substantially reduce counterfeiting in art, artwork, collectibles, and so on.

[0011] Yet another object of the present disclosure is to ensure guided labelling and digital verification of the objects / artworks.

[0012] Yet another object of the present disclosure is to provide a consolidated platform for price reference checks or comparisons for art pieces, collectibles, and antiques.

[0013] Yet another objective of the present disclosure is to provide a unique, non- counterfeitable, and tamper proof label.

[0014] Yet another objective of the present disclosure is to provide a label that is able to track and trace an object when it is attached to it through an online software to ensure that the object is the same over time and to record its existing location.

[0015] The present disclosure provides a unique combination of technology applications on labels that significantly enhances their effectiveness in authentication and anti-counterfeiting efforts. The present disclosure enables creation, management, tracking, and tracing of inventory and its authentication. The present disclosure provides a system that integrates physical labels with the accompanying digital software systems to digitally interface the label with the artwork, facilitating the tracing and tracking of the object / artwork. The unique labels ensure authenticity and traceability of the artwork. Each label is non-counterfeitable and possesses special forensic features to prevent replication.

[0016] The present disclosure enables comprehensive inventory management, authentication, tracking, tracing, and provenance verification of art and collectibles by assigning a unique number or ID to each individual object.

[0017] In one aspect of the present disclosure, a system for inventory management and object authentication may include one or more user devices configured to receive one or more input data provided by the user. The input data may include user data and label requests, one or more data repositories and a server configured to receive the input data from the user device, register new user by storing in the data repository and authenticate existing users, receive label requests from the user device, route label requests to at least one designated region based on the label request, schedule appointment with field agents, authenticators and conservators, generate one or more labels with code, dispatch the generated label to the at least one designated region and monitor and track usage of the label.

[0018] In an embodiment of the present disclosure, the server may be configured to receive input data from the at least one user device, register users by storing user data of new users in the data repository authenticate users by comparing received user data with stored user data and store the label requests, the appointment timestamp and the designated regions in the data repository.

[0019] In an embodiment of the present disclosure, the label request may include label application requirements and acceptance to terms and conditions. The server may be configured to route label requests to at least one designated region based on the label application requirements.

[0020] In accordance with a preferred embodiment of the present disclosure, the system includes two main types of labels, comprising but not limited to inventory labels and authenticity labels.

[0021] In an embodiment of the present disclosure, the server may be configured to schedule field agent appointments based on the designated region, deploy one or more field agents for field agent appointments, schedule appointment of field agents, authenticators and conservators, wherein the authenticators authenticate provenance of the object, the conservators inspect the object and field agents apply label on the object, dispatch the generated label through one or more field agents to the one or more designated regions and generate and store dossiers and appointment timestamps.

[0022] In an embodiment of the present disclosure, the generated code is a QR code that is scanned for logging into the system.

[0023] In another aspect of the present disclosure, a method for inventory management and object authentication by a system is provided. The system may include one or more user devices, a server and a data repository. The method may include receiving the input data from the users by the user devices, wherein the input data includes user data and label requests, registering new user by storing in a data repository and authenticating existing users by the server, receiving label requests from the user device by the server, routing label requests to at least one designated region based on the label request by the server, scheduling appointment with field agents, authenticators and conservators, generating one or more labels with code by the server, dispatching the generated label to the at least one designated region by the server by the server and monitoring and tracking usage of the label by the server.

[0024] In accordance with a preferred embodiment of the present disclosure, the inventory labels are configured for documentation and inventory purposes, featuring a curved edge on the left corners. These labels do not validate authenticity but are crucial for tracking and managing inventory.According to a preferred embodiment, authenticity labels comprise a complete pair of two unique labels used to authenticate an object or artwork. The authenticity labels feature a curved edge on the right comers and serve as visual identifiers of authenticity in an embodiment.BRIEF DESCRIPTION OF ACCOMPANYING DRAWINGS

[0025] The figures mentioned in this section are intended to disclose exemplary embodiments of the claimed system and method. Further, the components / modules and steps of a process are assigned reference numerals that are used throughout the description to indicate the respective components and steps. Other objects, features, and advantages of the present invention will be apparent from the following description when read with reference to the accompanying drawings:

[0026] Figure 1 illustrates a block diagram of a system for inventory management and object authentication, in accordance with an embodiment of the present disclosure.

[0027] Figure 2 illustrates a flowchart of the method for inventory management and object authentication, in accordance with an embodiment of the present disclosure.

[0028] Figure 3 illustrates a method for inventory management and object authentication depicting the steps of code generation, branch distribution and label application in accordance with an embodiment of the present disclosure.

[0029] Figure 4 illustrates a method for inventory management and object authentication depicting the steps of code generation, label printing, label distribution, label deployment and label monitoring, in accordance with another embodiment of the present disclosure.

[0030] Figure 5 illustrates a method for inventory management and object authentication depicting the steps from code generation to field deployment and monitoring, in accordance with another embodiment of the present disclosure.

[0031] Figure 6 illustrates a method for inventory management and object authentication depicting the steps from user registration to label application, in accordance with another embodiment of the present disclosure.

[0032] The foregoing shall be more apparent from the following more detailed description of the invention.DETAILED DESCRIPTION

[0033] The following presents a detailed description of various embodiments of the present disclosure with reference to the accompanying drawings.

[0034] The embodiments of the present disclosure are described in detail with reference to the accompanying drawings. However, the present disclosure is not limited to these embodiments, which are only provided to explain more clearly the present invention to a person skilled in the art of the present disclosure. In the accompanying drawings, like reference numerals are used to indicate like components.

[0035] The specification may refer to “an”, “one”, “different”, or “some” embodiment s) in several locations. This does not necessarily imply that each such reference is to the same embodiment(s), or that the feature only applies to a single embodiment. Single features of different embodiments may also be combined to provide other embodiments.

[0036] As used herein, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless expressly stated otherwise. It will be further understood that the terms “includes”, “comprises”, “including” and / or “comprising” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. It will be understood that when an element is referred to as being “attached” or “connected” or “coupled” or “mounted” to another element, it can be directly attached or connected or coupled to the otherelement, or intervening elements may be present. As used herein, the term “and / or” includes any and all combinations and arrangements of one or more of the associated listed items.

[0037] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this invention pertains. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0038] In the following description, for the purposes of explanation, numerous specific details have been set forth in order to provide a description of the invention. It will be apparent, however, that the invention may be practiced without these specific details and features.

[0039] The figures accompanying the specification depict a simplified structure only showing some elements and functional entities, all being logical units whose implementation may differ from what is shown.

[0040] Conventionally, labels identify objects such as art and collectibles, but neither link them to digital records nor verify the authenticity of the objects. The lack of a global identification system results in the proliferation of forgeries, reducing trust and limiting the growth and organization of the market. Additionally, due to the lack of proper tools for managing inventory, tracking and verifying provenance, it is difficult to manage, authenticate or trace objects through their lifetime, leading to confusion and inefficiency.

[0041] The present disclosure addresses the limitations of the prior art by providing a unique system 100 for inventory management and authentication of objects using unique, non- counterfeitable and tamper proof labels that physically link an object / artwork to the digital data.

[0042] The system 100 includes multiple user devices 120a-nthat receive the input data provided by the users. The input data may include user data and label requests.

[0043] The system 100 includes a server 140 that receives the user data of a new user, and stores it in a data repository 160. If the user is an existing user, the server 140 authenticates an existing user by comparing with the user credentials already stored in the server 140. After the server 140 registers a new user, the user signs up on the portal of the user device 120a-nand uploads the image of the artwork along with artwork details that may include providing detailed information about each artwork, including, but not limited to, title, artist details, dimensions, and images. The image of the artwork is stored in the data repository 160.

[0044] The server 140 is configured to receive label requests initiated by users through user devices 120a-n. Each label request submitted by the user contains two primary components, the label application requirements and the user's acceptance of the applicable terms and conditions. The label application requirements refer to the specific parameters or technical specifications that the label must fulfill in order to be compatible with a particular artwork or use case

[0045] The system 100 include physical labels and an accompanying digital software system. Including these details in the label request enables the system to generate a label that is properly tailored to digitally interact with the intended artwork.

[0046] The labels are designed to physically link objects or artworks to their corresponding digital data, ensuring authenticity and traceability. Each label is unique, non-counterfeitable, and possesses special forensic features to prevent replication.

[0047] The system includes two main types of labels, inventory labels and authenticity labels. Inventory labels are used for documentation and inventory purposes, characterized by a curved edge on the left corners. These labels are crucial for tracking and managing the inventory of the objects. On the other hand, authenticity labels, include a pair of two unique labels used to authenticate an object or artwork. The authenticity labels characterize a curved edge on the right comers and serve as visual identifiers of authenticity.

[0048] The labels are designed for strong adhesion to objects without causing damage and contain QR codes for easy access to corresponding digital information. However, they come with strict handling policies to prevent tampering or damage, ensuring the integrity of the system.

[0049] The server 140 routes the label requests to at least one designated region based on the label request, schedule appointment with field agents, authenticators and conservators, generate one or more labels with code, dispatch the generated label to a designated region or a city bucket, and monitor and track usage of the label. The generated code is scanned for logging into the system 100, wherein generated code is a QR code.

[0050] Appointments of field agents, authenticators and conservators are scheduled based on the designated region and one or more field agents are deployed for inspection. The authenticators authenticate provenance of the object, the conservators inspect the object and field agents apply label on the object, dispatch the generated label through field agents to the one or more designated regions and generate and store dossiers and appointment timestamps.

[0051] Figure 2 illustrates a method for inventory management and object authentication, in accordance with an embodiment of the present disclosure. The method 150 begins at a step 151 with by the user devices 120a-nreceiving the input data from the users, wherein the inputdata includes user data, object data and label requests. As a next step, at step 152, new user is registered by storing in a data repository 160 and authenticating existing users by the server 140. Following this, at a step 153, label requests are received from the user device 120a-n by the server 140. At a step 154, label requests are routed to at least one designated region based on the label request by the server 140. Following which, at a step 155, appointment is scheduled with field agents, authenticators and conservators. At a step 156, the server generates one or more labels are generated with code. Followed this, at a step 157, the server 140 dispatches the generated label to the at least one designated region. Following this, at a step 158 and monitoring and tracking usage of the label by the server 140.

[0052] The method for inventory management and authentication of objection according to the present involves several steps, encompassing both frontend and backend processes. These steps are designed to work in tandem to facilitate the management, tracking and authentication of objects within the system.

[0053] The present disclosure in an embodiment provides a frontend process. The first step in the front-end process comprises user registration and artwork upload. In user registration, users start by signing up on a portal, providing necessary details regarding user information. The registration process may include verification steps to ensure the authenticity of users. After registration, users can proceed to upload their artworks onto the collections management system. The upload process may involve providing detailed information about each artwork, including, but not limited to, title, artist details, dimensions, and images. The second step comprises providing label application requirements. In this step, users can apply for inventory labels, authenticity labels, or both by filling in the necessary information. The third step comprises agreement and request initiation. In the agreement and request initiation step, users accept terms and conditions and proceed to place a label request for their artworks. The fourth step comprises routing and scheduling. In this step, label requests are routed to respective city buckets, and appointments are scheduled for field agent deployment. The fifth step comprises field agent deployment and label application, in which field agents are dispatched to the client's location to apply labels to the artworks. The sixth step comprises online dossier generation, in which dossiers are generated online to document the label application process and capture artwork details.

[0054] The present disclosure in an embodiment provides the steps of backend process. The first step in the backend process comprises user registration and data management. In his step, the user data is securely captured and stored upon registration on the portal. The second step in the backend process comprises artwork upload and integration in which artwork data isintegrated into the collections management system and validated to meet system requirements. Further, the label request raised by the registered user is reviewed. The third step comprises label application requirements verification and provenance verification. The verification process ensures that users have filled all necessary information for label application and qualify for label requests. The provenance records submitted by the user for the object in question are reviewed and approved as part of the authentication process. As used herein, provenance is the chronology of the ownership, custody or location of a historical object, such as an artwork or collectible. Provenance may include, but is not limited to, details such as the origin of the object, records of previous ownership, transaction history, and any relevant certificates or documentation that help establish its authenticity and verify its chain of custody. These elements collectively provide a historical record that supports the legitimacy and value of the object. The fourth step comprises request initiation and communication step in which label request processes are triggered, and ongoing communication between users and the backend team is facilitated. At this step of inspection, the conservator / inspector will get in touch with the user to schedule an appointment for a physical visit to conduct site inspection and also inspect the object to ensure it is in good enough condition to apply labels. The fifth step comprises requesting routing and scheduling. In this step, label requests are routed to city buckets, and appointment scheduling is managed using dedicated applications. The sixth step comprises field agent deployment and task assignment in which field agents are assigned tasks and provided with necessary information for label application. It ensures the appropriate application of labels in various locations. The seventh step comprises online dossier generation and data recording in which online dossiers are generated and maintained, thereby recording data related to label requests and deployments. The final step of the backend process i.e., the eighth step includes label application and usage monitoring. In this final step, application process is monitored, and label usage is tracked, including records of used and unused labels.

[0055] Overall, the present disclosure integrates physical labels with a robust digital software system to ensure the authenticity and traceability of artworks, providing a comprehensive solution for art authentication and management.

[0056] Figure 3 illustrates a flowchart to illustrate a method 200a for inventory management and object authentication in accordance with an embodiment of the present disclosure. The order in which the blocks are described is not intended to be construed as a limitation, and some of the described blocks can be combined in any order to implement the method, or an alternative system. Additionally, some of the individual blocks may be deleted from method 200a without departing from the scope of the subject matter described herein.

[0057] The method 200a starts with code generation 10 in which the first step is to initiate 10-1 code generation. In an embodiment, the code may include a QR code. The first step 10-1 begins with a request to generate code. Following the initiation 10-1 of the code generation, the next steps in the code generation involve coordinating with security printers 10-2 to print the code. Thereafter, the label printing is managed by the system and packing into envelops 10-4 is supervised. The method 200a then proceeds to implement inventory management 10-5 and handling shipment to headquarters 10-6. At the last step of handling shipment to headquarters 10-6, labeled materials are shipped safely and efficiently to headquarters.

[0058] After the code generation 10, the method proceeds to the branch distribution 20 in which the first step is to coordinate branch office distribution 20-1. This step 20-1 ensures efficiently managing the distribution of printed labels to various branch offices. Thereafter, responsibilities to each branch office are allocated 20-2. After allocating responsibilities to branch offices, field agent distribution is facilitated 20-3 followed by dispatching 20-4 of field agents to distribute labeled materials to various locations.

[0059] Now, in block label application 30, the first step is to provide information on label applications 30-1. In the step 30-2, label application is monitored by the system and finally one or more systems are established for tracking label usage.

[0060] Figure 4 illustrates a flowchart to illustrate a method for inventory management and authentication of objects in accordance with an alternate embodiment of the present disclosure. The order in which the blocks are described is not included to be construed as a limitation, and some of the described blocks can be combined in any order to implement the method 200b, or an alternative system. Additionally, some of the individual blocks may be deleted from method 200b without departing from the scope of the subject matter described herein.

[0061] The method 200b starts with code generation 40 in which the first step is to initiate 40-1 code generation. The next steps include generation 40-2 of batch of codes and transmitting the codes to security printers 40-3 for printing. With steps 40-1 to 40-3, the present invention ensures that codes are smoothly and efficiently transmitted to a security printer and printed labels that meet the users’ specifications and requirements are produced.

[0062] Thereafter, the labels are printed in block label printing 50 and then are packed into envelopes 50-2. Further, at block label distribution 60, the first step is to assign unique identifiers 60-1 to the labels. In an embodiment, the unique identifiers 60-1 may include unique IDs, unique numbers etc. In a preferred embodiment, the unique identifier can be a QR code that can be scanned and logged into the inventory management system when the label is applied to an object. QR codes, short for Quick Response codes, are two-dimensional barcodes thatstore information in a pattern of black squares arranged on a white background. QR codes are generally used as a convenient way to link physical objects, such as products, packaging etc., to digital content, such as websites, videos etc. By scanning a QR code, users can access additional information related to the product.

[0063] After assigning the unique identifiers to the labels they are segregated into different batches as per different branch offices and these batches are transported to the headquarters 60- 2. The next step is to distribute batches to branch offices 60-3. In this step upon arrival at headquarters, batches are sorted based on their destination branch offices, and it is ensured that each batch is clearly labeled with the branch office it is intended for. Thereafter, the envelopes are prepared 60-4 for deployment. Details regarding the batches are per different branch offices are mentioned in the envelope and accordingly in step 60-5 these envelopes are distributed to filed agents.

[0064] Further, in block for label deployment 70, the first step is to dispatch field agents 70-1. These field agents are tasked with applying labels on art and collectibles. The next step is to deploy labels 70-2 and apply labels to art and collectibles 70-3. Field agents can effectively apply labels on art and collectibles while ensuring that the items are accurately identified.

[0065] Further, in block label monitoring 80 the steps are to monitor label usage 80-1 and record label usage 80-2. In the step of monitor label usage 80-1, the inventory management system is employed that tracks the usage and monitoring of labels. Furthermore, recording label usage involves systematically documenting each instance of usage of the label.

[0066] Figure 5 illustrates a method for inventory management and object authentication depicting the steps from code generation to field deployment and monitoring in accordance with another embodiment of the present disclosure. The order in which the blocks are described is not included to be construed as a limitation, and some of the described blocks can be combined in any order to implement the method 300, or an alternative system. Additionally, some of the individual blocks may be deleted from method 300 without departing from the scope of the subject matter described herein.

[0067] As shown in Figure 5, the method 300 comprises two processes i.e., a frontend process 200a and a backend process 120. In the frontend process 200a, the first step is code generation and printing 200a-l. In the step of code generation and printing 200a-l, batch of codes are generated using proprietary unique taxonomy to create labels with unique identifying numbers. Further, the generated codes are transmitted to the security printers for label production. The method then proceeds to the next step of label packaging and inventory 200a-2. In this step, each label is cautiously packed into individual envelopes on site at the securityprinters where the labels were printed. The individual envelopes containing the printed labels are subject to individual inventory management and are each assigned unique identifying numbers. At the next step of shipment to headquarters 200a-3, sealed envelopes with assigned unique identifying numbers are packaged into batches of 200a in an embodiment. Such batches are then packed into boxes, wherein each box contains approximately 20 batches, totaling 2000 envelopes per box. These batches are transported to the headquarters for further processing. The next step is distribution to branch offices 200a-4. In this step, the batches of envelopes after arriving at headquarters are ingested into ERP system, and then are allocated to various branch offices through the ERP system to be shipped at the respective branch offices. Once such batches of envelopes reach the allocated branch offices, at the next step of branch office handling 200a-5, the head of each branch office takes charge of the envelopes, scans them into the ERP system and creates a GRN. The head of the branch office then allocates the envelopes among the regional field agents as per requests raised by the field agents on the ERP against the label requests raised by clients. Further, at step field agent deployment 200a-6, field agents equipped with the envelopes, are dispatched to the client's location or artwork site. The primary task of the field agents is to deploy and adhere the labels to the appropriate objects or artworks. At the last step of label application and monitoring 200a-7, the field agents cautiously apply the labels as required and monitor the usage of labels, keep a tally of both used and unused ones through ERP system and update the label information on the ERP system. The frontend process 200a is replicated on the backend to track the entire process from code generation to deployment in the field.

[0068] Now, in the backend process 120, the first step is code generation and printing 120- 1. In the step of code generation and printing 120-1, the code generation process is initiated using taxonomy for unique label identification and coordination is done with the security printers to produce labels from generated codes. After the labels are produced at the security printers in the next step of label packaging and inventory control 102-2, batch details are provided which are entered into the ERP system. After the batch details are entered, the inventory management is implemented for individual label envelopes and their unique identifiers. At the next step of shipment and batch handling 102-3, the packed envelopes are shipped to the headquarters in boxes of 200b0 where the packed envelopes are scanned and the details of the packed envelopes are entered in the ERP system. The ERP system verifies the packed envelopes against the batch details provided by the secure printers before shipment. Further at the next step of branch office distribution coordination 120-4, headquarter allocates envelopes to each branch office according to the specific requirements of the branch officesand requests through the ERP system. The headquarter also organizes the distribution of batches to various branch offices and oversees their shipment. This step ensures prompt and accurate delivery to branch locations. After the batches of envelopes are delivered to the branch offices, in the next step of branch office handling and field agent assignment 120-5, the head of each branch office that receives the shipment, enters the inventory into the ERP system, and verifies the inventory against the allocated inventory. The head of each branch also facilitates distribution of envelopes to regional field agents through the ERP system. Further, at the next step field agent deployment and task assignment 120-6, field agents are dispatched to client locations or artwork sites and are provided with necessary information about specific label applications. At the final step i.e., label application and usage monitoring 120-7, the label application process carried out by field agents is monitored, label usage, including records of used and unused labels are tracked using the ERP system and information of the used labels on the ERP system is updated.

[0069] Figure 6 illustrates a method for inventory management and object authentication depicting the steps from user registration to label application in accordance with another embodiment of the present disclosure. The order in which the blocks are described is not included to be construed as a limitation, and some of the described blocks can be combined in any order to implement the method 400, or an alternative system. Additionally, some of the individual blocks may be deleted from method 400 without departing from the scope of the subject matter described herein.

[0070] The method 400 contains two processes i.e., a frontend process 140 and a backend process 160. In the frontend process 140, the first step is registration and Initial Steps 140-1. This step includes signing up by the user and uploading of artworks on the collections management system. In the next step of completing label application requirements 140-2, users fill in all necessary information to apply for either the inventory label or the authenticity label, or both, qualifying for label request. Further, in step 140-2, users can choose to request either of the two labels and users are required to fulfil all the field requirements stipulated in the CMS system for the corresponding artworks they have requested labels for. After the user has filled in all the required details, in the next step of agreement and request initiation 140-3, users are required to accept the terms and conditions of the agreement and place a label request for individual or multiple objects / artworks. The label request will be sent to the relationship manager / assigned agent, who will be in communication with the user from the moment the request is raised and reflected in the ERP system. Once the label request is sent to the relationship manager / assigned agent, at the next step routing and scheduling 140-4, the requestlands in respective buckets designated by cities / location in ERP system. After the request is landed in respective buckets, the authenticator will verify the provenance information provided by the user. Once confirmed as correct, the authenticator will process the request for the next step of inspection through the ERP system and an appointment is scheduled by the conservator. At the next step of field agent deployment and artwork labelling 140-4, at least two field agents along with a conservator are deployed to visit the site / location to identify the artwork requested for labelling, label the artwork, and make any edits to the information of the corresponding artwork, if required. The final step is online dossier generation 140-5 in which an online dossier is generated for all the information collected by the agents.

[0071] Now, in the backend process 160 the first step is user registration and data management 160-1. In this step when a user is registered on the portal, user data is safely collected and stored securely on the ERP system. The stored user data is managed for label application which ensures user qualification and preferences. Further at the next step request raised by user for labels 160-2, the ERP will reflect the label requests generated by the user from the frontend and will route label requests to the respective branch office buckets designated by cities / locations. The branch head has the option to assign the request to an authenticator to initiate the process, or the authenticator can independently allocate the request to themselves through the ERP system. Further at the step provenance verification 160-3, the provenance provided by the user will be verified and approved by the authenticator. After provenance verification 160-3, a conservator will schedule a site visit with the user and update the date and time manually in the ERP at the step of inspection visit scheduling 160-4. In the next step of inspection visit 160-5, at least two field agents, along with one conservator are assigned tasks for each label request. It is ensured that the field agents receive information about the client's site / location and artwork details and at last all objects and site observations are updated in the ERP system by the conservator. After inspection visit 160-5, the field agents schedule visit to the client’s site / location for the application of the artwork at the step of schedule visit for label application 160-6 and the date and time is manually entered into the ERP system by the assigned field agents. After a visit has been scheduled, the field agents will initiate the labelling process onsite and diligently update all essential information within the ERP system, adhering to the established due process at step field agent visit and label application 160-7. Once the labelling process has been completed, online dossiers are generated and maintained for each label request on the ERP system at step online dossier generation and data recording 160-8. In this step, the data related to label requests and deployments are also recorded and managed. At the last step of the backend process, i.e., label application andmonitoring 160-9, label application process of the field agents is monitored through the ERP and label usage is tracked through the ERP, including both used and unused labels.

[0072] According to the present disclosure, each label is provided with special forensic features and hidden identifiers that cannot be replicated and contain hidden identifiers. These features can vary depending on the intended use and level of security required, in an embodiment, these features include but are not limited to unique codes, unique dye, hologram, tamper proof, adhesive and hologram.

[0073] While the preferred embodiments of the present disclosure have been described hereinabove, it should be understood that various changes, adaptations, and modifications may be made therein without departing from the spirit of the invention and the scope of the appended claims. It will be obvious to a person skilled in the art that the present invention may be embodied in other specific forms without departing from its spirit or essential characteristics. The described embodiments are to be considered in all respects only as illustrative and not restrictive.

Claims

WE CLAIM1. A system (100) for inventory management and object authentication, comprises: one or more user devices ( 120a-n) configured to receive one or more input data provided by the user, wherein the input data comprises user data, object data and label requests; one or more data repositories (160); a server (140) configured to: receive the input data from the user device ( 120a-n); register new user by storing in the data repository (160) and authenticate existing users; receive label requests from the user device ( 120a-n); route label requests to at least one designated region based on the label request; schedule appointment with field agents, authenticators and conservators; generate one or more labels with code; dispatch the generated label to the at least one designated region; and monitor and track usage of the label.

2. The system (100) for inventory management and object authentication as claimed in claim 1, wherein the server (140) is configured to: receive input data from the at least one user device ( 120a-n); register users by storing user data of new users in the data repository (160); authenticate users by comparing received user data with stored user data; and store the label requests, the appointment timestamp and the designated regions in the data repository (160).

3. The system (100) for inventory management and object authentication as claimed in claim 1, wherein the label request includes label application requirements and acceptance to terms and conditions; wherein the server is configured to route label requests to at least one designated region based on the label application requirements;4. The system (100) for inventory management and object authentication as claimed in claim 1, wherein the server (140) is configured to: schedule appointment of field agents, authenticators and conservators based on the designated region; deploy one or more field agents for field agent appointments; wherein the authenticators authenticate provenance of the object, the conservators inspect the object and field agents apply label on the object; dispatch the generated label through one or more field agents to the one or more designated regions; and generate and store dossiers and appointment timestamps.

5. The system (100) for inventory management and object authentication as claimed in claim 1, wherein generated code is scanned for logging into the system (100); wherein generated code is a QR code.

6. A method (150) for inventory management and object authentication by a system (100), the system (100) comprising one or more user devices ( 120a-n), a server (140) and a data repository (160), the method (200) comprising: receiving the input data from the users by the user devices ( 120a-n), wherein the input data comprises user data, object data and label requests; registering new user by storing in a data repository (160) and authenticating existing users by the server (140); receiving label requests from the user device (120a.n) by the server (140); routing label requests to at least one designated region based on the label request by the server (140); scheduling appointment with field agents, authenticators and conservators; generating one or more labels with code by the server (140); dispatching the generated label to the at least one designated region by the server (140); and monitoring and tracking usage of the label by the server (140).

7. The method (200) for inventory management and object authentication as claimed in claim 6, wherein the server (140) is configured to: receive input data from the at least one user device ( 120a-n); register users by storing user data of new users, in the data repository (160); authenticate users by comparing received user data with stored user data; andstore the label requests, the appointment timestamp and the designated regions in the data repository (160).

8. The method (200) for inventory management and object authentication as claimed in claim 6, wherein the label request includes label application requirements and acceptance to terms and conditions; wherein the server is configured to route label requests to at least one designated region based on the label application requirements.

9. The method (200) for inventory management and object authentication as claimed in claim 6, wherein the server (140) is configured to: schedule field agent appointments based on the designated region; deploy one or more field agents for field agent appointments; schedule appointment of field agents, authenticators and conservators, wherein the authenticators authenticate the provenance of the object, the conservators inspect the object and field agents apply label on the object; dispatch the generated label through one or more field agents to the one or more designated regions; generate and store dossiers and timestamps of visit.

10. The method (200) for inventory management and object authentication as claimed in claim 6, wherein generated code is scanned for logging into the system (100); and wherein generated code is a QR code.

Images