JP7274562B2 - Shopping support device, shopping support method and program - Google Patents

Description

TECHNICAL FIELD Embodiments of the present invention relate to a shopping support device, a shopping support method, and a program.

A shopping list application (hereinafter referred to as "list application") is known that can create a shopping list by registering products to be purchased. The list application has a function that can indicate whether or not each registered product has been purchased based on the user's operation or the like. Among such list applications, there are those in which products with multiple names can be registered. In some cases, a linking dictionary that associates a plurality of names is used so that even if a name other than the name registered in the list application is input, the product can be marked as purchased. However, creating and updating the associated dictionary is troublesome because it relies on manual input.

JP 2015-166935 A

A problem to be solved by the embodiments of the present invention is to provide a shopping support device, a shopping support method, and a program that reduce the trouble of creating and updating a linking dictionary.

A shopping support device according to an embodiment includes a storage unit, an interface, and a control unit. The storage unit stores a linking dictionary that associates a first name with a second name and a plurality of shopping lists. The interface obtains a second name of the item purchased based on a first shopping list included in the plurality of shopping lists and including a first name of the item. The control unit extracts a second shopping list of a plurality of users who have purchased the product from the plurality of shopping lists, and extracts a third shopping list including the first name from the second shopping list. and if the third shopping list exists, associating the first name with the second name based on a ratio of the number of the second shopping list to the number of the plurality of shopping lists. Update the linking dictionary.

1 is a block diagram showing an example of a support system according to an embodiment and an example of a circuit configuration of main parts of components included in the support system; FIG. 1 is a block diagram showing an example of a support system according to an embodiment and an example of a circuit configuration of main parts of components included in the support system; FIG. The figure which shows an example of the member table contained in member DB in FIG. The figure which shows an example of the list table contained in list DB in FIG. The figure which shows an example of the registration table contained in list DB in FIG. FIG. 2 is a diagram showing an example of a dictionary table included in a dictionary DB in FIG. 1; FIG. 2 is a diagram showing an example of record configuration of a relation table included in a relation DB in FIG. 1; The figure which shows an example of record structure of the goods table contained in goods DB in FIG. FIG. 2 is a diagram showing an example of record configuration of a history table included in a history DB in FIG. 1; FIG. 3 is a flow chart of processing by a processor of the user terminal in FIG. 2; FIG. FIG. 3 is a flow chart of processing by a processor of the user terminal in FIG. 2; FIG. FIG. 3 is a flow chart of processing by a processor of the user terminal in FIG. 2; FIG. FIG. 3 is a flow chart of processing by a processor of the user terminal in FIG. 2; FIG. FIG. 3 is a flow chart of processing by a processor of the user terminal in FIG. 2; FIG. FIG. 3 is a flow chart of processing by a processor of the user terminal in FIG. 2; FIG. FIG. 3 is a flow chart of processing by a processor of the user terminal in FIG. 2; FIG. 2 is a flow chart of processing by a processor of the support server in FIG. 1; 2 is a flow chart of processing by a processor of the support server in FIG. 1; 2 is a flow chart of processing by a processor of the support server in FIG. 1; 3 is a flowchart of processing by a processor of the POS terminal in FIG. 2; 3 is a flowchart of processing by a processor of the POS terminal in FIG. 2; FIG. 3 is a diagram showing an example of a list screen displayed on the display device of the user terminal in FIG. 2;

A support system according to an embodiment will be described below with reference to the drawings.
1 and 2 are block diagrams showing an example of a support system 1 according to an embodiment and an example of a main circuit configuration of components included in the support system 1. FIG. The support system 1 provides a shopping support service. Shopping assistance services include list services and self-scan services. A list service provides a shopping list available on the information appliance. The self-scan service is a service that enables purchase registration of a product by reading a bar code or the like attached to the product at a store or the like. It is no longer necessary to read the bar code or the like attached to the merchandise at the cash register for the merchandise registered for purchase. The support system 1 includes a support server 10 , a POS (point of sale) server 20 , an application server 30 , a user terminal 40 and a POS terminal 50 . The support server 10, POS server 20, application server 30, user terminal 40 and POS terminal 50 are connected to a network NW. Network NW is a communication network typically including the Internet. The network NW may also include an intranet, a public mobile telephone network, a public switched telephone network, or any other communication network.
1 and 2 show one support server 10, one POS server 20, one application server 30, one user terminal 40, and one POS terminal 50, but there may be a plurality of each.

The assistance server 10 is used to provide shopping assistance services. Support server 10 includes processor 11 , ROM (read-only memory) 12 , RAM (random-access memory) 13 , auxiliary storage device 14 , communication interface 15 and bus 16 .

The processor 11 corresponds to a central portion of a computer that performs processing such as calculation and control required for the operation of the support server 10 . The processor 11 controls each part to realize various functions of the support server 10 based on programs such as system software, application software, or firmware stored in the ROM 12 or the auxiliary storage device 14 . The processor 11 is, for example, a CPU (central processing unit), MPU (micro processing unit), SoC (system on a chip), DSP (digital signal processor), or GPU (graphics processing unit). Alternatively, processor 11 is a combination of these. Processor 11 is an example of a control unit. A computer centered on the processor 11 is an example of a control unit.

The ROM 12 corresponds to the main memory of a computer with the processor 11 as its core. The ROM 12 is a non-volatile memory exclusively used for reading data. The ROM 12 stores the above program. In addition, the ROM 12 stores data or various setting values used by the processor 11 to perform various processes.

The RAM 13 corresponds to the main memory of a computer having the processor 11 as its core. The RAM 13 is a memory used for reading and writing data. The RAM 13 is used as a so-called work area for storing data temporarily used when the processor 11 performs various processes.

The auxiliary storage device 14 corresponds to an auxiliary storage device of a computer in which the processor 11 is central. The auxiliary storage device 14 is, for example, an EEPROM (registered trademark) (electric erasable programmable read-only memory), a HDD (hard disk drive), or an SSD (solid state drive). Auxiliary storage device 14 may store the above program. In addition, the auxiliary storage device 14 stores data used by the processor 11 to perform various processes, data generated by the processes performed by the processor 11, various setting values, and the like.

The auxiliary storage device 14 also stores a member DB (database) 141, a list DB 142, a dictionary DB 143, and a related DB 144.
The member DB 141 stores information on each member of the shopping support service. The member DB 141 includes, for example, a member table T1 as shown in FIG. FIG. 3 is a diagram showing an example of the member table T1. The member table T1 associates a member ID (identifier) with the member name, gender, date of birth, and the like of the member indicated by the member ID. The member ID is an identification code uniquely assigned to each member of the shopping support service.

The list DB 142 stores information about shopping lists and the like. The list DB 142 includes a list table T2 as shown in FIG. 4 and a registration table T3 as shown in FIG. FIG. 4 is a diagram showing an example of the list table T2. FIG. 5 is a diagram showing an example of the registration table T3.
The list table T2 defines the creator of the shopping list and the like. The list table T2 associates the list ID, the member ID of the member who created the shopping list identified by the list ID, the creation date of the shopping list identified by the list ID, and the like. A list ID is an identification code uniquely assigned to each shopping list.
The registration table T3 defines information about products to be purchased registered in the shopping list. The registration table T3 indicates the purchase plan ID, the list ID of the shopping list in which the purchase plan product identified by the purchase plan ID is registered, and the order in which the purchase plan product is displayed in the shopping list. The order of display, the name representing the product to be purchased, the number of planned purchases of the product to be purchased, the purchase flag indicating that the product to be purchased has already been purchased, and the date and time of purchase of the product to be purchased are associated. . The purchase plan ID is an identification code uniquely assigned to each purchase plan product included in the shopping list.

The dictionary DB 143 stores a linking dictionary or the like that associates the product name of the product with the alias of the product. The dictionary DB 143 includes a dictionary table T4 as shown in FIG. The dictionary table T4 associates, for each of a plurality of products, the product ID, product name, and alias of the product. The product ID is an identification code uniquely assigned to each product.

The relation DB 144 includes a relation table T5 as shown in FIG. 7 and the like. FIG. 8 is a diagram showing an example of the record configuration of the relation table T5. The association table T5 associates product IDs and list IDs. The association table T5 associates purchased products purchased based on the shopping list with the shopping list.

Programs stored in the ROM 12 or the auxiliary storage device 14 include a control program for executing processes described later. As an example, the support server 10 is transferred to an administrator of the support server 10 with the control program stored in the ROM 12 or the auxiliary storage device 14 . However, the support server 10 may be transferred to the administrator or the like in a state in which the control program for executing the processing described later is not stored in the ROM 12 or the auxiliary storage device 14 . Further, the support server 10 may be transferred to the administrator or the like with another control program stored in the ROM 12 or the auxiliary storage device 14 . Then, the control program for executing the processing described later may be separately transferred to the administrator or the like, and written to the ROM 12 or the auxiliary storage device 14 under the operation of the administrator or the serviceman. Transfer of the control program at this time can be realized by recording it on a removable storage medium such as a magnetic disk, magneto-optical disk, optical disk, or semiconductor memory, or by downloading it via the network NW.

The communication interface 15 is an interface for the support server 10 to communicate via the network NW or the like. Communication interface 15 is an example of a first communication unit.

The bus 16 includes a control bus, an address bus, a data bus, etc., and transmits signals to and from each part of the support server 10 .

The POS server 20 is a server for operating the POS system. The POS server 20 is installed, for example, in each store or shop. The POS server 20 stores data regarding commercial transactions on the POS system. POS server 20 includes processor 21 , ROM 22 , RAM 23 , auxiliary storage device 24 , communication interface 25 and bus 26 .

The processor 21 corresponds to a central portion of a computer that performs processing such as calculations and control necessary for the operation of the POS server 20 . The processor 21 controls each part to realize various functions of the POS server 20 based on programs such as system software, application software, or firmware stored in the ROM 22 or the auxiliary storage device 24 . The processor 21 is, for example, CPU, MPU, SoC, DSP or GPU. Alternatively, processor 21 is a combination of these.

The ROM 22 corresponds to a main storage device of a computer having the processor 21 as its core. The ROM 22 is a non-volatile memory exclusively used for reading data. The ROM 22 stores the above program. In addition, the ROM 22 stores data or various setting values used by the processor 21 to perform various processes.

The RAM 23 corresponds to a main memory device of a computer having the processor 21 as its core. The RAM 23 is a memory used for reading and writing data. The RAM 23 is used as a so-called work area for storing data temporarily used when the processor 21 performs various processes.

The auxiliary storage device 24 corresponds to an auxiliary storage device of a computer in which the processor 21 is central. The auxiliary storage device 24 is, for example, EEPROM, HDD or SSD. Auxiliary storage device 24 may store the above program. In addition, the auxiliary storage device 24 stores data used by the processor 21 to perform various processes, data generated by the processes performed by the processor 21, various setting values, and the like.

The auxiliary storage device 24 also stores a product DB 241 and a history DB 242 .
The product DB 241 stores information about each product. The product DB 241 includes, for example, a product table T11 as shown in FIG. FIG. 8 is a diagram showing an example of the record configuration of the product table T11. The product table T11 associates a product ID with product information such as the category, product name, price, number of products in stock, and weight of the product specified by the product ID.

The history DB 242 stores product sales records and the like. The history DB 242 includes, for example, a history table T12 as shown in FIG. FIG. 9 is a diagram showing an example of the record configuration of the history table T12. The history table T12 associates a transaction ID with sales information about the transaction ID. Transaction ID is an identification code uniquely assigned to each commercial transaction. The history DB 242 also associates transaction IDs with list IDs.

Programs stored in the ROM 22 or the auxiliary storage device 24 include control programs for executing processes described later. As an example, the POS server 20 is transferred to an administrator or the like of the POS server 20 with a control program for executing processing described later stored in the ROM 22 or the auxiliary storage device 24 . However, the POS server 20 may be transferred to the administrator or the like in a state in which the control program for executing the processes described later is not stored in the ROM 22 or the auxiliary storage device 24 . Also, the POS server 20 may be transferred to the administrator or the like with another control program stored in the ROM 22 or the auxiliary storage device 24 . Then, the control program for executing the processing described later may be separately transferred to the administrator or the like, and written to the ROM 22 or the auxiliary storage device 24 under the operation of the administrator or the serviceman. Transfer of the control program at this time can be realized by recording it on a removable storage medium such as a magnetic disk, magneto-optical disk, optical disk, or semiconductor memory, or by downloading it via the network NW.

The communication interface 25 is an interface for the POS server 20 to communicate via the network NW or the like.

The bus 26 includes a control bus, an address bus, a data bus, etc., and transmits signals exchanged with each part of the POS server 20 .

