WO2021014931A1

WO2021014931A1 - System

Info

Publication number: WO2021014931A1
Application number: PCT/JP2020/026127
Authority: WO
Inventors: 平本　雅祥; 村上　和宏; 直紀杉村; 広義大宮; 敏之尾上; 巌徹松井; 幸　裕弘
Original assignee: パナソニックＩｐマネジメント株式会社
Priority date: 2019-07-22
Filing date: 2020-07-03
Publication date: 2021-01-28
Also published as: JP2021018633A; CN114127774A

Abstract

This system that prompts a user to purchase a good comprises: a specification unit that specifies the purchase frequency at which the user purchases the good; a prediction unit that, on the basis of the purchase frequency specified by the specification unit, predicts the timing at which the user will next purchase the good; and a notification unit that, on the basis of the timing predicted by the prediction unit, prompts the user to purchase the good.

Description

system

This disclosure relates to a system that encourages users to purchase products.

Patent Document 1 discloses a system that manages the inventory of ingredients stored in a refrigerator using a mobile terminal and proposes to the user a menu using ingredients whose expiration date is near.

In addition, the user can grasp the inventory of products by using the inventory list showing the inventory of products such as foodstuffs. As a result of checking the inventory list by the user, if the inventory of a certain product is low, the user can determine that the product needs to be additionally purchased.

However, in the case of the conventional system, in order for the user to notice that an additional purchase of the product is necessary, the user himself has to check the inventory list. In other words, if the user forgot to check the inventory list, the user could not realize that an additional purchase of the item was necessary.

This disclosure provides a mechanism that can make the user aware that an additional purchase of a product is necessary.

Japanese Unexamined Patent Publication No. 2008-084102

The system provided by the present disclosure is a specific unit that specifies the purchase frequency at which the user purchases a product, and a prediction unit that predicts when the user will purchase the product next based on the purchase frequency specified by the specific unit. And a notification unit that prompts the user to purchase the product based on the timing predicted by the prediction unit.

FIG. 1 is a diagram showing a configuration of a mobile terminal 100. FIG. 2 is a diagram showing the configuration of the server 200. FIG. 3 is a flowchart showing a process executed by the mobile terminal 100. FIG. 4 is a flowchart showing a process executed by the server 200. FIG. 5 is a diagram showing a food material database 500. FIG. 6 is a flowchart showing a process executed by the server 200. FIG. 7 is a diagram showing a notification event database 700. FIG. 8 is a flowchart showing a process executed by the server 200. FIG. 9 is a flowchart showing a process executed by the mobile terminal 100. FIG. 10 is a diagram showing the configuration of the refrigerator 1000. FIG. 11 is a diagram showing a weight management database 1100. FIG. 12 is a flowchart showing a process executed by the refrigerator 1000. FIG. 13 is a flowchart showing a process executed by the server 200.

Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. It should be noted that the following embodiments do not limit the invention according to the claims, and not all combinations of features described in the embodiments are essential for the means for solving the invention.

(Embodiment 1)
The system of this embodiment is composed of a mobile terminal 100 owned by a user and a server 200 on a network such as the Internet. The user uses the camera of the mobile terminal 100 to read a code such as a barcode or QR code (registered trademark) attached to the food material. The server 200 predicts the demand for foodstuffs based on the reading status of the mobile terminal 100, and prompts the user to purchase the product according to the prediction result. Hereinafter, the present embodiment will be described in detail.

FIG. 1 is a diagram showing the configuration of the mobile terminal 100. The mobile terminal 100 is, for example, a smartphone or a tablet terminal, and is an example of an information device. The control unit 101 controls the operation of the mobile terminal 100. The control unit 101 has at least a processor, and the control unit 101 controls the operation of the mobile terminal 100 by reading and executing a control program stored in the memory 102 described later. The memory 102 is a non-volatile storage medium for storing various data such as a control program, and is, for example, a flash memory. The display unit 103 is a touch panel, displays information such as images and moving images, and receives instructions from the user by touch operation. The communication unit 104 is an interface for the mobile terminal 100 to communicate with an external device. The communication unit 104 is a wireless communication based on a wireless LAN standard such as IEEE802.11a / b / g / n / ac, a radio based on a 4th generation mobile communication system (commonly known as 4G) or a 5th generation mobile communication system (commonly known as 5G). Perform communication. The camera 105 has a photographing function and a reading function for reading a code such as a barcode or a QR code.

