Product state management support system using unique id

Abstract

To provide a system for a user to easily manage the product state of products stored at home.SOLUTION: A product state management support system includes as a system configuration: a) unique ID storage means for storing a unique ID, which individually identifies a product, attached to the product; b) pack ID storage means for storing a pack ID that identifies a pack attached to the pack of the product; c) a product database; d) registration request means for sending acquisition information including the pack ID of the pack related to a user's acquisition; e) linking registration means for linking and registering an application ID with product data whose item value is the pack ID; and f) notification means for monitoring a product state and giving a notification.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a product status management system, and more particularly to a system that monitors the expiration dates of products purchased by users and assists in managing the products so that the product status is maintained in an appropriate state. Here, the term "product status" refers to the status of the stored product, such as the product expiration date, the remaining period until the product expiration date, consumption, and the actual usable quantity stored. The term product expiration date is used as a term indicating the date set for a product such as a disaster prevention product, and indicates the final year, month, date, etc. until which the product can be used, consumed, or best-before, or the date when replacement is recommended due to the final year, month, date, etc. approaching its end. Expiration dates include expiration dates, best-before dates, and replacement dates, and provide information related to the safety and quality of products. Product expiration dates serve as a guide for using products appropriately, taking into account the storage conditions and usage methods of the product. [Background technology]

[0002] There is a problem with products stockpiled at home, where when the time comes to use them, the product's expiration date or best-before date has passed and it can no longer be used. In recent years, in response to the increasing frequency of natural disasters, there is a demand for local governments, companies, and even ordinary households to improve their stockpiles of disaster preparedness supplies. However, the disaster stockpiles of ordinary households are not in a secure state. It has been difficult for individuals and families to continue to maintain preparations for future unexpected disasters. Drinking water, food, hygiene products, medicines, first aid supplies, etc. are necessary to be stockpiled, but many of these products have long expiration dates, and if expiration date management is neglected, there are cases where the products will be expired and unusable when they are needed. This is a problem.

[0003] A system for preventing the above-mentioned cases of unusability is described in Patent Document 1. This document discloses a system including a product database that stores product information including an expiration date and user information in association with a unique ID given to a disaster prevention product, a replacement advance notice means that monitors the expiration date according to a predetermined monitoring schedule, determines whether or not it is time to replace the disaster prevention product, and transmits a replacement advance notice when it is determined that it is time to replace the disaster prevention product, a notice receiving means that automatically receives the replacement advance notice, a replacement command means that transmits an order request for the disaster prevention product related to the replacement advance notice, and a viewing means that connects the product information to the product database and views it, and a software program that is installed in a mobile terminal and cooperates with the mobile terminal to realize these. However, a mechanism must be in place that allows a user who acquires a disaster prevention product to read the unique ID assigned to the product, associate the read unique ID with a notification destination, and easily set the expiration date of the disaster prevention product.If a user tries to manage a product that does not have such a mechanism, there is a problem in that the user is required to perform cumbersome tasks related to setting product and user information. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent Publication No. 2021-43806 Summary of the Invention [Problem to be solved by the invention]

[0005] The problem to be solved by the present invention is to provide a system for easily managing the product status of products stored at home by users. The purpose of this system is to support the user in managing the product status without requiring the user to perform the complicated tasks of setting product information and user information. [Means for solving the problem]

[0006] According to a first aspect of the present invention, there is provided a product status management system including a mobile terminal of a user having a predetermined application installed thereon, a) a unique ID storage means for storing a unique ID attached to the product packaging or the product itself for individually identifying the product; b) a pack ID storage means for storing a pack ID for identifying a pack that is configured with one or more of the products and that is attached to the packaging of the pack or to the product itself; c) a product database storing product data including, as data items, a pack ID of a pack in which the product is included, a unique ID of the product, and a product expiration date of the product; d) a registration request means, which is realized by the application and the mobile terminal working together, for reading the pack ID from the ID storage means of the pack related to the user's acquisition and transmitting acquisition information including the pack ID; e) a linkage registration means for receiving the acquired information and registering a linkage between a notification destination related to the application and product data having the pack ID as an item value; f) a notification means for monitoring a product status including the product expiration date according to a predetermined monitoring schedule, and for notifying the notification destination registered in association with product data of a product that satisfies a preset notification criterion; The present invention provides a system including the above as a system configuration.

[0007] Here, the unique ID is an ID that individually identifies a product, and is used as a term indicating a code that is introduced to identify and specify a specific product among multiple products of the same type.

[0008] Here, the pack ID is used as a term representing identification information that identifies a pack in which a supply unit made up of one or more products is bundled into one package.

[0009] Here, the system configuration further comprises: g) a cancellation request means, which is realized by the application and the mobile terminal working together, for reading the unique ID of the product and transmitting a cancellation request including the unique ID; h) a deleting means for receiving the deleting request and deleting the product data of the product related to the unique ID; It may be stated as including.

[0010] Here, the notification destination may be an application ID that identifies a combination of the application related to the installation and the mobile terminal, and the notification may be a push notification with the application ID as the notification destination.