The application server 30 stores application software such as a list application AP1 and a self-scan application AP2. Also, the application server 30 transmits the list application AP1 or the self-scan application AP2 upon request.
The list application AP1 is application software used when using the list service. The list application AP1 may be list service software, or may be a general-purpose web browser.
The self-scan application AP2 is application software used when using the self-scan service. The self-scan application AP2 may be software for a self-scan service, or may be a general-purpose web browser.

The user terminal 40 is a device operated by a user of the shopping support service as an operator. The user terminal 40 is, for example, a mobile phone such as a smart phone, a PC (personal computer), a tablet PC, or the like. User terminal 40 includes processor 41 , ROM 42 , RAM 43 , auxiliary storage device 44 , communication interface 45 , input device 46 , display device 47 , camera 48 and bus 49 . The user terminal 40 is an example of a terminal device.

The processor 41 corresponds to a central portion of a computer that performs processing such as calculations and control required for the operation of the user terminal 40 . The processor 41 controls each part to implement various functions of the user terminal 40 based on programs such as system software, application software, or firmware stored in the ROM 42 or the auxiliary storage device 44 . The processor 41 is, for example, CPU, MPU, SoC, DSP or GPU. Alternatively, processor 41 is a combination of these.

The ROM 42 corresponds to the main storage device of the computer having the processor 41 as its core. The ROM 42 is a non-volatile memory exclusively used for reading data. The ROM 42 stores the above program. In addition, the ROM 42 stores data or various setting values used by the processor 41 to perform various processes.

The RAM 43 corresponds to the main storage device of the computer having the processor 41 as its core. The RAM 43 is a memory used for reading and writing data. The RAM 43 is used as a so-called work area for storing data temporarily used when the processor 41 performs various processes.

The auxiliary storage device 44 corresponds to an auxiliary storage device of a computer in which the processor 41 is central. The auxiliary storage device 44 is, for example, EEPROM, HDD or SSD. Auxiliary storage device 44 may store the above program. In addition, the auxiliary storage device 44 stores data used by the processor 41 to perform various processes, data generated by the processes performed by the processor 41, various setting values, and the like.
Also, the RAM 43 or the auxiliary storage device 44 stores the member ID.

Programs stored in the ROM 42 or the auxiliary storage device 44 include a list application and a self-scan application as application software for executing processes described later. As an example, the user terminal 40 is transferred to the administrator of the user terminal 40 or the like in a state in which the list application and the self-scan application are not stored in the ROM 42 or the auxiliary storage device 44 . Then, the list application and the self-scan application separately transferred to the administrator or the like are written to the auxiliary storage device 44 under the operation of the administrator or the like. However, the user terminal 40 may be transferred to the administrator or the like with the list application and the self-scan application stored in the ROM 42 or the auxiliary storage device 44 . Transfer of the control program described above can be realized by recording it on a removable storage medium such as a magnetic disk, magneto-optical disk, optical disk, or semiconductor memory, or by downloading it from the application server 30 or the like via the network NW. .

The communication interface 45 is an interface for the user terminal 40 to communicate via the network NW or the like. Communication interface 45 is an example of a second communication unit.

The input device 46 receives operations by the operator of the user terminal 40 . The input device 46 is, for example, a keyboard, keypad, touchpad or mouse.

The display device 47 displays a screen for notifying the operator of the user terminal 40 of various information. The display device 47 is, for example, a display such as a liquid crystal display or an organic EL (electro-luminescence) display. A touch panel can also be used as the input device 46 and the display device 47 . That is, a display panel provided with the touch panel can be used as the display device 47 and a touch pad provided with the touch panel can be used as the input device 46 . The display device 47 is an example of a display section.

A camera 48 takes an image of a bar code or the like.
The bus 49 includes a control bus, an address bus, a data bus, etc., and transmits signals exchanged with each part of the user terminal 40 .

The POS terminal 50 is installed in a store such as a supermarket or a convenience store. The POS terminal 50 is set for cash register operations such as purchase registration of products to be settled and payment for the registered products. The POS terminal 50 is mainly operated by, for example, a store clerk or the like. Alternatively, the POS terminal 50 may be a self-service terminal operated by a shopper or the like at the store. Also, the POS terminal 50 may be a semi-self-type terminal including a registration device for registering purchases of products and a payment device for making payments for the registered products. The semi-self-type POS terminal 50 is typically operated by a store clerk as a registration device and by a shopper as a settlement device. Each POS terminal 50 is assigned a unique POSID. Each POS terminal 50 is provided with a bar code in which the POSID is recorded. As an example, the following description will be made on the assumption that the POS terminal 50 is mainly operated by a store clerk. POS terminal 50 includes processor 501 , ROM 502 , RAM 503 , auxiliary storage device 504 , communication interface 505 , input device 506 , display device 507 , customer-side touch panel 508 , scanner 509 and bus 510 .

The processor 501 corresponds to the central portion of a computer that performs processing such as calculations and control necessary for the operation of the POS terminal 50 . The processor 501 controls each part to implement various functions of the POS terminal 50 based on programs such as system software, application software, or firmware stored in the ROM 502 or auxiliary storage device 504 . The processor 501 is, for example, CPU, MPU, SoC, DSP or GPU. Alternatively, processor 501 is a combination of these.

A ROM 502 corresponds to the main memory of a computer centered on the processor 501 . A ROM 502 is a non-volatile memory exclusively used for reading data. ROM 502 stores the above program. In addition, the ROM 502 stores data or various setting values used when the processor 501 performs various processes.

A RAM 503 corresponds to a main memory device of a computer centered on the processor 501 . A RAM 503 is a memory used for reading and writing data. The RAM 503 is used as a so-called work area in which data temporarily used when the processor 501 performs various processes is stored.

The auxiliary storage device 504 corresponds to an auxiliary storage device of a computer centered on the processor 501 . Auxiliary storage device 504 is, for example, EEPROM, HDD, or SSD. Auxiliary storage device 504 may store the above program. Further, the auxiliary storage device 504 stores data used by the processor 501 to perform various processes, data generated by the processes performed by the processor 501, various setting values, and the like. The auxiliary storage device 504 also stores a product list, which is a list of products registered as purchased products. Alternatively, the RAM 503 may store the product list. Furthermore, the auxiliary storage device 504 also stores a product database containing various information such as product codes, product names, and prices for products sold at stores.

Programs stored in the ROM 502 or the auxiliary storage device 504 include control programs for executing the processes described later. As an example, the POS terminal 50 is transferred to an administrator or the like of the POS terminal 50 in a state in which a control program for executing processing described later is stored in the ROM 502 or the auxiliary storage device 504 . However, the POS terminal 50 may be transferred to the administrator or the like in a state in which the control program for executing the processing described later is not stored in the ROM 502 or the auxiliary storage device 504 . Also, the POS terminal 50 may be transferred to the administrator or the like with another control program stored in the ROM 502 or the auxiliary storage device 504 . A control program for executing the processing described later may be separately transferred to the administrator or the like, and written to the ROM 502 or the auxiliary storage device 504 under the operation of the administrator or the serviceman. Transfer of the control program at this time can be realized by recording it on a removable storage medium such as a magnetic disk, magneto-optical disk, optical disk, or semiconductor memory, or by downloading it via the network NW.

A communication interface 505 is an interface for the POS terminal 50 to communicate via a network NW or the like.

The input device 506 receives operations by the operator of the POS terminal 50 . Input device 506 is, for example, a keyboard, keypad, touchpad, or mouse.

The display device 507 displays a screen for notifying the operator of the POS terminal 50 of various information. The display device 507 is, for example, a display such as a liquid crystal display or an organic EL display. Alternatively, as the display device 507, a display panel provided over the touch pad can be used. That is, a display panel included in the touch panel can be used as the display device 507 and a touch pad included in the touch panel can be used as the input device 506 .

The customer-side touch panel 508 functions as a display device that displays a screen for notifying the shopper of various information. Also, the customer-side touch panel 508 functions as an input device that receives touch operations by the shopper. As described above, the POS terminal 50 is mainly operated by a store clerk, but the customer-side touch panel 508 is operated by a shopper.

A scanner 509 reads a barcode displayed on a product or the like and outputs the product code represented by this barcode. The scanner 509 may be of a type that is held by hand, or of a type that is fixed to a register table or the like.

A bus 510 includes a control bus, an address bus, a data bus, etc., and transmits signals exchanged with each part of the POS terminal 50 .

The operation of the support system 1 according to the embodiment will be described below with reference to FIGS. 10 to 22 and the like. It should be noted that the contents of the processing in the following description of the operation are examples, and various processing that can obtain similar results can be used as appropriate. 10 to 16 are flowcharts of processing by the processor 41 of the user terminal 40. FIG. Processor 41 executes the processes of FIGS. 10 to 15 based on the list application stored in ROM 42, auxiliary storage device 44, or the like. The processor 41 executes the process of FIG. 16 based on the self-scan application stored in the ROM 42, auxiliary storage device 44, or the like. 17 to 19 are flow charts of processing by the processor 11 of the support server 10. FIG. The processor 11 executes this processing based on control programs stored in the ROM 12, the auxiliary storage device 14, or the like. 20 and 21 are flowcharts of processing by the processor 501 of the POS terminal 50. FIG. The processor 501 executes this process based on a control program stored in the ROM 502, auxiliary storage device 504, or the like. Unless otherwise specified, the processors 11, 41, and 501 proceed to Act(n+1) after processing Act(n) (where n is a natural number). Note that the processing performed by the support server 10 in the following description is performed for one user terminal 40 or one POS terminal 50 . Actually, the support server 10 performs similar processing for each of the plurality of user terminals 40 and the plurality of POS terminals 50 .

In Act1 of FIG. 10, the processor 41 of the user terminal 40 determines whether or not the user terminal 40 has logged into the list service. If the user terminal 40 is logged in to the list service, the processor 41 determines Yes in Act1 and proceeds to Act3. On the other hand, if the user terminal 40 is not logged in to the list service, the processor 41 determines No in Act1 and proceeds to Act2.

In Act 2, the processor 41 performs login processing for putting the user terminal 40 in a state of being logged in to the list service. A well-known method can be used for the login process. By the login process, the RAM 43 or the auxiliary storage device 44 stores the member ID used for login. The support server 10 also identifies that the user terminal 40 has logged into the list service with the member ID.

In Act3, the processor 41 generates an image corresponding to the start screen. Processor 41 then instructs display device 47 to display this generated image. In response to this instruction, the display device 47 displays the start screen.
The start screen includes, for example, a creation start button and a shopping start button. The creation start button is a button for the operator to operate when creating a shopping list. The shopping start button is a button for the operator to operate when starting shopping using the created shopping list.

In Act 4, the processor 41 determines whether or not an operation instructing start of creation of a shopping list has been performed. That is, the processor 41 determines whether or not a predetermined operation such as operating the creation start button has been performed. If the operation to instruct the start of shopping list creation is not performed, the processor 41 determines No in Act 4 and proceeds to Act 5 .

In Act 5, the processor 41 determines whether or not an operation instructing the start of shopping has been performed. That is, the processor 41 determines whether or not a predetermined operation such as operating the shopping start button has been performed. If the operation instructing the start of shopping is not performed, the processor 41 determines No in Act5 and returns to Act4. Thus, the processor 41 repeats Act 4 and Act 5 until an operation instructing the start of shopping list creation is performed or an operation instructing the start of shopping is performed.

The operator of the user terminal 40 operates a creation start button when creating a shopping list by editing a saved shopping list or creating and editing a new shopping list.
The processor 41 determines Yes in Act 4 and proceeds to Act 6 if an operation to instruct the start of shopping list creation is performed while in the standby state of Act 4 and Act 5 .

In Act 6, the processor 41 generates a creation start request indicating creation of a shopping list. The creation start request includes the member ID stored in RAM 43 or auxiliary storage device 44 . The processor 41 then instructs the communication interface 45 to transmit the generated creation start request to the support server 10 . Upon receiving this instruction, the communication interface 45 transmits the creation start request to the support server 10 . The transmitted creation start request is received by the communication interface 15 of the support server 10 .

On the other hand, in Act 201 of FIG. 17, the processor 11 of the support server 10 determines whether or not the communication interface 15 has received a creation start request. If the creation start request is not received, the processor 11 determines No in Act 201 and proceeds to Act 202 .

In Act 202, the processor 11 determines whether or not the communication interface 15 has received a registration start request. If the registration start request is not received, the processor 11 determines No in Act 202 and proceeds to Act 203 . Note that the registration start request will be described later.

