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 configuration: a) product 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 stockpiled product database; d) registration request means for sending acquisition information including the pack ID of a provision unit related to a user's acquisition; e) linking registration means for linking and registering a user 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. It includes expiration dates such as best before dates and replacement dates, and provides information on the safety and quality of the product. Product expiration dates serve as a guide for using the product appropriately, taking into account the storage conditions and usage method of the product. [Background technology]

[0002] There is a problem with products stockpiled for daily use at home, as they are no longer usable when needed due to expiration dates, expiration dates, etc. Furthermore, in response to the frequent occurrence of disasters in recent years, there is a demand not only for local governments and companies but also for ordinary households to improve their stockpiles of products for disaster prevention. In particular, the stockpiles for disasters at ordinary households are in a state where they are not safe. 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 have expired when they are needed and are no longer suitable for use, which is a problem.

[0003] In order to prevent the above-mentioned cases of products becoming unusable, a system for managing the condition of stockpiled products is described in Patent Document 1.

[0004] Patent document 1 discloses a system including a product database that stores product information including an expiration date and user information in association with a unique ID assigned to disaster prevention products, a replacement notice notification means that monitors the expiration date according to a predetermined monitoring schedule to determine whether it is time to replace the disaster prevention product, and if it is determined that it is time to replace the product, sends a replacement notice, a notification receiving means that automatically receives the replacement notice, a replacement command means that sends an order request for the disaster prevention product related to the replacement notice, and a viewing means that connects product information to the product database and views it, and a software program that is installed on a mobile terminal and operates in cooperation with the mobile terminal to realize these functions. However, a mechanism must be in place that allows the user who acquires a disaster prevention product to read the unique ID assigned to the product and easily set the product's expiration date.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]

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

[0006] 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]

[0007] According to a first aspect of the present invention, there is provided a product status management system including a user's mobile terminal on which a predetermined application is installed, a) a product ID storage means for storing a unique ID that is attached to the product packaging or the product itself and that individually identifies 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 constituent products themselves; c) a stockpiled product database that stores product data including, as data items, a pack ID of a pack in which the product is included, the unique ID, 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 pack ID storage means of the pack related to the user's acquisition and for transmitting acquisition information including the pack ID and authentication information of the user; e) a linkage registration means for receiving the acquisition information and the authentication information and registering a linkage between a user ID related to the authentication information and product data having the pack ID as an item value; f) a notification means for monitoring the product status including the product expiration date according to a predetermined monitoring schedule, and notifying the notification destination associated with the user ID when a preset notification criterion is met; The present invention provides a system including the above as a system configuration.

[0008] Here, the unique ID is an ID that individually identifies a disaster prevention product, and is used as a term to refer to an identifier introduced to identify and specify a specific disaster prevention product from among multiple disaster prevention products of the same type. The pack ID is used as a term representing identification information that specifies a "pack" in which one or more units of a product are bundled together in one package to the extent that they may be treated as the same from a certain perspective.

[0009] Here, the application may be a dedicated app for product status management that is prepared by the operator of the product status management system for the user to download, and the user ID may be ID information generated or selected as an identifier that uniquely identifies the user, and is registered in a user account created when the user logs in for the first time after downloading the application to their mobile device. Alternatively, the application may be a browser that displays a product condition management site provided by the operator of the product condition management system, and the user ID may be ID information generated or selected as an identifier that uniquely identifies the user and is registered in a user account created when the user logs in to the product condition management site for the first time.

[0010] Here, the pack ID may be an ID that identifies a pack having a common combination of the unique IDs of products that constitute the pack. Alternatively, the pack ID may be an ID that individually identifies the pack and specifies a unique pack.

[0011] Here, the pack may include sub-packs as its configuration.

[0012] Here, the notification may be a push notification whose notification destination is an application related to the user ID.

[0013] In the case of a dedicated product status management app, 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 a mechanism is adopted that allows messages to be displayed in the notification area of ​​the mobile device even when the app is in the background. This eliminates the hassle of users having to consciously launch the app to receive notifications in order to manage product status. If the application is a browser, it uses web push notifications that send push notifications to PCs and smartphones in the background even when the product status management site is not displayed. Once the user "allows notifications," they can receive information without taking any active action, eliminating the hassle of users having to consciously visit a product status management site to receive notifications in order to manage the product status.

[0014] Here, the product 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. Alternatively, the product 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 due to a bottleneck on which the code is printed.

[0015] 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. Alternatively, 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 by a bottleneck on which the code is printed.

[0016] Here, the pack ID, the unique ID and the product expiry date included in the data items of the product data may have their item values ​​registered in response to the installation of the product ID storage means and the pack ID storage means.

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

[0018] Here, the stockpiled product database may be provided in a memory of the mobile terminal.

[0019] Here, the product 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.

[0020] Here, the product ID storage means may be a wireless tag, and the attachment may be a seal, box or label incorporating the wireless tag, or a hanging around the neck of a bottle incorporating the wireless tag.

[0021] 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 portable terminal and the application.

[0022] Here, the pack ID storage means may be a wireless tag, and the attachment may be a seal, box or label incorporating the wireless tag, or a hanging around the neck of a bottle incorporating the wireless tag.

[0023] 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 any data selected from the product data of the product related to the unique ID; It may be stated as including. [Brief description of the drawings]

