Sales support system, sales support method, and sales support program

Abstract

To provide a sales support system, a sales support method, and a sales support program for updating a price of a registered commodity registered using a portable terminal through an operation of a customer when a set price of the commodity is changed.SOLUTION: A sales support system includes: a list generation unit configured to generate a purchase commodity list including a commodity registered using a portable terminal through an operation of a customer and a price based on a set price referred to for registration of the commodity; and a price update unit configured to update a price of a registered commodity included in the purchase commodity list to a new set price when an execution condition of a price updating process is satisfied.SELECTED DRAWING: Figure 11

Description

Technical Field

[0001] The present disclosure relates to a sales support system and the like.

Background Art

[0002] There is known a product sales system in which a customer uses a mobile terminal such as a smartphone owned by the customer in a store to read a barcode of a product and perform product registration. Such a system is called, for example, a self-scanning shopping system. For example, Patent Document 1 discloses a self-scanning shopping system that displays a selling price on a customer's mobile terminal when the selling price is changed according to a predetermined condition such as set sales. Patent Document 1 discloses, for example, a set discount for a specific combination of products and a total amount discount that occurs when the total amount of purchased products exceeds a predetermined amount.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the operation of a store, the set price of a product may be changed during store business hours. In a self-scanning shopping system, for a product registered using a mobile terminal, the price at a predetermined time is referred to. If the set price is changed after registration, it may be desired that the price change be reflected in the price of the registered product.

[0005] In Patent Document 1, it is not assumed that the set price of a product is changed during a customer's shopping.

[0006] The present disclosure aims to provide a sales support system or the like that can update the price of a registered product registered using a portable terminal by a customer's operation when the set price of the product is changed.

Means for Solving the Problem

[0007] The sales support system according to the present disclosure includes a list generation means for generating a purchase product list including a product registered using a portable terminal by a customer's operation and a price based on the set price referred to for the registration of the product, and an update means for updating the price of the registered product included in the purchase product list to a new set price when the execution condition of the price update process is satisfied.

[0008] The sales support method according to the present disclosure generates a purchase product list including a product registered using a portable terminal by a customer's operation and a price based on the set price referred to for the registration of the product, and updates the price of the registered product included in the purchase product list to a new set price when the execution condition of the price update process is satisfied.

[0009] The program according to the present disclosure includes a process for generating a purchase product list including a product registered using a portable terminal by a customer's operation and a price based on the set price referred to for the registration of the product, and a process for updating the price of the registered product included in the purchase product list to a new set price when the execution condition of the price update process is satisfied, and causes a computer to execute the processes.

Advantages of the Invention

[0010] According to the present disclosure, it is possible to provide a sales support system or the like that can update the price of a registered product registered using a portable terminal by a customer's operation when the price of the product is changed.

Brief Description of the Drawings

[0011]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9A

Figure 9B

Figure 9C

Figure 10

Figure 11

Figure 12

Figure 13

Embodiments for Carrying Out the Invention

[0012] Hereinafter, with reference to the drawings, embodiments of a sales support system, method, program, and recording medium for non-temporarily recording the program according to the present disclosure will be described in detail. This embodiment does not limit the disclosed technology.

[0013] (First Embodiment) FIG. 1 is a block diagram showing the configuration of a sales support system 11 according to the first embodiment. The sales support system 11 may be connected to a portable terminal 12 via a communication network 13, for example.

[0014] A customer acquires a product from a shelf or the like in a store and registers the product using the portable terminal 12. That is, the customer performs self-scanning shopping using the portable terminal 12.

[0015] The sales support system 11 is a server that manages various sales information such as the price, inventory status, and sales information of the store regarding the products sold in the store. Note that the sales support system 11 may manage the sales information of a plurality of stores collectively. Alternatively, the sales support system 11 may exist for each store. And the sales support system 11 may manage the sales information of one store.

[0016] The sales support system 11 according to the first embodiment includes a list generation unit 101, a price update unit 102, a settlement information generation unit 103, and a storage unit 114. The storage unit 114 includes a product DB (Database) 115, a purchased product list DB 116, and a sales DB 119. The list generation unit 101, the price update unit 102, and the settlement information generation unit 103 are examples of list generation means, update means, and settlement information generation means, respectively.

[0017] The portable terminal 12 is a terminal used by a customer. The portable terminal 12 is, for example, a mobile terminal such as a smartphone or a tablet. The type of the portable terminal 12 is not particularly limited. The portable terminal 12 may be owned by the customer or lent in the store. The portable terminal 12 may be attached to a shopping basket or a shopping cart, or may be provided integrally with the shopping basket or the shopping cart. An apparatus having the functions of the portable terminal 12 is also called a mobile terminal, a movable terminal, or a mobile body. The mobile body includes a robot. The mobile body may be movable manually or automatically by including, for example, movable parts such as tires and a driving device such as a motor.

[0018] The list generation unit 101 generates a purchased product list regarding the products registered using the portable terminal 12. The purchased product list includes at least the product registered using the portable terminal 12 by the customer's operation and the price based on the set price referred to for the registration of the product.

[0019] Specifically, the list generation unit 101 generates, for example, a purchased product list in which information for identifying the customer, product information of the product the customer plans to purchase, and the purchase quantity are associated. The list generation unit 101 stores the generated purchased product list in the purchased product list DB 116. The product that the customer plans to purchase and is included in the purchased product list is also called a registered product.

[0020] The purchased product list is uniquely identified by the information for identifying the customer. The information for identifying the customer is, for example, a customer ID (Identifier) that uniquely identifies the customer. For example, when the customer starts registering a product using the portable terminal 12, the list generation unit 101 assigns a customer ID to the customer. Assuming that one transaction is from the start of the store entry process or the registration process to the end of settlement, the customer ID may be assigned for each transaction.