In Act 203 , the processor 11 determines whether or not login has been performed from the POS terminal 50 . If the login from the POS terminal 50 has not been performed, the processor 11 determines No in Act 203 and returns to Act 201 . Thus, the processor 11 repeats Act 201 to Act 203 until a creation start request or registration start request is received or login is performed from the POS terminal 50 .

If the processor 11 receives a creation start request while in the standby state of Act201 to Act203, it determines Yes in Act201 and proceeds to Act204. In Act 204, the processor 11 generates a creation permission response indicating permission to create the shopping list. The creation permission response includes a list of shopping lists associated with the member ID included in the creation start request received in Act201. The processor 11 acquires the list of shopping lists, for example, from the list table T2. The list of shopping lists includes the list ID and creation date and time of each shopping list. Then, the processor 11 instructs the communication interface 15 to transmit the created creation permission response to the user terminal 40 . Upon receiving this instruction, the communication interface 15 transmits the creation permission response to the user terminal 40 . The transmitted creation approval response is received by the communication interface 45 of the user terminal 40 .

On the other hand, in Act 7 of FIG. 10 , the processor 41 waits for the communication interface 45 of the user terminal 40 to receive the creation approval response. If the creation permission response is received, the processor 41 determines Yes in Act7 and proceeds to Act8.

In Act8, the processor 41 generates an image corresponding to the first list screen. Processor 41 then instructs display device 47 to display this generated image. In response to this instruction, the display device 47 displays the first list screen.
The first list list screen includes, for example, a new creation button and a list of shopping lists included in the creation approval response received in Act7. The new creation button is a button operated by the operator of the user terminal 40 when instructing creation of a new shopping list.

In Act 9, the processor 41 determines whether or not an operation instructing creation of a new shopping list has been performed. That is, the processor 41 determines whether or not a predetermined operation such as operating a new creation button has been performed. If the operation of instructing creation of a new shopping list is not performed, the processor 41 determines No in Act 9 and proceeds to Act 10 .

In Act 10, the processor 41 determines whether or not a shopping list has been selected from the list of shopping lists included in the first list list screen. If the shopping list is not selected, the processor 41 determines No in Act10 and returns to Act9. Thus, the processor 41 repeats Act9 and Act10 until an operation instructing creation of a new shopping list is performed or a shopping list is selected.

When the operator of the user terminal 40 wants to create a new shopping list, he/she operates the new creation button.
If the processor 41 is in the standby state of Act9 and Act10 and an operation instructing creation of a new shopping list is performed, the processor 41 determines Yes in Act9 and proceeds to Act11.

In Act11, the processor 41 generates a new request to request the support server 10 to create a new shopping list. The new request includes the member ID stored in auxiliary storage device 44 . The processor 41 then instructs the communication interface 45 to transmit the generated new request to the support server 10 . Upon receiving this instruction, the communication interface 45 transmits the new request to the support server 10 . The sent new request is received by the communication interface 15 of the support server 10 . Also, the processor 41 creates a new shopping list and stores it in the RAM 43 or the auxiliary storage device 44 . The shopping list does not include any products to be purchased. Furthermore, the processor 41 causes the RAM 43 or the auxiliary storage device 44 to store the list ID of the newly created shopping list. Note that the list ID is transmitted from the support server 10 as will be described later.

On the other hand, in Act 205 of FIG. 17, the processor 11 of the support server 10 determines whether or not the user terminal 40 has acquired the list. If the list has not been obtained, the processor 11 determines No in Act 205 and proceeds to Act 206 .

In Act 206 processor 11 determines whether a new request has been received by communication interface 15 . If no new request has been received, the processor 11 determines No in Act 206 and returns to Act 205 . Thus, the processor 11 repeats Acts 205 and 206 until either the list is acquired by the user terminal 40 or a new request is received by the communication interface 15 .

If the processor 11 receives a new request while in the standby state of Act205 and Act206, it determines Yes in Act206 and proceeds to Act207. In Act 207, the processor 41 of the user terminal 40 creates a new shopping list. That is, processor 41 adds a record to list table T2. At this time, processor 41 assigns a unique list ID to the newly created shopping list. The added record contains the list ID and the member ID included in the new request received in Act 206 . Also, the processor 41 instructs the communication interface 15 to transmit the list ID to the user terminal 40 . Upon receiving this instruction, the communication interface 15 transmits the list ID to the user terminal 40 . The transmitted list ID is received by the communication interface 45 of the user terminal 40 . The list ID is stored in the RAM 43 or the auxiliary storage device 44 as described above.

On the other hand, when the operator of the user terminal 40 wants to edit a saved shopping list, he/she selects the shopping list to be edited from the list of shopping lists included in the first list list screen. The operator of the user terminal 40 specifies a desired shopping list by, for example, the creation date and time displayed on the first list screen.
If the shopping list is selected in the standby state of Act9 and Act10 in FIG. 10, the processor 41 determines Yes in Act10 and proceeds to Act12.
In Act12, the processor 41 of the user terminal 40 acquires from the support server 10 the shopping list selected in Act10. The processor 41 then causes the RAM 43 or the auxiliary storage device 44 to store the acquired shopping list. Also, the processor 41 causes the RAM 43 or the auxiliary storage device 44 to store the list ID corresponding to the shopping list.
The list ID stored in the RAM 43 or the auxiliary storage device 44 in Act11 or Act12 is hereinafter referred to as "creation target list ID".

After processing Act11 or Act12, the processor 41 proceeds to Act21 in FIG.
In Act21, the processor 41 generates an image corresponding to the registration screen. Processor 41 then instructs display device 47 to display this generated image. In response to this instruction, the display device 47 displays the registration screen.
The registration screen includes, for example, a list of products to be purchased, a register button, a delete button, and an end button. The list of products to be purchased is a list of products to be purchased included in the shopping list stored in the RAM 43 or the auxiliary storage device 44 . The registration button is a button operated by the operator of the user terminal 40 when additionally registering the product to be purchased in the shopping list. The delete button is a button for the operator of the user terminal 40 to operate when deleting a product to be purchased registered in the shopping list. The end button is a button operated by the operator of the user terminal 40 to finish editing the shopping list.

In Act 22, the processor 41 determines whether or not an operation to instruct additional registration of the product to be purchased has been performed. That is, the processor 41 determines whether or not a predetermined operation such as operating a registration button has been performed. The processor 41 determines No in Act 22 and proceeds to Act 23 if an operation to instruct additional registration of the product to be purchased is not performed.

In Act 23, the processor 41 determines whether or not an operation instructing deletion of the product to be purchased has been performed. That is, the processor 41 determines whether or not a predetermined operation such as operating the delete button has been performed. The processor 41 determines No in Act 23 and proceeds to Act 24 if the operation to instruct deletion of the product to be purchased is not performed.

In Act 24, the processor 41 determines whether or not an operation instructing the end of editing of the shopping list has been performed. That is, the processor 41 determines whether or not a predetermined operation such as operating the end button has been performed. The processor 41 determines No in Act 24 and returns to Act 22 if an operation to instruct the end of editing of the shopping list is not performed. Thus, the processor 41 repeats Act22 to Act24 until an operation for instructing additional registration of the product to be purchased, an operation for instructing deletion of the product to be purchased, or an operation for instructing the end of editing of the shopping list is performed.

If the processor 41 is in the standby state of Act22 to Act24 and an operation to instruct additional registration of the product to be purchased is performed, the processor 41 determines Yes in Act22 and proceeds to Act31 in FIG.
In Act 31, the processor 41 generates an image corresponding to the additional selection screen for selecting the product to be purchased to be added. Processor 41 then instructs display device 47 to display this generated image. In response to this instruction, the display device 47 displays an additional selection screen.
The additional selection screen includes, for example, a product list, a registration end button, and a registration button. A product included in the list of products is put into a selected state when the operator of the user terminal 40 performs an operation to select the product. In addition, the product in the selected state becomes the non-selected state when the operator of the user terminal 40 performs an operation to cancel the selection of the product. The registration end button is a button operated by the operator of the user terminal 40 to end the additional registration of the product to be purchased. The registration button is a button for the operator of the user terminal 40 to operate when additionally registering the selected product in the shopping list as a product to be purchased.

In Act 32, the processor 41 determines whether or not an operation to instruct termination of additional registration of the product to be purchased has been performed. That is, the processor 41 determines whether or not a predetermined operation such as operating the registration end button has been performed. The processor 41 determines No in Act 32 and proceeds to Act 33 if an operation to instruct termination of additional registration of the product to be purchased is not performed.

In Act33, the processor 41 determines whether or not the product has been selected. If the product is not in the selected state, the processor 41 determines No in Act 33 and returns to Act 32 . Thus, the processor 41 repeats Act32 and Act33 until an operation is performed to instruct termination of additional registration of the product to be purchased, or until the product is selected.

The processor 41 determines Yes in Act 32 and returns to Act 21 in FIG. 11 if an operation to instruct termination of additional registration of the product to be purchased is performed while the processor 41 is in the standby state of Act 32 and Act 33 . On the other hand, if the product is in the selected state in the standby state of Act32 and Act33 in FIG. 12, the processor 41 determines Yes in Act33 and proceeds to Act34.

In Act34, the processor 41 determines whether or not the item selected in Act33 has become non-selected. If the product in the selected state is not in the non-selected state, the processor 41 determines No in Act 34 and proceeds to Act 35 .

In Act 35, the processor 41 determines whether or not an operation has been performed to instruct additional registration of the product selected in Act 33 in the shopping list. That is, the processor 41 determines whether or not a predetermined operation such as operating a registration button has been performed. The processor 41 determines No in Act 35 and returns to Act 34 if an operation to instruct additional registration of the selected product in the shopping list is not performed. Thus, the processor 41 repeats Act34 and Act35 until the item in the selected state becomes unselected or an operation is performed to instruct additional registration of the item in the selected state in the shopping list.

The processor 41 determines Yes in Act 34 and returns to Act 32 if the product in the selected state becomes non-selected while in the standby state of Act 34 and Act 35 . On the other hand, if an operation for instructing additional registration of the selected product in the shopping list is performed while in the standby state of Acts 34 and 35, it is determined Yes in Act 35 and the process proceeds to Act 36.

In Act 36, the processor 41 generates a registration request for instructing the support server 10 to additionally register the selected product in the shopping list. The registration request includes the creation target list ID and the product ID of the selected product. The processor 41 then instructs the communication interface 45 to transmit the generated registration request to the support server 10 . Upon receiving this instruction, the communication interface 45 transmits the registration request to the support server 10 . The transmitted registration request is received by the communication interface 15 of the support server 10 . After processing Act36, the processor 41 proceeds to Act26 in FIG.

On the other hand, if the processor 41 is in the standby state of Act22-Act24 and an operation instructing deletion of the product to be purchased is performed, it determines Yes in Act23 and proceeds to Act41 in FIG.
In Act 41, the processor 41 generates an image corresponding to the deletion screen for selecting the product to be purchased to be deleted. Processor 41 then instructs display device 47 to display this generated image. In response to this instruction, the display device 47 displays the deletion screen.
The delete screen includes, for example, a list of products to be purchased registered in the shopping list, a delete end button, and a delete button. A product to be purchased included in the list of products to be purchased is put into a selected state when the operator of the user terminal 40 performs an operation to select the product to be purchased. In addition, when the operator of the user terminal 40 performs an operation to cancel the selection of the product to be purchased, the product to be purchased that is in a selected state becomes a non-selected state. The deletion end button is a button for the operator of the user terminal 40 to operate when deleting the product to be purchased is ended. The delete button is used by the operator of the user terminal 40 to delete the selected product to be purchased from the shopping list.

In Act 42, the processor 41 determines whether or not an operation has been performed to instruct termination of deletion of the product to be purchased. That is, the processor 41 determines whether or not a predetermined operation such as operating the deletion end button has been performed. The processor 41 determines No in Act 42 and proceeds to Act 43 if an operation to instruct termination of deletion of the product to be purchased is not performed.

In Act 43, the processor 41 determines whether or not the product has been selected. If the product is not in the selected state, the processor 41 determines No in Act 43 and returns to Act 42 . Thus, the processor 41 repeats Act 42 and Act 43 until an instruction to end deletion of the product to be purchased is performed or the product to be purchased is selected.

If the processor 41 is in the standby state of Act42 and Act43 and an operation to instruct the end of deletion of the product to be purchased is performed, the processor 41 determines Yes in Act42 and returns to Act21 of FIG. On the other hand, if the product to be purchased is in the selected state in the standby state of Act42 and Act43 in FIG. 12, the processor 41 determines Yes in Act43 and proceeds to Act44.

In Act 44, the processor 41 determines whether or not the product to be purchased that has been selected in Act 43 has become non-selected. If the product to be purchased in the selected state is not in the non-selected state, the processor 41 determines No in Act 44 and proceeds to Act 45 .

