JP7410550B2 - System and program - Google Patents

Description

The present invention relates to a system and a program.

For example, there is a known technology in which a customer is presented (printed on a receipt) with a specific day selected based on the current date from among pre-stored specific days such as holidays and sale days (for example, patent document (see 1).

Special Publication No. 62-062397

However, there was room for improvement in terms of improving customer attraction and customer satisfaction.

The present invention has been made in view of these circumstances, and its purpose is to provide a technology that improves customer attraction and customer satisfaction.

In order to solve the above-mentioned problems, a product sales data processing system that is one aspect of the present invention includes a registration unit that identifies and registers a product to be purchased, and a display unit that displays the product registered by the registration unit as a purchased product. and storage means capable of storing information regarding the product, the display means storing the product specified by the registration means in the storage means as information regarding the product compared to when the product was specified. If the product is a product for which future information regarding the product is stored, the future information regarding the product is displayed before displaying the product as a purchased product.

It is a conceptual diagram of a network for explaining a sales system. It is an explanatory diagram explaining a payment device. This is an example of a display on a display unit of a mobile terminal. This is an example of a display on a display unit of a mobile terminal. This is an example of a display on a display unit of a mobile terminal. 2 is a sequence diagram illustrating an overview of the overall flow of product purchase by the sales system 1. FIG. 2 is a sequence diagram illustrating an overview of the overall flow of product purchase by the sales system 1. FIG. 2 is a sequence diagram illustrating an overview of the overall flow of product purchase by the sales system 1. FIG. 2 is a sequence diagram illustrating an overview of the overall flow of product purchase by the sales system 1. FIG. 5 is a flowchart illustrating an example of the operation of a mobile terminal by the sales system 1. FIG.

FIG. 1 is a conceptual diagram of a network for explaining a sales system 1. As shown in FIG. The sales system 1 shown in FIG. 1 includes a management device (for example, a store controller) 10, a cloud server 20, a registered settlement device 30, a settlement device 40, a monitoring device 50 (for example, a personal computer, etc.), and a mobile terminal 60 (for example, a smartphone). etc.). Although one registration and payment device 30 is illustrated in FIG. 1, the number of registration and payment devices 30 in one store may be two or more. Further, although two payment devices 40 are shown in FIG. 1, the number of payment devices 40 in one store may be one or three or more. Further, although one monitoring device 50 is illustrated in FIG. 1, the number of monitoring devices 50 in one store may be two or more. Furthermore, although there is basically one management device 10 per store, there may be two or more management devices 10. The sales system 1 can be introduced into various stores (supermarkets, convenience stores, drug stores, home centers, home electronics retailers, apparel shops, other specialty stores, etc.).

The sales system 1 shown in FIG. We provide various services such as (hereinafter referred to as Service A). Note that the portion of the sales system 1 that provides service A may be referred to as a specific sales system. In other words, the specific sales system is a subsystem of the sales system 1 and provides service A. Note that in the following description, among the customers, customers who use the service A may be particularly referred to as members.

The management device 10, the registration and payment device 30, the payment device 40, and the monitoring device 50 are installed in the store, and are communicably connected via a LAN 19 (which may be wired or wireless). The management device 10 can communicate with the cloud server 20.

The management device 10 is a device that mainly manages various devices within the LAN 19. For example, the management device 10 has a communication function with external devices. The management device 10 receives, for example, a product file (product master) and a special sale file from an external device (for example, it may be a server at the headquarters (not shown) or a cloud server 20), and sends the registration and settlement device 30, etc. It also receives transaction information from the settlement device 40, etc., and transmits it to an external device (for example, the cloud server 20, etc.).

The product file is, for example, a file that stores product names, selling prices, etc. in association with product identification information (product code) that identifies individual products. The sale file is, for example, a file that stores the sale period (start date and time, end date and time) and sale details (discount and discount conditions, discount and discount details) in association with product identification information.

The cloud server 20 is a server that provides various services. For example, the cloud server 20 provides service A (a service corresponding to a mode in which a customer who is a member himself/herself registers a product using the mobile terminal 60). For example, the cloud server 20 manages (stores) various information related to service A (for example, transaction information (cart information), etc.).

The cloud server 20 manages (stores) product files and special sale files. Note that, as described above, the cloud server 20 provides the service A, but the sale based on the sale file (the sale realized by referring to the sale file) may be performed in the entire sales system 1. However, it may be limited to a specific sales system (service A) of the sales system 1. In other words, the sale based on the sale file may be applied both when a store clerk registers a product using the registration and settlement device 30 and when a customer who is a member himself registers a product using the mobile terminal 60. A special sale based on a special sale file may be applied only when a customer who is a member registers a product using the mobile terminal 60. Note that instead of the cloud server 20, another device (for example, a server at the headquarters (not shown)) may manage the product file. Further, instead of the cloud server 20, another device (for example, a server at the headquarters (not shown)) may manage the special sale file.

Further, the cloud server 20 manages an age verification product file that stores product codes of age verification products (products that require confirmation of the age of the purchaser; also referred to as clerk call products; for example, alcohol, cigarettes, etc.). The age verification product file is used, for example, to determine whether the product is an age verification product. Note that instead of the cloud server 20, another device (for example, a server at the headquarters (not shown)) may manage the age verification product file. Note that, for example, the product file may also serve as the age-verification product file by storing a flag indicating whether the product file corresponds to the age-verification product (value 0: applicable, value 1: not applicable).

