Information processing system, information processing method, and program

Abstract

To improve the efficiency of work in changing a commodity price in a store.SOLUTION: An information processing system includes a display device installed in a store that sells a commodity, and a server capable of communicating with the display device. The commodity has discount instruction information attached thereto, which is one of multiple different pieces of discount instruction information. The server includes: an instruction information determination unit which determines one or more pieces of discount instruction information attached to the commodity which is discount from a base price of the commodity, out of the multiple different pieces of discount instruction information; and a display control unit which causes the display device to display the one or more pieces of discount instruction information determined by the instruction information determination unit.SELECTED DRAWING: Figure 23

Description

Technical Field

[0001] The present invention relates to an information processing system, an information processing method, and a program.

Background Art

[0002] Conventionally, for example, in the retail industry, in order to give customers a sense of gain and enhance their purchasing desire, a label (markdown label) for markdown (price reduction) is attached to a product. Various printers configured to issue this markdown label have been proposed. For example, a printer has been proposed that includes a determination unit that determines to print a plurality of price data including regular price data and price data lower than the regular price, and a display unit that displays a notation indicating the regular price near the regular price data when the determination unit determines to print the plurality of price data (see, for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] <0​​On the other hand, if markdowns are not implemented, consumers will not be informed of the reduced prices, resulting in products nearing their expiration date remaining unsold and ultimately leading to food waste. Therefore, stores are currently unable to eliminate markdowns.

[0005] Therefore, the present invention aims to improve the efficiency of operations when changing product prices in stores. [Means for solving the problem]

[0006] One aspect of the present invention is an information processing system comprising a display device placed in a store that handles goods, and a server capable of communicating with the display device, wherein the goods are assigned one of a plurality of different discount instruction pieces of information, and the server comprises an instruction information determination unit that determines one or more discount instruction pieces of information from the plurality of different discount instruction pieces of information to be assigned to a product that is to be discounted relative to the standard price of the goods, and a display control unit that causes the one or more discount instruction pieces determined by the instruction information determination unit to be displayed on the display device. [Effects of the Invention]

[0007] According to one aspect of the present invention, it is possible to improve the efficiency of operations when changing product prices in a store. [Brief explanation of the drawing]

[0008] [Figure 1] This diagram schematically shows the system configuration of the price presentation system according to the first embodiment. [Figure 2] This diagram shows an example of screen transitions in a store application on a user's terminal. [Figure 3] This diagram shows an example of screen transitions in a store application on a user's terminal. [Figure 4] This is a block diagram showing the internal configuration of each device in the price presentation system of the first embodiment. [Figure 5] This figure shows an example of the data structure of a user database. [Figure 6] This figure shows an example of the data structure of a purchase history database. [Figure 7] This is a sequence chart showing the operation of the price presentation system of the first embodiment. [Figure 8] This is a sequence chart showing the operation of the price presentation system of the first embodiment. [Figure 9] This figure shows an example of the store application screen on a user terminal in the price display system of the second embodiment. [Figure 10] This figure shows an example of the data structure of the user database in the second embodiment. [Figure 11] This is a diagram illustrating the mechanism of the price presentation system in the third embodiment. [Figure 12] This figure illustrates a label issued in the price presentation system of the third embodiment. [Figure 13] This figure shows an example of the screen of the store application on a user terminal in a modified embodiment. [Figure 14] This figure shows an example of screen transitions in a store application on a user terminal in a modified embodiment. [Figure 15] This figure shows an example of screen transitions in a store application on a user terminal in a modified embodiment. [Figure 16] This figure shows an example of the screen of the store application on a user terminal in a modified embodiment. [Figure 17] This figure shows an example of screen transitions in a store application on a user terminal in a modified embodiment. [Figure 18] This figure shows an example of screen transitions in a store application on a user terminal in a modified embodiment. [Figure 19] This is a sequence chart showing the operation of a price presentation system according to a modified embodiment. [Figure 20] A modified example of the embodiment shows an example of screen transitions in the store application on the user terminal. [Figure 21]It is a diagram showing an example of the data configuration of a user database according to a modification of the embodiment. [Figure 22] It is a diagram showing an example of the data configuration of an allergen database according to a modification of the embodiment. [Figure 23] It is a diagram schematically showing the system configuration of a price presentation system according to a modification of the embodiment. [Figure 24] It is a diagram showing an example of the display of a markdown code in a price presentation system according to a modification of the embodiment.

Modes for Carrying Out the Invention

[0009] In the present disclosure, the "product information" of a product is information for identifying the product. For example, a product name, a product code, a product ID, a product model, etc. are examples of product information. The product ID is identification information for identifying the product. In the present disclosure, the "expiration information" of a product is information regarding an expiration date indicating an index as to whether a user can use, enjoy the taste of, or consume the product. Examples of the expiration date include a use-by date, a freshness date, a consumption date, a quality guarantee period, etc. In the present disclosure, the "reference price" of a product means the price of the product serving as a reference before a price change such as a price cut is made at a store. In the following description, the normal price is an example of the reference price.

[0010] In the present disclosure, the method for acquiring product information and expiration information from a product is not limited, and various methods can be adopted. For example, if code information corresponding to product information and expiration date information is displayed on the product, the product information and expiration date information can be obtained by reading the code information. Furthermore, if text information (human-readable characters) corresponding to product information and expiration date information is displayed on the product, an image containing the text information can be captured, and the text information can be obtained from the image using image recognition technology. Here, the forms in which code information or text information is displayed on a product include forms in which the code information or text information is printed on the product's packaging, and forms in which a printing medium such as a label with the code information or text information printed on it is affixed to the product itself or the product's packaging. The code information may be a one-dimensional code (barcode) or a two-dimensional code. The following explanation uses the example of obtaining product information and expiration date information by scanning the barcode displayed on the product.

[0011] (1) First Embodiment The following describes a price display system, which is an example of an information processing system. The price display system is configured to display the price of the product (offering price) to the customer on the customer's terminal. The user terminal is equipped with a store application that can communicate with the application server. The store application retrieves product information such as the product ID and expiration date information from the code displayed on the product and notifies the application server. Based on the information obtained from the store application, the application server determines the price at which to offer the product to the user and notifies the store application. The store application displays the price notified by the application server on the user terminal's display, thereby presenting the price to the user. In this system, the price presented to the user is determined by the application server, taking into account factors such as the product's expiration date, and then displayed to the user. As a result, store staff are freed from markdown tasks, making it possible to improve the efficiency of store operations.

[0012] (1-1) System Configuration The system configuration of the price presentation system 1 of this embodiment will be described with reference to Figure 1. As shown in Figure 1, the price presentation system 1 of this embodiment includes a user terminal 3 held by a user CT shopping at a store, an application server 5, and a payment processing server 7, and is configured to display the prices of products in the store to the user CT. In this embodiment, the store is a retail business such as a supermarket that handles products such as food with expiration dates. User terminal 3 has a store application installed that displays the prices of items in the store to the user CT when they make a purchase. User terminal 3 can communicate with application server 5 via a network NW. The network NW can be, for example, the internet, LAN (Local Area Network), or WAN (Wide Area Network).

[0013] The application server 5 is configured to perform predetermined processing in response to inquiries or requests from the store application and return the processing results to the store application. Predetermined processing includes, for example, determining a discounted price (an example of a offered price) to be offered to the user based on product information and expiration date information such as the best before date obtained from the product by the store application.

[0014] The payment processing server 7 can communicate with the application server 5 via the network NW and provides a service to process payments for products purchased by users CT within the store. If users CT do not make payments for products through the store application, the payment processing server 7 is not required in the price display system 1 of this embodiment.