In Act 45, the processor 41 determines whether or not an operation has been performed to instruct deletion of the product to be purchased selected in Act 43 from the shopping list. That is, the processor 41 determines whether or not a predetermined operation such as operating the delete button has been performed. The processor 41 determines No in Act 45 and returns to Act 44 if an operation to instruct deletion of the selected product to be purchased from the shopping list is not performed. Thus, the processor 41 repeats Act 44 and Act 45 until the selected product to be purchased becomes non-selected or an operation instructing deletion of the selected product to be purchased from the shopping list is performed.

The processor 41 determines Yes in Act 44 and returns to Act 42 if the product to be purchased in the selected state becomes non-selected while in the standby state of Act 44 and Act 45 . On the other hand, if an operation to instruct deletion of the selected product to be purchased from the shopping list is performed while in the standby state of Acts 44 and 45, it is determined Yes in Act 45 and the process proceeds to Act 46.

In Act 46, the processor 41 generates a deletion request for instructing the support server 10 to delete the selected product to be purchased from the shopping list. The deletion request includes the creation target list ID and the purchase plan ID of the selected purchase plan product. The processor 41 then instructs the communication interface 45 to transmit the generated deletion request to the support server 10 . Upon receiving this instruction, the communication interface 45 transmits the deletion request to the support server 10 . The transmitted deletion request is received by the communication interface 15 of the support server 10 . After processing Act46, the processor 41 proceeds to Act26 in FIG.

On the other hand, in Act 208 of FIG. 17, the processor 11 of the support server 10 determines whether the communication interface 15 has received a registration request. If the communication interface 15 has not received a registration request, the processor 11 determines No in Act 208 and proceeds to Act 209 .

In Act 209 the processor 11 determines whether or not the communication interface 15 has received a delete request. If the communication interface 15 has not received a deletion request, the processor 11 determines No in Act 209 and proceeds to Act 210 .

At Act 210 , the processor 11 determines whether or not a termination request has been received by the communication interface 15 . Note that the termination request will be described later. If the communication interface 15 has not received a termination request, the processor 11 determines No in Act 210 and returns to Act 208 . Thus, processor 11 repeats Acts 208-210 until communication interface 15 receives a registration request, deletion request, or termination request.

If the processor 11 receives a registration request while in the standby state of Act208 to Act210, it determines Yes in Act208 and proceeds to Act211.
In Act 211, the processor 11 additionally registers the product specified by the product ID included in the registration request as a planned purchase product in the shopping list specified by the creation target list ID included in the registration request. That is, processor 11 adds a record to registration table T3. At this time, the processor 11 assigns a unique purchase plan ID to the purchase plan product. The added record includes the purchase plan ID, the creation target list ID, and the product ID. The initial value of the purchase flag included in the added record is False. Also, the display order included in the added record is, for example, the number of purchase plan IDs associated with the creation target list ID.

Also, if the processor 11 receives a deletion request while in the standby state of Act208 to Act210, it determines Yes in Act208 and proceeds to Act212.
In Act 212, the processor 11 deletes the intended purchase product identified by the intended purchase ID included in the deletion request from the shopping list identified by the creation target list ID included in the deletion request. That is, the processor 11 deletes the record identified by the purchase plan ID from the registration table T3.

After processing Act211 or Act212, the processor 11 proceeds to Act213.
In Act 213, the processor 11 generates a first completion notification indicating that the registration or deletion has been completed. The first completion notification includes the shopping list specified by the creation target list ID. The processor 11 then instructs the communication interface 15 to transmit the generated first completion notification to the user terminal 40 . Upon receiving this instruction, the communication interface 15 transmits the first completion notification to the user terminal 40 . The transmitted first completion notification is received by the communication interface 45 of the user terminal 40 . After processing Act213, the processor 11 returns to Act210.

On the other hand, in Act 26 of FIG. 11, the processor 41 of the user terminal 40 waits for the communication interface 45 to receive the first completion notification. If the first completion notification is received, the processor 41 determines Yes in Act 26 and proceeds to Act 27 .

In Act 27, the processor 41 causes the RAM 43 or the auxiliary storage device 44 to store the shopping list included in the first completion notification received in Act 26. FIG. The processor 41 overwrites the shopping list already stored in the RAM 43 or the auxiliary storage device 44 with the shopping list. After processing Act27, the processor 41 returns to Act21.

If the processor 41 is in the standby state of Act22 to Act24 and an operation to instruct the end of editing the shopping list is performed, it determines Yes in Act24 and proceeds to Act25.

In Act 25, the processor 41 instructs the communication interface 45 to send a termination request to the support server 10 to terminate editing of the shopping list. Upon receiving this instruction, the communication interface 45 transmits the termination request to the support server 10 . The sent termination request is received by the communication interface 15 of the support server 10 .
On the other hand, if the processor 11 of the support server 10 receives a termination request while in the standby state of Act208 to Act210 in FIG. 17, it determines Yes in Act210 and returns to Act201.

Then, the operator of the user terminal 40 operates the shopping start button when shopping using the created shopping list.
The processor 41 of the user terminal 40 determines Yes in Act5 and proceeds to Act13 if an operation instructing the start of shopping is performed while in the standby state of Act4 and Act5 in FIG.

In Act13, the processor 41 generates a shopping start request indicating to start shopping. The shopping start request includes the member ID stored in RAM 43 or auxiliary storage device 44 . The processor 41 then instructs the communication interface 45 to transmit the generated shopping start request to the support server 10 . Upon receiving this instruction, the communication interface 45 transmits the shopping start request to the support server 10 . The transmitted shopping start request is received by the communication interface 15 of the support server 10 .

On the other hand, if the processor 11 of the support server 10 receives a request to start shopping while in the standby state of Act201 to Act203 in FIG.
In Act 214, the processor 11 generates a shopping approval response indicating approval to start shopping using the shopping list. The shopping approval response includes a list of shopping lists associated with the member ID included in the shopping initiation request received in Act202. The processor 11 acquires the list of shopping lists, for example, from the list table T2. The list of the shopping list includes the list ID of the shopping list and the creation date and time. The processor 11 then instructs the communication interface 15 to transmit the generated shopping approval response to the user terminal 40 . Upon receiving this instruction, the communication interface 15 transmits the shopping permission response to the user terminal 40 . The transmitted shopping authorization response is received by the communication interface 45 of the user terminal 40 .

On the other hand, in Act 14 of FIG. 10, the processor 41 of the user terminal 40 waits for the communication interface 45 to receive the shopping authorization response. If the purchase approval response is received, the processor 41 determines Yes in Act 14 and proceeds to Act 15 .

In Act15, the processor 41 generates an image corresponding to the second list screen. Processor 41 then instructs display device 47 to display this generated image. In response to this instruction, the display device 47 displays the second list screen.
The second list view screen includes, for example, a list of shopping lists included in the shopping approval response received in Act14.

The operator of user terminal 40 selects a shopping list to be used for shopping from the saved shopping lists displayed on the second list screen. The operator of the user terminal 40 specifies a desired shopping list by, for example, the creation date and time displayed on the second list screen.

In Act17, the processor 41 of the user terminal 40 acquires from the support server 10 the shopping list selected in Act16. The processor 41 then causes the RAM 43 or the auxiliary storage device 44 to store the acquired shopping list. Also, the processor 41 causes the RAM 43 or the auxiliary storage device 44 to store the list ID corresponding to the shopping list. The list ID stored in the RAM 43 or the auxiliary storage device 44 in Act 17 will be referred to as the "shopping object list ID".

On the other hand, in Act 215 of FIG. 17, the processor 11 of the support server 10 waits for the user terminal 40 to acquire the list. If the user terminal 40 acquires the list, the processor 11 determines Yes in Act 215 and proceeds to Act 221 in FIG. 18 .

On the other hand, the processor 41 of the user terminal 40 proceeds to Act51 of FIG. 14 after the processing of Act17 of FIG.
In Act 51, the processor 41 activates the self-scan application. The processor 41 starts the process shown in FIG. 16 in response to activation of the self-scan application. Note that the processor 41 performs the processing shown in FIG. 16 in parallel with or in parallel with the processing shown in FIGS. Also, the self-scan application activated by the processing of Act 51 operates in cooperation with the list application.
In Act 101 of FIG. 16, the processor 41 determines whether or not the user terminal 40 has logged in to the self-scan service. If the user terminal 40 is logged in to the self-scan service, the processor 41 determines Yes in Act 101 and proceeds to Act 103 . On the other hand, if the user terminal 40 is not logged in to the self-scan service, the processor 41 determines No in Act 101 and proceeds to Act 102 .

In Act 102, the processor 41 performs login processing to put the user terminal 40 in a state of being logged in to the self-scan service. A well-known method can be used for the login process. By the login process, the RAM 43 or the auxiliary storage device 44 stores the member ID used for login. The support server 10 also identifies that the user terminal 40 has logged in to the self-scan service with the member ID. Note that the operator of the user terminal 40 designates a store to use the self-scan service at the time of login, for example. Thereby, the support server 10 identifies at which store the user terminal 40 uses the self-scan service. Hereinafter, when communicating with the POS server 20, the support server 10 communicates with the POS server 20 corresponding to the store.

In Act 103 the processor 41 activates the camera 48 .
In Act 104 , the processor 41 determines whether or not the barcode attached to the product has been read by the camera 48 . If the barcode attached to the product has not been read by the camera 48 , the processor 41 determines No in Act 104 and proceeds to Act 105 .

In Act 105, the processor 41 determines whether or not a payment command has been input to the self-scan application. If the payment command is not input to the self-scan application, the processor 41 determines No in Act 105 and returns to Act 104 . Thus, the processor 41 repeats Act 104 and Act 105 until the barcode attached to the product is read by the camera 48 or a payment command is input to the self-scan application.

On the other hand, in Act 52 of FIG. 14, the processor 41 waits for the self-scan application to start. If the self-scan application is activated, the processor 41 determines Yes in Act 52 and proceeds to Act 53 in FIG. 15 .

In Act53, the processor 41 generates an image corresponding to the list screen SC1 as shown in FIG. Processor 41 then instructs display device 47 to display this generated image. In response to this instruction, the display device 47 displays the list screen SC1.
FIG. 21 is a diagram showing an example of the list screen SC1. The list screen SC1 includes an area A1 displaying a list of products to be purchased included in the shopping list stored in the RAM 43 or the auxiliary storage device 44, and an end button B1. Here, the arranging order of the products to be purchased displayed in the area A1 is, for example, the ascending order of the arranging order values shown in the registration table T3. In the area A1 in FIG. 22, as an example, bread, beef, apple, pork, onion, and grape are displayed in this order. Note that a check mark or the like is displayed in the area where the products to be purchased whose purchase flag value is True are displayed. In addition, the areas in which the products to be purchased included in the area A1 are displayed are buttons. The respective buttons are buttons for the operator of the user terminal 40 to operate when selecting the product to be purchased displayed within the respective buttons. When the button is operated, the corresponding product to be purchased is selected. The end button B1 is a button operated by the operator of the user terminal 40 to end shopping using the shopping list.

In Act54, the processor 41 determines whether or not an operation to select the product to be purchased displayed on the list screen SC1 has been performed. If the operation to select the product to be purchased has not been performed, the processor 41 determines No in Act 54 and proceeds to Act 55 .

In Act 55 the processor 41 determines whether a request such as a confirmation request or a selection request has been received by the communication interface 45 . If the request has not been received, the processor 41 determines No in Act 55 and proceeds to Act 56 . The confirmation request and selection request will be described later.

In Act 56 the processor 41 determines whether or not the communication interface 45 has received the third completion notification. If the third completion notification has not been received, the processor 41 determines No in Act56 and proceeds to Act57. Note that the third completion notification will be described later.

In Act 57, the processor 41 determines whether or not an operation has been performed to finish shopping and make payment. That is, the processor 41 determines whether or not a predetermined operation such as operating the settlement button B3 has been performed. The processor 41 determines No in Act 57 and returns to Act 54 if the operation for finishing the shopping and making the payment is not performed. Thus, the processor 41 repeats Acts 54 to 57 until an operation to select a product to be purchased is performed, a request or a third completion notice is received, or an operation to finish shopping and make payment is performed. repeat.

