Information processing device and program

Abstract

To provide an information processing device and a program for supporting in purchasing a product(s) related to a shopping service.SOLUTION: In a shopping support system in which a portable terminal, a settlement terminal and a server device can communicate via a network, the server device 30 comprises: a shopping list management unit 352 for acquiring a shopping list created by a client requesting a shopping service; a shopping request management unit 353 for acquiring identification information which can identify the type(s) of a product(s) among products sold in a shop, targeted for purchase by a contractor who accepted the request and registering the same in association with the transaction of the client or the contractor; and a transaction management unit 354 for executing processing related to the settlement of both the transactions of the client and the contractor in response to instructions to complete the register or start the settlement.SELECTED DRAWING: Figure 11

Description

[Technical Field]

[0001] An embodiment of the present invention relates to an information processing device and a program. [Background technology]

[0002] BACKGROUND ART Conventionally, a user who visits a retail store (shop) such as a supermarket purchases products at the store and carries the purchased products home by himself or herself.

[0003] On the other hand, with the aging population and regional depopulation progressing, some customers find it difficult to go to stores.

[0004] Incidentally, as a shopping style for users who find it difficult to go to a store, it is assumed that the user will share a shopping list created by the user with other users and ask them to do the shopping for them. For example, a technology has been proposed in the past in which shopping lists created by users belonging to the same group are shared and the shopping lists are displayed for each user in the group.

[0005] However, with conventional technology, purchases made by a user visiting a store and purchases made based on a shopping list created by another user are treated as the same transaction, making it difficult to separate each user's share, and there is room for improvement in terms of convenience. Summary of the Invention [Problem to be solved by the invention]

[0006] The problem to be solved by the present invention is to provide an information processing device and a program that can support purchasing of products related to shopping proxy services. [Means for solving the problem]

[0007] The information processing device of the embodiment includes a first acquisition means for acquiring a shopping list created by a client who requests shopping to be performed on their behalf; a second acquisition means for acquiring identification information that can identify the type of product sold in the store that is the target of purchase by the contractor who accepted the request; a registration means for registering the identification information acquired by the second acquisition means in association with a transaction of the client or the contractor; and an execution means for executing processing related to the settlement of both the transactions of the client and the contractor in response to an instruction to end registration or start settlement. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an example of a shopping support system according to an embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of the mobile terminal according to the embodiment. [Figure 3] FIG. 3 is a diagram illustrating an example of a hardware configuration of the payment terminal according to the embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of a hardware configuration of a server device according to the embodiment. [Figure 5] FIG. 5 is a diagram illustrating an example of a data configuration of the product master according to the embodiment. [Figure 6] FIG. 6 is a diagram illustrating an example of a data configuration of a user management table according to the embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of a data configuration of a group management table according to the embodiment. [Figure 8] FIG. 8 is a diagram illustrating an example of a data configuration of a shopping list management table according to the embodiment. [Figure 9] FIG. 9 is a diagram illustrating an example of a data configuration of a shopping request management table according to the embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of a data configuration of a transaction information management table according to the embodiment. [Figure 11] FIG. 11 is a diagram illustrating an example of functional configurations of the mobile terminal, the payment terminal, and the server device. [Figure 12]FIG. 12 is a diagram illustrating an example of a product registration screen displayed on the mobile terminal according to the embodiment. [Figure 13] FIG. 13 is a diagram illustrating an example of a registration destination selection screen displayed on the mobile terminal according to the embodiment. [Figure 14] FIG. 14 is a diagram illustrating an example of a shopping list display field displayed on the mobile terminal according to the embodiment. [Figure 15] FIG. 15 is a diagram showing another example of a shopping list display field displayed on the mobile terminal according to the embodiment. [Figure 16] FIG. 16 is a diagram illustrating an example of a notification screen displayed on the mobile terminal according to the embodiment. [Figure 17] FIG. 17 is a diagram illustrating an example of a statement screen displayed on the payment terminal according to the embodiment. [Figure 18] FIG. 18 is a sequence diagram illustrating an example of a process related to a shopping proxy request executed by the mobile terminal and the server device according to the embodiment. [Figure 19] FIG. 19 is a sequence diagram illustrating an example of a process related to shopping support executed by the mobile terminal and the server device according to the embodiment. [Figure 20] FIG. 20 is a sequence diagram illustrating an example of a process related to payment executed by the payment terminal and the server device according to the embodiment. [Figure 21] FIG. 21 is a flowchart illustrating an example of a shopping support process performed by the mobile terminal according to the embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0009] An information processing device and a program according to an embodiment will be described below with reference to the drawings. In the embodiment described below, an example will be described in which the information processing device and the program are applied to a shopping support system that supports the purchase of products sold in stores such as supermarkets. However, the present invention is not limited to the embodiment described below.

[0010] 1 is a diagram illustrating an example of a shopping support system 1. As shown in FIG. 1, the shopping support system 1 includes a mobile terminal 10, a payment terminal 20, and a server device 30.

[0011] The mobile terminal 10 is an example of an information processing device. The mobile terminal 10 is a portable communication terminal, such as a smartphone or tablet terminal, carried by a customer who visits a store. By operating the mobile terminal 10, the customer can perform a registration process to register a product to be purchased. The mobile terminal 10 can communicate with other mobile terminals 10, a payment terminal 20, a server device 30, etc., via a network Na such as the Internet or a public line.

[0012] The payment terminal 20 is an example of a product sales data processing device installed in a store. The payment terminal 20 executes a payment process to make payments (also called accounting) for registered products using the mobile terminal 10. The payment terminal 20 is capable of communicating with the mobile terminal 10 and the server device 30 via the in-store network Nb.

[0013] The payment terminal 20 may be configured to be operated by a store clerk, or may be configured as a self-service terminal in which the user performs operations related to product registration and payment. The payment terminal 20 may also be configured to be capable of executing a registration process in which the user registers the products they wish to purchase.

[0014] The server device 30 provides services to support shopping for users who use the store. Note that, although the server device 30 is configured as a single device in Fig. 1, it is not limited to this, and may be a cloud configured as a plurality of server devices 30.

[0015] Next, the configuration of each device in the above-mentioned shopping support system 1 will be described.

[0016] 2 is a diagram illustrating an example of a hardware configuration of the mobile terminal 10. As illustrated in FIG. 2, the mobile terminal 10 includes a CPU (Central Processing Unit) 101, a ROM (Read Only Memory) 102, and a RAM (Random Access Memory) 103.

[0017] The CPU 101 is an example of a processor and performs overall control of the operation of the mobile terminal 10. The ROM 102 stores various programs. The RAM 103 is a workspace for loading programs and various data. The CPU 101, the ROM 102, and the RAM 103 are connected to one another via a bus 104. The CPU 101, the ROM 102, and the RAM 103 constitute a control unit 100 having a computer configuration. In the control unit 100, the CPU 101 operates in accordance with a control program 1051 stored in the ROM 102 or the memory unit 105 and loaded in the RAM 103, thereby executing various processes.

[0018] The control unit 100 is connected to a storage unit 105 and a communication unit 106 via a bus 104. The storage unit 105 is configured with an HDD (Hard Disc Drive), flash memory, etc., and maintains its stored contents even when the power is cut off. The storage unit 105 stores, for example, the user ID of the operator (user) who operates the mobile terminal 10, and a control program 1051.

[0019] The control program 1051 is a control program for controlling the operation of the mobile terminal 10. The control program 1051 may also include an application for using the services provided by the server device 30.

[0020] The communication unit 106 is a communication interface that can be connected to the network Na. The communication unit 106 communicates with the server device 30 and the like via the network Na.

[0021] Furthermore, the control unit 100 is connected to a display unit 108, an operation unit 109, an imaging unit 110, and the like via a bus 104 and an input / output controller 107. The display unit 108 is a display device such as an LCD (Liquid Crystal Display), and displays various information under the control of the control unit 100. The operation unit 109 has various operation buttons, and outputs key information according to operations by an operator to the control unit 100. Note that the operation unit 109 may be, for example, a touch panel provided on the surface of the display unit 108.

[0022] The imaging unit 110 is an imaging device having an image sensor such as a CCD (Charge Coupled Device) or a CMOS (Complementary Metal Oxide Semiconductor). The imaging unit 110 captures an image of a code symbol such as a barcode or a two-dimensional code attached to a product in a store, for example.

[0023] 3 is a diagram showing an example of the hardware configuration of payment terminal 20. As shown in FIG.

[0024] The CPU 201 is an example of a processor and controls the overall operation of the payment terminal 20. The ROM 202 stores various programs. The RAM 203 is a workspace where programs and various data are deployed. The CPU 201, the ROM 202, and the RAM 203 are connected to one another via a bus 204. The CPU 201, the ROM 202, and the RAM 203 constitute a control unit 200 having a computer configuration. In the control unit 200, the CPU 201 operates in accordance with a control program 2051 stored in the ROM 202 or the memory unit 205 and deployed in the RAM 203, thereby executing various processes.