[0021] The product information included in the purchased product list includes information that can identify the product, such as the product name or product ID. Also, the product information in the purchased product list may include the price of the product obtained by referring to the product DB 115 as an example of the price based on the set price referred to for the registration of the product.

[0022] The list generation unit 101 generates a purchased product list based on a registration request from the portable terminal 12. Specifically, the list generation unit 101 adds or deletes the products included in the purchased product list based on the product information included in the registration request. That is, the product that the customer plans to purchase is registered using the portable terminal 12 by the customer's operation.

[0023] The list generation unit 101 may transmit the purchased item list in which items are registered to the portable terminal 12. When the purchased item list is transmitted, for example, the purchased item list is displayed on the portable terminal 12, and the user can check the purchased item list.

[0024] The price stored in the product DB 115 can be changed during the customer's shopping. The price change is at least assumed to be the case where the store manager or the sales support system 11 changes the price during business hours, and the case where a time schedule is set in advance for the price stored in the product DB 115, but is not limited to this.

[0025] For example, the price may be changed based on the input of the store manager in order for the store manager to adjust the sales volume and profit margin of the product. The sales support system 11 may change the price based on, for example, the date, day of the week, time, target sales number, inventory status, expiration date of the product, consumption date, etc. When a time schedule is set, the price for each time zone is stored for the product.

[0026] When the execution condition is satisfied, the price update unit 102 performs a price update process of updating the price of the registered product included in the purchased item list to a new set price. The execution condition of the price update process is not particularly limited, but for example, it may be that one or more products have been registered using the portable terminal 12. That is, the price update unit 102 may perform the price update process every time a predetermined number of new products are registered. The price update process will be described later.

[0027] The price update unit 102 may determine whether the execution condition is satisfied. Specifically, for example, when the execution condition is that one new product has been registered using the portable terminal 12, the price update unit 102 determines whether the number of products in the purchased item list has increased since the previous determination. That is, in this case, the price update unit 102 determines that the execution condition is satisfied when the number of products in the purchased item list has increased since the previous determination.

[0028] Alternatively, instead of determining the execution conditions, the price update unit 102 may receive a notification that the execution conditions are satisfied. Specifically, when the execution condition is that a new product has been registered using the portable terminal 12, the price update unit 102 may receive a notification from the list generation unit 101 that a product has been added. The price update unit 102 may receive a notification that the execution conditions are satisfied from sources other than the list generation unit 101.

[0029] As an example of the price update process, when a predetermined execution condition is satisfied, the price update unit 102 refers to the set price and updates the price included in the purchased product list based on the referred set price.

[0030] As an example of the price update process, when a predetermined execution condition is satisfied, the price update unit 102 may determine whether the set price has been changed, and if the price has been changed, update the price included in the purchased product list. To determine whether the set price has been changed, the price update unit 102 may determine whether the price of the product included in the purchased product list matches the price stored in the product DB 115. Alternatively, the price update unit 102 may determine whether there has been an update to the product DB 115 after the list generation unit 101 generated the list. Or, the price update unit 102 may determine whether there has been an update to the product DB 115 after adding a product to the list. Further, the price update unit 102 may determine whether the price has been changed by determining whether there has been an update to the product DB 115 since the previous determination.

[0031] If the price has been changed, the price update unit 102 updates the price of the registered product included in the purchased product list to the new price. Specifically, the price update unit 102 updates the price of the product in the purchased product list stored in the purchased product list DB 116 to the new set price indicated by the product DB 115. In the present embodiment, the price update unit 102 may update the price to a lower price or a higher price. The price update unit 102 may refer to the set price and update the price even when the set price has not been changed.

[0032] The price update unit 102 may transmit to the portable terminal 12 a purchase product list in which the prices of registered products have been updated. Further, the price update unit 102 may cause the portable terminal 12 to display a notification that the price has been updated.

[0033] The settlement information generation unit 103 generates settlement information used for settling the payment based on the purchase product list. The settlement information includes at least the total payment amount for the registered products included in the purchase product list. The settlement information may further include the total quantity of the registered products, the product names and prices of each registered product, etc.

[0034] When the price update unit 102 updates the price, the settlement information generation unit 103 generates settlement information based on the updated purchase product list. The settlement information generation unit 103 may transmit the settlement information to the portable terminal 12 for settlement, or may transmit it to the settlement device installed in the store.

[0035] The settlement information generation unit 103 updates the sales DB 119, for example, according to the content of the settlement.

[0036] The storage unit 114 stores, for example, data used for the processing of each part of the sales support system 11.

[0037] The product DB 115 stores product information of products handled in a store or a chain store including the store. Specifically, the product DB 115 stores product information for each product, for example. The product information stored in the product DB 115 includes a product ID, a product name, and the price of the product. The product ID is, for example, a product code (hereinafter referred to as a product code). The product code is, for example, a JAN (Japanese Article Number) code, an EAN (European Article Number) code, or a UPC (Universal Product Code). Further, the product ID may be the product name. The price of the product may be the price before tax or the price including tax of the product.

[0038] The product DB 115 may further include information such as, for example, product classification, product features, and product inventory status. The product classification is not particularly limited. For example, the product classification may be a broad classification such as food, stationery, etc. Also, the product classification may be a classification such as confectionery, meat, vegetables, etc. The product features are not particularly limited. The product features may be, for example, expiration date, consumption deadline, name of manufacturing company, name of selling company, etc. The product inventory status may be, for example, the number of products in stock.

[0039] In addition to the product ID, the product information may include information for identifying the product. For example, the product information may include image data of the product, or information on feature quantities obtained from the image data of the product.