[0024] [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 a block diagram showing items of user information that make up a user account. [Diagram 3] FIG. 3 is an image diagram showing the details of the work in the shipping work area. [Figure 4] FIG. 4 shows details and variations of the product pack that the user acquires through the above-mentioned distribution process. [Diagram 5] FIG. 5 is a perspective view showing a modified example of a product pack that a user acquires through a distribution process. [Figure 6] FIG. 6 is an image diagram showing a product pack in which one product is provided as a unit. [Figure 7] FIG. 7 is a functional block diagram showing the functional configuration of the product status management server. [Figure 8] FIG. 8 is a block diagram showing a functional configuration realized by a mobile terminal of a user on which an application of this embodiment is installed, in cooperation with the application. [Figure 9] FIG. 9 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 10] FIG. 10 is a block diagram showing the data structure of the product data stored in the stockpiled product database. [Figure 11] FIG. 11 shows a registration request application screen displayed on a mobile terminal by the operation of the registration request unit. [Figure 12] FIG. 12 is a conceptual diagram showing the association between a user ID and product data on the system side. [Figure 13] FIG. 13 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 14] FIG. 14 shows an application screen for a viewing request displayed on a mobile terminal by the operation of the viewing request unit. [Figure 15] FIG. 15 is an example of a data viewing screen displayed on a user's mobile terminal. [Figure 16] FIG. 16 is an example of a reconciliation request screen displayed on the user's mobile terminal. [Figure 17] FIG. 17 shows an example of the notification information display screen. [Figure 18] FIG. 18 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. [Figure 19] FIG. 19 is an overall diagram showing, in time series, the process from the shipment of a product whose expiration date is managed by the system of this embodiment to its sale and stockpiling through a physical store. [Figure 20] FIG. 20 is a block diagram showing items of user information that make up a user account. [Figure 21] FIG. 21 is an image diagram showing the details of the work in the shipping work area. [Figure 22] FIG. 22 shows details of the product pack that the user acquires through the above-mentioned distribution process, as well as modified examples. [Diagram 23] FIG. 23 is a perspective view showing a modified example of a product pack that a user acquires through the above-mentioned distribution process. [Figure 24] FIG. 24 is an image diagram showing a product pack in which one product is provided as a unit. [Diagram 25] FIG. 25 is a functional block diagram showing the functional configuration of the product status management server. [Figure 26] FIG. 26 is a block diagram showing the functional configuration realized by the user's mobile terminal in this embodiment in cooperation with the browser displaying the product status management site. [Figure 27] FIG. 27 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 28] FIG. 28 is a block diagram showing the data structure of the product data stored in the stockpiled product database. [Figure 29] FIG. 29 is an image diagram of a registration request page displayed on a browser, which constitutes the registration request section. [Diagram 30] FIG. 30 is a conceptual diagram showing the association between a user ID and product data on the system side. [Diagram 31] FIG. 31 is a diagram showing a modified example of the structure of product data to be registered and a modified example of linking registration in the product data of the same structure. [Diagram 32] FIG. 32 shows an example of a browsing request page displayed on a browser of a user's mobile terminal. [Diagram 33] FIG. 33 shows an example of a data browsing page displayed on the browser of the user's mobile terminal. [Diagram 34]FIG. 34 shows an example of a reconciliation request page displayed on a browser on the user's mobile terminal. [Diagram 35] FIG. 35 is an example of a notification information display page. [Diagram 36] FIG. 36 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

[0025] The object of supporting a user in managing the status of merchandise stored by the user without requiring the user to perform troublesome operations related to setting merchandise information and user information is realized by providing a merchandise status management system utilizing a portable terminal on which a specified application is installed.

[0026] 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

[0027] 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 .

[0028] In the shipping work area 1002, a label printer 1005 outputs a product 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 pack ID storing two-dimensional code label printed with a two-dimensional code storing the pack ID of a lower-level pack. Here, a two-dimensional code is used as the product ID storage means for storing the unique ID, but the product ID 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 used as appropriate as long as they can be read using the functions provided in the mobile terminal. Also, a two-dimensional code is used as the pack ID storage means for storing the pack ID and lower 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.

[0029] A worker 1004 picks multiple products from a product shelf 1003, and the multiple products with a two-dimensional code label storing the product ID attached are packed into an empty lower pack. A two-dimensional code label storing the lower pack ID is attached to the lower pack, which is then packed into another pack to complete the product pack. A two-dimensional code label storing the pack ID is attached to the pack into which the lower pack is 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 including product information of the products contained in the product pack and the lower pack ID in the case of a nested structure is registered. Here, pack ID is used as a term to represent identification information (hereinafter referred to as expiration date item group pack ID) that specifies the range in which the combination of product items and product expiration dates contained in a pack in which one or more product units are grouped together in a single package are the same. Here, we have adopted a pack ID for item groups by expiration date, which assigns the same pack ID to multiple packs that have the same product expiration date and item combination, but the pack IDs that can be used in this invention are not limited to this, and may also be unique pack IDs that treat each pack as unique.

[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 a stockpiled product pack 1012 is read by a user 1010 operating a mobile terminal 1013 and a dedicated product status management application (hereinafter referred to as this app or simply "the app") installed on the mobile terminal, and the acquired information including the pack ID is sent to the product status management server together with authentication information.

[0031] Communications from the app are authenticated by the product status management server, and the user ID related to the authentication information is linked to the product data of the products that make up the product pack, and then registered. Here, the user ID is ID information that identifies the user in the user account created when the app is downloaded and installed, but a unique username or email address created by the user may also be used as the user ID. To distinguish this from the product registration described above, it will be referred to as "linked registration" in the following description. 2 is a block diagram showing items of user information that make up a user account. In a user account, user information consisting of a user ID 2001, which is ID information for identifying a user, a unique username 2002 created by the user, an email address 2003, a password 2004, notification settings 2005 for deciding whether or not to receive push notifications, and personal information 2006 such as the user's telephone number, address, payment method, etc. is registered and stored in a user information database, which will be described later.

[0032] Returning to the explanation of Figure 1. 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.

[0033] FIG. 3 is an image diagram showing the details of the work in the shipping work area 1002. Product A 3001, product B 3002, and product C 3003 are picked by a worker 1004 from a product shelf 1003. Product ID storing two-dimensional code labels 3005 and 3006, on which two-dimensional codes storing the respective unique IDs output by a label printer 1005 are printed, are affixed to products A and B, and the products are packed in a lower pack packaging material 3004. A lower pack ID storing two-dimensional code label 3006, 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, on which a product ID storing two-dimensional code label 3007 is affixed, are packed in a packaging pack 3008 on which a pack ID storing two-dimensional code label 3007, on which a two-dimensional code storing a pack ID is printed, is affixed, and the product pack is completed.

[0034] 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. The storage information may include information selected from a unique ID that identifies the picked 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 and store the product data in a local stockpiled product database installed in the user's mobile device, making it possible to manage the product status on a stand-alone basis.

[0035] The worker 1004 transmits product data for the picked products from the business tablet 3011 or business computer 1007 to the product status management server 1001, the data including pack hierarchy information such as the unique ID of the packed product, the product expiration date, the pack ID related to the packaging, and the lower pack ID if a lower pack exists. The product status management server additionally registers the received product data in a stockpiled product database, which will be described later. This registration is called product registration to distinguish it from linking registration, which will be described later.

[0036] FIG. 4 shows details and variations of the product pack that the user acquires through the above-mentioned distribution process. Reference numeral 4000 indicates a lower pack, which is a content of the upper product pack in Fig. 3, and a product C, which is a primary product directly contained therein. Product A 4003 and product B 4004 are contained in a package 4001 to which a pack ID storing two-dimensional code label 4002, which has a two-dimensional code printed thereon storing the pack ID of the lower pack, is affixed. Here, a two-dimensional code is used as the pack ID storage means for storing the pack ID and lower 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.

[0037] For both product A 4003 and product B 4004, which are secondary products when viewed from the higher-level pack, and product C 4005, which is a primary product, item IDs 4006, 4007, 4008 that identify the type of product and their product expiration dates 4009, 4010, 4011 are written as one-dimensional barcodes, symbols, letters, etc., and can be read by workers using a scanner installed on the business tablet 3009 or business computer 1007 as necessary.

[0038] 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.

[0039] Product A 4003, product B 4004, and product C 4005 have product ID storing two-dimensional code labels 4012, 4013, and 4014 attached thereto, on which a two-dimensional code storing a unique ID for individually identifying each product is printed.

[0040] Reference numeral 4015 denotes a modified example in which a two-dimensional code sealing label 4016 is used, on which a two-dimensional code storing a pack ID is printed on the seal of the package. This can be used not only for 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] Reference numeral 4017 denotes a modified example in which a two-dimensional code sealing tape 4018 is used, on which a two-dimensional code storing a pack ID is printed on the seal of the package. This can be used 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.