[0015] (1-2) How to use the store application Next, we will explain how to use the store application on user terminal 3 with reference to Figures 2 and 3. Figures 2 and 3 show examples of screen transitions in the store application on user terminal 3. By running the store application, users can check the regular price and discounted price of each product in the store and make a payment for the products they have selected. Screens G1 to G3 in Figure 2 show how the store application is used when a user checks the price of a product and adds it to their shopping cart.

[0016] When a user launches the store application on the user terminal 3, the imaging function of the user terminal 3 is activated, as shown in screen G1 of Figure 2, and the captured image is displayed in window w1. Screen G1 shows an image of product P taken from the store shelf by the user, with the code information C1 displayed on product P visible, in window w1. By displaying the code information C1 of product P in window w1 (i.e., the user performs a scan operation), the store application reads (scans) the code information C1. When multiple code information is displayed in window w1, it is preferable that the imaging function of the user terminal 3 includes a function to display a scan area 100 in window w1 in order to ensure that the desired code information is reliably read. In that case, only the code information C1 displayed in the scan area 100 will be read from among the multiple code information in window w1.

[0017] For example, code information C1 includes the product ID of the corresponding product P (an example of product information) and expiration date information (an example of expiration date information). As long as the product ID and expiration date information are included, the code format of code information C1 is not specified, but if it is to be a barcode (one-dimensional code), then CODE128 such as GS1-128 can be used. Since CODE128 can convert all 128 ASCII characters into barcodes, it can be configured to include the product ID and expiration date information.

[0018] Furthermore, in order to affix labels containing GS1-128 to each product in the store, a batch automatic labeling system using labeling robots or the like may be used at the logistics center, or weighing labels containing GS1-128 may be affixed during the manufacturing of prepared foods and other items in the store. This makes it possible to affix labels with GS1-128 printed on them that include expiration date information, even to products that have codes printed on them that do not include expiration date information (for example, JAN13, etc.).

[0019] When the store application reads code information C1, it sends a query to the application server 5 regarding the discounted price of product P, including the product ID and expiration date information contained in code information C1. The application server 5 retrieves and displays the regular price and discounted price information for product P. Window w2 of screen G2, which is displayed following screen G1, contains information such as the product name corresponding to the product ID ("Yogurt B 500ml"), the regular price ("300 yen"), the discounted price ("250 yen"), and the expiration date ("September 13, 2020"). If product P for which code information C1 has been read is not a product subject to a discount, the application may display that the product is not subject to a discount, or display the date on which the product is scheduled to be subject to a discount. Window w2 may also include information on the discounted price and the discount rate (or fluctuation rate) from the regular price. Displaying the regular price and discount rate information in addition to the discounted price makes it easier to appeal to users about product discounts. The store application may not only display the reduced price on the screen, but also notify users through video output, audio output, etc. Information such as the reduced price and discount rate for discounted items may be displayed using, for example, augmented reality (AR). For example, the reduced price and discount rate information can be displayed in AR overlaid on the image of the product displayed on screen G2. By displaying the reduced price and discount rate information using AR, the price reduction can be more effectively communicated to users. Furthermore, if the store application has other products in the store with expiration dates closer to the expiration date of the product scanned by the user, it may display information about the product, such as its discounted price (i.e., an even lower discounted price than the scanned product), its location (e.g., shelf location), and the number of items in stock. The store application may also display discounted prices for purchasing multiple items (e.g., two) of products with approaching expiration dates (e.g., milk), or for purchasing a combination of different products with approaching expiration dates. This can encourage users to make purchases.

[0020] The discounted price displayed in window w2 reflects the expiration date included in the code information C1 of product P each time that code information C1 is read. As a result, store staff are freed from the task of marking down each product in the store.

[0021] The user can view the information in window w2 and choose whether or not to add product P to their shopping cart. If the user chooses to add product P to their shopping cart, they can operate button b1 ("Add to Cart"; an example of the first operation section) displayed on screen G2, which will display screen G3 and notify the user that product P has been added to their shopping cart (window w3). In this case, the user places the product P they have picked up into an actual shopping cart or basket in the store.

[0022] Screens G4-G6 in Figure 3 show how a user uses the store application to check their purchase list and make a payment for their items. After the user checks the discounted price of an item and adds it to their shopping list (i.e., after repeatedly viewing screens G1-G3), if they wish to proceed with payment, they operate button b2 ("View Cart") on screen G4 to display screen G5, which includes the shopping list BL. The shopping list BL contains a list of the items added so far (product name, quantity, price, etc. for each item) and the total price. The price of an item displayed on the shopping list BL is the discounted price if the item is subject to a price reduction, and the regular price if it is not. Although not shown in the diagram, if a user decides to cancel the purchase of a specific item from their purchase list (BL) due to exceeding their budget, they can remove that item from the BL. In this case, the user returns the item they are canceling to the store shelf from their shopping cart or basket.

[0023] On screen G5, once the purchase list BL is finalized, the user operates button b3 (payment button; an example of the second operation unit), causing the store application to send a payment request (or payment instruction) to application server 5, and the payment process is completed over the network as described later. Once the payment process is complete, the store application displays screen G6, which includes code information C2 as the paid code. The paid code indicates that payment for the goods has been completed and includes a payment ID (described later) that identifies the payment. Here, a 2D code is shown as an example of the paid code, but a barcode or the like may also be used.

[0024] The payment confirmation code is used to notify the store or store staff that payment for the items in your shopping cart has been completed. For example, the system could be configured so that customers can exit the store by showing a payment code to store staff, or so that a gate opens allowing customers to exit the store when they have a designated device inside the store read the payment code. In this case, customers do not need to wait in line at the register, and store cashiers do not need to process the payment, which is advantageous for both customers and stores. The system could be configured so that the cashier at the store scans the payment code with a scanner or similar device, allowing the customer to pass through the checkout. In this case, the cashier does not need to scan the code information of each individual item in the shopping basket, and the customer can pass through the checkout quickly, which is advantageous for both the customer and the store.

[0025] (1-3) Configuration of each device in the system Next, with reference to Figure 4, the configuration of each device within the price presentation system 1 of this embodiment will be described. Figure 4 is a block diagram including the internal configuration of the user terminal 3 and the application server 5 in the price presentation system 1 of this embodiment.

[0026] (1-3-1) User terminal 3 As shown in Figure 4, the user terminal 3 comprises a control unit 31, storage 32, operation input unit 33, display unit 34, imaging unit 35, code reader 36, and communication unit 37. The user terminal 3 may be a smartphone, tablet, smartwatch, or other wearable device. The control unit 31 is mainly composed of a microprocessor and controls the entire user terminal 3. For example, the microprocessor included in the control unit 31 loads and executes the store application program stored in the storage 32 and displays the execution result on the display unit 34. Storage 32 is non-volatile memory and may be an SSD (Solid State Drive) such as flash memory. Storage 32 stores the store application program, as well as data and files created by running the store application.

[0027] By executing the store application, the control unit 31 realizes the following functions: (1-i) A function to obtain product information, expiration date information, etc. of a product from code information displayed on the product, for example. (1-ii) A function that sends a price query to the application server 5 regarding information on the reduced price of a product to the user (i.e., requests information on the reduced price of a product). (1-iii) Function as a display control unit that receives (acquires) information on the reduced price of products from the application server 5 and displays the acquired information on the reduced price of products on the display unit 34. Furthermore, the display control unit is not limited to displaying information about price reductions; it also has the function of displaying various information on the display unit 34 by running a store application. Furthermore, the control unit 31 may either display the information on the reduced price of the product on the display unit 34, or display it on the display unit 34 and also provide a function to output the reduced price of the product as an audio signal. In that case, the user terminal 3 is equipped with an audio processing unit and a speaker.

[0028] The operation input unit 33 is, for example, a touch panel type input device provided on the display panel of the user terminal 3. The operation input unit 33 notifies the store application of operation inputs to the display panel. The display unit 34 includes, for example, a liquid crystal display panel or an organic EL panel, and displays the execution results of the store application. The display unit 34 also displays the digital image signal generated by the imaging unit 35. The imaging unit 35 includes, for example, an optical lens and an image sensor that converts incident light from the optical lens into an electrical signal, and sequentially generates digital images and outputs them to the display unit 34.