[0040] The product DB 115 may include all of the above-mentioned information regarding the product, or may include only a part of it. Also, the product DB 115 may include information other than the above-mentioned information regarding the product.

[0041] The purchased product list DB 116 stores the latest purchased product list for each customer that has not been settled yet. Note that a membership ID may be used as the customer ID that uniquely identifies the purchased product list. The membership ID is an ID that uniquely identifies a member registered in the store's service. Alternatively, the purchased product list DB 116 may store the customer ID and the membership ID in association with each other.

[0042] The purchased product list DB 116 may include the entry time, which is the time when the customer executed the entry process. The entry process is, for example, a process for starting the above-mentioned registration process. The purchased product list DB 116 may include the time when the registration request for each product was received.

[0043] Based on the product ID in the purchased product list, the price of the product is obtained from the product DB 115. In the purchased product list, the price indicated by the product DB 115 at the time when the product is registered may be registered first. Alternatively, the price of the product DB 115 corresponding to the time when the store entry process is executed may be registered first. The purchased product list DB 116 may store the price of the product including tax calculated based on the price of the tax-excluded product obtained from the product DB 115. The price update unit 102 can update the price first registered in the purchased product list.

[0044] The purchased product list DB 116 may include all or part of the aforementioned information regarding the purchased product list. Further, the purchased product list DB 116 may include information other than the aforementioned information regarding the purchased product list.

[0045] The sales DB 119 stores information regarding the sales of each store, for example. The sales DB 119 may manage information corresponding to each settlement for each store, for example. The sales DB 119 stores, for example, by associating each piece of information such as the store ID, the ID of the portable terminal 12 that registered the product, the member ID of the user, the product ID of the purchased product, the purchase quantity, the selling price, and the purchase date and time. The store ID is an identifier that uniquely identifies the store.

[0046] The sales DB 119 may include all or part of the aforementioned information regarding the sales. Further, the sales DB 119 may include information other than the aforementioned information regarding the sales.

[0047] Also, for example, the sales DB 119 and the product DB 115 are linked by the product ID. The sales support system 11 may update the inventory status of the product DB 115 based on the information on the purchase quantity registered in the sales DB 119, for example.

[0048] The sales support system 11 may not have some of the functional units such as the settlement information generation unit 103, for example. The sales support system may have functional units not shown in the figure.

[0049] The device configuration of the sales support system 11 is not particularly limited. The sales support system 11 may be implemented by a single device, or may be implemented by different devices according to functions or databases (Databases). Further, some functions of the sales support system 11 may be implemented by the portable terminal 12. For example, at least any one of the list generation unit 101, the price update unit 102, and the settlement information generation unit 103 may be implemented by the portable terminal 12.

[0050] The sales support system 11 may be configured by a combination of servers such as a backbone server, a database server, a PLU (Price Look Up) server, a POS (Point of Sales) server, and an application server. For example, the PLU server and the application server may be used to implement the list generation unit 101. The server that manages the sales DB 119 may function as, for example, a database server. The server that displays the screen on the portable terminal 12 may be at least any one of an application server, a POS server, or a backbone server. Each server exchanges information used for the processes assigned to each via, for example, the communication network 13 or the like. However, the names of the servers constituting the sales support system 11 are not limited to these. Further, the sales support system 11 may not include some of these servers.

[0051] FIG. 2 is a block diagram showing a configuration example of the portable terminal 12. The portable terminal 12 includes an acquisition unit 121 and an output unit 122. The output unit 122 includes a display unit 1230. A storage unit (not shown) of the portable terminal 12 may store a customer ID and an identifier for identifying the portable terminal 12.

[0052] The acquisition unit 121 acquires the product ID of the product selected by the customer. The output unit 122 transmits a registration request including the product ID acquired by the acquisition unit 121 to the sales support system 11, and causes the sales support system 11 to register the product as a purchased product.

[0053] The acquisition unit 121 acquires the product ID of the purchased product by reading the product code attached to a product or the like through, for example, an imaging device (not shown). The imaging device is not particularly limited, but is, for example, a camera provided in the portable terminal 12. The product code is the JAN code or the like described above. The imaging device reads an encoded product code such as a barcode or a two-dimensional code. The acquisition unit 121 may acquire the product ID by identifying the product from the image of the product captured by the imaging device using an image recognition function, for example.

[0054] Further, the acquisition unit 121 may acquire the product ID by reading, through the imaging device, a pre-captured image of the product or an image of a picture of the product. Note that these images may include a product code.

[0055] Further, the acquisition unit 121 may acquire the product ID by reading, through a reading device, a tag to which an RFID (Radio Frequency Identifier) is attached. When using RFID, the reading device is an RFID reader.

[0056] Further, the acquisition unit 121 may acquire the product ID by receiving a selection of a product from the result of a product search. For example, the method of product search is not particularly limited. The product search may be performed by characters. The product search may be performed by an image. For example, the acquisition unit 121 may acquire the product ID by receiving a selection of a product to be purchased from the displayed image of the product.

[0057] Further, the acquisition unit 121 may acquire the product ID by receiving an input of a number such as a JAN code through an input device (not shown). Examples of the input device include a touch panel display and a keyboard capable of inputting numbers and characters.

[0058] The output unit 122 transmits the product ID acquired by the acquisition unit 121 to the sales support system 11. At this time, the output unit 122 also transmits to the sales support system 11 the customer ID or an identifier for identifying the portable terminal 12. The portable terminal 12 may receive from the sales support system 11 the name and price of the product corresponding to the transmitted product ID. At this time, the display unit 1230 displays the name and price of the product.