An operator of the user terminal 40 acquires the product to be purchased from a display place such as a display shelf, and puts it in a basket or the like. At this time, the operator of the user terminal 40 selects a product to be purchased from among the products to be purchased included in the shopping list in a state in which it can be seen that the product to be purchased has already been acquired or purchased (hereinafter referred to as “purchased product”). state”), for example, the following operations (1) or (2) are performed. The following description is based on the assumption that the operator of the user terminal 40 picks up an "apple" from a display shelf or the like.
(1) Operation A
The operator of the user terminal 40 selects a product to be purchased corresponding to the product acquired from the display place from among the products to be purchased displayed on the list screen SC1. That is, the operator of user terminal 40 selects "apple" by operating the button corresponding to "apple" from among the products to be purchased displayed on list screen SC1.
(2) Operation B
The operator of the user terminal 40 causes the camera 48 to read the bar code attached to the product acquired from the display place. That is, the operator of the user terminal 40 causes the camera 48 to read the barcode attached to the apple.

The processor 41 determines Yes in Act54 and proceeds to Act58 if an operation to select a product to be purchased is performed while in the standby state of Act54 to Act57.
In Act 58, the processor 41 generates an image corresponding to the selected screen. Processor 41 then instructs display device 47 to display this generated image. In response to this instruction, the display device 47 displays the selected screen.
The selected screen includes area A2. The area A2 is popped up on the list screen SC1, for example. Area A2 includes character string S21, check button B21, and cancel button B22. The character string S21 includes a character string inquiring whether or not the product to be purchased in the selected state has been taken from a display place or the like, or a character string inquiring whether or not the product to be purchased is allowed to be in a purchased state. The character string S21 is, for example, "Do you want to put 'apple' in the basket?" is a string such as The check button B21 is a button operated by the operator of the user terminal 40 when the product to be purchased indicated by the character string S21 is put in the purchased state. As an example, the processor 41 displays a check mark next to the product to be purchased to place it in a purchased state. Alternatively, for example, the processor 41 changes the color of part or all of the area where the product to be purchased is displayed to put it in the purchased state. The cancel button B22 is a button for the operator of the user terminal 40 to operate when canceling the selection of the selected product to be purchased because the product indicated by the character string S21 has not been taken from the display area. be. When the release button B22 is operated, the selected product to be purchased is deselected. The state of the product to be purchased that is not in the purchased state is referred to as "unpurchased state". The product to be purchased in the unpurchased state is in a state in which it can be seen that the product has not been acquired or purchased.
Note that FIG. 21 shows the selected screen SC2 when an unpurchased product is selected. The selected screen when the purchased state is selected includes a character string S22 instead of the character string S21, and a cancel button B23 instead of the check button B21. The character string S22 includes a character string asking whether or not the selected product to be purchased has been returned to the display place, or a character string asking whether the product to be purchased may be put in an unpurchased state. The cancel button B23 is a button operated by the operator of the user terminal 40 when the product to be purchased indicated by the character string S21 is put in a non-purchased state.

In Act 59, the processor 41 determines whether or not an operation to deselect the selected product to be purchased has been performed. That is, the processor 41 determines whether or not a predetermined operation such as operating the release button B22 has been performed. The processor 41 determines No in Act 59 and advances to Act 60 if the operation to cancel the selection of the product to be purchased in the selected state is not performed.

In Act 60, the processor 41 determines whether or not an operation has been performed to change the product to be purchased into a purchased state. That is, the processor 41 determines whether or not a predetermined operation such as operating the check button B21 has been performed. The processor 41 determines No in Act 60 and proceeds to Act 61 if the operation to change the purchase-planned product to the purchased state is not performed.

In Act 61, the processor 41 determines whether or not an operation has been performed to set the product to be purchased to an unpurchased state. That is, the processor 41 determines whether or not a predetermined operation such as operating the cancel button B23 has been performed. The processor 41 determines No in Act 61 and returns to Act 59 if an operation is not performed to set the product to be purchased to an unpurchased state. Thus, the processor 41 repeats Act59 to Act61 until the operation of deselecting the product to be purchased in the selected state, the operation to set the product to be purchased to the purchased state, or the operation to set the product to be purchased to the non-purchased state. .
The processor 41 determines Yes in Act59 and returns to Act53 if an operation to cancel the selection of the product to be purchased in the selected state is performed while in the standby state of Act59 to Act61.

On the other hand, if the processor 41 is in the standby state of Act59-Act61 and an operation is performed to put the product to be purchased into the purchased state, the processor 41 determines Yes in Act60 and proceeds to Act62.
In Act 62, the processor 41 generates a check request for instructing the product to be purchased to be in the purchased state. The check request includes the shopping target list ID, the purchase plan ID of the selected purchase plan product, and the member ID stored in the RAM 43 or the auxiliary storage device 44 . The processor 41 then instructs the communication interface 45 to transmit the generated check request to the support server 10 . Upon receiving this instruction, the communication interface 45 transmits the check request to the support server 10 . The transmitted check request is received by the communication interface 15 of the support server 10 .

On the other hand, in Act 221 of FIG. 18, the processor 11 of the support server 10 determines whether or not the communication interface 15 has received a check request. If the communication interface 15 has not received a check request, the processor 11 determines No in Act 221 and proceeds to Act 222 .

In Act 222, the processor 11 determines whether or not the communication interface 15 has received a cancel request. Note that the cancellation request will be described later. If the communication interface 15 has not received a cancel request, the processor 11 determines No in Act 222 and proceeds to Act 223 .

In Act 223, the processor 11 determines whether or not the communication interface 15 has received a purchase request. The purchase request will be described later. If the communication interface 15 has not received a purchase request, the processor 11 determines No in Act 223 and proceeds to Act 224 .

In Act 224, the processor 11 determines whether or not the communication interface 15 has received a payment request. The payment request will be described later. If the communication interface 15 has not received a payment request, the processor 11 determines No in Act 224 and returns to Act 221 . Thus, the processor 11 repeats Act221-Act224 until a check request, cancellation request, purchase request or payment request is received.

If the processor 11 receives a check request while in the standby state of Act221 to Act224, it determines Yes in Act221 and proceeds to Act225. In Act225, the processor 11 sets the purchase flag associated with the purchase plan ID in the registration table T3 in order to put the purchase plan product identified by the purchase plan ID included in the check request received in Act221 in the purchased state. Set the value to True. The processor 11 also substitutes the current time for the date and time of purchase associated with the purchase schedule ID in the registration table T3.

In addition, if the processor 41 of the user terminal 40 determines that the product to be purchased is in a non-purchased state while in the standby state of Act59 to Act61 in FIG. and proceed.

In Act 63, the processor 41 generates a cancellation request for instructing the product to be purchased to be in a non-purchased state. The cancellation request includes the shopping target list ID, the purchase plan ID of the selected purchase plan product, and the member ID stored in the RAM 43 or the auxiliary storage device 44 . The processor 41 then instructs the communication interface 45 to transmit the generated cancellation request to the support server 10 . Upon receiving this instruction, the communication interface 45 transmits the cancellation request to the support server 10 . The transmitted cancellation request is received by the communication interface 15 of the support server 10 .

On the other hand, if the processor 11 receives a cancel request while in the waiting state of Act221 to Act224 in FIG. 18, it determines Yes in Act222 and proceeds to Act226.
In Act 226, the processor 11 sets the purchase flag associated with the purchase plan ID in the registration table T3 in order to set the purchase plan product identified by the purchase plan ID included in the cancellation request received in Act 222 to an unpurchased state. Set the value to False.

After processing Act225 or Act226, the processor 11 proceeds to Act227.
In Act 227, the processor 11 sends a second message indicating that the purchase plan product specified by the purchase plan ID included in the check request or cancellation request received in Act 221 or Act 222 has been changed to the purchased state or the non-purchased state. Generate a completion notification for . The second completion notification includes the shopping list identified by the shopping list ID included in the check request or cancellation request received in Act221 or Act222. The processor 11 then instructs the communication interface 15 to transmit the generated second completion notification to the user terminal 40 . Upon receiving this instruction, the communication interface 15 transmits the second completion notification to the user terminal 40 . The transmitted second completion notification is received by the communication interface 45 of the user terminal 40 .
After processing Act227, the processor 11 returns to Act224.

On the other hand, the processor 41 of the user terminal 40 proceeds to Act64 after processing Act62 or Act63 in FIG.
In Act 64 processor 41 waits for a second completion notification to be received by communication interface 45 . If the second completion notification is received, the processor 41 determines Yes in Act64 and proceeds to Act65.

At Act 65 , the processor 41 causes the RAM 43 or auxiliary storage device 44 to store the shopping list included in the second completion notification received at Act 64 . The processor 41 overwrites the shopping list already stored in the RAM 43 or the auxiliary storage device 44 with the shopping list. After processing Act65, the processor 41 returns to Act53. Note that the list screen SC1 displayed in the process of Act53 when returning from Act65 to Act53 is based on the shopping list overwritten by the process of Act65.

On the other hand, if the barcode attached to the product is read by the camera 48 while the processor 41 is in the standby state of Act 104 and Act 105 in FIG.
In Act 106, the processor 41 generates a purchase request for requesting purchase registration of the bar code read in Act 104. FIG. The purchase request includes the shopping list ID and the commodity ID recorded in the bar code. The processor 41 then instructs the communication interface 45 to transmit the generated purchase request to the support server 10 . Upon receiving this instruction, the communication interface 45 transmits the purchase request to the support server 10 . The transmitted purchase request is received by the communication interface 15 of the support server 10 .

On the other hand, if the processor 11 of the support server 10 receives a purchase request while in the standby state of Act221 to Act224 in FIG. 18, it determines Yes in Act223 and proceeds to Act241 in FIG. The merchandise ID included in the purchase request received in Act 223 or Act 230 is hereinafter referred to as the "registration target ID".
In Act 241, the processor 11 generates a product information request to acquire information on the product specified by the registration target ID. The product information request includes the product ID. The processor 11 then instructs the communication interface 15 to transmit the generated product information request to the POS server 20 . Upon receiving this instruction, the communication interface 15 transmits the product information request to the POS server 20 . The transmitted product information request is received by the communication interface 25 of the POS server 20 .
On the other hand, when the POS server 20 receives the product information request, it refers to the product DB 241 to acquire product information about the product specified by the product ID included in the product information request. The POS server 20 then transmits the product information to the support server 10 .

On the other hand, in Act 242 of FIG. 19, the processor 11 of the support server 10 waits for product information to be received by the communication interface 25 . If the product information is received, the processor 11 determines Yes in Act 242 and proceeds to Act 243 . The following description will be made on the assumption that the product name of the product information received in Act 242 is "Shinano Gold". "Shinano Gold" is a kind of apple.

In Act 243, processor 11 creates a transaction file if the transaction file has not yet been created. Processor 11 stores the transaction file in auxiliary storage device 14 or the like in association with the shopping list ID included in the purchase request. The transaction file includes member information including a member ID, a product list that is a list of products registered as purchased products, a shopping target list ID, and the like. Processor 11 then updates the transaction file based on the product information received in Act 242 . That is, the processor 11 registers the product specified by the product ID in the product list included in the transaction file based on the registration target ID and product information received in Act 242 .

In Act 244, the processor 11 determines whether or not the shopping list identified by the shopping target list ID includes a product to be purchased that has the same name as the product identified by the registration target ID. For example, when the product specified by the registration target ID is "Shinano Gold", the processor 11 refers to the list DB 142 and selects a purchase item whose name is "Shinano Gold" in the shopping list specified by the shopping target list ID. Determine whether or not the planned product is included. If the shopping list specified by the shopping target list ID includes the product to be purchased with the same name as the product specified by the registration target ID, the processor 11 determines Yes in Act 244 and proceeds to Act 245 . Note that even if the shopping list includes "apple", since "shinano gold" and "apple" are not identical names, the processor 11 determines that "shinano gold" is "apple" in the processing of Act 244. do not specify

In Act 245, the processor 11 sets the purchase flag associated with the purchase plan ID corresponding to the purchase plan product in the registration table T3 in order to put the same purchase plan product as the product specified by the registration object ID into the purchased state. Set the value to True.

In Act 246, the processor 11 generates a third completion notification indicating that the product specified by the registration target ID has been registered in the transaction file. The third completion notice includes the shopping list identified by the shopping list ID included in the purchase request. The processor 11 then instructs the communication interface 15 to transmit the generated third completion notice to the sender of the purchase request. Upon receiving this instruction, the communication interface 15 transmits the third completion notification to the user terminal 40, for example. The third completion notification sent to user terminal 40 is received by communication interface 45 .

On the other hand, in Act 107 of FIG. 16, the processor 41 of the user terminal 40 waits for the communication interface 45 to receive the second completion notification or the third completion notification. If the second completion notification or the third completion notification is received, the processor 41 determines Yes in Act 107 and returns to Act 104 .