[0029] The code reader 36 analyzes the code information contained in the image signal generated by the imaging unit 35 and extracts (acquires) data from the code information, such as product information like product ID and expiration date information. The communication unit 37 is a communication interface for communicating with the application server 5.

[0030] (1-3-2) Application Server 5 As shown in Figure 4, the application server 5 comprises a control unit 51, storage 52, and a communication unit 53. The control unit 51 is mainly composed of a microprocessor and controls the entire application server 5. For example, the microprocessor included in the control unit 51 loads and executes the server program stored in the storage 52. Storage 52 is a large-capacity storage device such as an HDD (Hard Disk Drive), and stores the server program, as well as a user database (user DB) and a purchase history database (purchase history DB). The user database and purchase history database are accessed by the control unit 51 as needed when the server program is executed. The user database and purchase history database will be explained later with examples. Although not shown in the diagram, storage 52 stores data on the regular price of each product sold in the store (i.e., data on the regular price corresponding to each product ID). The regular price data is referenced by the control unit 51 when determining the discounted price. The communication unit 53 is a communication interface for communicating with the user terminal 3 and the payment processing server 7.

[0031] Figure 5 shows an example of the user database configuration. Each record in the user database illustrated in Figure 5 includes values ​​for the following fields: "User ID," "User Name," and "Payment Method." Here, the value of the "User ID" field is the identification information assigned to the user. The value of the "User Name" field is obtained based on the user's input when the user installs the store application on the user terminal 3 and recorded in the user database. The value of the "Payment Method" field is obtained based on the user's input when the user installs the store application on the user terminal 3, or at any time after installation, and recorded or updated in the user database. The value in the "Payment Method" field is data necessary for the user to pay for the product, such as credit card number information and / or information related to electronic money (prepaid number, etc.). The value in the "Payment Method" field is provided to the payment processing server 7 when the user corresponding to the user ID makes a payment.

[0032] Figure 6 shows an example of the configuration of the purchase history database. Each record in the purchase history database illustrated in Figure 6 contains values ​​for the following fields: "User ID," "Payment ID," "Payment Occurrence Date and Time," and "Purchase Details." Here, the value of the "Payment ID" field is data uniquely assigned to each individual payment of the corresponding user. The value of the "Payment Occurrence Date and Time" field indicates the date and time when the payment identified by the Payment ID occurred. The "Purchase Details" field includes the following subfields: "Product ID," "Product Name," "Price," and "Quantity." The values ​​in each subfield represent detailed data about the purchase subject to payment, identified by the payment ID. Furthermore, the store's POS system (not shown) can read data from the purchase history database, allowing it to aggregate sales data from transactions made using the store application and sales data from transactions made without using the store application.

[0033] By executing the server program, the control unit 51 realizes the functions of the price determination unit 511, the price information provision unit 512, and the settlement processing unit 513. The price determination unit 511 is a function that determines a discounted price by changing the regular price of a product based on at least one of the product ID and expiration date information obtained by the store application on the user terminal 3. For example, in order to eliminate unsold products, the discounted price will be lower the closer the expiration date is. Some products may be discounted regardless of their expiration date, in which case the discounted price will be determined based only on the product ID. The price determination unit 511 preferably calculates the price using a predetermined algorithm. The calculation of the discounted price of the product using the algorithm takes into account various information such as the product's expiration date, climate, location, inventory status, and past sales history. Artificial intelligence can also be used in such an algorithm.

[0034] The decision on a product's price reduction can be made from various perspectives. For example, the price determination unit 511 may determine the discounted price of a product based on at least one of the following: product ID, expiration date information, and user information. This allows for flexible determination of the discounted price according to the user's attributes. Here, user information includes, for example, the user's age, gender, and address. The store application obtains user information, for example, through user input operations, and sends the obtained user information to the application server 5. The application server 5 records the received user information, for example, in a user database. For example, if the user's age, as indicated by the user information, falls within the target age range for the product, a larger discount may be offered compared to users outside that range. Similarly, if the user's gender, as indicated by the user information, is male, a larger discount may be offered on men's products compared to female users.

[0035] The price determination unit 511 may determine the discounted price of a product based on the product ID and the closing time of the store selling the product. This increases the likelihood of selling out the product before the store closes. For example, the discounted price of a particular product may be lowered as the store approaches closing time. A particular product is one that the store wants to sell out of that day, such as bento boxes or prepared foods. The price determination unit 511 may determine the discounted price based on the product ID, the time the price inquiry was received from the store application (i.e., the time the user performed the product scanning operation), the store's closing time, and the remaining quantity of the product corresponding to that product ID in the store. This further increases the likelihood of selling out the products before the store closes. For example, the shorter the time between the price inquiry and the store's closing time, the lower the discounted price; and the larger the remaining quantity of the product, the larger the discount. Depending on the product, the relationship between the time the price inquiry was received, the store's closing time, and the discount, or the relationship between the remaining quantity of the product and the discount, may be varied. For products that the store absolutely wants to sell out, it is preferable to increase the discount.

[0036] The price information provision unit 512 is a function that provides information including the discounted price of a product determined by the price determination unit 511 to the user terminal 3. The price information provision unit 512 provides information including the discounted price of a product to, for example, the store application on the user terminal 3. For example, the information contained in screens G2 and G3 in Figure 2 is provided by the price information provision unit 512.

[0037] The payment processing unit 513 is a function that, in response to operation instructions (i.e., payment requests) from the payment button received from the user terminal 3, performs payment processing for items added to the purchase schedule list in cooperation with the payment processing server 7. The payment processing unit 513 reads user name and payment method data from the user database and provides it to the payment processing server 7. The payment processing unit 513 also creates a new record in the purchase history database when it receives a payment request from the store application.

[0038] (1-4) Operation of Price Display System 1 Next, the operation of the price display system 1 of this embodiment will be described with reference to Figures 7 and 8. Figure 7 is a sequence chart showing the operation of the price display system 1 when a user checks the price of a product and adds the product to their purchase list. Figure 8 is a sequence chart showing the operation of the price display system 1 when a user makes a payment for a product.

[0039] First, referring to Figure 7, for example, as shown in screen G1 of Figure 2, when a user picks up a product from the store shelf and displays the product's code information on the user terminal 3, the store application performs, for example, reading (scanning) the code information (step S2). This code information includes, for example, the product ID and expiration date information.

[0040] When the store application obtains the product ID and expiration date information from the product, it sends a price inquiry containing the product ID and expiration date information to the application server 5 (step S4). If the product corresponding to the product ID included in the received price inquiry is subject to a price reduction (step S6: YES), the application server 5 calculates the discounted price by changing the regular price of the product based on at least one of the product ID and expiration date information included in the price inquiry (step S8). If the product corresponding to the product ID included in the price inquiry is not subject to a price reduction, the price reduction will not be calculated (Step S6: NO). Next, the application server 5 returns price data and other information associated with the product ID to the store application (step S10). The price data for products subject to price reduction includes data on the regular price and the discounted price. The price data for products not subject to price reduction includes data on the regular price.

[0041] Upon receiving price data, the store application displays the regular price, discounted price, and expiration date information of the product on the user terminal 3, for example, as shown in screen G2 of Figure 2 (step S12). For example, when button b1 ("Add to Cart") is pressed on screen G2 in Figure 2 (Step S14: YES), the store application updates the purchase list to add the product displayed in Step S12 to the purchase list (Step S16).