[0025] The control unit 200 is connected to a memory unit 205 and a communication unit 206 via a bus 204. The memory unit 205 is composed of a hard disk drive (HDD), flash memory, etc., and maintains its stored contents even when the power is cut off. The memory unit 205 stores, for example, a control program 2051. The control program 2051 is a control program for controlling the operation of the payment terminal 20.

[0026] The communication unit 206 is a communication interface that can be connected to the in-store network Nb. The communication unit 206 can communicate with other payment terminals 20 via the in-store network Nb, and can also communicate with the server device 30 of the network Na.

[0027] Furthermore, the control unit 200 is connected to a display unit 208 , an operation unit 209 , a scanner unit 210 , a printer 211 , a deposit / withdrawal unit 212 , a card reading unit 213 , and the like via a bus 204 and an input / output controller 207 .

[0028] The display unit 208 is a display device such as an LCD, and displays various information under the control of the control unit 200. The operation unit 209 has various operation buttons such as numeric keys and a closing key, and outputs key information according to the operation of the operator to the control unit 200. Note that the operation unit 209 may be, for example, a touch panel provided on the surface of the display unit 208.

[0029] The scanner unit 210 is a reading device capable of reading code symbols such as barcodes, two-dimensional codes, etc. For example, the scanner unit 210 reads a user ID, payment information related to electronic payment, etc. from a code symbol displayed on the display unit 108 of the mobile terminal 10, and outputs the read information to the CPU 201.

[0030] The printer 211 prints receipts and the like showing transaction details under the control of the control unit 200. The deposit / withdrawal unit 212 has storage units (not shown) that store currency (coins and banknotes) by denomination, and performs processes such as depositing payment amounts and dispensing change.

[0031] The card reading unit 213 is a reading device that reads information from a card medium such as a magnetic card or an IC card. For example, the card reading unit 213 reads credit information related to payment of the price of a product from a credit card, and outputs the read credit information to the CPU 201. Also, for example, the card reading unit 213 reads the user ID of a registered member (hereinafter also referred to as a member) from a membership card distributed to the member, and outputs the read user ID to the CPU 201.

[0032] 4 is a diagram illustrating an example of a hardware configuration of the server device 30. As illustrated in FIG.

[0033] The CPU 301 is an example of a processor and performs overall control of the operation of the server device 30. The ROM 302 stores various programs. The RAM 303 is a workspace where programs and various data are deployed. The CPU 301, the ROM 302, and the RAM 303 are connected to one another via a bus 304. The CPU 301, the ROM 302, and the RAM 303 constitute a control unit 300 having a computer configuration. In the control unit 300, the CPU 301 operates in accordance with a control program 3051 stored in the ROM 302 or the storage unit 305 and deployed in the RAM 303, thereby executing various processes.

[0034] The control unit 300 is connected to a memory unit 305 via a bus 304. The memory unit 305 is configured with a hard disk drive (HDD), flash memory, etc., and maintains its stored contents even when the power is turned off. The memory unit 305 stores, for example, a control program 3051, a product master 3052, a user management table 3053, a group management table 3054, a shopping list management table 3055, a shopping request management table 3056, and a transaction information management table 3057.

[0035] The control program 3051 is a control program for controlling the operation of the server device 30. The control program 3051 may also include a server program for cooperating with an application installed in the mobile terminal 10.

[0036] The product master 3052 stores product information about each product sold in the store. FIG. 5 is a diagram showing an example of the data configuration of the product master 3052. As shown in FIG. 5, the product master 3052 stores product information such as product name, price, and product image in association with a product code. Here, the product code is an example of product identification information that can identify the type of product. The product name is information that indicates the name of the product identified by the product code. The price is information that indicates the unit price of the product identified by the product code. The product image is image information such as a photograph or illustration that represents the appearance or features of the product.

[0037] The user management table 3053 stores and manages the user ID of each user who has been registered in advance through procedures such as membership registration. Fig. 6 is a diagram showing an example of the data configuration of the user management table 3053. As shown in Fig. 6, the user management table 3053 stores user information and the like in association with the user ID.

[0038] The user information stores information about a user identified by a user ID, such as name, age, and gender.

[0039] Here, the user ID is an example of user identification information that can identify each user. The user ID can be, for example, unique information such as the telephone number of the mobile terminal 10 owned by the user, or a user ID used on an application installed on the mobile terminal 10. In this embodiment, the user ID also serves as destination information that can communicate with the mobile terminal 10 of the user corresponding to the user ID, but this is not limiting, and the destination information of the mobile terminal 10 may be stored separately in association with the user ID.

[0040] The name is information indicating the name of the user identified by the user ID. The age is information indicating the age of the user identified by the user ID. The gender is information indicating the gender of the user identified by the user ID.

[0041] The user information registered in the user management table 3053 is not limited to the example in Fig. 6. For example, the user information may include contact information such as the user's address and telephone number.

[0042] The group management table 3054 is a data table for storing and managing the user IDs of users who have been divided into groups. Fig. 7 is a diagram showing an example of the data configuration of the group management table 3054. As shown in Fig. 7, the group management table 3054 stores the user IDs of the members belonging to each group in association with a group ID that identifies the group.

[0043] For example, in group ID "001," five users with user IDs "U0001, U0002, U0003, U0004, and U0005" are grouped together. Also, in group ID "002," four users with user IDs "U0101, U0102, U0103, and U0104" are grouped together.

[0044] Grouping of user IDs is performed by the user via the mobile terminal 10, etc. For example, a user can group other users with whom they have a friendship relationship, other users such as relatives, other users living in the neighborhood, etc. In addition, it is preferable that the specific user described below and the users to be grouped are aware of the address of the specific user.

[0045] The shopping support system 1 of this embodiment provides shopping support to a user who cannot go to a store (hereinafter also referred to as a specific user) by acting as an intermediary between the specific user and members of the group to which the specific user belongs. Note that the specific user may be, for example, an elderly person, a user with a physical disability, a user living in a depopulated remote area, or a user who cannot go to a store for other reasons.

[0046] The shopping list management table 3055 is a data table for storing and managing shopping lists created by users. Fig. 8 is a diagram showing an example of the data configuration of the shopping list management table 3055. As shown in Fig. 8, the shopping list management table 3055 stores data of shopping lists created by users identified by their user IDs, in association with the user IDs of the users.

[0047] The shopping list stores the product code, product name, quantity, etc. of each product to be purchased. In the shopping support system 1 of this embodiment, a shopping list created by a specific user is stored in the shopping list management table 3055 in association with the user ID of the specific user, but this is not limitative. For example, the shopping list management table 3055 may also store a shopping list created by an unspecified user.

[0048] The shopping request management table 3056 is a database for storing and managing the relationship between a specific user and other users to whom the specific user has made a shopping request. FIG. 9 is a diagram showing an example of the data configuration of the shopping request management table 3056. As shown in FIG. 9, the shopping request management table 3056 stores a request number, requester information, and contractor information in association with each other. The request number is identification information for identifying each request. The requester information registers the user ID of the specific user who made the request. The contractor information registers the user ID of the user who accepted the shopping request.

[0049] The transaction information management table 3057 is a database for storing and managing products registered by users at a store. Fig. 10 is a diagram showing an example of the data configuration of the transaction information management table 3057. As shown in Fig. 10, the transaction information management table 3057 stores transaction codes, user IDs, and transaction information indicating the details of registered products in association with each other.

[0050] The transaction code is identification information for identifying each transaction. A transaction refers to the unit of commercial transaction that is the subject of payment processing. The user ID is the user ID of the user who registered the product. Specifically, the user ID field registers the user ID of the user who uses the mobile terminal 10 used to register the product. The transaction information includes the product code, product name, price, quantity, etc. of the registered product.

[0051] Here, for normal transactions, there is a one-to-one correspondence between transaction codes and user IDs. In other words, a unique transaction code is assigned to each user. On the other hand, for transactions carried out by a user (hereinafter referred to as a contractor) who accepts a request from a specific user who acts as a client, the transaction code for the client's transaction and the transaction code for the contractor's transaction are associated with the contractor's user ID. Therefore, based on the relationship between the transaction code and user ID, it is possible to distinguish between a normal transaction (hereinafter referred to as a normal transaction) and a transaction that includes shopping on behalf of the client (hereinafter referred to as a special transaction).

[0052] The data structure of the transaction information management table 3057 is not limited to that shown in Figure 10. For example, the transaction information management table 3057 may store data entries for special transactions in association with the "request number" for the transaction, in order to distinguish between normal transactions and special transactions.

[0053] Returning to Fig. 4, the control unit 300 is connected to a communication unit 306 via a bus 304. The communication unit 306 is a communication interface connectable to a network Na. The communication unit 306 can communicate with each mobile terminal 10 via the network Na, and can also communicate with a payment terminal 20 connected to an in-store network Nb.

[0054] Next, a description will be given of the functional configuration of the above-mentioned shopping support system 1. Fig. 11 is a diagram showing an example of the functional configuration of the mobile terminal 10, the payment terminal 20, and the server device 30.

