Patent ID: 12205153

EXAMPLE EMBODIMENT

Hereinafter, example embodiments of a sales support system, a method, a program, and a recording medium that non-transiently records the program according to the present disclosure will be described in detail with reference to the drawings. The present example embodiments do not limit the disclosed technology.

First Example Embodiment

FIG.1is a block diagram illustrating a configuration of a sales support system11according to a first example embodiment. For example, the sales support system11may be connected to a portable terminal12via a communication network13.

A customer acquires a product from a shelf or the like in a store, and registers the product using the portable terminal12. That is, the customer performs self-scan shopping using the portable terminal12.

The sales support system11is a server that manages various types of sales information such as a price, an inventory status, and sales information of a store related to a product that is sold in the store. The sales support system11may collectively manage sales information of a plurality of stores. Alternatively, the sales support system11may be located at for each store. The sales support system11may manage sales information of one store.

The sales support system11according to the first example embodiment includes a list generation unit101, a price updating unit102, an adjustment information generation unit103, and a storage unit114. The storage unit114includes a product database (DB)115, a purchase product list DB116, and a sales DB119. The list generation unit101, the price updating unit102, and the adjustment information generation unit103are examples of a list generation unit, an updating unit, and an adjustment information generation unit, respectively.

The portable terminal12is a terminal used by a customer. The portable terminal12is, for example, a portable terminal such as a smartphone or a tablet. The type of portable terminal12is not particularly limited. The portable terminal12may be owned by a customer or may be lent at a store. The portable terminal12may be mounted on a shopping basket or a shopping cart or may be integrated with the shopping basket or the shopping cart. A device that has functions of the portable terminal12is also referred to as a mobile terminal, a movable terminal, or a moving object. The moving object includes a robot. The moving object may be movable manually or automatically by including, for example, a movable portion such as a tire and a drive device such as a motor.

The list generation unit101generates a purchase product list related to a product registered using the portable terminal12. The purchase product list includes at least a product registered using the portable terminal12through an operation of the customer and a price based on a set price referred to in registration of the product.

Specifically, for example, the list generation unit101generates a purchase product list in which information for identifying a customer, product information of a product that the customer is planning to purchase, and a purchase quantity are associated with each other. The list generation unit101stores the generated purchase product list in the purchase product list DB116. A product included in the purchase product list and planned to be purchased by the customer is also referred to as a registered product.

The purchase product list is uniquely identified in accordance with the information for identifying a customer. The information for identifying the customer is, for example, a customer identifier (ID) for uniquely identifying a customer. For example, when a customer starts registering a product using the portable terminal12, the list generation unit101assigns a customer ID to the customer. When the process from start of a store entrance process or start of a registration process to end of adjustment is defined as one transaction, the customer ID may be assigned for each transaction.

The product information included in the purchase product list includes, for example, information such as a product name or a product ID with which a product can be identified. The product information of the purchase product list may include a price of the product obtained with reference to the product DB115as an example of the price based on the set price referred to in the registration of the product.

The list generation unit101generates a purchase product list based on a registration request from the portable terminal12. Specifically, the list generation unit101adds or deletes a product included in the purchase product list based on the product information included in the registration request. That is, the product which the customer plans to purchase is registered using the portable terminal12through an operation of the customer.

The list generation unit101may transmit the purchase product list in which the items are registered to the portable terminal12. When the purchase product list is transmitted, for example, the purchase product list is displayed on the portable terminal12, in such a way that the user can check the purchase product list.

The price stored in the product DB115may be changed during customer shopping. At least a case where the price is changed by the store manager or the sales support system11during business hours and a case where a time schedule is set in advance to the price stored in the product DB115are assumed as changes in the price, but the present disclosure is not limited thereto.

For example, in order for the store manager to adjust a sales volume and a profit rate of the product, the price may be changed based on the input of the store manager. The sales support system11may change the price based on, for example, a date, a day of week, a time, a target sales quantity, an inventory status, a best-before date of the product, an expiration date, and the like. When the time schedule is set, the price for each time period is stored for the product.

When an execution condition is satisfied, the price updating unit102performs a price updating process of updating the price of the registered product included in the purchase product list to a new set price. The execution condition of the price updating process is not particularly limited, but may be, for example, that one or more products are registered using the portable terminal12. That is, the price updating unit102may perform the price updating process whenever a predetermined number of products are newly registered. The price updating process will be described below.

The price updating unit102may determine whether the execution condition is satisfied. Specifically, for example, when the execution condition is registration of one new product using the portable terminal12, the price updating unit102determines whether the number of products in the purchase product list has increased from the previous determination. That is, in this case, the price updating unit102determines that the execution condition is satisfied when the number of products in the purchase product list increases from the previous determination.