FIG. 2 is a diagram showing the configuration of the server 200. The control unit 201 controls the operation of the server 200. The control unit 201 has at least a processor, and the control unit 201 controls the operation of the server 200 by reading and executing a control program stored in the memory 202 described later. The memory 202 is a non-volatile storage medium for storing various data such as a control program and a food material database 500 described later, and is, for example, an HDD (hard disk drive). The communication unit 203 is an interface for the server 200 to communicate with an external device. The communication unit 203 executes wireless communication based on a wireless LAN standard such as IEEE802.11a / b / g / n / ac or wired LAN communication based on Ethernet (registered trademark).

Next, the process executed by the mobile terminal 100 will be described using the flowchart of FIG. Each step shown in the flowchart of FIG. 3 is a process realized by the control unit 101 of the mobile terminal 100, and is realized by the processor of the control unit 101 reading and executing the control program stored in the memory 102. To.

First, in step 301, the mobile terminal 100 determines whether or not the code has been read by the camera 105. In the present embodiment, a code such as a bar code or a QR code is added to the food material. This code includes identification information such as a food material ID (identification) described later, and the mobile terminal 100 reads the code using the camera 105 and analyzes the read code to acquire the identification information. To do. The fact that the code is attached to the food material indicates a mode in which a sticker on which the code is printed is attached to the food material itself, a mode in which the code is printed on a bag for packaging the food material, and the like. When the mobile terminal 100 determines that the code has been read in step 301 (Yes in step 301), the process proceeds to step 302. On the other hand, if the code has not been read (No in step 301), the mobile terminal 100 waits until the code is read.

Next, in step 302, the mobile terminal 100 determines whether or not the foodstuff can be specified based on the read code. In the present embodiment, the mobile terminal 100 transmits the foodstuff ID acquired from the code to the server 200, and identifies the foodstuff by receiving the response from the server 200. The process executed by the server 200 will be described later. When the mobile terminal 100 determines that the foodstuff can be specified (Yes in step 302), the process proceeds to step 303. On the other hand, if the mobile terminal 100 determines that the foodstuff cannot be specified (No in step 302), the process proceeds to step 305. When the foodstuff cannot be specified, the response from the server 200 is not available for a predetermined time (for example, 1 minute), or the response from the server 200 is "no corresponding record".

Next, step 303 will be described. In step 303, the mobile terminal 100 registers the specified foodstuff in the inventory list managed by the mobile terminal 100. The inventory list is a list that stores information such as the name of the food, the type of the food, the date and time when the storage was started, the storage expiration date, and the remaining amount for each of the plurality of foods. The response received by the mobile terminal 100 from the server 200 includes a food material name, a food material type, a storage period, and a storage location, and registration to the inventory list is executed using these information. The date and time when the ingredients are registered in the inventory list is automatically registered as the "date and time when the storage is started" in the inventory list. In addition, the "retention date" of the inventory list is automatically calculated and registered from the date and time when the foodstuff is registered in the inventory list, when the "retention period" included in the response from the server 200 has passed. .. The "retention period" included in the response from the server 200 may be used as it is in the calculation of the "retention period date", or a period shorter than the "retention period" included in the response from the server 200. For example, two-thirds of the period may be used to calculate the "retention date". By checking this inventory list, the user can check what kind of food is at home. In addition, the user can easily grasp the ingredients whose storage expiration date is near.

In the following description, the inventory list will be described as being stored by the mobile terminal 100, but the inventory list may be stored by the server 200. In this case, the mobile terminal 100 may acquire the latest inventory list from the server 200 at a predetermined timing (for example, the timing when an operation for displaying the inventory list is input to the mobile terminal 100).