[0011] Here, the application ID is an identifier that uniquely identifies the combination of an application and a mobile device, which is generated with the user's approval in the notification settings when creating a user account after the user downloads an application to his or her mobile device from an application store, etc. The application ID is stored in the database of the application provider or in the user account management system. This application ID is stored as part of a header, query parameter, or authentication token that serves as authentication information for an access request to a destination in communication that the application executes in cooperation with a mobile device. Therefore, the user does not have to consciously enter the application ID when accessing the system, which is the application provider, for example, to transmit data from the application. For example, the application ID may be a push notification token of a push notification in the Apple Push Notification Service or ID information associated with the push notification token.

[0012] Push notifications are a mechanism for sending messages and information to users who have given their prior permission to use a mobile device that has the app installed, and can display messages in the notification area of ​​the mobile device even when the app is in the background. This eliminates the need for users to consciously launch the app to receive notifications in order to manage the status of their products.

[0013] Here, the pack ID storage means may be at least one code selected from a two-dimensional code and a one-dimensional barcode, and the attachment may be at least one code selected from a seal, a box, or a label printed with the code.

[0014] Here, the unique ID storage means may be at least one code selected from a two-dimensional code and a one-dimensional barcode, and the attachment may be at least one code selected from a seal, a box, or a label printed with the code.

[0015] Here, the pack ID storage means may be at least one code selected from a two-dimensional code and a one-dimensional bar code, and the attachment may be due to a bottleneck on which the code is printed.

[0016] Here, the unique ID storage means may be at least one code selected from a two-dimensional code and a one-dimensional barcode, and the attachment may be by a bottleneck on which the code is printed.

[0017] Here, the pack ID, the unique ID of the product, and the product expiry date of the product, which are included in the data items of the product data, may have their item values ​​registered in accordance with the attachment.

[0018] Here, the pack ID storage means may further store the unique ID and the product expiry date of the product included in the pack.

[0019] The product database may be provided in a memory of the mobile terminal.

[0020] Here, the unique ID storage means may be a wireless tag, and the reading may be achieved by cooperation between a wireless function of the mobile terminal and the application.

[0021] Here, the unique ID storage means may be a wireless tag, and the attachment may be a label incorporating the wireless tag or a hanging around the neck of a bottleneck incorporating the wireless tag.

[0022] Here, the pack ID storage means may be a wireless tag, and the reading may be achieved by cooperation between a wireless function of the mobile terminal and the application.

[0023] Here, the pack ID storage means may be a wireless tag, and the attachment may be a label incorporating the wireless tag or a hanging around a bottleneck incorporating the wireless tag.

[0024] Here, the pack may include sub-packs as its configuration. [Brief description of the drawings]

[0025] [Figure 1] FIG. 1 is an overall diagram showing, in chronological order, the process from shipment of a product whose expiration date is managed by the system of this embodiment to its sale and stockpiling through a physical store. [Diagram 2] FIG. 2 is an image diagram showing the details of the work carried out in the shipping work area. [Diagram 3] FIG. 3 shows details and variations of a product pack that a user acquires through a distribution process. [Figure 4] FIG. 4 is a perspective view showing a modified example of a product pack that a user acquires through a distribution process. [Diagram 5] FIG. 5 is an image diagram showing a product pack containing one product. [Figure 6] FIG. 6 is a functional block diagram showing the functional configuration of the product status management server. [Figure 7] FIG. 7 is a block diagram showing a functional configuration realized by a mobile terminal of a user on which the application of the present embodiment is installed, in cooperation with the application. [Figure 8]FIG. 8 is a sequence diagram showing the operation of the product status management system of this embodiment, divided into the user side and the system operator side. [Figure 9] FIG. 9 is a block diagram showing the data structure of the product data stored in the product database. [Figure 10] FIG. 10 shows a registration request application screen displayed on the mobile terminal by the operation of the registration request unit. [Figure 11] FIG. 11 is a conceptual diagram showing the association between the application ID of the notification destination and product data. [Figure 12] FIG. 12 is a diagram showing modified examples of the structure of product data to be registered and modified examples of linking in the product data of the structure. [Figure 13] FIG. 13 shows an application screen for a registration request displayed on a mobile terminal by the operation of the browsing request unit. [Figure 14] FIG. 14 is an example of a data viewing screen displayed on a user's mobile terminal. [Figure 15] FIG. 15 is an example of a reconciliation request screen displayed on the user's mobile terminal. [Figure 16] FIG. 16 shows an example of the notification information display screen. [Figure 17] FIG. 17 is an overall diagram showing the operations related to the distribution process and product status management when products managed by the system of this embodiment are sold online. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0026] The objective of supporting a user in managing the status of merchandise stored by the user without requiring the user to perform cumbersome tasks related to setting product information and user information is realized by providing a product status management system utilizing a mobile terminal on which a specified application is installed.

[0027] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, specific examples of the present invention will be described with reference to the accompanying drawings. In the embodiments, each functional component that realizes the functions of the present invention is realized by executing a control program such as pre-installed firmware or an application stored in a storage device on a processor such as a mobile terminal, computer, circuit, etc. EXAMPLES