Alternatively, instead of determining the execution condition, the price updating unit102may receive a notification indicating that the execution condition is satisfied. Specifically, when the execution condition is registration of one new product using the portable terminal12, the price updating unit102may receive a notification indicating that a product has been added from the list generation unit101. The price updating unit102may receive a notification indicating that the execution condition is satisfied other than from the list generation unit101.

As an example of the price updating process, when a predetermined execution condition is satisfied, the price updating unit102refers to the set price and updates the price included in the purchase product list based on the set price.

As an example of the price updating process, the price updating unit102may determine whether the set price has been changed when the predetermined execution condition is satisfied, and may update the price included in the purchase product list when the price has been changed. In order to determine whether the set price has been changed, the price updating unit102may determine whether the price of the product included in the purchase product list matches a price stored in the product DB115. Alternatively, the price updating unit102may determine whether the product DB115has been updated after the list generation unit101generates the list. Alternatively, the price updating unit102may determine whether the product DB115has been updated after a product is added to the list. The price updating unit102may determine whether the price has been changed by determining whether the product DB115has been updated since the previous determination.

When the price has been changed, the price updating unit102updates the price of the registered product included in the purchase product list to a new price. Specifically, the price updating unit102updates the price of the product in the purchase product list stored in the purchase product list DB116to a new set price indicated by the product DB115. In the present example embodiment, the price updating unit102may update the price to a lower price or a higher price. The price updating unit102may update the price with reference to the set price even when the set price has not changed.

The price updating unit102may transmit the purchase product list in which the price of the registered product has been updated to the portable terminal12. The price updating unit102may cause the portable terminal12to display a notification indicating that the price has been updated.

The adjustment information generation unit103generates adjustment information used for adjustment of the price based on the purchase product list. The adjustment information includes at least a total payment amount of the registered products included in the purchase product list. The adjustment information may further include a total quantity of registered products, a product name and a price of each registered product, and the like.

When the price updating unit102updates the price, the adjustment information generation unit103generates the adjustment information based on the updated purchase product list. The adjustment information generation unit103may transmit the adjustment information to the portable terminal12for adjustment or may transmit the adjustment information to an adjustment device installed in the store.

For example, the adjustment information generation unit103updates the sales DB119in accordance with the content of the adjustment.

The storage unit114stores, for example, data used for a process of each unit of the sales support system11.

The product DB115stores product information of products handled in a store or a chain store including a store. Specifically, the product DB115stores product information, for example, for each product. The product information stored in the product DB115includes a product ID, a product name, and a price of a product. The product ID is, for example, a product code (hereinafter referred to as a product code). The product code is, for example, a Japanese Article Number (JAN) code, a European Article Number (EAN) code, or a Universal Product Code (UPC). The product ID may be a product name. The price of the product may be a tax-excluded price of the product or a tax-included price.

The product DB115may further include, for example, information such as classification of a product, a feature of the product, and an inventory status of a product. The classification of the products is not particularly limited. For example, the classification of products may be broadly classified into, for example, food, stationery, and the like. The classification of the products may be classification of confectionery, meats, vegetables, or the like. The features of the products are not particularly limited. The features of the products may be a best-before date, a use-by date, a manufacturer name, a vendor name, or the like. The inventory status of the products may be an inventory quantity of the products or the like.

The product information may include information for identifying a product in addition to a product ID. For example, the product information may include image data of a product, or information of a feature amount obtained from the image data of the product.

The product DB115may include some or all of the above-described information regarding the product. The product DB115may include information other than the above-described information regarding the product.

The purchase product list DB116stores, for each customer, the latest purchase product list for which adjustment has not been completed. The member ID may be used as a customer ID with which the purchase product list is uniquely identified. The member ID is an ID with which a member registered in a service of a store is uniquely identified. Alternatively, the purchase product list DB116may store the customer ID and the member ID in association.

The purchase product list DB116may include a store entrance time which is a time when the customer executes the store entrance process. The store entrance process is, for example, a process of starting the above-described registration process. The purchase product list DB116may include a time at which a registration request of each product is received.

A price of the product is obtained from the product DB115based on the product ID of the purchase product list. The price indicated by the product DB115may be registered initially in the purchase product list when the product is registered. Alternatively, the price of the product DB115associated to a time at which the store entrance process is executed may be registered initially. The purchase product list DB116may store the tax-excluded price of the product calculated based on the tax-excluded price of the product acquired from the product DB115. The price initially registered in the purchase product list can be updated by the price updating unit102.

The purchase product list DB116may include all or part of the above-described information regarding the purchase product list. The purchase product list DB116may include information other than the above-described information regarding the purchase product list.