Next, in step 304, the mobile terminal 100 notifies the user of the storage location of the specified foodstuff. The mobile terminal 100 notifies the user to store the foodstuff in the storage location based on the storage location information included in the response received from the server 200. As will be described in detail later, if the specified ingredient is radish, the mobile terminal 100 displays a notification screen prompting the user to store the radish in the refrigerator's refrigerator compartment. In addition to displaying the notification screen, the mobile terminal 100 may notify the user of the storage location of the food material by using another method, for example, a voice message. Further, when the mobile terminal 100 instructs the smart speaker having the communication function, the smart speaker may notify the storage location of the food material by a voice message. Further, the mobile terminal 100 may instruct the refrigerator provided with the communication function to display a notification screen in which the refrigerator notifies the user of the storage location of the foodstuff, and the refrigerator is the storage location of the foodstuff. May be notified by voice message. The process of step 304 allows the user to store the food in an appropriate storage location.

Next, step 305 will be described. In step 305, the mobile terminal 100 causes the user to input information necessary for registering in the inventory list. Specifically, the mobile terminal 100 displays an input screen for allowing the user to input the food material name, the food material type, and the storage expiration date. As for the date and time when the storage is started, the input screen for inputting the storage expiration date may be displayed with the date and time when the foodstuff is registered in the inventory list automatically set. Next, in step 306, the mobile terminal 100 registers the information input by the user in the inventory list.

Next, the process executed by the server 200 will be described using the flowchart of FIG. Each step shown in the flowchart of FIG. 4 is a process realized by the control unit 201 of the server 200, and is realized by the processor of the control unit 201 reading and executing the control program stored in the memory 202. ..

First, in step 401, the server 200 determines whether or not the food material ID has been received. When the server 200 determines that the food ID has been received (Yes in step 401), the process proceeds to step 402. In the present embodiment, the server 200 receives the food material ID from the mobile terminal 100. On the other hand, when the foodstuff ID is not received (No in step 401), the server 200 waits until the foodstuff ID is received.

Next, in step 402, the server 200 determines whether or not there is a record corresponding to the received foodstuff ID in the foodstuff database 500 shown in FIG. The food material database 500 is information stored in the memory 202 of the server 200, and is a database that stores the food material name, the type of food material, the storage period, and the storage location for each of the plurality of food materials. For example, paying attention to a record having a food ID of 003, it is defined that the food name is radish, the food type is vegetables, the storage period is 3 days, and the storage location is a refrigerator. When the server 200 determines that there is a record corresponding to the received food material ID (Yes in step 402), the process proceeds to step 403. On the other hand, if the server 200 determines that there is no record corresponding to the received food material ID (No in step 402), the process proceeds to step 405.

Next, step 403 will be described. In step 403, the server 200 responds to the mobile terminal 100 with the information of the record corresponding to the foodstuff ID. The record information corresponding to the food material ID is, specifically, as shown in FIG. 5, the food material name, the type of food material, the storage period, and the storage location. Based on this information, the processes described in steps 303 and 304 of FIG. 3 are executed in the mobile terminal 100. For example, when the information transmitted to the mobile terminal 100 in step 403 is the information of the 003 record of the food material database 500 shown in FIG. 5, the radish information is registered in the inventory list in the mobile terminal 100, and the foodstuff ID is registered in the inventory list. , The user is notified that the storage location of the radish is the refrigerator compartment. Further, when the information transmitted to the mobile terminal 100 in step 403 is the information of the record whose foodstuff ID is 005, the potato information is registered in the inventory list in the mobile terminal 100, and the potato storage location is in a cool and dark place. The user is notified that there is. According to step 403 of FIG. 4 and step 304 of FIG. 3, the user can grasp a storage location suitable for the food material and store the food material by an appropriate storage method. It can be seen that the refrigerating room, the freezing room, the vegetable room, and the partial room in the food material database 500 of FIG. 5 correspond to the storage room of the refrigerator, respectively, and the storage room of the refrigerator is included as a candidate for the storage place. Further, the cool and dark place in FIG. 5 indicates the outside of the refrigerator, and is sometimes called room temperature.