Also, if the processor 41 receives the second completion notification or the third completion notification while in the standby state of Act54 to Act57 in FIG. 14, it determines Yes in Act56 and proceeds to Act66.
At Act 66 , the processor 41 causes the RAM 43 or auxiliary storage device 44 to store the shopping list included in the third completion notification received at Act 56 . The processor 41 overwrites the shopping list already stored in the RAM 43 or the auxiliary storage device 44 with the shopping list. After processing Act66, the processor 41 returns to Act53.

On the other hand, in Act 247 of FIG. 19, the processor 11 of the support server 10 determines whether or not the POS terminal 50 is the transmission source of the purchase request. If the source of the purchase request is not the POS terminal 50, the processor 11 determines No in Act247 and returns to Act224 in FIG.

If the shopping list specified by the shopping target list ID does not include the product to be purchased with the same name as the product specified by the registration target ID, the processor 11 determines No in Act 244 and proceeds to Act 248. move on.

In Act 248, the processor 11 uses the linking dictionary to confirm that the alias of the product name specified by the registration target ID is the same as the name of any product to be purchased included in the shopping list specified by the shopping target list ID. explore something like That is, the processor 11 searches the dictionary table T4 for a record whose product name is the product name specified by the registration target ID and whose alias is the same as the name of any product to be purchased included in the shopping list. do. Alternatively, the processor 11 searches the dictionary table T4 for a record whose product ID is the ID to be registered and whose alias is the same as the name of any product to be purchased included in the shopping list. Further, when the processor 11 finds the record, the processor 11 causes the RAM 13 or the like to store the purchase plan ID of the purchase plan product having the same name as the alias of the record.
For example, if the product name specified by the registration target ID is "Shinano Gold" and the product names of the products included in the shopping list are "bread", "beef", "apple", . . . , do the following: That is, the processor 11 searches the dictionary table T4 for a record whose product ID is the ID to be registered or a record whose product name is "Shinano Gold", and extracts a record that meets the conditions. Then, the processor 11 searches for a record whose alias matches any of the product names “bread”, “beef”, “apples”, . As a result, for example, if there is a record in the dictionary table T4 in which the product name is "Shinano Gold" and the alias is "Apple", the processor 11 finds the record.

In Act249, the processor 11 determines whether or not a record that satisfies the conditions is found by the processing of Act248. If the processor 11 finds a record that satisfies the conditions by the processing of Act248, it determines Yes in Act249 and proceeds to Act250.

In Act 250, the processor 11 sets the value of the purchase flag associated with the purchase plan ID stored in Act 248 in the registration table T3 to True in order to put the product to be purchased identified by the purchase plan ID stored in Act 248 in the purchased state. to After processing Act250, the processor 11 proceeds to Act246.

On the other hand, if the processor 11 fails to find a record that satisfies the condition by the processing of Act248, it determines No in Act249 and proceeds to Act251. For example, the processor 11 determines No in Act249 when "shinano gold" and "apple" are not associated in the dictionary table T4.
In Act 251, the processor 11 associates the registration object ID with the shopping object list ID. That is, the processor 11 adds a record in which the product ID is the registration target ID and the list ID is the shopping target list ID to the relation table T5.

In Act 252, the processor 11 searches for identifying the alias of the product identified by the registration target ID. First, the processor 11 extracts records whose product ID is the ID to be registered from the relation table T5. Further, the processor 11 refers to the registration table T3 and extracts the name associated with the shopping list identified by the shopping list ID included in the extracted record (hereinafter referred to as "extraction target list"). Furthermore, the processor 11 counts the number of extracted names for each extracted name. For example, if there are n items in the extraction target list that include products to be purchased whose name is "apple", the count of apples is n. Then, the processor 11 selects the name with the highest count from among the names already associated with the registration target ID as alias names in the dictionary table T4, and determines the name with the highest count as the candidate for the alias name of the product specified by the registration target ID. The alternative name candidate is an example of the first name. Also, the product name of the product specified by the registration target ID is an example of the second name.

In Act 253, the processor 11 determines whether or not an alias candidate (hereinafter referred to as "target candidate") that is highly likely to be the alias of the product specified by the registration target ID is found. That is, the processor 11 determines that the target candidate has not been found when the alias candidate has not been found by the processing of Act 252 . Then, when an alias candidate is found by the processing of Act 252, the processor 11 determines that the target candidate has been found if the conditions are satisfied. On the other hand, the processor 11 determines that no target candidate is found when the condition is not satisfied. Three types (A) to (C) are shown below as examples of the conditions. Note that the target candidate is an example of the first name.
(A) Condition A
The value of count n is greater than or equal to a predetermined threshold. The threshold is determined by, for example, the designer or administrator of the support system 1 .
(B) Condition B
(Number of lists to be extracted)/(Number of shopping lists included in list DB 142) is equal to or greater than a predetermined threshold. The threshold is determined by, for example, the designer or administrator of the support system 1 .
(C) Condition C
(value of count n)/(number of lists to be extracted) is equal to or greater than a predetermined threshold. The threshold is determined by, for example, the designer or administrator of the support system 1 .

If the target candidate is found, the processor 11 determines Yes in Act253 and proceeds to Act254.
In Act 254, the processor 11 generates a confirmation request to have the user of the shopping support service confirm that the target candidate is another name for the product specified by the registered target ID. The confirmation request includes the target candidate and the product name specified by the registered target ID. For example, the confirmation request includes "apple" as the target candidate and "shinano gold" as the product name. The processor 11 then instructs the communication interface 15 to transmit the generated confirmation request to the sender of the purchase request. Upon receiving this instruction, the communication interface 15 transmits the confirmation request to the user terminal 40, for example. The transmitted confirmation request is received by the communication interface 45 of the user terminal 40 .

On the other hand, if the processor 41 of the user terminal 40 receives a request such as a confirmation request while in the standby state of Act54 to Act57 in FIG. 14, it determines Yes in Act55 and proceeds to Act81 in FIG. .
At Act81, the processor 41 determines whether the request received at Act54 is a confirmation request. If the request received in Act54 is a confirmation request, the processor 41 determines Yes in Act81 and proceeds to Act82.

In Act 82, the processor 41 generates an image corresponding to the first confirmation screen. Processor 41 then instructs display device 47 to display this generated image. In response to this instruction, the display device 47 displays the first confirmation screen.
The first confirmation screen is a screen for asking the operator of the user terminal 40 whether it is correct that the target candidate included in the confirmation request is an alias of the product name included in the confirmation request. The first confirmation screen includes, for example, a character string S31, an affirmative button B31 and a negative button B32. The character string S31 is, for example, "Is 'Shinano Gold''Ringo'?" is a string such as The affirmative button B31 is a button to be operated when the operator of the user terminal 40 determines that the target candidate is another name for the product name. The deny button B32 is a button that is operated when the operator of the user terminal 40 determines that the target candidate is not another name for the product name.

In Act83, the processor 41 waits for the operation of the affirmative button B31 or the negative button B32 displayed on the first confirmation screen. If the affirmative button B31 or the negative button B32 is operated, the processor 41 determines Yes in Act83 and proceeds to Act84.

In Act84, the processor 41 generates an acknowledgment indicating which of the affirmative button B31 and the negative button B32 has been operated. The processor 41 then instructs the communication interface 45 to transmit the generated acknowledgment to the support server 10 . Upon receiving this instruction, the communication interface 45 transmits the confirmation response to the support server 10 . The sent acknowledgment is received by the communication interface 15 of the assistance server 10 . After processing Act84, the processor 41 returns to Act54 in FIG.

Meanwhile, at Act 255 of FIG. If the selection response is received, the processor 11 determines Yes in Act 255 and proceeds to Act 256 .

In Act256, the processor 11 determines whether the confirmation response received in Act255 indicates that the Yes button B31 has been operated. If the confirmation response received in Act255 indicates that the Yes button B31 has been operated, the processor 11 determines Yes in Act256 and proceeds to Act257.

In Act 257, the processor 11 updates the linking dictionary. That is, processor 11 adds a record to dictionary table T4. In the record, the product ID is the registration target ID, the product name is the product name specified by the registration target ID, and the alias is the target candidate. For example, the record has a trade name of "Shinano Gold" and an alias of "Apple". As a result, it is recorded in the linking dictionary that another name for "Shinano Gold" is "apple".

On the other hand, if the target candidate is not found, the processor 11 determines No in Act 253 and proceeds to Act 258 . If the confirmation response received in Act255 indicates that the deny button B32 has been operated, the processor 11 determines No in Act256 and proceeds to Act258.

In Act 258, the processor 11 selects to allow the user of the shopping support service to select which product to be purchased included in the shopping list identified by the shopping list ID that the alias of the product identified by the registration target ID indicates. Generate a request. The selection request includes the product name specified by the registration target ID. For example, the confirmation request includes "Shinano Gold" as the product name. The processor 11 then instructs the communication interface 15 to transmit the generated selection request to the sender of the purchase request. Upon receiving this instruction, the communication interface 15 transmits the selection request to the user terminal 40, for example. The transmitted selection request is received by the communication interface 45 of the user terminal 40 .

On the other hand, if the processor 41 of the user terminal 40 receives a request such as a selection request while in the standby state of Act54 to Act57 in FIG. 14, it determines Yes in Act55 and proceeds to Act81 in FIG. .
Then, if the request received in Act54 is not a confirmation request, the processor 41 determines No in Act81 and proceeds to Act85.
At Act 85, processor 41 determines whether the request received at Act 54 is a select request. If the request received in Act54 is not a selection request, the processor 41 determines No in Act85 and performs processing according to the received request. On the other hand, if the request received in Act54 is a selection request, the processor 41 determines Yes in Act85 and proceeds to Act86.

In Act86, the processor 41 generates an image corresponding to the first selection screen. Processor 41 then instructs display device 47 to display this generated image. In response to this instruction, the display device 47 displays the first selection screen.
The first selection screen is a screen for asking the operator of the user terminal 40 which product to be purchased included in the shopping list specified by the shopping list ID indicated by the product name included in the selection request. . The first selection screen includes, for example, a character string S41, multiple selection buttons B41, and a negative button B42. The character string S41 is, for example, "Which of the following products is 'Shinano Gold' to be purchased?" is a string such as A plurality of selection buttons B41 each indicate a product to be purchased included in the shopping list stored in the RAM43 or the auxiliary storage device 44. FIG. Therefore, as in the area A1 of the list screen SC1, for example, a plurality of buttons B41 corresponding to bread, beef, apples, pork, onions, grapes, etc. are displayed. The deny button B42 is a button operated by the operator of the user terminal 40 when the product name included in the selection request is not any of the products to be purchased included in the shopping list.

In Act87, the processor 41 waits for any one of the plurality of selection buttons B41 and negative buttons B42 to be operated. If any one of the multiple selection buttons B41 and Negative button B42 is operated, the processor 41 determines Yes in Act87 and proceeds to Act88.

In Act88, the processor 41 generates a selection response indicating which one of the multiple selection buttons B41 and the negative button B42 has been operated. When the selection response indicates that the selection button B41 has been operated, the selection response includes the name corresponding to the selection button B41. For example, the name is "apple". The processor 41 then instructs the communication interface 45 to transmit the generated selection response to the support server 10 . Upon receiving this instruction, the communication interface 45 transmits the selection response to the support server 10 . The transmitted selection response is received by the communication interface 15 of the assistance server 10 . After processing Act88, the processor 41 returns to Act54 in FIG.

Meanwhile, at Act 259 of FIG. If the selection response is received, processor 11 determines Yes in Act 259 and proceeds to Act 260 .

In Act260, the processor 11 determines whether or not the acknowledgment received in Act255 indicates that any of the selection buttons B41 has been operated. If the acknowledgment received in Act255 indicates that the deny button B42 has been operated, the processor 11 determines No in Act260 and proceeds to Act246. On the other hand, if the acknowledgment received in Act255 indicates that any of the selection buttons B41 has been operated, the processor 11 determines Yes in Act260 and proceeds to Act261.

In Act261, the processor 11 updates the linking dictionary. That is, processor 11 adds a record to dictionary table T4. The record is a name whose product ID is the registration target ID, product name is the product name specified by the registration target ID, and alias is the name included in the selection response. For example, the record has a trade name of "Shinano Gold" and an alias of "Apple". As a result, it is recorded in the linking dictionary that another name for "Shinano Gold" is "apple".

After processing Act257 or Act261, the processor 11 proceeds to Act262.
In Act 262, the processor 11 changes the value of the purchase flag associated with the purchase plan ID corresponding to the purchase plan product indicated by the registration target ID in the registration table T3 in order to put the purchase plan product indicated by the registration object ID into the purchased state. to True. After processing Act262, the processor 11 proceeds to Act246.