The sales DB119stores, for example, information regarding store sales for each store. For example, the sales DB119may manage information in accordance with each adjustment for each store. The sales DB119stores, for example, information of a store ID, an ID of the portable terminal12that has registered a product, a member ID of a user, a product ID of a purchased product, a purchase quantity, a selling price, and a purchase date and time in association. The store ID is an identifier for uniquely identifying the store.

The sales DB119may include all or part of the above-described information regarding sales. The sales DB119may include information other than the above-described information regarding sales.

For example, the sales DB119and the product DB115are associated with each other with a product ID. For example, the sales support system11may update the inventory status of the product DB115based on information regarding a purchase quantity registered in the sales DB119.

The sales support system11may not include some of the functional units such as the adjustment information generation unit103. The sales support system may include a functional unit (not illustrated).

A device configuration of sales support system11is not particularly limited. The sales support system11may be implemented by one device or may be implemented by different devices for each function or database (DB). Some functions of the sales support system11may be implemented by the portable terminal12. For example, at least one of the list generation unit101, the price updating unit102, and the adjustment information generation unit103may be implemented by the portable terminal12.

The sales support system11may be configured in a combination of servers such as a backbone server, a database server, a price look up (PLU) server, a point of sales (POS) server, and an application server. For example, the PLU server and the application server may be used to implement the list generation unit101. The server that manages the sales DB119may function as, for example, a database server. The server that displays a screen on the portable terminal12may be at least one of an application server, a POS server, or a backbone server. Each server passes information to be used for the assigned process via, for example, the communication network13or the like. However, names of the servers included in the sales support system11are not limited thereto. The sales support system11may not include some of these servers.

FIG.2is a block diagram illustrating a configuration example of the portable terminal12. The portable terminal12includes an acquisition unit121and an output unit122. The output unit122includes a display unit1230. A storage unit (not illustrated) of the portable terminal12may store a customer ID and an identifier for identifying the portable terminal12.

The acquisition unit121acquires a product ID of a product selected by a customer. The output unit122transmits a registration request including the product ID acquired by acquisition unit121to the sales support system11, and causes the sales support system11to register the product as a purchased product.

The acquisition unit121acquires the product ID of the purchased product by reading a product code attached to the product or the like via, for example, an imaging device (not illustrated). The imaging device is not particularly limited and is, for example, a camera included in the portable terminal12. The product code is the above-described JAN code or the like. The imaging device reads an encoded product code such as a barcode or a 2-dimensional code. For example, the acquisition unit121may acquire the product ID by identifying the product using the image recognition function from an image of the product captured by the imaging device.

The acquisition unit121may acquire the product ID by reading the image of the product or an image of a picture of the product captured in advance via the imaging device. These images may contain a product code.

The acquisition unit121may acquire the product ID by reading a tag to which a radio frequency identifier (RFID) is attached via a reading device. When the RFID is used, the reading device is an RFID reader.

The acquisition unit121may acquire the product ID by receiving a selection of a product from a result of product searching. For example, a method of searching for the product is not particularly limited. The product may be searched for with characters. The product may be searched for with an image. For example, the acquisition unit121may acquire the product ID by receiving a selection of a product to be purchased from the displayed image of the product.

The acquisition unit121may acquire the product ID by receiving an input of a number such as a JAN code via an input device (not illustrated). Examples of the input device include a touch panel display and a keyboard with which numbers and characters can be input.

The output unit122transmits the product ID acquired by acquisition unit121to the sales support system11. At this time, the output unit122also transmits the customer ID or the identifier for identifying the portable terminal12to the sales support system11. The portable terminal12may receive a name and a price of the product related to the transmitted product ID from the sales support system11. At this time, the display unit1230displays the name and price of the product.

The portable terminal12receives the purchase product list from the sales support system11. The display unit1230displays the purchase product list received from the sales support system11. The display unit1230may display a notification indicating that the price of the registered product has been updated.

Hereinafter, exemplary operations of the sales support system11and the portable terminal12according to the first example embodiment will be described with reference to the drawings.

1. Product Registration Process

FIG.3is a flowchart illustrating an example of a registration process. The acquisition unit121of the portable terminal12acquires a product ID of a purchased product by reading a product code attached to the product or the like. The output unit122causes the portable terminal12to transmit a registration request including the product ID to the sales support system11(step S01). In addition to the product ID, the registration request may include a customer ID and an ID of the portable terminal12.

FIG.4is a diagram illustrating an example of a product registration screen for reading a product code. The display unit1230of the portable terminal12displays a screen d050for reading the product code. For example, the screen d050includes a reading portion d051, a display field d052for displaying information regarding a read product, and a button d053for displaying “To shopping basket” for displaying a purchase product list. When the product code of the imaged product is located in a predetermined area of the reading portion d051, the acquisition unit121acquires the product ID of the purchased product. The sales support system11may transmit the product information of the product of which a product ID has been acquired to the portable terminal12with reference to the product DB115. In this case, the portable terminal12displays the received product information. For example, inFIG.4, in the display field d052, “ZOO biscuit” which is a name of the product and 252 yen which is a price of the product are displayed among the product information received by the portable terminal12.