[0028] FIG. 1 is an overall diagram showing, in chronological order, the process from shipment of a product whose expiration date is managed by the system of this embodiment to its sale and stockpiling through a physical store. A product status management server 1001 provided in a communication network 1000 is communicatively connected to a product registration computer 1007 in a shipping work area 1002 and a user's mobile terminal 1013 .

[0029] In the shipping work area 1002, a label printer 1005 outputs a unique ID storing two-dimensional code label printed with a two-dimensional code storing a unique ID, a pack ID storing two-dimensional code label printed with a two-dimensional code storing the pack ID of the pack, and a lower pack ID storing two-dimensional code label printed with a two-dimensional code storing the pack ID of a lower pack. A worker 1004 picks multiple products from a product shelf 1003, and the multiple products with unique ID storing two-dimensional code labels attached are packed into an empty lower pack. A lower pack ID storing two-dimensional code label is affixed to the lower pack, which is then packed into another pack to complete the product pack. A pack ID storing two-dimensional code label is affixed to the pack into which the lower pack is to be placed. 1006 shows a product pack in the packing process. For each product, the unique ID, pack ID, product expiration date, and the lower pack ID of the lower pack in the case where the product is packed in a nested pack structure are entered into a shipping registration computer 1007 located in the shipping work area in accordance with the above-mentioned affixing, and transmitted to a product status management server 1001 on a communication network 1000, where product data of the products included in the product pack and product data including the lower pack ID in the case of a nested structure are registered. Here, the pack ID is used as a term representing identification information that identifies a "product pack" in which one or more units of a product are bundled together in one package.

[0030] A registered product pack 1009 delivered to and displayed at a store 1008 is purchased by a user 1010 and stored in the user's home 1011 . The pack ID of the stockpiled product pack 1012 is read by the mobile terminal 1013 carried by the user 1010, and is transmitted to the product status management server together with authentication information for a product status management application (hereinafter referred to as this application or simply "application") installed on the mobile terminal, and the notification destination related to this application is linked to the product data of the products that make up the product pack and registered. To distinguish it from the product registration explained above, it will be referred to as "linked registration" in the following description. Below, we will explain the configuration when push notifications are approved and the app ID is used as the notification destination. However, if push notifications are not approved, notifications will be sent by sending a notification email or a short message to a phone number instead of a push notification.

[0031] Here, different symbols are used to distinguish between product packs being packed and labeled in the shipping area, product packs on display in stores, and product packs stored in homes, but the same items move chronologically through the distribution process. Furthermore, the term "user" is used to refer to a user who uses this system to maintain the condition of products stored in their own home, office, or other storage locations.

[0032] FIG. 2 is an image diagram showing the details of the work in the shipping work area 1002. Product A 2001, product B 2002, and product C 2003 are picked by a worker 1004 from a product shelf 1003. Products A and B are affixed with a unique ID storing two-dimensional code label 2005 on which a two-dimensional code storing a unique ID output by a label printer 1005 is printed, and packed in a lower pack packaging material 2004. A lower pack ID storing two-dimensional code label 2006 on which a two-dimensional code storing a lower pack ID is printed is affixed to the lower pack packaging material after packaging is completed, and a lower pack is completed. The lower pack and product C are packed in a pack packaging material 2008 on which a pack ID storing two-dimensional code label 2007 on which a two-dimensional code storing a pack ID is printed is affixed, and a product pack is formed.

[0033] Here, the storage information stored in the pack ID storage two-dimensional code is the pack ID only, but the storage information that can be adopted in the present invention is not limited to this, and the storage information may also include product information selected from a unique ID that identifies each packaged product, product display information, an item ID that identifies the item, and a product expiration date in addition to the pack ID. With this configuration, the user's mobile device and the app work together to read the two-dimensional code that stores the pack ID, and the product information related to the readout is registered in a local product database in the mobile device as a standalone, making it possible to manage the product status without a network connection. As a result, even if a network failure occurs during a disaster, it is possible to view the product status of stockpiled products and perform a certain level of product status management.

[0034] The worker 1004 transmits product data for the picked product from a business tablet 2008 or business computer 1007 to a product status management server 1001, the product data including pack hierarchical information such as the unique ID of the packed product, the product expiration date, the pack ID related to the packing, and the lower pack ID if a lower pack exists. The product status management server additionally registers the received product data in a product database, which will be described later. Product data is registered in correspondence with the affixing of the unique ID storing two-dimensional code label, the pack ID storing two-dimensional code label, and the lower pack ID storing two-dimensional code label, which are associated with this packing. This registration is called product registration to distinguish it from the linking registration, which will be described later.

[0035] FIG. 3 shows details of the product pack that the user acquires through the above-mentioned distribution process, as well as variations thereof. Reference numeral 3000 indicates a subpack of the product pack in Fig. 2 and a primary product, product C, directly contained therein. Product A 3003 and product B 3004 are contained in a package 3001 to which a two-dimensional code label 3002 is attached, on which a two-dimensional code is printed and in which the subpack ID of the subpack is stored. Here, a two-dimensional code is used as the pack ID storage means for storing the pack ID, but the code storage means that can be used in the present invention is not limited to this. Other types of ID storage means, such as one-dimensional barcodes and wireless tags, can be appropriately used as long as they can be read using the functions provided in the mobile terminal.