Next, in step 404, the server 200 executes the demand forecast processing. This demand forecast processing will be described later with reference to the flowchart of FIG.

Next, step 405 will be described. In step 405, the server 200 responds to the mobile terminal 100 with "no corresponding record". Upon receiving this response, the mobile terminal 100 executes the processes described in steps 305 and 306 of FIG.

Next, how to utilize the inventory list managed by the mobile terminal 100 will be described. When performing a menu search on the mobile terminal 100, only menus that use ingredients with a near expiration date may be searched, or menus that use ingredients with a near expiration date may be searched so as to be higher than other menus. The result may be displayed. Further, the mobile terminal 100 may urge the user to use the food material when the storage expiration date is approaching.

Next, the demand forecast processing executed by the server 200 will be described with reference to the flowchart of FIG. Each step shown in the flowchart of FIG. 6 is a process realized by the control unit 201 of the server 200, and is realized by the processor of the control unit 201 reading and executing the control program stored in the memory 202. ..

First, in step 601 the server 200 stores the date and time when the code is read for the foodstuff indicated by the foodstuff ID received in step 401. In the present embodiment, the date and time when the food material ID is received in step 401 is set as the code reading date and time. The server 200 stores the reading date and time of the code for each of the plurality of foodstuffs.

Next, in step 602, the server 200 determines whether or not the demand for the food material can be predicted based on the stored reading date and time. In the present embodiment, the server 200 determines whether or not there is regularity in the frequency with which the user purchases a certain foodstuff, and predicts the demand according to the regularity.

In the present embodiment, for example, if the purchase frequency of three out of the last four purchases of a certain foodstuff is the same, the server 200 determines that the purchase frequency of the foodstuff is regular. More specifically, for example, for beef whose foodstuff ID is 007 in the foodstuff database 500 of FIG. 5, the latest four reading dates and times were 4 days, 4 days, 3 days, and 4 days after the previous code reading. To do. It can be said that the last four purchases are four days, four days, three days, and four days after the previous purchase date. In this case, the server 200 can predict that the beef purchase frequency is every 4 days and the next beef demand (in other words, the next beef purchase) is 4 days later. When the server 200 determines that the demand for the food material can be predicted in step 602 (Yes in step 602), the process proceeds to step 603. On the other hand, if the server 200 determines that the demand for the food material cannot be predicted (No in step 602), the server 200 ends the demand forecasting process.

Next, step 603 will be described. In step 603, the server 200 registers the notification event according to the demand forecast result. For example, in the beef case described above, the server 200 predicts that the next beef demand will be four days later. In this case, the server 200 registers a notification event in the notification event database 700 of FIG. 7 so as to prompt the user to purchase beef four days later in the morning (for example, 7:00 am). The notification event database 700 of FIG. 7 is information stored in the memory 202 of the server 200, and stores events to be notified to the user. In FIG. 7, a record having an event ID (identification) of 003 is a notification event registered to prompt the user to purchase beef in the morning four days later. The notification date and notification time of the notification event database 700 can be changed by the user.

Next, using the flowchart of FIG. 8, a process in which the server 200 prompts the user to purchase foodstuffs according to the information registered in the notification event database 700 will be described. Each step shown in the flowchart of FIG. 8 is a process realized by the control unit 201 of the server 200, and is realized by the processor of the control unit 201 reading and executing the control program stored in the memory 202. ..

First, in step 801 the server 200 determines whether or not the notification timing has been reached. The server 200 specifies the current date and time. Then, when the specified current date and time reaches the notification date and the notification time of any of the notification events registered in the notification event database 700, the server 200 determines that the notification timing has been reached in step 801 (). Yes) in step 801), the process proceeds to step 802. On the other hand, when the notification timing has not been reached (No in step 801), the server 200 waits until the notification timing is reached.