Referring back toFIG.3, the list generation unit101of the sales support system11adds the product included in the registration request to the purchase product list of the customer (step S02).FIG.5is a diagram illustrating an example of the product information stored in the product DB115referred to by the list generation unit101.FIG.5illustrates the “ZOO biscuit” of which a price is 252 yen at 14:34. The list generation unit101adds data of a product name “ZOO biscuit”, a price of “252 yen”, and a quantity “1 item” to a purchase product list of a predetermined customer ID.

The list generation unit101transmits the purchase product list to which a product has been added to the portable terminal12. The portable terminal12displays the purchase product list to which the product has been added (step S03).

FIG.6is a diagram illustrating an example of a screen of a purchase product list displayed on the portable terminal12. A screen d060includes, for example, a summary field d061of the purchase product list, a detail field d062, a product addition button d064, and a payment button d065.

When the customer does not end the product registration (No in step S04), the sales support system11and the portable terminal12repeat the processes of steps S01to S03. For example, when the product addition button d064is pressed on the screen ofFIG.6, the portable terminal12displays the product registration screen ofFIG.4and acquires the product ID.

When payment is performed, the portable terminal12ends the registration process and causes the process to proceed to the adjustment process (Yes in step S04). For example, when the payment button d065is pressed on the screen ofFIG.6, the portable terminal12terminates the product registration.

2. Updating Price

FIG.7is a flowchart illustrating an example of the price updating process. The price updating unit102determines whether the execution condition of the price updating process is satisfied at any timing (step S11). The price updating unit102may execute the determination in step S11at predetermined time intervals while the registration process inFIG.3is being executed.

When the execution condition is satisfied (Yes in step S12), the price updating unit102executes the price updating process. Specifically, the price updating unit102checks the price in the product DB115(step S13). Hereinafter, a case where a product is further added to the purchase product list ofFIG.6will be described as an example. When the price updating unit102refers to the product DB115ofFIG.5at 3:00 PM, it is determined inFIG.6that the set price of the registered “ZOO biscuit” does not match the price registered in the purchase product list.

When the set price has been changed (Yes in step S14), the price updating unit102updates the price of the registered product included in the purchase product list to the new set price indicated by the product DB115(step S15). InFIG.5, since the price has been changed, the price updating unit102updates the price of the “ZOO biscuit” on the purchase product list of the customer to 240 yen.

The price updating unit102transmits the purchase product list in which the price of the registered product has been updated to the portable terminal12. The price updating unit102thus ends the price updating process.

The portable terminal12displays the purchase product list in which the price of the registered product has been updated (step S16).

In the flowchart ofFIG.7, in the case of No in step S12, the price updating unit102does not execute the price updating process. In the case of No in step S14, the price updating unit102ends the price updating process without updating the price.

FIG.8is a diagram illustrating an example of a screen of a purchase product list of which a price has been updated. InFIG.8, the price of the “ZOO biscuit” has been updated from 252 yen to 240 yen afterFIG.6.

The price updating unit102may cause the portable terminal12to display a notification indicating that the price has been updated. d063inFIG.8is an example of the notification indicating that the price has been updated. The notification d063displays a message “Amount of money has been updated since time of scanning” in association with the product of which the price has been updated. However, an example of the notification is not limited thereto. The notification may include at least one of a product name of the product of which the price has been updated, the price before the updating, and the amount of change in the price. The notification may be displayed in a different display form such as color or blinking depending on whether the price has increased or decreased due to the updating.

A display position of the notification is not limited to the position associated with the product, and may be displayed, for example, in the summary field d061of the purchase product list inFIG.6. The notification may be pop-up displayed on any of the product registration screen, the display screen of the purchase product list, and the payment screen.

The price updating unit102may cause the portable terminal12to display a list of products of which the prices have been updated. The list may include at least one of a product name of each product of which a price has been updated, a price of each product before updating or a change amount of the price, and a sum of the change amounts.

The price updating unit102may repeat the processes of steps S11to S15whenever the execution condition is satisfied. Alternatively, the price updating unit102may perform the process of step S15once and then end the process. For example, the price updating unit102may be configured to perform the processes of steps S11to S16only once before the customer performs payment. In the case of No in step S12and No in step S14, the sales support system may end the process.

3. Adjustment

FIG.9Ais a flowchart illustrating an example of an adjustment process. When the registration process is completed, the adjustment process is started. For example, in the portable terminal12, the adjustment process may be started when a button is pressed to proceed to the payment process such as the payment button d065inFIG.6.