[0042] Next, referring to Figure 8, for example, as shown in screen G5 of Figure 3, when a user operates the payment button (step S20: YES), the store application sends a payment request including the displayed purchase list to the application server 5 (step S22). When the application server 5 receives the payment request from the store application, it reads the user name and payment method data from the user database and sends a payment request including the read user name and payment method data and the payment amount (total amount of the purchase list) to the payment processing server 7 (step S24). The payment processing server 7 performs the payment processing based on the data provided by the application server 5 (step S26), and when the payment processing is completed, it sends a payment completion notification to the application server 5 (step S28). Once the payment is complete, the application server 5 issues a new payment ID (step S30) and updates the purchase history database by creating a new record in the purchase history database (step S32).

[0043] Next, the application server 5 sends a payment completion notification to the store application corresponding to the payment request in step S22 (step S34). This payment completion notification includes the payment ID issued in step S30. The store application creates a paid code, which is a two-dimensional code containing the payment ID included in the received payment completion notification (step S36), and displays it on the user terminal 3, for example, as shown in screen G6 in Figure 3 (step S38).

[0044] As described above, with the price display system 1 of this embodiment, users can recognize the discounted price of products using the user terminal 3 within the store. Specifically, the store application on the user terminal 3 obtains the product ID and expiration date information from the product code information and sends it to the application server 5. The application server 5 determines the discounted price based on the received product ID and expiration date information and returns the discounted price information to the store application. The store application displays the discounted price information received from the application server 5. Therefore, the price presentation system 1 of this embodiment can achieve the following effects.

[0045] (i) Stores can significantly reduce labor and personnel costs because store staff will no longer need to perform the markdown task of attaching labels with reduced prices to products as their expiration date approaches. In other words, it will be possible to improve the efficiency of store operations. If a product does not have a code information (e.g., GS1-128) that includes expiration date information, this code information can be attached through bulk labeling at a distribution center or by weighing and labeling products in stores. (ii) The application server 5 can optimally determine the discounted price of the products, making it possible to effectively prevent unsold products and product waste. (iii) The store can eliminate markdown operations and reduce the number of cashiers through cashless payments, allowing the store to pass on the savings in labor costs to customers using the store application in the form of discounts on products. (iv) By using the store application, customers can scan products themselves and complete the payment process, significantly reducing the waiting time at the checkout counter. In addition, since customers will have fewer opportunities to pass through the checkout counter, the opportunities for people to come into contact with each other in the store will be significantly reduced. (v) This will significantly reduce the waiting times for customers at the checkout counter, which is expected to improve customer satisfaction with the store and increase the frequency of customers visiting the store. (vi) In this embodiment, a method of reading code information was given as an example of how to obtain product ID and expiration date information from a product. This method is less expensive than methods that use wireless communication such as RFID or image recognition technology to obtain the information. (vii) Stores can offer larger discounts to customers who use the store application than to customers who do not. This flexibility in setting discounts cannot be achieved with conventional discount display methods, such as using electronic shelf labels.

[0046] (2) Second embodiment Next, the pricing system of the second embodiment will be described with reference to Figures 9 and 10. Note that the following descriptions of each embodiment will focus on the differences from the first embodiment. The price presentation system of this embodiment differs from the price presentation system 1 of the first embodiment in that the discounted price presented to the user may differ depending on the user status (an example of a category). User status can be set from various perspectives. For example, user status can be determined by the user's purchase history, user attributes (age, gender, whether or not they require care, etc.), and the user's history of soliciting other users. In this embodiment, the control unit 51 of the application server 5 functions as a mapping unit that associates users with one of several user statuses. The price determination unit 511 (see Figure 4) determines the discounted price of the product based on the user status associated by the mapping unit.

[0047] For example, consider a scenario where user statuses are categorized into Platinum, Gold, and Silver (with customer statuses in this order being considered more valuable). In this case, Figure 9 shows examples of discounted prices presented to users when their status is Gold (screen G7) and when their status is Platinum (screen G8). Screens G7 and G8 correspond to screen G2 in Figure 2, respectively. In the example in Figure 9, the discounted price for Platinum members ("180 yen") in window w2b of screen G8 is lower than the discounted price for Gold members ("200 yen") in window w2a of screen G7, indicating that Platinum members are given preferential treatment.

[0048] An example of the user database in this embodiment is shown in Figure 10. The user database in Figure 10 differs from the user database in the first embodiment (see Figure 5) in that a value for the "User Status" field has been added to each record. The value for the "User Status" field is data that indicates, for example, Platinum, Gold, Silver, etc. For example, when determining a user's status based on their purchase history, the control unit 51 of the application server 5 refers to the purchase history database (see Figure 6). Based on the purchase history database, the total amount of each user's purchase history is calculated, and by comparing the calculated total amount with a threshold corresponding to each user's status, the user status can be determined for each user. In the pricing system of this embodiment, the application server 5 determines the discounted price according to the user status. For example, if the discounted price calculated by the price determination unit 511 in the application server 5 of the first embodiment is the price for silver members, the discounted prices for gold members and platinum members can be set to a price that is reduced by a predetermined amount or a predetermined ratio from the discounted price for silver members.

[0049] According to the pricing system of this embodiment, the discounted prices offered to users can be flexibly set according to their user status. In particular, if user status is determined and updated based on the user's purchase history, it can encourage users to purchase products at stores. Furthermore, by giving preferential treatment to users with higher user status, it is possible to retain valuable customers.

[0050] (3) Third Embodiment Next, a price presentation system of a third embodiment will be described with reference to Figures 11 and 12. In the price display systems of the first and second embodiments, the system is configured so that users can recognize the discounted price by performing an operation to read the product code information themselves. However, if there is a mechanism that allows users to recognize in advance which products in the store are subject to discounts, they do not need to blindly perform an operation to read code information, and only need to perform an operation to read the code information of discounted products, which is convenient for users. From this perspective, in this embodiment, store staff issue labels (labels with markdown codes) that have a markdown code printed on them in advance to indicate whether or not a product is subject to a discount, and affix them to the product. Based on the markdown code on the label attached to the product, the user can recognize that the product is subject to a discount and then perform an operation to read the product code information printed on the label.

[0051] The pricing system of this embodiment includes a printer that prints different Markdown codes on labels to be affixed to at least two products with different expiration dates. In the pricing system of this embodiment, the application server 5 sends an instruction signal to the printer to print multiple labels with markdown codes, as illustrated in Figure 11. Based on this instruction signal, the printer prints and issues multiple labels with markdown codes.

[0052] Figure 11 illustrates examples of setting markdown codes to be printed on labels ("Label Issuance Example") and setting markdown codes for discounted items in stores ("Price Reduction Operation Example"), and these examples are explained below. Multiple Markdown codes are provided depending on the remaining time (e.g., number of days) until the product's expiration date. For example, Figure 11 shows an example where, on May 19, 2020, ten different Markdown codes (A-J) are assigned to products whose expiration date falls between today and nine days from that date (i.e., an example of printing and issuing labels with ten Markdown codes). In other words, on May 19, 2020, labels are issued and affixed to all products whose expiration date falls between today and nine days from that date. In this example, once the labels are affixed to products with an expiration date of nine days from that date, there is no need to issue any other labels, such as Markdown labels. In this case, Figure 12 shows an example of a label PL issued for product P, which has an expiration date of May 20, 2020. Figure 12 shows an example of a weighing label PL affixed to product P, and the markdown code display section 103 of the label PL has the markdown code "B" printed on it.

[0053] In Figure 11, the markdown codes for discounted items change, for example, according to the passage of time, and are notified to customers in-store, within the store, or through the store application. The markdown codes for items discounted on a given day may be handwritten by store staff on a board in the store or displayed on an electronic shelf label. The Markdown codes for items subject to price reductions on that day may be displayed when the store application is launched. In this case, the store application receives and displays the day's Markdown codes from the application server 5 upon startup. In the example in Figure 11, on May 19, 2020, the items eligible for price reductions in the store were those with labels printed with the markdown code "A" or "B". Similarly, on May 20, 2020, the items eligible for price reductions were those with labels printed with the markdown code "B" or "C". The same applies from May 21 to May 28, 2020. In other words, in the price reduction example shown in Figure 11, products whose expiration date is on the same day or the next day are designated as products subject to price reduction.