[0055] 11, for the sake of convenience, the functional configurations of each of the mobile terminals 10 are shown as being divided into two mobile terminals 10 (11, 12). The mobile terminals 11 and 12 are mobile terminals 10 owned by users who are grouped into the same group.

[0056] Here, mobile terminal 11 refers to a mobile terminal 10 owned by a specific user who is a member of the same group and who will be the shopping requester. Also, mobile terminal 12 refers to a mobile terminal 10 owned by a user who is a member of the same group and who will be the contractor who will accept the request from the requester. Note that when there is no need to distinguish between mobile terminal 11 and mobile terminal 12, they are simply referred to as mobile terminal 10.

[0057] As shown in FIG. 11, the mobile terminal 10 has, as its functional configuration, a group registration unit 151, a shopping list creation support unit 152, a shopping request unit 153, a request reception unit 154, a shopping start notification unit 155, a shopping support unit 156, and a stockout notification reception unit 157, etc.

[0058] Furthermore, the payment terminal 20 includes a payment processing unit 251 and the like as functional components.

[0059] The server device 30 also includes a group management unit 351, a shopping list management unit 352, a shopping request management unit 353, a transaction management unit 354, and the like as functional components.

[0060] Some or all of the functional configurations of each of the above-mentioned devices may be software configurations realized by cooperation between the processor (CPU) of the device and various programs (e.g., control programs) stored in memory (ROM, storage unit, etc.). Also, some or all of the functional configurations of each of the above-mentioned devices may be hardware configurations realized by dedicated circuits or the like provided in the device. In Fig. 11, related functional configurations between devices are connected by dashed lines.

[0061] Group registration unit 151 of mobile terminal 11 makes a request to server device 30 to register a group in response to an operation on operation unit 109. Specifically, group registration unit 151 transmits to server device 30 a registration request including the user ID of the user operating mobile terminal 11 and the user IDs of users who will become members in response to an operation via operation unit 109.

[0062] Here, the method of specifying the user ID and the timing of the registration request are not particularly important. For example, the group registration unit 151 may accept a selection of user IDs to be grouped from a list of user IDs stored in advance in the storage unit 105.

[0063] In response to a registration request from the mobile terminal 11, the group management unit 351 of the server device 30 groups the members specified in the registration request. Specifically, the group management unit 351 associates the user IDs included in the registration request with the same group ID and registers them in the group management table 3054.

[0064] Prior to registration in the group management table 3054, the group management unit 351 may send a message to the mobile terminal 10 (mobile terminal 12) of the user identified by the user ID included in the registration request to confirm whether the user agrees to member registration. In this case, when the group management unit 351 receives a response from the mobile terminal 12 indicating consent to member registration, the group management unit 351 registers the user ID of the user corresponding to the mobile terminal 12 in the group management table 3054. When the group management unit 351 receives a response from the mobile terminal 12 indicating no consent to member registration, the group management unit 351 returns an error to the mobile terminal 11 and suppresses grouping.

[0065] The shopping list creation support unit 152 of the mobile terminal 11 supports the creation of a shopping list. For example, when the shopping list creation support unit 152 receives an instruction to start creating a shopping list via the operation unit 109, it accesses the server device 30 and displays on the display unit 108 an operation screen (not shown) (hereinafter also referred to as a product selection screen) on which candidate products for purchase can be selected from products sold in the store, based on the product master 3052 stored in the server device 30. On the product selection screen, for example, the product name, product image, price, etc. are displayed for each product sold in the store, and the number of products to be purchased can be entered.

[0066] When the shopping list creation support unit 152 receives the selection of a product to be purchased and the input of the quantity, it associates the product's product code, product name, and quantity and stores them as a shopping list in RAM 103 or the like. Furthermore, each time the shopping list creation support unit 152 receives the selection of a product and the input of the quantity, it associates the product's product code, product name, and quantity and adds them to the shopping list. Then, when the shopping list creation support unit 152 receives an instruction via the operation unit 109 to complete the creation of the shopping list, it sends a shopping list registration request to the server device 30, which includes the user ID of the operator operating the mobile terminal 11 and the shopping list.

[0067] In response to a shopping list registration request from the mobile terminal 11, the shopping list management unit 352 of the server device 30 registers the shopping list specified in the shopping list registration request in the shopping list management table 3055. Specifically, the shopping list management unit 352 associates the user ID included in the shopping list registration request with the shopping list and registers them in the shopping list management table 3055.

[0068] The shopping request unit 153 of the mobile terminal 11 requests another user who operates the mobile terminal 12 to do shopping on the user's behalf via the server device 30. For example, when the shopping request unit 153 receives an instruction to request shopping on the user's behalf via the operation unit 109, the shopping request unit 153 transmits client information including the user ID of the operator who operates the mobile terminal 11 to the server device 30.

[0069] The shopping request management unit 353 of the server device 30 cooperates with the shopping request unit 153 and the request receiving unit 154 to support shopping proxy requests and manage the relationship between the requester and the contractor. For example, when the shopping request management unit 353 receives requester information from the mobile terminal 11, it obtains the user IDs of other members of the group to which the user ID belongs from the group management table 3054 based on the user ID included in the requester information. Next, the shopping request management unit 353 transmits a member list including the obtained user IDs to the mobile terminal 11. Note that the shopping request management unit 353 may also obtain user information such as the name corresponding to the user ID of each member from the user management table 3053 and transmit the member list together with the obtained user information.

[0070] When the shopping request unit 153 of the mobile terminal 11 receives the member list from the server device 30 as a response to the requester information, it displays an operation screen (hereinafter, "member selection screen") on the display unit 108, which allows the user to select a user requesting shopping based on the member list. On the member selection screen, for example, the names of users corresponding to the user IDs included in the member list are displayed in a selectable state.

[0071] When the shopping request unit 153 receives the selection of the user requesting shopping agency, it sends a shopping agency request including the user ID of the operator who operates the user's mobile terminal 11, i.e., the user ID of the requester, and the user ID of the selected user, i.e., the user ID of the candidate contractor, to the server device 30. Note that the user ID of the requester and the user ID of the candidate contractor are transmitted in a distinguishable manner.

[0072] When the shopping request management unit 353 of the server device 30 accepts a shopping agent request from the mobile terminal 11, it sends a request notification to the mobile terminal 12 corresponding to the user ID of the potential contractor included in the shopping agent request, notifying that a shopping agent request has been made by the client included in the shopping agent request. For example, the shopping request management unit 353 obtains the name corresponding to the client's user ID from the user management table 3053, and sends a request notification including the obtained name and a message indicating that a shopping agent request has been made by the client with that name.

[0073] The request receiving unit 154 of the mobile terminal 12 is an example of a first acquisition means. The request receiving unit 154 receives a request notification for shopping proxy service from the server device 30. Upon receiving the request notification from the server device 30, the request receiving unit 154 notifies the operator of the mobile terminal 12 that a shopping proxy service request has been made by displaying the content included in the request notification on the display unit 108. The request receiving unit 154 also receives a response via the operation unit 109 as to whether or not to accept the shopping proxy service request. Upon receiving the response to the shopping proxy service request, the request receiving unit 154 transmits response information indicating the content of the response to the server device 30.

[0074] When the shopping request management unit 353 of the server device 30 receives response information from the mobile terminal 12, it determines whether the response information indicates that the request is accepted. If the response information indicates that the request is accepted, the shopping request management unit 353 sets the user ID of the mobile terminal 12 from which the response of consent was obtained as the contractor's user ID, associates it with the user ID of the client specified in the corresponding shopping agent request, and registers it in the shopping request management table 3056. Specifically, the shopping request management unit 353 registers the client's user ID in the client information field and the client's user ID in the contractor information field. The shopping request management unit 353 may issue a unique request number when registering the request in the shopping request management table 3056.

[0075] Furthermore, if the response information indicates that the request is accepted, the shopping request management unit 353 transmits response information to the mobile terminal 11 corresponding to the user ID of the requester, notifying that consent to the request has been obtained. Furthermore, if the response information indicates that the request is accepted, the shopping request management unit 353 obtains a shopping list associated with the user ID of the requester from the shopping list management table 3055, and transmits the shopping list together with the user ID of the requester, etc., to the mobile terminal 12 corresponding to the user ID of the contractor. In this case, the request receiving unit 154 of the mobile terminal 12 obtains the shopping list created by the requester from the server device 30.

[0076] The shopping list may be included in the request notification and sent. The timing at which the shopping list is provided to the contractor is not limited to this, and the shopping list may be provided to the contractor when the contractor is notified at the store that shopping has started.

[0077] On the other hand, if the response information indicates that the request will not be accepted, the shopping request management unit 353 sends response information to the mobile terminal 11 corresponding to the requester's user ID, notifying that consent to the request has not been obtained.

[0078] When the shopping request unit 153 of the mobile terminal 11 receives response information from the server device 30 as a response to the shopping agent request, the shopping request unit 153 causes the display unit 108 to display the content indicated by the response information.

