Information Processing Systems

Abstract

To provide an information processing system, an information processing method, and a program that facilitate a procedure for product delivery.SOLUTION: An information processing system 1 includes an identification information acquisition unit 111 that acquires product identification information for identifying a product by an operation of a customer to a terminal apparatus in a store, a delivery reception unit 112 that receives whether to deliver each product indicated by the acquired product identification information, and a delivery destination reception unit 113 that receives delivery destination information related to a destination of the product regarding the product to be delivered.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present disclosure relates to an information processing system and the like. [Background technology]

[0002] When customers want to have items they have purchased at a store delivered, they go to a special counter and complete procedures such as writing down the delivery address on a piece of paper.

[0003] In addition, there are cases where the delivery address and the like can be input into each device. For example, Patent Document 1 describes that when a product code is read at a POS (Point of Sales) terminal, two types of keys, a payment key and a payment / delivery key, are displayed, and when the payment / delivery key is pressed, a process for inputting the address is performed, followed by a payment process. For example, Patent Document 2 describes that a screen for inputting delivery destination information such as the recipient's name, address, and telephone number is displayed on a mobile terminal.

[0004] Furthermore, there is scan shopping, in which customers shop at stores while registering products on a terminal device. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Laid-Open No. 2014-170466 [Patent Document 2] Japanese Patent Application Laid-Open No. 2014-002453 Summary of the Invention [Problem to be solved by the invention]

[0006] Even when customers use scan shopping at a store, they may want to have some products delivered.

[0007] An example of a purpose of the present disclosure is to provide an information processing system that facilitates procedures related to product delivery. [Means for solving the problem]

[0008] An information processing system in one aspect of the present disclosure includes, in a store, an identification information acquisition means for acquiring product identification information that identifies a product through a customer's operation on a terminal device, a delivery acceptance means for accepting whether to have each product represented by the acquired product identification information delivered, and a delivery destination acceptance means for accepting delivery destination information regarding the delivery destination of the product to be delivered.

[0009] An information processing method in one aspect of the present disclosure includes, at a store, acquiring product identification information that identifies a product through a customer's operation on a terminal device, accepting whether or not to have each product represented by the acquired product identification information delivered, and, if the product is to be delivered, accepting delivery destination information regarding the delivery destination of the product.

[0010] A program in one aspect of the present disclosure causes a computer to execute a process of acquiring product identification information that identifies products through customer operation on a terminal device at a store, accepting whether to have each product represented by the acquired product identification information delivered, and, if the product is to be delivered, accepting delivery destination information regarding the delivery destination of the product.

[0011] The program may be stored in a non-transitory computer-readable recording medium. [Effects of the Invention]

[0012] According to the present disclosure, it is possible to simplify the procedures for delivering products. [Brief explanation of the drawings]

[0013] [Figure 1] 1 is a block diagram illustrating a configuration example of an information processing system according to a first embodiment. [Figure 2]4 is a flowchart illustrating an example of an operation of the information processing system according to the first embodiment. [Figure 3] FIG. 10 is an explanatory diagram illustrating an example of an information processing system according to a second embodiment. [Figure 4] FIG. 10 is a block diagram showing a configuration example of a terminal device according to a second embodiment. [Figure 5] FIG. 10 is a block diagram illustrating a configuration example of a server according to a second embodiment. [Figure 6] FIG. 10 is an explanatory diagram showing an example of reading a product code. [Figure 7] FIG. 10 is an explanatory diagram showing a display example of a purchased product list according to reception example 1. [Figure 8] FIG. 10 is an explanatory diagram showing an example before accepting whether to have each product delivered according to acceptance example 1. [Figure 9] FIG. 10 is an explanatory diagram showing an example (part 2) after accepting whether to have each product delivered according to acceptance example 1. [Figure 10] FIG. 10 is an explanatory diagram showing an example of an input screen for delivery destination information. [Figure 11] FIG. 10 is an explanatory diagram showing a payment example. [Figure 12] 10 is a flowchart showing an example of the operation of the information processing system according to Reception Example 1. [Figure 13] FIG. 10 is an explanatory diagram showing an example of accepting whether to have each product delivered according to Acceptance Example 2. [Figure 14] FIG. 10 is an explanatory diagram showing a display example of a purchased product list according to a second reception example. [Figure 15] 10 is a flowchart showing an example of the operation of the information processing system according to a second reception example. [Figure 16] FIG. 10 is an explanatory diagram showing a display example before accepting a purchased product list and whether to have each product delivered, according to a third reception example. [Figure 17] FIG. 10 is an explanatory diagram showing an example of accepting whether to have each product delivered according to Acceptance Example 3. [Figure 18] FIG. 10 is an explanatory diagram showing an example of a display after accepting a list of purchased products and whether or not to have each product delivered, according to Reception Example 3. [Figure 19] FIG. 10 is an explanatory diagram showing a display example of a purchased product list according to a fourth reception example. [Figure 20] FIG. 10 is a block diagram showing an example of the configuration of a server according to Modification 2. [Figure 21] FIG. 2 is an explanatory diagram illustrating an example of a hardware configuration of a computer device. DETAILED DESCRIPTION OF THE INVENTION

[0014] Hereinafter, with reference to the drawings, embodiments of an information processing system, an information processing method, a program, and a non-transitory recording medium for recording a program according to the present disclosure will be described in detail. The present embodiments do not limit the disclosed technology.

[0015] (Embodiment 1) First, basic functions of an information processing system will be described in the first embodiment. Fig. 1 is a block diagram showing an example of the configuration of an information processing system 1 according to the first embodiment. The information processing system 1 includes an identification information acquisition unit 111, a delivery reception unit 112, and a delivery destination reception unit 113.

[0016] The identification information acquisition unit 111 acquires product identification information for identifying a product in a store through a customer's operation on a terminal device.

[0017] The store is not particularly limited. For example, the store may be a supermarket, a supercenter, a convenience store, a mass retailer, a home improvement store, a drugstore, a store selling apparel products, or a privately owned store such as a bakery or a prepared food store. The terminal device will be described in detail in the second embodiment, but is not particularly limited as long as it can be operated by a customer.

[0018] The product identification information includes the name of the product, an identifier for identifying the product, image data of the product, etc. The identifier for identifying the product may be a product code such as a JAN (Japanese Article Number) code, an EAN (European Article Number) code, or a UPC (Universal Product Code).

[0019] The delivery acceptance unit 112 accepts, for each product represented by the acquired product identification information, whether to have the product delivered. There are no particular limitations on the timing at which the delivery acceptance unit 112 accepts whether to have the product delivered. A specific example of this timing will be described in the second embodiment.

[0020] The delivery destination receiving unit 113 receives delivery destination information regarding the delivery destination of a product to be delivered. For example, the delivery destination information includes the name, address, telephone number, etc. of the person receiving the product. The person receiving the product may be the same person as the customer, or may be different people. The timing at which the delivery destination receiving unit 113 receives the delivery destination information is not particularly limited. A specific example of this timing will be described in the second embodiment. The delivery destination receiving unit 113 may receive delivery destination information for each product, or may receive delivery destination information for multiple products.

[0021] 2 is a flowchart showing an example of an operation of the information processing system 1 according to the first embodiment. The identification information acquisition unit 111 acquires product identification information (step S101). In step S101, the identification information acquisition unit 111 acquires the product identification information via a terminal device.

[0022] Next, the delivery acceptance unit 112 accepts whether to have each product delivered (step S102), and the delivery destination acceptance unit 113 accepts delivery destination information (step S103).