[0059] The portable terminal 12 receives a purchased product list from the sales support system 11. The display unit 1230 displays the purchased product list received from the sales support system 11. The display unit 1230 may display a notification that the price of the registered product has been updated.

[0060] Hereinafter, an operation example of the sales support system 11 and the portable terminal 12 according to the first embodiment will be described with reference to the drawings.

[0061] 1. Product registration process FIG. 3 is a flowchart showing an example of the registration process. The acquisition unit 121 of the portable terminal 12 acquires the product ID of the purchased product by reading the product code attached to the product or the like. The output unit 122 transmits a registration request including the product ID from the portable terminal 12 to the sales support system 11 (step S01). In addition to the product ID, the registration request may include a customer ID, the ID of the portable terminal 12, and the like.

[0062] FIG. 4 is a diagram showing an example of a product registration screen for reading a product code. The display unit 1230 of the portable terminal 12 displays a screen d050 for reading the product code. For example, the screen d050 has a reading portion d051, a display column d052 for displaying information on the read product, and a button d053 with "To Shopping Cart" displayed for displaying the purchased product list. When the product code of the imaged product is located in a predetermined area of the reading portion d051, the acquisition unit 121 acquires the product ID of the purchased product.

[0063] The sales support system 11 may refer to the product DB 115 and transmit the product information of the product with the acquired product ID to the portable terminal 12. In this case, the portable terminal 12 displays the received product information. For example, in FIG. 4, in the display column d052, the name of the product is "ZOO Biscuit" and the price of the product is 252 yen among the product information received by the portable terminal 12.

[0064] Returning to FIG. 3, the list generation unit 101 of the sales support system 11 adds the product included in the registration request to the customer's purchased product list (step S02). FIG. 5 is a diagram showing an example of product information stored in the product DB 115 referred to by the list generation unit 101. In FIG. 5, it is shown that the price of "ZOO Biscuit" is 252 yen at 14:34. The list generation unit 101 adds data of the product name "ZOO Biscuit", price "252 yen", and quantity "1 piece" to the purchased product list of a predetermined customer ID.

[0065] The list generation unit 101 transmits the purchased product list with the product added to the portable terminal 12. The portable terminal 12 displays the purchased product list with the product added (step S03).

[0066] FIG. 6 is a diagram showing an example of the screen of the purchased product list displayed on the portable terminal 12. The screen d060 includes, for example, a summary column d061 of the purchased product list, a detail column d062, a product addition button d064, and a payment button d065.

[0067] If the customer does not finish product registration (step S04: No), the sales support system 11 and the portable terminal 12 repeat the processes of steps S01 to S03. For example, on the screen of FIG. 6, when the product addition button d064 is pressed, the portable terminal 12 displays the product registration screen of FIG. 4 and acquires the product ID.

[0068] When payment is made, the portable terminal 12 ends the registration process and proceeds to the settlement process (step S04: Yes). For example, on the screen of FIG. 6, when the payment button d065 is pressed, the portable terminal 12 ends the product registration.

[0069] 2. Price Update Figure 7 is a flowchart showing an example of the price update process. The price update unit 102 determines whether the execution condition of the price update process is satisfied at an arbitrary timing (step S11). The price update unit 102 may execute the determination in step S11 at predetermined time intervals while the registration process in FIG. 3 is being executed.

[0070] When the execution condition is satisfied (step S12: Yes), the price update unit 102 executes the price update process. Specifically, the price update unit 102 checks the price in the product DB 115 (step S13). Hereinafter, the case where a product is further added to the purchased product list in FIG. 6 will be described as an example. When the price update unit 102 refers to the product DB 115 in FIG. 5 at 3:00 p.m., it is determined in FIG. 6 that the set price of the "ZOO Biscuit" registered does not match the price registered in the purchased product list.

[0071] When the set price has been changed (step S14: Yes), the price update unit 102 updates the price of the registered products included in the purchased product list to the new set price indicated by the product DB 115 (step S15). In FIG. 5, since the price has been changed, the price update unit 102 updates the price of "ZOO Biscuit" in the customer's purchased product list to 240 yen.

[0072] The price update unit 102 transmits the purchased product list in which the prices of the registered products have been updated to the portable terminal 12. Thus, the price update unit 102 ends the price update process. The portable terminal 12 displays the purchased product list in which the prices of the registered products have been updated (step S16).

[0073] In the flowchart of FIG. 7, when step S12: No, the price update unit 102 does not execute the price update process. Also, when step S14: No, the price update unit 102 ends the price update process without updating the price.

[0074] FIG. 8 is a diagram showing an example of a screen of a purchased item list with updated prices. In FIG. 8, after FIG. 6, the price of "ZOO Biscuits" has been updated from 252 yen to 240 yen.

[0075] The price update unit 102 may cause the portable terminal 12 to display a notification that the price has been updated. D063 in FIG. 8 is an example of a notification that the price has been updated. The notification D063 displays a message "The amount has been updated since scanning" in association with the item whose price has been updated. However, the example of the notification is not limited to this. The notification may include at least any one of the product name of the product whose price has been updated, the price before the update, and the amount of change in the price. Also, the notification may be displayed with different display forms such as color and blinking depending on whether the price has increased or decreased due to the update.

[0076] The display position of the notification is not limited to the position associated with the item. For example, it may be displayed in the summary column D061 of the purchased item list in FIG. 6. The notification may be popped up and displayed on any one of the product registration screen, the display screen of the purchased item list, or the payment screen.

[0077] The price update unit 102 may cause the portable terminal 12 to display a list of the items whose prices have been updated. The list may include at least any one of the product name of each item whose price has been updated, the price before the update of each item or the amount of change in the price, and the total amount of change.