[0079] The operator of mobile terminal 11 can confirm whether the request for shopping proxy service has been agreed to by looking at the content displayed on display unit 108. If the request for shopping proxy service is not agreed to, the operator of mobile terminal 11 can, for example, select another member to request shopping proxy service.

[0080] The agent who has accepted the shopping service travels to the store to purchase the requested product. The agent then operates the mobile terminal 12 at the store to notify the server device 30 that the shopping has begun.

[0081] The shopping start notification unit 155 of the mobile terminal 12 is an example of a first acquisition means. The shopping start notification unit 155 transmits a shopping start notification to the server device 30. Specifically, the shopping start notification unit 155 transmits a shopping start notification including the user ID of the operator who operates the mobile terminal 12 to the server device 30.

[0082] The method for transmitting the shopping start notification is not particularly limited, and various methods can be employed. For example, a code symbol for the shopping start notification, which includes the address of the server device 30 on the in-store network Nb, may be displayed near the entrance of the store, and the shopping start notification may be transmitted upon reading the code symbol. In this case, when the shopping start notification unit 155 of the mobile terminal 12 reads the code symbol for the shopping start notification via the imaging unit 110 of the mobile terminal 12, it transmits the shopping start notification to the address included in the code symbol. Also, for example, the shopping start notification unit 155 of the mobile terminal 12 may transmit the shopping start notification to the server device 30 upon receiving an operation to start shopping via the operation unit 109.

[0083] The transaction management unit 354 of the server device 30 manages transactions performed at the store. For example, when the transaction management unit 354 receives a shopping start notification from the mobile terminal 12, it determines that the user identified by the user ID included in the shopping start notification has visited the store. In this case, the transaction management unit 354 issues a unique transaction code for the user identified by the user ID included in the shopping start notification and transmits response information including the transaction code to the mobile terminal 12.

[0084] Furthermore, if the user ID included in the shopping start notification is registered in the contractor information field of the shopping request management table 3056, the transaction management unit 354 acquires the information registered in the request number field and requester information field of the corresponding data entry. In this case, the transaction management unit 354 issues a transaction code for the user ID in the requester information field, i.e., for the requester, and transmits this code together with the information acquired from the shopping request management table 3056 in response information to the mobile terminal 12.

[0085] In addition, the transaction management unit 354 associates the transaction code issued in response to the shopping start notification with the user ID of the operator of the mobile terminal 12 that sent the shopping start notification and registers them in the transaction information management table 3057.

[0086] In this way, when a contractor who has accepted a shopping agent request visits the store, the transaction management unit 354 issues a transaction code for the contractor and a transaction code for the client separately and transmits them to the mobile terminal 12. In addition, when a contractor who has accepted a shopping agent request visits the store, the transaction management unit 354 registers the transaction code for the contractor and the transaction code for the client in the transaction information management table 3057 in association with the contractor's user ID.

[0087] Upon receiving the shopping start notification, the transaction management unit 354 may obtain a shopping list associated with the requester's user ID from the shopping list management table 3055, and include the obtained shopping list in the response information to be sent to the mobile terminal 12. In this case, the shopping start notification unit 155 of the mobile terminal 12 obtains the shopping list created by the requester from the server device 30.

[0088] Furthermore, the transaction management unit 354 may notify the mobile terminal 11 corresponding to the client's user ID that the contractor has come to the store at the timing when the shopping start notification is received.

[0089] When the shopping start notification unit 155 of the mobile terminal 12 receives a response (response information) to the shopping start notification from the server device 30, the shopping start notification unit 155 stores the response information in the RAM 103 or the like. For example, the shopping start notification unit 155 stores a transaction code issued for the operator who operates the mobile terminal 12 in association with the user ID of the operator. Also, for example, if the response information includes a transaction code for the requester, the shopping start notification unit 155 stores the transaction code in association with the user ID of the requester.

[0090] The shopping support unit 156 of the mobile terminal 12 is an example of a first acquisition means, a second acquisition means, a registration means, and an execution means. The shopping support unit 156 executes various processes to support shopping at a store.

[0091] When the shopping support unit 156 receives a response to the shopping start notification from the server device 30, it displays an operation screen (hereinafter also referred to as a product registration screen) for supporting shopping at the store on the display unit 108. For example, if a shopping list is stored in RAM or the like, the shopping support unit 156 displays the shopping list on the product registration screen. The product registration screen will be described later.

[0092] Furthermore, the shopping support unit 156 cooperates with the imaging unit 110 to read information from a code symbol captured by the imaging unit 110 and executes various processes related to the purchase of a product based on the read information. For example, when the shopping support unit 156 reads a product code from a code symbol attached to the product, it transmits a product registration request to the server device 30, the product code including a specified transaction code for the registration destination.

[0093] When the transaction management unit 354 of the server device 30 receives a product registration request from the mobile terminal 12, it obtains product information related to the product code included in the product registration request from the product master 3052, and registers the information in the transaction information management table 3057 in association with the transaction code specified in the product registration request. Furthermore, if multiple product registration requests specifying the same product code and registration destination are received, the transaction management unit 354 increments the number of products corresponding to the product code by one each time a request is received. Note that the transaction management unit 354 registers the quantity "1" at the time of initial registration.

[0094] When the shopping support unit 156 of the mobile terminal 12 registers a product by sending a product registration request, the shopping support unit 156 displays the registered product on the product registration screen. For example, the shopping support unit 156 cooperates with the transaction management unit 354 of the server device 30 to display on the product registration screen products included in the transaction information associated with the user ID of the operator operating the mobile terminal 12, among the transaction information registered in the transaction information management table 3057.

[0095] Fig. 12 is a diagram showing an example of a product registration screen displayed on the mobile terminal 12. As shown in Fig. 12, the product registration screen A has a shopping list display field Aa, a first shopping cart display field Ab, and a second shopping cart display field Ac.

[0096] The shopping list display field Aa is an area for displaying the shopping list. When the client's shopping list is stored in RAM 103 or the like, the product names, quantities, etc. of the products included in the shopping list are displayed in the shopping list display field Aa. The shopping list display field Aa also has a check box Aaa for checking whether or not each product included in the shopping list has been purchased.

[0097] The first shopping cart display field Ab is an area for displaying the products registered in association with the transaction code for the client. The first shopping cart display field Ab displays a list of the product name, number of items, price (e.g., number of items x price) for each registered product.

[0098] The second shopping cart display field Ac is an area for displaying products registered in association with a contractor's transaction code. Similar to the first shopping cart display field Ab, the second shopping cart display field Ac lists the product name, number of items, and price (e.g., number of items x price) for each registered product. Note that in FIG. 12, in order to make it possible to identify which user the first shopping cart display field Ab and the second shopping cart display field Ac are shopping cart display fields for (hereinafter also referred to as "shopping carts"), the corresponding user's name (AAAA, EEEE) is displayed at the top of each field, but personal pronouns such as "client," "contractor," "other party," and "I" may also be used to make the names identifiable.

[0099] As described above, the shopping support unit 156 of the mobile terminal 12 transmits a product registration request specifying the transaction code to which the product is to be registered to the server device 30. Here, the transaction code to which the product is to be registered may be determined automatically by the shopping support unit 156 or may be determined in response to an operation by the operator.

[0100] When determining automatically, for example, the shopping support unit 156 compares the product code read from the product with the product codes of each product included in the shopping list to determine whether a matching product exists. If a matching product exists in the shopping list, the shopping support unit 156 may determine the client's transaction code as the registration destination, and if a matching product does not exist in the shopping list, the shopping support unit 156 may determine the contractor's transaction code as the registration destination. Note that even if a matching product exists in the shopping list, the shopping support unit 156 preferably determines the contractor's transaction code as the registration destination if the specified number of products is exceeded.

[0101] When the decision is made based on the operation of the operator, for example, the shopping support unit 156 may display a screen (hereinafter also referred to as a registration destination selection screen) on the display unit 108 to confirm the registration destination of the product, as shown in FIG. 13, to prompt the operator to make a selection.

[0102] Fig. 13 is a diagram showing an example of a registration destination selection screen displayed on the mobile terminal 12. As shown in Fig. 13, the registration destination selection screen B has a product name display field Ba, a first registration destination display field Bb, and a second registration destination display field Bc.

[0103] The product name of the product code to be registered that was read from the code symbol is displayed in the product name display field Ba. For example, the shopping support unit 156 queries the server device 30 about the product code read from the code symbol, acquires the product name of the corresponding product, and displays it in the product name display field Ba.