The registration and settlement device 30 is a device that executes registration processing and settlement processing. The registration and payment device 30 is used by a store clerk (registration processing and payment processing are executed by the store clerk's operations).

The payment device 40 is a device that executes payment processing. The payment device 40 is basically used by a customer (performs payment processing by the customer's operation). The payment device 40 is used by at least a customer (member) who uses the service A.

The monitoring device 50 is a device that mainly monitors various devices within the LAN 19. The monitoring device 50 monitors the operating status of other devices (for example, the registered payment device 30, the payment device 40, etc.), displays various information on the other devices, outputs various commands to the other devices, etc. do.

The mobile terminal 60 is operated by a customer who is a member. The mobile terminal 60 is used when using the service A. The mobile terminal 60 includes a communication function, an imaging function (camera), and a recognition function for recognizing various codes (barcodes, two-dimensional codes, etc.). For example, the mobile terminal 60 recognizes a barcode attached to a product. For example, the mobile terminal 60 may extract feature points in a captured image (an image acquired as a through image) captured by the imaging function and recognize objects (various codes).

Although the mobile terminal 60 is basically assumed to be the property of each member, it may be lent by the store. Note that the number of mobile terminals 60 (the number in operation) changes depending on the number of visitors, etc., and in FIG. It shows.

Note that the mobile terminal 60 displays various screens related to the service A. For example, an application program for using service A is installed in the mobile terminal 60. Hereinafter, it will also be referred to as a specific application. ) may be installed, and the mobile terminal 60 may display various screens related to the service A.

Note that part or all of the sales system 1 (or specific sales system) may be called other names (for example, product registration system, payment system, product sales data processing system, etc.).

Furthermore, in the above description, the cloud server 20, the payment device 40, and the mobile terminal 60 are used for the service A, but the management device 10 is also used for the service A (for example, the payment device 40 and the cloud server 20 are used for the service A). (used for sending and receiving information). Note that other devices (such as the registration and settlement device 30, the monitoring device 50, a server at the headquarters (not shown), etc.) may be used for the service A.

FIG. 2 is an explanatory diagram illustrating the payment device 40. As shown in FIG. FIG. 2(A) is a diagram showing an example of the appearance of the payment device 40 (a perspective view seen from the customer side). FIG. 2(B) is a diagram showing a configuration example of the payment device 40. In FIG. 2(A) and FIG. 2(B), the same parts are given the same reference numerals. Note that the payment device 40 is basically operated by the customer.

Hereinafter, a configuration example of the payment device 40 shown in FIG. 2(B) will be described with reference to FIG. 2(A). The payment device 40 includes a CPU 401, a ROM 402, a RAM 403, a hard disk 404, a display section 405, a scanner section 406, a card payment section 408, a change machine 409, a printing section 413, an audio output section 414, A communication section 415 is provided. These can communicate with each other via a bus. Note that the payment device 40 may further include a key operation section, an imaging section (camera), and a notification section (a lamp such as a sign pole).

The CPU 401 is a central processing unit, and controls the operation of the payment device 40 by reading and executing a program stored in the ROM 402 .
The ROM 402 is a read-only memory and stores various information used by the CPU 401 including programs.

RAM 403 is a read/write memory and stores various information. For example, the RAM 403 stores information read from the ROM 402 or the hard disk 404, information acquired from the outside, information generated during processing, and the like.

Hard disk 404 stores various information. For example, instead of the ROM 402, the hard disk 404 may store programs executed by the CPU 401. Further, instead of the RAM 403, information read from the ROM 402, information acquired from the outside, information generated during processing, etc. may be stored.

The display unit 405 is a touch display, and displays various information and receives various inputs.

The scanner unit 406 optically reads various information. For example, the scanner unit 406 scans a code (such as a two-dimensional code for payment) displayed on the display unit of the mobile terminal 60 and reads information necessary for payment processing. The scanner unit 406 also scans codes (barcodes, two-dimensional codes, etc.) printed on checkout tickets (registered trademark) issued by other devices (for example, the registered payment device 30), and scans codes (barcodes, two-dimensional codes, etc.) necessary for payment processing. The scanner unit 406 may also scan a barcode attached to a product and read the product code.The scanner unit 406 may also scan a barcode attached to a store clerk's name tag. You may also scan a code or the like and read the clerk code.

The card payment unit 408 is a payment mechanism using various cards (credit cards, prepaid cards such as transportation cards, cash cards for debit payments, point cards for point payments, etc.). The card payment unit 408 includes a card recognition unit (reading unit), a display unit, and an operation unit, but any device may be used as long as it includes at least a card recognition unit. Note that the card recognition unit may recognize various cards (for example, point cards, membership cards, shareholder cards, etc.) for granting benefits, discounts, and the like.

The change machine 409 (cash payment unit) is a cash payment mechanism, has an input slot for banknotes and coins, and a discharge port for banknotes and coins, calculates the amount inserted into the slot, and compares the input amount and the purchase amount. The difference in change amount is calculated and the change is discharged from the discharge port. When banknotes or coins are inserted into the slot, they are detected by a sensor (detection of insertion, detection of number of coins for each denomination, etc.).

The printing unit 413 prints and issues various media (receipts, billing tickets, etc.).
Audio output unit 414 outputs audio. For example, the audio output unit 414 outputs audio guidance and the like.
The communication unit 415 transmits and receives information to and from other devices (management device 10, registered payment device 30, other payment device 40, monitoring device 50, etc.).

Although the appearance and hardware configuration of the payment device 40 have been described, the description of the appearance and hardware configuration of the registration and payment device 30 and the like will be omitted. Note that, as described in FIG. 1, the registration and payment device 30 is basically used by a store clerk (registration processing and payment processing are executed by the store clerk's operations).

In addition, the registration and payment device 30 has a display unit and a scanner unit on each side (clerk side, customer side), and a payment unit (card payment unit, cash payment unit) on one side (customer side). Good too. The registration and payment device 30 having the above configuration has a plurality of operation modes (a mode in which a registration process is executed by a clerk's operation and a settlement process by a customer's operation, a mode in which a registration process is executed by a customer's operation) depending on the operating status, etc. The device may be capable of switching to any one of the following operating modes: a mode in which the payment process is executed, a mode in which the registration process is executed by the operation of the clerk and the customer, and a mode in which the payment process is executed by the customer's operation, etc. . Further, the registered payment device 30 can be used for the service A if the payment processing is executed by the customer's operation. That is, the customer can perform the registration process using the mobile terminal 60 and the payment process using the registration and payment device 30.

3 to 5 are display examples on the display unit of the mobile terminal 60. FIG. 3(A) is an example of a start screen for service A. The mobile terminal 60 acquires information specifying the store (store specifying information) and displays a start screen. For example, a 2D code containing store specific information, etc. is displayed near the entrance of the store (outputting the 2D code on a display screen, pasting a medium on which the 2D code is printed, etc.), and customers who visit the store When the (member) scans (reads) the two-dimensional code with the mobile terminal 60, the mobile terminal 60 may acquire the store specific information. Note that when a customer visiting the store launches a specific app, a screen may be displayed that instructs the customer to scan the two-dimensional code, or when the customer visiting the store scans the two-dimensional code with the mobile terminal 60, A specific application may be started and a start screen may be displayed.

In FIG. 3(A), symbol a is a store information button for displaying store information (location, telephone number, business hours, etc.). When the store information button is operated (touched), the mobile terminal 60 displays store information regarding the store in question (〇〇〇 store XXXX store) instead of the start screen (or on the front side of the start screen). do. Reference numeral b is a notification button for displaying notifications (information on changes in business hours, new product information, local event information, etc.). When the notification button is operated, the mobile terminal 60 displays a notification instead of the start screen (or in front of the start screen). Reference numeral c is a bargain information button for displaying bargain information (introduction of bargain products, general information regarding special sales, etc.). When the advantageous information button is operated, the mobile terminal 60 displays advantageous information in place of the start screen (or in front of the start screen). The symbol d is a memo button for displaying memo information. When the memo button is operated, the mobile terminal 60 displays memo information in place of the start screen (or in front of the start screen). The symbol e is a shopping start button for starting shopping. When the shopping start button is operated, the mobile terminal 60 displays the registration screen shown in FIG. 3(B) and subsequent figures instead of the start screen. Note that the mark "NEW" in the upper right corner of the bargain information button indicates that the bargain information has been updated (updated since the last viewing, updated today, etc.).

FIG. 3(B) is a display in a scene subsequent to FIG. 3(A). Specifically, FIG. 3(B) is a registration screen (initial registration screen) that is displayed after the shopping start button (symbol e) is operated on the start screen of FIG. 3(A). In FIG. 3(B), symbol f is a captured image display area that displays a captured image. Symbol g is a registered information display area (also referred to as a registered product list) that displays registered information of products. Note that since the initial registration screen is a registration screen that is displayed immediately after the shopping start button is operated, nothing is displayed in the registration information display area.

FIG. 3(C) is a display in a scene subsequent to FIG. 3(B). Specifically, FIG. 3(C) is a registration screen when the barcode attached to the product (350 ml of 〇〇 beer) is being imaged. When registering a desired product (product to be purchased), the customer images the barcode attached to the product (reads and recognizes the product code of the product), as shown in FIG. 3(C).

FIG. 3(D) is a display in a scene subsequent to FIG. 3(C). In FIG. 3(D), it is reported that the product (350 ml of 〇〇 beer) identified by imaging the barcode is an age-verified product. In FIG. 3(D), the symbol h is a small screen (window) that informs that the product is an age-verified product. In other words, when the product identified by capturing an image of the barcode corresponds to an age-verified product, the mobile terminal 60 displays a message on the registration screen (on the near side of the registration screen) as shown in FIG. 3(D). A small screen (symbol h) is displayed to inform that the product is an age verification product.

Note that if an age confirmation product is registered (purchased), a store clerk is called to confirm the purchaser's age at the time of checkout. In other words, the small screen (symbol h) notifies you in advance that the clerk will be called at the time of payment.

FIG. 4(A) is a display in a scene subsequent to FIG. 3(D). In FIG. 4A, it is reported that the product (350 ml of 〇〇 beer) specified by capturing an image of the barcode has been registered. In FIG. 4(A), symbol i is a small screen that notifies that a product has been registered. The code j is the registration information of the product. In other words, when a product is identified by capturing an image of a barcode, the mobile terminal 60 displays a small screen (symbol i) on the registration screen (on the near side of the registration screen), as shown in FIG. 3(A). is displayed to notify that the product has been registered, and the registration information of the product is displayed in the registration information display area.

As described above, when a product identified by capturing an image of a barcode corresponds to an age-verified product, the mobile terminal 60 displays the small screen (symbol h) as shown in FIG. 3(D). After a certain period of time (for example, about 2 to 5 seconds) has elapsed, the small screen (symbol h) is deleted and a new small screen (symbol h) is displayed, as shown in Fig. 4 (A). Notification that the product has been registered is given using symbol i), and registration information (symbol j) of the product is displayed in the registration information display area. In addition, in FIG. 3(D) and FIG. 4(A), an example was explained in which the small screen (symbol h) is automatically deleted after a certain period of time and the small screen (symbol i) is displayed, but the customer's operation (For example, based on placing an OK button on the small screen (code h) and operating the OK button), erase the small screen (code h) and display the small screen (code i). You may.

Further, in FIG. 4(A), symbol k is a checkout button for ending shopping and proceeding to checkout. When the checkout button is operated, the mobile terminal 60 displays a two-dimensional code for payment (FIG. 5(D)).

FIG. 4(B) is a display in a scene subsequent to FIG. 4(A). Specifically, FIG. 4(B) shows the registration screen when the registration of the product (350 ml of 〇〇 beer) is completed.

Note that in FIGS. 4(A) and 4(B), an example was explained in which the small screen (coded i) is automatically deleted after a certain period of time has passed, but depending on the customer's operation (for example, the small screen (coded i) i) An OK button may be placed above the screen, and the small screen (symbol i) may be deleted based on the operation of the OK button.

Note that if the product identified by capturing an image of the barcode corresponds to an age verification product, the mobile terminal 60 performs the following process from FIG. 3(C) → FIG. 3(D) → FIG. 4(A) → FIG. 4( B), but if the product identified by capturing the barcode does not correspond to the age verification product, the display will change from Figure 3 (C) → Figure 4 (A) → Figure 4 (B). transition. Note that the display manner of registered information of age-confirmed products in the registered information display area is the same as the display manner of registered information of products that do not correspond to age-confirmed products (for example, white bread, etc.).

FIG. 4(C) is a display in a scene subsequent to FIG. 4(B). Specifically, FIG. 4(C) is a registration screen when the barcode attached to the product (XX shampoo) is being imaged.

FIG. 4(D) is a display in a scene subsequent to FIG. 4(C). In FIG. 4(D), it is reported that the product (〇〇shampoo) identified by imaging the barcode is a special sale preview product (a product scheduled for a special sale). In FIG. 4(D), reference numeral l is a small screen that informs that the item is on sale. In other words, when the product identified by capturing an image of the barcode corresponds to a product scheduled for sale, the mobile terminal 60 displays a message on the registration screen (on the near side of the registration screen) as shown in FIG. 4(D). A small screen (symbol 1) is displayed to inform that the product is an age verification product.

On the small screen (symbol 1) in FIG. 4(D), as special sale information, it is announced that the product (〇〇shampoo) will be discounted from 500 yen to 420 yen for one week from three days later. In the small screen (code 1) of FIG. 4(D), code m is a purchase button that is selected when the user decides to purchase the product (〇〇shampoo) this time. The symbol n is a purchase later button that is selected when the user decides to purchase the product (〇〇shampoo) at a later date. In other words, the customer refers to future discount information on the small screen (symbol l), operates the purchase button (symbol m) if he or she wants to purchase immediately without waiting for future discounts, and waits for future discounts. If you wish to purchase at a later date, operate the purchase at a later date button (symbol n). In other words, the mobile terminal 60 displays a purchase button (symbol m) and a purchase later button (symbol n) as selection buttons (instruction buttons) for accepting a customer's selection (instruction) regarding the purchase of a product scheduled for sale.

FIG. 5(A) is a display in a scene subsequent to FIG. 4(D). Specifically, FIG. 5(A) is a registration screen when the purchase button (symbol m) is operated on the small screen (symbol l) of FIG. It is. In FIG. 5(A), the symbol o is the registration information of the product scheduled for special sale. The symbol p is coupon issue information of a coupon issued in connection with the current purchase of the product scheduled for special sale. In other words, when the purchase button (symbol m) is operated after notifying that the product is a special sale preview product by capturing an image of the barcode, the mobile terminal 60 registers the special sale preview product in the registration information display area. In addition to displaying information, coupon issuance information of a coupon issued in connection with the current purchase of the product scheduled for special sale is also displayed.

The coupon issue information (symbol p) includes the fact that a coupon is provided and the details of the provided coupon (discount amount, etc.). In the example shown in FIG. 5(A), the above is summarized and coupon issue information such as "80 yen coupon issued at time of payment" is displayed. The face value (discount amount) of the coupon is the same as the discount amount of the product scheduled for special sale.

In addition, after operating the purchase button (symbol m), the mobile terminal 60 notifies that the special sale preview product has been registered using a small screen similar to the small screen (symbol i) in FIG. Registration information of advance notice products and coupon issuance information may also be displayed.

FIG. 5(B) is a display in a scene subsequent to FIG. 4(D). Specifically, FIG. 5(B) shows the registration when the purchase later button (symbol n) is operated on the small screen (symbol l) of FIG. It's a screen. In FIG. 5(B), reference numeral q is a small screen that notifies the user that the item scheduled for special sale will be purchased at a later date and that the item should be returned to the shelf.

FIG. 5(C) is a display in a scene subsequent to FIG. 5(B). In FIG. 5(C), the reference numeral r is information regarding the bargain sale product that the user has decided to purchase at a later date (later purchase information). In other words, when the purchase button (symbol n) is operated after the mobile terminal 60 notifies that the product is a special sale preview product by capturing an image of the barcode, the mobile terminal 60 displays the special sale preview product in the registered information display area. Display purchase information at a later date.

Purchase information at a later date (symbol r) includes a mark ("later date" in Figure 5 (C)), product name (○○ shampoo in Figure 5 (C)), and quantity ("x1" button in Figure 5 (C)). ), including the scheduled sale price (“¥420” in FIG. 5(C)). The mobile terminal 60 displays the purchase information at a later date in a clay-down display so that it can be distinguished from other product information (in FIG. 5(C), information on "XX Beer").

In addition, in FIG. 5(B) and FIG. 5(C), an example was explained in which the small screen (coded q) is automatically deleted after a certain period of time has passed, but depending on the customer's operation (for example, the small screen (coded q) q) An OK button may be placed above the screen, and the small screen (marked q) may be erased based on the OK button being operated.

FIG. 5(D) is a two-dimensional code display screen displaying a two-dimensional code for payment. When the checkout button (symbol k) is operated on the registration screen, the mobile terminal 60 displays a two-dimensional code display screen as shown in FIG. 5(D) instead of the registration screen. Note that, instead of the two-dimensional code display screen, the mobile terminal 60 may display a small screen on which the two-dimensional code for payment is displayed on the registration screen (on the near side of the registration screen).

FIG. 6 is a sequence diagram illustrating an overview of the overall flow of product purchase by the sales system 1 (specifically, service A provided by the specific sales system). Specifically, FIG. 6 shows that a certain customer (a member who has a mobile terminal 60 with a specific application installed) comes to a certain store (a store where service A operates) and uses the mobile terminal 60. The mobile terminal 60, the payment device 40 installed in the store, and the cloud server installed outside the data center etc. until the products displayed at the store are registered and the payment for the registered products is completed. 20 shows an example of the flow of processing in each of 20. The left side of FIG. 6 is the process of the mobile terminal 60, the center is the process of the payment device 40, and the right side is the process of the cloud server 20.

In the explanation of the sequence diagram in FIG. 6, it is assumed that a two-dimensional code (a two-dimensional code obtained by converting store specific information etc. into a two-dimensional code) for identifying the store is displayed near the entrance of the store. do. Furthermore, in the explanation of the sequence diagram of FIG. 6, it is assumed that the product identified by capturing an image of the barcode is neither an age confirmation product nor a product scheduled for sale.

Step S1: The mobile terminal 60 acquires store specific information. Specifically, when a customer visiting the store uses the mobile terminal 60 to scan a two-dimensional code displayed near the entrance of the store, the mobile terminal 60 acquires store specific information.

Step S2: The mobile terminal 60 that has acquired the store specific information transmits the store specific information to the cloud server 20 together with customer identification information (user ID).

(Address of cloud server 20)
When step S2 is executed, the address (destination information) of the cloud server 20 is stored in the mobile terminal 60. Specifically, the mobile terminal 60 stores the address of the cloud server 20 during customer registration (for example, when installing a specific application on the mobile terminal 60). For example, the address of the cloud server 20 is held within a specific application, and upon completion of customer registration, the address of the cloud server 20 is stored in the storage unit of the mobile terminal 60 (or may be the user storage area of the specific application). The information may be stored in a storage area common to all applications.

(About customer identification information)
The customer identification information is stored in the mobile terminal 60 when step S2 is executed. Specifically, the mobile terminal 60 stores customer identification information at the time of customer registration. In customer registration, information entered into the registration form using the mobile terminal 60 is stored as customer information in the cloud server 20. In the case of the embodiment), the customer identification information input in the registration form is stored in the storage unit of the mobile terminal 60, and is also transmitted to the cloud server 20 and stored in the cloud server 20 as customer information. On the other hand, in the case of a mode in which customer identification information is not input in the registration form (a mode in which the cloud server 20 generates customer identification information), the customer identification information generated by the cloud server 20 is stored as customer information in the cloud server 20. , is transmitted to the mobile terminal 60 and also stored in the storage unit of the mobile terminal 60.