[0042] Here, three products are configured as a product pack and are the unit of supply to the purchasing user, but the packaging form, type of items, combination and quantity of different items of the products that make up the pack that is the unit of supply that can be adopted in the present invention can be changed as appropriate without being limited to this.

[0043] FIG. 5 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 5001 on which an item ID 5002 and a product expiration date 5003 are written using a one-dimensional barcode, symbol, character, or the like is stored in a box 5004 for packaging. A two-dimensional code 5005 storing the product's unique ID is printed on the box 5004.

[0044] The product packed in the box 5004 is packed in a bag 5007 on which a two-dimensional code 5008 storing a pack ID is printed, thereby forming a product pack. Here, two products are configured as the primary products of the product pack and are the unit of supply to the purchasing user, but the packaging form of the products that are the unit of supply that can be adopted in this invention, the presence or absence of sub-packs, the type of item, the combination and number of different items can be changed as appropriate without being limited to this.

[0045] FIG. 6 is an image diagram showing a product pack in which one product is provided as a unit. An unpackaged product 6001 has an item ID 6002 and a product expiration date 6003 written on it using a one-dimensional barcode, symbol, character, or the like, and has a bottleneck 6004 attached. A two-dimensional code 6005 storing a pack ID and a two-dimensional code 6006 storing a unique ID are printed on the bottleneck.

[0046] 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.

[0047] FIG. 7 is a functional block diagram showing the functional configuration of the product status management server 1001. It is composed of functional components including a verification unit 7001, a product registration unit 7002, a linking registration unit 7003, a product data monitoring unit 7004, a notification generation unit 7005, a notification distribution unit 7006, a product data viewing support unit 7007, a settlement unit 7008, a product master 7009, a stockpiled product database 7010, and a user information database 7011 that stores user account information.

[0048] When a user logs in from an application on the mobile terminal 1013, the verification unit 7001 verifies the user name and password contained in the verification information to verify that the access is from a legitimate user. If the login is successful, the verification unit 7001 returns an authentication token to the application, and in subsequent communications, the application attaches the authentication token.

[0049] A product registration unit 7002 registers 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, in a stock product database 7010.

[0050] The association registration unit 7003 registers an association between the user ID of the user account related to the verification information or authentication token attached to the registration request received from the verified application and the product data of the product related to the pack ID related to this registration request. When requesting registration, the user who operates the mobile device on which the app is installed does not have to go through the trouble of consciously setting a user ID. The user simply operates the logged-in app to read and send the pack ID.

[0051] The product data monitoring unit 7004 determines whether or not a product is subject to notification based on whether or not the product condition of the product registered in the stockpiled 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 the state where the value of the remaining period until the product expiration date at the monitoring timing is below the set reference value, and products whose item value for the product expiration date reaches the notification criterion are determined to be products to be notified.

[0052] The notification generation unit 7005 generates notification content for a product that meets the notification criteria, addressed to the notification destination described in the user account related to the user ID linked to the product data. If the notification setting is set to receive push notifications, a notification message to be displayed by push notification is generated. If the notification setting is set to not receive push notifications, a notification email to the email address and a short message to the phone number described in the user account are generated.

[0053] If notification settings are configured to receive push notifications, the notification delivery unit 7006 transmits a notification message to an app on the user's device via a push notification service. Push notifications can be used to notify apps using functions provided by the mobile device platform even when the app is not running, which means that users are freed from the hassle of having to consciously launch an app to monitor product data. Available push notification services include Firebase Cloud Messaging (FCM) and Apple Push Notification Service (APNs).

[0054] If your notification settings are configured not to receive push notifications, a notification email will be sent via an email sending service and a short message will be sent via a short message service.

[0055] The product data viewing support unit 7007 extracts product data in response to a viewing request relating to access from an app on the user's mobile device, generates viewing information display data in a specified format using information such as the product name searched for in the product master 7009 using the item ID contained in the product data, and sends the data 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. If the request does not include a pack ID or a unique ID, product data having the user ID of the user related to the request as the item value of the data item is extracted.

[0056] In response to a deletion request including information to be deleted from an app on the user's mobile device, the deletion unit 7008 selects one of the product data corresponding to the information to be deleted from the stockpiled product database in a preset order and deletes it.

[0057] The product master 7009 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.

[0058] The stock product database 7010 stores product data of products related to product packs. The user information database 7011 stores user information that constitutes a user account.

[0059] When the user launches the downloaded app for the first time, the user account creation unit 7012 receives user information input via a user information input screen presented by the app from the app, creates a user account consisting of user information with the user ID as a primary key, and saves the notification settings for the user's approval or rejection of the push notification. If the push notification is approved, the application ID that is the destination is registered in the notification settings as the notification destination.