[0023] As described above, in the first embodiment, the information processing system 1 accepts whether to have each product delivered in self-scan shopping. This allows the information processing system 1 to simplify the procedures for product delivery in self-scan shopping.

[0024] The first embodiment is not limited to the above-described examples and can be modified in various ways. Furthermore, each functional unit may be realized by a single device. For example, each functional unit may be realized by a single server or a single terminal device that can be operated by a customer. Alternatively, each functional unit may be realized by a plurality of devices. For example, each functional unit may be realized by a plurality of servers.

[0025] (Embodiment 2) Next, a second embodiment will be described in detail with reference to the drawings. In the second embodiment, the functions described in the first embodiment are used as the basis, and further, the timing of accepting whether to have the product delivered and the timing of accepting the delivery destination information will be described in more detail. Furthermore, in the second embodiment, an example will be given of the process from product registration to payment for the product. Below, explanations of content that overlaps with the above explanation will be omitted to the extent that the explanation of the second embodiment is not unclear.

[0026] 3 is an explanatory diagram illustrating an example of an information processing system according to the second embodiment. The information processing system 2 includes, for example, a terminal device 20 and a server 21. For example, the terminal device 20 and the server 21 are connected via a communication network 22.

[0027] The terminal device 20 is a device capable of acquiring product identification information. For example, the terminal device 20 acquires product identification information through an operation by a customer. The terminal device 20 may be a smartphone or a tablet device. The terminal device 20 may also be a device attached to a mobile object such as a shopping cart. The terminal device 20 may be pre-installed with a specific application program used in the store.

[0028] The server 21 also manages various databases, such as a product database (DB) that stores product information.

[0029] Furthermore, in the second embodiment, an example will be described in which the terminal device 20 performs credit card payment. However, the payment method and the device performing the payment are not particularly limited. A settlement device (not shown) may perform the payment. For this reason, the server 21 may be connectable to the settlement device. Furthermore, the payment may be performed jointly by the server 21 and the terminal device 20 or the settlement device. Alternatively, the payment may be performed jointly by the terminal device 20 or the settlement device and a server (not shown) other than the server 21.

[0030] 4 is a block diagram showing a configuration example of the terminal device 20 according to the second embodiment. The terminal device 20 includes an acquisition unit 201, a reception unit 202, a display control unit 203, and a settlement unit 204. Data used in the processing of each unit and the results of the processing of each unit may be stored in a storage unit (not shown). The storage unit (not shown) may be included in the terminal device 20 or in a device different from the terminal device 20.

[0031] 5 is a block diagram showing an example of the configuration of server 21 according to the second embodiment. Server 21 has an identification information acquisition unit 211, a delivery acceptance unit 212, a delivery destination acceptance unit 213, a product registration unit 214, and a payment control unit 215. In the second embodiment, the product registration unit 214 and the payment control unit 215 are newly added to the components of the first embodiment. For example, the identification information acquisition unit 211, the delivery acceptance unit 212, and the delivery destination acceptance unit 213 have the functions of the identification information acquisition unit 111, the delivery acceptance unit 112, and the delivery destination acceptance unit 113, respectively, which are described in the first embodiment.

[0032] Server 21 also has a product DB 2101, a purchase product list DB 2102, and a delivery DB 2103. Each DB, data used in the processing of each unit, and the results of the processing of each unit may be stored in a storage unit (not shown). Note that the storage unit (not shown) may be provided in server 21, or may be provided in a device different from server 21. Also, some of the multiple DBs may be realized by a single DB. Also, each DB may be divided into multiple DBs in more detail. In this way, the method of realizing each DB is not particularly limited.

[0033] The product DB 2101 stores information about products sold at a store or affiliated stores including the store. Product information is information that describes a product. The product DB 2101 stores product information by product identification information. As described above, product identification information is not limited to product codes, product names, and image data. The product identification information used may differ depending on the method of acquiring product identification information, which will be described later. For example, when a product code is used as product identification information, product names and image data are information that can identify a product, but may also be used as product information. Specifically, the product DB 2101 stores product information by product code. For example, the product DB 2101 stores product codes in association with information such as product names, product categories, product prices, other product features, product image data, and product video data. Product categories are not limited to a particular category. For example, product categories may be broad categories such as food and stationery. Product categories may also be subcategories that divide broad categories, such as confectionery, meat, and vegetables. Product prices are, for example, the base prices of the products. The base price is the base price used when calculating the tax-inclusive price, subtotal, and total amount. Hereinafter, the base price will also be referred to as the tax-exclusive price. The tax-inclusive price is the price calculated by adding consumption tax to the tax-exclusive price. Other product features include the product name, product category, and other features other than the product price, and are not limited to these. Other product features may vary depending on the product and product category. For example, if the product is a shirt, the other product features may be the length, size, material, country of origin, etc. For example, if the product is food, the other product features may be information about the expiration date and allergies. Instead of the price, other features, image data, and video data, the product DB 2101 may store information indicating the location of the storage location where these are stored.

[0034] The purchase item list DB2102 stores, for each customer, the latest list of purchase items for which payment has not yet been completed. The purchase item list stores, for example, for each customer, information identifying the customer, product identification information of the products the customer plans to purchase, and purchase quantity information, in association with each other. The information identifying the customer is not particularly limited as long as it can uniquely identify the customer. For example, before registering products for a new customer begins, the customer is assigned a customer ID (identifier). Note that, if a member ID such as a point card number is accepted, the member ID may be used as the customer ID.

[0035] Furthermore, the product identification information registered in the purchased product list of the purchased product list DB 2102 may be, for example, a product code. This allows the terminal device 20 and the server 21 to obtain product prices, product names, etc. from the product DB 2101 using the product codes registered in the purchased product list. Furthermore, the contents stored in the purchased product list can be changed in various ways depending on the construction method of the information processing system 2.

[0036] The delivery DB 2103 stores, for each customer, the product to be delivered, the product quantity, and delivery destination information. For example, the delivery DB 2103 stores a customer ID, a product code, the product quantity, and delivery destination information in association with each other.

[0037] The identification information acquisition unit 211 acquires product identification information that identifies a product in a store through a customer's operation on the terminal device 20. Here, an example will be described in which the identification information acquisition unit 211 acquires the product identification information via the acquisition unit 201 of the terminal device 20.

[0038] The acquisition unit 201 of the terminal device 20 acquires product identification information. There is no particular limitation on the method by which the acquisition unit 201 acquires the product identification information. If the product identification information is a product code, the acquisition unit 201 may acquire the product code by reading the product code attached to the product using an imaging device. The product code may be represented by, for example, a one-dimensional code (barcode) or a two-dimensional code. In this way, the product identification information is not limited to the product code, and may be image data representing an image of a barcode representing the product code. Alternatively, the acquisition unit 201 may acquire image data representing an image of a product code or a barcode from a storage unit (not shown).

[0039] The acquiring unit 201 may also acquire the commodity identification information by reading a tag equipped with an RFID (Radio Frequency Identifier) ​​via a reading device. When an RFID is used, the reading device is an RFID reader. The acquiring unit 201 may acquire the commodity identification information via a reading device other than the RFID, such as by short-range wireless communication.

[0040] The acquisition unit 201 may also acquire product identification information by selecting product information from the product search results. For example, the method of product search is not particularly limited. Product search may be performed by text. Product search may be performed by image. More specifically, for example, the acquisition unit 201 may acquire product identification information by selecting a product from displayed product images through a customer operation.