Step S3: The cloud server 20, which has received the customer identification information and store specific information from the mobile terminal 60, generates cart information (cart information, also referred to as basket information) for the transaction. The cart information may include, for example, cart identification information, transaction start date and time, transaction end date and time, customer identification information, registered product information, and the like. The cart identification information is identification information that uniquely identifies the cart. For example, the cart identification information may include store identification information, a date, and a serial number (for example, a serial number for each store and date). The transaction start date and time is the transaction start date and time (for example, the cart information generation date and time). Note that the transaction start date and time may be the registration date and time of the first product item. Both the generation date and time of cart information and the registration date and time of one item of product may be stored separately. Note that when cart information is generated, cart identification information, transaction start date and time, and customer identification information are generated, but since this is before the actual transaction (product registration) starts, other information is not generated.

Step S4: The cloud server 20 that generated the cart information for the transaction generates screen information (screen information of the start screen, screen information of the initial registration screen), and sends the generated screen information to the mobile terminal 60 together with the cart identification information. do.

Step S5: The mobile terminal 60 that has received the cart identification information and screen information from the cloud server 20 stores the cart identification information and displays a start screen on the display unit as shown in FIG. 3(A).

Step S6: In response to the operation of the shopping start button (symbol e), the mobile terminal 60 displays a registration screen (initial registration screen) on the display unit, as shown in FIG. 3(B).

Note that in the sequence diagram of FIG. 6, the screen information of the initial registration screen is sent and received along with the screen information of the start screen, but the screen information of the initial registration screen may be sent and received after the screen information of the start screen is sent and received. . That is, step S6 may operate as shown in (1) to (3) below, for example. (1) The mobile terminal 60 transmits information indicating that the shopping start button has been operated to the cloud server 20 together with customer identification information. (2) The cloud server 20, which has received the information that the shopping start button has been operated and the customer identification information from the mobile terminal 60, generates screen information (screen information of the initial registration screen) and transfers the generated screen information to the mobile terminal. Send to 60. (3) The mobile terminal 60 that has received the screen information from the cloud server 20 displays the initial registration screen on the display unit.

Step S7: In response to the customer's reading operation, the mobile terminal 60 scans the barcode attached to the product and reads the product code.

Step S8: The mobile terminal 60 transmits the read product code to the cloud server 20 together with the cart identification information.

Step S9: The cloud server 20, which has received the cart identification information and product code from the mobile terminal 60, specifies the cart information of the transaction from the cart identification information.

Step S10: The cloud server 20 updates the specified cart information (adds product data). For example, when the cloud server 20 receives a product code as item N, it stores the product code in the specified cart information as a product code of registered product information (registered product N), and stores the product code corresponding to the product code. The product name and price are acquired from the product information and stored as the product and price of the registered product information (registered product N). Further, the cloud server 20 updates the registered product information (total) in the specified cart information.

Step S11: The cloud server 20 that has updated the cart information generates screen information after product registration (screen information of the registration screen corresponding to the updated cart information), and sends the generated screen information to the mobile terminal 60 along with the cart identification information. Send to.

Step S12: After receiving the cart identification information and screen information from the cloud server 20, the mobile terminal 60 checks whether the cart identification information matches the stored cart identification information, and then displays a registration screen based on the screen information. Display on the display. That is, the product is added to the registration screen of the mobile terminal 60.

Although simplified in FIG. 6 for convenience of explanation, the processes from step S7 to step S12 are repeatedly executed every time a product code is read in step S7 until a checkout instruction is received in step S13 below. That is, after step S12, there are two cases: accepting a checkout instruction (proceeding to step S13 below) and reading the product code again (returning to step S7).

Step S13: The mobile terminal 60 receives an accounting instruction as an operation by the customer. Specifically, the mobile terminal 60 accepts the operation of the checkout button (symbol k).

Step S14: The mobile terminal 60 that has received the payment instruction generates a two-dimensional code for payment. That is, the mobile terminal 60 converts information (for example, cart identification information) necessary for executing the payment process for the purchased product by the mobile terminal 60 into a two-dimensional code. The mobile terminal 60 that has generated the two-dimensional code displays the generated two-dimensional code on the display unit, as shown in FIG. 5(D).

Step S15: In response to the customer's reading operation, the payment device 40 scans the two-dimensional code displayed on the display section of the mobile terminal 60 and reads the two-dimensional code. For example, the payment device 40 scans a two-dimensional code displayed on the display section of the mobile terminal 60 that is pointed within the imaging range by the scanner section 406 by the customer, and reads the two-dimensional code.

Step S16: After reading the two-dimensional code, the payment device 40 requests the cloud server 20 to calculate the subtotal amount. For example, the payment device 40 transmits a calculation request requesting calculation of a subtotal amount (subtotal calculation request information) to the cloud server 20 via the management device 10 together with cart identification information obtained from the two-dimensional code.

Step S17: The cloud server 20, which has received the cart identification information and the subcalculation request information from the mobile terminal 60, specifies the cart information of the transaction from the cart identification information.

Step S18: The cloud server 20 that has specified the cart information calculates the subtotal amount of the specified cart information.