Next, step 802 will be described. In step 802, the server 200 transmits a notification prompting the purchase of the food material that has reached the notification timing to the mobile terminal 100. For example, if the current date and time is 7:00 am on July 26, 2019, the server 200 determines that the beef with the ingredient ID 007 has reached the notification timing, and the server 200 carries a notification prompting the purchase of the beef. Send to terminal 100.

Next, using the flowchart of FIG. 9, the process executed by the mobile terminal 100 that has received the notification prompting the purchase of the foodstuff will be described. Each step shown in the flowchart of FIG. 9 is a process realized by the control unit 101 of the mobile terminal 100, and is realized by the processor of the control unit 101 reading and executing the control program stored in the memory 102. To.

First, in step 901, the mobile terminal 100 determines whether or not a notification prompting the purchase of foodstuffs has been received from the server 200. When the mobile terminal 100 determines that the notification prompting the purchase of the food material has been received from the server 200 (Yes in step 901), the process proceeds to step 902. On the other hand, when the notification prompting the purchase of the food material has not been received from the server 200 (No in step 901), the mobile terminal 100 waits until the notification is received.

Next, in step 902, the mobile terminal 100 prompts the user to purchase foodstuffs according to the notification received from the server 200. For example, if the server 200 sends a notification prompting the purchase of beef to the mobile terminal 100, the mobile terminal 100 displays a notification screen prompting the user to purchase beef. In addition to displaying the notification screen, the mobile terminal 100 may urge the user to purchase foodstuffs by using another method, for example, a voice message. Further, when the mobile terminal 100 instructs the smart speaker having the communication function, the smart speaker may prompt the user to purchase the foodstuff. The user can be aware that the purchase of the foodstuff is necessary because the purchase of the foodstuff is prompted based on the predicted result of the demand of the foodstuff.

In the system of the present embodiment, the timing at which the user purchases the product next is predicted based on the specific unit that specifies the purchase frequency for the user to purchase the product and the purchase frequency specified by the specific unit. It may be configured to include a prediction unit and a notification unit that prompts the user to purchase a product based on the timing predicted by the prediction unit. The display unit 103 of the mobile terminal 100 is an example of a notification unit that notifies the user of the storage location specified by the specific unit. The system may be configured to include a registration unit that registers information obtained by reading the code attached to the product by the camera of the mobile terminal 100 in the inventory list. The specifying unit may specify the purchase frequency based on the date and time when the code is read by the camera 105 of the mobile terminal 100.

Note that the process executed by the mobile terminal 100 described in the flowcharts of FIGS. 3 and 9 may be realized by installing an application on the mobile terminal 100.

(Embodiment 2)
Next, a system that prompts the user to purchase additional foodstuffs by using a weight sensor that detects the weight of the foodstuffs will be described. The system of the present embodiment includes a mobile terminal 100 owned by a user, a server 200 on a network such as the Internet, and a refrigerator 1000. The mobile terminal 100 and the server 200 have the same configuration as that described in the first embodiment, and carry out the same processing as the processing described in the first embodiment. Hereinafter, the differences from the first embodiment will be mainly described.

FIG. 10 is a diagram showing the configuration of the refrigerator 1000. Refrigerator 1000 has a plurality of storage chambers such as a refrigerator compartment, a freezer compartment, and a vegetable compartment. The refrigerator 1000 cools each storage chamber to a target temperature by a refrigerating cycle composed of a compressor, a cooler, and the like (not shown in FIG. 10). The refrigerator 1000 is an example of a storage for storing foodstuffs.

The control unit 1001 controls the operation of the refrigerator 1000. The control unit 1001 has at least a processor, and the processor reads and executes a control program stored in the memory 1002 described later, so that the control unit 1001 controls the operation of the refrigerator 1000. The memory 1002 is a non-volatile storage medium for storing various data such as a control program, and is, for example, a flash memory. The communication unit 1003 executes wireless communication based on a wireless LAN standard such as IEEE802.11a / b / g / n / ac. The weight sensor 1004 is a sensor that detects the weight. As will be described in detail later, the refrigerator 1000 is provided with a plurality of weight sensors in a door pocket, a shelf, or the like.