[0036] For both product A3003 and product B3004, which are secondary products when viewed from the higher-level pack, and product C3005, which is a primary product, item IDs 3006, 3007, 3008 that identify the type of product and their product expiration dates 3009, 3010, 3011 are written as one-dimensional barcodes, symbols, letters, etc., and can be read by an operator using a scanner installed on the business tablet 2007 or business computer 1007 as necessary.

[0037] Item ID is used as a term to represent identification information that identifies a product category. Product codes such as JAN code (Japanese Article Number) and EAN (European Article Numbering), which is an international standard, can be used as item IDs. Identification information that identifies a product category newly created for this system may also be used as item IDs. Here, the JAN code is used as the item ID. The system searches existing product master data using this item ID as a key, making it possible to use product information such as the product name, product category, and brand that represent the product item.

[0038] Unique ID storing two-dimensional code labels 3012, 3013, and 3014, on which a two-dimensional code storing a unique ID is printed, are attached to product A3003, product B3004, and product C3005.

[0039] Reference numeral 3015 denotes a modified product pack that employs a two-dimensional code sealing label 3016 on which a two-dimensional code storing a pack ID is printed on the seal of the pack. By combining the work of sealing the pack with the work of attaching the pack ID storage means, this has the effect of increasing work efficiency.

[0040] Reference numeral 3017 denotes a modified product pack that employs a two-dimensional code sealing tape 3016 on which a two-dimensional code storing a pack ID is printed on the seal of the pack. This can be employed not only for the lower-level packs shown here, but also for higher-level packs, and has the effect of increasing work efficiency by combining the work of sealing the package with the work of attaching the pack ID storage means.

[0041] Here, three products are configured as a product pack and are provided to the purchasing user, but the packaging form, type of item, combination and quantity of different items of products that can be used as a unit of provision in this invention are not limited to this and can be changed as appropriate.

[0042] FIG. 4 is a perspective view showing a modified example of a product pack that a user acquires through the above-mentioned distribution process. Here, a product 4001, on which an item ID 4002 and a product expiration date 4003 are written using a one-dimensional barcode, symbol, character, or the like, is stored in a box 4004 for packaging. A two-dimensional code 4005 storing the product's unique ID is printed on the box 4004.

[0043] The product packed in the box 4004 is packed in a back packaging material 4007 on which a two-dimensional code 4008 storing a pack ID is printed, thereby forming a product pack. Here, two products are configured as a product pack and are provided to the purchasing user, but the packaging form of the products that can be used as a unit of provision in this invention, the presence or absence of sub-packs, the type of item, the combination and quantity of different items can be changed as appropriate without being limited to this.

[0044] FIG. 5 is an image diagram showing a product pack in which one product is provided as a unit. An unpackaged product 5001 has an item ID 5002 and a product expiration date 5003 written thereon by a one-dimensional barcode, symbol, character, or the like, and has a bottleneck 5004 attached. A two-dimensional code 5005 storing a pack ID and a two-dimensional code 5006 storing a unique ID are printed on the bottleneck.

[0045] Here, two two-dimensional codes are printed on one bottleneck, however, the bottleneck attachment that can be used in the present invention is not limited to this and can be modified as appropriate, such as attaching one of the two-dimensional codes to the bottleneck and attaching the other two-dimensional code in some other way, such as by sticking a label on it, or attaching two bottlenecks and printing a two-dimensional code storing a unique ID on one and printing a two-dimensional code storing a pack ID on the other.

[0046] FIG. 6 is a functional block diagram showing the functional configuration of the product status management server 1001. It comprises the following functional components: an application verification unit 6001 , a product registration unit 6002 , a linking registration unit 6003 , a product data monitoring unit 6004 , a notification generation unit 6005 , a notification distribution unit 6006 , a product data browsing support unit 6007 , a settlement unit 6008 , a product master 6009 and a product database 6010 .

[0047] When an access is made from an application of the user's mobile terminal 1013, the application verification unit 6001 verifies authentication information included in the request, and verifies whether the access is from a legitimate application.

[0048] The product registration unit 6002 registers in the product database 3009 product data, which is composed of a unique ID, pack ID, item ID, and product expiration date, for products that have been picked and packaged for shipping.

[0049] The association registration unit 6003 extracts a pack ID from a registration request received from an application verified as a legitimate application, and performs association registration between the pack ID related to this registration request and the application ID that is the notification destination related to the verified application. When requesting registration, the user who operates the mobile device on which the application is installed does not have to go through the trouble of consciously setting the application ID. All the user has to do is launch the application, read and send the ID.

[0050] The product data monitoring unit 6004 determines whether or not a product is subject to notification based on whether or not the product status of the product registered in the product database at the monitoring timing of a specified monitoring cycle meets the notification criteria previously set for each item at that timing. Here, the notification criterion is set to a state in which the remaining time until the product expiration date at the monitoring timing falls below a preset reference value, and products that have a product expiration date that indicates a remaining time value that falls below the reference value as their item value are determined to be products to be notified.