[0054] For example, a customer who visited the store on May 25, 2020, would be notified via the storefront, in-store, or through the store application that the Markdown Code for that day is "G" or "H". The customer would then know that products in the store with labels printed with the Markdown Code "G" or "H" are the discounted items for that day. Therefore, the customer only needs to scan the code information of the discounted items in the store, improving customer convenience. Furthermore, setting a Markdown Code provides an incentive for customers to proactively scan products in the store. In other words, by scanning the code information of discounted items with labels printed with the Markdown Code, the customer can use the user terminal 3 to recognize the discounted price of the product according to its expiration date, etc., similar to the first and second embodiments. On the other hand, since store staff do not need to attach markdown labels to products once the labels have been attached, it becomes possible to improve the efficiency of store operations, similar to the first and second embodiments.

[0055] Note that while Figure 11 shows 10 types of Markdown codes, this is not the only option. The number of Markdown codes will be determined as appropriate according to the store's operations. In Figure 11, different Markdown codes are assigned to different expiration dates, but this is not required. The same Markdown code may be assigned to different expiration dates. For example, in the example in Figure 11, the Markdown code assigned to May 19th to May 21st could be "A", and the Markdown code assigned to May 22nd to May 24th could be "B". Markdown code is an example of discount instruction information. Discount instruction information is not limited to letters such as "A" to "J," but may also include symbols, codes, marks, emblems, designs, etc.

[0056] Markdown codes do not have to be switched on a daily basis; they can also be switched on an hourly basis. For example, for products that are manufactured multiple times a day, such as prepared foods and bento boxes, the markdown codes can be switched multiple times within a single day. For instance, if products are manufactured three times a day at 8:00, 12:00, and 16:00, and the markdown codes printed on the labels attached to the products are "A," "B," and "C," and the products manufactured at 8:00 have an expiration date of 16:00 on the same day, and the products manufactured at 12:00 have an expiration date of 20:00 on the same day. In this case, for example, the markdown code for discounted products could be set to "A" between 12:00 and 16:00, and the markdown code for discounted products could be set to "B" between 16:00 and 20:00. By switching markdown codes on an hourly basis in this way, store employees no longer need to frequently attach markdown labels to products with short expiration dates, significantly improving operational efficiency.

[0057] (4) Modified examples of embodiments Next, a price presentation system relating to a modified embodiment will be described.

[0058] (4-1) First variation The first variation will be explained below. In the first and second embodiments, the case in which the application server 5 determines the discounted price of a product was described, but the price determination unit 511 of the application server 5 may also determine the start time of the discounted price. Information indicating the start time of the determined discounted price is transmitted from the application server 5 to the store application and displayed on the display unit 34 of the user terminal 3. In other words, the control unit 31 of the user terminal 3 may function as a display control unit that causes the display unit 34 to display information indicating the start time of the discounted price of a product.

[0059] In this modified example, the price determination unit 511 of the application server 5 determines the start time of the price reduction for the product based on the closing time of the store selling the product and the remaining quantity of the product. For example, the start time for price reductions on products may be set a predetermined time before the store's closing time. In this case, it is preferable to make the predetermined time longer the more products remain (unsold quantity). In other words, if there are many products remaining, starting the reduction earlier increases the likelihood of selling all the products before closing time.

[0060] Furthermore, in the second embodiment, the start time for price reductions on a certain product may be earlier for users with higher user statuses than for users with lower user statuses. For example, the start time for price reductions may be changed to: Platinum members: 3 PM today, Gold members: 4 PM today, Silver members: 5 PM today. The timing at which the store application notifies users of the start time for price reductions is, for example, when screen G7 or screen G8 in Figure 9 is displayed, but is not limited to this. For example, when the store notifies users (members) of price reductions on products, the store may notify users in advance of the price reductions and start times for each customer status. Furthermore, regardless of the user's status, the start time of the discounted price for each user status may be displayed. This would give users with relatively higher user statuses a sense of superiority, as they would be offered the discounted price earlier than others, thus motivating them to return to the store. On the other hand, the store would benefit from being able to retain users with higher user statuses. The duration for which discounted prices are offered may vary depending on the user's status. For example, Platinum members could receive a discount for 3 hours, Gold members for 2 hours, and Silver members for 1 hour. This also allows users with higher status levels to be given preferential treatment over users with lower status levels.

[0061] (4-2) Second variation Next, a second modified example will be described with reference to Figures 13 and 14. In this modified version, when the reduced price of a product is presented to the user, related information about that product is also displayed. Screen G9, illustrated in Figure 13, is a screen where the store application displays the discounted price to the user terminal 3, similar to screen G2 in Figure 2. In addition to the product name, regular price, discounted price, and expiration date information, window w9 of screen G9 displays link information 104 indicating the place of origin and producer information of the product as related information. In this example, the user can access a webpage containing the place of origin and producer information of the product by manipulating the link information 104. Therefore, the user can check the safety of the product before adding it to their purchase list.

[0062] Screen G10, illustrated in Figure 14, is a screen where the store application displays the discounted price to the user, similar to screen G2 in Figure 2. In window w10 of screen G10, in addition to information such as the product name, regular price, discounted price, and expiration date, a menu list ML of dishes that use the product is displayed as related information. A scroll bar 101 may be provided in the menu list ML to display many menus. Because the menu list ML is displayed, the user can consider how to use the product in question. Therefore, the user can obtain useful information in a timely manner to decide whether or not to include the product displayed in window w10 in their shopping cart, which leads to improved customer satisfaction and increased willingness to visit the store again.

[0063] When a user selects one dish from the menu list ML in window w10 (in the example in Figure 14, "Qingjiao Rousi"), screen G11 is displayed on user terminal 3. Window w11 on screen G11 displays a list of ingredients needed to prepare the selected dish. If the required ingredients include discounted items, information indicating that they are discounted items (the string "Discounted" in the example of screen G11 in Figure 14) may be displayed. This allows the store to encourage users to purchase additional items. It also benefits the user, as they can see which dishes on the menu list ML can be prepared with inexpensive ingredients. When displaying screen G11, the store application may query the application server 5 to determine whether or not each food item is eligible for a price reduction.

[0064] (4-3) Third variation Next, a third modified example will be explained with reference to Figure 15. In this modified version, the store application has a function to manage the user's home inventory. In this modified example, for instance, the storage 32 of the user terminal 3 stores a database of products in the user's home inventory. The store application adds data for each product included in the purchase list to the home inventory database each time payment for a product on the purchase list is completed. When a product is consumed or discarded by the user, the store application deletes the selected product from the home inventory database based on, for example, an action by the user. In this modified example, the user's home inventory database may be stored, for example, on the application server 5.

[0065] Referring to Figure 15, an example of how the store application can be used when managing home inventory is shown. In this modified example, as shown in screen G12 of Figure 15, a button b4 ("Home Inventory") is added to the store application. When button b4 is operated, screen G13, which includes the Home Inventory List HL, is displayed. The Home Inventory List HL is a list of products that reflect the home inventory database. If the products included in the Home Inventory List HL cannot be displayed on one screen, all products can be viewed using the scroll bar 102. When a user consumes or discards a product at home, they can delete the corresponding product from the Home Inventory List HL (i.e., delete it from the home inventory database) by operating button b5 ("Delete"), etc.

[0066] This modified version allows users to visualize how many products in their homes are nearing their expiration date, thus contributing to reducing food waste at home. Furthermore, since data obtained from users scanning products in stores is reflected in their home inventory database, the effort required to create a home inventory database is virtually eliminated.