FIG. 11 is a diagram showing a weight management database 1100 stored in the memory 202 of the server 200. The weight management database 1100 is for the server 200 to manage the storage state of the foodstuffs stored in the refrigerator 1000 based on the detection result of the weight sensor 1004 of the refrigerator 1000.

The refrigerator 1000 of the present embodiment is provided with three weight sensors indicated by sensor IDs (identification) 001 to 003 in the door pockets (door pockets 1 to 3). Further, the refrigerator 1000 includes a plurality of shelves. One shelf out of the plurality of shelves is provided with four areas (shelf 1 to shelf 4) corresponding to each of the four weight sensors indicated by sensor IDs 004 to 007. The number of weight sensors and the number of areas corresponding to the weight sensors are merely examples, and are not limited to the numbers described in the present embodiment. In the case of the weight management database 1100 of FIG. 11, it can be seen that apple juice having a weight of 100 g is placed in the door pocket 3 corresponding to the weight sensor of the sensor ID 003. In addition, the weight management database 1100 also stores past weight transitions.

There are two possible methods for the server 200 to identify what kind of foodstuff is placed in the area where the weight sensor exists. The first method is a method in which the user manually sets a method of storing foodstuffs in the refrigerator 1000 using the mobile terminal 100. In the case of this method, the user inputs the information that "apple juice is stored in the door pocket 3" to the mobile terminal 100, and the mobile terminal 100 notifies the server 200 of the information input by the user.

The second method is a method in which the server 200 automatically identifies the stored state of the foodstuff based on the user reading the code attached to the foodstuff using the mobile terminal 100 and the detection result of the weight sensor. Is. For example, suppose a user uses a mobile terminal 100 to read a code attached to apple juice and places the apple juice in the door pocket 3 of the refrigerator 1000. At this time, the mobile terminal 100 notifies the server 200 of the foodstuff ID read from the code. Further, when the refrigerator 1000 notifies the server 200 that the weight detected by the weight sensor having the sensor ID of 003 has been changed, the server 200 can determine that the apple juice is placed in the door pocket 3.

Next, the process executed by the refrigerator 1000 will be described using the flowchart of FIG. Each step shown in the flowchart of FIG. 12 is a process realized by the control unit 1001 of the refrigerator 1000, and is realized by the processor of the control unit 1001 reading and executing the control program stored in the memory 1002. ..

First, in step 1201, the refrigerator 1000 determines whether or not there is a change in the detection result of the weight sensor 1004. If the refrigerator 1000 determines that the detection result of the weight sensor 1004 has changed (Yes in step 1201), the process proceeds to step 1202. On the other hand, if there is no change in the detection result of the weight sensor 1004 (No in step 1201), the refrigerator 1000 stands by.

Next, in step 1202, the refrigerator 1000 transmits the weight information to the server 200. The weight information is information indicating the sensor ID of the weight sensor whose detection result has changed and the weight detected by the weight sensor.

Next, the process executed by the server 200 will be described using the flowchart of FIG. Each step shown in the flowchart of FIG. 13 is a process realized by the control unit 201 of the server 200, and is realized by the processor of the control unit 201 reading and executing the control program stored in the memory 202. ..

First, in step 1301, the server 200 determines whether or not the weight information has been received from the refrigerator 1000. When the server 200 receives the weight information from the refrigerator 1000 (Yes in step 1301), the process proceeds to step 1302. On the other hand, if the server 200 has not received the weight information (No in step 1301), the server 200 waits.

Next, in step 1302, the server 200 updates the weight management database 1100 according to the weight information received from the refrigerator 1000.

Next, in step 1303, the server 200 estimates the usage status of the foodstuff based on the information managed by the weight management database 1100, and determines whether or not it is necessary to prompt the user to purchase additional foodstuffs. If the server 200 determines that the user needs to be prompted to purchase additional ingredients (Yes in step 1303), the process proceeds to step 1304. On the other hand, when the server 200 determines that it is not necessary to prompt the user to purchase additional ingredients (No in step 1303), the server 200 ends the process shown in the flowchart of FIG.