When the adjustment process is started, the portable terminal12transmits an adjustment request to the sales support system11(step S21). The adjustment information generation unit103generates adjustment information based on the adjustment request (step S22), and transmits the adjustment information to the portable terminal12. The adjustment information includes, for example, a total payment amount of the registered products. The portable terminal12displays a payment screen (step S23). The payment screen may display a total quantity of registered products, a total payment amount of the registered products, and the like. The payment screen may display a settlement process execution button. The portable terminal12communicates with a settlement server (not illustrated) using settlement information such as a credit card, a debit card, or electronic money and executes the settlement process (step S24). The portable terminal12transmits completion of the settlement process to the sales support system11. When completion of the settlement process is received, the adjustment information generation unit103updates the sales DB119(step S25).

The operation examples of the sales support system11and the portable terminal12according to the first example embodiment have been described above.

According to an example embodiment, the price updating unit102updates a price of a registered product registered using the portable terminal12through an operation of a customer included in a purchase product list. When an execution condition of a price updating process is satisfied, the price updating unit102determines whether a price in the product DB115that stores a product and the price of the product in association has been changed. Accordingly, when the price of the product is changed, a price of the registered product registered using the portable terminal12can be updated through an operation of the customer.

According to an example embodiment, the price updating unit102transmits the purchase product list in which the price of the registered product has been updated to the portable terminal12, and the portable terminal12displays the updated purchase product list. Accordingly, the customer can check the updated price.

According to an example embodiment, the adjustment information generation unit103generates the adjustment information based on the updated purchase product list. Accordingly, the customer and the store can perform adjustment based on the updated price.

(Modification: Using Adjustment Device)

In the above operation example, the case where the adjustment is performed using the portable terminal12has been described, but the adjustment may be performed in accordance with any method. For example, the adjustment may be performed using an adjustment device (not illustrated) instead of the portable terminal12. The sales support system11transmits adjustment information to the adjustment device. The adjustment device executes a settlement process in accordance with any method such as cash settlement or cashless settlement based on the adjustment information.

The customer inputs an adjustment code which is information for specifying the adjustment information, to the adjustment device. The adjustment code includes, but is not limited to, an identifier of a purchase product list or an identifier of the portable terminal12. The adjustment code may be adjustment information. In order to input the adjustment code to the adjustment device, another recording medium such as the portable terminal12or a member card may be used.

FIG.9Bis a flowchart illustrating another example of the adjustment process. As in the above-described step S21, the portable terminal12transmits an adjustment request to the sales support system11(step S31). The adjustment information generation unit103generates adjustment information and an adjustment code based on the adjustment request from the portable terminal12(step S32).

The adjustment information generation unit103outputs the adjustment code to the portable terminal12. The portable terminal12outputs the adjustment code and causes the adjustment device to read the adjustment code (step S33). A method of causing the adjustment device to read the adjustment code is not particularly limited. For example, the display unit1230may display a barcode obtained by encoding an adjustment code or a two-dimensional code. Alternatively, the output unit122may communicate with the adjustment device and cause the adjustment device to read the code. Specifically, the output unit122may transmit the adjustment code to the adjustment device through wireless communication such as near field communication (NFC), Wi-Fi (registered trademark), or Bluetooth (registered trademark).

The adjustment device reads the adjustment code and acquires the adjustment information related to the adjustment code from the sales support system11(step S34). The adjustment device executes a settlement process based on the acquired adjustment information (step S35), and the sales support system11updates the sales DB119when a completion of the settlement process is received (step S36).

The portable terminal12may transmit an adjustment request to the sales support system11at a time point at which the adjustment code is read by the adjustment device. The sales support system11may not generate the adjustment code. When the adjustment code is stored in the portable terminal12or another recording medium, the adjustment device reads the stored adjustment code using any reader.

InFIG.9B, the case where the portable terminal12transmits the adjustment request has been described. However, the adjustment request may be transmitted by the adjustment device. For example, when the adjustment code is input, the adjustment device transmits an adjustment request to sales support system11.

FIG.9Cis a flowchart illustrating another example of the adjustment process. The adjustment process ofFIG.9Cmay be started when an adjustment code is input to the adjustment device. First, the portable terminal12outputs the adjustment code (step S41). This adjustment code may be stored in advance in the portable terminal12. Alternatively, the adjustment code may be transmitted from the sales support system11based on a request in response to an input of a button for starting an adjustment process in the portable terminal12. In step S41, the portable terminal12may not be used by using another storage medium that stores the adjustment code.