Step S19: The cloud server 20 that calculated the subtotal amount updates the cart information (memorizes the subtotal amount (subtotal amount after calculation)), and also updates the management device 10 with the subtotal information indicating the calculated subtotal amount together with the cart identification information. The information is transmitted to the payment device 40 via the computer.

Step S20: After receiving the cart identification information and subtotal information from the cloud server 20, the payment device 40 displays the subtotal amount on the display unit 405. That is, the payment device 40 displays the subtotal amount on the payment screen (not shown).

Step S21: The payment device 40 displays the subtotal amount on the display unit 405 and executes payment (settlement). Specifically, the payment device 40 accepts the selection of the payment type. In the case of cash, the deposit is accepted, the amount of change is calculated, and if there is change, the change is released and a receipt is issued. In addition, when the payment is completed, the payment device 40 transmits payment completion information together with the cart information to the cloud server 20 via the management device 10, and the cloud server 20 transmits the transaction end date and time of the cart information (payment date and time).

As mentioned above, the sequence diagram in FIG. 6 is a sequence diagram for the case where the product identified by imaging the barcode is neither an age confirmation product nor a product scheduled for sale. If the specified product is an age-verified product, in step S15, the payment device 40 calls the store clerk (sends a call message to the terminal carried by the store clerk, the registered payment device 30, the monitoring device 50, etc.). Note that the payment device 40 may be equipped with a light-emitting member such as a lamp, and the clerk may be called by causing the light-emitting member to emit light.

Various methods can be considered for causing the payment device 40 to call a store clerk, and for example, the following method may be used. When the mobile terminal 60 receives the checkout instruction in step S13, the mobile terminal 60 determines whether or not an age verification product is registered (for example, by checking the clerk call flag described later), and performs age verification when the checkout instruction is received. If the product is registered, a two-dimensional code containing information indicating that a store clerk needs to be called is generated in the subsequent step S14. Thereby, when an age verification product is purchased, the payment device 40 can call a store clerk in step S21.

In addition, if the product identified by capturing the barcode is a product scheduled for sale, and the product scheduled for sale is purchased (the purchase button (symbol m) is pressed for the customer's selection regarding the purchase of the product scheduled for sale) If the coupon has been operated), the payment device 40 issues a coupon in step S21. Various methods can be considered for causing the payment device 40 to issue a coupon, and for example, the following method may be used. If the mobile terminal 60 is displaying the coupon issuance information when the checkout instruction is received in step S13, the mobile terminal 60 displays the coupon indicated in the coupon issuance information (for example, the coupon issuance information in FIG. 5A) in the subsequent step S14. If displayed, a two-dimensional code is generated that also includes information necessary to cause the payment device 40 to issue an 80 yen coupon. Thereby, when a product scheduled for sale is purchased, the payment device 40 can issue a coupon in step S21.

Note that the mobile terminal 60 may generate one two-dimensional code that includes the information necessary to perform the payment process for the purchased product and the information necessary to issue the coupon, or may You may generate two two-dimensional codes including the following. Further, the payment device 40 may issue the coupon as a separate medium (separate paper) from the receipt (including the case of issuing the coupon so that it can be easily separated from the receipt), or may issue the coupon as a part of the receipt. (A receipt and coupon medium may also be issued.)

In addition, the payment device 40 encodes and prints the contents of the coupon (discount amount, etc.) on a coupon that is a medium (a coupon issued as a separate medium from a receipt or a coupon that also serves as a receipt). You may. For example, the payment device 40 may print a two-dimensional code that can be read by the payment device 40 and the registered payment device 30.

Further, the identification information for identifying the customer (or the mobile terminal 60) may be encoded. As a result, the payment device 40 and the like read the code (two-dimensional code, etc.) printed on the coupon, and determine the usage status of the coupon as the sales system 1 (specifically, service A provided by the specific sales system). This makes it possible to understand whether or not the device is used, the date and time of use, etc. For example, in step S15, the payment device 40 may input a two-dimensional code for payment (the two-dimensional code generated by the mobile terminal 60 in step S14) and a code (two-dimensional code, etc.) printed on the coupon. , and by comparing the identification information obtained by reading the two-dimensional code for payment with the identification information obtained by reading the coupon, it is possible to ensure that only the person in question can use the coupon. It is also possible to In other words, it is possible to invalidate and prevent the transfer of coupons for a fee or for free.

7 to 9 are other examples of the sequence diagram shown in FIG. 6. Specifically, FIG. 7(A), FIG. 7(B), FIG. 8(A), FIG. 8(B), FIG. 9(A), and FIG. 9(B) each correspond to the broken line frame P in FIG. (In other words, the processing each time a product code is read until a checkout instruction is received). Note that the broken line frame P in FIG. 6 does not include the processing of the payment device 40, so the processing of the payment device 40 is not included in FIG. is not listed.

(For age verification products (1))
In the explanation of the sequence diagram of FIG. 7(A), it is assumed that the product identified by capturing an image of a barcode is an age verification product. That is, it is assumed that the mobile terminal 60 reads the product code of the age verification product in step S7 of FIG. 6 before executing the process of step S7A1 of FIG. 7(A).

Step S7A1 in FIG. 7A: The mobile terminal 60 determines that the product specified by the product code read in step S7 in FIG. 6 is an age-verified product. Note that the mobile terminal 60 stores information for determining whether or not the product is an age verification product (for example, an age verification product file storing the product code of the age verification product) in the storage unit. It may be determined whether or not the product specified by the product code read in step S7 of 6 is an age-verified product, or another method that stores information for determining whether or not the product is an age-verified product may be used. By inquiring the device, it may be determined whether the product specified by the product code read in step S7 of FIG. 6 is an age-verified product.

Step S7A2 in FIG. 7A: The mobile terminal 60 sets a clerk call flag (value 0: no purchase of age verification product, value 1: purchase of age verification product) indicating whether or not an age verification product has been purchased. (set the value to 1). The clerk call flag is, for example, provided in the storage section of the mobile terminal 60, and is cleared (with an initial value of 0) when shopping (transaction) is started (for example, when the initial registration screen is displayed). It is set (value is 1) when the barcode of the age verification product is scanned (when the product code of the age verification product is read).

Step S7A3 in FIG. 7A: The mobile terminal 60 displays a message indicating that the product is an age-verified product. For example, the mobile terminal 60 displays a small screen (symbol h) shown in FIG. 3(D). It is assumed that the mobile terminal 60 has already stored the screen information of the small screen (symbol h) (stored at the time of downloading a specific application or acquiring the start screen). Hereinafter, steps S8 to S12 in FIG. 7(A) are the same as steps S8 to S12 in FIG. 6, so a description thereof will be omitted.

(For age verification products (2))
In the description of the sequence diagram of FIG. 7(B), it is assumed that the product identified by capturing an image of a barcode is an age verification product. That is, it is assumed that the mobile terminal 60 reads the product code of the age verification product in step S7 of FIG. 6 before executing the process of step S7A1 of FIG. 7(B). Note that the sequence diagram in FIG. 7(A) shows the flow in the case where the clerk call flag is provided on the mobile terminal 60 side, but the sequence diagram in FIG. The flowchart is shown in the embodiment provided in FIG.

Step S7A1 in FIG. 7B: Similar to step S7A1 in FIG. 7A, the mobile terminal 60 determines that the product identified by the product code read in step S7 in FIG. 6 is an age-verified product.

Step S7A3 in FIG. 7(B): Similar to step S7A3 in FIG. 7(A), the mobile terminal 60 displays a message indicating that the product is an age-verified product.

Step S8A1 in FIG. 7B: The mobile terminal 60 transmits the product code (the product code read in step S7 in FIG. 6) and information indicating that the product is an age-verified product to the cloud server 20 together with the cart identification information.

Step S9 in FIG. 7B: The cloud server 20 receives the cart identification information, the product code, and the information indicating that the product is an age-verified product from the mobile terminal 60, and uses the cart identification information to identify the transaction. Identify cart information.

Step S10 in FIG. 7(B): The cloud server 20 updates the specified cart information (adds product data), similarly to step S10 in FIG.

Step S10A1 in FIG. 7(B): The cloud server 20 sets a clerk call flag. The clerk call flag is, for example, provided in the storage unit of the cloud server 20 (for example, in the cart information), and is cleared when shopping (transaction) is started (for example, when the cart information is generated). The initial value is set to 0), and is set (the value is set to 1) when information indicating that the product is an age verification product is received (when the product code of the age verification product is read). Hereinafter, steps S11 and S12 in FIG. 7(B) are the same as steps S11 and S12 in FIG. 6, so a description thereof will be omitted.

(If you are purchasing a product scheduled for sale this time (1))
In the description of the sequence diagram in FIG. 8A, it is assumed that the product identified by capturing an image of a barcode is a product scheduled for sale. That is, it is assumed that the mobile terminal 60 has read the product code of the product scheduled for sale in step S7 of FIG. 6 before executing the process of step S7B2 of FIG. 8(A). In addition, it is assumed that a product scheduled for sale will be purchased during this shopping trip.

Step S7B2 in FIG. 8A: The mobile terminal 60 determines that the product specified by the product code read in step S7 in FIG. 6 is a product scheduled for sale. Note that the mobile terminal 60 stores information (for example, a sale file) for determining whether a product is scheduled for sale in the storage unit, so that the product specified by the product code is determined to be a product scheduled for sale. Alternatively, by querying another device that stores information for determining whether or not the product is a product scheduled for sale, the product identified by the product code may be determined to be a product scheduled for sale. It may be determined whether or not.