Step 1303 will be specifically described. In the present embodiment, for example, the server 200 calculates the average value of the weight changes of a certain food material four times, and if the remaining amount of the food material is equal to or less than the calculated average value, prompts the user to purchase an additional food material. The server 200 determines that it is necessary. Focusing on the weight sensor having the sensor ID of 003 in FIG. 11, the average value of the weight changes of the last four times is 100 g, and the remaining amount of the food material detected by the weight sensor is 100 g. In this case, since the remaining amount of the foodstuff is equal to or less than the calculated average value, the server 200 determines that it is necessary to prompt the user to purchase additional foodstuff. As is clear from FIG. 11, the past weight transition may increase as well as decrease. This corresponds to the case where the user purchases a new ingredient because the stock is exhausted, or the case where the user purchases a new ingredient by discarding the old ingredient. In order to pay attention to the amount used by the user, when the server 200 calculates the average value of the weight change of the food material in the last N times (N is a natural number) in step 1303, only the value of the case where the weight is reduced is used. It is desirable to use it.

Next, step 1304 will be described. In step 1304, the server 200 transmits a notification prompting the purchase of the food material to the mobile terminal 100. For example, in the above case, the server 200 transmits a notification prompting the purchase of the food material corresponding to the weight sensor having the sensor ID of 003, that is, apple juice, to the mobile terminal 100. Upon receiving this notification, the mobile terminal 100 executes the process described with reference to FIG. For the user, the next time he / she uses the food, he / she will be prompted to purchase the food that may be insufficient due to the low remaining amount, so that the food can be additionally purchased at an appropriate timing.

(Modification example)
The target for which the server 200 prompts the user for additional purchase is not limited to the foodstuff. The above-described embodiment can be applied not only to foodstuffs but also to various products including consumables such as detergents used in dishwashers or washing machines.

Further, when the server 200 prompts the user to purchase a product, the user may be prompted to purchase a similar product similar to the product instead of the product, or the user may purchase both the product and the similar product. May be urged to. The similar product corresponds to, for example, if the product is a frozen food of a certain manufacturer, the newly released frozen food of the manufacturer is applicable.

Further, in the above-described embodiment, the server 200 prompts the user to purchase an additional product, but the server 200 may automatically order the purchase of the product from the store instead of prompting the user to purchase the product. .. Further, in the case of automatic ordering, it is desirable to consider the delivery time and place an order at an earlier timing (for example, one day before) than the above-described embodiment.

100 Mobile terminal 101 Control unit 102 Memory 103 Display unit 104 Communication unit 105 Camera 200 Server 201 Control unit 202 Memory 203 Communication unit 500 Foodstuff database 700 Notification event database 1000 Refrigerator 1001 Control unit 1002 Memory 1003 Communication unit 1004 Weight sensor 1100 Weight management database

Claims

A specific part that identifies the purchase frequency at which the user purchases the product,
A prediction unit that predicts when the user will purchase the product next based on the purchase frequency specified by the specific unit.
A notification unit that prompts the user to purchase the product based on the timing predicted by the prediction unit.
System with.
It also has a registration unit that registers information obtained by reading the code attached to the product by the camera of the mobile terminal in the inventory list.
The specific unit specifies the purchase frequency based on the date and time when the code is read by the camera of the mobile terminal.
The system according to claim 1.
The product is an ingredient
In the inventory list, at least the ingredient name of the ingredient and the shelf life of the ingredient are managed.
The system according to claim 2.
By reading the code, the mobile terminal acquires the identification information of the foodstuff and obtains the identification information of the foodstuff.
The system notifies the user of a suitable storage location for the foodstuff based on the identification information.
The system according to claim 3.
Candidate storage locations suitable for the ingredients include at least a refrigerator storage room.
The system according to claim 4.
Candidate storage locations suitable for the ingredients further include cool and dark places.
The system according to claim 5.
The code is a barcode or a QR code.
The system according to any one of claims 2 to 6.