[0078] The price update unit 102 may repeat the processes of step S11 to step S15 each time the execution condition is satisfied. Alternatively, the price update unit 102 may end the process after performing the process of step S15 once. For example, the price update unit 102 may be configured to perform the processes of step S11 to step S16 only once before the customer makes a payment. When step S12: No and step S14: No, the sales support system may end the process.

[0079] 3. Settlement FIG. 9A is a flowchart showing an example of a settlement process. When the registration process ends, the settlement process starts. For example, in the portable terminal 12, when a button for proceeding to a payment process, such as the payment button d065 in FIG. 6, is pressed, the settlement process may start.

[0080] When the settlement process starts, the portable terminal 12 transmits a settlement request to the sales support system 11 (step S21). The settlement information generation unit 103 generates settlement information based on the settlement request (step S22), and transmits the settlement information to the portable terminal 12. The settlement information includes, for example, the total payment amount for the registered products. The portable terminal 12 displays a payment screen (step S23). The payment screen may display the total quantity of the registered products, the total payment amount for the registered products, and the like. Further, the payment screen may display an execution button for the settlement process. The portable terminal 12 communicates with a settlement server (not shown) using settlement information such as a credit card, a debit card, or electronic money, and executes a settlement process (step S24). The portable terminal 12 transmits the completion of the settlement process to the sales support system 11. When receiving the completion of the settlement process, the settlement information generation unit 103 updates the sales DB 119 (step S25).

[0081] Thus, the description of the operation example of the sales support system 11 and the portable terminal 12 according to the first embodiment is completed.

[0082] According to an embodiment, the price update unit 102 updates the price of the registered products included in the purchased product list and registered using the portable terminal 12 by a customer operation. Further, when the execution condition of the price update process is satisfied, the price update unit 102 determines whether the price in the product DB 115 that stores the association between the product and the price has been changed. Therefore, when the price of the product is changed, the price of the registered products registered using the portable terminal 12 by a customer operation can be updated.

[0083] Also, according to one embodiment, the price update unit 102 transmits a purchase product list in which the prices of registered products have been updated to the portable terminal 12, and the portable terminal 12 displays the updated purchase product list. Therefore, the customer can check the updated price.

[0084] Also, according to one embodiment, the settlement information generation unit 103 generates settlement information based on the updated purchase product list. Therefore, the customer and the store can perform settlement based on the updated price.

[0085] (Modification example: Use of a settlement device) In the above operation example, the case where settlement is performed using the portable terminal 12 has been described, but settlement may be performed by any method. For example, settlement may be performed using a settlement device (not shown) instead of the portable terminal 12. The sales support system 11 transmits settlement information to the settlement device. The settlement device executes settlement processing by any method such as cash settlement or cashless settlement based on the settlement information.

[0086] The customer inputs a settlement code, which is information for identifying the settlement information, to the settlement device. The settlement code includes, but is not limited to, the identifier of the purchase product list or the identifier of the portable terminal 12. The settlement code may be the settlement information. In order to input the settlement code to the settlement device, the portable terminal 12 or other recording media such as a membership card may be used.

[0087] FIG. 9B is a flowchart showing another example of the settlement process. Similar to step S21 described above, the portable terminal 12 transmits a settlement request to the sales support system 11 (step S31). The settlement information generation unit 103 generates settlement information and a settlement code based on the settlement request from the portable terminal 12 (step S32).

[0088] The actuarial information generation unit 103 outputs an actuarial code to the portable terminal 12. The portable terminal 12 outputs the actuarial code and causes the actuarial device to read the actuarial code (step S33). The method of causing the actuarial device to read the actuarial code is not particularly limited. For example, the display unit 1230 may display a barcode or a two-dimensional code obtained by encoding the actuarial code. Alternatively, the output unit 122 may communicate with the actuarial device and cause the actuarial device to read the code. Specifically, the output unit 122 may transmit the actuarial code to the actuarial device by wireless communication such as NFC (Near Field Communication), Wi-Fi (registered trademark), or Bluetooth (registered trademark).

[0089] The actuarial device reads the actuarial code and acquires actuarial information corresponding to the actuarial code from the sales support system 11 (step S34). The actuarial device executes a settlement process based on the acquired actuarial information (step S35), and the sales support system 11 updates the sales DB 119 when receiving the completion of the settlement process (step S36).

[0090] The portable terminal 12 may transmit an actuarial request to the sales support system 11 when the actuarial code is read by the actuarial device. Note that the sales support system 11 does not necessarily need to generate the actuarial code. When the actuarial code is stored in the portable terminal 12 or another recording medium, the actuarial device reads the stored actuarial code using an arbitrary reader.

[0091] In FIG. 9B, the case where the portable terminal 12 transmits an actuarial request has been described, but the actuarial request may be transmitted by the actuarial device. For example, when the actuarial code is input, the actuarial device transmits an actuarial request to the sales support system 11.

[0092] FIG. 9C is a flowchart showing another example of the settlement process. The settlement process of FIG. 9C may start when a settlement code is input to the settlement device. First, the portable terminal 12 outputs a settlement code (step S41). This settlement code may be stored in the portable terminal 12 in advance. Alternatively, the settlement code may be transmitted from the sales support system 11 based on a request in response to the input of a button for starting the settlement process in the portable terminal 12. Also, in step S41, the portable terminal 12 may not be used by using another storage medium for storing the settlement code.

[0093] The settlement device reads the settlement code and transmits a settlement request to the sales support system 11 (step S42). The sales support system 11 generates settlement information based on the settlement request (step S43). The settlement device acquires the generated settlement information (step S44). Thereafter, the settlement device executes a payment process based on the settlement information (step S45), and the sales support system 11 updates the sales DB 119 (step S46).