The adjustment device reads the adjustment code and transmits an adjustment request to the sales support system11(step S42). The sales support system11generates adjustment information based on the adjustment request (step S43). The adjustment device acquires the generated adjustment information (step S44). Thereafter, the adjustment device executes a settlement process based on the adjustment information (step S45), and the sales support system11updates the sales DB119(step S46).

(Modification: Price Updating Button)

In the first example embodiment, the case where the execution condition of the price updating process is that a new product is registered has been described as an example. However, the execution condition is not limited thereto.

The execution condition may be, for example, that the price updating button is pressed in the portable terminal12. The product registration screen or the display screen of the purchase product list displayed by the portable terminal12may include a price updating button.

FIG.10is a diagram illustrating an example of the price updating button included in the display screen of the purchase product list. A description of “update: reflection of latest price” is displayed on a price updating button d066inFIG.10. When a customer presses the price updating button, the price updating unit102executes a price updating process and determines, for example, whether the price stored in the product DB115has been changed.

According to the configuration in which the price is updated by the price updating button, the sales support system11can present the updated price to the customer in response to the request of the customer.

(Modification: Passing of Predetermined Time)

Alternatively, the execution condition of the price updating process may be a time condition.

The time condition may be that a predetermined time has passed during the registration process. The passing of the predetermined time includes, for example, passing of the predetermined time from start of the registration process, or passing of the predetermined time after the price updating unit102determines reference or change in the price once. The predetermined time is arbitrarily determined, for example, within a range of 1 minute to 1 hour.

The time condition may include reaching of a predetermined time such as 1:00, 2:00, and 3:00.

When the time condition is satisfied, the price updating unit102executes the price updating process. Specifically, for example, when it is determined that the predetermined time has passed, the price updating unit102determines whether the set price stored in the product DB115has been changed. When the set price has been changed, the price updating unit102updates the price.

For example, the price updating unit102executes the price updating process at predetermined time intervals such as every 10 minutes or every 1 hour, in such a way that the process of determining whether the price of the purchase product list is updated can be automatically started.

(Modification: Updating Before Payment)

The execution condition of the price updating process may be, for example, that the product registration process in the portable terminal12is completed. Alternatively, the execution condition may be that the adjustment process for the registered product is started. Specifically, for example, when the payment button d065is pressed on the screen ofFIG.6, the price updating unit102refers to the price.

The execution condition may be that an adjustment request is received from the portable terminal12or the adjustment device according to the modification. For example, when the adjustment request is received from the portable terminal12or the adjustment device, the price updating unit102refers to the set price.

Alternatively, the execution condition may be that the adjustment code is read by the adjustment device. For example, the price updating unit102receives that the adjustment code is read from the portable terminal12or the adjustment device to refer to the price.

When the price updating unit102updates the price, the adjustment information generation unit103generates the adjustment information based on the updated price. The price of the registered product is paid with the portable terminal12or the adjustment device using the generated adjustment information. A notification indicating that the price has been updated may be displayed on the screen related to payment of the portable terminal12or the adjustment device.

For example, when the product registration process is completed or when the adjustment process is started, the price updating unit102can update the price of the purchase product list before payment by the customer by checking the price before the payment.

(Modification: Discount of Product)

The price of the product in the product DB115may include discount information regarding a discount of the price of the product. The discount information includes a discount amount from the price before the discount of the product or discount at a predetermined rate. The discount information includes, for example, at least one of classified discount information, bundle discount information, set discount information, and total amount discount information, but is not limited thereto.

The classified discount information is information regarding discount of a product belonging to specific classification (for example, frozen food or the like). For example, classification information indicating classification that is a discount target and a discount amount are associated with each other. The bundle discount information is information regarding a discount allowed when a plurality of specific products is purchased. For example, products (specifically, product IDs) to be discounted, the number of products, and a discount amount are associated with each other. The set discount information is information regarding a discount of a specific combination of products. For example, a combination of products to be discounted and a discount rate are associated with each other. The total amount discount information is information regarding a discount offered when the total amount of the purchased products is equal to or more than a predetermined amount of money. For example, the total amount to be discounted and the discount rate are associated with each other.

The list generation unit101reflects the discount in the purchase product list with reference to the discount information in the product DB115. When the execution condition of the price updating process is satisfied, the price updating unit102also updates the price of the registered product with reference to the discount information in the product DB115.

The execution condition may be that the discount information stored in the product DB115has been changed. The price updating unit102applies the discount to the registered product in the purchase product list based on the changed discount information. A case where the discount applied once is not applied due to a change in the discount information is also assumed.

When the discount information is changed, the price updating unit102executes the price updating process, in such a way that the discount can be applied to the registered product based on the new discount information.

(Modification: Change in Price in Product DB115)

The execution condition of the price updating process may be that the price of the product stored in the product DB115has been changed. A case where the price of the product is changed due to the change in the discount information includes a case where the price of the product is changed.