[0060] (User's mobile device) FIG. 8 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 8001 , a data viewing unit 8002 , a clearing request unit 8003 , a notification viewing unit 8004 , and a local stockpiled product database 8005 .

[0061] The registration request unit 8001 transmits a registration request to the product status management server 1001, the registration request including the pack ID obtained 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.

[0062] The data viewing unit 8002 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.

[0063] The cancellation request unit 8003 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 expiration date item ID of the product to be cancelled, which is obtained by reading the item 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 expiration item ID read from the product ID storage means of the product to be cancelled.

[0064] The notification viewing unit 8004 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, and may be, for example, a method in which a local stockpiled product database is configured, the 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, the unique ID, product name, and product expiry date of the product to be notified may be sent by a short message to a phone number registered in the user account, or, if a notification destination is not registered, by an in-app notification when the app is launched.

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

[0066] FIG. 9 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 9001, 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 stockpiled product database 7010.

[0067] (Stockpile Product Database) FIG. 10 is a block diagram showing the data structure of the product data stored in the stockpile product database 7010. As shown in FIG. The structure is comprised of a unique ID 10001 that individually identifies the product, a pack ID 10002, a lower pack ID 10003, an item ID 10004, and a product expiration date 10005. 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.

[0068] In a product pack purchase step 9002, the user purchases a product pack at a 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.

[0069] In an application installation step 9003, the application is downloaded by the user from a predetermined application store or the like onto the user's mobile terminal and installed. In the initial startup step 9004, the application is launched by the user's application startup action, and a screen is displayed prompting the user to create a user account. Here, the user is requested to input user information consisting of a user name, email address, telephone number, address, payment method, etc., and the user information is sent to the system operator according to the input and send action from the user. In a user account creation step 9005, the user account creation unit 7012 creates a user account made up of user information with the user ID as a primary key based on the received user information, and transmits a push notification approval request to the user side. In a notification approval step 9006, depending on the user's action on a screen prompting approval of the push notification from the user account creation unit 7012, approval or rejection of the push notification is returned to the system side. In destination storage step 9007, if the push notification is approved, the user account creation unit 7012 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 stores the app ID as the destination of the user account stored in the user information database 7011. 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.

[0070] In pack ID reading step 9008, the user operates the mobile terminal to launch the application, and activates the registration request section 8001 to read the pack ID of the purchased product pack. In registration request step 9009, the registration request section transmits a registration request including the pack ID and authentication information to the system operator.

[0071] FIG. 11 shows a registration request application screen displayed on a mobile terminal by the operation of the registration request unit. Reference numeral 11000 denotes the application screen. When the user presses the read button 11001, the scanner on the mobile device is started. 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 11002. When the user presses the registration request button 11003 in this state, a registration request including the read pack ID is sent to the system operator. If a lower-level pack exists, sending the pack ID of the higher-level pack makes it possible to request registration of the primary product of the higher-level pack and the secondary products included in the lower-level pack all at once, thus eliminating the inefficiency of users having to register each product individually as in conventional systems.

[0072] In a link registration step 9010, the link registration unit 7003 links the user ID related to the registration request with the product data related to the pack ID.

[0073] FIG. 12 is a conceptual diagram showing the association between a user ID and product data on the system side. Reference numeral 12001 denotes product data, and includes in its data item a pack ID 10002. A linking table 12002 stores pairs of values ​​of pack IDs 12003 and user IDs 12004. The user IDs and product data are linked via the pack IDs.

[0074] (Variation of linking registration) FIG. 13 is a diagram showing a modified example of the structure of product data to be registered and a modified example of linking registration in the product data of the same structure. A block diagram 13000 shows the structure of product data when a product is registered. Data items 13001 include a unique ID 13001, a pack ID 13003, a lower pack ID 13004, a user ID 13005, an item ID 13006 and a product expiration date 13007. 13008 is the product data for product A, and the field value for the user ID is "null", i.e. blank. 13009 is the product data for product B, and the field value for the user ID is "null", i.e. blank. 13010 is the product data for product C, and the field value for the user ID is "null", i.e. blank. Therefore, at this point, it is not linked to any user ID. Here, the value of pack ID 13003 is the same, "abc", so it can be seen that although there is a difference between being a primary product and a secondary product, they are constituent products of the same product pack.

[0075] Reference numeral 13011 is a block diagram showing the structure of product data after linking and registration. When one looks at the item value of the user ID 13012, one can see that "yyx" is registered as the item value of the user ID. The modified example of the linking registration is a method of linking registration in which the value of the user ID is registered in the item of the user ID in this way.

[0076] Returning to the explanation of Figure 9. In a viewing request step 9011, the user operates the mobile terminal to operate the data viewing request unit 8002, 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.

[0077] FIG. 14 shows an application screen for a viewing request displayed on a mobile terminal by the operation of the viewing request unit. Reference numeral 14000 denotes an application screen for requesting viewing. When the user applies an action to a read button 14001, the scanner of the mobile terminal is started. When the user points the scanner at a two-dimensional code label storing a product ID or a two-dimensional code label storing a pack ID, the read ID is displayed in a unique ID list display section 14002 or a pack ID list display section 14003. When an action is applied to a view request button 14004 in this state, a view request including the read unique ID or pack ID is sent to the system operator. It is also possible to send a request to the system operator that does not include any IDs, without reading any IDs. In this case, the request to view the product data of all products related to this user ID will be sent.

[0078] In a browsing information creating step 9012, the product data browsing support unit 7007 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 user ID of the user related to the browse request as the item value of the data item is extracted.

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

[0080] In a stock viewing step 9014, 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.

[0081] FIG. 15 is an example of a data viewing screen displayed on a user's mobile terminal. A data viewing screen 15000 displays a product data list 15002 having items 15001 such as a unique ID, a product name, and a product expiration date.

[0082] In a product consumption step 9015, the product is consumed by the user or the like. In a unique ID reading step 9016, the user operates the mobile terminal to operate the clearing request unit 8003, and reads the unique ID of the product to be cleared. In a cancellation request step 9017, the cancellation request section transmits a cancellation request including the read unique ID to the system operator.

[0083] FIG. 16 is an example of a reconciliation request screen displayed on the user's mobile terminal. The cancellation request screen 16000 generated and displayed by the cancellation request unit displays product data 16001, with items such as expiry item ID, product name, and product expiry date. When canceling the displayed product data, an action is added to cancellation request button 16002, and a cancellation request is sent to the system operator. The screen is configured so that the cancellation request can be cancelled by adding an action to cancel button 16003.

[0084] In a product data deletion step 9018, the deletion unit 7008 that received the deletion request deletes the product data that has the unique ID included in the deletion request as its item value.

[0085] In the product data monitoring step 9019, the product data monitoring unit 7004 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 9020 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 9021 .

[0086] 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.

[0087] In a notification information generation step 9021, the notification generation unit 7005 generates notification content for a product that meets the notification criteria, addressed to the notification destination described in the user account related to the user ID linked to the product data. If the notification setting is set to receive push notifications, a notification message to be displayed by push notification is generated. If the notification setting is set to not receive push notifications, a notification email to the email address and a short message to the phone number described in the user account are generated. Here, the notification contents are notification information display data that display the unique ID, product name, and product expiration date, generated by referring to the product data that meets the notification criteria and the product master 7009.

[0088] In a notification step 9022, the notification distribution unit 7006 executes notification with the application ID or the like as the notification destination and notification content as notification information display data.

[0089] In a notification viewing step 9023, 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 a notification viewing unit 8004.

[0090] FIG. 17 shows an example of a notification information display screen that changes over time. Notification information display screen 17001 is the notification information display screen for February 1, 2025. The diagonal shading in the display frames for "Curry A" shown in 17002 and "Stew B" shown in 17003 indicates a pink notification display notifying that the product expiration date is less than March. The frame for "Rice C" 17004 displays no notification because these do not meet the notification criteria. Reference numeral 17005 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. Notification information display screen 17006 is the notification information display screen for March 1, 2025. The vertical shading in the display frame of "A Curry" shown in 17007 indicates a red display notifying that the product expiration date is less than January. The diagonal shading in the display frame of "Stew B" 17008 and the frame of "C Rice" 17009 is a pink notification display indicating that the product expiration date is less than March. 17010 is a purchase support button similar to 17005. Notification information display screen 17011 is the notification information display screen for April 1, 2025. The horizontal shading in display box 17012 for "A Curry" is a gray display indicating that the product has expired. The vertical shading in display box 17013 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 box for "C Rice" shown in 17014 is a pink notification display indicating that the product has less than three months left until its expiration date. 17015 is a purchase support button similar to 17005. 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.

[0091] 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

[0092] The second embodiment is an example of product status management by the product status management system in the case where the product pack in the first embodiment is acquired not from a store but online from an EC site or the like.

[0093] FIG. 18 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.

[0094] The registered product pack 18003 delivered to the delivery system 18001 is delivered to the user's home 1011 by a delivery person 18002. The product pack 18003 received by the user 1010 is stored in the user's home 1011. The product pack received by the user and the stockpiled product pack are assigned different reference numbers for convenience since they are at different chronological positions in the distribution process, but are the same product pack.

[0095] 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. EXAMPLES

[0096] FIG. 19 is an overall diagram showing, in time series, the process from the 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 19001 provided in a communication network 19000 is communicatively connected to a product registration computer 19007 in a shipping work area 19002 and a user's mobile terminal 19013 .

[0097] In the shipping work area 19002, a label printer 19005 outputs a product 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. Here, a two-dimensional code is used as the product ID storage means for storing the unique ID, but the product ID 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 used as appropriate as long as they can be read using the functions provided in the mobile terminal. Also, a two-dimensional code is used as the pack ID storage means for storing the pack ID and lower 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.

[0098] A worker 19004 picks multiple products from a product shelf 19003, and the multiple products with a two-dimensional code label storing the product ID attached are packed into an empty lower pack. A two-dimensional code label storing the lower pack ID is attached to the lower pack, which is then packed into a pack to complete the product pack. A two-dimensional code label storing the pack ID is attached to the pack that will contain the lower pack. 19006 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 19007 located in the shipping work area in accordance with the above-mentioned affixing, and transmitted to a product status management server 19001 on a communications network 19000, where product data including product information of the products contained in the product pack and the lower pack ID in the case of a nested structure is registered. Here, pack ID is used as a term to represent identification information (hereinafter referred to as expiration date item group pack ID) that specifies the range in which the combination of product items and product expiration dates contained in a pack in which one or more product units are grouped together in a single package are the same. Here, we have adopted an expiration date-specific pack ID that assigns the same ID to multiple packs to the extent that the combination of product expiration date and item of the packaged products is the same, but the pack ID that can be used in this invention is not limited to this, and it may also be a unique pack ID that treats each pack as unique.

[0099] A product pack 19009 containing registered products is delivered to and displayed at a store 19008 , and is then purchased by a user 19010 and stored in the user's home 19011 . When a user 19010 operates a page of a product status management site (a website consisting of pages provided by each functional component of the product status management server of this embodiment, hereinafter referred to as this site) displayed in a browser on a mobile terminal 19013 carried by the user, the pack ID of the stockpiled product pack 19012 is read, and the acquired information including the pack ID is sent to the product status management server together with authentication information.

[0100] Communications from the browser display of this site are authenticated by the product status management server, and the user ID related to the authentication information is linked to the product data of the products that make up the product pack and registered. Here, the user ID is the ID information that identifies the user in the user account created to log in to this site, but the user ID may also be a unique username or email address created by the user. To distinguish it from the product registration explained above, it will be called "linked registration" in the following description.

[0101] Fig. 20 is a block diagram showing items of user information constituting a user account. In a user account, user information consisting of a user ID 20001 for identifying a user, a unique username 20002 created by the user, an email address 20003, a password 20004, notification settings 20005 consisting of settings for whether or not to permit web push notifications and notification destination information saved according to the settings, and personal information 20006 such as the user's telephone number, address, payment method, etc. is registered and saved in a user information database, which will be described later. If the notification setting is set to allow web push notifications, the browser will maintain a state that allows push notifications from this site, making it possible to receive push notifications.

[0102] Returning to the explanation of FIG. 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.

[0103] FIG. 21 is an image diagram showing the details of the work in the shipping work area 19002. Product A 21001, product B 21002, and product C 21003 are picked by a worker 19004 from a product shelf 19003. Product A and B are affixed with respective product ID storing two-dimensional code labels 21005 and 21006 outputted by a label printer 19005, and are packed in a lower pack packaging material 21004. A lower pack ID storing two-dimensional code label 21008 is affixed to the lower pack packaging material after packaging is completed, and a lower pack is completed. The lower pack and product C to which the product ID storing two-dimensional code label 21007 is affixed are packed in a packaging pack 21010 to which a pack ID storing two-dimensional code label 21009 in which a pack ID is stored is affixed, and a product pack is formed.

[0104] The worker 19004 transmits product data about the picked products from the business tablet 21011 or business computer 19007 to the product status management server 19001, the data including pack hierarchy information such as the unique ID of the packed product, the product expiration date, the pack ID related to the packaging, and the lower pack ID if a lower pack exists. The product status management server additionally registers the received product data in a stockpiled product database, which will be described later. This registration is called product registration to distinguish it from linking registration, which will be described later.

[0105] FIG. 22 shows details of the product pack that the user acquires through the above-mentioned distribution process, as well as modified examples. Reference numeral 22000 indicates a lower pack, which is a content of the upper product pack in Fig. 21, and product C, which is a primary product directly contained therein. Product A 22003 and product B 22004 are contained in package 22001 to which is attached a two-dimensional code label 22002 on which a two-dimensional code is printed and in which the pack ID of the lower pack is stored.

[0106] For both product A 22003 and product B 22004, which are secondary products when viewed from the higher-level pack, and product C 22005, which is a primary product, item IDs 22006, 22007, 22008 which identify the type of product and their product expiration dates 22009, 22010, 22011 are written as one-dimensional barcodes, symbols, letters, etc., and can be read by an employee using a scanner installed on the business tablet 21011 or business computer 19007 as necessary.

[0107] 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.

[0108] Product A 22003, product B 22004, and product C 22005 have product ID storing two-dimensional code labels 22012, 22013, and 22014 attached thereto, on which a two-dimensional code storing a unique ID for individually identifying each product is printed.

[0109] 22015 is a modified example in which a two-dimensional code sealing label 22016, on which a two-dimensional code storing a pack ID is printed on the seal of the package, is used as the pack ID storage means. This can be used 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.

[0110] 22017 is a modified example in which a two-dimensional code sealing tape 22018, on which a two-dimensional code storing a pack ID is printed on the seal of the package, is used as the pack ID storage means. This can be used not only for the lower-level packs shown here, but also for higher-level packs, and by combining the work of sealing the package with the work of attaching the pack ID storage means, it has the effect of increasing work efficiency.

[0111] Here, three products are configured as a product pack and are the unit of supply to the purchasing user, but the packaging form, type of items, combination and quantity of different items of the products that make up the pack that is the unit of supply that can be adopted in the present invention can be changed as appropriate without being limited to this.

[0112] FIG. 23 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 23001 on which an item ID 23002 and a product expiration date 23003 are written by a one-dimensional barcode, symbol, character, or the like is stored in a box 23004 for packaging. A two-dimensional code 23005 storing a unique ID of the product is printed on the box 23004.

[0113] The product packed in the box 23004 is packed in a bag 23007 on which a two-dimensional code 23008 storing a pack ID is printed, thereby forming a product pack. Here, two products are configured as the primary products of the product pack and are the unit of supply to the purchasing user, but the packaging form of the products that are the unit of supply that can be adopted in this invention, the presence or absence of sub-packs, the type of item, the combination and number of different items can be changed as appropriate without being limited to this.

[0114] FIG. 24 is an image diagram showing a product pack in which one product is provided as a unit. An unpackaged product 24001 has an item ID 24002 and a product expiration date 24003 written thereon by a one-dimensional barcode, symbol, character, or the like, and has a bottleneck 24004 attached. A two-dimensional code 24005 storing a pack ID and a two-dimensional code 24006 storing a unique ID are printed on the bottleneck.

[0115] 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.

[0116] FIG. 25 is a functional block diagram showing the functional configuration of the product status management server 1001. It is composed of the following functional components: a verification unit 25001, a product registration unit 25002, a linking registration unit 25003, a product data monitoring unit 25004, a notification generation unit 25005, a notification distribution unit 25006, a product data viewing support unit 25007, a settlement unit 25008, a product master 25009, a stockpile product database 25010, a user information database 25011 that stores user account information, and a user account creation unit 25012. In the following explanation, for convenience, it is sometimes simply written as "the user's mobile terminal", but more accurately it means "the user's mobile terminal that displays the product status management site in a browser". Similarly, it is sometimes simply written as "this site", but more accurately it means "the product status management site provided by this product status management system".

[0117] When a user logs in to the product status management site from the browser of the mobile terminal 19013, the verification unit 25001 verifies the user name and password to verify that the access is from a legitimate user, and if the login is successful, returns a cookie containing authentication information including the user ID to the browser, and causes the browser to save the cookie. In subsequent communications, the browser attaches the cookie containing the user ID as authentication information.

[0118] The product registration unit 25002 registers 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, in a stock product database 25010.

[0119] The linking registration unit 25003 displays a registration request page in response to a request from an authenticated browser, and performs linking registration between the user ID related to the cookie attached to the registration request received from the browser display of that page and the product data related to the pack ID related to this registration request. When making a registration request, the user operating the browser does not have to go through the trouble of consciously setting a user ID. The user simply operates a logged-in browser to read and send the pack ID.

[0120] The product data monitoring unit 25004 determines whether or not a product is subject to notification based on whether or not the product condition of the product registered in the stockpiled 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 the state where the value of the remaining period until the product expiration date at the monitoring timing is below the set reference value, and products whose item value for the product expiration date reaches the notification criterion are determined to be products to be notified.

[0121] The notification generation unit 25005 generates notification content for a product that meets the notification criteria, addressed to the notification destination described in the user account related to the user ID linked to the product data. If the notification setting is set to receive web push notifications, a notification message is generated that is displayed in a push notification addressed to the endpoint related to the notification setting. If the notification setting is set to not receive web push notifications, a notification email is generated to the email address and a short message is generated to the phone number described in the user account.

[0122] If notification settings are configured to receive Web push notifications, the notification delivery unit 25006 transmits the notification message to the user's browser via a push notification service. Web push notifications use functions provided by the mobile device platform to send notifications to the endpoint browser even when the browser is not displaying the product status management site, thus freeing users from the hassle of having to consciously display the product status management site to monitor product data. Available push notification services include Firebase Cloud Messaging for Chrome and Apple Push Notification Service for Safari.

[0123] If your notification settings are configured not to receive push notifications, a notification email will be sent via an email sending service and a short message will be sent via a short message service.

[0124] The product data viewing support unit 25007 extracts product data in response to a viewing request from the browser of the mobile device of the user who is viewing this site, and generates a viewing information display page in a specified format using information such as the product name searched for in the product master 25009 using the item ID contained in the product data, and sends the page to the browser of 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. If the request does not include a pack ID or a unique ID, product data having the user ID of the user related to the request as the item value of the data item is extracted.

[0125] In response to a cancelation request including information to be cancelled from a browser displaying the cancelation request screen of this site, the cancelation unit 25008 selects one of the product data corresponding to the information to be cancelled from the stockpiled product database in a preset order and cancels it.

[0126] The product master 25009 is a 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.

[0127] The stock product database 25010 stores product data of products related to product packs.

[0128] The user information database 25011 stores user information that constitutes a user account. When a user displays the product status management site of this system from a browser for the first time, the user account creation unit 25012 creates a user account consisting of user information with a user ID, which is newly generated or selected by the user, as a primary key via a user account creation screen presented in the browser of the user's mobile terminal, and saves the notification destination in the notification settings after the user approves or rejects the web push notification. If the web push notification is approved, the destination endpoint is registered in the notification settings as the notification destination. If you want to refuse web push notifications, register the recipient's email address, phone number, etc. as the notification destination in the notification settings.

[0129] (User's mobile device) FIG. 26 is a block diagram showing the functional configuration realized by the user's mobile terminal 19013 in this embodiment in cooperation with the browser displaying the product status management site. The functional configuration includes a registration request unit 26001, a data viewing unit 26002, a deletion request unit 26003, and a notification viewing unit 26004.

[0130] The registration request unit 26001 is a functional component realized by a registration request page of the product status management site displayed in a browser on the user's mobile terminal 19013, and cooperates with the scanner of the mobile terminal to send a registration request including the pack ID read by the user operating the scanner via this registration request screen to the product status management server 19001.

[0131] The data viewing unit 26002 is a functional component realized by a viewing request page displayed in a browser on the user's mobile terminal 19013, and upon receiving a viewing request operation on this page, sends the viewing request to the product status management server 19001 and displays the product data viewing page received from the product status management server in the browser. The viewing request may include a pack ID or unique ID read by the user using a scanner via a viewing request screen displayed in a browser on the user's mobile terminal 19013, or it may not include a pack ID or unique ID for viewing all of the user's stockpiled products.

[0132] The cancellation request unit 26003 receives a cancellation request operation for a cancellation request displayed on the browser of the user's mobile terminal 19013 and transmits the cancellation request to the product status management server 1901 . The cancellation request is a functional component realized by a browser display page launched on the user's mobile terminal 19013, and includes the expiring item ID of the product to be cancelled, which is read by the user operating the scanner via this page. 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 expiration item ID read from the product ID storage means of the product to be cancelled.

[0133] The notification viewing unit 26004 detects a predetermined action taken by the user in response to a notification message of a web push notification, the notification destination of which is a browser launched on the user's mobile terminal 19013, and displays the notification content in the browser on the notification viewing page of this site. The notification viewing page 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 web push notification, but may be sent within the browser display of the product status management site, sent by email to the email address registered when the user account was created, or sent by short message to a similarly registered telephone number, and the notification content may include the unique ID, product name, and product expiration date of the product that is the subject of the notification.

[0134] FIG. 27 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.

[0135] In a product registration step 27001, a worker 19004 at the shipping work area 19002 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 19001, and the product status management server additionally registers the received product data in the stockpiled product database 25010.

[0136] (Stockpile Product Database) FIG. 28 is a block diagram showing the data structure of the product data stored in the stockpile product database 25010. As shown in FIG. The structure includes a unique ID 28001 for individually identifying the product, a pack ID 28002, a sub-pack ID 28003, an item ID 28004, and a product expiration date 28005. 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.

[0137] In a product pack purchase step 27002, the user purchases a product pack at a store 19008. 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.

[0138] In first access step 27003, a user who wishes to use the system operates his / her mobile terminal to read a two-dimensional code that stores link information to the site provided by the operator of the system, thereby obtaining a link to the site and accessing the site.

[0139] In user account creation step 27004, the user account creation unit 25012 displays a user information registration page on the browser of the mobile terminal of the user who is accessing the page for the first time, the user inputs user information, a user account is created based on the input user information, and a web push notification approval page requesting approval of the web push notification is displayed on the user's mobile terminal. In a notification approval step 27005, depending on the user's action on the web push notification approval page from the user account creation unit 25012, approval or rejection of the push notification is returned to the system side. In destination storage step 27006, if the web push notification is approved, the user account creation unit 25012 creates a subscription for the web push notification service, and generates an endpoint that uniquely identifies the combination of the browser and mobile device as the destination of the web push notification. The endpoint is stored as the destination of the user account stored in the user information database 25011. If push notification approval is rejected, at least one of the following will be registered as the notification destination instead of the endpoint: an email address and / or a phone number. In the following explanation, "endpoint, etc." refers to information that will be the notification destination value, including the endpoint, email address, and phone number.

[0140] In pack ID reading step 27007, the user operates the browser display of the registration request page of this site to operate the scanner of the user's mobile terminal and read the pack ID of the purchased product pack. In registration request step 27008, the registration request including the pack ID and authentication information are sent to the system operator via the browser display of the registration request page of this site.

[0141] FIG. 29 is an image diagram of a registration request page displayed on a browser, which constitutes the registration request section. Reference numeral 29000 denotes a registration request page. When the user presses the read button 29001, the scanner on the mobile device is started. When the user points the scanner at the two-dimensional code label storing the pack ID and reads it, the read pack ID is displayed in the pack ID display section 29002. When an action is applied to the registration request button 29003 in this state, a registration request including the read pack ID is sent to the system operator. If a lower-level pack exists here, by sending the pack ID of the higher-level pack, a registration request can be made for the primary product of the higher-level pack and the secondary products contained in the lower-level pack all at once, eliminating the inefficiency of users having to register each product individually as in conventional systems.

[0142] In a link registration step 27009, the link registration unit 25003 links the user ID related to the registration request with the product data related to the pack ID.

[0143] FIG. 30 is a conceptual diagram showing the association between a user ID and product data on the system side. 30001 is product data, and includes in its data item a pack ID 10002. A linking table 30002 stores pairs of values ​​of pack IDs 30003 and user IDs 30004. The user IDs and product data are linked via the pack IDs.

[0144] (Variation of linking registration) FIG. 31 is a diagram showing a modified example of the structure of product data to be registered and a modified example of linking registration in the product data of the same structure. A block diagram 31000 shows the structure of product data when a product is registered. Data items 31001 include a unique ID 31001, a pack ID 31003, a lower pack ID 31004, a user ID 31005, an item ID 31006 and a product expiration date 31007. 31008 is the product data for product A, and the field value for the user ID is "null", i.e. blank. 31009 is the product data for product B, and the field value for the user ID is "null", i.e. blank. 31010 is the product data for product C, and the field value for the user ID is "null", i.e. blank. Therefore, at this point, it is not linked to any user ID. Here, the value of pack ID 31003 is the same, "abc", so it can be seen that although there is a difference between being a primary product and a secondary product, they are constituent products of the same product pack.

[0145] A block diagram 31011 shows the structure of product data after linking and registration. Looking at the item value of the user ID 31012, we can see that "yyx" is registered as the item value of the user ID. The modified example of linking registration is a method of linking registration in which the value of the user ID is registered in the user ID item in this way.

[0146] Returning to the explanation of Figure 27. In viewing request step 27010, the pack ID or unique ID is read as necessary by the user operating his / her mobile device on the viewing request page displayed in the browser, and a viewing request including the read pack ID or unique ID, or a viewing request including neither ID, is sent to the system operator.

[0147] FIG. 32 shows the view request page displayed in a browser. Reference numeral 32000 denotes a view request page. When the user applies an action to read button 32001, the scanner of the mobile terminal is started. When the user points the scanner at the two-dimensional code label storing the product ID or the two-dimensional code label storing the pack ID, the read ID is displayed in unique ID list display section 32002 or pack ID list display section 32003. When an action is applied to view request button 32004 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 the user's user ID will be sent.

[0148] In a browse information creation step 27011, the product data browse support unit 25007 extracts product data in response to a browse request from the user's mobile terminal, and generates a browse information display page 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 user ID of the user related to the browse request as the item value of the data item is extracted.

[0149] In a browse information delivery step 27012, the product data browse support unit 25007 transmits a browse information display page to the user's mobile terminal.

[0150] In a stock browsing step 27013, a browse information display page is displayed on the browser of the user's portable terminal.

[0151] FIG. 33 shows an example of a data browsing page displayed on the browser of a user's mobile terminal. A data viewing page 33000 displays a product data list 33002 having items 33001 such as a unique ID, a product name, and a product expiration date.

[0152] In a product consumption step 27014, the product is consumed by the user or the like. In a unique ID reading step 27015, the unique ID of the product to be cancelled is read by the user operating the scanner via the cancellation request page displayed on the browser. In a cancellation request step 27016, a cancellation request including the read unique ID is sent to the system operator side by the user through a cancellation request page displayed on the browser.

[0153] FIG. 34 shows an example of a reconciliation request page displayed on a browser on the user's mobile terminal. Cancellation request page 34000 displays product data 34001, with items such as expiry item ID, product name, and product expiry date. When cancelling the displayed product data, an action is added to cancellation request button 34002, and a cancellation request is sent to the system operator. It is configured so that adding an action to cancel button 34003 allows the cancellation request to be cancelled.

[0154] In the product data deletion step 27017, the deletion unit 25008 that received the deletion request deletes data selected from the product data having the unique ID included in the deletion request as its item value. If there are multiple data with the unique ID to be deleted, the data that was registered in the stockpile product database earlier is selected, but the method of selecting the deletion target that can be adopted in the present invention is not limited to this, and can be changed as appropriate as long as it is a method in which one or multiple data corresponding to the deadline item ID related to the deletion request are deleted.

[0155] In a product data monitoring step 27018, the product data is monitored at a predetermined cycle by the product data monitoring unit 25004. If none of the product data meets the notification criteria, the process proceeds to a waiting step 27019, 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 27020 .

[0156] 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.

[0157] In the notification information generation step 27021, the notification generation unit 25005 For products that meet the notification criteria, notification content is generated with the notification destination listed in the user account related to the user ID linked to that product data. If notification settings are configured to receive web push notifications, the notification message to be displayed in the push notification is generated as the notification content. If the notification settings are configured not to receive push notifications, a notification email sent to the email address listed in the user account and a short message sent to the phone number are generated as notification content. Here, the notification contents are notification information display data that display the unique ID, product name, and product expiration date, generated by referring to the product data that meets the notification criteria and the product master 25009.

[0158] In notification step 27022, if notification settings have been made to receive web push notifications by the notification distribution unit 25006, the notification is executed. If an email address, phone number, or the like is saved in the contacts with notification settings to reject web push notifications, notification is executed by email or short message.

[0159] In notification viewing step 27023, when the user takes an action on the notification message displayed on the browser of the user's portable terminal, the page moves to a notification contents page of this site, and the notification information is displayed on the browser. If an email address, telephone number, etc. is saved in the contacts with notification settings that reject web push notifications, the user can view email notifications and short message notifications by operating the mobile device.

[0160] FIG. 35 is an example of a notification information display screen that changes over time. Notification information display screen 35001 is the notification information display screen for February 1, 2025. The diagonal shading in the display frame for "Curry A" shown in 35002 and the display frame for "Stew B" shown in 35003 indicates a pink notification display notifying that the product expiration date is less than March. The frame for "Rice C" 35004 shows no notification because these do not meet the notification criteria. 35005 is a purchase support button, which is set up so that by the user taking action on the purchase support 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. Notification information display screen 35006 is the notification information display screen for March 1, 2025. The vertical shading in the display frame of "A Curry" shown in 35007 indicates a red display notifying that the product expiration date is less than January. The diagonal shading in the display frame of "Stew B" 35008 and the frame of "C Rice" 35009 is a pink notification display indicating that the product expiration date is less than March. 35010 is a purchase support button similar to 35005. Notification information display screen 35011 is the notification information display screen for April 1, 2025. The horizontal shading in display frame 35012 for "A Curry" is a gray display indicating that the product has expired. The vertical shading in display frame 35013 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 35014 is a pink notification display indicating that the product has less than three months left until its expiration date. 35015 is a purchase support button similar to 35005. 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.

[0161] 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

[0162] The fourth embodiment is an example of product status management by the product status management system in the case where the product pack in the third embodiment is acquired not from a store but from online such as an EC.

[0163] FIG. 36 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 relating to store sales shown in FIG. 19 are given the same reference numerals and their explanations are omitted.

[0164] The registered product pack 36003 delivered to the delivery system 36001 is delivered to the user's home 19011 by a delivery person 36002. The product pack 36003 received by the user 1910 is stored in the user's home 1911. The product pack received by the user and the stockpiled product pack are assigned different reference numbers for convenience since they are at different chronological positions in the distribution process, but are the same product pack.

[0165] 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 third embodiment can be achieved by using the same system operations and user operations as in the third embodiment. [Industrial Applicability]

[0166] The present invention can be applied to product dealers and home users who stockpile products to manage the expiration dates of products at the stockpiling location. [Explanation of symbols]

[0167] 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 user's mobile terminal on which a predetermined application is installed, a) a product ID storage means for storing a unique ID that is attached to the product packaging or the product itself and that individually identifies 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 constituent products themselves; c) a stockpiled product database storing product data including, as data items, a pack ID of a pack in which the product is included, the unique ID, 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 pack ID storage means of the pack related to the user's acquisition and for transmitting acquisition information including the pack ID and authentication information of the user; e) a linking registration means for receiving the acquisition information and the authentication information and registering a link between a user ID related to the authentication information and product data having the pack ID as an item value; f) a notification means for monitoring the product status including the product expiration date according to a predetermined monitoring schedule, and notifying a notification destination associated with the user ID when a preset notification criterion is met; A system comprising the above as a system configuration.