[0094] (Modification Example: Price Update Button) In the first embodiment, the case where the execution condition of the price update process is that a new product is registered has been described as an example. However, the execution condition is not limited to this.

[0095] The execution condition may be, for example, that a price update button is pressed on the portable terminal 12. The product registration screen or the display screen of the purchased product list displayed on the portable terminal 12 may include a price update button.

[0096] FIG. 10 is a diagram showing an example of a price update button included in the display screen of the purchased product list. An explanation of "Update: Reflect the latest price" is displayed on the price update button d066 in FIG. 10. When the price update button is pressed by the customer, the price update unit 102 executes a price update process and determines, for example, whether the price stored in the product DB 115 has been changed.

[0097] According to the configuration for updating the price by the price update button, the sales support system 11 can present the updated price to the customer according to the customer's request.

[0098] (Modification example: Elapse of a predetermined time) Alternatively, the execution condition of the price update process may be a time condition.

[0099] The time condition may be that a predetermined time has elapsed during the registration process. The elapse of the predetermined time includes, for example, the elapse of a predetermined time since the start of the registration process, or the elapse of a predetermined time since the price update unit 102 once determines whether to refer to or change the price. The predetermined time can be arbitrarily determined, for example, between 1 minute and 1 hour.

[0100] Also, the time condition may include reaching a predetermined time such as 1 o'clock, 2 o'clock, or 3 o'clock.

[0101] When the time condition is satisfied, the price update unit 102 executes the price update process. Specifically, for example, when the price update unit 102 determines the elapse of a predetermined time, it determines whether the set price stored in the product DB 115 has been changed. If the set price has been changed, the price update unit 102 updates the price.

[0102] For example, by the price update unit 102 executing the price update process at a predetermined time interval such as every 10 minutes or every 1 hour, the process of determining whether the price of the purchased product list should be updated can be automatically started.

[0103] (Modification example: Update before payment) The execution condition of the price update process may be, for example, that the product registration process on the portable terminal 12 has been completed. Alternatively, the execution condition may be that the settlement process for the registered product has been started. Specifically, for example, on the screen of FIG. 6, when the payment button d065 is pressed, the price update unit 102 refers to the price.

[0104] Alternatively, the execution condition may be that the payment request is received from the portable terminal 12 or the payment device according to the modification example. When receiving the payment request from the portable terminal 12 or the payment device, for example, the price update unit 102 refers to the set price.

[0105] Alternatively, the execution condition may be that the payment code is read by the payment device. When receiving from the portable terminal 12 or the payment device that the payment code has been read, for example, the price update unit 102 refers to the price.

[0106] When the price update unit 102 updates the price, the payment information generation unit 103 generates payment information based on the updated price. The price of the registered product is paid in the portable terminal 12 or the payment device using the generated payment information. A notification that the price has been updated may be displayed on the screen related to the payment of the portable terminal 12 or the payment device.

[0107] Before payment, such as when the product registration process is completed or when the payment process is started, the price update unit 102 checks the price, so that the price of the purchased product list can be updated before the customer makes the payment.

[0108] (Modification example: Regarding the discount of products) The price of the product in the product DB 115 may include discount information regarding the discount of the product price. The discount information includes the discount amount from the price before the discount of the product or the discount at a predetermined rate. The discount information includes, for example, at least one of category-based discount information, bundle discount information, set discount information, total amount discount information, etc., but is not limited thereto.

[0109] The category-based discount information is discount information for products belonging to a specific category (such as frozen foods, etc.). For example, classification information indicating the category targeted for discount is associated with the discount amount. The bundle discount information is discount information given when purchasing a plurality of specific products. For example, the product targeted for discount (specifically, the product ID), the quantity thereof, and the discount amount are associated with each other. The set discount information is discount information for a specific combination of products. For example, the combination of products targeted for discount is associated with the discount rate. The total amount discount information is discount information that occurs when the total amount of purchased products is equal to or more than a predetermined amount. For example, the total amount targeted for discount is associated with the discount rate.

[0110] The list generation unit 101 refers to the discount information in the product DB 115 and reflects the discount in the purchased product list. When the execution condition of the price update process is satisfied, the price update unit 102 also refers to the discount information in the product DB 115 and updates the prices of the registered products.

[0111] The execution condition may be that the discount information stored in the product DB 115 has been changed. The price update unit 102 applies the discount to the registered products in the purchased product list based on the changed discount information. Note that it is also assumed that the discount once applied may become inapplicable due to the change in the discount information.

[0112] When the price update unit 102 executes the price update process when the discount information is changed, the discount can be applied to the registered products based on the new discount information.

[0113] (Modification example: Change in the price of the product DB 115) The execution condition of the price update process may be that the price of the product stored in the product DB 115 has been changed. When the price of the product is changed due to the change in the discount information, it is included in the fact that the price of the product has been changed.

[0114] The price update unit 102 may determine whether the price in the product DB 115 has been changed. Specifically, for example, the product DB 115 stores the time when the price was changed. The price update unit 102 may refer to the time when the price was changed and determine whether it is after the time when the previous price determination was made. If the time when the price was changed is later than the time of the previous determination, the price update unit 102 refers to the price in the product DB 115.

[0115] Alternatively, the price update unit 102 may receive a notification from the storage unit 114 that the price in the product DB 115 has been changed. Upon receiving the notification, the price update unit 102 refers to the changed set price and updates the prices of the registered products.

[0116] When the price update unit 102 executes the price update process when the price of the product stored in the product DB 115 is changed, the prices of the registered products can be updated.