If the processor 41 of the user terminal 40 is in the standby state of Act54 to Act57 in FIG. proceed to

In Act 67, the processor 41 determines whether or not the shopping list stored in the RAM 43 or the auxiliary storage device 44 includes an unpurchased product to be purchased. If the shopping list stored in the RAM 43 or the auxiliary storage device 44 contains an unpurchased product to be purchased, the processor 41 determines Yes in Act 67 and proceeds to Act 68 .

In Act 68, the processor 41 controls to perform an operation for notifying the operator of the user terminal 40 that there is an unpurchased product to be purchased. The operation is, for example, notification by screen display or sound.

On the other hand, if there is no unpurchased product to be purchased in the shopping list, the processor 41 determines No in Act 67 and proceeds to Act 69 . The processor 41 also proceeds to Act69 after the processing of Act68.
In Act 69, the processor 41 inputs a payment command to the self-scan application to instruct payment.

On the other hand, if the processor 41 receives a settlement command while it is in the standby state of Act104 and Act105 in FIG. 16, it determines Yes in Act105 and proceeds to Act108.

In Act 108, the processor 41 generates a payment request indicating that payment will be made. The payment request includes the shopping list ID stored in RAM 43 or auxiliary storage device 44 . The processor 41 then instructs the communication interface 45 to transmit the generated payment request to the support server 10 . Upon receiving this instruction, the communication interface 45 transmits the payment request to the support server 10 . The transmitted payment request is received by the communication interface 15 of the support server 10 .

On the other hand, if the processor 11 of the support server 10 receives a payment request while in the standby state of Act221 to Act224 in FIG.

On the other hand, the operator of the user terminal 40 causes the camera 48 to read the bar code attached to the POS terminal 50 for accounting.
In Act 109 of FIG. 16, the processor 41 of the user terminal 40 waits for the bar code storing the POSID to be read by the camera 48 . If the barcode storing the POSID is read, the processor 41 determines Yes in Act 109 and proceeds to Act 110 .

At Act 110 , the processor 41 instructs the communication interface 45 to send the POSID stored in the bar code read at Act 109 to the support server 10 . Upon receiving this instruction, the communication interface 45 transmits the POSID to the support server 10 . The transmitted POSID is received by the communication interface 15 of the support server 10 .

Meanwhile, at Act 228 of FIG. If the POSID is received, the processor 11 determines Yes in Act 228 and proceeds to Act 229 .

In Act 229, the processor 11 transmits the shopping list identified by the shopping target list ID included in the payment request received in Act 224 and the transaction file associated with the target list to the POS terminal 50 identified by the POSID.

On the other hand, in Act 301 of FIG. 20, the processor 501 of the POS terminal 50 determines whether the communication interface 15 has received the shopping list and the transaction file. If the shopping list and transaction file have not been received, processor 501 determines No in Act 301 and proceeds to Act 302 .

In Act 302, the processor 501 determines whether or not an operation has been performed to log the POS terminal 50 into the shopping support service. If an operation for logging in to the shopping support service has not been performed, the processor 501 determines No in Act 302 and returns to Act 301 . Thus, processor 501 repeats Acts 301 and 302 until a shopping list and transaction file are received or an operation is performed to log in to the shopping assistance service.

If the shopping list and the transaction file are received while the processor 501 is in the standby state of Acts 301 and 302, the processor 501 determines Yes in Act 301 and proceeds to Act 303. FIG.

In Act 303, processor 501 stores the shopping list and transaction file received in Act 301 in RAM 503, auxiliary storage device 504, or the like. In Act 304 the processor 501 causes the display device 507 to display the product list included in the transaction file received in Act 301 .
In Act305, the processor 501 causes the customer-side touch panel 508 to display the shopping list received in Act301.

The shopper can log in to the shopping support service using the POS terminal 50 by, for example, operating the customer-side touch panel 508 and inputting information necessary for logging in. By this operation, the POS terminal 50 stores the member ID and the like used for login in the auxiliary storage device 504RAM503 and the like.
The processor 501 determines Yes in Act 302 and proceeds to Act 306 if the POS terminal 50 is operated to log in to the shopping support service while in the standby state of Acts 301 and 302 .

On the other hand, if the processor 11 of the support server 10 is in the standby state of Act201 to Act203 in FIG. 17 and the login is performed from the POS terminal 50, it determines Yes in Act203 and proceeds to Act231 in FIG. .

On the other hand, in Act 306 of FIG. 20, processor 501 obtains the shopping list from support server 10 . The shopping list acquired here is, for example, the shopping list associated with the member ID stored in the auxiliary storage device 504 RAM 503 and having the latest creation date and time. Alternatively, the shopping list acquired here is a shopping list specified in advance by the member identified by the member ID.

In Act 307, the processor 501 determines whether or not an operation has been performed to complete product registration and start payment. That is, the processor 501 determines whether or not a predetermined operation such as touching a subtotal button displayed on the display device 507 has been performed. The processor 501 determines No in Act 307 and proceeds to Act 308 if an operation to instruct completion of registration is not performed.

In Act 308, the processor 501 determines whether or not a product ID has been input. Note that the product ID is input to the processor 501 as shown below as an example. The operator of the POS terminal 50 causes the scanner 509 to read the bar code attached to the product. As a result, the product ID recorded in the bar code is input to the processor 501 . If the product ID is not input, the processor 501 determines No in Act 308 and returns to Act 307 . Thus, the processor 501 repeats Acts 307 and 308 until an operation for starting payment is performed or a product ID is entered.

On the other hand, in Act111 of FIG. 16, the processor 41 of the user terminal 40 inputs an end command to the list application. The processor 41 terminates the self-scan application after the process of Act111.

On the other hand, in Act 70 of FIG. 15, the processor 41 waits for an end command to be input to the list application. If the end command is input, the processor 41 determines Yes in Act70 and returns to Act3 in FIG.

On the other hand, the processor 501 of the POS terminal 50 determines Yes in Act 308 and proceeds to Act 309 if the product ID is input while in the standby state of Acts 307 and 308 .
In Act 309 , the processor 501 generates a purchase request for requesting purchase registration of the product identified by the product ID input in Act 308 . The purchase request includes the shopping target list ID and the product ID entered in Act 308 . The processor 501 then instructs the communication interface 505 to transmit the generated purchase request to the support server 10 . Upon receiving this instruction, the communication interface 505 transmits the purchase request to the support server 10 . The transmitted product ID is received by the communication interface 15 of the support server 10 .

On the other hand, in Act 230 of FIG. 18, the processor 11 of the support server 10 determines whether or not the communication interface 15 has received a purchase request. If the purchase request has not been received, the processor 11 determines No in Act 230 and proceeds to Act 231 .

In Act 231 , the processor 11 determines whether or not the communication interface 15 has received a termination notification. If the end notification has not been received, the processor 11 determines No in Act 231 and returns to Act 230 . Thus, processor 11 repeats Act 230 and Act 231 until communication interface 15 receives a purchase request or termination notice.

If the processor 11 receives a purchase request through the communication interface 15 while it is in the standby state of Act230 and Act231, it determines Yes in Act230 and proceeds to Act241 in FIG.
18 to Act 241 in FIG. 19, the communication interface 15 transmits the third completion notification to the POS terminal 50 in Act 246. FIG. The transmitted third completion notification is received by the communication interface 55 of the POS terminal 50 . Similarly, in Act 254 the communication interface 15 sends a confirmation request to the POS terminal 50 . The transmitted confirmation request is received by the communication interface 55 of the POS terminal 50 . Similarly, in Act 258 the communication interface 15 sends a selection request to the POS terminal 50 . The transmitted selection request is received by the communication interface 55 of the POS terminal 50 .
If the source of the purchase request is the POS terminal 50, the processor 11 determines Yes in Act247 and returns to Act231 in FIG.

On the other hand, in Act 310 of FIG. 20, the processor 501 of the POS terminal 50 waits for the communication interface 15 to receive the third completion notification. If the third completion notification is not received, the processor 501 determines No in Act 310 and proceeds to Act 311 .

In Act 311 processor 501 determines whether a request, such as a confirmation request or a selection request, has been received by communication interface 45 . If a request such as a confirmation request or a selection request has not been received, the processor 501 determines No in Act 311 and returns to Act 310 . Thus, processor 501 repeats Acts 310 and 311 until a third completion notification or request is received. If the processor 501 receives the third completion notification in the standby state of Act310 and Act311, it determines Yes in Act310 and proceeds to Act312.

In Act 312, the processor 501 adds the product identified by the product ID input in Act 308 to the product list stored in the auxiliary storage device 504 or the like. Also, based on the product list, the processor 501 updates the product list displayed on the display device 507 .
As described above, it is possible to register in the transaction list by reading the barcode with the POS terminal 50 even for products whose barcode is not read by the self-scan application.

In Act313, the processor 501 causes the RAM 503, auxiliary storage device 504, or the like to store the shopping list included in the second completion notification received in Act310. Note that the processor 501 overwrites the shopping list already stored in the RAM 503 or the auxiliary storage device 504 with the shopping list. In addition, processor 501 updates the shopping list displayed on customer-side touch panel 508 based on the shopping list. Note that the processor 501 skips the processing of Act 313 when the third completion notification is received in Act 310 . After processing Act313, the processor 501 returns to Act307.

Also, if the processor 501 receives a request such as a confirmation request or a selection request in the standby state of Acts 310 and 311, it determines Yes in Act 310 and proceeds to Act 321 in FIG.
At Act 321, the processor 501 determines whether the request received at Act 311 is a confirmation request. If the request received in Act 311 is a confirmation request, the processor 501 determines Yes in Act 321 and proceeds to Act 322 .

In Act 322, the processor 501 generates an image corresponding to the second confirmation screen. The processor 501 then instructs the customer-side touch panel 508 to display the generated image. In response to this instruction, the customer-side touch panel 508 displays the second confirmation screen.
The second confirmation screen is a screen for asking the operator of the POS terminal 50 whether or not the target candidate included in the confirmation request is the correct name of the product name included in the confirmation request. The display contents of the second confirmation screen are the same as those of the first confirmation screen.

In Act323, the processor 501 waits for the operation of the affirmative button B31 or the negative button B32 displayed on the second confirmation screen. If the affirmative button B31 or the negative button B32 is operated, the processor 501 determines Yes in Act323 and proceeds to Act324.

At Act 324, processor 501 generates an acknowledgment. The processor 501 then instructs the communication interface 505 to transmit the generated acknowledgment to the support server 10 . Upon receiving this instruction, the communication interface 505 transmits the confirmation response to the support server 10 . The sent acknowledgment is received by the communication interface 15 of the assistance server 10 . After processing Act 324, the processor 501 returns to Act 310 of FIG.

If the request received in Act 311 of FIG. 21 is not a confirmation request, the processor 501 determines No in Act 321 and proceeds to Act 325 .
At Act 325, processor 501 determines whether the selection received at Act 311 is a confirmation request. If the selection received in Act 311 is not a confirmation request, the processor 501 determines No in Act 325 and performs processing according to the received request. Conversely, if the selection received at Act 311 is a confirmation request, processor 501 determines Yes at Act 325 and proceeds to Act 326 .

In Act 326, the processor 501 generates an image corresponding to the second selection screen. The processor 501 then instructs the customer-side touch panel 508 to display the generated image. In response to this instruction, the customer-side touch panel 508 displays the second selection screen.
The second selection screen is a screen for asking the operator of the POS terminal 50 which products to be purchased included in the shopping list specified by the shopping list ID are to be shown. The display contents of the second selection screen are the same as those of the first selection screen.

In Act327, the processor 501 waits for any one of the plurality of selection buttons B41 and negative buttons B42 to be operated. The processor 501 determines Yes in Act 327 and proceeds to Act 328 if any one of the plurality of selection buttons B41 and Negative button B42 is operated.

At Act 328 processor 501 generates a selection response. The processor 501 then instructs the communication interface 505 to send the generated selection response to the support server 10 . Upon receiving this instruction, the communication interface 505 transmits the selection response to the support server 10 . The transmitted selection response is received by the communication interface 15 of the assistance server 10 . After processing Act 328, the processor 501 returns to Act 310 of FIG.

The processor 501 determines Yes in Act 307 and proceeds to Act 314 if an operation for completing product registration is performed while in the standby state of Act 307 and Act 308 .

In Act 314, the processor 501 determines whether or not the shopping list stored in the RAM 503 or the auxiliary storage device 504 includes an unpurchased product to be purchased. If the shopping list stored in the RAM 503 or the auxiliary storage device 504 contains an unpurchased product to be purchased, the processor 501 determines Yes in Act 314 and proceeds to Act 315 .