[0041] The acquiring unit 201 may also accept input of a product code represented by numbers or letters via an input device or an input / output device. Examples of the input / output device include a touch panel display. Examples of the input device include a keyboard that can input numbers and letters.

[0042] Here, in the second embodiment, an example will be described in which the acquisition unit 201 acquires a product code by reading a barcode representing the product code via an imaging device. Specifically, for example, the acquisition unit 201 may start the imaging device via a specific application program and read the barcode using the imaging device.

[0043] Here, the display control unit 203 causes various screens to be displayed on a display device. The display device may be provided in the terminal device 20 or may be connected to the terminal device 20. In the following description, an example will be described in which the display device is provided in the terminal device 20. Therefore, in the following description, the display control unit 203 causing the terminal device 20 to display a screen means that the display control unit 203 causes the display device provided in the terminal device 20 to display a screen.

[0044] 6 is an explanatory diagram showing an example of reading a product code. The display control unit 203 causes the terminal device 20 to display a screen d001 including a frame indicating the position where the barcode is to be read. The acquisition unit 201 captures an image of the barcode captured within the frame by, for example, a customer's operation. Then, the acquisition unit 201 acquires the product code represented by the captured barcode. The acquisition unit 201 sends the acquired product code to the server 21.

[0045] Then, the identification information acquisition unit 211 of the server 21 receives the product code transmitted from the terminal device 20, and acquires the product code as product identification information.

[0046] Next, the delivery acceptance unit 212 accepts whether to have the product delivered for each product represented by the acquired product identification information. The timing at which the delivery acceptance unit 212 accepts whether to have the product delivered is not particularly limited.

[0047] For example, the delivery acceptance unit 212 may accept whether to have the product delivered before the product represented by the acquired product identification information is registered. Registering a product means that the product purchased by the customer is registered in the POS. In the second embodiment, registering in the POS means that the product code is registered in the purchased product list.

[0048] Furthermore, for example, the delivery reception unit 212 may accept whether to have the product delivered after the product represented by the acquired product identification information has been registered. Specifically, for example, the delivery reception unit 212 may accept whether to have each product delivered after the registration of all products purchased by the customer has been completed. More specifically, for example, the delivery reception unit 212 may accept whether to have each product delivered after a "Pay" button or the like is tapped on the terminal device 20.

[0049] Furthermore, specifically, for example, after the customer has completed registration of all products to be purchased, the delivery acceptance unit 212 may accept a request as to whether to have each product delivered before making payment.

[0050] Furthermore, the delivery reception unit 212 may receive information on whether or not a product that can be delivered should be delivered. For example, the product DB 2101 may further include information indicating whether or not delivery is possible for each product. This allows the delivery reception unit 212 to determine whether or not a product can be delivered.

[0051] Furthermore, the delivery acceptance unit 212 may accept whether to have each product delivered by pressing a button for accepting delivery displayed on the terminal device 20. An example of the display on the terminal device 20 will be described later.

[0052] The delivery address receiving unit 213 receives delivery address information regarding the delivery address of a product to be delivered. The timing at which the delivery address receiving unit 213 receives the delivery address information is not particularly limited. For example, the delivery address receiving unit 213 may receive the delivery address information before payment. For example, the delivery address receiving unit 213 may receive the delivery address information after payment. Furthermore, for example, the delivery address receiving unit 213 may receive the delivery address information each time a product is delivered. Furthermore, for example, the delivery address receiving unit 213 may receive the delivery address information in advance. "In advance" may be before the start of scan shopping, and is not particularly limited. For example, the delivery address receiving unit 213 may receive the delivery address information in advance using a specific application program at the customer's home, etc. Then, the delivery address receiving unit 213 may make the previously received delivery address information available when the product is to be delivered.

[0053] Next, each functional unit from product registration to payment will be described in detail using examples of screens displayed on the terminal device 20.

[0054] (Reception example 1) First, an example (reception example 1) will be described in which the delivery reception unit 212 receives a request as to whether to have the products delivered after the registration of all products to be purchased by the customer is completed and before payment is made. The description will be given using an example in which the reception unit 202 of the terminal device 20 receives various inputs.

[0055] For example, when the product identification information is acquired as described with reference to Fig. 6, the product registration unit 214 registers the product identification information in the purchased product list. Registering the product identification information in the purchased product list is also called product registration.

[0056] FIG. 7 is an explanatory diagram showing an example of the display of a purchased item list according to Reception Example 1. The display control unit 203 causes the terminal device 20 to display a screen d002 including the purchased item list. In the example of FIG. 7, biscuits and a television are registered in the purchased item list. As shown in FIG. 7, the screen d002 may include information about the registered items, such as the name and price of the items, as well as information such as the total amount and total number of items. Furthermore, the screen d002 may include, for example, a "Pay" button, an "Add Item" button, and a "Cancel Transaction" button.

[0057] The reception unit 202 receives taps on various buttons. For example, when the "Add Product" button is tapped, the display control unit 203 displays a screen d001 shown in Fig. 6 on the terminal device 20. When the "Cancel Transaction" button is tapped, the transaction is canceled.

[0058] The accepting unit 202 may accept completion of product registration by accepting a tap on the "Pay" button.

[0059] Next, after product registration is completed, the delivery acceptance unit 212 accepts whether or not to have each product delivered before payment.

[0060] 8 is an explanatory diagram showing an example before receiving a request for delivery for each product according to Reception Example 1. The display control unit 203 causes the terminal device 20 to display a screen d003 including buttons for selecting whether to have the product delivered, for each product. The screen d003 includes a button for each product name.

[0061] In FIG. 8, the button labeled "Takeout" is a button that allows a customer to select whether to have the product delivered. In the example of FIG. 8, each product is set to not be delivered by default. For example, the reception unit 202 may accept a request to have the product delivered when the button labeled "Takeout" is tapped. For example, when this button is tapped, the display control unit 203 causes the terminal device 20 to display a screen d003 in which the word "Takeout" has been changed to "Delivery." Note that while the screen d003 also includes other buttons such as an "End" button, the screen is similar to that of FIG. 9, and therefore the other buttons will be described using FIG. 9. Furthermore, the button that allows a customer to select whether to have the product delivered is not limited to the example of FIG. 8, as long as it allows the customer to select whether to have the product delivered.

[0062] Fig. 9 is an explanatory diagram showing an example after accepting whether to have each product delivered according to Reception Example 1. On screen d004 shown in Fig. 9, the button for selecting whether to have a television delivered is marked "Delivery." In this way, the customer can specify whether to have each product delivered.

[0063] Furthermore, the screen d004 may include an "End" button, a "Cancel Transaction" button, an "Add to Cart" button, etc. When the "Cancel Transaction" button is tapped, the transaction is canceled. When the "Add to Cart" button is tapped, the display control unit 203 may cause the terminal device 20 to display the screen d002 shown in FIG. 7.

[0064] For example, when the reception unit 202 receives a tap on the “Finish” button, it transmits to the server 21 the reception result indicating whether or not to have each product delivered.

[0065] The delivery acceptance unit 212 accepts whether to have each product delivered by receiving the acceptance result as to whether to have each product delivered.

[0066] Next, when there is a product delivery, the delivery destination receiving unit 213 receives delivery destination information. The delivery destination receiving unit 213 may receive delivery destination information input by the customer operating the terminal device 20.