[0067] Furthermore, if a household budget management application is installed on user terminal 3, the store application may be linked with the household budget management application. In this case, the store application will provide the household budget management application with data for each item included in the purchase list each time payment for an item on the purchase list is completed. Since the data for each item on the purchase list includes the purchase price, the household budget management application can perform household budget management based on the data for each item provided by the store application. In this case as well, the effort required of the user to input the data of purchased items and their prices into the household budget management application can be saved.

[0068] (4-4) Fourth variation Next, we will explain the fourth modified example. The price display system 1 of the first embodiment is a system in which a user scans an item in a store, places the item in a basket or shopping cart, and completes the payment for the item cashless. However, with this system, it is also possible for a user to place the item in their own bag, for example, without scanning it, and leave the store. An additional mechanism to prevent such shoplifting will be described as the fourth modification.

[0069] In this modified example, one or more surveillance cameras are installed inside the store. Each surveillance camera sequentially acquires images from a fixed point inside the store and transmits them to a computer device connected to each camera. The computer device is configured to perform image analysis using artificial intelligence to detect suspicious behavior by customers.

[0070] While computer devices can detect suspicious user behavior from images, they cannot identify the user who performed the suspicious behavior. Therefore, wireless tags that periodically emit beacon signals are attached to each shopping cart in the store, and receivers that receive the beacon signals are installed, for example, on the ceiling of the store. The communication protocol between the wireless tags and the receivers is not limited, but for example, Bluetooth® Low Energy (BLE) can be used. The receiver calculates the arrival angle of the beacon signal and notifies the computer device of the arrival angle data. Based on the received arrival angle data, the computer device identifies the location (coordinates) of each shopping cart in the store in real time.

[0071] The computer system can identify users who have engaged in suspicious behavior by matching the detection results of suspicious user behavior (time, coordinates of fixed points) with the location information of each shopping cart within the store according to the time. If a user who has engaged in suspicious behavior is identified, the computer system outputs an alert notification (display output or audio output) so that store staff can be aware of it. If an alert notification is issued, it is preferable to conduct a random check as customers leave the store in order to indirectly deter shoplifting. In a random check, for example, a store staff member would visually check the reusable bag of one randomly selected customer out of 10. By conducting a random check, it is expected that customers who have shoplifted will voluntarily return any unpaid items to the shelves before leaving the store.

[0072] (4-5) Fifth variation Next, I will explain the fifth variation. In the embodiments described above, the method for obtaining product ID and expiration date information from a product was described as reading the product's code information, but this is not the only method. Another method for obtaining product IDs and expiration date information from products is to receive product IDs and expiration date information from wireless tags attached to the product, shelf labels, or product packaging, or from wireless tags placed near the product. In this case, the communication method used to receive the information (e.g., communication protocol, frequency used) is not specified. Examples of communication methods include RFID (Radio Frequency Identification) such as NFC (Near Field Communication) and Bluetooth (registered trademark). For example, consider a scenario where an NFC tag containing the product ID and expiration date information is attached to a product or shelf label, and the user terminal 3 is equipped with an NFC reader. In this case, when the user brings their user terminal 3 close to the product, the NFC reader on the user terminal 3 receives the product ID and expiration date information from the product's NFC tag. The store application on the user terminal 3 sends a price inquiry, including the received product ID and expiration date information, to the application server 5. Upon receiving the price inquiry, the application server 5 determines the discounted price of the product, similar to the embodiment described above, and returns information indicating the discounted price to the store application. The store application on user terminal 3 may, for example, if RFID tags or BLE tags are attached to products or shelf labels, acquire identification information from the product, query the application server 5 for the product's price including its expiration date, and display information indicating the discounted price. This eliminates the need to store the expiration date information of products corresponding to RFID tags or BLE tags, and allows the application server 5 to centrally manage the expiration date information for each product.

[0073] The product ID of a product can also be identified from an image of the product's appearance. For example, if the user terminal 3 has an imaging unit, the store application sends an image of the product acquired by the imaging unit to the application server 5. The application server 5 identifies the product ID of the product from the acquired image. Artificial intelligence using a trained model can be used to identify the product ID. In this case, the product image is an example of product information. At this time, the application server 5 can be configured to access a database where product IDs and product expiration date information are associated, and to obtain the expiration date information corresponding to the identified product ID. Multiple pieces of information obtained from a product may be combined to obtain the product ID and expiration date information of that product. For example, the product ID and expiration date information of a product can be obtained by combining at least two pieces of information from among code information obtained from the product or shelf label, text information, information obtained from wireless tags, and images of the product's appearance.

[0074] (4-6) Sixth Variation Next, we will explain the sixth variation. The sixth variation is an example in which, after checking the price of a product using the store application, payment is made at a regular or self-checkout counter in the store using a user code issued by the store application that is associated with the price of the products on the purchase list. The seventh variation, which will be described later, is an example in which only the price check is performed using the store application. The above-described embodiment explains the case where the user scans the product using the user terminal 3 and makes a payment (i.e., performs self-checkout), but this is not the only case. The user can also scan the product using the user terminal 3 to confirm the price of the product and then make a payment for the product at a regular cash register (manned register) or self-checkout register (unmanned register) in the store. A standard cash register refers to a register terminal where a store employee reads the product codes of the items the customer intends to purchase using a code reader, and then the total amount of the items is paid in cash or by credit card based on the employee's instructions. A self-checkout register refers to a register terminal where the customer either reads the product codes of the items they intend to purchase using a code reader themselves, or has them read by a batch reading device, and then the total amount of the items is paid in cash or by credit card based on the customer's instructions. In essence, it refers to a register terminal where payment can be completed without any operation by a store employee.

[0075] Examples of the store application screen on the user terminal in this modified case are shown in Figures 16 and 17. Figure 16 shows an example of a screen displayed after launching the store application in this modified example. Screen G0 in Figure 16 includes a button b11 for self-checkout and a price checker button b12 for checking the price of the product. When the user operates button b11, the screen transitions to screen G1 in Figure 2, and self-checkout becomes possible as described in the first and second embodiments. On the other hand, if the user operates button b12 on screen G0 in Figure 16, the user can check the price of the product and obtain a user code that is necessary when purchasing the product at that price at a regular register or self-checkout. The user code may be a code associated with the user ID (see Figure 6), or a code associated with the membership number assigned to the user on a store's point card, membership card, etc.

[0076] When a user operates button b12 on screen G0, as shown on screens G21 and G22 in Figure 17, the code information C1 is read (scanned) from the product image displayed in window w1, similar to screens G1 and G2 in Figure 2. This allows the user to view the discounted price and expiration date information for each user, as described above. Screen G22 includes buttons b1 and b2 from screen G2 (see Figure 2), as well as button b13 for issuing a user code. When button b13 is operated on screen G22, user code C3 is displayed as shown on screen G23. User code C3 is read by a code reader located at regular registers and self-checkout counters. At regular registers, the user presents user code C3 to the cashier, who then uses a code reader to read only user code C3, and the discounted price displayed on screen G22 is used to process the payment for the goods. At this time, the register terminal queries the application server 5 based on user code C3 read from the code reader to obtain information on the discounted price provided to the user. The process is similar at self-checkout counters, where the user themselves reads only user code C3 using the code reader connected to the self-checkout counter, instead of a cashier.

[0077] If button b2 is pressed on screen G22, for example, screen G5a in Figure 18 will be displayed. Screen G5a contains the same display content as screen G5 in Figure 3, but differs in that it includes button b14 ("Issue Code") instead of button b3. When button b14 is pressed, user code C3 will be displayed, similar to screen G23 in Figure 17. This user code is required when paying for items in a shopping basket at a regular register or self-checkout.