The price updating unit102may determine whether the price of the product DB115has been changed. Specifically, for example, the product DB115stores a time at which the price has been changed. The price updating unit102may determine whether the time is later than a time when the previous price determination is performed with reference to the time when the price is changed. When the time at which the price is changed is later than the time of the previous determination, the price updating unit102refers to the price in the product DB115. Alternatively, the price updating unit102may receive a notification indicating that the price of the product DB115has been changed from the storage unit114. When the notification is received, the price updating unit102updates the price of the registered product with reference to the changed set price.

When the price of the product stored in the product DB115is changed, the price updating unit102can update the price of the registered product by executing the price updating process.

(Modification: Maintaining Price)

When a new set price stored in the product DB115is higher than the price registered in the purchase product list, the price updating unit102may not update the price of the product in the purchase product list. That is, the price updating unit102may update the price of the product of which the new set price stored in the product DB115is lower than the price of the registered product included in the purchase product list. In this case, the price updating unit102may include a determination unit that determines the presence or absence of a product of which a price rises due to the updating of the price. The determination unit is an example of a determination means.

The price updating unit102stops updating the price of the product of which the price is determined to rise, and maintains the price indicated in the purchase product list.

When the price rises, the price updating unit102maintains the price, and thus it is possible to prevent a disadvantage to the customer.

Second Example Embodiment

Next, a sales support system11according to a second example embodiment will be described. In the sales support system11according to a second example embodiment, the basic configuration of the first example embodiment will be described.

FIG.11is a block diagram illustrating a configuration of the sales support system11according to the second example embodiment. The sales support system11according to the second example embodiment includes a list generation unit101and a price updating unit102.

The sales support system11is connected to a server that has the functions of the adjustment information generation unit103and the storage unit114according to the first example embodiment via a network. The sales support system11communicates with a portable terminal operated by a customer through a network. The sales support system11according to the second example embodiment may include some or all of the functions of the sales support system11according to the first example embodiment.

The list generation unit101generates a purchase product list including products registered using the portable terminal through an operation of the customer and prices based on the set price referred to in registration of the product. The set prices are stored, for example, in a storage unit (not illustrated) in association with information for identifying the products. The stored set prices may be changed during the product registration by the customer.

When the execution condition of the price updating process is satisfied, the price updating unit102updates the price of the registered product included in the purchase product list to a new set price.

In the second example embodiment, as in the first example embodiment, the price updating unit102may determine whether the set price stored in the storage unit has been changed with reference to the storage unit. Alternatively, the price updating unit102may receive a notification indicating that the set price has been changed from another functional unit. The price updating unit102may receive the changed set price from another functional unit. The price updating unit102may update the price of the purchase product list with reference to the received set price.

A plurality of execution conditions may be provided. In this case, the price updating unit102updates the price of the purchase product list when any of the plurality of execution conditions is satisfied and the set price is changed.

The generated and updated purchase product list is used to generate adjustment information. The adjustment method is arbitrarily determined.

FIG.12is a flowchart illustrating an operation example of the sales support system11according to the second example embodiment. The list generation unit101generates a purchase product list including a product registered using the portable terminal through an operation of a customer and a set price referred to in registration of the product (step S101).

When the set price is changed, the price updating unit102updates the price of the registered product included in the purchase product list on condition that the execution condition is satisfied (step S102).

According to one example embodiment, when the set price is changed, the price updating unit102updates the price of the registered product included in the purchase product list on condition that the execution condition is satisfied. Accordingly, when the price of the product is changed, the price of the registered product registered using the portable terminal through the operation of the customer can be updated.

[Hardware Configuration]

In each of the above-described example embodiments, each constituent of the sales support system11indicates a functional unit block. Some or all of the constituents of each device may be implemented in any combination of a computer500and a program.

FIG.13is a block diagram illustrating an example of a hardware configuration of the computer500. Referring toFIG.13, the computer500includes, for example, a central processing unit (CPU)501, a read-only memory (ROM)502, a random access memory (RAM)503, a program504, a storage device505, a drive device507, a communication interface508, an input device509, an input/output interface511, and a bus512.

The program504includes instructions to implement each function of each device. The program504is stored in advance in the ROM502, the RAM503, or the storage device505. The CPU501implements each function of each device by executing the instructions included in the program504. For example, CPU501of the sales support system11implements the function of sales support system11by executing a command included in program504. The RAM503may store data to be processed in each function of each device. For example, product information or a purchase product list may be stored in the RAM503of the computer500.