[0067] 10 is an explanatory diagram showing an example of an input screen for delivery destination information. The display control unit 203 causes the terminal device 20 to display a screen d005 on which delivery destination information can be input. For example, the screen d005 has input fields for the name of the delivery destination, the delivery destination address, and contact information. The receiving unit 202 receives input for each input field.

[0068] When the receiving unit 202 receives the input of the delivery destination information, it transmits the delivery destination information to the server 21. Then, the delivery destination receiving unit 213 receives the delivery destination information and thereby accepts the delivery destination information.

[0069] Next, the payment control unit 215 settles the payment based on the price including the cost of delivery. The cost of delivery is called a delivery fee. The payment control unit 215 adds up the prices of the products registered in the purchase list and the delivery fee, and generates settlement information including the total amount including tax. Note that the settlement information only needs to include the information necessary for payment, and may be modified in various ways depending on the type of payment.

[0070] Then, the settlement unit 204 of the terminal device 20 performs settlement using the settlement information generated by the settlement control unit 215.

[0071] 11 is an explanatory diagram showing an example of payment. For example, the payment unit 204 performs a credit card payment. To this end, the display control unit 203 causes the terminal device 20 to display a screen d006 including the total amount included in the settlement information. The screen d006 also has input fields into which payment information for the credit card payment can be entered. Specifically, for example, the screen d006 has input fields into which the credit card number, the name written on the card, the credit card expiration date, the security code, the number of payments, etc. can be entered.

[0072] The screen d006 further includes a "Cancel Transaction" button, a "Confirm" button, etc. When the "Cancel Transaction" button is tapped, the transaction is canceled.

[0073] The reception unit 202 receives a tap of the "Confirm" button. When the "Confirm" button is tapped, the settlement unit 204 performs settlement based on the entered settlement information. Note that the specific credit settlement method is not particularly limited and may use existing technology.

[0074] In the above-described reception example 1, an example in which payment is made after input of delivery destination information is received has been described, but this is not limiting. For example, input of delivery destination information may be received after payment is completed.

[0075] 12 is a flowchart showing an example of the operation of the information processing system 2 according to Reception Example 1. The acquisition unit 201 of the terminal device 20 acquires a product code (step S201). The acquisition unit 201 transmits the accepted product code. The identification information acquisition unit 211 of the server 21 receives the product code and thereby acquires the product code.

[0076] Next, the product registration unit 214 registers the product (step S202). In step S202, the product registration unit 214 registers the product code in a list of products purchased by the customer.

[0077] Then, the product registration unit 214 transmits the registration result to the terminal device 20 (step S203). For example, in step S204, the product registration unit 214 may transmit a purchase product list as the registration result, or may transmit an identifier that identifies the purchase product list as the registration result.

[0078] The display control unit 203 causes the terminal device 20 to display a screen including the updated purchased product list (step S204). The reception unit 202 determines whether registration is complete (step S205). In step S205, the reception unit 202 may determine whether product registration is complete based on whether the "Pay" button has been tapped. For example, the reception unit 202 determines that product registration is complete when the "Pay" button has been tapped.

[0079] If product registration is not complete (step S205: No), the information processing system 2 returns to step S201.

[0080] When product registration is complete (step S205: Yes), the display control unit 203 causes the terminal device 20 to display a screen for accepting whether or not to have each product delivered (step S206). The reception unit 202 accepts whether or not to have each product delivered (step S207). The reception unit 202 transmits the acceptance result to the server 21. The delivery reception unit 212 receives the acceptance result and accepts whether or not to have each product delivered. The delivery reception unit 212 registers the product codes of the products to be delivered in the delivery DB 2103 (step S208).

[0081] The reception unit 202 receives the delivery destination information (step S209). Then, the reception unit 202 transmits the delivery destination information to the server 21. The delivery destination reception unit 213 receives the delivery destination information, thereby receiving the delivery destination information. Then, the delivery destination reception unit 213 registers the delivery destination information in the delivery DB 2103 (step S210).

[0082] Next, the payment control unit 215 generates payment information based on the prices and shipping fees of the products registered in the purchase product list (step S211). Then, the payment control unit 215 causes the terminal device 20 to make payment based on the payment information. Specifically, the payment control unit 215 transmits the payment information or an identifier that identifies the payment information to the terminal device 20. The payment unit 204 makes payment based on the payment information (step S212). The information processing system 2 then terminates its operation.

[0083] (Reception example 2) Next, an example (reception example 2) of accepting whether to have a product delivered during product registration will be described. First, an example will be described in which the delivery acceptance unit 212 accepts whether to have a product delivered after the product code is scanned and before the product registration result is displayed. Note that the example in which the product registration unit 214 registers a product is as described above, so a detailed explanation will be omitted.

[0084] FIG. 13 is an explanatory diagram showing an example of accepting whether to have each product delivered according to Reception Example 2. For example, when a product code is scanned, the display control unit 203 causes the terminal device 20 to display a screen d007 that can accept whether to have the product delivered. The screen d007 includes a "Delivery" button and a "Takeout" button. For example, when the "Delivery" button is tapped, the reception unit 202 accepts that the product is to be delivered. For example, when the "Takeout" button is tapped, the reception unit 202 accepts that the product is not to be delivered.

[0085] Then, when the reception unit 202 receives the tap of any button, it transmits the reception result to the server 21. The delivery reception unit 212 receives the reception result of whether to have each product delivered, and thereby receives whether to have each product delivered. When the delivery reception unit 212 has decided to have each product delivered, it registers the product code in the delivery DB 2103. Note that the button that allows the customer to select whether to have the product delivered is not limited to the example in FIG. 13 as long as it allows the customer to select whether to have the product delivered.

[0086] FIG. 14 is an explanatory diagram showing an example of the display of the purchased item list according to Reception Example 2. The display control unit 203 causes the terminal device 20 to display a screen d008 including the updated purchased item list. For example, the screen d008 includes product information for each item. Furthermore, the screen includes information for each item indicating whether the item is a delivery item. According to the screen d008, the television will be delivered after the customer purchases it. The biscuits will not be delivered, but will be taken home by the customer after purchase. The screen d008 may also include a total price including a delivery fee.

[0087] The screen d008 may also include a "Cancel Transaction" button and a "Pay" button. The "Cancel Transaction" button is the same as in the first reception example.

[0088] When the "Pay" button is tapped, the payment control unit 215 generates settlement information. The payment unit 204 performs payment using the settlement information.

[0089] Furthermore, the delivery destination receiving unit 213 receives delivery destination information in the same manner as in Reception Example 1. An example in which the delivery receiving unit 212 receives delivery destination information may be the same as in Reception Example 1. The timing for receiving the delivery destination information may be after product registration is completed, before payment, or after payment.

[0090] 15 is a flowchart showing an example of operation of the information processing system 2 according to Reception Example 2. The acquisition unit 201 of the terminal device 20 acquires a product code (step S221). The acquisition unit 201 transmits the accepted product code. The identification information acquisition unit 211 of the server 21 receives the product code and thereby acquires the product code.

[0091] Next, the product registration unit 214 registers the product (step S222). In step S222, the product registration unit 214 registers the product code in a list of products purchased by the customer.

[0092] Furthermore, the display control unit 203 causes the terminal device 20 to display a screen on which the user can select whether or not to have the product represented by the product code delivered (step S223). The reception unit 202 receives whether or not to have the product represented by the product code delivered (step S224). The reception unit 202 transmits the reception result to the server 21. By receiving the reception result, the delivery reception unit 212 receives whether or not to have each product delivered. The delivery reception unit 212 registers the product codes of the products to be delivered in the delivery DB 2103 (step S225).