[0078] This sequence of events will be further explained with reference to the sequence chart in Figure 19. When button b14 (code issuance button) is operated on screen G5a in Figure 18 (step S50: YES), the store application on user terminal 3 sends a code issuance request to application server 5 (step S52). The code issuance request includes the displayed purchase plan list. When application server 5 receives the code issuance request from the store application, it issues a user code (step S54) and records the issued user code in association with the offering price of each product in the purchase plan list included in the code issuance request in step S52 (official price of the product list) (step S56). Next, application server 5 returns the user code issued in step S54 to the store application (step S58). The store application converts the user code into a two-dimensional code (step S60) and displays the user code C3 on the display unit 34 of the user terminal 3, as shown in screen G23 of Figure 18 (step S62).

[0079] When a user brings the items they wish to purchase to a regular cashier, for example, and presents the user code displayed on the user terminal 3 to the store staff, the store staff reads the user code using a code reader connected to the cashier. The cashier then sends the read user code to the application server 5 for inquiry (step S64). The application server 5 reads the offered prices from the product list recorded in accordance with the user code received in step S56 and returns them to the cashier (step S66). The cashier processes the payment based on the offered prices from the received product list (step S68). As a result, users can efficiently make payments based on the prices of the products they confirmed on the store application before payment. The same applies to self-checkout registers. The difference is that instead of store staff, the customer themselves scans their user code using a code reader connected to the self-checkout machine.

[0080] Furthermore, it is preferable that the user code includes not only the membership number assigned to the user, but also information such as the date and time of the visit to the store, so that it contains different information depending on when the user uses (requests) the user code. Since the price of the same product may fluctuate from day to day, by making the user code obtained by the user different depending on when the request is made, the application server 5 can appropriately manage the user code and the product price for the user. Standard cash registers and self-checkout systems are just a few examples of store terminals.

[0081] When a user purchases multiple items at a regular register or self-checkout, the system may read the user code issued for one item, query the application server 5 for all of those items, and process the payment based on the discounted price.

[0082] (4-7) Seventh variation Next, we will explain the seventh modified example. The sixth modification describes a case where the user is matched with the offered prices on the product list in advance before making a payment at a regular or self-checkout register, but this is not the only case. In the seventh modification, the user may only check the offered prices of the products offered to them or the product list using the price checker, and then at a regular or self-checkout register, they may scan the products to be purchased, and also scan a user identification code such as a user code or membership code displayed on the user terminal 3, and make a payment at the offered price of the products corresponding to the user. For example, a store user can use the price checker function shown in Figures 16 and 17 to see the price of the product offered to them, and then decide whether or not to purchase it. In this case, as shown in Figure 9, different product prices may be presented depending on the user's status. If a user decides to purchase an item using the price checker, they place the item in a store basket or shopping cart, go to a regular or self-checkout register, and the purchase is processed when the barcode of the item to be purchased is scanned. At this time, for example, by operating button b13 on screen G22, a user code that identifies the user is displayed in the store application. This user code is then either scanned by a store staff member using a code reader (in the case of a regular checkout register) or scanned by the user themselves using a code reader (in the case of a self-checkout register). The regular or self-checkout register then queries the application server 5 for the price of the item whose barcode has been scanned, based on the user status of the scanned user code. The application server 5 determines the price for the user and returns the price information to the regular or self-checkout register. The regular or self-checkout register then processes the payment based on the price information received from the application server 5. Thus, in this modified version, the user can simply confirm the price of the product by scanning it on the user terminal 3, and then actually pay for the purchased product by having the barcode of the product read at a regular or self-checkout register in the store.

[0083] (4-8) Variation 8 Next, we will explain the eighth variant. In the eighth modification, the user registers information about the substances that cause their allergies (hereinafter referred to as "allergens") in advance on the application server 5. Then, when the store application reads the code information of a product, if the product contains an allergen that the user has registered, it is configured to display a message on the user terminal 3 indicating that the product contains the allergen. As a result, the user can safely purchase products knowing that they do not contain their allergens.

[0084] Figure 20 shows an example of screen transitions in the store application on user terminal 3 in this modified example. Screens G30 and G31 in Figure 20 correspond to screens G1 and G2 in Figure 2, respectively. Window w12 on screen G31 contains information such as the product name corresponding to the product ID, the regular price, the discounted price, and the expiration date, as well as information on the presence or absence of allergens. Here, we show an example where the user has already registered "almonds" as their allergen. It indicates that the allergens contained in the product being read (in this example, "granola") include the allergen that the user has previously registered ("almonds"). The window w12 on screen G31 may include a button b15 that allows the user to check the details of the allergens contained in the product. By operating button b15, screen G32 is displayed. Screen G32 displays the allergens contained in the product (for example, "almonds" and "peanuts") from among the items that are subject to allergen labeling (for example, items specified in the Food Labeling Act), and allergens that the user has registered in advance ("almonds") are highlighted.

[0085] Figure 21 shows an example of the configuration of the user database in this modified example. The user database in Figure 21 differs from the user database of the first embodiment (see Figure 5) in that a value has been added to the "Registered Allergen" field for each record. The value of the "Registered Allergen" field is entered in response to a request from the corresponding user and indicates the allergen specific to that user. Furthermore, the storage 52 (an example of a storage unit) of the application server 5 stores an allergen database as illustrated in Figure 22. As shown in Figure 22, the allergen database contains information about allergens (contained allergens) contained in each product sold at the store. The contained allergens correspond to the content displayed on screen G32 in Figure 20.

[0086] As explained with reference to Figure 7, when the store application on user terminal 3 reads the product code information, it sends a price inquiry to application server 5 that includes the product ID and expiration date information of the received product. In this modified example, when the control unit 51 of application server 5 receives the price inquiry, it refers to the user database (Figure 21) and reads the registered allergen information corresponding to the user ID of the store application. Next, the control unit 51 refers to the allergen database (Figure 22) and determines whether the read registered allergen is included in the contained allergens corresponding to the product ID included in the price inquiry. The communication unit 53 of the application server 5 sends back information to the store application on the user terminal 3, along with price data, regarding the determination result of whether or not the registered allergen is included in the allergens contained in the target product. In other words, the communication unit 53 functions as a notification unit that notifies the user terminal 3 of allergy information indicating the presence of the allergen when the registered allergen is included in the allergens corresponding to the product ID. Based on the price data and the determination result, the store application on the user terminal 3 displays the information exemplified in screen G31 of Figure 20.

[0087] It is preferable to establish a system that prevents users from purchasing products containing their registered allergens. For example, if a product contains a user's registered allergen, the store application may control the operation of button b1 ("Add to Cart") on screen G31 to be disabled. Alternatively, for example, when the user code described in the sixth modification is read by a code reader at a regular register or self-checkout, the register terminal may query the application server 5 including the product ID to be paid for, and receive a result from the application server 5 indicating whether or not the registered allergen is included in the allergens corresponding to the product ID. If the registered allergen is present, the register terminal may output an alert (warning sound or warning display) to the user, or prevent payment for the product containing the registered allergen. In this way, a system can be established that prevents users from purchasing products containing their registered allergens. Therefore, users do not need to visually check product ingredient labels to see if their allergens are present. Furthermore, it prevents users from accidentally purchasing products containing their allergens due to forgetting to visually check product ingredient labels. Furthermore, if the product is a prepared food item, information on allergens contained in another product manufactured immediately before that product may also be registered in the database. In this case, when a user reads, for example, the product code information using the store application on user terminal 3, if the user's registered allergens are contained in another product manufactured immediately before the product being read, the store application will display a message indicating that the product being read may also contain trace amounts of the registered allergens. This makes it possible to provide consumers with a system that allows them to purchase products with greater peace of mind and safety.

[0088] (4-9) Ninth variation Next, I will explain the ninth modified example. In the third embodiment, a case was described in which a label with a Markdown code printed on it is affixed to the product, and the Markdown code of the discounted product is notified to the user. The use of this Markdown code is not limited to when the user has a user terminal 3 with the store application installed. In this modification, a system is described in which the Markdown code of the discounted product is displayed on an in-store display device (for example, digital signage or electronic shelf label).