Step S7B4 in FIG. 8A: The mobile terminal 60 displays a message indicating that the product is on sale and a selection button (a selection button that accepts the customer's selection regarding the purchase of the product on sale). For example, the mobile terminal 60 displays a small screen (symbol 1) shown in FIG. 4(D). Note that the mobile terminal 60 has already memorized the information necessary for displaying the small screen (symbol l) (for example, image information for selection buttons that cannot be obtained from the special sale file) (memorizes it when downloading a specific application or acquiring the start screen). ).

Step S8B1 in FIG. 8(A): The mobile terminal 60 that has received the selection to purchase the currently scheduled sale product (for example, the operation of the purchase button (symbol m) in FIG. 4(D)) selects the product code (see 6) and the selection result ("Purchase") are sent to the cloud server 20 together with the cart identification information.

Step S9 in FIG. 8(A): The cloud server 20 receives the cart identification information, the product code, and the selection result (“Purchase”) from the mobile terminal 60, and, as in step S9 in FIG. Identify cart information.

Step S10B1 in FIG. 8(A): The cloud server 20 updates the specified cart information (adds product data and coupon issue information).

Step S11B1 in FIG. 8(A): The cloud server 20 that has updated the cart information generates screen information after adding product data and coupon issue information (screen information of the registration screen corresponding to the updated cart information), The generated screen information is transmitted to the mobile terminal 60 together with the cart identification information.

Step S12B1 in FIG. 8(A): After receiving the cart identification information and screen information from the cloud server 20, the mobile terminal 60 checks whether the cart identification information matches the stored cart identification information, and then displays the screen on the screen. A registration screen based on the information is displayed on the display unit. That is, as shown in FIG. 5(B), product information (product information (symbol o) of a product scheduled for sale) and coupon issue information (symbol p) are added to the registration screen of the mobile terminal 60.

(If you are purchasing a product scheduled for sale this time (2))
In the explanation of the sequence diagram of FIG. 8(B), it is assumed that the product identified by capturing an image of the barcode is a product scheduled for sale. That is, it is assumed that the mobile terminal 60 has read the product code of the product scheduled for sale in step S7 of FIG. 6 before executing the process of step S7B1 of FIG. 8(B). In addition, it is assumed that a product scheduled for sale will be purchased during this shopping trip. Note that the sequence diagram in FIG. 8(A) shows the flow in a manner in which the mobile terminal 60 side determines whether the product is scheduled for sale, but the sequence diagram in FIG. 8(B) shows the flow for determining whether the product is scheduled for sale. The flowchart shows a flow in which the cloud server 20 side determines whether

Step S7B1 in FIG. 8(B): The mobile terminal 60 transmits the read product code to the cloud server 20 together with the cart identification information, similar to step S8 in FIG.

Step S7B2 in FIG. 8B: The cloud server 20, which has received the cart identification information and product code from the mobile terminal 60, determines that the product specified by the received product code is a product scheduled for sale. Note that the cloud server 20 stores information (for example, a sale file) for determining whether or not the product is a sale item in the storage unit, so that the product specified by the product code is determined to be a sale item. Alternatively, by querying another device that stores information for determining whether or not the product is a product scheduled for sale, the product identified by the product code may be determined to be a product scheduled for sale. It may be determined whether or not.

Step S7B3 of FIG. 8(B): The cloud server 20 displays screen information (a message indicating that the product is on sale, screen information of a selection button. For example, the screen of the small screen (symbol l) shown in FIG. 4(D) information) and transmits the generated screen information to the mobile terminal 60 together with the cart identification information.

Step S7B4 in FIG. 8B: The mobile terminal 60, which has received the cart identification information and screen information from the cloud server 20, displays a message indicating that the item is on sale and a selection button. For example, the mobile terminal 60 displays a small screen (symbol 1) shown in FIG. 4(D). Hereinafter, steps S8B1 to S12B1 in FIG. 8(B) are the same as steps S8B1 to S12B1 in FIG. 8(A), so a description thereof will be omitted.

(If you do not purchase the product scheduled for sale this time (1))
In the description of the sequence diagram of FIG. 9A, it is assumed that the product identified by capturing an image of a barcode is a product scheduled for sale. That is, it is assumed that the mobile terminal 60 has read the product code of the product scheduled for sale in step S7 of FIG. 6 before executing the process of step S7B2 of FIG. 9(A). In addition, it is assumed that no products scheduled for sale will be purchased during this shopping trip.

Step S7B2 in FIG. 9A: Similar to step S7B2 in FIG. 8A, the mobile terminal 60 determines that the product specified by the product code read in step S7 in FIG. 6 is a product scheduled for sale.

Step S7B4 in FIG. 9(A): Similar to step S7B4 in FIG. 8(A), the mobile terminal 60 displays a message indicating that the product is on sale and a selection button. For example, the mobile terminal 60 displays a small screen (symbol 1) shown in FIG. 4(D).

Step S8C1 in FIG. 9(A): The mobile terminal 60 that has received the selection to purchase the sale scheduled product at a later date (for example, the operation of the purchase later button (symbol n) in FIG. 4(D)) selects the product code ( The product code read in step S7 of FIG. 6) and the selection result ("purchase at a later date") are sent to the cloud server 20 together with the cart identification information.

Step S8C2 in FIG. 9(A): The mobile terminal 60 that has sent the product code and selection result (“Purchase at a later date”) to the cloud server 20 along with the cart identification information displays a message to the effect that the sale scheduled product will be returned to the shelf. . For example, the mobile terminal 60 displays a small screen (symbol q) shown in FIG. 5(B).

Step S9 in FIG. 9A: The cloud server 20 receives the cart identification information, product code, and selection result (“purchase at a later date”) from the mobile terminal 60, and, as in step S9 in FIG. Identify cart information.

Step S10C1 in FIG. 9(A): The cloud server 20 updates the specified cart information (adds purchase information at a later date).

Step S11C1 in FIG. 9A: The cloud server 20 that has updated the cart information generates screen information after adding purchase information at a later date (screen information of the registration screen corresponding to the updated cart information), and the generated screen The information is transmitted to the mobile terminal 60 together with the cart identification information.

Step S12C1 in FIG. 9(A): After receiving the cart identification information and screen information from the cloud server 20, the mobile terminal 60 checks whether the cart identification information matches the stored cart identification information, and then displays the screen on the screen. A registration screen based on the information is displayed on the display unit. That is, purchase information (symbol r) is added to the registration screen of the mobile terminal 60 at a later date, as shown in FIG. 5(C).

(If you do not purchase the product scheduled for sale this time (2))
In the explanation of the sequence diagram of FIG. 9(B), it is assumed that the product identified by imaging the barcode is a product scheduled for sale. That is, it is assumed that the mobile terminal 60 reads the product code of the product scheduled for sale in step S7 of FIG. 6 before executing the process of step S7B1 of FIG. 9(B). In addition, it is assumed that no products scheduled for sale will be purchased during this shopping trip. Note that the sequence diagram in FIG. 9(A) shows the flow in a mode in which the mobile terminal 60 side determines whether the product is scheduled for sale, but the sequence diagram in FIG. 9(B) shows the flow for determining whether the product is scheduled for sale. The flowchart shows a flow in which the cloud server 20 side determines whether

Step S7B1 in FIG. 9B: The mobile terminal 60 transmits the read product code to the cloud server 20 together with the cart identification information, similar to step S8 in FIG.

Step S7B2 in FIG. 9(B): Upon receiving the cart identification information and product code from the mobile terminal 60, the cloud server 20 determines that the product specified by the received product code is scheduled to be on sale, as in step S7B2 in FIG. 8(B). It is determined that it is a product.

Step S7B3 in FIG. 9(B): The cloud server 20 generates screen information and transmits the generated screen information to the mobile terminal 60 together with the cart identification information, similarly to step S7B3 in FIG. 8(B).

Step S7B4 in FIG. 9(B): The mobile terminal 60, which has received the cart identification information and screen information from the cloud server 20, displays a message indicating that the product is on sale and a selection button, similar to step S7B3 in FIG. 8(B). indicate. Hereinafter, steps S8C1 to S12C1 in FIG. 9(B) are the same as steps S8C1 to S12C1 in FIG. 9(A), so a description thereof will be omitted.

FIG. 10 is a flowchart illustrating an example of the operation of the mobile terminal 60. Specifically, the flowchart in FIG. 10 shows the process within the broken line frame P in FIG. ), processing corresponding to FIG. 8(A), and FIG. 9(A)).

Step S100: The mobile terminal 60 determines whether the product specified by the read product code is an age verification product. If the product is an age-verified product (step S100: YES), the process advances to step S101. If the product is not an age-verified product (step S100: NO), the process advances to step S110.

Step S101: The mobile terminal 60 sets a clerk call flag (value 0: no purchase of age verification product, value 1: purchase of age verification product) indicating whether or not an age verification product has been purchased (value is set to 1). do). The process then proceeds to step S102.

Step S102: The mobile terminal 60 displays a message indicating that the product is an age-verified product. For example, the mobile terminal 60 displays a small screen (symbol h) shown in FIG. 3(D). The process then proceeds to step S102.

Step S110: The mobile terminal 60 determines whether the product specified by the read product code is a product scheduled for sale. If the product is scheduled for sale (step S110: YES), the process advances to step S130. If the product is not scheduled for sale (step S110: NO), the process advances to step S120.

Step S120: The mobile terminal 60 transmits the read product code to the cloud server 20 together with the cart identification information. The process then proceeds to step S122.

Step S122: The mobile terminal 60 adds (displays) a product (product specified by the read product code) to the registration screen according to the screen information received from the cloud server 20. Then, the flowchart of FIG. 10 ends.

Step S130: The mobile terminal 60 displays a message indicating that the item is on sale and a selection button. For example, the mobile terminal 60 displays a small screen (symbol 1) shown in FIG. 4(D). The process then proceeds to step S131.

Step S131: The mobile terminal 60 determines whether or not a selection to purchase the product scheduled for sale this time (eg, operation of the purchase button (symbol m) in FIG. 4(D)) is received. If the selection to purchase this time is accepted (step S131: YES), the process advances to step S140. If the selection to purchase this time has not been accepted (step S131: NO), the process advances to step S132.

Step S132: The mobile terminal 60 determines whether or not it has received a selection to purchase the product scheduled for sale at a later date (eg, operation of the purchase later button (symbol n) in FIG. 4(D)). If the selection to purchase at a later date is accepted (step S132: YES), the process advances to step S150. If the selection to purchase at a later date has not been accepted (step S132: NO), the process returns to step S131.

Step S140: The mobile terminal 60 transmits the read product code and the selection result (“Purchase”) to the cloud server 20 together with the cart identification information. The process then proceeds to step S142.

Step S142: The mobile terminal 60 adds (displays) the product (product specified by the read product code) and coupon issue information to the registration screen according to the screen information received from the cloud server 20. Then, the flowchart of FIG. 10 ends.