[0117] (Modification example: Price maintenance) If the new set price stored in the product DB 115 is higher than the price registered in the purchased product list, the price update unit 102 may not update the prices of the products in the purchased product list. That is, the price update unit 102 may update the prices of the products whose new set prices stored in the product DB 115 are lower than the prices of the registered products included in the purchased product list. In this case, the price update unit 102 may include a determination unit that determines whether there are products whose prices increase due to the price update. The determination unit is an example of a determination means.

[0118] For the products determined to have a price increase, the price update unit 102 aborts the price update and maintains the prices shown in the purchased product list.

[0119] When the price increases, the price update unit 102 can prevent the customer from suffering disadvantages by maintaining the price. (Second Embodiment) Next, the sales support system 11 according to the second embodiment will be described. The sales support system 11 according to the second embodiment will describe the basic configuration of the first embodiment.

[0120] FIG. 11 is a block diagram showing the configuration of the sales support system 11 according to the second embodiment. The sales support system 11 according to the second embodiment includes a list generation unit 101 and a price update unit 102.

[0121] The sales support system 11 is connected through a network to a server having the functions of the settlement information generation unit 103 and the storage unit 114 according to the first embodiment. Further, the sales support system 11 communicates with a portable terminal operated by a customer through a network. Note that the sales support system 11 according to the second embodiment may include some or all of the functions of the sales support system 11 according to the first embodiment.

[0122] The list generation unit 101 generates a purchase product list including a product registered using a portable terminal by a customer's operation and a price based on a set price referred to for the registration of the product. The set price is stored, for example, in a storage unit (not shown) in association with information for identifying the product. The stored set price may be changed during registration of the product by the customer.

[0123] When the execution condition of the price update process is satisfied, the price update unit 102 updates the price of the registered product included in the purchase product list to a new set price.

[0124] In the second embodiment, the price update unit 102 may refer to the storage unit and determine whether the set price stored in the storage unit has been changed, as in the first embodiment. Alternatively, the price update unit 102 may receive a notification that the set price has been changed from another functional unit. Also, the price update unit 102 may receive the changed set price from another functional unit. The price update unit 102 may refer to the received set price and update the price of the purchase product list.

[0125] A plurality of execution conditions may be provided. In this case, the price update unit 102 updates the prices of the purchased item list when any one of the plurality of execution conditions is satisfied and the set price has been changed.

[0126] The generated and updated purchased item list is used for generating settlement information. The settlement method is arbitrarily determined.

[0127] FIG. 12 is a flowchart showing an operation example of the sales support system 11 according to the second embodiment.

[0128] The list generation unit 101 generates a purchased item list including the items registered using the portable terminal by the operation of the customer and the set prices referred to for the registration of the items (step S101).

[0129] The price update unit 102 updates the prices of the registered items included in the purchased item list on the condition that the execution condition is satisfied when the set price has been changed (step S102).

[0130] According to one embodiment, the price update unit 102 updates the prices of the registered items included in the purchased item list on the condition that the execution condition is satisfied when the set price has been changed. Therefore, when the price of an item has been changed, the prices of the registered items registered using the portable terminal by the operation of the customer can be updated.

[0131] [Hardware Configuration] In each of the above-described embodiments, each component of the sales support system 11 indicates a block of a functional unit. Part or all of each component of each device may be realized by any combination of a computer 500 and a program.

[0132] FIG. 13 is a block diagram showing an example of the hardware configuration of computer 500. Referring to FIG. 13, computer 500 includes, for example, a CPU (Central Processing Unit) 501, a ROM (Read Only Memory) 502, a RAM (Random Access Memory) 503, a program 504, a storage device 505, a drive device 507, a communication interface 508, an input device 509, an input / output interface 511, and a bus 512.

[0133] Program 504 includes instructions for realizing each function of each device. Program 504 is stored in advance in ROM 502, RAM 503, or storage device 505. By executing the instructions included in program 504, CPU 501 realizes each function of each device. For example, by the CPU 501 of sales support system 11 executing the instructions included in program 504, the functions of sales support system 11 are realized. Also, RAM 503 may store data processed in each function of each device. For example, product information or a purchased product list may be stored in RAM 503 of computer 500.

[0134] Drive device 507 reads and writes to recording medium 506. Communication interface 508 provides an interface with a communication network. Input device 509 is, for example, a mouse, a keyboard, etc., and accepts input of information from a store manager or the like. Output device 510 is, for example, a display, and outputs (displays) information to a store manager or the like. Input / output interface 511 provides an interface with peripheral devices. Bus 512 connects these hardware components. Note that program 504 may be supplied to CPU 501 via a communication network, or may be stored in advance in recording medium 506, read by drive device 507, and supplied to CPU 501.

[0135] Note that the hardware configuration shown in FIG. 13 is an example, and other components may be added, or some components may be omitted.

[0136] There are various modifications to the implementation methods of each device. For example, each device may be implemented by any combination of different computers and programs for each component. Also, a plurality of components included in each device may be implemented by any combination of one computer and a program.

[0137] Furthermore, some or all of each component of each device may be realized by general-purpose or dedicated circuitry (including a processor, etc.) or a combination thereof. These circuits may be constituted by a single chip or may be constituted by a plurality of chips connected via a bus. Some or all of each component of each device may be realized by a combination of the above-described circuitry, etc. and a program.

[0138] Also, when some or all of each component of each device are realized by a plurality of computers, circuitry, etc., the plurality of computers, circuitry, etc. may be centrally arranged or may be distributedly arranged.

[0139] Also, at least a part of the sales support system 11 may be provided in the form of SaaS (Software as a Service). That is, at least a part of the functions for realizing the sales support system 11 may be executed by software executed via a network.