[0089] Figure 23 shows a schematic diagram of the system configuration of the price presentation system 2 of this modified example. As shown in Figure 23, the price display system 2 of this modified example includes an application server 5 and a digital signage 8 installed in the store as an example of a display device. The application server 5 and the digital signage 8 can communicate with each other via a network NW.

[0090] As described in the third embodiment, at least some of the products in the store have labels with markdown codes attached. In this modified example, the application server 5 determines the markdown codes to be discounted and displays the determined markdown codes on the digital signage 8 in the store. That is, in this modified example, the control unit 51 of the application server 5 functions as the following instruction information determination unit and display control unit. For example, the control unit 51 is configured to enable the following functions on the computer by executing a server program. (i) An instruction information determination unit that determines one or more markdown codes from among several different markdown codes to be applied to products that will be discounted relative to their base price (i.e., products subject to price reduction). (ii) Display control unit that displays one or more Markdown codes determined by the instruction information determination unit on the digital signage 8.

[0091] The control unit 51 of the application server 5 determines the markdown code of the discounted product, for example, as illustrated in Figure 11, but is not limited to this. The control unit 51 may also determine the markdown code of the discounted product according to the daily inventory status of the product. For example, unlike the example shown in Figure 11, the markdown code of the discounted product may be switched as appropriate, depending on the inventory status of the product, to be either the markdown code of the product whose expiration date is today or tomorrow, or the markdown code of the product whose expiration date is today, tomorrow, or the day after tomorrow. Furthermore, the markdown code of the discounted product may not be determined by the application server 5, but may be determined by store staff or the like. By displaying Markdown codes on the digital signage 8, users can identify discounted items even without having a user terminal with the store application installed, and purchase these discounted items at a regular register or self-checkout.

[0092] When the control unit 51 of the application server 5 displays two or more different Markdown codes on the digital signage 8, it may associate and display one of several pieces of information with different discount levels (for example, discount rate information) for each of the two or more different Markdown codes. An example of such a display is shown in Figure 24. The display example shown in Figure 24 corresponds to the setting of the Markdown code label exemplified in Figure 11, and is displayed on the in-store digital signage 8, for example, on May 19, 2020. In Figure 24, the Markdown code is displayed to the user as a "special sale code". As an example, the discount rate is varied for each special sale code (i.e., Markdown code). In other words, it is displayed that products expiring on the same day (Markdown code: A) will be 20% off, products expiring the next day (Markdown code: B) will be 10% off, and products expiring the day after that (Markdown code: C) will be 5% off. Users who check this information on the in-store digital signage 8 can immediately recognize whether a product is eligible for a discount, and if so, what the discount rate is, based on the Markdown code on the label attached to the product in the store.

[0093] Figure 24 shows an example where markdown codes are displayed on the digital signage 8 for discounted items, without being limited to specific products within the store or distinguishing by product type, etc. However, this is not the only way. When displaying markdown codes on electronic shelf labels corresponding to products, individual codes can be displayed for each product. For example, suppose the markdown codes on the labels attached to product PX are "X1", "X2", ... and the markdown codes on the labels attached to product PY are "Y1", "Y2", ... In this case, the electronic shelf label corresponding to product PX will display "X1", "X2", ... as "sale codes", and the electronic shelf label corresponding to product PY will display "Y1", "Y2", ... as "sale codes". Because Digital Signage 8 can be a relatively large-screen display device, when displaying Markdown codes on Digital Signage 8, hanging Digital Signage 8 on the store wall allows many customers in the store to recognize the Markdown codes. Therefore, it is suitable for displaying a common Markdown code for all products in the store, rather than for a specific product. In contrast, electronic shelf labels are small display devices placed on product shelves, making them suitable for displaying Markdown codes for individual products. As mentioned above, each electronic shelf label corresponding to a product can display the Markdown code appropriate for that product.

[0094] As described in the third embodiment, the Markdown codes for discounted items may be displayed, for example, when the store application is launched. In this case, when the application server 5 determines one or more Markdown codes attached to discounted items, the store application (an example of a display control unit) on the user terminal 3 receives the one or more Markdown codes from the application server 5 and displays them on the display unit 34. Therefore, a user who has a user terminal 3 with the store application installed can identify discounted items without having to check the display content of the digital signage 8 or other displays in the store.

[0095] Although embodiments of the information processing system, information processing method, and program of the present invention have been described above, the present invention is not limited to the embodiments described above. Furthermore, the above embodiments can be improved or modified in various ways without departing from the spirit of the present invention. For example, the individual technical features described in each of the above embodiments and each of the modified examples can be appropriately combined with some or all of the other embodiments and other modified examples, as long as there is no technical contradiction. In the embodiments and modifications described above, at least a portion of the functions of the application server 5 may be implemented by the software of the user terminal 3, or at least a portion of the functions of the user terminal 3 may be implemented by the software of the application server 5. Furthermore, the functions of the user terminal 3 and the functions of the application server 5 may be distributed between the user terminal 3 and the application server 5 as needed. The functions executed by the application server 5 may also be distributed and executed across multiple devices. [Explanation of Symbols]

[0096] 1, 2... Price display system 3…User terminal 31…Control Unit 32...Storage 33... Operation input section 34…Display section 35…Imaging Unit 36... Code reader 37… Communications Department 5…Application Server 51... Control Unit 511...Price determination section 512…Price Information Department 513...Payment Processing Unit 52...Storage 53... Communications Department 7…Payment processing server 8…Digital signage 100...Scan area 101, 102… scrollbar 103...Markdown code display section 104…Link Information CT…User BL...Purchase list ML... Menu List HL... Home inventory list NW...Network P…Product PL...label

Claims

1. An information processing system including a display device placed in a store that handles goods, and a server capable of communicating with the display device, The aforementioned product is pre-assigned with at least one discount information from among several discount information assigned according to the expiration date information of the product. The server includes an instruction information determination unit that determines information on multiple discounts to be assigned to individual products of different product types according to the expiration date information, The system includes a display control unit that causes the display device to display, at the same discount timing, information regarding the same discount applied to a discounted product, from among the multiple discount information determined by the instruction information determination unit, respectively. Information processing system.

2. When the display control unit displays information about two or more discounts on the display device, it associates and displays one of a plurality of pieces of information with different discount degrees for each of the two or more pieces of information about discounts. The information processing system described in claim 1.

3. This includes a user terminal owned by the user and capable of communicating with the aforementioned server, The user terminal has a display control unit that displays information regarding one or more discounts provided by the server on its display unit. An information processing system according to claim 1 or 2.

4. Includes a printer capable of communicating with the server, The server instructs the printer to issue a printable medium on which one of the multiple discount information items assigned according to the expiration date information is printed for each individual product of a different product type. An information processing system according to claim 1 or 2.

5. An information processing method performed by a server that can communicate with a display device installed in a store that handles goods, The aforementioned product is pre-assigned with at least one discount information from among several discount information assigned according to the expiration date information of the product. The aforementioned information processing method is A step of determining information on multiple discounts to be assigned to individual products of different product types according to the expiration date information, The step includes displaying information on the display device, at the same discount timing, information on the same discount that applies to the discounted product from among the multiple discount information that has been determined, respectively. Information processing methods.

6. A program that causes a computer to execute a predetermined procedure on a server that can communicate with a display device installed in a store that handles goods, The aforementioned product is pre-assigned with at least one discount information from among several discount information assigned according to the expiration date information of the product. The aforementioned prescribed procedure is, A procedure for determining information on multiple discounts to be assigned to individual products of different product categories according to the expiration date information, The procedure includes, of displaying information on the same discount targeting the discounted product from among the multiple discount information determined, on the display device at the same discount timing, program.

Images