[0093] Then, the product registration unit 214 transmits the product registration result to the terminal device 20 (step S226). For example, in step S226, the product registration unit 214 may transmit a purchased product list as the registration result, or may transmit an identifier that identifies the purchased product list as the registration result.

[0094] The display control unit 203 causes the terminal device 20 to display a screen including the updated purchased product list (step S227). In step S227, the display control unit 203 may also cause the terminal device 20 to display the result of accepting whether to have the product delivered.

[0095] The reception unit 202 determines whether the registration is complete (step S228). In step S228, the reception unit 202 may determine whether the registration of the product is complete based on whether the "Pay" button is tapped. For example, the reception unit 202 determines that the registration of the product is complete when the "Pay" button is tapped.

[0096] If product registration is not complete (step S228: No), the information processing system 2 returns to step S221.

[0097] When product registration is complete (step S228: Yes), the information processing system 2 accepts the delivery destination information (step S229), and the accepting unit 202 transmits the delivery destination information to the server 21. The delivery destination accepting unit 213 accepts the delivery destination information by receiving it. The delivery destination accepting unit 213 then registers the delivery destination information in the delivery DB 2103 (step S230).

[0098] Next, the payment control unit 215 generates payment information based on the prices and shipping fees of the products registered in the purchase product list (step S231). Then, the payment control unit 215 causes the terminal device 20 to make a payment based on the payment information. Specifically, the payment control unit 215 transmits the payment information or an identifier that identifies the payment information to the terminal device 20. The payment unit 204 makes a payment based on the payment information (step S232). The information processing system 2 then terminates its operation.

[0099] (Reception example 3) Next, an example will be described in which the delivery acceptance unit 212 accepts whether or not to have the product delivered after the product registration result is displayed.

[0100] 16 is an explanatory diagram showing a display example before accepting the purchased product list and whether to have each product delivered according to Reception Example 3. The display control unit 203 causes the terminal device 20 to display a screen d009 including the updated purchased product list. For example, the screen d009 includes product information for each product.

[0101] 16 may include a "Cancel Transaction" button and a "Pay" button. The "Cancel Transaction" button is the same as in Reception Example 1 and Reception Example 2.

[0102] When the "Pay" button is tapped, the payment control unit 215 generates settlement information as described above. The payment unit 204 performs payment using the settlement information.

[0103] Furthermore, the screen d009 includes a "Delivery" button. For example, when the delivery button is tapped, the delivery acceptance unit 212 accepts, for each product, whether or not to have it delivered.

[0104] 17 is an explanatory diagram showing an example of accepting whether to have each product delivered according to Reception Example 3. The display control unit 203 causes the terminal device 20 to display a screen d010 including buttons for selecting whether to have each product delivered. The screen d010 includes a button for each product name.

[0105] In FIG. 17, the button labeled "Takeout" is a button that allows a customer to select whether to have the product delivered. In the example of FIG. 17, each product is not delivered by default. For example, the reception unit 202 may accept a request to have the product delivered when the button labeled "Takeout" is tapped. Note that the button that allows a customer to select whether to have the product delivered is not limited to the example of FIG. 17, as long as it allows the customer to select whether to have the product delivered.

[0106] Although not shown in the figures, the description of the tapped button may be changed as described in Reception Example 1. Here, an example will be described in which the button corresponding to a television is tapped. The display control unit 203 causes the terminal device 20 to display a screen (not shown) in which the description of the button corresponding to the television has been changed from "Takeout" to "Delivery."

[0107] For example, when the reception unit 202 receives a tap on the "confirm" button, it transmits to the server 21 the reception result indicating whether or not to have each product delivered.

[0108] The delivery acceptance unit 212 receives the acceptance result of whether to have each product delivered, and accepts whether to have each product delivered. Then, the delivery acceptance unit 212 registers the product code of the product to be delivered in the delivery DB 2103.

[0109] FIG. 18 is an explanatory diagram showing an example of a display after receiving a list of purchased items and whether or not to have each item delivered according to Reception Example 3. Next, the display control unit 203 causes the terminal device 20 to display a screen d011 including the list of purchased items. In addition to the information included in screen d010 shown in FIG. 16, screen d011 includes information for each item indicating whether it is a delivery item. According to screen d011, the television will be delivered after the customer purchases it. The biscuits will not be delivered, but will be taken home by the customer after purchase. Screen d011 may also include a total price including a delivery fee.

[0110] The screen d011 may also include a "Cancel Transaction" button and a "Pay" button. The "Cancel Transaction" button is the same as in the previous example, so a description thereof will be omitted.

[0111] Furthermore, when the "Pay" button is tapped, the payment control unit 215 generates settlement information, similar to reception example 1 and reception example 2. The payment unit 204 performs payment using the settlement information.

[0112] Furthermore, the delivery destination receiving unit 213 receives delivery destination information in the same manner as in Reception Example 1 and Reception Example 2. The example in which the delivery receiving unit 212 receives delivery destination information may be the same as in Reception Example 1 and Reception Example 2. The timing for receiving the delivery destination information may be after product registration is completed, before payment, or after payment.

[0113] The flowchart according to Reception Example 3 only needs to differ from the flowchart according to Reception Example 1 or Reception Example 2 in the order of steps, and therefore a detailed description thereof will be omitted.

[0114] (Reception example 4) Next, an example will be described in which the delivery reception unit 212 receives a request to have the product delivered after the product registration result is displayed. In reception example 3, a "Delivery" button is displayed on the display screen of the purchased product list, and when the "Delivery" button is tapped, the server 21 receives a request to have each product delivered for that product. On the other hand, in reception example 4, a button that can receive a request to have each product delivered for that product is displayed on the display screen of the purchased product list on the terminal device 20, and the server 21 receives a request to have each product delivered for that product via the button.

[0115] FIG. 19 is an explanatory diagram showing a display example of a purchased item list according to Reception Example 4. The display control unit 203 causes the terminal device 20 to display a screen d012 including the purchased item list. The screen d012 includes product information for each item. The screen d012 also has a "Delivery Acceptance" button for each item that can accept a request to have the item delivered. For example, when the "Delivery Acceptance" button is tapped, the delivery acceptance unit 212 accepts a request to have the item delivered. Note that the button for selecting whether to have the item delivered is not limited to the example of FIG. 19, as long as it allows the customer to select whether to have the item delivered.

[0116] Screen d012 may also include a "Cancel Transaction" button and a "Pay" button. The "Cancel Transaction" button is the same as in the previous example, so its explanation will be omitted. The "Pay" button is the same as in Reception Example 3. When the "Pay" button is tapped, the payment control unit 215 generates settlement information. The payment unit 204 makes payment using the settlement information. Although not shown in the figure, screen d012 may also include information indicating that the product to be delivered is a delivery product.

[0117] The flowchart according to Reception Example 4 only differs from the flowchart according to Reception Example 1 or Reception Example 2 in the order of steps, and therefore a detailed description thereof will be omitted.

[0118] This concludes the description of each reception example. Note that although reception examples 1 to 4 have been described separately, the reception examples may be combined and are not particularly limited.

[0119] As described above, the delivery reception unit 212 may also receive a request as to whether or not to have a deliverable product delivered. Although detailed explanations will be omitted, in each reception example, the display control unit 203 displays a screen on the terminal device 20 that receives a request as to whether or not to have a deliverable product delivered.

[0120] Furthermore, in the above example, take-out is set as the default value, but delivery may also be set as the default value.