2. The system described in claim 1, characterized in that the application is a dedicated product status management app prepared by the operator of the product status management system for downloading by the user, and the user ID is at least one selected from ID information generated as an identifier uniquely identifying the user when the user downloads the app to their mobile device and creates a user account, a username, an email address, and a telephone number registered by the user themselves.

3. The system described in claim 1, characterized in that the application is a browser that displays a product status management site provided by the operator of the product status management system, and the user ID is ID information generated or selected as an identifier that uniquely identifies the user and is registered in a user account created when the user logs in to the product status management site for the first time.

4. 2. The system according to claim 1, wherein the pack ID is an ID that identifies a pack having a common combination of the unique IDs of products that constitute the pack.

5. 2. The system of claim 1, wherein the pack ID is an ID that uniquely identifies the pack and specifies a unique pack.

6. 2. The system of claim 1, wherein the pack includes subpacks as its components.

7. The system according to claim 1 , wherein the notification is a push notification whose notification destination is an application related to the user ID.

8. The system according to claim 1, characterized in that the product 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.

9. 2. The system according to claim 1, wherein said product 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.

10. The system according to 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.

11. 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.

12. The system described in claim 1, characterized in that the pack ID, unique ID and product expiration date included in the data items of the product data are registered in accordance with the installation of the product ID storage means and the pack ID storage means.

13. 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.

14. 2. The system according to claim 1, wherein the stockpiled commodity database is provided within a memory of the mobile terminal.

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

16. 2. The system according to claim 1, wherein said product ID storage means is a wireless tag, and said attachment is performed by attaching a seal, box or label incorporating said wireless tag, or by hanging said wireless tag around a bottleneck incorporating said wireless tag.

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

18. 2. The system according to claim 1, wherein said pack ID storage means is a wireless tag, and said attachment is a seal, box or label incorporating said wireless tag, or a hanging around a bottleneck incorporating said wireless tag.

19. The system configuration further includes: 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; 2. The system of claim 1, comprising:

Images