Step S150: The mobile terminal 60 transmits the read product code and the selection result (“purchase at a later date”) to the cloud server 20 together with the cart identification information. The process then proceeds to step S151.

Step S151: The mobile terminal 60 displays a message to the effect that the product scheduled for sale will be returned to the shelf. For example, the mobile terminal 60 displays a small screen (symbol q) shown in FIG. 5(B). The process then proceeds to step S152.

Step S152: The mobile terminal 60 adds (displays) purchase information to the registration screen at a later date according to the screen information received from the cloud server 20. The process then proceeds to step S153.

Step S153: If the clerk call flag is set, the mobile terminal 60 clears it (sets the value to 0). Then, the flowchart of FIG. 10 ends.

Although the embodiments of the present invention have been described above in detail with reference to the drawings, the specific configuration is not limited to these embodiments, and includes designs within the scope of the gist of the present invention.

In the above example, age-confirmed products are not displayed separately from other products in the registered information display area (the display format of registered information for age-confirmed products is the same as the display format of registered information for products that do not fall under age-confirmed products). However, age verification products may be displayed separately from other products. For example, a mark (for example, "confirmation", etc.) may be attached to the age confirmation product.

In the above example, the product scheduled for special sale that will be purchased this time is not displayed separately from other products in the registered information display area (for example, in FIG. Although an example has been described (not particularly different from the above), the product scheduled to be on sale this time may be displayed separately from other products. For example, a mark (for example, "this time", etc.) may be attached to a product scheduled for sale that is to be purchased this time.

In the above example, the mobile terminal 60 displays a message indicating that the product is an age-verified product every time the product code of the age-verified product is read even within one transaction (within one shopping from the start of shopping to the end of payment). Although an example has been described in which the product is an age verification product, the mobile terminal 60 may display a message indicating that the product is an age verification product only once in one transaction. For example, in FIGS. 7(A) and 7(B), after determining that the product identified by the read product code is an age verification product, the mobile terminal 60 determines whether the clerk call flag is set. Further judgment may be made, and if the clerk call flag is set, the message indicating that the product is an age verification product may not be displayed. Alternatively, the mobile terminal 60 first determines whether or not the clerk call flag is set, and if the clerk call flag is set, the mobile terminal 60 performs age verification without determining whether the product is an age verification product. A message indicating that the item is a product may not be displayed. Note that even if the message indicating that the product is an age verification product is displayed only once in one transaction, a mark or the like may be attached to each age verification product.

Note that in the case of an age verification product, the customer may be allowed to select whether or not to register. For example, if the product identified by the read product code is an age-verified product, the small screen (code h) that is displayed will include a purchase button to select when purchasing the age-verified product, and a button to select the age-verified product. A non-purchase button may also be provided, which is selected if the item is not purchased. For example, if the product code read by a minor is for an alcoholic beverage that they mistakenly believe is juice, they must operate the non-purchase button before actually registering and place the product (the alcoholic beverage in question) on the shelf. This eliminates the need for unnecessary age verification at checkout, which would occur if the user were to register as is.

In the above, as shown in FIG. 5(C), an example was explained in which the later purchase information (symbol r) is displayed in a clay-down manner. However, if the later purchase information can be distinguished from other information in the registered information display area, good. For example, the display format of at least one of the product name, quantity, and price (planned sale price) in later purchase information (e.g., at least one of font color, font size, and background color) may be different from general product information. It's okay. For example, the display format of the product name, quantity, and price (scheduled sale price) of the product may be the same as general product information, but the presence or absence of a mark ("later date" in FIG. 5(C)), etc. may be simply different. (That is, you don't have to clay down the purchase information at a later date).

In the above, as shown in FIG. 5(C), an example was explained in which later purchase information (symbol r) is displayed in a common area (registered information display area) with other information. It may be displayed in a different area. For example, part of the registered information display area (symbol g) may be set as a later purchase product area, and later purchase information may be displayed in the later purchase product area.

In the above, the purchase information at a later date includes the mark ("later" in Figure 5(C)), product name (XX shampoo in Figure 5(C)), and quantity ("x1" button in Figure 5(C)). , an example of displaying the planned sale price ("¥420" in FIG. 5(C)) has been described, but the display content is not limited to this. For example, since the planned sale price is generally a unit price, the quantity may not be displayed as purchase information at a later date. For example, the current price (the price before the sale of the planned sale price) may be displayed. For example, "¥500→¥420" may be displayed in FIG. 5(C). Furthermore, for example, a scheduled sale period (eg, "one week from three days later" in FIG. 5C) may be displayed.

Note that it may be possible to change a product scheduled for sale that was scheduled to be purchased at a later date to be purchased at this time. For example, although it was explained above that the purchase information at a later date is displayed in a clay-down display (that is, the operation is not accepted), it may be possible to accept a long-press operation and change the purchase information to the current purchase by a long-press operation (long-press operation). (You may be able to switch between purchasing at a later date and purchasing at this time each time you press the button, or you may display a small screen that allows you to change from purchasing at a later date to purchasing at this time by long-pressing the button.) For example, a ``Change current purchase'' button that allows you to change from purchasing at a later date to purchasing at this time is placed, and by operating this button, you can change the sale item that was scheduled to be purchased at a later date to purchase at this time. Good too. Furthermore, it may be possible to change the sale schedule item that the user was planning to purchase this time to purchase at a later date.

Of course, if you change the purchase of a bargain sale product that you had planned to purchase at a later date to the current purchase, the mobile terminal 60 will display later purchase information (for example, code r in FIG. 5C) for the bargain sale product. is changed to the general product information of the product scheduled for sale (for example, code o in FIG. 5(B)), and the coupon issued in connection with the decision to purchase the product scheduled for sale this time. Issue information (for example, symbol p in FIG. 5(B)) is displayed. On the other hand, if you change your plan to purchase the bargain sale product that you were planning to purchase this time to purchase it at a later date, the mobile terminal 60 changes the general product information of the bargain sale product to future purchase information for the bargain sale product. , the coupon issuance information of the coupon issued in connection with the decision to purchase the product scheduled for sale this time is deleted.

In the above example, the face value (discount amount) of the coupon is the same as the discount amount of the product scheduled for sale, but the face value (discount amount) of the coupon may be less than or equal to the discount amount of the product scheduled for sale. Coupons are issued as compensation (or benefits) for purchasing a product scheduled for sale instead of at the sale price, so the face value of the coupon should not exceed the discount amount of the product scheduled for sale. Make it.

Note that restrictions may be placed on the use of coupons. For example, as a restriction on products that can be used, a coupon issued in connection with the current purchase of a certain product scheduled for special sale may be used for the product scheduled for special sale or for products related to the product scheduled for special sale (the product scheduled for special sale) It may be possible to make it available only for products in the same category, products from the same manufacturer (seller) as the product scheduled for special sale, etc.). As a result, in addition to the above-mentioned compensation (or benefits), the coupon can also be used as a promotion for products in the same category or products from the same manufacturer (seller).

Further, instead of or in addition to the above-mentioned restrictions regarding the target product, restrictions regarding the period of use may be set. For example, a coupon issued in connection with the current purchase of a certain product scheduled for sale may be made available only during the scheduled sale period (in whole or in part) of the product scheduled for sale. good. Thereby, the coupon can also be used as a sales promotion during the scheduled special sale period. Note that a coupon issued in connection with a decision to purchase a certain sale item this time may be made available for use on the sale sale item during the sale period of the sale sale item. (It may also be possible to further discount coupons from the special sale price for scheduled products.)

Moreover, although the example in which the coupon is provided as a paper medium has been described above, it may be provided as an electronic coupon that can be displayed on the mobile terminal 60.

In the above example, when you decide to purchase a product scheduled for sale at a later date, the purchase information for the sale preview product is displayed in the registration information display area. Instead of or in addition to displaying the later purchase information of the special sale preview product in the information display area, the later purchase information (or information equivalent to the later purchase information) of the special sale preview product is displayed as memo information (start screen (Figure 3) It may also be stored as information displayed when the memo button (coded d) in (a)) is operated. In other words, in the above, an example was explained in which a product scheduled for sale at a later date is displayed in the registered information display area (in Figure 5 (C), it is displayed in a clay-down manner so that it can be distinguished from other information). It is not necessary to display the sale scheduled product in the registered information display area for the sale scheduled product that has been purchased at a later date, and regardless of whether or not the sale scheduled product that will be purchased at a later date is displayed in the registration information display area, it may be stored in the memo information. Good too.

Note that when the user visits the store, later purchase information (or information equivalent to later purchase information) that has been stored as memo information in the past may be automatically displayed without operating the memo button. In other words, later purchase information (or information equivalent to later purchase information) that is stored as memo information in connection with the next purchase of a certain product scheduled for special sale at a certain store, is stored at the time of the visit to the store (the relevant The memo button may be automatically displayed when the user visits the store during the scheduled sale period of the product scheduled for sale, without operating the memo button.

The later purchase information (or information equivalent to later purchase information) displayed as memo information is, for example, the product name and price, but may also include the display location. In addition, later purchase information (or information equivalent to later purchase information) displayed as memo information includes not only text information (character information) such as product name and price, but also images (images of the product, display location, etc.). image, etc.) (or a link to the image; in other words, the image may be displayed through an operation).

Note that the period during which the later purchase information (or information equivalent to later purchase information) stored as memo information is displayed is within the scheduled sale period of the product scheduled for sale. Note that when a product scheduled for sale is purchased with later purchase information (or information equivalent to later purchase information) stored as memo information, the later purchase information is deleted. Thereby, even if you visit the store (when you visit the store within the scheduled sale period for the product scheduled for sale), it may not be displayed after purchase.

Furthermore, if the user decides to purchase a product scheduled for sale at a later date, it may be possible to make a purchase reservation or request for home delivery in advance. For example, by operating a purchase later button (symbol n) for a certain sale preview product, the purchase information for the sale preview product at a later date is displayed in the registered information display area, and it is also possible to declare a purchase reservation or home delivery request for the sale preview product. A small screen may also be displayed. In addition, a button corresponding to later purchase information that is displayed after operating a later purchase button (symbol n) for a certain special sale preview product may be provided (displayed), and the above-mentioned small screen may be displayed by operating the button. .