[0121] As described above, in the second embodiment, the information processing system 2 accepts, for each product, whether to have the product delivered after product registration is complete and before payment. In this way, the customer can confirm whether to have the product delivered at the end after product registration and before payment, so the customer can specify whether to have the product delivered without forgetting. Therefore, the information processing system 2 can simplify the procedures for product delivery.

[0122] When a product code is scanned, the information processing system 2 may accept a request for delivery of the product represented by the scanned product code. This allows the customer to confirm whether or not they want the product delivered immediately after scanning, so that the customer can specify whether or not to have the product delivered without forgetting. This allows the information processing system 2 to simplify the procedures for product delivery when customers use scan shopping.

[0123] Furthermore, the information processing system 2 displays a button for each registered product that allows the customer to select whether or not to have the product delivered, and the customer can select whether or not to have the product delivered using the button. The customer can easily specify whether or not to have the product delivered. Therefore, the information processing system 2 can simplify the procedures for product delivery.

[0124] Furthermore, the information processing system 2 performs settlement including the delivery fee, thereby enabling the information processing system 2 to simplify the procedures for delivery of products in self-scan shopping.

[0125] Furthermore, the above-described embodiments are not limited to the examples described above and can be modified in various ways. Furthermore, the configuration of the information processing system in each embodiment is not particularly limited. The information processing system may be realized by a single device, or by different devices for different functions or databases. The information processing system may be configured by a combination of multiple servers 21, such as a backbone server, a database server, a PLU (Price Look Up) server, a POS server, and an application server. The server managing various databases may function as, for example, a database server. The server outputting information to a terminal device may be at least one of an application server, a POS server, and a backbone server. Each server transfers information used for its assigned process, for example, via a communication network or the like. However, the names of the servers constituting the information processing system are not limited to these. The information processing system may also be configured by several of these servers. For example, a single terminal device may have the functional units of the server described in the second embodiment.

[0126] Furthermore, between devices such as the terminal device and the server described in each embodiment, the object of transmission and reception may be the information itself or an identifier representing the information. For example, when the terminal device displays an updated purchased item list on the display device of the terminal device, the server may transmit the purchased item list to the terminal device, or an identifier identifying the purchased item list.

[0127] The combination of the respective embodiments is not particularly limited. For example, in each embodiment, the information processing system may be configured to include some of the functional units and information. Furthermore, in each embodiment, the information processing system may have functional units and information that are not shown.

[0128] In each embodiment, each DB may include part of the information described above. Also, each DB may include information other than the information described above. Also, part of the multiple DBs may be realized by one DB. Also, each DB may be divided into multiple DBs in more detail. In this way, the method of realizing each DB is not particularly limited.

[0129] Furthermore, on each screen, each button is a GUI (Graphical User Interface) button, but the type of button is not particularly limited. For example, in the above example, a button that allows the customer to select whether or not to have the product delivered is displayed to allow the customer to select whether or not to have the product delivered, but the type of button is not particularly limited. For example, if the customer can select whether or not to have the product delivered, a check box or the like may be displayed.

[0130] Furthermore, the position, color, and size of each item, such as a button, input field, or display field, on each screen are not particularly limited. Buttons, information display fields, input fields, and the like (not shown) may be added to each screen. Furthermore, the background color of the screen may be changed.

[0131] Next, modified examples of each embodiment will be described. In the modified examples, the reference numerals used in the second embodiment will be used.

[0132] [Variation 1] In the second embodiment, an example of receiving new delivery destination information has been described, as shown in FIG. 10. The example of receiving delivery destination information is not limited to this. For example, the server 21 may have a personal DB that stores, for each customer, delivery destination information from previous delivery attempts. In such a case, the delivery destination receiving unit 213 may acquire the delivery destination information from the personal DB. Then, the display control unit 203 may cause the terminal device 20 to display a screen on which the acquired delivery destination information is entered in each input field of the screen d005 shown in FIG. 10. Alternatively, the delivery destination receiving unit 213 may accept an instruction to use delivery destination information that was previously entered.

[0133] [Variation 2] In the second modification, an example of estimating whether to have a product delivered will be described.

[0134] 20 is a block diagram showing an example of the configuration of the server 21 according to Modification 2. The server 21 shown in FIG. 20 further includes an estimation unit 216 in addition to the functional units of the server 21 shown in FIG.

[0135] The estimation unit 216 may estimate whether to have the product delivered based on the characteristics of the product. The estimation unit may also estimate whether to have the product delivered based on whether the product has been placed in a basket. The basket may be a physical shopping basket or a shopping cart, and is not particularly limited.

[0136] First, an example will be described in which the estimation unit 216 estimates whether to have the product delivered based on the product characteristics. The product characteristics are not particularly limited. For example, the product characteristics may be price, weight, size, etc. The estimation unit 216 acquires the product characteristics associated with the product identification information from the product DB 2101. The estimation unit 216 estimates whether to have the product delivered based on whether the product characteristics satisfy a predetermined condition. The predetermined condition is not particularly limited as long as it is a condition for narrowing down the product characteristics. The predetermined condition may be set by the customer or by an administrator of a specific application program. For example, the predetermined condition may be determined by a threshold value, a range, or the like. For example, the estimation unit may estimate that the product will be delivered if the weight of the product is equal to or greater than a threshold value.

[0137] Next, the estimation unit 216 may estimate whether to have the product delivered based on whether the product has been placed in the basket. The method for detecting whether the product has been placed in the basket is not particularly limited. For example, a weight sensor may be provided in the basket, and the estimation unit 216 may detect whether the registered product has been placed in the basket based on a change in the weight of the product in the basket detected by the weight sensor. Alternatively, an imaging device may be used. For example, the imaging device may be provided in the basket or in the store. The estimation unit 216 detects whether the product has been placed in the basket by capturing an image of the product placed in the basket with the imaging device.

[0138] Furthermore, for example, when payment is made using a payment device, the estimation unit 216 may detect whether an item has been placed in the basket using a weight sensor or an imaging device attached to the payment device.

[0139] Specifically, for example, the estimation unit 216 estimates that if a registered product is added to the cart, the product will not be delivered. Also, for example, the estimation unit 216 estimates that if a registered product is not added to the cart, the product will be delivered. More specifically, for example, the estimation unit 216 may estimate that if a product is not added to the cart even after a predetermined time has elapsed since the product was registered, the product will be delivered. Alternatively, for example, the estimation unit 216 may estimate that if a product is not added to the cart even after all product registrations have been completed, the product will be delivered.

[0140] There is no particular limitation on how the estimation result by the estimation unit 216 is used. For example, the delivery reception unit 212 may receive a request as to whether to deliver the product that is estimated by the estimation unit 216 to be delivered. Alternatively, the estimation result by the estimation unit 216 may be used, for example, as an initial value setting for each reception example. Furthermore, for example, when receiving a delivery request by the delivery reception unit 212, the display control unit 203 may also display the estimation result. There is no particular limitation on how the estimation result is displayed. For example, a message such as "There is no registered product in the cart. Do you want to deliver it?" or "There is more than 10 kg of product. Do you want to deliver it?" may be displayed.

[0141] [Variation 3] Furthermore, the default value for whether or not to perform delivery may be set in advance by the store. For example, the default value may be set for each product category. Specifically, for example, the default value for home appliances may be set to perform delivery, and the default value for food may be set to not perform delivery.