[0051] The notification generating unit 6005 generates notification information for a product that meets the notification criteria, with the application ID linked to the product data as the notification destination.

[0052] The notification delivery unit 6006 pushes the notification information to a mobile terminal on which the notification destination application is installed. Push notifications can be sent to apps using the functionality provided by the mobile device platform, even when the app is not running. This has the effect of freeing users from the hassle of having to consciously launch an app to monitor product data.

[0053] The product data viewing support unit 6007 extracts product data in response to a viewing request related to access from an app on the user's mobile device, generates viewing information display data in a specified format, and sends it to the app on the mobile device related to the viewing request. If the request includes a pack ID or a unique ID, product data having the pack ID or the unique ID as the item value of the data item is extracted, viewing information is generated, and the viewing information is sent to the application having the application ID that is the notification destination. If the request does not include a pack ID or a unique ID, product data having the application ID of the application related to the request as the item value of the data item is extracted, viewing information is generated, and the viewing information is sent to the application having the application ID that is the notification destination.

[0054] In response to a cancellation request including information to be cancelled from an application on a user's mobile terminal, the canceling unit 6008 cancels the product data corresponding to the information to be cancelled from the product database.

[0055] The product master 6009 is an existing database that can call up product information such as the product name, product category, and brand that represent the product item by searching using the item ID as a key.

[0056] The product database 6010 stores product data of products related to a product pack. The user information database 6011 stores user information related to a user account that is created when an application is first started after installation, which will be described later. The user account creation unit 6012 receives user information input via a user information input screen presented by the application at the time of initial startup from the application, creates a user account, and stores it in a user information database. Furthermore, the application ID is registered as a notification destination related to the user account created upon receiving approval of the push notification.