[0140] As described above, the present disclosure has been described with reference to the embodiments, but the present disclosure is not limited to the above embodiments. Various changes that can be understood by those skilled in the art can be made to the configuration and details of the present disclosure within the scope of the present disclosure. Also, the configurations in each embodiment can be combined with each other as long as they do not deviate from the scope of the present disclosure.

[0141] Some or all of the above embodiments may be described as follows in the appended claims, but are not limited thereto.

[0142] [Appended Claim 1] List generation means for generating a purchase product list including products registered using a portable terminal by a customer's operation and a price based on the set price referred to for registration of the products; Update means for updating the price of the registered products included in the purchase product list to a new set price when the execution condition of the price update process is satisfied; A sales support system comprising:

[0143] [Appendix 2] The update means transmits the purchase product list in which the price of the registered product has been updated to the portable terminal. The sales support system according to Appendix 1.

[0144] [Appendix 3] Further comprising settlement information generation means for generating settlement information based on the updated purchase product list. The sales support system according to Appendix 1 or 2.

[0145] [Appendix 4] The update means causes the portable terminal to display a notification that the price of the registered product has been updated. The sales support system according to any one of Appendices 1 to 3.

[0146] [Appendix 5] The execution condition includes that one or more products have been registered using the portable terminal. The sales support system according to any one of Appendices 1 to 4.

[0147] [Appendix 6] The execution condition includes that the product registration process on the portable terminal has been completed. The sales support system according to any one of Appendices 1 to 5.

[0148] [Appendix 7] The execution condition includes that the settlement process for the registered product has been started. The sales support system according to any one of Appendices 1 to 5.

[0149] [Appendix 8] The execution conditions include that a price update button is pressed on the portable terminal. The sales support system according to any one of Appendices 1 to 7.

[0150] [Appendix 9] The execution conditions include time conditions. The sales support system according to any one of Appendices 1 to 8.

[0151] [Appendix 10] The execution conditions include that the set price has been changed. The sales support system according to any one of Appendices 1 to 9.

[0152] [Appendix 11] The update means further determines whether the execution conditions are satisfied. The sales support system according to any one of Appendices 1 to 10.

[0153] [Appendix 12] When the execution conditions are satisfied, the update means checks the set price in order to update the prices of the registered products included in the purchased product list. The sales support system according to any one of Appendices 1 to 11.

[0154] [Appendix 13] The update means checks whether the set price has been changed, and if the set price has been changed, updates the prices of the registered products. The sales support system according to Appendix 12.

[0155] [Appendix 14] The system further includes a determination means for determining whether there is a registered product whose new set price is higher than the price of the registered product. The update means aborts the update in which the price of the registered product increases. The sales support system according to any one of Appendices 1 to 13.

[0156] [Appendix 15] Generate a purchase product list including the product registered using a portable terminal by a customer's operation and the price based on the set price referred to for the registration of the product. When the execution condition of the price update process is satisfied, update the price of the registered product included in the purchase product list to a new set price. Sales support method.

[0157] [Appendix 16] A process of generating a purchase product list including the product registered using a portable terminal by a customer's operation and the price based on the set price referred to for the registration of the product. When the execution condition of the price update process is satisfied, a process of updating the price of the registered product included in the purchase product list to a new set price. A recording medium that non-temporarily records a sales support program for causing a computer to execute the above.

Explanation of Signs

[0158] 11 Sales support system 101 List generation unit 102 Price update unit 103 Settlement information generation unit 114 Storage unit 115 Product DB 116 Purchase product list DB 119 Sales DB 12 Portable terminal

Claims

1. a list generating means for generating a purchase list including products registered by a customer using a portable terminal by reading product codes in a store and prices based on set prices referenced when the products are registered; an update means for updating the prices of registered products included in the purchase product list to new set prices when a condition for executing a price update process is satisfied before the customer makes a payment, transmitting the purchase product list in which the set prices of the registered products have been updated to the portable terminal, and displaying a notification on the portable terminal that the prices of the registered products have been updated; A sales support system equipped with:

2. The execution condition includes that one or more products are registered using the portable terminal. The sales support system according to claim 1.

3. The execution condition includes that a product registration process in the portable terminal is completed. The sales support system according to claim 1 or 2.

4. The execution condition includes that a checkout process for the registered product has started. The sales support system according to any one of claims 1 to 3.

5. The execution condition includes pressing a price update button on the portable terminal. The sales support system according to any one of claims 1 to 4.

6. The execution condition includes that a predetermined time has elapsed since product registration was performed using the portable terminal. The sales support system according to any one of claims 1 to 5.

7. The device further includes a determination unit for determining whether or not there is a registered product whose new set price is higher than the price of the registered product, The update means executes an update in which the price of the registered product decreases. The sales support system according to any one of claims 1 to 6.

8. A purchase item list is generated, the purchase item list including the items registered by the customer using the portable terminal by reading the item code in the store and the prices based on the set prices referenced in the registration of the items; If a condition for executing a price update process is met before the customer's checkout, the price of the registered product included in the purchase product list is updated to a new set price; transmitting the purchased item list with the updated prices of the registered items to the portable terminal; displaying on the portable terminal a notice that the price of the registered product has been updated; Sales support methods.

9. A process of generating a purchase item list including items registered using a portable terminal by a customer reading item codes in a store and prices based on set prices referenced when the items were registered; If a condition for executing a price update process is met before the customer's checkout, the price of the registered product included in the purchase product list is updated to a new set price; transmitting the purchased item list with the updated prices of the registered items to the portable terminal; A process of displaying a notification that the price of the registered product has been updated on the portable terminal; A sales support program that causes a computer to execute the above.

Images