Note that in the above example, when a product scheduled for sale is to be purchased this time, coupon issuance information is displayed in the registration information display area (symbol g). However, it is also possible to display coupon issuance information in the registration information display area. In addition, the fact that a coupon will be issued may be displayed on the two-dimensional code display screen for payment (step S14 in FIG. 6, FIG. 5(D)). In addition to displaying the coupon issue information in the registration information display area, a message that a coupon will be issued may be displayed on the payment screen of the payment device 40 (step S20 in FIG. 6).

Additionally, in the above example, when a product scheduled for sale is to be purchased this time, the coupon issuance information is displayed in the registration information display area (code g), but the coupon issuance information is not displayed in the registration information display area. It's okay. In other words, a coupon may be issued at the time of payment without displaying coupon issuing information in the registration information display area. This can prevent unexpected troubles.

Note that even if the coupon is issued at the time of checkout without displaying the coupon issuing information in the registration information display area, the fact that the coupon will be issued may be notified before the coupon is actually issued. For example, in a case where a coupon is issued, the coupon issuance information is not displayed in the registration information display area, but the fact that the coupon is issued is displayed on the two-dimensional code display screen for payment (step S14 in FIG. 6). Alternatively, instead of or in addition to the display screen of the two-dimensional code for payment, a message that a coupon will be issued may be displayed on the payment screen of the payment device 40 (step S20 in FIG. 6).