[0142] [Variation 4] In the second embodiment, for example, an example has been described in which the terminal device 20 includes the display control unit 203, and the display control unit 203 controls the display of each screen on the display device of the terminal device 20. For example, the server 21 may include the display control unit 203. In such a case, the display control unit 203 of the server 21 generates information on a screen to be displayed on the display device of the terminal device 20 and transmits the information to the terminal device 20. The terminal device 20 may display the screen on the display device based on the received screen information.

[0143] In addition, in the second embodiment, examples of output and reception are given as displaying a screen and receiving an input to a screen, but the present invention is not limited to these examples. For example, reception by audio output or audio input may also be used.

[0144] [Variation 5] In each embodiment, an example has been described in which whether or not to have delivery performed for each product is accepted. However, for example, whether or not to have delivery performed for each product category may also be accepted.

[0145] [Variation 6] As mentioned above, in the second embodiment, an example has been described in which the terminal device 20 performs the payment, but the payment may also be performed by a settlement device. In such a case, the settlement device includes at least the payment unit 204 of the terminal device 20. When the settlement device includes the payment unit 204, as mentioned above, the payment method by the payment unit 204 is not particularly limited and existing technology may be used, so detailed description will be omitted.

[0146] Furthermore, for example, the settlement device may also include a reception unit and a display control unit, similar to the terminal device 20. The delivery reception unit 212 and delivery destination reception unit 213 of the server 21 may receive various information via the settlement device. In such a case, the settlement device may also include a registration result acquisition unit for reading the product registration results from the terminal device 20.

[0147] Specifically, in reception example 1, the display control unit 203 of the terminal device 20 displays screen d002 of FIG. 7 , and the reception unit 202 of the terminal device 20 accepts a tap on the “Pay” button. The display control unit 203 of the terminal device 20 causes the terminal device 20 to display information that enables the settlement device to obtain the product registration results. The registration result acquisition unit of the settlement device then acquires this information from the terminal device 20. The acquisition method is not particularly limited, and may include reading a one-dimensional code or a two-dimensional code, or reading via near-field wireless communication. Taking reading a two-dimensional code as an example, for example, the display control unit 203 of the terminal device 20 causes the terminal device 20 to display a screen including a two-dimensional code that enables the product registration results to be obtained. The registration result acquisition unit of the settlement device reads the two-dimensional code displayed on the terminal device 20. As a result, the registration result acquisition unit of the settlement device can acquire the product registration results represented by the two-dimensional code from the server 21. The display control unit of the settlement device then causes screen d003 shown in FIG. 8 to be displayed on the display device of the settlement device. The reception unit of the settlement device receives whether to have each product delivered and transmits the reception result to server 21. Then, delivery reception unit 212 may receive the reception result and thereby receive whether to have each product delivered. In this way, delivery reception unit 212 may receive whether to have each product delivered via the settlement device.

[0148] The method by which the registration result acquisition unit of the settlement device acquires information from which the product registration results can be obtained is not limited to the above example. For example, the terminal device 20 may output this information to a portable medium. The portable medium may be paper or a plastic sheet, and is not particularly limited. For example, in the case of paper, the terminal device 20 may cause a printing device (not shown) connected via a communication network to print information from which the product registration results can be obtained on the paper. A one-dimensional code, a two-dimensional code, or the like representing this information may be printed on the paper. The registration result acquisition unit of the settlement device may then acquire this information from the printed paper.

[0149] Alternatively, for example, terminal device 20 may transmit this information to the settlement device using a specific application program used in the store. Then, the registration result acquisition unit of the settlement device may acquire this information by receiving it from terminal device 20.

[0150] Specifically, in reception examples 3 and 4, similar to reception example 1, the registration result acquisition unit of the settlement device reads the two-dimensional code displayed on the terminal device 20. The registration result acquisition unit of the settlement device can then acquire the product registration result represented by the two-dimensional code from the server 21. The display control unit of the settlement device then displays a screen such as screen d009 shown in FIG. 16 or screen d012 shown in FIG. 19 on the display device of the settlement device. Note that if all products are registered on the terminal device but no products are registered on the settlement device, the "Add Product" button is not displayed on screen d009 shown in FIG. 16 or screen d012 shown in FIG. 19. Similar to reception example 1, the reception unit of the settlement device then accepts whether to have each product delivered and transmits the acceptance result to the server 21. The delivery acceptance unit 212 may then accept whether to have each product delivered by receiving the acceptance result. In this manner, the delivery acceptance unit 212 may accept whether to have each product delivered via the settlement device.

[0151] Additionally, in Reception Example 1 to Reception Example 4, the display control unit of the settlement device may cause the display device of the settlement device to display screen d005 shown in Fig. 10. When the reception unit of the settlement device receives delivery destination information through operation by the customer, it transmits the received delivery destination information to server 21. Then, the delivery destination reception unit 213 may receive the delivery destination information from the settlement device, thereby receiving the delivery destination information.

[0152] This concludes the description of the embodiments and their modifications. Note that the embodiments and their modifications may be used in combination.

[0153] (Computer equipment) Next, an example of a hardware configuration in which each device such as a terminal device, a server, etc. is realized by a computer device will be described. Fig. 20 is an explanatory diagram showing an example of a hardware configuration of a computer device. For example, some or all of the devices such as the terminal device and the server can be realized using any combination of a computer device 30 and a program as shown in Fig. 20.

[0154] The computer device 30 includes, for example, a processor 301, a read-only memory (ROM) 302, a random access memory (RAM) 303, a storage device 304, a communication interface 305, and an input / output interface 306. Each component is connected to the other via a bus 307.

[0155] The processor 301 controls the entire computer device 30. Examples of the processor 301 include a CPU (Central Processing Unit) and a DSP (Digital Signal Processor). There may be multiple processors 301. The computer device 30 has a storage unit including a ROM 302, a RAM 303, and a storage device 304. Examples of the storage device 304 include a semiconductor memory such as a flash memory, a hard disk drive (HDD), and a solid state drive (SSD). For example, the storage device 304 stores an operating system (OS) program, application programs, and programs according to the embodiments. Alternatively, the ROM 302 stores application programs and programs according to the embodiments. The RAM 303 is used as a work area for the processor 301.

[0156] The processor 301 also loads programs stored in the storage device 304, ROM 302, etc. The processor 301 then executes each process coded in the program. The processor 301 may also download various programs via the communication network 32. The processor 301 also functions as a part or all of the computer device 30. The processor 301 may then execute the processes or instructions in the illustrated flowchart based on the program.

[0157] The communication interface 305 is connected to a communication network 32, such as a LAN (Local Area Network) or WAN (Wide Area Network), via a wireless or wired communication line. This allows the computer device 30 to be connected to external devices and external computers via the communication network 32. The communication interface 305 serves as an interface between the communication network 32 and the inside of the computer device 30. The communication interface 305 also controls the input and output of data from external devices and external computers.

[0158] Furthermore, the input / output interface 306 is connected to at least one of an input device, an output device, and an input / output device. The connection method may be wireless or wired. Examples of the input device include a keyboard, a mouse, and a microphone. Examples of the output device include a display device, a lighting device, and a speaker that outputs sound. Examples of the input / output device include a touch panel display. The input device, output device, and input / output device may be built into the computer device 30 or may be external.

[0159] The hardware configuration of the computer device 30 is an example. The computer device 30 may have some of the components shown in FIG. 20 . The computer device 30 may have components other than those shown in FIG. 20 . For example, the computer device 30 may have a drive device or the like. The processor 301 may then read programs and data stored on a recording medium attached to the drive device or the like into the RAM 303. Examples of non-transitory tangible recording media include optical disks, flexible disks, magneto-optical disks, and USB (Universal Serial Bus) memories. As described above, the computer device 30 may also have input devices such as a keyboard and a mouse. The computer device 30 may also have an output device such as a display. The computer device 30 may also have an input device, an output device, and an input / output device.