[0104] The first registration destination display field Bb is associated with the transaction code for the client, and displays the name of the user corresponding to the client's user ID. The second registration destination display field Bc is associated with the transaction code for the contractor, and displays the name of the user corresponding to the contractor's (operator's) user ID. For example, the shopping support unit 156 queries the server device 30 for the user ID, obtains the name of the corresponding user, and displays it in each registration destination display field. Note that instead of displaying the name of each user, personal pronouns may be displayed.

[0105] On the registration destination selection screen B, when the request receiving unit 154 receives an operation to select a registration destination, it determines the transaction code of the selected registration destination. For example, if the first registration destination display field Bb and the second registration destination display field Bc are operators such as buttons, the transaction code associated with the selected operator is determined as the registration destination. Also, for example, if the product name display field Ba is an operator that can be flicked, the transaction code of the registration destination may be determined according to the registration destination display field to which the product name display field Ba is moved.

[0106] It is preferable that the registration destination selection screen B is displayed when the products included in the shopping list are read and when the specified number of products has not been exceeded. The registration destination selection screen B may also be displayed superimposed on the product registration screen A. In this case, it is preferable that the registration destination selection screen B be displayed superimposed on the first shopping cart display field Ab and the second shopping cart display field Ac so as not to superimpose on the shopping list display field Aa of the product registration screen A. This allows the operator to select a registration destination while viewing the shopping list, thereby improving convenience.

[0107] Furthermore, the method of selecting the registration destination is not limited to the above example. It is also possible to accept the selection operation of the registration destination while the product registration screen A is displayed, without displaying the registration destination selection screen B. For example, the request receiving unit 154 may determine the transaction code for the requester as the registration destination when the shopping list display field Aa or the first shopping cart display field Ab is selected after the product is read, and may determine the transaction code for the contractor as the registration destination when the second shopping cart display field Ac is selected. As with the above, it is preferable that the selection operation is accepted when the products included in the shopping list are read and when the specified number of products has not been exceeded. Furthermore, when this selection method is adopted, it is preferable that a message guiding the selection method (operation method) is also displayed.

[0108] Returning to Fig. 12, the description of the product registration screen A will continue. When the request receiving unit 154 specifies the client's transaction code as the registration destination, the request receiving unit 154 displays the product name, number of items, and price of the registered product in the client's shopping cart (first shopping cart display field Ab). Furthermore, when the request receiving unit 154 specifies the contractor's transaction code as the registration destination, the request receiving unit 154 displays the product name, number of items, and price of the registered product in the client's shopping cart (second shopping cart display field Ac).

[0109] Furthermore, when a product is added to the requester's shopping cart, the request receiving unit 154 checks the check box Aaa in the shopping list corresponding to that product. Specifically, when a specified number of products from the shopping list are added to the requester's shopping cart, the request receiving unit 154 adds a check mark to the check box Aaa for the corresponding product. For example, FIG. 12 shows an example in which a check mark is added to the check box Aaa for a product with the product name "Product E."

[0110] This allows the operator of the mobile terminal 12 to easily check the items for which shopping has been completed and the items for which shopping has not yet been completed by looking at the shopping list display field Aa, thereby improving convenience regarding shopping.

[0111] In this embodiment, the check box Aaa is automatically checked by the request receiving unit 154, but the present invention is not limited to this and the check box Aaa may be manually checked by an operator. In this case, for example, the check box Aaa may be an operator that can switch between a checked state and an unchecked state in response to an operator's operation. This allows the operator of the mobile terminal 12 to easily check the items that have been purchased and the items that have not yet been purchased by checking the check box Aaa while viewing the items registered in the requester's shopping cart.

[0112] In addition, in the shopping list display field Aa, it is possible to perform an operation to remove from the shopping list any product that cannot be purchased at the store due to reasons such as being out of stock (hereinafter also referred to as out-of-stock product). For example, if any product displayed in the shopping list display field Aa is out of stock, the operator can remove that product from the shopping list by performing a predetermined operation (such as a long press) on the out-of-stock product.

[0113] 14 is a diagram showing an example of a shopping list display field displayed on the mobile terminal 12. As shown in FIG. 14, when an out-of-stock item is set in the shopping list, the shopping support unit 156 displays "Not listed" in the check box Aaa for the out-of-stock item "Item A" that was the target of the operation, and grays out the data entry for that out-of-stock item. This allows the operator to easily check the out-of-stock items that have been excluded from shopping.

[0114] When the shopping support unit 156 receives an operation to set an out-of-stock item, it may notify the requester of the existence of the out-of-stock item via the server device 30. In this case, the shopping support unit 156 transmits an out-of-stock notification to the server device 30, which includes, for example, the product code, product name, and quantity of the out-of-stock item, the user code of the requester, etc. The out-of-stock notification may also include a message entered by the operator of the mobile terminal 12.

[0115] When a stock-out-of-stock notification is sent from the mobile terminal 12, the transaction management unit 354 of the server device 30 forwards the stock-out-of-stock notification to the mobile terminal 11 corresponding to the client's user ID included in the stock-out-of-stock notification. Furthermore, when the stock-out-of-stock notification receiving unit 157 of the mobile terminal 11 receives the stock-out-of-stock notification from the server device 30, it notifies the client of the existence of the out-of-stock item by displaying the product name, etc. of the out-of-stock item included in the stock-out-of-stock notification on the display unit 108. This allows the client who requested shopping proxy service to confirm that there is a out-of-stock item on their shopping list.

[0116] The client who receives the notice of out-of-stock may inform the contractor of the substitute product by contacting the contractor separately. Also, the client who receives the notice of out-of-stock may register a substitute product for the out-of-stock product in the shopping list by editing the shopping list.

[0117] In this case, the shopping list creation support unit 152, in cooperation with the shopping list management unit 352 of the server device 30, reads the shopping list associated with the requester's user ID from the shopping list management table 3055 and displays it on the display unit 108 in an editable state. When an editing operation is performed, such as deleting an out-of-stock item or adding a substitute item, the shopping list management unit 352 of the server device 30 updates the shopping list with the edited content and stores it in the shopping list management table 3055. Furthermore, the shopping request management unit 353 (or transaction management unit 354) of the server device 30 identifies a data record in which the user ID is registered in the requester information field based on the user ID of the updated shopping list from the shopping request management table, and transmits the updated shopping list to the mobile device 12 corresponding to the user ID registered in the contractor information field of that data record. In this case, the shopping support unit 156 of the mobile terminal 12 obtains the shopping list created (edited) by the requester from the server device 30.

[0118] As a result, the edited shopping list with the added substitute product is provided in real time to the mobile terminal 12 operated by the contractor. For example, for the out-of-stock product "Product A" shown in Fig. 14, if "Product A" is deleted and an alternative product is added to replace "Product A," the contents of the shopping list after the edit are displayed in the shopping list display field Aa on the product registration screen A, as shown in Fig. 15.

[0119] FIG. 15 is a diagram showing another example of a shopping list display field displayed on the mobile terminal 12. In the shopping list display field Aa of FIG. 15, the out-of-stock item "Item A" that was displayed in the shopping list display field Aa of FIG. 14 has been deleted, and a substitute item "Item F" has been added and registered. This allows the operator to easily check the substitute item designated by the requester. Furthermore, because the updated shopping list is displayed in real time, shopping based on the shopping list can be carried out efficiently.

[0120] Returning to Fig. 12, the product registration screen A has a payment button Ad. The payment button Ad is an operator for instructing completion of product registration (or start of payment). When the shopping support unit 156 of the mobile terminal 12 accepts operation of the payment button Ad, it completes product registration.

[0121] Here, when the payment button Ad is operated, the shopping support unit 156 compares the products registered in the client's shopping cart with the products registered in the shopping list, and determines whether there are any unregistered (unpurchased) products.

[0122] Specifically, the shopping support unit 156 determines whether the product code and the specified quantity of each product registered on the shopping list, other than the out-of-stock product, are registered in the requester's shopping cart. If it is determined that each product, other than the out-of-stock product, is registered in the requester's shopping cart, the shopping support unit 156 determines that all products on the shopping list have been purchased, and executes processing to settle the registered products.

[0123] On the other hand, if it is determined that some or all of the products other than the out-of-stock products are not registered in the client's shopping cart, the shopping support unit 156 determines that there are unpurchased products and causes the display unit 108 to display a notification screen informing the client that there are unpurchased products.

[0124] Fig. 16 is a diagram showing an example of a notification screen displayed on the mobile terminal 12. As shown in Fig. 16, the notification screen C displays a message notifying the user that an item on the shopping list has not yet been purchased, as well as a hold button Ca and a continue shopping button Cb.

[0125] The hold button Ca is an operator for instructing to end product registration while leaving unpurchased products on hold. When the shopping support unit 156 of the mobile terminal 12 receives an operation of the hold button Ca, it places on hold the product codes and quantities of products registered on the shopping list that are not registered in the client's shopping cart, and executes processing to settle the registered products. Note that "on hold" means that the products remain on the shopping list as unpurchased products.

[0126] The Continue Shopping button Cb is an operator for canceling the operation of the Settlement button Ad and instructing to continue registering the product. When the shopping support unit 156 of the mobile terminal 12 accepts the operation of the Continue Shopping button Cb, it displays the product registration screen A and continues the product registration process.

[0127] Furthermore, the shopping support unit 156 of the mobile terminal 12 executes, for example, the following process as a process for making payment for registered products. The shopping support unit 156 sends a registration completion notice to the server device 30, notifying that product registration has been completed. The registration completion notice may include, for example, the user ID of the operator operating the mobile terminal 12. Furthermore, in order to make payment for the registered products at the payment terminal 20, the shopping support unit 156 encodes information capable of identifying the corresponding transaction (hereinafter also referred to as transaction identification information) into a code symbol such as a two-dimensional code, and displays a screen (not shown) representing the encoded code symbol (hereinafter referred to as a transaction notification screen) on the display unit 108.

[0128] Here, the transaction identification information is, for example, a transaction code for the client and a transaction code for the contractor. The transaction identification information may also be, for example, the user ID of the operator who operates the mobile terminal 12. For example, if a request number is notified from the server device 30, the transaction identification information may also be the request number. The operator's user ID and request number can be used to identify the transaction related to the registration of the product made on the mobile terminal 12 by referring to the shopping request management table 3056 and the transaction information management table 3057 in the server device 30.

[0129] The operator of the mobile terminal 12, i.e., the user purchasing the product, inputs transaction specific information into the payment terminal 20 by having the scanner unit 210 of the payment terminal 20 read the transaction notification screen displayed on the display unit 108.

[0130] The payment processing unit 251 of the payment terminal 20 executes payment processing for the products registered on the mobile terminal 12. The payment processing unit 251 controls the scanner unit 210 to acquire various information read by the scanner unit 210. Specifically, the payment processing unit 251 acquires transaction identification information from a code symbol displayed on the transaction notification screen of the mobile terminal 12. Upon acquiring the transaction identification information, the payment processing unit 251 transmits a transaction information acquisition request including the transaction identification information to the server device 30.

[0131] When the transaction management unit 354 of the server device 30 receives a transaction information acquisition request from the payment terminal 20, it acquires the transaction information of the transaction identified by the transaction identification information included in the transaction information acquisition request from the transaction information management table 3057. For example, if the transaction identification information includes the client's transaction code and the contractor's transaction code, it acquires the transaction information corresponding to each of these transaction codes from the transaction information management table 3057. Furthermore, for example, if the transaction identification information includes a user ID, it acquires the transaction information associated with that user ID from the transaction information management table 3057.

[0132] When transaction management unit 354 of server device 30 acquires transaction information from transaction information management table 3057, it transmits the acquired transaction information to payment terminal 20 that sent the transaction information acquisition request.

[0133] When the payment processing unit 251 of the payment terminal 20 receives transaction information from the server device 30, it calculates the total amount of the products included in the transaction information for each transaction (transaction code). The payment processing unit 251 also calculates a detailed total amount by adding up the total amounts for each transaction code. The payment processing unit 251 then displays a detailed screen on the display unit 208 showing the breakdown of the products included in the transaction information, the calculated total amount, and the detailed total amount.

[0134] Fig. 17 is a diagram showing an example of a statement screen displayed on the payment terminal 20. As shown in Fig. 17, the statement screen D has a first statement display field Da, a second statement display field Db, and a statement total amount display field Dc.

[0135] The first detail display field Da is an area for displaying the details of the products registered in association with the client's transaction code and the total price. The first detail display field Da displays the product name, number of items, price (e.g., number of items x price) for each registered product.

[0136] The second detail display field Db is an area for displaying details of products registered in association with the contractor's transaction code and their total price. Similar to the first detail display field Da, the second detail display field Db displays a list of the product name, number of items, price (e.g., number of items x price) for each registered product. In FIG. 17, the first detail display field Da and the second detail display field Db display the corresponding user's name (AAAA, EEEE) at the top of each field to make it possible to identify which user the details relate to. However, personal pronouns such as "client," "contractor," "other party," and "I" may also be used to make the details identifiable.

[0137] The total detailed amount display field Dc displays the total amount of the amounts displayed in the first detailed display field Da and the second detailed display field Db.

[0138] When a user who purchases a product pays the total detailed amount displayed on the display unit 208, the payment processing unit 251 of the payment terminal 20 executes the payment process. The payment method for the total detailed amount may be cash, electronic payment, or any other method.

[0139] When the payment processing unit 251 of the payment terminal 20 executes the payment processing, it issues a receipt showing transaction details from the printer 211. Here, the payment processing unit 251 issues a receipt for each transaction (transaction code) that is the subject of the payment processing from the printer 211. For example, in the case of a transaction related to the details screen shown in FIG. 17, a receipt related to the client's transaction code and a receipt related to the contractor's transaction code are issued. The payment processing unit 251 may also issue receipts that include the names and personal pronouns of the client and contractor.

[0140] In this way, the shopping support system 1 outputs separate receipts for the client and the contractor, allowing the contractor to, for example, hand over to the client a receipt for the items related to the shopping carried out on behalf of the client. This also improves convenience when the contractor collects fees related to the shopping carried out on behalf of the client.

[0141] Furthermore, when the payment process is completed, the payment processing unit 251 of the payment terminal 20 transmits a payment completion notice including the transaction identification information to the server device 30.

[0142] When the transaction management unit 354 of the server device 30 receives a payment completion notification from the payment terminal 20, it deletes, for example, the data record related to the relevant transaction from the shopping request management table 3056 or the transaction information management table 3057. The transaction management unit 354 may also notify the mobile terminal 12 of the requester related to the transaction for which payment has been completed that the purchases on the shopping list have been completed.

[0143] In addition, the transaction management unit 354 of the server device 30 may, on the condition that it receives a payment completion notification, perform processing such as removing purchased items from the shopping list stored in association with the requester's user ID or adding a check mark to the purchased items.

[0144] For example, the transaction management unit 354 may compare the product codes included in the shopping list with the product codes registered in the client's shopping cart, subtract the number of items in the shopping cart from the number of items in the shopping list for each matching product code, and remove from the shopping list any data entries for items whose number is reduced to "zero." The transaction management unit 354 may also compare the product codes included in the shopping list with the product codes registered in the client's shopping cart, and add a check mark or other mark indicating that the item has been purchased to the data entry for any matching item in the shopping list. This allows the client who requested shopping proxy service to easily check the purchased and pending items by viewing the shopping list.

[0145] An example of the operation of the mobile terminal 10, the payment terminal 20, and the server device 30 will be described below.

[0146] First, an example of the operation related to a shopping proxy request will be described with reference to Fig. 18. Fig. 18 is a sequence diagram showing an example of the processing related to a shopping proxy request executed by the mobile terminal 10 (11, 12) and the server device 30. Note that this processing is premised on the assumption that grouping of users has been completed. Also, it is premised on the assumption that the requester has completed creating a shopping list.

[0147] First, when the shopping request unit 153 of the mobile terminal 11 receives an operation to request a proxy via the operation unit 109 (step S11), it transmits client information including the user ID of the operator operating the mobile terminal 11 to the server device 30 (step S12).

[0148] When the shopping request management unit 353 of the server device 30 receives the requester information from the mobile terminal 11, it acquires the user IDs of other members of the group to which the user ID belongs from the group management table 3054 based on the user ID included in the requester information (step S13). Next, the shopping request management unit 353 transmits a member list including the acquired user IDs to the mobile terminal 11 (step S14).

[0149] When the shopping request unit 153 of the mobile terminal 11 receives the member list from the server device 30, it causes the display unit 108 to display a member selection screen on which the user can select a user to request shopping based on the member list (step S15). Next, when the shopping request unit 153 receives the user's selection (step S16), it sends a shopping proxy request to the server device 30, which includes the user ID of the requester operating the mobile terminal 11 and the user ID of the selected user (step S17).

[0150] When the shopping request management unit 353 of the server device 30 receives the shopping agent request from the mobile terminal 11, it sends a request notification to the mobile terminal 12 corresponding to the user ID of the contractor candidate included in the shopping agent request (step S18).

[0151] When the request receiving unit 154 of the mobile terminal 12 receives the request notification from the server device 30, it displays the content included in the request notification on the display unit 108 (step S19). Next, when the request receiving unit 154 receives a response via the operation unit 109 as to whether or not to accept the shopping proxy request (step S20), it transmits response information indicating the content of the response to the server device 30 (step S21).

[0152] When the shopping request management unit 353 of the server device 30 receives the response information from the mobile terminal 12, it determines whether the response information indicates that the request is accepted (step S22). If the response information indicates that the request is accepted, the shopping request management unit 353 sets the user ID of the mobile terminal 12 from which the response of agreement was obtained as the user ID of the contractor, associates it with the user ID of the client specified in the corresponding shopping agent request, and registers it in the shopping request management table 3056 (step S23). Next, the shopping request management unit 353 transmits response information (agreement) to the mobile terminal 11 notifying that agreement to the request has been obtained (step S24).

[0153] Then, the shopping request unit 153 of the mobile terminal 11 displays the content of the received response information on the display unit 108 (step S25), thereby notifying the user that the shopping proxy request has been accepted.

[0154] On the other hand, if the response information indicates that the request will not be accepted, the shopping request management unit 353 sends response information (non-consent) to the mobile terminal 11 corresponding to the requester's user ID, notifying that consent to the request has not been obtained (step S26).

[0155] Then, the shopping request unit 153 of the mobile terminal 11 displays the content of the received response information on the display unit 108 (step S27), thereby notifying the user that the shopping proxy request has been unsuccessful.

[0156] If the request for shopping on behalf of the customer is not successful, the operator of the mobile terminal 11 can display the member selection screen and select another member, thereby executing the processing from step S17 onwards again.

[0157] Next, an example of the operation for supporting shopping by a contractor who has accepted a shopping proxy request will be described with reference to Fig. 19. Fig. 19 is a sequence diagram showing an example of the process related to shopping support executed by the mobile terminal 10 (12) and the server device 30. Note that this process is premised on the premise that matching between the client and the contractor has been completed.

[0158] First, the shopping start notification unit 155 of the mobile terminal 12 transmits a shopping start notification including the user ID of the operator who operates the mobile terminal 12 to the server device 30 (step S31).

[0159] When the transaction management unit 354 of the server device 30 receives a shopping start notification from the mobile terminal 12, it identifies a data entry in which the user ID included in the shopping start notification is registered in the contractor information field from the shopping request management table 3056, based on the user ID included in the shopping start notification. Next, the transaction management unit 354 issues a transaction code for the requester and a transaction code for the contractor based on the request number field and the requester information field of the identified data entry (step S32). The transaction management unit 354 also obtains a shopping list associated with the requester's user ID from the shopping list management table 3055 (step S33). Next, the transaction management unit 354 transmits response information including the issued transaction code and the requester's shopping list to the mobile terminal 12 (step S34).

[0160] When the shopping support unit 156 of the mobile terminal 12 receives the response information from the server device 30, it causes the display unit 108 to display a product registration screen (see FIG. 12) based on the response information (step S35). Next, when the shopping support unit 156 acquires a product code via the imaging unit 110 (step S36), it transmits a product registration request including the product code and the transaction code of the registration destination to the server device 30 (step S37).

[0161] When the transaction management unit 354 of the server device 30 receives a product registration request from the mobile terminal 12, it obtains product information related to the product code included in the product registration request from the product master 3052 and registers it in the transaction information management table 3057 in association with the transaction code indicated in the product registration request (step S38).

[0162] Furthermore, the shopping support unit 156 of the mobile terminal 12 displays the product whose registration has been completed on the server device 30 in the shopping cart corresponding to the transaction code of the registration destination (step S39). Furthermore, every time the shopping support unit 156 of the mobile terminal 12 acquires a product code via the imaging unit 110, it executes the processes from step S36 onward and displays the product whose registration has been completed in the shopping cart of the registration destination.

[0163] When the shopping support unit 156 of the mobile terminal 12 registers a product code in association with the client's transaction code, the shopping support unit 156 adds additional information (for example, a check mark) to indicate that the product on the shopping list corresponding to the product code has been purchased.

[0164] Next, when the shopping support unit 156 of the mobile terminal 12 receives an operation to end product registration (or start payment) (step S40), it compares the product codes registered in the shopping list with the product codes registered in association with the requester's transaction code, and determines whether all products registered in the shopping list have been purchased (step S41).

[0165] If it is determined that all products registered in the shopping list have been purchased, the shopping support unit 156 of the mobile terminal 12 notifies the server device 30 of the completion of registration (step S42).Then, the shopping support unit 156 of the mobile terminal 12 causes the display unit 108 to display a transaction notification screen showing a code symbol that encodes the transaction identification information (step S43).

[0166] On the other hand, if it is determined that there are unpurchased products, the shopping support unit 156 of the mobile terminal 12 causes the display unit 108 to display a notification screen (see FIG. 16) informing the user that there are unpurchased products (step S44). Here, if an instruction is given to continue registering the products by operating the "Continue Shopping button Cb," for example, the shopping support unit 156 of the mobile terminal 12 continues the product registration process by returning the process to step S36.

[0167] Furthermore, when an instruction is given to end product registration while keeping unpurchased products on hold, for example by operating the "hold button Ca," the shopping support unit 156 of the mobile terminal 12 notifies the server device 30 of registration completion (step S45).Then, the shopping support unit 156 of the mobile terminal 12 causes the display unit 108 to display a transaction notification screen showing a code symbol that encodes the transaction identification information (step S46).

[0168] Next, an example of an operation for supporting shopping by a contractor who has accepted a shopping proxy request will be described with reference to Fig. 20. Fig. 20 is a sequence diagram showing an example of a process related to payment executed by payment terminal 20 and server device 30.

[0169] When the payment processing unit 251 of the payment terminal 20 acquires transaction identification information from the code symbol displayed on the display unit 108 of the mobile terminal 12 (step S51), it sends a transaction information acquisition request including the transaction identification information to the server device 30 (step S52).

[0170] When the transaction management unit 354 of the server device 30 receives the transaction information acquisition request from the payment terminal 20, it acquires the transaction information of each transaction identified by the transaction identification information included in the transaction information acquisition request from the transaction information management table 3057 (step S53). Next, the transaction management unit 354 transmits the acquired transaction information to the payment terminal 20 (step S54).

[0171] When the payment processing unit 251 of the payment terminal 20 receives the transaction information from the server device 30, it calculates the total price of the products included in the transaction information for each transaction (step S55), and also calculates a detailed total amount by adding up the total prices of each transaction (step S56). Next, the payment processing unit 251 displays a detailed screen (see FIG. 17) on the display unit 208 showing the breakdown of the products included in the transaction information, the calculated total price, and the detailed total amount (step S57).

[0172] Next, the payment processing unit 251 of the payment terminal 20 executes the payment processing of the total detailed amount (step S58), and issues a receipt for each transaction that was the subject of the payment processing (step S59). Then, when the payment processing is completed, the payment processing unit 251 transmits a payment completion notice including transaction identification information to the server device 30 (step S60).

[0173] When the transaction management unit 354 of the server device 30 receives a payment completion notification from the payment terminal 20, it deletes the data record of the transaction identified by the transaction identification information included in the payment completion notification from the shopping request management table 3056 and the transaction information management table 3057 (step S61).

[0174] Next, an example of the operation performed by the shopping support unit 156 of the mobile terminal 12 will be described with reference to Fig. 21. Fig. 21 is a flowchart showing an example of shopping support processing performed by the mobile terminal 12. Note that this processing shows an example of the operation of the shopping support unit 156 performed in steps S36 to S46 in Fig. 19 described above.

[0175] First, the shopping support unit 156 determines whether or not a product code has been acquired (Step S71). If it is determined that a product code has not been acquired (Step S71; No), the shopping support unit 156 proceeds to Step S76.

[0176] When the product code is acquired in step S71 (step S71; Yes), the shopping support unit 156 compares the product code with that of each product registered in the shopping list other than out-of-stock products, and determines whether the product is registered in the shopping list (step S72).

[0177] If the product is not registered in the shopping list (step S72; No), the shopping support unit 156 registers the product in the contractor's shopping cart by sending a product registration request to the server device 30 with the contractor's transaction code set as the registration destination for the acquired product code (step S73), and then proceeds to step S76.

[0178] If the item is registered in the shopping list (step S72; Yes), the shopping support unit 156 determines whether the number of corresponding items registered in the client's shopping cart is the same as the number specified in the shopping list (step S74). If the number is the same as the number specified in the shopping list (step S74; Yes), the shopping support unit 156 determines that the item code acquired in step S71 is an excess item, and proceeds to step S73.

[0179] Furthermore, if it is determined in step S74 that the number of corresponding items registered in the requester's shopping cart is less than the number specified in the shopping list (step S74; No), the shopping support unit 156 registers the items in the requester's shopping cart by sending a product registration request to the server device 30 with the registration destination of the acquired product code set to the requester's transaction code (step S75), and then proceeds to step S76.

[0180] In the next step S76, the shopping support unit 156 determines whether or not an operation to set an out-of-stock item has been accepted (step S76). If an operation to set an out-of-stock item has been accepted (step S76; Yes), the shopping support unit 156 sets the item in the shopping list that was the target of the operation as an out-of-stock item (step S77), and proceeds to step S78. On the other hand, if an operation to set an out-of-stock item has not been accepted (step S76; No), the shopping support unit 156 proceeds immediately to step S78.

[0181] In the next step S78, the shopping support unit 156 determines whether an operation to instruct the end of product registration has been accepted (step S78). If an instruction to end product registration has not been accepted (step S78; No), the shopping support unit 156 returns the process to step S71 to continue the product registration process.

[0182] If an instruction to end product registration is received (step S78; Yes), the shopping support unit 156 compares the product code and quantity of each product registered on the shopping list, excluding out-of-stock products, with the product code and quantity of each product registered in the client's shopping cart, and determines whether all products registered on the shopping list have been purchased (step S79).

[0183] If it is determined that all the products registered in the shopping list have been purchased (step S79; Yes), the shopping support unit 156 proceeds to step S82.

[0184] On the other hand, if it is determined that there are unpurchased products (step S79; No), the shopping support unit 156 causes the display unit 108 to display a notification screen (see FIG. 16) notifying the user that there are unpurchased products (step S80). Next, the shopping support unit 156 determines whether an instruction to end product registration has been issued (step S81).

[0185] If an instruction to continue product registration is given (step S81; No), the shopping support unit 156 continues the product registration process by returning the process to step S71. If an instruction to end product registration is given (step S81; Yes), the shopping support unit 156 proceeds to step S82.

[0186] In the next step S82, the shopping support unit 156 notifies the server device 30 of the completion of registration (step S82). Then, the shopping support unit 156 of the mobile terminal 12 causes the display unit 108 to display a transaction notification screen showing a code symbol that encodes the transaction identification information (step S83), and ends this process.

[0187] As described above, the mobile terminal 10 (12) obtains from the server device 30 a shopping list created by a client requesting shopping on their behalf. The mobile terminal 10 (12) also obtains product codes for products sold in the store that have been selected for purchase by the contractor who accepted the request, and registers the obtained product codes in association with the client's or contractor's transactions, i.e., registers them in the client's or contractor's shopping cart. Then, in response to an instruction to complete registration or start payment, the mobile terminal 10 (12) displays transaction identification information that can identify both the client's and contractor's transactions, thereby executing processing related to the payment of both transactions.

[0188] As a result, the mobile terminal 10 (12) operated by the contractor who accepted the request from the client can simultaneously register products based on the shopping list created by the client and the products to be purchased by the contractor, and these can be processed as independent transactions. Therefore, the mobile terminal 10 (12) can easily separate the client's and contractor's shares, improving shopping convenience. Therefore, the shopping support system 1 can efficiently provide support for purchasing products related to shopping proxy services.

[0189] In addition, the mobile terminal 10 (12) automatically determines the shopping cart to which the product to be purchased by the contractor is to be registered depending on whether the product is included in the shopping list or not, or whether the number of products specified in the shopping list has been registered.

[0190] This allows the contractor to register the product in either the client's or contractor's shopping cart without performing any special operations. Therefore, the mobile terminal 10 (12) can improve the convenience of selecting the registration destination.

[0191] Furthermore, the mobile terminal 10 (12) determines the shopping cart to which the product will be registered in response to instructions from the contractor. This allows the contractor to arbitrarily set the registration destination for the product, thereby improving convenience for shopping.

[0192] The above-described embodiment can be modified as needed by partially changing the configuration or functions of each of the above-described devices. Therefore, several modifications of the above-described embodiment will be described below as other embodiments. The following mainly focuses on differences from the above-described embodiment, and detailed descriptions of commonalities with the content already described will be omitted. The modifications described below may be implemented individually or in appropriate combination.

[0193] (Variation 1) In the above embodiment, the server device 30 is located outside the store, but the present invention is not limited to this, and the server device 30 may be a store server located inside the store.

[0194] Furthermore, in the above-described embodiment, the shopping support unit 156 of the mobile terminal 10 (12) is configured to perform shopping support processing such as matching with products registered in a shopping list and selecting a shopping cart to register in. However, the present invention is not limited to this, and the shopping support processing may be performed in the server device 30. In this case, the server device 30 may have, for example, some or all of the functions of the shopping support unit 156, and may output various operation screens and processing results of the shopping support processing via the mobile terminal 12. In other words, the mobile terminal 12 may be configured as an input / output device for the server device 30.

[0195] (Variation 2) In the above embodiment, a configuration has been described in which payment processing for products registered using mobile terminal 12 is performed using payment terminal 20, but this configuration is not limiting. For example, if mobile terminal 12 has an electronic payment function such as code payment or credit card payment, payment processing may be performed using mobile terminal 10.

[0196] In this case, the receipt may be issued using a printer device installed in the store, or may be issued in the form of an electronic receipt, which will be described later.

[0197] (Variation 3) In the above-described embodiment, the mobile terminal 12 is a terminal device carried by the user, but it is not limited to this and may be, for example, a portable terminal device rented out in a store or a terminal device attached to a shopping cart (hereinafter collectively referred to as a store terminal).

[0198] In this case, the user (contractor) operating the store terminal starts shopping at the store by entering his / her own user ID into the store terminal. Also, the shopping start notification unit 155 of the store terminal can perform the same processing as in the above-described embodiment by sending a shopping start notification to the server device 30 on the condition that the operator's user ID has been entered.

[0199] (Variation 4) In the above embodiment, the payment terminal 20 is configured to issue (output) a paper receipt, but this is not limiting and the receipt may be output in the form of an electronic receipt. In this case, the payment terminal 20 generates an electronic receipt for each transaction by digitizing the content that would be printed on the receipt, and provides it to the user.

[0200] For example, the payment terminal 20 may provide an electronic receipt to each user via the server device 30. As an example, when the transaction management unit 354 of the server device 30 acquires an electronic receipt for each transaction from the payment terminal 20, it may provide electronic receipts for the client and the contractor to the mobile terminal 10 corresponding to the user ID of the contractor involved in the transaction.

[0201] As another example, when the transaction management unit 354 of the server device 30 obtains an electronic receipt for each transaction from the payment terminal 20, it may identify the user IDs of the client and contractor involved in the transaction and provide electronic receipts for the corresponding transactions to the mobile terminals 10 of the client and contractor. This allows the client to check the details of the transactions based on the shopping list made at the store in real time, thereby improving convenience.

[0202] (Variation 5) In the above embodiment, a form has been described in which a shopping agent is requested without providing the address and the like of the client, but the present invention is not limited to this, and a configuration in which the address and the like of the client are provided may also be used.

[0203] In this case, the shopping request management unit 353 of the server device 30 may identify the user information of the user ID registered in the requester information from the user management table 3053, and include information such as the address contained in the user information in a request notification, etc., and send it to the mobile terminal 12.

[0204] This allows the contractor who has accepted the request to confirm the address of the client even if he has forgotten the client's address, thereby improving convenience.

[0205] The programs executed by each device in the above-described embodiments are provided in advance in a ROM, etc. The programs executed by each device in the above-described embodiments may be provided by being recorded in an installable or executable file format on a computer-readable recording medium such as a CD-ROM, a flexible disk (FD), a CD-R, or a digital versatile disk (DVD).

[0206] Furthermore, the programs executed by each device in the above-described embodiments may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network. Also, the programs executed by each device in the above-described embodiments may be provided or distributed via a network such as the Internet.

[0207] Although several embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be embodied in various other forms, and various omissions, substitutions, modifications, and combinations can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope and spirit of the invention, and are also included in the scope of the invention and its equivalents as defined in the claims. [Explanation of symbols]

[0208] 1. Shopping support system 10 Mobile devices 20 Payment terminals 30 Server device 151 Group Registration Department 152 Shopping List Creation Support Department 153 Shopping Request Department 154 Request Reception Department 155 Shopping Start Notification Section 156 Shopping Support Department 251 Payment Processing Unit 351 Group Management Department 352 Shopping List Management Department 353 Shopping Request Management Department 354 Transaction Management Department [Prior art documents] [Patent documents]

[0209] [Patent Document 1] Japanese Patent Application Laid-Open No. 2015-082257

Claims

1. a first acquiring means for acquiring a shopping list created by a client requesting a shopping service; a second acquiring means for acquiring identification information capable of identifying the type of product selected as a purchase target by the contractor who accepted the request from among the products sold in the store; a registration means for registering the identification information acquired by the second acquisition means in association with a transaction between the client or the contractor; an execution means for executing a process related to the settlement of both the transactions of the client and the contractor in response to an instruction to end registration or start settlement; An information processing device comprising:

2. the registration means, when the type of product corresponding to the identification information acquired by the second acquisition means is included in the shopping list, registers the identification information in association with the transaction of the client; The information processing device according to claim 1 .

3. The registration means registers the identification information in association with the contractor's transaction even if the type of product corresponding to the identification information acquired by the second acquisition means is included in the shopping list, if the number of products corresponding to the identification information registered in association with the client's transaction reaches the number specified in the shopping list. The information processing device according to claim 2 .

4. the registration means, when the type of product corresponding to the identification information acquired by the second acquisition means is not included in the shopping list, registers the identification information in association with the contractor's transaction; 4. The information processing device according to claim 1.

5. The registration means, in response to an instruction from the contractor, registers the identification information acquired by the second acquisition means in association with a transaction between the client or the contractor. The information processing device according to claim 1 .

6. The computer of the information processing device, a first acquiring means for acquiring a shopping list created by a client requesting a shopping service; a second acquiring means for acquiring identification information capable of identifying the type of product selected as a purchase target by the contractor who accepted the request from among the products sold in the store; a registration means for registering the identification information acquired by the second acquisition means in association with a transaction between the client or the contractor; an execution means for executing a process related to the settlement of both the transactions of the client and the contractor in response to an instruction to end registration or start settlement; A program to make it function as such.

Images