[0057] (User's mobile device) FIG. 7 is a block diagram showing a functional configuration realized by a mobile terminal 1013 of a user on which the application of this embodiment is installed, in cooperation with the application. The functional configuration includes a registration request unit 7001 , a view request unit 7002 , a deletion request unit 7003 , a notification view unit 7004 , and a local product database 7005 .

[0058] The registration request unit 7001 transmits a registration request to the product status management server 1001, the registration request including the pack ID acquired in response to operation by the user of the scanner launched from the registration request screen of the app of this embodiment launched on the user's mobile terminal 1013.

[0059] The data viewing unit 7002 receives a viewing request operation on the viewing request screen of the app of this embodiment launched on the user's mobile terminal 1013, sends a viewing request to the product status management server 1001, and displays a product data viewing screen generated from the viewing information display data received from the product status management server. The viewing request may include a pack ID or unique ID obtained by reading in response to user operation of a scanner launched from the viewing request screen of the app of this embodiment launched on the user's mobile terminal 1013, or it may not include a pack ID or unique ID for viewing all of the user's stockpiled products.

[0060] The cancellation request unit 7003 receives a cancellation request operation on a cancellation request screen of the application of this embodiment launched on the user's mobile terminal 1013 and transmits the cancellation request to the product status management server 1001 . The cancellation request includes the unique ID of the product to be cancelled, which is obtained by reading the product in response to user operation of a scanner launched from the cancellation request screen of the app of this embodiment launched on the user's mobile terminal 1013. The product data of products for which product status management is no longer required due to consumption, disposal, etc. can be easily and reliably identified by including in the cancellation request the unique ID read from the unique ID storage means of the product to be cancelled.

[0061] A notification viewing unit 7004 displays a notification viewing screen when the user launches this application by taking a predetermined action in response to a push notification message displayed on the screen of the user's mobile terminal, the push notification having this application as the notification destination. The notification viewing screen displays the unique ID, product name, and product expiry date of the product that is the subject of the notification. The notification of the present invention is not limited to a push notification, but may be, for example, a method in which a local product database is configured, the product expiration date of product data is monitored by a launched app, and a notification message is displayed on the app screen when product data that meets specified notification criteria is extracted. Alternatively, an email notification may be sent to the email address registered when the user account was created when the app was installed, and the email content may include the unique ID, product name, and product expiration date of the product that is the subject of the notification. Furthermore, a short message may be sent to the telephone number registered when a user account is created when the app is first launched after installation, and the message may include the unique ID, product name, and product expiration date of the product that is the subject of the notification.

[0062] When a registration request including a pack ID is sent to the product status management server 1001 , the local product database 7005 acquires product data of the product related to the pack ID, and stores the same product data as that stored in the product database 6010 .

[0063] FIG. 8 is a sequence diagram showing the operation of the product status management system of this embodiment, divided into the user side and the system operator side. In the following description, for the sake of convenience, the mobile terminal is simply referred to as a "mobile terminal", but more accurately, the mobile terminal is the "mobile terminal of the user on which this application is installed". In product registration step 8001, a worker 1004 at the shipping work area 1002 transmits product data for the picked product, including pack hierarchical information such as the packed product's unique ID, product expiration date, pack ID, and, if necessary, a lower pack ID, to a product status management server 1001, and the product status management server additionally registers the received product data in the product database 6010.

[0064] (Product database) FIG. 9 is a block diagram showing the data structure of the product data stored in the product database 6010. The structure includes a unique ID 9001 for individually identifying the product, a pack ID 9002, a lower pack ID 9003, an item ID 9004, and a product expiration date 9005. Here, in the case of a pack that does not have a lower pack, the item value of the lower pack ID is set to "null", i.e., empty.

[0065] In a product pack purchase step 8002, the user purchases a product pack at the store 1008. Here, an example is shown in which the user purchases a product pack at a real store, but the purchase of a product pack in the present invention is not limited to this, and the product pack may also be purchased at an online net store.

[0066] In app installation / first launch step 8003, the user downloads the app from a specified app store or the like to the user's mobile device, and when the app is subsequently launched for the first time, the user information entered into a user account creation screen presented by the app is sent to the system side. In a user account creation step 8004, the user account creation unit 6012 creates a user account based on the received user information, and transmits a push notification approval request to the user side. In a notification approval step 8005, depending on the user's approval action on the approval screen displayed on the browser in response to the push notification approval request from the user account creation unit 6012, approval or rejection of the push notification is returned to the system side. In the notification destination saving step 8006, if the push notification is approved, the user account creation unit 6012 generates an app ID as an identifier that uniquely identifies the combination of the app and the mobile terminal as the destination of the push notification, and saves it in the user account stored in the user information database 6011. If push notification approval is rejected, at least one of the following will be registered as the notification destination instead of the app ID: email address, phone number, etc. In the following explanation, "app ID, etc." refers to information that will be the notification destination value, including the app ID, email address, and phone number.

[0067] In pack ID reading step 8007, the user operates the mobile terminal to launch the application, and activates the registration request section 7001 to read the pack ID of the purchased product pack. In a registration request step 8008, the registration request section transmits a registration request including the pack ID to the system operator.

[0068] FIG. 10 shows a registration request application screen displayed on the mobile terminal by the operation of the registration request unit. Reference numeral 10000 denotes the application screen. When the user presses the read button 10001, the scanner on the mobile device is activated. When the user points the scanner at the two-dimensional code label storing the pack ID, the read pack ID is displayed in the pack ID display section 10002. When the user presses the registration request button 10003 in this state, a registration request including the read pack ID is sent to the system operator. If a lower-level pack exists, the pack ID of the higher-level pack can be sent to request registration of the primary product of the pack and the secondary products included in the lower-level pack all at once, eliminating the inefficiency of users having to register each product individually as in conventional systems.

[0069] In a linking registration step 8009, the product registration unit 6002 links the application ID of the application related to the registration request with the product data related to the pack ID.

[0070] FIG. 11 is a conceptual diagram showing the association between the application ID of the notification destination and product data. Reference numeral 11001 denotes product data, and includes in its data item the pack ID 9002. A linking table 11002 stores pairs of values ​​of pack ID 11003 and application ID 11004. Application IDs and product data that share a common pack ID value are linked together.

[0071] (Modification of linking) FIG. 12 is a diagram showing modified examples of the structure of product data to be registered and modified examples of linking in the product data of the structure. A block diagram 12000 shows the structure of product data when a product is registered. Data items 12001 include a unique ID 12002, a pack ID 12003, a lower pack ID 12004, an application ID 12005, an item ID 12006, and a product expiration date 12007. 12008 is the product data for product A, and the notification destination field value is "null", i.e. blank. 12009 is the product data for product B, and the notification destination field value is "null", i.e. blank. 12010 is the product data for product C, and the notification destination field value is "null", i.e. blank. Therefore, at this point, none of the product data is linked to the application ID that will be the notification destination. Here, the pack ID value is the same, "abc", so it can be seen that these are constituent products of the same product pack.

[0072] A block diagram 12011 shows the structure of product data after linking and registration. When one looks at the item value of the notification destination 12012, one can see that the application ID value "yyx" is registered as the item value of the notification destination. The modified example of the linking registration is a method in which the application ID value is registered in the notification destination item in this way.

[0073] Returning to the explanation of Figure 8. In the viewing request step 8010, the user operates the mobile terminal to operate the data viewing request unit 7002, which reads the pack ID or unique ID as necessary, and sends a viewing request including the read pack ID or unique ID, or a viewing request including neither ID, to the system operator.

[0074] FIG. 13 shows an application screen for a registration request displayed on a mobile terminal by the operation of the browsing request unit. Reference numeral 13000 denotes an application screen for a viewing request. When the user applies an action to a read button 13001, the scanner of the mobile terminal is started. When the user points the scanner at a two-dimensional code label storing a unique ID or a two-dimensional code label storing a pack ID, the read ID is displayed in a unique ID list display section 13002 or a pack ID list display section 13003. When an action is applied to a view request button 13004 in this state, a view request including the read unique ID or pack ID is sent to the system operator. It is possible to send a request to the system operator to view without reading any IDs. In this case, the request to view the product data of all products related to this application ID will be sent.

[0075] In a browsing information creating step 8011, the product data browsing support unit 6007 extracts product data in response to a browsing request from the user's mobile terminal, and generates browsing information display data in a predetermined format. If the browse request includes a pack ID or a unique ID, product data that has the pack ID or unique ID as the item value of the data item is extracted. If the browse request does not include a pack ID or a unique ID, product data that has the app ID of the app related to the browse request as the item value of the data item is extracted.

[0076] In a browse information delivery step 8012, the product data browse support unit 6007 transmits the generated browse information display data to the data browse request unit of the user's mobile terminal.

[0077] In a stock viewing step 8013, the data viewing unit 7002 that has received the view information display data generates a data viewing screen from the view information display data and displays it on the screen.

[0078] FIG. 14 is an example of a data viewing screen displayed on a user's mobile terminal. A data viewing screen 14000 displays a product data list 14002 with items 14001 including a unique ID, product name, and product expiry date. A selection button 14003 is generated at the end of the listed product data, and the selected product data can be deleted by adding a selection action to the selection button and adding an action to a deletion request button 14004 in the selected state. By deleting product data for which product status management is no longer necessary, such as data for lost products, the complexity of management can be reduced.

[0079] In a product consumption step 8014, the product is consumed by the user or the like. In unique ID reading step 8015, the user operates the mobile terminal to operate the clearing request unit 7003, and reads the unique ID of the product to be cleared. In a cancellation request step 8013, the cancellation request section transmits a cancellation request including the read unique ID to the system operator.

[0080] FIG. 15 is an example of a reconciliation request screen displayed on the user's mobile terminal. Cancellation request screen 15000 generated and displayed by cancellation request unit 7003 displays product data 15001 including items such as the unique ID related to the reading, product name, and product expiration date. When canceling the displayed product data, an action is added to cancellation request button 15002, and a cancellation request is sent to the system operator. The system is configured so that the cancellation request can be canceled by adding an action to cancel button 15003.

[0081] In a product data deletion step 8017, the deletion unit 8008 that has received the deletion request deletes the product data of the unique ID included in the deletion request.

[0082] In the product data monitoring step 8018, the product data monitoring unit 6004 The product data is monitored at a predetermined cycle. If none of the product data meets the notification criteria, the process moves to a waiting step 8019 and waits until the next monitoring timing. If there is any product data that meets the notification criteria, the operation of the product status monitoring unit proceeds to a notification information generating step 8020 .

[0083] The notification criteria for all product types will be two-stage criteria: for products where the remaining period from the monitoring timing to the product expiration date is less than three months, and for products where the remaining period is less than one month. The notification criteria that can be adopted in the present invention are not limited to those shown here, and can be changed as appropriate according to the characteristics of the user or item, or the system's policies, such as a length of time remaining different from that shown here, three or more stages of criteria, or a different remaining time period for each item.

[0084] In a notification information generating step 8020, the notification generating unit 6005 references the product data that meets the notification criteria and the product master 6009, and generates notification information display data that displays the unique ID, product name, and product expiry date. In a push notification step 8021, the notification distribution unit 6006 executes a push notification with this application as the notification destination and the notification content as notification information display data.

[0085] In a notification viewing step 8022, when the user performs an action on the notification message displayed on the user portable terminal, this application is started, and the notification information is displayed by the notification viewing unit 7004.

[0086] FIG. 16 shows an example of a notification information display screen that changes over time. Notification information display screen 16001 is the notification information display screen for February 1, 2025. The diagonal shading in the display frames for "Curry A" shown in 16002 and "Stew B" shown in 16003 indicates a pink notification display notifying that the product expiration date is less than March. The frame for "Rice C" 16004 shows no notification because these do not meet the notification criteria. Reference numeral 16005 denotes a purchase assistance button, which is set up so that by the user taking action on the purchase assistance button, the user is directed to a purchasing site where a product equivalent to the product for which the notification is targeted can be obtained. The notification information display screen 16006 is the notification information display screen for March 1, 2025. The vertical shading in the display frame of "A Curry" shown in 16007 indicates a red display notifying that the product expiration date is less than January. The diagonal shading in the display frame of "Stew B" 16008 and the frame of "C Rice" 16009 is a pink notification display indicating that the product expiration date is less than March. 16010 is a purchase support button similar to 16005. Notification information display screen 16011 is the notification information display screen for April 1, 2025. The horizontal shading in display frame 16012 for "A Curry" is a gray display indicating that the product has expired. The vertical shading in display frame 16013 for "Stew B" is a red notification display indicating that the product has less than one month left until its expiration date. The diagonal shading in the display frame for "C Rice" shown in 16014 is a pink notification display indicating that the product has less than three months left until its expiration date. 16015 is a purchase support button similar to 16005. By displaying notifications in gradually different display formats according to the remaining time until the product expiration date, it becomes possible to promote consumption according to the urgency of the expiration date, which supports the optimization of product condition management. Here, notifications in gradually different display formats using red, pink, and gray colors are used, but the display format of the present invention is not limited to this, and the display format can be changed as appropriate.

[0087] By operating the system configured as described above, users of this system can easily manage the product status of products stored at home. This system can support users in managing the product status without requiring them to perform cumbersome tasks related to setting product information and user information. EXAMPLES

[0088] The second embodiment is an example of product status management by the product status management system when a product pack is ordered and obtained online, such as through an EC site, rather than through a store.

[0089] FIG. 17 is an overall diagram showing the operations related to the distribution process and product status management when products managed by the system of this embodiment are sold online. Components similar to those related to store sales shown in FIG. 1 are given the same reference numerals and their explanations are omitted.

[0090] The registered product pack 17003 delivered to the delivery system 17001 is delivered to the home 1011 of the user 1010 by a delivery person 17002. The product pack 17003 received by the user 1010 is stockpiled at the user's home 1011. The pack ID of the stockpiled product pack 1012 is read by the mobile terminal 1013 carried by the user 1010, and is transmitted to the product status management server 1001 together with the application ID of the application installed on the mobile terminal, and is registered in association with the product data of the products that make up the product pack. Here again, the product pack received by the user and the stockpiled product pack are given different reference numbers for convenience since they are at different chronological positions in the distribution process, but they are the same product pack.

[0091] For products that are ordered and sold online through EC or the like and then stockpiled, the same effect of eliminating the complexity as in the first embodiment can be achieved by using the same system operations and user operations as in the first embodiment. [Industrial Applicability]

[0092] The present invention can be applied to the purpose of managing the expiration dates of stockpiled products by dealers of stockpiled products and home users who stockpile products. [Explanation of symbols]

[0093] 1001 Product status management server 1002 Shipping Workshop 1004 Worker 1005 Label Printer 1006 Product packs in the process of being packed 1008 stores 1009 Product packs displayed in stores 1010 Users 1011 User's Home 1012 Stockpiled Product Pack

Claims

1. A product status management system including a mobile terminal of a user on which a predetermined application is installed, a) a unique ID storage means for storing a unique ID attached to the product packaging or the product itself for individually identifying the product; b) a pack ID storage means for storing a pack ID for identifying a pack that is attached to the packaging of the pack or to the product itself, the pack ID being composed of one or more of the products; c) a product database storing product data including, as data items, a pack ID of a pack in which the product is included, a unique ID of the product, and a product expiration date of the product; d) a registration request means, which is realized by the application and the mobile terminal working together, for reading the pack ID from the ID storage means of the pack related to the user's acquisition and transmitting acquisition information including the pack ID; e) a linking registration means for receiving the acquired information and registering a link between a notification destination related to the application and product data having the pack ID as an item value; f) a notification means for monitoring a product status including the product expiration date according to a predetermined monitoring schedule, and for notifying the notification destination registered in association with product data of a product that satisfies a preset notification criterion; A system comprising the above as a system configuration.