[0160] The computer device 30 may have an imaging device capable of reading barcodes, etc. Furthermore, as described above, the computer device 30 may have a reading device for performing near field wireless communication, etc.

[0161] The computer device 30 may have various sensors (not shown). The type of sensor is not particularly limited. Examples of the sensor include an acceleration sensor, a gyro sensor, a magnetic sensor, a GPS (Global Positioning System) sensor, etc. Examples of the sensor include a fingerprint sensor, a LiDAR (Light, Detection and Ranging), a proximity sensor, and an ambient light sensor.

[0162] This concludes the description of the hardware configuration of each device. There are various variations in the implementation of each device. For example, the information processing system may be implemented by any combination of different computers and programs for each component. Furthermore, multiple components included in each device may be implemented by any combination of a single computer and program.

[0163] Furthermore, some or all of the components of the information processing system may be implemented using circuits for specific applications. Alternatively, some or all of the information processing system may be implemented using general-purpose circuits including a processor such as an FPGA (Field Programmable Gate Array). Alternatively, some or all of the information processing system may be implemented using a combination of circuits for specific applications and general-purpose circuits. These circuits may be a single integrated circuit. Alternatively, these circuits may be divided into multiple integrated circuits. These multiple integrated circuits may be connected via a bus or the like.

[0164] Furthermore, when some or all of the components of each device are realized by a plurality of computers, circuits, etc., the plurality of computers, circuits, etc. may be centrally located or distributed.

[0165] The information processing method described in each embodiment is realized by execution by a terminal device or a server. Furthermore, the information processing method is realized by execution by a computer such as a terminal device or a server of a prepared program. The program described in each embodiment is recorded on a computer-readable recording medium such as an HDD, SSD, flexible disk, optical disk, flexible disk, magneto-optical disk, or USB memory. The program is then executed by being read from the recording medium by a computer. Furthermore, the program may be distributed via a communication network 32.

[0166] The functions of each of the components of the information processing system in each embodiment described above may be realized by hardware, such as a computer device, or may be realized by a computer device or firmware under program control.

[0167] Although the present disclosure has been described above with reference to various embodiments, the present disclosure is not limited to the above embodiments. The configuration and details of each of the present disclosures may include embodiments to which various modifications that would be apparent to those skilled in the art are applied within the scope of the present disclosure. The present disclosure may also include embodiments in which the details described herein are appropriately combined or substituted as necessary. For example, details described using a particular embodiment may also be applied to other embodiments to the extent that no contradiction occurs. For example, although multiple operations are described in sequence in the form of a flowchart, the order of the descriptions does not limit the order in which the multiple operations are performed. Therefore, when implementing each embodiment, the order of the multiple operations may be changed as long as it does not interfere with the content.

[0168] Some or all of the above-described embodiments can be described as follows: However, some or all of the above-described embodiments are not limited to the following.

[0169] (Appendix 1) an identification information acquisition means for acquiring product identification information for identifying a product in response to a customer's operation on a terminal device in the store; a delivery acceptance means for accepting whether or not to have each of the products represented by the acquired product identification information delivered; a delivery destination receiving means for receiving delivery destination information regarding a delivery destination of the product to be delivered; An information processing system comprising: (Appendix 2) the delivery acceptance means accepts whether to have each product delivered after the product registration is completed and before payment for the registered product is made; 10. The information processing system of claim 1. (Appendix 3) the delivery acceptance means accepts a request for delivery of the newly registered product each time the product is newly registered; 10. The information processing system of claim 1. (Appendix 4) the delivery acceptance means accepts, for each of the products, whether or not to have the product delivered by means of a button capable of accepting delivery displayed on the terminal device; 4. An information processing system according to any one of appendices 1 to 3. (Appendix 5) an estimation means for estimating whether the product should be delivered based on whether the product has been added to a cart after the product has been registered; 5. An information processing system according to any one of claims 1 to 4, comprising: (Appendix 6) an estimation means for estimating whether the product should be delivered based on the characteristics of the product; 6. An information processing system according to any one of appendices 1 to 5, comprising: (Appendix 7) The delivery acceptance means accepts whether to deliver the product estimated to be delivered. 7. The information processing system according to claim 5 or 6. (Appendix 8) A payment control means for making payment based on the price including the amount of delivery when the product is delivered. 8. An information processing system according to any one of appendices 1 to 7, comprising: (Appendix 9) In the store, product identification information for identifying the product is acquired through an operation of a customer on a terminal device; Accept a request for delivery for each of the products represented by the acquired product identification information; When the product is to be delivered, receiving delivery destination information regarding a delivery destination of the product; Information processing methods. (Appendix 10) On the computer, In the store, product identification information for identifying the product is acquired through an operation of a customer on a terminal device; Accept a request for delivery for each of the products represented by the acquired product identification information; When the product is to be delivered, receiving delivery destination information regarding a delivery destination of the product; A program that executes a process. (Appendix 11) On the computer, In the store, product identification information for identifying the product is acquired through an operation of a customer on a terminal device; Accept a request for delivery for each of the products represented by the acquired product identification information; When the product is to be delivered, receiving delivery destination information regarding a delivery destination of the product; A non-transitory recording medium readable by the computer that records a program for executing processing. [Explanation of symbols]

[0170] 1,2 Information Processing Systems 20 Terminal equipment 21 Server 22 Communication Network 30 Computer Equipment 32 Communication Network 111,211 Identification information acquisition unit 112,212 Delivery Reception Department 113,213 Delivery Reception Department 201 Acquisition Department 202 Reception 203 Display control unit 204 Payment Department 214 Product Registration Department 215 Payment Control Unit 301 processor 302 ROM 303 RAM 304 Storage device 305 Communication Interface 306 Input / Output Interface 307 Bus d001 screen d002 screen d003 screen d004 screen d005 Screen d006 Screen d007 Screen d008 Screen d009 screen d010 screen d011 Screen d012 Screen 2101 Product DB 2102 Purchased Product List DB 2103 Delivery DB

Claims

1. an identification information acquisition means for acquiring product identification information for identifying a product in response to a customer's operation on a terminal device in the store; a delivery acceptance means for accepting whether or not to have each of the products represented by the acquired product identification information delivered; a delivery destination receiving means for receiving delivery destination information regarding a delivery destination of the product to be delivered; an estimation means for estimating whether the product should be delivered based on whether the product has been added to a cart after the product has been registered; Equipped with The delivery acceptance means determines that the registration of the registered products is completed when it accepts an instruction to pay for the registered products, and accepts whether or not to have each product delivered before making the payment for the registered products; The estimation means estimates that the product will not be delivered if the product is placed in the basket, and estimates that the product will be delivered if the product is not placed in the basket. Information processing system.

2. the delivery acceptance means accepts, for each of the products, whether or not to have the product delivered by means of a button capable of accepting delivery displayed on the terminal device; The information processing system according to claim 1 .

3. The estimation means estimates whether to have the product delivered based on the characteristics of the product.

3. The information processing system according to claim 1.

4. The delivery acceptance means accepts whether to deliver the product estimated to be delivered.

4. The information processing system according to claim 1.

5. a payment control means for making payment based on a price including the cost of delivery when the product is delivered; 5. The information processing system according to claim 1, comprising:

Images