Additionally, in the above example, if you decide to purchase a product scheduled for sale this time, a coupon that can be used in future transactions is issued. However, it is also possible to purchase the product scheduled for sale without purchasing it at the sale price. This compensation (or benefit) is not limited to coupons. For example, if you decide to purchase a product that is scheduled to go on sale, instead of or in addition to issuing a coupon, you may give a discount for the transaction or give points (in addition to regular points). good. In addition, if you decide to purchase a product scheduled for sale this time, it may contribute to improving your customer rank (if other purchase records are the same, the number of customers who frequently purchase products scheduled for sale this time (You may also choose to have a higher customer rank than a customer with fewer customers.)

Furthermore, in the above example, if you decide to purchase a product scheduled for sale this time, a coupon is issued as compensation (or a benefit) for purchasing the product scheduled for sale without purchasing it at the sale price. For example, We understand that the notification that a product is on sale (display on the small screen (symbol 1)) itself is quite beneficial to the customer, and that the choice not to wait for a sale is at the customer's discretion (unexpected sale). However, the above-mentioned compensation (benefits) may not be provided.

Furthermore, in the above example, when a product scheduled for sale is to be purchased at a later date, the purchase information is displayed in the registered information display area. Good too. In other words, if you decide to purchase a product scheduled for sale at a later date, it is sufficient to store the later purchase information (or information equivalent to later purchase information) as memo information, and the later purchase information will not be displayed in the registered information display area. You can do it like this.

In addition, in the above example, if the product code of any product scheduled for sale is read, it will be uniformly notified that the product is scheduled for sale. It may be possible to notify that the product is a scheduled product. In other words, even if the product code is read, there may be a case where the product is notified that the product is on sale, and a case where the product is not notified. For example, it was explained that a special sale file is a file that stores the special sale period (start date and time, end date and time) and special sale contents (discount and discount conditions, discount and discount details) in association with product identification information. For example, a notification flag (value 0: no notification, value 1: notification presence) indicating whether or not to notify that the product is scheduled for sale, in association with the product identification information, in the special sale file, and a notification start condition ( For example, if there is a notification, how many hours before the start of the special sale period the notification should start), and conditions for ending the notification (for example, if there is a notification, how many hours before the start of the special sale period should the notification end? By storing information such as whether the product is on sale or not, even if the product is scheduled for sale, the notification flag is set as "No notification", or the product scheduled for sale is set with the notification flag as "Yes". For products scheduled for sale that do not satisfy the notification start condition or the notification end condition, the notification that the product is scheduled for sale may not be notified.

In addition, in relation to the above-mentioned example of the notification start condition (information on how many hours before the start of the sale period the notification should start), each explanation after FIG. 4(D) uses "purchase at a later date". The notification of the start of the sale (that is, the start of the sale) does not have to be "at a later date," that is, after the next business day. For example, it may be the same day, ie, any number of hours (or minutes) later on the business day.

In addition, above, we explained an example in which a coupon is issued uniformly when you decide to purchase any product scheduled for sale this time, but it is also possible to issue a coupon depending on each product scheduled for sale. You may also do so. In other words, even when making a current purchase, there may be cases where a coupon is issued and cases where a coupon is not issued. For example, it was explained that a special sale file is a file that stores the special sale period (start date and time, end date and time) and special sale contents (discount and discount conditions, discount and discount details) in association with product identification information. For example, by storing an issuance flag (value 0: not issued, value 1: issued) indicating whether or not to issue a coupon in association with the product identification information in the special sale file, a special sale for the current purchase can be made. Even if the product is scheduled for sale, it may not be reported that the product is scheduled for sale, but the issue flag is set to indicate that it will not be issued.

In addition, in the above, any customer (member) will be uniformly informed that the product scheduled for sale is a product scheduled for sale, and if he or she decides to purchase the product scheduled for sale this time. Although an example in which a coupon is issued has been described, it is also possible to notify each customer that the product is on sale and issue a coupon.

(1) Depending on the customer's attributes, there may be a case where the product is notified that the product is on sale, and a case where the product is not notified that the product is on sale. For example, if the best customer (e.g., the best customer based on RFM analysis, etc.) reads a product scheduled for sale, a notification will be sent to the effect that the product is scheduled for sale, and if a customer other than the best customer reads the product scheduled for sale, then It is also possible not to notify that the product is on sale. In addition, if the above-mentioned notification flag is set to indicate whether or not to notify that the product is scheduled for sale, for example, if the product is scheduled for sale with no notification (value 0), it will always be Even if the product is on sale, the notification that the product is on sale may not be notified. The same applies to (2) below.

(2) Depending on the customer's attributes, the target (frequency) of notification to the effect that the product is on sale may be varied. For example, the best customers are notified that all products scheduled for sale are scheduled for sale, and the next best customers are notified that some products scheduled for sale are scheduled for sale. However, other general customers may not be notified that all products scheduled for sale are scheduled for sale.

(3) Depending on the customer's attributes, there may be cases where a coupon is issued or cases where a coupon is not issued. For example, informing best customers and best customers that all products scheduled for sale are scheduled for sale (without informing general customers that all products scheduled for sale are scheduled for sale), Further, if the best customer decides to purchase the product scheduled for sale this time, a coupon may be issued, but if the best customer decides to purchase the product scheduled for sale this time, the coupon may not be issued. In addition, if the above-mentioned issuance flag is set to indicate whether or not to issue a coupon, for example, if the product is scheduled for sale without being issued (value 0), the coupon will always be issued (even if the customer is the best customer). Coupons may not be issued. The same applies to (4) below.

(4) The content of the coupon may vary depending on the customer's attributes. For example, if the best customer decides to purchase a certain product scheduled for sale this time, a high-value coupon will be issued, and if a general customer decides to purchase the product scheduled for sale (the same product scheduled for sale) this time, may issue a coupon with a low value, and if a good customer decides to purchase the product scheduled for sale (the same product scheduled for sale) this time, a coupon with a medium value may be issued. Note that a coupon with a high value is a coupon that is more advantageous for the customer than a coupon with a low value in at least one of the discount amount, usage target, and usage period.

In addition, in relation to (1) to (4) above, instead of or in addition to the best customers (or best customers), we will provide support to nearby customers (customers who live nearby, customers who work nearby). , similar control may be performed. For example, in example (1), if a nearby customer (or a customer in the neighborhood who is the best customer) reads a product scheduled for sale, it will be notified that the product is scheduled for sale; When a product is read, the notification that the product is on sale may not be notified.

Alternatively, the total amount of coupons may be managed. For example, there is a limit on the number of coupons issued (or total face value) within one transaction (from the start of shopping to the end of checkout), or the number of coupons issued (or total face value) for the same customer on the same day. may be provided. Note that the above upper limit may be changed depending on the customer's attributes. Also, the number of coupons (or total face value) that will be issued if you decide to purchase a certain sale item this time, and one or more sale items from a certain manufacturer (or seller). An upper limit may be set on the number of coupons (or total face value) that will be issued when the product scheduled for special sale is purchased this time. As a result, for example, it is possible to manage the total amount of coupons that will be issued when purchasing multiple types of products scheduled for special sale from Manufacturer S, making it possible to appropriately implement campaigns related to Manufacturer S. You can also.

In addition, although it was explained above that the payment device 40 is basically a device that performs payment processing by the customer's operation, the device that pays out products registered by the mobile terminal 60 also performs payment processing in addition to payment processing. The device may also be capable of executing registration processing. For example, a device that pays for products registered using the mobile terminal 60 is a device whose operating mode changes in response to a mode switching operation by a store clerk or a mode switching instruction from another device (for example, a device that can be operated from both sides (store clerk side, customer side)). For example, the operating modes include an operating mode in which the store clerk performs the registration process and the customer performs the payment process, an operation mode in which the customer performs both the registration process and the payment process, and an operation mode in which the store clerk performs the registration process. (a mode in which the payment processing function is turned off), an operation mode in which a customer executes payment processing (a mode in which the registration processing function is turned off), etc.).

A summary of the embodiments will be described below.
[Technical field]
The present invention relates to a product sales data processing system and program.
[Background technology]
For example, there is a known technology in which a customer is presented (printed on a receipt) with a specific day selected based on the current date from among pre-stored specific days such as holidays and sale days (for example, patent document (see 1).
[Prior art documents]
[Patent Document 1] Japanese Patent Publication No. 62-062397 [Summary of the invention]
[Problem to be solved by the invention]
However, there was room for improvement in terms of improving customer attraction and customer satisfaction.
The present invention has been made in view of these circumstances, and its purpose is to provide a technology that improves customer attraction and customer satisfaction.
[Means to solve the problem]
(1) In order to solve the above-mentioned problems, a product sales data processing system, which is an aspect of the present invention, includes a registration means for identifying and registering a product to be purchased, and a product sales data processing system for purchasing a product registered by the registration means. The display means is provided with a display means for displaying the product as a product, and a storage means capable of storing information regarding the product, and the display means stores the product specified by the registration means in the storage means as information regarding the product. If the product is a product for which future information (information regarding the product scheduled for special sale) is stored after that time, the future information regarding the product (information regarding the product scheduled for special sale) is stored before displaying the product as a purchased product. A product sales data processing system characterized by displaying information such as "applicable".
According to the product sales data processing system of (1) above, it is possible to improve customer attraction and customer satisfaction. For example, a message indicating that the product is on sale is displayed before registration, so you can shop based on the sale date (when the sale will start) and the sale price (how cheap it will be). These will improve customer satisfaction and, as a result, improve the ability to attract customers.
(2) In the product sales data processing system of (1) above, when the product specified by the registration means is a product for which the future information is stored in the storage means, the display means displays the A selection button that allows you to select whether to purchase or not (for example, see Figure 4 (D).The purchase button (symbol m) is a button to be selected when purchasing this time.The purchase button at a later date (symbol n) is a button to be selected when purchasing at a later date. ) is displayed.
According to the product sales data processing system (2) above, it is possible to improve customer attraction and customer satisfaction. For example, regarding a product scheduled for sale, it is possible to decide whether to purchase it now or at a later date, with reference to the scheduled sale date and sale price. These will improve customer satisfaction and, as a result, improve the ability to attract customers.
(3) In the product sales data processing system of (2) above, the display means displays the product for which the selection button is displayed as a purchased product when there is a selection to purchase the product. For example, see Figure 5 (A). The code o is the registration information of the product scheduled for special sale.) If there is a selection not to purchase, the product is not displayed as a purchased product (for example, Figure 5 (C) (Reference: The code r is not the registration information of the product scheduled for sale, but the information to be purchased at a later date.)
It is characterized by
According to the product sales data processing system in (3) above, for example, the display is easy to understand according to the selection content (selection to purchase, selection to purchase), and the selection content can be confirmed by the display. As a result, customer satisfaction improves, and as a result, the ability to attract customers improves.
(4) In the product sales data processing system set forth in (2) or (3) above, if there is a selection not to purchase the product for which the selection button is displayed, the display means displays the product for purchase at a later date. (For example, see FIG. 5(C)).
According to the product sales data processing system (4) above, for example, it is possible to confirm that a product scheduled for sale will be purchased at a later date, thereby improving customer satisfaction and, as a result, improving the ability to attract customers.
(5) If the product sales data processing system described in (2) to (4) above selects not to purchase the product for which the selection button is displayed, information regarding the product will be displayed when the customer enters the store at a later date. (for example, displayed as memo information when visiting the store).
According to the product sales data processing system of (5) above, since useful information is suitably provided, customer satisfaction is improved, and as a result, the ability to attract customers is improved.
(6) In the product sales data processing system of (1) to (5) above, the future information is information provided to a specific customer (for example, a good customer), and the display means is information provided to a specific customer (for example, a good customer). The product specified by the registration means as the product to be purchased by the customer is a product in which future information regarding the product after the time of identification is stored in the storage means as information regarding the product. In some cases, the future information regarding the product is displayed before the product is displayed as a purchase product.
According to the product sales data processing system of (6) above, since the target audience for which future information is displayed is limited to specific customers, provision of future information can be suitably managed. For example, it is possible to exclude C and D rank customers who are looking for future information, and to provide better treatment to S and A rank customers who are highly contributing. It also motivates certain customers to become customers.
(7) In order to solve the above-mentioned problems, a mobile terminal according to another aspect of the present invention includes a registration means for identifying and registering a product to be purchased, and a product registered by the registration means as a purchase product. If the product specified by the registration means is a product that has future information, the display means displays future information regarding the product before displaying the product as a purchased product. It is characterized by displaying information.
According to the mobile terminal (7) above, it is possible to improve customer attraction and customer satisfaction.
(8) In order to solve the above-mentioned problem, a program that is another aspect of the present invention is a program that causes a computer to function as a mobile terminal, the program that causes the computer to function as a mobile terminal.
The display means functions as a registration means for specifying and registering a product to be purchased, and a display means for displaying the product registered by the registration means as a purchased product, and the display means is configured to display the product specified by the registration means as the product. If the product has future information regarding the product, the feature is that future information regarding the product is displayed before displaying the product as a purchase product.
According to the program (8) above, the ability to attract customers and customer satisfaction can be improved.
(9) In order to solve the above-mentioned problems, a product sales data processing system that is one aspect of the present invention includes a registration means for identifying and registering products to be purchased, and a product sales data processing system for purchasing products registered by the registration means. The display means includes a display means for displaying the product as a product, and a storage means capable of storing additional information regarding the product (information regarding the age confirmation product, information regarding the product scheduled for special sale), and the display means includes:
When the product specified by the registration means is a product for which additional information is stored in the storage means, the additional information regarding the product (corresponding to age verification products) is displayed before displaying the product as a purchased product. It is characterized by displaying a message indicating that the item corresponds to a special sale item, etc.).
According to the product sales data processing system of (9) above, it is possible to improve customer attraction and customer satisfaction. For example, the fact that the product corresponds to age verification is displayed before registration, so customers can know in advance that the age of the registered age verification product will be verified by a store staff, thereby reducing confusion that may occur if they are not aware of this. It can be made less likely to occur. In addition, since the information that the product is on sale is displayed before registration, you can shop based on the sale date (when the sale will start) and the sale price (how cheap it will be). These will improve customer satisfaction and, as a result, improve the ability to attract customers.
(10) In the product sales data processing system of (9) above, when the product specified by the registration device is a product for which additional information is stored in the storage device, the display means displays the product. A selection button that allows you to select whether to purchase or not (for example, see FIG. 4(D).The purchase button (symbol m) is a button to be selected when purchasing this time.The purchase later button (symbol n) is a button for purchasing at a later date. ) is displayed.
According to the product sales data processing system (2) above, it is possible to improve customer attraction and customer satisfaction. For example, if the product code read by a minor is for an alcoholic beverage that they mistakenly believe is juice, they must operate the non-purchase button before actually registering and place the product (the alcoholic beverage in question) on the shelf. This eliminates the need for unnecessary age verification that would occur if the user were to register as is. In addition, regarding products scheduled for sale, it is possible to decide whether to purchase them now or at a later date, with reference to the scheduled sale date and sale price. These will improve customer satisfaction and, as a result, improve the ability to attract customers.

Note that the programs for realizing the sales system 1, management device 10, cloud server 20, registration and payment device 30, payment device 40, monitoring device 50, mobile terminal 60, etc. described above are stored in a computer-readable recording medium. The program may be recorded, and the program may be loaded into a computer system and executed. Note that the "computer system" herein includes hardware such as an OS and peripheral devices. Furthermore, the term "computer-readable recording medium" refers to portable media such as flexible disks, magneto-optical disks, ROMs, and CD-ROMs, and storage devices such as hard disks built into computer systems. Furthermore, "computer-readable recording medium" refers to volatile memory (RAM) inside a computer system that serves as a server or client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line. This also includes programs that are retained for a certain period of time. Further, the program may be transmitted from a computer system storing the program in a storage device or the like to another computer system via a transmission medium or by a transmission wave in a transmission medium. Here, the "transmission medium" that transmits the program refers to a medium that has a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line. Moreover, the above-mentioned program may be for realizing a part of the above-mentioned functions. Furthermore, it may be a so-called difference file (difference program) that can realize the above-described functions in combination with a program already recorded in the computer system.

1...Sales system (including specific sales system)
10...Management device (store controller, etc.)
20...Cloud server 30...Registered payment device 40...Payment device 50...Monitoring device 60...Mobile terminal 401...CPU
402...ROM
403...RAM
404...Hard disk 405...Display section 406...Scanner section 408...Card payment section 409...Change machine 413...Printing section 414...Audio output section 415...Communication section

Claims (6)

A system in which a customer goes around a store and registers each product at each product display location,
an imaging means for imaging products displayed in the store;
product identifying means for identifying the product imaged by the imaging means;
Display means for displaying the product specified by the product identification means as a registered product;
and a storage means capable of storing product sale schedule information,
The display means is
When the product specified by the product specifying means is a product scheduled for sale , for which the sale schedule information is stored in the storage means, before displaying the product as a registered product, the sale schedule information of the product is stored. A system characterized by displaying. The display means is
The system according to claim 1, wherein when the product specified by the product specifying means is the product scheduled for sale , a selection button is displayed that allows the user to select whether or not to purchase the product. . 3. The system according to claim 2 , wherein if there is a selection not to purchase the product for which the selection button is displayed, information regarding the product is notified when the customer enters the store at a later date. A program that makes a computer function as a mobile terminal,
The computer,
an imaging means for imaging products displayed in the store;
product identifying means for identifying the product imaged by the imaging means;
Display means for displaying the product specified by the product identification means as a registered product
function as
The display means is
If the product identified by the product specifying means is a product scheduled for sale , information on the sale schedule for the product is displayed before displaying the product as a registered product. program to do. a registration means for identifying and registering a product to be purchased;
Display means for displaying the product registered by the registration means as a purchased product;
and a storage means capable of storing information about the product,
The display means is
If the product specified by the registration means is a product for which future information regarding the product after the time of identification is stored in the storage means, the product is a purchased product. , displaying the future information regarding the product and displaying a selection button that allows the user to select whether or not to purchase the product;
If the customer chooses not to purchase the product for which the selection button is displayed, information regarding the product will be displayed when the customer enters the store at a later date.
A system characterized by: A program that makes a computer function as a mobile terminal,
The computer,
A registration method for identifying and registering products to be purchased;
Display means for displaying the product registered by the registration means as a purchased product
function as
The display means is
If the product specified by the registration means is a product that has future information regarding the product, display the future information regarding the product and purchase the product before displaying the product as a purchased product. Displays a selection button that allows you to select whether to
If the customer chooses not to purchase the product for which the selection button is displayed, information regarding the product will be displayed when the customer enters the store at a later date.
A program characterized by:

Images