The drive device507executes reading and writing from and on a recording medium506. The communication interface508provides an interface with a communication network. The input device509is, for example, a mouse, a keyboard, or the like, and receives an input of information from a store manager or the like. The output device510is, for example, a display and outputs (displays) information to the store manager or the like. The input/output interface511provides an interface with a peripheral device. The bus512connects the constituents of the hardware to each other. The program504may be supplied to the CPU501via a communication network or may be stored in the recording medium506in advance, read by the drive device507, and supplied to the CPU501.

The hardware configuration illustrated inFIG.13is exemplary, and other constituents may be added or some constituents may not be included.

There are various modifications of a method of implementing each device. For example, for each constituent, each device may be implemented in any combination of a different computer and a different program. A plurality of constituent units included in each device may be implemented in any combination of one computer and a program.

Some or all of the constituents of each device may be implemented by general-purpose or dedicated circuitry including a processor or the like, or a combination thereof. These circuits may be configured with a single chip or may be configured with a plurality of chips connected via a bus. Some or all of the constituents of each device may be implemented in a combination of the above-described circuit or the like and a program.

When some or all of the constituents of each device are implemented by a plurality of computers, circuits, and the like, the plurality of computers, circuits, and the like may be centralized or distributed.

At least a part of the sales support system11may be provided in a software as a service (SaaS) format. That is, at least some of the functions of implementing the sales support system11may be executed by software executed via a network.

Although the example embodiments of the present disclosure have been described above, the present disclosure is not limited to the example embodiments. For the configurations or the details of the present disclosure, various modifications that can be understood by those skilled in the art can be made within the scope of the present disclosure. The configurations in the example embodiments can be combined with each other without departing from the scope of the present disclosure.

Some or all of the above example embodiments can be described as the following supplementary notes, but are not limited to the following.

[Supplementary Note 1]

A sales support system includinga list generation means that generates a purchase product list including a product 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 product, andan updating means that updates a price of a registered product included in the purchase product list to a new set price when an execution condition of a price updating process is satisfied.
[Supplementary Note 2]

The sales support system according to Supplementary Note 1, in whichthe updating means transmits the purchase product list in which the price of the registered product is updated to the portable terminal.
[Supplementary Note 3]

The sales support system according to Supplementary Note 1 or 2, further includingan adjustment information generation means that generates adjustment information based on the updated purchase product list.
[Supplementary Note 4]

The sales support system according to any one of Supplementary Notes 1 to 3, in whichthe updating means causes the portable terminal to display a notification indicating that the price of the registered product has been updated.
[Supplementary Note 5]

The sales support system according to any one of Supplementary Notes 1 to 4, in whichthe execution condition includes registration of one or more products using the portable terminal.
[Supplementary Note 6]

The sales support system according to any one of Supplementary Notes 1 to 5, in whichthe execution condition includes completion of a product registration process in the portable terminal.
[Supplementary Note 7]

The sales support system according to any one of Supplementary Notes 1 to 5, in whichthe execution condition includes start of an adjustment process for the registered product.
[Supplementary Note 8]

The sales support system according to any one of Supplementary Notes 1 to 7, in whichthe execution condition includes a price updating button having been pressed on the portable terminal.
[Supplementary Note 9]

The sales support system according to any one of Supplementary Notes 1 to 8, in whichthe execution condition includes a time condition.
[Supplementary Note 10]

The sales support system according to any one of Supplementary Notes 1 to 9, in whichthe execution condition includes a change in the set price.
[Supplementary Note 11]

The sales support system according to any one of Supplementary Notes 1 to 10, in whichthe updating means further determines whether the execution condition is satisfied.
[Supplementary Note 12]

The sales support system according to any one of Supplementary Notes 1 to 11, in whichthe updating means checks the set price to update the price of the registered product included in the purchase product list when the execution condition is satisfied.
[Supplementary Note 13]

The sales support system according to Supplementary Note 12, in whichthe updating means checks whether the set price has been changed, and updates the price of the registered product when the set price has been changed.
[Supplementary Note 14]

The sales support system according to any one of Supplementary Notes 1 to 13, further includinga determination means that determines presence or absence of the registered product of which a new set price is higher than a price of the registered product, in whichthe updating means stops updating in which the price of the registered product rises.
[Supplementary Note 15]

A sales support method includinggenerating a purchase product list including a product 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 product, andupdating a price of a registered product included in the purchase product list to a new set price when an execution condition of a price updating process is satisfied.
[Supplementary Note 16]

A recording medium that non-transiently records a sales support program causing a computer to executea process of generating a purchase product list including a product 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 product, anda process of updating a price of a registered product included in the purchase product list to a new set price when an execution condition of a price updating process is satisfied.

REFERENCE SIGNS LIST

11Sales support system101List generation unit102Price updating unit103Adjustment information generation unit114Storage unit115Product DB116Purchase product list DB119Sales DB12Portable terminal