2. The system configuration further includes: g) a clearing request means, which is realized by the application and the mobile terminal working together, for reading the unique ID of the product and transmitting a clearing request including the unique ID; h) a deleting means for receiving the deleting request and deleting the product data of the product related to the unique ID; 2. The system of claim 1, further comprising:

3. The system according to claim 1, wherein the notification destination is an application ID that identifies a combination of the installed application and the mobile terminal, and the notification is a push notification with the application ID as the notification destination.

4. The system described in claim 1, characterized in that the pack ID storage means is at least one code selected from a two-dimensional code and a one-dimensional barcode, and the attachment is at least one code selected from a seal, a box, or a label printed with the code.

5. The system described in claim 1, characterized in that the unique ID storage means is at least one code selected from a two-dimensional code and a one-dimensional barcode, and the attachment is at least one code selected from a seal, a box, or a label printed with the code.

6. 2. The system according to claim 1, wherein said pack ID storage means is at least one code selected from a two-dimensional code and a one-dimensional bar code, and said attachment is by a bottleneck on which said code is printed.

7. 2. The system according to claim 1, wherein said unique ID storage means is at least one code selected from a two-dimensional code and a one-dimensional barcode, and said attachment is by a bottleneck on which said code is printed.

8. The system according to claim 1, characterized in that the pack ID, the unique ID of the product, and the product expiration date of the product, which are included in the data items of the product data, have their item values ​​registered according to the installation.

9. 2. The system according to claim 1, wherein said pack ID storage means further stores said unique ID and said product expiry date of a product contained in said pack.

10. 2. The system according to claim 1, wherein the product database is provided in a memory of the mobile terminal.

11. 2. The system according to claim 1, wherein the unique ID storage means is a wireless tag, and the reading is achieved by cooperation between a wireless function of the mobile terminal and the application.

12. 2. The system according to claim 1, wherein the unique ID storage means is a wireless tag, and the attachment is performed by sticking a label incorporating the wireless tag or hanging a bottleneck incorporating the wireless tag around the neck.

13. 2. The system according to claim 1, wherein the pack ID storage means is a wireless tag, and the reading is realized by cooperation between a wireless function of the mobile terminal and the application.

14. 2. The system according to claim 1, wherein the pack ID storage means is a wireless tag, and the attachment is performed by sticking a label incorporating the wireless tag or hanging a bottleneck incorporating the wireless tag around the neck.

15. 2. The system of claim 1, wherein the pack comprises subpacks.

Images