In Act 315, the processor 501 controls to perform an operation for notifying the shopper that there is an unpurchased product to be purchased. The operation is, for example, notification by screen display or sound.

On the other hand, if the shopping list stored in the RAM 503 or the auxiliary storage device 504 does not contain an unpurchased product to be purchased, the processor 501 determines No in Act 314 and proceeds to Act 316 . The processor 501 also proceeds to Act 316 after processing Act 315 .

In Act 316, the processor 501 performs settlement processing based on the product ID registered in the product list. It should be noted that the processor 501 acquires the product price and product name indicated by the product ID from the product DB 241 or the like. Since the settlement process is a well-known process, detailed description thereof will be omitted.

In Act317, the processor 501 controls the printer to issue a receipt based on the payment details in Act316.

In Act 318 , the processor 501 instructs the communication interface 505 to transmit to the POS server 20 the merchandise sales history based on the settlement details of Act 316 . Upon receiving this instruction, the communication interface 505 transmits the merchandise sales history to the POS server 20 . The product sales history also includes the list ID of the shopping list stored in the RAM 503, the auxiliary storage device 504, or the like. The transmitted merchandise sales history is received by the communication interface 25 of the POS server 20 . Based on the product sales history, the POS server 20 stores the product sales history in the history DB 242 by adding a record corresponding to each product settled in Act 316 to the history table T12. Also, the POS server 20 causes the history DB 242 to store information that associates the transaction ID corresponding to the received product sales history with the list ID included in the product sales history.

In Act 319, the processor 501 instructs the communication interface 505 to transmit to the support server 10 a completion notification indicating that the payment has been completed. Upon receiving this instruction, the communication interface 505 transmits the end notification to the support server 10 . The transmitted end notification is received by the communication interface 15 of the support server 10 . Processor 501 returns to Act 301 after processing Act 319 .

On the other hand, if the processor 11 of the support server 10 receives the end notification by the communication interface 15 while in the standby state of Act230 and Act231 of FIG. return.

According to the shopping support system 1 of the embodiment, the support server 10 identifies the name of the product to be purchased that is included in, for example, the largest number of shopping lists among the shopping lists associated with the registration target ID, using the registration target ID. It is determined as an alternative name for the product that is used. Therefore, the support server 10 can automatically update the association dictionary. Therefore, it is not necessary to manually create or update a linking dictionary.

According to the shopping support system 1 of the embodiment, the support server 10 displays a confirmation screen to confirm whether or not the alias of the product name is correct based on the operator's operation. Therefore, the support server 10 can prevent incorrect aliases from being associated with product names.

According to the shopping support system 1 of the embodiment, when the product name or alias of the product specified by the registration target ID does not match the product to be purchased included in the shopping list, the related table T5 is used to perform the registration. Associate the target ID with the list ID of the shopping list. By doing so, the search for identifying the alias of the product identified by the registration target ID can be performed at high speed. If no association is made in this way, the processor 11 needs to refer to the list DB 142 and the history DB 242, for example.

According to the shopping support system 1 of the embodiment, in the support server 10, the operator selects which purchase plan product included in the shopping list the product name of the product specified by the registration target ID is. Then, the support server 10 determines the name of the product to be purchased as another name for the product specified by the registration target ID. Therefore, it is not necessary for the operator of the shopping support system 1 or the like to manually create or update the linking dictionary. Therefore, the effort of the operator of the shopping support system 1 is reduced.

The shopping support system 1 of the embodiment can use the POS terminal 50 to log in to the shopping support service. Therefore, the user of the shopping support service can use the shopping support service even if he does not have the portable user terminal 40 .

In addition, according to the support system 1 of the embodiment, the support server 10 can be used when the shopping list includes a product to be purchased with a name that matches the product name or alias of the product whose product ID is read using the self-scan application. , the product to be purchased is put in a purchased state. Therefore, the operator of the user terminal 40 can update both the shopping list related to the list service and the transaction file related to the self-scan service by reading the bar code or the like attached to the product once.

The above embodiment can also be modified as follows.
In the above embodiment, the linking dictionary associates product names with aliases. However, the association dictionary is not limited to the product name and the alias name, and may be one that associates two names with each other.

The support server 10 may refer to the list DB 142 and the history DB 242 instead of the related table T5 to perform a search for identifying the alias of the product identified by the registration target ID. The list DB 142 and history DB 242 associate purchased products purchased based on the shopping list with the shopping list.

In the above-described embodiment, two types of methods are used for updating the association dictionary: the method indicated by Act251 to Act257 and the method indicated by Act258 to Act261. However, the support system 1 may be configured to use either one of the two methods.

The user terminal 40 may be capable of inputting the name of the product to be purchased that has been acquired from the display and placed in the basket by character input, handwriting input, voice input, or the like. In this case, the processor 11 of the support server 10 can refer to the linking dictionary and place the planned purchase product with the same name as the input alias as the purchased state.

In the above embodiment, the linking dictionary is updated in response to the product purchase registration. However, the processor 11 may, for example, update the linking dictionary during a time period when computational resources are available, such as at night. In this case, the processor 11, for example, uses each product ID included in the product DB 241 instead of the registration target ID, and performs the same processing as Act252 to Act257. However, in this case, the processor 11 skips the processing of Act254 to Act256. Also, the threshold value in this case may be a value different from that in the above embodiment.

The user terminal 40 may be a digital signage installed in the store, a distributed kiosk terminal, or the like. A plurality of such digital signage or distributed kiosk terminals are installed, for example, in a store. A shopper, for example, after picking up an item from a shelf or the like, uses any nearby digital signage or distributed kiosk terminals to log into the listing and self-scanning services. Then, the shopper performs an operation to put the product to be purchased corresponding to the product in the purchased state. In the above case, the user of the shopping assistance service can use the shopping assistance service even if he or she does not have a portable user terminal 40 .
The user terminal 40 may be a terminal attached to a shopping cart or the like. The shopper uses the terminal to log into the list service and self-scan service. Then, the shopper picks up an item from, for example, a display shelf and puts it in a basket. At this time, the shopper performs an operation to put the product to be purchased corresponding to the product in the purchased state. In the above case, the shopper can use the shopping support service even if he or she does not have the portable user terminal 40 .
After creating a shopping list on a PC or the like in advance, the shopper can use the shopping list on a terminal attached to the digital signage, distributed kiosk terminal, or shopping cart.
The user terminal 40 or the POS terminal 50 may have a card reader or the like for reading an IC (integrated circuit) card. In this case, it may be possible to log in to the list service and the self-scan service by reading the IC card into the user terminal 40 . In this case, the operator of the user terminal 40 or the POS terminal 50 does not need to enter a login ID or the like. Since the member card of the store can also be used as an IC card for logging in, it is particularly suitable for terminals attached to the above-mentioned digital signage, distributed kiosk terminals, shopping carts, and the like.
The user terminal 40 or the POS terminal 50 may have a device for biometric authentication. In this case, it may be possible to log in to the list service and the self-scan service by performing biometric authentication. In this case, the operator of the user terminal 40 or the POS terminal 50 does not need to enter a login ID or the like. Furthermore, the operator of the user terminal 40 or the POS terminal 50 does not need to carry an IC card for login. For this reason, it is particularly suitable for terminals attached to digital signage, distributed kiosks or shopping baskets as described above.

The user terminal 40 may be equipped with a scanner for reading barcodes instead of the camera 48 .
The support system 1 may use IC tags instead of bar codes. In this case, the user terminal 40 and the POS terminal 50 read the IC tag instead of the barcode. The user terminal 40 and the POS terminal 50 read the IC tag using an NFC (near field radio communication) reader or the like.

The user terminal 40 may perform part of the processing performed by the support server 10 in the above embodiment. Further, the support server 10 may perform part of the processing performed by the user terminal 40 in the above embodiment.
The POS terminal 50 may perform part of the processing performed by the support server 10 in the above embodiment. Also, the support server 10 may perform part of the processing performed by the POS terminal 50 in the above embodiment.
Therefore, the support server 10, the user terminal 40, or the POS terminal 50 are examples of a shopping support device. Alternatively, the support server 10 and the user terminal 40 cooperate to operate as a shopping support device. Alternatively, the support server 10 and the POS terminal 50 cooperate to operate as a shopping support device. Also, the support system 1 is an example of a shopping support device.

While several embodiments of the invention have been described, these embodiments have been presented by way of example and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, replacements, and modifications can be made without departing from the scope of the invention. These embodiments and modifications thereof are included in the scope and gist of the invention, and are included in the scope of the invention described in the claims and equivalents thereof.
The invention described in the scope of claims at the time of filing of the present application will be additionally described below.
[C1]
Among the plurality of shopping lists associated with the purchase item purchased based on the shopping list in which the purchase item is registered, the purchase item includes the purchase item with a first name and the purchase item with a second name. A shopping support device, comprising: a control unit that associates the first name and the second name when the number of shopping lists associated with products satisfies a predetermined condition.
[C2]
The shopping support device according to C1, wherein whether or not the first name and the second name can be associated is determined based on an input by an operator.
[C3]
If the name of the product to be purchased included in the shopping list does not match the product name or alias of the purchased product, the control unit associates the purchased product with the shopping list. The shopping assistance device described.
[C4]
A control unit that associates the first name and the second name in response to input of the first name corresponding to the purchased product with the second name based on the input by the operator,
The shopping support device, wherein the first name is the name of the product to be purchased registered in the shopping list.
[C5]
Among the plurality of shopping lists associated with the purchase item purchased based on the shopping list in which the purchase item is registered, the purchase item includes the purchase item with a first name and the purchase item with a second name. A shopping support method, wherein the first name and the second name are associated when the number of shopping lists associated with products satisfies a predetermined condition.
[C6]
The computer provided with the shopping support device,
Among the plurality of shopping lists associated with the purchase item purchased based on the shopping list in which the purchase item is registered, the purchase item includes the purchase item with a first name and the purchase item with a second name. A program functioning as a control unit that associates the first name and the second name when the number of shopping lists associated with products satisfies a predetermined condition.

DESCRIPTION OF SYMBOLS 1... Support system, 10... Support server, 11, 21, 41, 501... Processor, 12, 22, 42, 502... ROM, 13, 23, 43, 503... RAM, 14, 24, 44, 504... Auxiliary memory Device, 15, 25, 45, 505... communication interface, 16, 26, 49, 510... bus, 20... POS server, 30... application server, 40... user terminal, 46, 506... input device, 47, 507 display device , 48... camera, 50... POS terminal, 508... customer-side touch panel, 509... scanner

Claims (6)

a storage unit that stores a linking dictionary that associates a first name with a second name and a plurality of shopping lists ;
an interface for obtaining a second name of the item purchased based on a first shopping list that is included in the plurality of shopping lists and includes a first name of the item;
extracting a second shopping list of a plurality of users who have purchased the product from the plurality of shopping lists;
extracting a third shopping list containing the first name from the second shopping list;
when the third shopping list exists, the first name and the second name are associated with each other based on a ratio of the number of the second shopping list to the number of the plurality of shopping lists, and the linking is performed; update the dictionary,
a control unit;
A shopping assistance device comprising: The control unit determines whether or not the first name and the second name may be associated based on an input by an operator.
The shopping support device according to claim 1. If the first name associated with the second name of the product in the association dictionary is not included in the first shopping list, the control unit updates the association dictionary.
The shopping support device according to claim 1 or 2. The control unit
updating the linking dictionary by associating the first name and the second name when the ratio is equal to or greater than a predetermined threshold ;
if the ratio is not equal to or greater than a predetermined threshold, based on the input of the first name of the product, updating the association dictionary by associating the input first name and the second name;
A shopping support device according to any one of claims 1 to 3. A shopping assistance method executed by a processor, comprising:
obtaining a second name of an item purchased based on a first shopping list that is included in a plurality of shopping lists and includes the first name of the item;
extracting a second shopping list of a plurality of users who have purchased the product from the plurality of shopping lists;
extracting a third shopping list containing the first name from the second shopping list;
if the third shopping list exists, associate the first name and the second name based on a ratio of the number of the second shopping list to the number of the plurality of shopping lists, and A shopping support method for updating a linking dictionary that associates a first name with a second name. A program executed by a processor,
to the processor;
obtaining a second name of an item purchased based on a first shopping list that includes a first name of an item included in a plurality of shopping lists ;
a function of extracting a second shopping list of a plurality of users who have purchased the product from the plurality of shopping lists;
a function of extracting a third shopping list containing the first name from the second shopping list;
if the third shopping list exists, associate the first name and the second name based on a ratio of the number of the second shopping list to the number of the plurality of shopping lists, and a function of updating a linking dictionary that associates a first name with a second name;
program to realize

Images