Store terminal device, information output method, and program

Abstract

To efficiently increase customers who utilize an application.SOLUTION: A store terminal device is set at a store, and is used by a customer in a transaction. The store terminal device includes a control unit. The control unit uses a customer terminal device that the customer possesses to cause information for installing an application for registering a commodity in the customer terminal device to be output. For example, the control unit causes display means to display an image obtained by encoding the information when a screen during commodity registration transitions to another screen.SELECTED DRAWING: Figure 10

Description

[Technical Field]

[0001] The present invention relates to a store terminal device, an information output method, and a program. [Background technology]

[0002] In recent years, systems have become widespread in which customers are prompted to install a specific application on their mobile terminal devices and use the mobile terminal devices to register products. Stores have made various efforts to encourage customers to install the application on their mobile terminal devices. As a related technology, a system for sending emails to non-member users that prompts them to register on the application has been disclosed (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 6164345 Summary of the Invention [Problem to be solved by the invention]

[0004] However, the conventional technology has had the problem that the introduced system is not being effectively utilized.

[0005] The present invention has been made in view of the above circumstances, and an object of the present invention is to provide a technique for effectively utilizing a system. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems, one aspect of the present invention is a store terminal device that is installed in a store and used by customers in transactions, and is characterized by having a control means that outputs information for installing an application for registering products using a customer terminal device owned by the customer into the customer terminal device.

[0007] In order to solve the above-mentioned problems, another aspect of the present invention is an information output method characterized in that a computer used in a store terminal device installed in a store and used by a customer in a transaction executes a process to output information for installing an application for registering products into the customer terminal device owned by the customer.

[0008] In order to solve the above-mentioned problems, another aspect of the present invention is a program that executes a process to cause a computer used in a store terminal device installed in a store and used by a customer in a transaction to output information for installing an application for registering products using a customer terminal device owned by the customer into the customer terminal device. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is an explanatory diagram showing a network configuration of a shopping system St according to an embodiment. [Figure 2] 1 is an explanatory diagram showing an example of installation of a self-service checkout device 20. FIG. [Figure 3] 2 is a block diagram showing the hardware configuration of the self-checkout device 20. FIG. [Figure 4] FIG. 2 is an explanatory diagram showing an example of a hardware configuration of a mobile terminal device 30. [Figure 5] FIG. 2 is an explanatory diagram showing an example of various types of information managed by the cloud server Sv. [Figure 6] FIG. 2 is a sequence diagram showing the flow of processing from product registration to transaction completion in the shopping system St. [Figure 7]10 is a flowchart showing an example of processing performed by the customer terminal device 30a while a shopping application is running. [Figure 8] 10 is a flowchart showing an example of processing performed by the rental terminal device 30b while a shopping application is running. [Figure 9] FIG. 10 is an explanatory diagram showing an example of a screen displayed on the customer terminal device 30a when using a shopping memo tool. [Figure 10] FIG. 10 is an explanatory diagram showing an example of a screen displayed on the rental terminal device 30b when using a shopping memo tool. [Figure 11] FIG. 10 is an explanatory diagram showing an example of a screen displayed on the customer terminal device 30a when a history display tool is used. [Figure 12] FIG. 10 is an explanatory diagram showing an example of a screen displayed on the rental terminal device 30b when using a history display tool. [Figure 13] FIG. 10 is an explanatory diagram showing an example of a screen displayed on the self-checkout apparatus 20 during a mobile registration transaction. [Figure 14] 10 is an explanatory diagram showing an example of a receipt issued by the self-checkout apparatus 20 in a mobile registration transaction. FIG. [Figure 15] 10 is an explanatory diagram showing an example of installation of a dual-purpose POS terminal device 40. FIG. [Figure 16] FIG. 2 is a block diagram showing the hardware configuration of a dual-purpose POS terminal device 40. [Figure 17] 10 is a flowchart showing an example of processing performed by a dual-purpose POS terminal device 40. [Figure 18] 10 is a flowchart showing an example of information output processing performed by a dual-purpose POS terminal device 40. [Figure 19] 10 is an explanatory diagram showing an example of a screen displayed on a display unit of a dual-purpose POS terminal device 40. FIG. [Figure 20] FIG. 10 is an explanatory diagram showing an example of a receipt issued by a dual-purpose POS terminal device 40 in a POS registration transaction. [Figure 21] FIG. 10 is an explanatory diagram showing an example of a charging screen displayed by the rental terminal device 30b when the charge amount is equal to or less than a predetermined value. DETAILED DESCRIPTION OF THE INVENTION

[0010] (Embodiment) (Network configuration of the shopping system St) 1 is an explanatory diagram showing the network configuration of a shopping system St according to an embodiment. The shopping system St can be introduced into various stores such as supermarkets, home improvement stores, convenience stores, and various supply stores.

[0011] In FIG. 1, the shopping system St includes an external cloud server Sv, a store controller (store computer, management device) 10, a transaction status management device 11, a store terminal device 1 within the store, and a customer terminal device 30a owned by a customer. The store terminal device 1 includes a self-checkout device 20, a rental terminal device 30b, and a dual-purpose POS (Point of Sales) terminal device 40. The store terminal device 1 is a device installed in the store and used by customers in transactions. The store terminal device 1 may be owned by the store, rented from a manufacturer, or rented from a leasing company under a lease contract.

[0012] The dual-purpose POS terminal device 40 is a dual-purpose device that can be used by the customer himself or herself, as well as by store clerks for registration operations, etc. In the following, the customer terminal device 30a and the rental terminal device 30b will be described as the portable terminal device 30 unless otherwise specified.

[0013] Each device and each terminal is communicatively connected via a network. For example, the store controller 10, the transaction status management device 11, the self-checkout device 20, and the dual-purpose POS terminal device 40 are communicatively connected via a LAN (Local Area Network) 55. Each device and each terminal is a computer device equipped with a CPU (Central Processing Unit), ROM (Read Only Memory), RAM (Random Access Memory), a communication unit, etc.

[0014] The cloud server Sv is a server device that manages various types of information, such as customer information about customers, store information about stores, product information (product master) about products for each store, and cart information that indicates a virtual cart. For example, cart information is generated as a virtual cart for each customer and updated based on a product code read by the mobile terminal device 30. Cart identification information for identifying the cart (transaction and customer) is assigned to the cart information. The information managed (generated and stored) by the cloud server Sv will be described later with reference to FIG. 5.

[0015] The store controller 10 manages the multipurpose POS terminal device 40 and a weighing device (not shown), and stores various information necessary for transactions, such as a product master. The product master is a file that stores product information such as product identification information (e.g., JAN (Japanese Article Number) code), product name, and sales price for each product. The product master also includes various information such as product identification information, product name, and unit price for products that require weighing. In addition to the product master, the store controller 10 also stores various information such as inventory status, sales history, and deposit and withdrawal records. The store controller 10 may also store customer membership information.

[0016] The transaction status management device 11 monitors the self-checkout device 20 and the combined POS terminal device 40. Specifically, the transaction status management device 11 displays the status (processing status) of the self-checkout device 20 and the combined POS terminal device 40, and controls the self-checkout device 20 and the combined POS terminal device 40. The shopping system St may also include a terminal device carried by a store clerk. For example, the terminal device may display the same content as that displayed on the transaction status management device 11, or notify the store clerk to be called.

[0017] The dual-purpose POS terminal device 40 can be operated by either the customer or a store clerk depending on the mode. The modes referred to here are store clerk registration mode, full self-service mode, and checkout-only mode. The clerk registration mode is a mode in which a clerk registers the product and the customer performs either face-to-face payment at their own device or self-payment at another device. The other device is the self-payment device 20 or another dual-purpose POS terminal device 40. In the clerk registration mode, the dual-purpose POS terminal device 40 transmits payment information to the other device. However, in the clerk registration mode, the clerk may receive cash or the like from the customer and perform the payment.

[0018] The full self-service mode is a mode in which the customer registers products (self-service registration) and performs self-payment on the device. The checkout-only mode is a mode in which payment information for products registered by another device (for example, another dual-purpose POS terminal device 40 or a mobile terminal device 30) is acquired and payment is carried out by the user.

[0019] The self-checkout device 20 is a POS terminal device operated by the customer himself / herself for settlement purposes. The self-checkout device 20 may have a function for self-registration, and specifically, may be switchable to full self-service mode. Although FIG. 1 illustrates multiple self-checkout devices 20 and dual-purpose POS terminal devices 40, there may be only one.

[0020] The mobile terminal devices 30 include a customer terminal device 30a owned by the customer and a rental terminal device 30b owned by the store. When not in use, the rental terminal device 30b is connected to a charger installed at the entrance of the store or the like for charging. The rental terminal device 30b may be charged by a wired charging method or a contactless charging method (wireless charging). The mobile terminal device 30 is a portable computer device such as a smartphone, tablet device, or mobile phone. The mobile terminal device 30 is equipped with a communication unit, an imaging unit (camera), a touch panel, etc., and is operated by the customer. In this embodiment, the mobile terminal device 30 is detachably attached to the shopping cart. However, the rental terminal device 30b may be installed in the shopping cart, i.e., it may not be detachable from the shopping cart.

[0021] Application software (hereinafter referred to as the "shopping app") for registering products related to the shopping system St and for settling the registered products is installed on the mobile terminal device 30. By launching the shopping app, the mobile terminal device 30 scans (reads) the barcode (code information) attached to the product and accepts the product registration. When the mobile terminal device 30 reads the barcode attached to the product, it transmits the read information together with cart identification information to the cloud server Sv. As a result, the product information corresponding to the barcode is registered in the cart information (virtual cart) of the cloud server Sv.

[0022] Furthermore, when performing payment, the mobile terminal device 30 encodes and displays the cart identification information assigned to the device. This code is, for example, a two-dimensional code (QR Code (registered trademark)), but it can also be a one-dimensional code (barcode). The customer has the self-checkout device 20 read this two-dimensional code (hereinafter referred to as the "payment code"). After reading the payment code, the self-checkout device 20 requests the cloud server Sv to send cart information (transaction information) indicated by the cart identification information. In response to this transmission request, the self-checkout device 20 then receives the transaction information from the cloud server Sv, enabling payment to be performed. Note that payment is not limited to being performed by the self-checkout device 20; it can also be performed by a dual-purpose POS terminal device 40 in payment-only mode.

[0023] In this shopping system St, there are two transaction modes: The first transaction mode is a transaction in which a product is registered using a mobile terminal device 30 (hereinafter referred to as a "mobile registration transaction"); and the second transaction mode is a transaction in which a product is registered using a dual-purpose POS terminal device 40 (hereinafter referred to as a "POS registration transaction"). Therefore, depending on the customer, either a mobile registration transaction or a POS registration transaction is carried out.

[0024] Here, with the dual-use POS terminal device 40, customers may have to wait for the store clerk to complete product registration or may have to wait their turn for other customers to complete their transactions. In contrast, with mobile registration transactions, product registration is performed on each mobile terminal device 30, so customers do not have to wait for other customers to register products. Furthermore, the only device that a customer will occupy is the self-checkout device 20 of the store terminal device 1 at the time of checkout. Therefore, if mobile registration transactions become widespread, smooth transactions will be possible in stores, even when there are many customers. Furthermore, the workload of store clerks related to product registration can be reduced, allowing them to perform other tasks, such as replenishing inventory. This also contributes to more efficient store operations. In the following, we will first mainly explain mobile phone registration transactions, and POS registration transactions will be described later with reference to Figure 15 onwards.

[0025] (Configuration example of self-payment device 20) First, the configuration of the self-checkout apparatus 20 will be described with reference to FIGS. FIG. 2 is an explanatory diagram showing an example of installation of the self-checkout apparatus 20. Fig. 3 is a block diagram showing the hardware configuration of the self-checkout apparatus 20. In Fig. 2 and Fig. 3, the same components are denoted by the same reference numerals.

[0026] An example configuration of the self-checkout apparatus 20 shown in Fig. 3 will be described below with reference to Fig. 2. The self-checkout apparatus 20 includes a CPU 201, a ROM 202, a RAM 203, a hard disk 204, an operation display unit 205, a scanner unit 206, a card payment unit 208, a change dispenser 209, a printer unit 213, an audio output unit 214, a communication unit 215, a camera 216, and a sign pole 220. These units can communicate with each other via a bus.

[0027] The CPU 201 is a central processing unit that reads and executes various programs stored in the ROM 202 to control the operation of the self-payment apparatus 20. The various programs include an information output program according to this embodiment. The ROM 202 is a read-only memory that stores various types of information used by the CPU 201, including programs.

[0028] The RAM 203 is a readable and writable memory that stores various information. For example, the RAM 203 stores information acquired from the outside (e.g., transaction information (registration information) acquired from the cloud server Sv, product master data acquired from the store controller 10, etc.) and information generated during processing. This information also includes settlement information generated during a settlement process for settling (paying for) registered products.

[0029] Hard disk 204 stores various types of information. For example, hard disk 204 stores imaging results (e.g., video) captured by camera 216. For example, hard disk 204 may store various programs, such as an information output program executed by CPU 201, instead of ROM 202. Furthermore, hard disk 204 may store information acquired from the outside or information generated during processing, instead of RAM 203.

[0030] The operation display unit 205 is a touch display (touch panel) and is, for example, a vertical type. The operation display unit 205 displays various information to the customer and receives various operation inputs from the customer.

[0031] The scanner unit 206 optically reads various codes. The scanner unit 206 includes a stationary scanner fixed to the housing, a handheld scanner held by the operator, a pen-shaped scanner, and the like. The various codes are, for example, a payment code displayed on the mobile terminal device 30 and a code (barcode, two-dimensional code, etc.) printed on a checkout ticket (registered trademark). The various codes also include codes (barcode, two-dimensional code, etc.) printed on gift certificates (gift certificates, coupons, complimentary coupons) and various cards (for example, membership cards, point cards, etc.). The various codes also include a store clerk code attached to the name tag of a store clerk.

[0032] Furthermore, if the self-checkout apparatus 20 has a product registration function, the scanner unit 206 reads the barcode (product code, etc.) attached to the product. Product registration is not limited to registration by reading the barcode attached to the product. For example, a preset key (a button for ordering the product) corresponding to the product may be displayed on the operation display unit 205, and the product may be registered by operating (pressing) the preset key.

[0033] The card payment unit 208 is a payment mechanism that uses various cards (credit cards, prepaid cards such as transportation IC cards, point cards, etc.). The card payment unit 208 is equipped with a card recognition unit, a display unit, and an operation unit. The card recognition unit magnetically or electrically reads information from various cards. The read information is used to settle the registered product bill. The card recognition unit can also recognize information to be used in settling the registered product bill this time, for example, when using points held on a point card. The card recognition unit can also recognize information that is not to be used in settling the registered product bill this time, for example, when points are awarded to a point card. The card recognition unit can recognize contact cards (IC cards, magnetic cards) and contactless cards (IC cards).

[0034] The change machine 209 is a cash settlement mechanism, and has an input port for banknotes and coins, and an output port for banknotes and coins. The change machine 209 has a sensor that detects banknotes and coins inserted into the input port. The sensor detects that banknotes and coins have been inserted into the input port, and detects the number of banknotes and coins by denomination. The change machine 209 calculates the amount inserted into the input port, calculates the change amount, which is the difference between the input amount and the purchase amount, and outputs the change from the output port. The change machine 209 faces the operator, and accepts various operations and cash insertions from customers.

[0035] The printing unit 213 issues various media (receipts, bills, etc.) The printing unit 213 can change the direction of the media issuing port. The audio output unit 214 outputs audio. For example, the audio output unit 214 outputs audio guidance, warning sounds, etc. The audio guidance and warning sounds are related to product registration and payment. The communication unit 215 is an interface for transmitting and receiving information to and from other devices (the store controller 10, the transaction status management device 11, and the combined POS terminal device 40).

[0036] Camera 216 is attached to the upper right of operation display unit 205. Camera 216 is a camera that continuously captures moving or still images. A CCD (charge coupled device) camera or a CMOS (complementary metal oxide semiconductor) camera can be used as camera 216. Camera 216 captures images of the customer's operations during checkout. If self-checkout apparatus 20 has a product registration function, camera 216 captures images of the products during the customer's product registration operations.

[0037] Specifically, camera 216 is installed so as to capture an image of a customer performing operations related to payment from a customer-side position. The captured image by camera 216 can be used as a monitoring image for monitoring the customer performing payment. The captured image is stored in a storage device such as hard disk 204.

[0038] The captured image can be used, for example, to verify the amount actually deposited or as evidence. For example, suppose a customer deposits a 1,000 yen bill into the change dispenser 209, but then says, "I deposited a 10,000 yen bill, but I got less change." In this case, the change dispenser 209 records that a 1,000 yen bill was deposited. However, it cannot be said that misrecognition by the change dispenser 209 is impossible. Therefore, by examining the captured image, a store clerk can confirm the denomination actually deposited by the customer. Furthermore, the captured image can be presented to the customer as evidence.

[0039] It is also possible to constantly display the image information captured by camera 216 in real time on operation display unit 205 of self-checkout apparatus 20. Constantly displaying the captured image makes customers using self-checkout apparatus 20 aware that they are being photographed, which can have the effect of deterring fraud.

[0040] The captured image is displayed in a partial area of ​​operation and display unit 205. However, if self-checkout apparatus 20 is equipped with a display unit different from operation and display unit 205 (hereinafter referred to as "second customer-side display unit"), the captured image may be displayed on the second customer-side display unit. The second customer-side display unit may have a larger display area than operation and display unit 205. Increasing the display area of ​​the second customer-side display unit can further improve the deterrent effect against fraud. The second customer-side display unit may be attached to the top, left, or right side of operation and display unit 205. In particular, if it is attached in a position that improves visibility from a distance (for example, the top), even a store employee (particularly a supervisor) who is far from self-checkout apparatus 20 can monitor customer usage.

[0041] The period for recording captured images is, for example, the period from the start of a transaction until the customer receives a receipt and leaves the self-checkout terminal 20. The presence or absence of a customer in front of the self-checkout terminal 20 is determined, for example, by a human presence sensor. The camera 216 may record the period during which a customer is in front of the self-checkout terminal 20.

[0042] The camera 216 may also capture (record) images continuously. That is, the camera 216 may record images continuously, regardless of whether a transaction is taking place or whether a customer is standing in front of the self-checkout apparatus 20. When continuously recording, the self-checkout apparatus 20 may be equipped with a function to delete unnecessary portions. For example, this function stores images from five seconds before the start checkout button is pressed to accept the start of checkout until five seconds have passed since the receipt was removed, and deletes any other images. This allows captured images to be saved, even of the state before the start checkout button is pressed.

[0043] The sign pole 220 has a light-emitting unit. The light-emitting unit of the sign pole 220 is, for example, a lamp or an LED (light emitting diode), and can be lit in a predetermined color or a predetermined lighting pattern. The lighting pattern of the sign pole 220 indicates that the self-checkout device 20 is in use or issues a warning. The sign pole 220 is installed facing upward, so that even store staff who are not near the self-checkout device 20 can recognize the lighting pattern.

[0044] (Hardware configuration of the mobile terminal device 30) Fig. 4 is an explanatory diagram showing an example of the hardware configuration of mobile terminal device 30. In Fig. 4, mobile terminal device 30 includes a CPU 401, a ROM 402, a RAM 403, a memory 404, a communication unit 405, an operation unit 406, a camera 407, a microphone 408, a display 409, a speaker 410, and a GPS (Global Positioning System) unit 411. Each unit is connected to each other via a bus 420.

[0045] The CPU 401 controls the entire mobile terminal device 30. The ROM 402 stores various programs. The RAM 403 is used as a work area for the CPU 401. That is, the CPU 401 controls the entire mobile terminal device 30 by executing various programs, such as a shopping application, stored in the ROM 402 while using the RAM 403 as a work area.

[0046] The memory 404 stores various data. For example, a flash memory is used as the memory. The memory 404 stores various programs such as a shopping app, and various data such as map data and store information. The memory 404 of the rental terminal device 30b also stores an information output program according to this embodiment. The communication unit 405 is connected to a network, and is connected to other devices (for example, a cloud server Sv) via the network. Examples of communication networks that function as networks include the Internet and mobile phone networks.

[0047] The operation unit 406 is a touch panel that displays a plurality of touch keys for inputting characters, numbers, various instructions, etc., or hard keys. The camera 407 reads barcodes attached to products and various two-dimensional codes. The microphone 408 inputs the operator's voice. The display 409 displays icons, cursors, menus, windows, characters, images, codes, and the like.

[0048] The speaker 410 outputs sounds including voice. The GPS unit 411 has a function of receiving position information from GPS satellites and detecting the current position on map data of the mobile terminal device 30. The mobile terminal device 30 also includes various sensors (not shown) (for example, a gyro sensor, an acceleration sensor, a distance sensor, etc.) and has a function of detecting various states of the mobile terminal device 30 (for example, the inclination of the mobile terminal device 30, the distance between the mobile terminal device 30 and a product), etc.

[0049] (An example of information managed by the cloud server Sv) Next, an example of information managed by the cloud server Sv will be described with reference to FIG. 5 is an explanatory diagram showing an example of various types of information managed by the cloud server Sv. As shown in FIG. 5, the information stored by the cloud server Sv includes (A) customer information 501, (B) store information 502, and (C) cart information 503. Note that instead of or in addition to storing the various types of information in a storage unit within the cloud server Sv, the cloud server Sv may store some or all of the various types of information in another device, such as a file server, accessible by the cloud server Sv.

[0050] (Customer information 501) FIG. 5(A) shows an example of customer information 501. The customer information 501 is information for managing individual customers. The customer information 501 is information managed for each store or each affiliated store. As shown in FIG. 5(A), the customer information 501 includes customer identification information, customer name, customer registration date, customer rank, and number of points.

[0051] The customer identification information is identification information that uniquely identifies a customer. The customer identification information is generated, for example, when a shopping app is installed on the mobile terminal device 30 from the cloud server Sv or a predetermined server that provides general applications. For example, the customer identification information may be identification information that is uniquely assigned to each installed shopping app when the shopping app is installed on the mobile terminal device 30.

[0052] The customer name is the customer's name, nickname, etc. The customer name is generated based on the information entered in the name field of the registration form (input form) of the mobile terminal device 30 when registering a new customer, for example. The customer registration date is the date and time when the customer information 501 is newly registered in the cloud server Sv. The customer registration date is generated based on the current date and time when the customer is newly registered. The customer rank indicates a rank according to the customer's purchasing history. The number of points is the number of membership points given to a customer when they make a purchase by presenting their membership card.

[0053] (Store information 502) Fig. 5(B) shows an example of store information 502. Store information 502 is information for managing each store. As shown in Fig. 5(B), store information 502 includes store identification information, store name, first store identification information (two-dimensional code information), and second store identification information (location information). The store identification information includes a store (trade name) or company code and a branch code. The store name is the name of the store, and is composed of, for example, the store name (trade name) or company name and the branch name.

[0054] The first store identification information is information for identifying the store where the transaction takes place (the store where the product is bought and sold). The first store identification information is, for example, two-dimensional code information. The second store identification information is location information (GPS information) that indicates the location of the store. In the example shown in FIG. 5(B), both the first store identification information and the second store identification information are stored, but since both are information that can uniquely identify the store, it is sufficient to store at least one of the information.

[0055] (Cart information 503) Fig. 5(C) shows an example of cart information 503. The cart information 503 is information about products registered by a customer. As shown in Fig. 5(C), the cart information 503 includes cart identification information, transaction start date and time, transaction end date and time, customer identification information, and registered product information. The cart identification information is information for identifying the cart information 503. Specifically, the cart identification information includes store identification information, a date, and a serial number (for example, a serial number for each store by date).

[0056] The transaction start date and time is the date and time when the transaction started, for example, the date and time when the cart information 503 was generated. The transaction start date and time may be the registration date and time of one product item, specifically, the date and time when the registered product information (registered product 1: XX medium-thick sauce) shown in FIG. 5(C) was stored. Alternatively, instead of or in addition to the transaction start date and time, the registration date and time for each product may be stored separately.

[0057] The transaction end date and time is the date and time when the transaction ended, specifically, the date and time when the settlement was made. The customer identification information is information that uniquely identifies the customer who performs the transaction, and is the same information as the customer identification information in the customer information 501.

[0058] The registered product information (total) is cumulative information that is updated each time a product is registered. The registered product information (total) includes the number of items (number of products), estimated subtotal amount, subtotal amount, etc. Registered product information (registered product N: N is an integer) includes the number (data number) of the product registered in item N. Registered product information N includes the product code, product name, sales price (shown as "price" in the figure), and the date and time of registration of the product. Specifically, registered product information (registered product 1: XX medium-thick sauce) indicates the product registered in item 1. Registered product information (registered product 2: XX cheese) indicates the product registered in item 2. Note that in the example shown in Figure 5(C), registered product information for items 3 and beyond is omitted from the illustration.

[0059] Next, we will explain reserved product information that indicates reserved products. Reserved products are products that require confirmation by a store clerk. For example, reserved products are classified into categories such as unscanned products, non-file products, products that require age verification, products that require the removal of security tags, and pharmaceuticals.

[0060] An unscanned product is a product that has not been scanned. The mobile terminal device 30 uses the detection results of various sensors to determine that a barcode is being read when the mobile terminal device 30 is tilted and a product is located a certain distance away from the mobile terminal device 30. If the mobile terminal device 30 determines that a barcode is being read but is unable to read it within a predetermined time, it determines that a timeout has occurred. At this time, the captured image of the product is stored as an unscanned product.

[0061] A non-file product is, for example, a product that is not registered in the product master. Specifically, a non-file product is a product that could not be registered because the product code was successfully scanned (not marked as an unscanned product) and the product with that product code was queried from the product master, but the product could not be identified (the product query was rejected).

[0062] Furthermore, products that require age verification, products that require security tags to be removed, and pharmaceuticals are products that are registered by the customer but require confirmation by a store clerk before payment is completed. Specifically, products that require age verification are products that cannot be purchased by minors, such as alcohol and tobacco. Products that require security tags to be removed are products that have security tags attached, such as products over a certain amount. Pharmaceuticals, for example, are products that require explanation from a pharmacist.

[0063] 5C, the reserved product information (total) includes the number of reserved products (unscanned products, non-file products) and the reserved product type. The reserved product type is information indicating the type of reserved product.

[0064] Reserved product information (reserved product N: N is an integer) is information about N reserved products and includes the reserved product type of the N reserved products. In the illustration, reserved product type "1" indicates an unscanned product, and reserved product type "2" indicates a non-filed product. Although not shown, reserved product type "3" indicates a product that requires age verification, reserved product type "4" indicates a product that requires the removal of the security tag, and reserved product type "5" indicates a pharmaceutical product. Reserved product information also includes the registration date and time of the product.

[0065] Furthermore, the pending product information of an unscanned product includes the pending product type "1" as well as image data of the product (image data captured when the mobile terminal device 30 reads the barcode). For example, pending product information (1) includes the pending product type "1 (unscanned product)" and image data.

[0066] Furthermore, the reserved product information of a non-file product includes the reserved product type "2 (non-file product)" as well as the product code read by the mobile terminal device 30. For example, reserved product information (2) includes the reserved product type "2 (non-file product)" and the product code.

[0067] (Initiatives to introduce mobile registration transactions) In the shopping system St, transactions are carried out either by mobile phone registration transactions or by POS registration transactions. Even if a store has introduced mobile phone registration transactions, the shopping system St cannot be effectively utilized unless customers install a shopping app on their own mobile terminal devices 30 (customer terminal devices 30a). For this reason, the store is making efforts to encourage customers to install the shopping app on their customer terminal devices 30a using rental terminal devices 30b.

[0068] Although store staff want as many customers as possible to use the rental terminal device 30b, there is a limit to the number of rental terminal devices 30b that can be prepared in the store. Therefore, store staff want to prevent the same customer from using the rental terminal device 30b multiple times. In other words, store staff want customers who use the rental terminal device 30b to install a shopping app on their own customer terminal device 30a as soon as possible. This embodiment makes it possible to efficiently increase the number of customers who use applications. The functional configuration of the shopping system St according to this embodiment will be described below.

[0069] (Functional configuration of the self-payment device 20 and the rental terminal device 30b) The self-checkout apparatus 20 and the rental terminal apparatus 30b each include a control unit. The control unit is realized, for example, by the CPU 201 of the self-checkout apparatus 20 and the CPU 401 of the rental terminal apparatus 30b. That is, the functions of the control unit are realized by the CPUs 201 and 401 each executing an information output program.

[0070] The control unit outputs information (hereinafter referred to as "installation support information") for installing an application (shopping app) for registering products on the customer terminal device 30a using the customer terminal device 30a. The installation support information includes a uniform resource locator (URL) that the customer terminal device 30a acquires to access a site (app distribution server) that distributes the shopping app. When the customer terminal device 30a accesses the app distribution server, the customer terminal device 30a installs the shopping app under the customer's operation.

[0071] The installation support information is coded and is represented, for example, by a two-dimensional code (hereinafter referred to as an "installation code"). The installation code includes unique information (for example, store identification information) that identifies the store where the rental terminal device 30b that generated the installation code is installed. The installation code is displayed on the display of each device. Specifically, the installation code is displayed as an image on the operation display unit 205 of the self-checkout device 20 or on the display 409 of the rental terminal device 30b. The installation code is also output on a receipt. When the customer terminal device 30a reads the installation code using the camera 407, it accesses the application distribution server.

[0072] The installation assistance information does not necessarily have to be coded. For example, the installation assistance information may be displayed as text, such as the URL address of the application distribution server, or may be output by transmission. In other words, the customer terminal device 30a may acquire the URL through an operation input by the customer, or may acquire the URL through communication. The communication may be, for example, Bluetooth (registered trademark), NFC (Near Field Communication), infrared communication, or the like.

[0073] The control unit displays the installation code when the product registration screen transitions to another screen, such as when payment is made or when a support icon (described later) is pressed.

[0074] The control unit also outputs the installation code when settlement is performed. When settlement is performed, for example, when settlement begins or when settlement is completed. When settlement begins, specifically, when the start settlement button (subtotal button) is pressed. When settlement is completed, for example, when the checkout button (current total button) is pressed.

[0075] (Regarding the rental terminal device 30b) A shopping app is installed on the rental terminal device 30b. The shopping app installed on the rental terminal device 30b is installed on the customer terminal device 30a, or is the same app as the shopping app installed on the customer terminal device 30a. The shopping app is installed on the rental terminal device 30b by a store clerk.

[0076] The customer terminal device 30a, on which the shopping app is installed, displays a support icon that accepts the execution of a support tool that supports the customer's shopping. The support icon includes a shopping memo icon that indicates a shopping memo function (shopping memo tool) and a history display icon that indicates a history display function (history display tool) that displays the shopping history. The shopping memo function is a function that accepts the input of memo information about items that the customer will purchase before shopping, for example. The history display function is a function that displays information about previously purchased items (purchase date and time, product name, unit price, etc.).

[0077] In addition to the support icon, the icons displayed on the mobile terminal device 30 also include a product registration icon. The product registration icon is an icon that activates the camera 407 and activates a shopping registration tool that registers and displays products. When the shopping app is launched, the shopping registration tool is launched even if the product registration icon is not pressed.

[0078] The control unit of the rental terminal device 30b displays the same support icon as the support icon displayed on the customer terminal device 30a on the display 409. When the support icon is selected, the rental terminal device 30b displays an installation code on the display 409.

[0079] Furthermore, when a support icon is selected, the control unit of the rental terminal device 30b displays an explanatory image showing an explanation of the support tool corresponding to the selected support on the display 409. Specifically, the explanatory image is an explanatory image about using the memo function or the history display function.

[0080] Furthermore, when a support icon is selected, the control unit of the rental terminal device 30b executes a support tool corresponding to the selected support. For example, the control unit executes the support tool while displaying an explanatory image. However, the control unit may execute the support tool without displaying an explanatory image.

[0081] (An example of processing from product registration to transaction completion in the shopping system St) Fig. 6 is a sequence diagram showing the process flow from product registration to transaction completion in shopping system St. Fig. 6 illustrates the process flow when a customer visits a store, registers a product to be purchased using their own customer terminal device 30a or rental terminal device 30b, and completes the transaction at self-checkout device 20.

[0082] Step S601: First, the mobile terminal device 30 starts up the shopping application. Step S602: The mobile terminal device 30 acquires information that identifies the store (store identification information). Here, an example of how the store identification information is acquired will be described. For example, a two-dimensional code indicating the store identification information (first store identification information) is displayed near the entrance of the store. The two-dimensional code may be displayed on a predetermined display device or may be displayed by printing on a medium. The camera 407 scans the two-dimensional code in response to an operation by the customer. As a result, the mobile terminal device 30 acquires the store identification information. The two-dimensional code may include store identification information for identifying the store.

[0083] Another example of a manner in which store identification information is acquired is the acquisition of location information. For example, the mobile terminal device 30 acquires location information (GPS information) in response to an operation by a customer who visits the store. This location information is used for comparison with the second store identification information and is information that replaces the first store identification information. In addition, the mobile terminal device 30 may acquire location information and connect to the cloud server Sv by starting a shopping app in response to an operation by the customer who visits the store, and may display a screen as an initial screen informing the customer that the mobile terminal device 30 is currently connected to the cloud server Sv.

[0084] The mobile terminal device 30, which has acquired the store identification information, requests the cloud server Sv to start a transaction. Specifically, the mobile terminal device 30 transmits the acquired store identification information and customer identification information to the cloud server Sv. Note that in the case of the rental terminal device 30b, the store identification information may be acquired in advance.

[0085] Step S603: When the cloud server Sv receives customer identification information and store identification information as a request to start a transaction from the mobile terminal device 30, it generates cart information 503 for the transaction. Specifically, as shown in FIG. 5(C), the cloud server Sv generates cart information 503 including cart identification information, transaction start date and time, and customer identification information. More specifically, when the cloud server Sv receives store identification information from the mobile terminal device 30 as a request to start a transaction, it refers to the store information 502 (see FIG. 5(B)) to identify the store identification information. Note that, when the cloud server Sv receives location information from the mobile terminal device 30, it refers to the second store identification information in the store information 502 to identify the store identification information corresponding to the location information. Note that, if the two-dimensional code includes store identification information, the cloud server Sv acquires the store identification information from the received two-dimensional code.

[0086] Furthermore, when the cloud server Sv receives a transaction start request from the mobile terminal device 30, it acquires the current date and issues (assigns) a serial number. Furthermore, the cloud server Sv generates and stores cart identification information by combining the acquired store identification information, the acquired current date, and the issued serial number. Furthermore, when the cloud server Sv receives a transaction start request from the mobile terminal device 30, it stores the current date and time as the transaction start date and time (generation date and time) in the cart information 503. Furthermore, when the cloud server Sv receives a transaction start request from the mobile terminal device 30, it stores the received customer identification information in the cart information 503.

[0087] Step S604: The mobile terminal device 30 scans and registers the product (the barcode attached to the product) in response to the customer's operation. After scanning the product, the mobile terminal device 30 transmits the product code obtained by the scan together with the cart identification information to the cloud server Sv.

[0088] Step S605: When the cloud server Sv receives the product code and cart identification information from the mobile terminal device 30, it identifies the cart information 503 that includes the received cart identification information, and updates the registered product information included in the identified cart information 503.

[0089] Step S606: The mobile terminal device 30 returns to step S604 until registration is completed. Completion of registration is, for example, when a settlement start button displayed on the display 409 for accepting the start of settlement is pressed. Step S607: When the registration is completed, the mobile terminal device 30 generates a settlement code and displays it on the display 409.

[0090] Step S608: The self-checkout apparatus 20 scans the checkout code displayed on the mobile terminal device 30. The checkout code includes cart identification information and information that enables the self-checkout apparatus 20 to receive cart information 503 from the cloud server Sv. Step S609: After scanning the payment code, the self-checkout apparatus 20 requests the cloud server Sv to send the cart information 503. In the request to send the cart information 503, the self-checkout apparatus 20 transmits the cart identification information included in the payment code to the cloud server Sv.

[0091] Step S610: When the cloud server Sv receives a request to send the cart information 503 from the self-checkout apparatus 20, the cloud server Sv uses the cart identification information to identify the cart information 503. After identifying the cart information 503, the cloud server Sv transmits the cart information 503 to the self-checkout apparatus 20.

[0092] Step S611: When the self-checkout apparatus 20 receives the cart information 503 from the cloud server Sv, it executes a checkout process according to the type of mobile terminal device 30 (customer terminal device 30a or rental terminal device 30b). In the checkout process for the rental terminal device 30b, the self-checkout apparatus 20 displays an installation code on the operation display unit 205 or prints it on a receipt. The self-checkout apparatus 20 uses the customer identification information (or customer name) to determine whether it is the customer terminal device 30a or the rental terminal device 30b. When the self-checkout apparatus 20 executes the checkout process, it transmits a transaction completion notification including the cart identification information to the cloud server Sv.

[0093] Step S612: When the cloud server Sv receives the transaction completion notification from the self-checkout apparatus 20, it extracts the cart identification information from the transaction completion notification. The cloud server Sv then stores the transaction completion date and time (checkout date and time) of the cart information 503 that includes the cart identification information, and transmits the transaction completion notification to the mobile terminal device 30.

[0094] Step S613: When the mobile terminal device 30 receives the transaction completion notification from the cloud server Sv, it deletes the products registered in the mobile terminal device 30 and terminates the shopping app. Note that the mobile terminal device 30 may delete the products registered in the mobile terminal device 30 and terminate the shopping app after displaying the settlement code in step S607. In this case, the cloud server Sv may not perform the process of transmitting the transaction completion notification (step S612).

[0095] In steps S604 and S605, the mobile terminal device 30 transmits a product code to the cloud server Sv and receives product information corresponding to the product code. Upon receiving the product information, the mobile terminal device 30 stores the product information in memory 404. In this embodiment, upon receiving the product information, the mobile terminal device 30 is configured not to communicate with the cloud server Sv. For example, even if the mobile terminal device 30 accepts a quantity change or cancellation, the mobile terminal device 30 is configured not to transmit the product information to the cloud server Sv. This is because, if the mobile terminal device 30 communicates with the cloud server Sv every time it accepts an operation such as a quantity change or cancellation, the communication volume would be large. When generating a settlement code, the mobile terminal device 30 transmits product information for registered products to the cloud server Sv in a lump.

[0096] For example, if there is Wi-Fi (registered trademark) within the store to which the mobile terminal device 30 can connect and the communication volume of the mobile terminal device 30 is not taken into consideration, the mobile terminal device 30 may be configured to communicate with the cloud server Sv at all times.

[0097] (Processing performed by the mobile terminal device 30 while the shopping app is running) Next, the process performed by the mobile terminal device 30 while the shopping application is running will be described with reference to FIGS.

[0098] (Processing performed by the customer terminal device 30a while the shopping application is running) Fig. 7 is a flowchart showing an example of processing performed by the customer terminal device 30a while the shopping application is running. In Fig. 7, the customer terminal device 30a determines whether the shopping application is running (step S701). The customer terminal device 30a waits until the shopping application is running (step S701: NO). When the shopping application is running (step S701: YES), the customer terminal device 30a determines whether the product registration icon has been pressed (step S702). Note that when the application is running, even if the product registration icon is not pressed, the product registration tool, which is a function for starting the camera 407 and registering products, is launched.

[0099] If the product registration icon is not pressed (step S702: NO), the customer terminal device 30a proceeds to step S704. If the product registration icon is pressed (step S702: YES), the customer terminal device 30a activates the product registration tool, that is, activates the camera 407 to scan the product (step S703).

[0100] The customer terminal device 30a then determines whether the shopping memo icon has been pressed (step S704). If the shopping memo icon has not been pressed (step S704: NO), the customer terminal device 30a proceeds to step S706. If the shopping memo icon has been pressed (step S704: YES), the customer terminal device 30a launches the shopping memo tool, i.e., accepts input of a shopping memo (step S705).

[0101] The customer terminal device 30a then determines whether the history display icon has been pressed (step S706). If the history display icon has not been pressed (step S706: NO), the customer terminal device 30a proceeds to step S708. If the history display icon has been pressed (step S706: YES), the customer terminal device 30a launches the history display tool, i.e., displays the shopping history (step S707).

[0102] Next, the customer terminal device 30a determines whether the settlement button has been pressed (step S708). If the settlement button has not been pressed (step S708: NO), the customer terminal device 30a proceeds to step S710. If the settlement button has been pressed (step S708: YES), the customer terminal device 30a generates a settlement code and displays it on the display 409 (step S709).

[0103] Next, the customer terminal device 30a determines whether or not a transaction completion notification has been received from the cloud server SV (step S710). If a transaction completion notification has not been received from the cloud server SV (step S710: NO), the customer terminal device 30a proceeds to step S712. If a transaction completion notification has been received from the cloud server SV (step S710: YES), the customer terminal device 30a deletes the registered product (step S711).

[0104] Next, the customer terminal device 30a determines whether the shopping application has been terminated (step S712). If the shopping application has not been terminated (step S712: NO), the customer terminal device 30a returns to step S702. If the shopping application has been terminated (step S712: YES), the customer terminal device 30a terminates the series of processes.

[0105] (Processing performed by the rental terminal device 30b while the shopping application is running) Fig. 8 is a flowchart showing an example of processing performed by the rental terminal device 30b while a shopping application is running. In Fig. 8, the rental terminal device 30b determines whether the shopping application is running (step S801). The rental terminal device 30b waits until the shopping application is running (step S801: NO), and when the shopping application is running (step S801: YES), it determines whether the product registration icon has been pressed (step S802). Note that when the application is started, the product registration tool is started even if the product registration icon is not pressed.

[0106] If the product registration icon is not pressed (step S802: NO), the rental terminal device 30b proceeds to step S804. If the product registration icon is pressed (step S802: YES), the rental terminal device 30b starts the product registration tool, that is, starts the camera 407 and scans the product (step S803).

[0107] The lending terminal 30b then determines whether the shopping memo icon has been pressed (step S804). If the shopping memo icon has not been pressed (step S804: NO), the lending terminal 30b proceeds to step S809. If the shopping memo icon has been pressed (step S804: YES), the lending terminal 30b displays an installation code on the display 409 (step S805). Then, the lending terminal 30b determines whether the trial use button, which indicates trial use of the shopping memo tool, has been pressed (step S806).

[0108] If the trial use button is not pressed (step S806: NO), the rental terminal 30b proceeds to step S809. If the trial use button is pressed (step S806: YES), the rental terminal 30b activates the shopping memo tool, that is, accepts the input of a shopping memo (step S807). At this time, the rental terminal 30b displays an explanatory image of the shopping memo tool (step S808).

[0109] The lending terminal device 30b then determines whether the history display icon has been pressed (step S809). If the history display icon has not been pressed (step S809: NO), the lending terminal device 30b proceeds to step S814. If the history display icon has been pressed (step S809: YES), the lending terminal device 30b displays an installation code on the display 409 (step S810). Then, the lending terminal device 30b determines whether the trial use button, which indicates trial use of the history display tool, has been pressed (step S811).

[0110] If the trial use button is not pressed (step S811: NO), the rental terminal device 30b proceeds to step S814. If the trial use button is pressed (step S811: YES), the rental terminal device 30b starts the history display tool, i.e., displays the shopping history (step S812). At this time, the rental terminal device 30b displays an explanatory image of the history display tool (step S813).

[0111] Next, the rental terminal device 30b determines whether the settlement button has been pressed (step S814). If the settlement button has not been pressed (step S814: NO), the rental terminal device 30b proceeds to step S816. If the settlement button has been pressed (step S814: YES), the rental terminal device 30b generates a settlement code and displays it on the display 409 (step S815).

[0112] Next, the rental terminal device 30b determines whether or not a transaction completion notification has been received from the cloud server Sv (step S816). If a transaction completion notification has not been received from the cloud server Sv (step S816: NO), the rental terminal device 30b proceeds to step S819. If a transaction completion notification has been received from the cloud server Sv (step S816: YES), the rental terminal device 30b deletes the registered product (step S817).

[0113] Then, the rental terminal device 30b displays an installation code at the end before returning the item (step S818). Next, the rental terminal device 30b determines whether the shopping app has been terminated (step S819). If the shopping app has not been terminated (step S819: NO), the rental terminal device 30b returns to step S802. If the shopping app has been terminated (step S819: YES), the rental terminal device 30b terminates the series of processes.

[0114] (Example of a screen displayed on the mobile terminal device 30) Next, examples of screens displayed on the customer terminal device 30a and the rental terminal device 30b will be described with reference to Fig. 9 to Fig. 12. First, an example of a screen displayed on the customer terminal device 30a when using a shopping memo tool will be described with reference to Fig. 9. FIG. 9 is an explanatory diagram showing an example of a screen displayed on the customer terminal device 30a when using the shopping memo tool.

[0115] 9A shows a product registration screen 910 displayed on the customer terminal device 30a when the product registration tool is launched. The product registration screen 910 includes an imaging area 911, a total display area 912, a checkout start button 913, a registered product display area 914, and icons 915 (915a, 915b, 915c).

[0116] The imaging area 911 is an area where the barcode attached to the product can be captured using the function of the camera 407 of the mobile terminal device 30. The total display area 912 is an area where the total number of registered products and the total price are displayed. The checkout start button 913 is a button that is used to complete registration and receive instructions to start the checkout procedure.

[0117] The registered product display area 914 is an area where the product name, quantity, price, etc. of the registered product are displayed. The registered products are displayed in the order in which they were registered in the registered product display area 914. Specifically, the most recently registered product is displayed at the top of the registered product display area 914.

[0118] The icons 915 include a product registration icon 915a, a shopping memo icon 915b, and a history display icon 915c. On the product registration screen 910, the product registration icon 915a is on, which indicates that the product registration tool is running. When the shopping memo icon 915b is pressed on the product registration screen 910, the screen transitions to a shopping memo screen 920 shown in FIG. 9(B).

[0119] 9(B) shows a shopping memo screen 920 displayed on the customer terminal device 30a when the shopping memo tool is activated. The shopping memo screen 920 includes an input field 921. On the shopping memo screen 920, the shopping memo icon 910b is on, which indicates that the shopping memo tool is activated. When the input field 921 is pressed (tapped) on the shopping memo screen 920, the screen transitions to an input screen 930 shown in FIG. 9(C).

[0120] FIG. 9(C) shows an input screen 930 for inputting characters into input fields 921. The input screen 930 includes input fields 921 (921a, 921b, 921c) and an input button 931. Before shopping, a customer uses the input button 931 to input items to be purchased into the input fields 921. An additional input field 921 is displayed once the input of items is complete. For example, once the customer has completed input of items to be purchased into input field 921b, a new input field 921c is displayed. When an area other than the input field 921 and input button 931 is pressed, the screen transitions to an input completion screen 940 shown in FIG. 9(D).

[0121] 9(D) shows an input completion screen 940 when input into the input field 921 is complete. The input completion screen 940 includes the input field 921, a deletion acceptance button 941, and a check input field 942. When the check input field 942 is pressed, a check image is displayed in the check input field 942. When the deletion acceptance button 941 is pressed with a check image displayed in the check input field 942, the product corresponding to the check input field 942 is deleted. When the product registration icon 915a or the history display icon 915c is pressed on the input completion screen 940, the shopping memo tool is terminated.

[0122] The content displayed on the input completion screen 940 is saved. Specifically, when the input completion screen 940 is closed, another tool or another app is launched, and then the shopping memo tool is launched again, the input completion screen 940 that was last displayed is displayed. This allows the customer to use the shopping memo tool at home or the like to enter notes, and then launch the shopping memo tool in a store to refer to the notes. In addition, products entered in the shopping memo can be deleted during shopping. Therefore, when the customer actually adds a product to the shopping cart, the memo corresponding to that product can be deleted. This allows for efficient shopping.

[0123] (Example of a screen displayed on the rental terminal device 30b when using the shopping memo tool) FIG. 10 is an explanatory diagram showing an example of a screen displayed on the rental terminal device 30b when using the shopping memo tool.

[0124] Fig. 10(A) shows a product registration screen 1010 displayed on the rental terminal device 30b when the product registration tool is launched. The product registration screen 1010 is the same as the product registration screen 910 shown in Fig. 9(A). When the shopping memo icon 915b is pressed in Fig. 10(A), the screen transitions to an installation recommendation screen 1020 shown in Fig. 10(B).

[0125] 10(B) shows an installation recommendation screen 1020 displayed on the rental terminal device 30b. The installation recommendation screen 1020 includes installation guidance 1021, an installation code 1022, and a trial use button 1023. The installation guidance 1021 indicates that the rental terminal device 30b is a loaned item and therefore the shopping memo tool cannot be used, and encourages the customer to install a shopping app on the customer terminal device 30a owned by the customer.

[0126] The installation code 1022 is a code that is scanned by the customer terminal device 30a owned by the customer to install the shopping app on the customer terminal device 30a. The trial use button 1023 is a button that accepts the start of trial use of the shopping memo tool. When the trial use button 1023 is pressed on the installation recommendation screen 1020, the screen transitions to the screen shown in FIG. 10(C).

[0127] Fig. 10(C) shows a trial use screen 1030 of the shopping memo tool. The trial use screen 1030 includes an explanation image 1031, an input field 921, and an input button 931. The explanation image 1031 shows an explanation of the functions of the shopping memo tool, for example, an explanation for inputting characters into the input field 921. When the input is completed, the screen transitions to an input completion screen 940 shown in Fig. 10(D).

[0128] 10(D) shows an input completion screen 1040 when input into the input field 921 is complete. The input completion screen 1040 includes an explanatory image 1041, the input field 921, and a delete acceptance button 941. The explanatory image 1041 shows an explanation that the checked product can be deleted by checking the check input field 942. When the product registration icon 915a or the history display icon 915c is pressed on the input completion screen 1040, the shopping memo tool is terminated.

[0129] (Example of a screen displayed on the customer terminal device 30a when using the history display tool) FIG. 11 is an explanatory diagram showing an example of a screen displayed on the customer terminal device 30a when the history display tool is used. Fig. 11(A) shows a product registration screen 1110 displayed on the customer terminal device 30a when the product registration tool is launched. The product registration screen 1110 is the same as the product registration screen 910 shown in Fig. 9(A). When the history display icon 915c is pressed in Fig. 11(A), the screen transitions to a history selection screen 1120 shown in Fig. 11(B).

[0130] 11(B) shows a history selection screen 1120 displayed on the customer terminal device 30a when the history display tool is activated. The history selection screen 1120 includes a date and time display 1121 and a check input field 1122. On the history selection screen 1120, the history display icon 915c is on, which indicates that the history display tool is activated. The check input field 1122 is displayed corresponding to the date and time display 1121. When any of the check input fields 1122 is pressed on the history selection screen 1120, the screen transitions to a history display screen 1130 shown in FIG. 11(C).

[0131] FIG. 11(C) shows a history display screen 1130. The history display screen 1130 displays information about products purchased by a customer on a certain date and time. Specifically, the history display screen 1130 displays the purchase date and time, product name, and unit price. The history display screen 1130 allows a customer to check products purchased in the past and the prices at which they were purchased in the past. When the product registration icon 915a or shopping memo icon 915b is pressed on the history display screen 1130, the history display tool closes.

[0132] (Example of a screen displayed on the rental terminal device 30b when using the history display tool) FIG. 12 is an explanatory diagram showing an example of a screen displayed on the rental terminal device 30b when the history display tool is used. Fig. 12(A) shows a product registration screen 1210 displayed on the rental terminal device 30b when the product registration tool is launched. The product registration screen 1210 is the same as the product registration screen 910 shown in Fig. 9(A). When the history display icon 915c is pressed in Fig. 12(A), the screen transitions to an installation recommendation screen 1220 shown in Fig. 12(B).

[0133] 12(B) shows an installation recommendation screen 1220 displayed on the rental terminal device 30b. The installation recommendation screen 1220 includes installation guidance 1221, an installation code 1222, and a trial use button 1223. The installation guidance 1221 indicates that the rental terminal device 30b is a loaned item and therefore the history display tool cannot be used, and encourages the customer to install a shopping app on the customer terminal device 30a owned by the customer.

[0134] The installation code 1222 is a code that is scanned by the customer terminal device 30a owned by the customer to install the shopping app on the customer terminal device 30a. The trial use button 1223 is a button that accepts the start of trial use of the history display tool. When the trial use button 1223 is pressed on the installation recommendation screen 1220, the screen transitions to the screen shown in FIG. 12(C).

[0135] 12(C) shows a trial use screen 1230 of the history display tool. The trial use screen 1230 includes an explanatory image 1231, a date and time display 1121, and a check input field 1122. The explanatory image 1131 explains the function of the history display tool, for example, by prompting the user to select a date. When any of the check input fields 1122 is pressed on the trial use screen 1230, the screen transitions to a history display screen 1240 shown in FIG. 12(D).

[0136] 12(D) shows a history display screen 1240. The history display screen 1130 displays information about products purchased on a certain date and time. Specifically, the history display screen 1130 includes an explanatory image 1241. The explanatory image 1241 displays an explanation that past shopping history can be displayed. When the product registration icon 915a or the shopping memo icon 915b is pressed on the history display screen 1130, the history display tool closes.

[0137] (Example of a screen displayed on the self-payment device 20) Next, with reference to FIG. 13, examples of screens displayed on the self-checkout apparatus 20 for a mobile registration transaction using the customer terminal device 30a and a mobile registration transaction using the rental terminal device 30b will be described. FIG. 13 is an explanatory diagram showing an example of a screen displayed on the self-checkout apparatus 20 in a mobile registration transaction.

[0138] 13(A) shows a payment completion screen 1310 that is displayed on the self-checkout apparatus 20 when payment is completed for a mobile registration transaction using the customer terminal device 30a. The payment completion screen 1310 indicates that the transaction has been completed and displays the benefits (e.g., member points) that can be earned for this purchase.

[0139] 13(B) shows a payment completion screen 1320 that is displayed on the self-checkout apparatus 20 when payment is completed for a mobile registration transaction using the rental terminal device 30b. The payment completion screen 1320 indicates that the transaction has been completed. The payment completion screen 1320 also includes an installation guide 1321 and an installation code 1322. The installation guide 1321 prompts the customer to install a shopping app on the customer terminal device 30a owned by the customer, and also indicates, for example, that installing the shopping app will result in the customer receiving a special benefit.

[0140] The installation code 1322 is a code that is scanned by the customer terminal device 30a owned by the customer to install the shopping app on the customer terminal device 30a. Note that the installation guide 1321 and the installation code 1322 are not limited to being displayed after the payment is completed, but may be displayed before the payment is completed, such as immediately after the payment code is scanned or during the payment.

[0141] (Example of a receipt for a mobile phone registration transaction) Next, with reference to FIG. 14, the receipts issued in a mobile registration transaction using the customer terminal device 30a and in a mobile registration transaction using the rental terminal device 30b will be described. FIG. 14 is an explanatory diagram showing an example of a receipt issued by the self-checkout apparatus 20 in a mobile registration transaction.

[0142] 14(A) shows a receipt 1410 issued by the self-checkout apparatus 20 in a mobile registration transaction using the customer terminal device 30a. The receipt 1410 is a normal receipt.

[0143] FIG. 14(B) shows a receipt 1420 issued by the self-checkout apparatus 20 when settlement is completed for a mobile registration transaction using the rental terminal apparatus 30b. In addition to the contents of the receipt 1410, the receipt 1420 includes installation instructions 1421 and an installation code 1422. The installation instructions 1421 prompt the customer to install a shopping app on the customer terminal apparatus 30a owned by the customer, and also indicate, for example, that installing the shopping app will earn the customer a special benefit. The installation code 1422 is a code that is scanned by the customer terminal apparatus 30a owned by the customer to install the shopping app on the customer terminal apparatus 30a.

[0144] (Regarding POS registered transactions) Next, a POS registration transaction will be described. The configuration of the combined POS terminal device 40 will be described with reference to Figures 15 and 16. Figure 15 is an explanatory diagram showing an example of installation of the combined POS terminal device 40. Fig. 16 is a block diagram showing the hardware configuration of the dual-purpose POS terminal device 40. In Fig. 15 and Fig. 16, the same parts are denoted by the same reference numerals.

[0145] An example of the configuration of the dual-purpose POS terminal 40 shown in Fig. 16 will be described below with reference to Fig. 15. The dual-purpose POS terminal 40 includes a CPU 1501, a ROM 1502, a RAM 1503, a hard disk 1504, a customer display unit 1505, a customer scanner unit 1506, a card payment unit 1508, a change dispenser 1509, a store clerk display unit 1510, a key operation unit 1511, a store clerk scanner unit 1512, a printing unit 1513, an audio output unit 1514, a communication unit 1515, and a camera 1516. These components can communicate with each other via a bus.

[0146] The CPU 1501 is a central processing unit that reads and executes various programs stored in the ROM 1502 to control the operation of the dual-purpose POS terminal device 40. The various programs include an information output program according to this embodiment. The ROM 1502 is a read-only memory that stores various types of information used by the CPU 1501, including programs.

[0147] The RAM 1503 is a readable and writable memory that stores various information. For example, the RAM 1503 stores information acquired from the outside (e.g., a product master acquired from the store controller 10) and information generated during processing. This information includes, for example, registration information generated during a registration process for registering products and settlement information generated during a settlement process for settling (paying for) the registered products.

[0148] The hard disk 1504 stores various types of information. For example, the hard disk 1504 stores imaging results (e.g., video) captured by the camera 1516. The hard disk 1504 may store various programs, such as an information output program executed by the CPU 1501, instead of the ROM 1502. Furthermore, instead of the RAM 1503, the hard disk 1504 may store information acquired from the outside or information generated during processing.

[0149] The customer-side display unit 1505 is a touch display for customers, and displays various information to customers and accepts various inputs from customers.

[0150] The customer-side scanner unit 1506 is a scanner unit for customers, and optically reads various types of information. For example, the customer-side scanner unit 1506 optically reads barcodes (product codes, etc.) attached to products and codes printed on receipts. The customer-side scanner unit 1506 can also read a payment code displayed on the mobile terminal device 30. When the payment code is read by the customer-side scanner unit 1506, the dual-purpose POS terminal device 40 can perform payment based on the read content.

[0151] The card settlement unit 1508 is a settlement mechanism using various cards (credit cards, prepaid cards such as transportation cards, point cards, etc.). The change machine 1509 is a cash settlement mechanism, and has an insertion slot for bills and coins and an ejection slot for bills and coins.

[0152] The clerk display unit 1510 is a touch display for the clerk. The clerk display unit 1510 displays various information to the clerk and accepts various inputs from the clerk. The clerk display unit 1510 displays preset keys corresponding to products, and the product is registered when the clerk presses the preset keys. The clerk display unit 1510 also displays a subtotal key that accepts completion of product registration.

[0153] The key operation unit 1511 is made up of various keys (hardware keys, buttons). The key operation unit 1511 accepts various inputs from the store clerk. Specifically, the key operation unit 1511 includes a mode switching button. The mode switching button is a button that can switch to a destination mode in a predetermined order each time it is pressed.

[0154] The store clerk scanner unit 1512 is a scanner unit for store clerks and optically reads various types of information. For example, the store clerk scanner unit 1512 optically reads barcodes attached to products and store clerk codes attached to the store clerk's name tags.

[0155] The printing unit 1513 prints and outputs various media (receipts, invoices, bills, etc.). The printing unit 1513 can change the direction of the media issuing slot. Specifically, the printing unit 1513 has a rotatable mechanism and is configured so that the media issuing slot faces from the store clerk side to the customer side, and from the customer side to the store clerk side.

[0156] The audio output unit 1514 outputs audio. For example, the audio output unit 1514 outputs audio guidance, warning sounds, etc. The audio guidance and warning sounds are related to product registration and payment. The communication unit 1515 is an interface for transmitting and receiving information to and from other devices (the store controller 10, the transaction status management device 11, and other multipurpose POS terminal devices 40).

[0157] Camera 1516 is attached to the upper right of customer display unit 1505 when viewed from the customer side. Camera 1516 is a camera that continuously captures video or still images. Camera 1516 captures, for example, the customer's operational status during registration and payment. Specifically, camera 1516 captures the actions taken during product registration, such as the contents (products) of the shopping carts on the counters provided on both sides of dual-purpose POS terminal device 40 and the customer's operational status during registration. Camera 1516 also captures the actions taken during payment, such as the bills and coins held by the customer, the change dispenser 1509, and hand movements.

[0158] (Functional configuration with the dual-purpose POS terminal device 40) The dual-purpose POS terminal 40 includes a control unit. The control unit is realized by the CPU 1501 of the dual-purpose POS terminal 40. That is, the CPU 1501 executes an information output program to realize the functions of the control unit.

[0159] The control unit outputs the installation support information. Specifically, the control unit displays the installation code on the customer side display unit 1505 according to the conditions. The conditions are the following conditions 1 to 7.

[0160] Condition 1: The control unit displays the installation code in response to an operation by the store clerk. Specifically, when the store clerk presses a predetermined button displayed on the store clerk display unit 1510 or a predetermined key located on the key operation unit 1511, the control unit displays the installation code. On the other hand, when the button is not pressed, the control unit does not display the installation code.

[0161] Condition 2: The control unit displays the installation code in response to the customer's operation. Specifically, when the customer presses a predetermined button displayed on the customer-side display unit 1505, the control unit displays the installation code. On the other hand, when the customer does not press the button, the control unit does not display the installation code.

[0162] Condition 3: The control unit displays an installation code depending on the product being purchased. Specifically, the control unit displays an installation code when the product being purchased includes a specific product, and does not display an installation code when the product being purchased does not include the specific product. The specific product is a pre-set product, such as a product whose purchase you do not want others, including store clerks, to know about. Specifically, the specific product is, for example, sanitary products, contraceptive products, magazines for young people, or products needed due to a health or physical condition.

[0163] Condition 4: The control unit displays the installation code according to the customer's store visit frequency. Specifically, the control unit displays the installation code when the store visit frequency is equal to or greater than a threshold, and does not display the installation code when the store visit frequency is less than the threshold.

[0164] Condition 5: The control unit displays the installation code according to the time period. Specifically, the control unit displays the installation code when the current date and time is within a preset busy period, and does not display the installation code when the current date and time is within a preset off-peak period.

[0165] Condition 6: The control unit displays the installation code according to the number of times the installation code has been output in the past. Specifically, the control unit displays the installation code if the number of times the installation code has been output within a predetermined period in the past is equal to or less than a threshold, and does not display the installation code if the number of times the installation code has been output exceeds the threshold.

[0166] Condition 7: The control unit displays the installation code according to the rental record of the rental terminal device 30b. Specifically, the control unit displays the installation code when the rental record of the rental terminal device 30b is equal to or less than a threshold, and does not display the installation code when the rental record exceeds the threshold.

[0167] (Example of processing performed by the dual-purpose POS terminal device 40) Next, the process performed by the combined POS terminal device 40 will be described with reference to FIGS. 17 is a flowchart showing an example of processing performed by the combined POS terminal device 40. First, the combined POS terminal device 40 performs a code display process (see FIG. 18(A)) to display an installation code according to conditions 1 to 7 (step S1701). Then, the combined POS terminal device 40 determines whether the barcode of the first item has been scanned (step S1702). If the barcode of the first item has not been scanned (step S1702: NO), the combined POS terminal device 40 returns to step S1701. If the barcode of the first item has been scanned (step S1702: YES), the combined POS terminal device 40 registers the item (step S1703).

[0168] Then, the combined POS terminal device 40 performs a code display process (see FIG. 18(A)) (step S1704). Next, the combined POS terminal device 40 determines whether the barcodes of the second and subsequent items have been scanned (step S1705). If the barcodes of the second and subsequent items have been scanned (step S1705: YES), the combined POS terminal device 40 returns to step S1703.

[0169] If the barcodes of the second and subsequent items are not scanned (step S1705: NO), the combined POS terminal device 40 determines whether the subtotal button has been pressed (step S1706). If the subtotal button has not been pressed (step S1706: NO), the combined POS terminal device 40 returns to step S1704. On the other hand, if the subtotal button has been pressed (step S1706: YES), the combined POS terminal device 40 performs code display processing (see FIG. 18(A)) (step S1707).

[0170] Next, the combined POS terminal device 40 accepts coins inserted by the customer into the change dispenser 1509 (step S1708). Then, the combined POS terminal device 40 determines whether the inserted amount is equal to or greater than the total amount (step S1709). If the inserted amount is not equal to or greater than the total amount (step S1709: NO), the combined POS terminal device 40 returns to step S1707.

[0171] If the deposited amount is equal to or greater than the total amount (step S1709: YES), the combined POS terminal 40 determines whether the checkout button (a button that confirms the deposit and advances the process) has been pressed (step S1710). If the checkout button has not been pressed (step S1710: NO), the combined POS terminal 40 returns to step S1707.

[0172] If the checkout button is pressed (step S1710: YES), the combined POS terminal device 40 performs a receipt issuing process (see FIG. 18(B)) (step S1711) and ends the series of processes. When issuing a receipt, the combined POS terminal device 40 also dispenses change if any is due.

[0173] (An example of information output processing performed by the dual-purpose POS terminal device 40) Fig. 18 is a flowchart showing an example of information output processing performed by the dual-purpose POS terminal device 40. Fig. 18(A) is a flowchart showing an example of code display processing (steps S1701, 1704, 1707 in Fig. 17) as information output processing.

[0174] In FIG. 18(A), the combined POS terminal device 40 determines whether the value of the information output flag is 1 (step S1801). The information output flag is information that is set (the value is set to 1) when it is determined that an installation code should be displayed. The value of the information output flag is 0 at the start of each transaction. If the value of the information output flag is 1 (step S1801: YES), the combined POS terminal device 40 proceeds to step S1804.

[0175] If the value of the information output flag is not 1 (step S1801: NO), the combined POS terminal 40 determines whether or not it is necessary to display the installation code (step S1802). In step S1802, the combined POS terminal 40 determines whether or not one or more of the above-mentioned conditions 1 to 7 are met. If it is not necessary to display the installation code (step S1802: NO), the combined POS terminal 40 ends the series of processes (proceeds to FIG. 17).

[0176] If it is necessary to display the installation code (step S1802: YES), the combined POS terminal 40 sets the value of the information output flag to 1 (step S1803). Then, the combined POS terminal 40 displays the installation code on the customer side display unit 1505 (step S1804), and ends the series of processes. Note that in step S1804, if the installation code has already been displayed, the combined POS terminal 40 continues to display the installation code.

[0177] FIG. 18B is a flowchart showing an example of a receipt issuing process (step S1711 in FIG. 17) as an information output process. In FIG. 18B, the dual-purpose POS terminal 40 determines whether the value of the information output flag is 1 (step S1811). If the value of the information output flag is not 1 (step S1811: NO), the dual-purpose POS terminal 40 prints and issues a regular receipt (step S1812) and proceeds to step S1814. If the value of the information output flag is 1 (step S1811: YES), the dual-purpose POS terminal 40 issues a receipt on which an installation code is printed (step S1813). The dual-purpose POS terminal 40 then sets the value of the information output flag to 0 (step S1814) and ends the process.

[0178] According to the flowcharts of Figures 17 and 18, for example, when condition 1 is met (when a store clerk presses a specified button), it is determined that an installation code needs to be displayed (step S1802 in Figure 18(A): YES), and the installation code is displayed (step S1804 in Figure 18(A)), and the installation code can be printed on the receipt (step S1813 in Figure 18(B)).

[0179] (An example of a screen displayed on the display unit of the dual-purpose POS terminal device 40) Next, a screen displayed on the display unit of the dual-purpose POS terminal device 40 will be described with reference to Fig. 19. Note that Fig. 19 will be described taking as an example a screen for face-to-face settlement in the clerk registration mode.

[0180] Fig. 19 is an explanatory diagram showing an example of a screen displayed on the display unit of the combined POS terminal device 40. Fig. 19(A) shows a subtotal screen 1910 as an example of a screen displayed on the store clerk's display unit 1510. The subtotal screen 1910 shows the screen that appears after a store clerk operates the combined POS terminal device 40 to register the products purchased by a certain customer (canned beer, asparagus) and operates the subtotal button.

[0181] The master plan screen 1910 includes a code display button 1911. The code display button 1911 is a button that accepts the start of display of the installation code on the customer display unit 1505 and indicates whether the installation code is currently being displayed or not. When the store clerk presses the code display button 1911 (when condition 1 is met), the installation code is displayed on the customer display unit 1505. At this time, the code display button 1911 is displayed in a display mode that indicates that the installation code is currently being displayed on the customer display unit 1505. Note that even when other conditions (conditions 2 to 7) other than condition 1 are met, the installation code is also displayed on the customer display unit 1505, and in this case, the code display button 1911 is also displayed in a display mode that indicates that the installation code is currently being displayed.

[0182] FIG. 19(B) shows a sub-screen 1920 as an example of a screen displayed on the customer display unit 1505. The sub-screen 1920 includes an installation guide 1921 and an installation code 1922. The installation guide 1921 indicates the time (xx minutes) required for registration on the dual-purpose POS terminal device 40, that the time (xx minutes) will be eliminated if mobile registration transactions are used, and encourages the customer to install a shopping app on the customer terminal device 30a owned by the customer. The installation code 1922 is a code that is scanned by the customer terminal device 30a owned by the customer to install the shopping app on the customer terminal device 30a.

[0183] 19 has been described using an example of a screen for face-to-face settlement in clerk registration mode, but the installation code can also be displayed on customer display unit 1505 in full self-service mode and checkout-only mode. For example, in full self-service mode, the installation code may be displayed on at least one of the product registration screen, the sub-screen, and the screen displayed after checkout is complete. In checkout-only mode, the installation code may be displayed before checkout is complete, after checkout is complete, or both before and after checkout is complete.

[0184] (Example of a receipt for a POS registered transaction) Next, a receipt issued by the dual-purpose POS terminal device 40 in a POS registration transaction will be described with reference to FIG. FIG. 20 is an explanatory diagram showing an example of a receipt issued by the dual-purpose POS terminal device 40 in a POS registration transaction.

[0185] The receipt 2010 shown in Figure 20(A) includes an installation guide 2011 and an installation code 2012. The installation guide 2011 indicates the time (xx minutes) required for registration on the dual-purpose POS terminal device 40, that the time (xx minutes) will be eliminated if a mobile registration transaction is used, and a message urging the customer to install a shopping app on the customer terminal device 30a owned by the customer. The installation code 2012 is a code that is scanned by the customer terminal device 30a owned by the customer to install the shopping app on the customer terminal device 30a.

[0186] The receipt 2020 shown in FIG. 20(B) is a receipt issued by the dual-purpose POS terminal device 40 when a specific product (for example, a product that you do not want others, including store clerks, to know about) is purchased. The receipt 2020 includes an installation guide 2021 and an installation code 2022. The installation guide 2021 indicates that the specific product can be purchased without others knowing when using a mobile registration transaction. The installation code 2022 is the same as the installation code 2012 in FIG. 20(A).

[0187] As described above, the store terminal device 1 (self-checkout device 20, rental terminal device 30b, and dual-purpose POS terminal device 40) according to this embodiment is configured to output installation support information for prompting the customer terminal device 30a to install a shopping app. This allows the store terminal device 1 used by the customer to output the installation support information, thereby efficiently encouraging the customer to install the shopping app. This therefore efficiently increases the number of customers who use the shopping app, allowing for effective use of the mobile registration transaction system.

[0188] Furthermore, the store terminal device 1 according to this embodiment is configured to display an image (installation code) that encodes the installation support information when transitioning from the product registration screen to another screen. This allows the user to easily install the shopping app from the display screen when the screen transitions, thereby more efficiently encouraging the user to install the shopping app.

[0189] Furthermore, the store terminal device 1 according to this embodiment is configured to output installation support information when making a payment. This allows the store terminal device 1 to prompt the customer to install a shopping app when making a payment. This allows, for example, a customer who is waiting in a queue for a POS registration transaction to be efficiently prompted to install the shopping app when making a payment. Furthermore, since the installation support information can be printed on a receipt, the customer can be prompted to install the shopping app even at home.

[0190] In addition, the rental terminal device 30b according to this embodiment is assumed to have a shopping app installed. This allows installation support information to be presented to customers who are using the shopping app using the rental terminal device 30b and are willing to use the shopping app. This allows for more efficient promotion of the installation of the shopping app.

[0191] Furthermore, the rental terminal device 30b according to this embodiment displays the same support icon as the support icon displayed on the customer terminal device 30a on which the shopping app is installed, and when the support icon is selected, installation support information is displayed. This can motivate customers to use the shopping app and ensure that opportunities to install the shopping app are not missed. Therefore, installation of the shopping app can be promoted more efficiently.

[0192] Furthermore, when a support icon is selected, the rental terminal device 30b according to this embodiment displays an explanatory image that explains the support tool. This makes it possible to appeal to customers that the support tool makes shopping more convenient. This further encourages the installation of the shopping app.

[0193] Furthermore, when a support icon is selected, the rental terminal device 30b according to this embodiment executes the support tool corresponding to the support icon. This allows the customer to use the support tool, which can motivate the customer to use the shopping app. Therefore, the installation of the shopping app can be further encouraged.

[0194] In the above embodiment, the installation support information includes a URL for accessing the application distribution server and store identification information for the store where the rental terminal device 30b that generated the installation code is installed. Therefore, by compiling the installation status, the store can determine which method is effective for promoting shopping app downloads and shift to the method determined to be more effective, thereby more optimally promoting installation. Specifically, the aggregated information may be imported into the shopping system St to control the output of the two-dimensional code. For example, if it is determined that downloads from the installation code displayed on the customer display unit 1505 are going well (e.g., if the number of downloads within a specified period exceeds an initially planned target number), the frequency of outputting the installation code from the customer display unit 1505 may be increased. Furthermore, if it is determined that downloads from the installation code on the receipt are going poorly (e.g., if the number of downloads within a specified period falls short of an initially planned target number), the frequency of outputting the installation code on the receipt may be reduced. For example, in order to avoid excessive solicitation (advertising) for installation and leaving a bad impression on customers, installations that are determined to have little effect may be scaled down or discontinued.

[0195] (Modification of the embodiment) Next, modified examples of the embodiment will be described. Note that in the following modified examples, the content explained in the above-mentioned embodiment will be omitted as appropriate. Furthermore, the following modified examples and the above-mentioned embodiment can be combined with each other.

[0196] (Variation 1) In the above-described embodiment, the support tools (shopping memo tool and history display tool) are executed in the lending terminal device 30b. In variant example 1, a configuration is described in which the support tools are not executed in the lending terminal device 30b. In variant example 1, the lending terminal device 30b does not display the trial use buttons 1023, 1223 (see Figures 10(B) and 12(B)). Furthermore, the lending terminal device 30b may display a button that accepts display of an explanation of the support tool instead of the trial use buttons 1023, 1223. When the button is pressed, the lending terminal device 30b may display an explanatory image that explains the function of the support tool.

[0197] Even if the first modification is adopted, by deliberately not allowing the customer to use the assistance tool, it is possible to stimulate the customer's desire to use the assistance tool. Also, by displaying an explanatory image, it is possible to appeal to the customer that the assistance tool will make shopping more convenient. Therefore, it is possible to encourage the installation of the shopping app.

[0198] (Variation 2) In Modification 2, installation support information is not output at the time of payment or on a receipt to a customer who has installed a shopping app using the rental terminal device 30b. Specifically, the rental terminal device 30b displays a display button on the installation recommendation screen 1020, 1220 (see FIGS. 10(B) and 12(B)), for example, to accept a customer's decision on whether or not to install the app. When the rental terminal device 30b accepts a decision to install the app via the display button, it assumes that the customer using the rental terminal device 30b has installed the shopping app on their customer terminal device 30a, and transmits information to the cloud server Sv indicating that the app has been installed.

[0199] The cloud server Sv manages a flag indicating that installation has been performed, and when it receives information indicating that installation has been performed from the rental terminal device 30b, it turns on the flag.

[0200] When the self-checkout apparatus 20 reads the checkout code of the rental terminal apparatus 30b, it receives checkout information including information about the flag from the cloud server Sv. When the self-checkout apparatus 20 receives the checkout information, if the flag is on, it does not display the installation code 1322 (FIG. 13(B)), but instead displays the checkout completion screen 1310 (see FIG. 13(A)). On the other hand, if the flag is off, the self-checkout apparatus 20 displays the checkout completion screen 1320 (see FIG. 13(B)) displaying the installation code 1322.

[0201] Furthermore, when issuing a receipt, if the flag is on, the self-checkout apparatus 20 does not print the installation code 1422 (FIG. 14(B)), i.e., issues a normal receipt 1410 (see FIG. 14(A)). On the other hand, if the flag is off, the self-checkout apparatus 20 issues a receipt 1420 (see FIG. 13(B)) on which the installation code 1422 is printed.

[0202] According to variant example 2, by using the installation recommendation screens 1020, 1220 (installation codes 1022, 1222) of the rental terminal device 30b, customers who have installed a shopping app on their customer terminal device 30a can be prevented from being prompted to install the shopping app again.

[0203] (Variation 3) In Variation 3, we will explain the installation code displayed while the rental terminal device 30b is charging. When not in use, the rental terminal device 30b is connected to a charger installed at the entrance of the store or the like and charged. If the charge level is low, the device will run out of power in the middle of registering a product. For this reason, the rental terminal device 30b is prevented from being used if the charge level is below a predetermined value.

[0204] FIG. 21 is an explanatory diagram showing an example of a charging screen displayed by the rental terminal device 30b when the charge amount is below a predetermined value. The control unit of the rental terminal device 30b according to the third modification causes the charge amount and installation support information to be output on the same screen. For example, as shown in FIG. 21, a charging screen 2100 is displayed on the display 409. The charging screen 2100 includes a charging notice 2101, an installation notice 2102, and an installation code 2103. The charging notice 2101 indicates the current charge amount and that although charging is in progress, the device cannot be used because the charge amount is below a predetermined value.

[0205] The installation guide 2102 indicates that another rental terminal device 30b will be used and prompts the customer to install the shopping app on the customer terminal device 30a owned by the customer. The installation code 2103 is a code that is scanned by the customer terminal device 30a owned by the customer to install the shopping app on the customer terminal device 30a.

[0206] Although the installation code 2103 in the rental terminal device 30b is displayed when the charge amount is equal to or less than a predetermined value, it may also be displayed when the charge amount exceeds the predetermined amount. In other words, the installation code 2103 may be displayed as long as the device is being charged, regardless of the charge amount.

[0207] The rental terminal device 30b according to the third modification is configured to output the charge amount and installation support information on the same screen. According to the third modification, it is possible to notify the customer whether or not the device can be used depending on the charge amount, and to encourage the customer to install the shopping app using an unused rental terminal device 30b. Therefore, it is possible to effectively utilize the unused rental terminal device 30b.

[0208] (Variation 4) Next, we will explain Modification 4. In the above-mentioned Modification 3, we have explained an example in which an installation code is displayed on the display 409 of a rental terminal device 30b that is unavailable because it is being charged. In Modification 4, an installation code is displayed on a rental terminal device 30b that is sufficiently charged and available for use at any time.

[0209] For example, the installation code may be displayed when the rental terminal device 30b placed on the charger is removed from the charger, i.e., when charging stops and the charge amount exceeds a predetermined amount. The rental terminal device 30b may also display the installation code when the customer declares that they want to start shopping and transitions to a product registration screen. Furthermore, the rental terminal device 30b may display the installation code when registering a product on the product registration screen.

[0210] According to the fourth modification, the customer can be prompted to install the shopping app by using the spare time between the use of the rental terminal device 30b, which makes it possible to more efficiently prompt the customer to install the shopping app.

[0211] The following is a summary of the embodiments. [Title of invention] Store terminal device, information output method, and program [Technical field] The present invention relates to a store terminal device, an information output method, and a program. [Background technology] In recent years, systems have become widespread in which customers are prompted to install a specific application on their mobile terminal devices and use the mobile terminal devices to register products. Stores have made various efforts to encourage customers to install the application on their mobile terminal devices. As a related technology, a system for sending emails to non-member users that prompts them to register on the application has been disclosed (see, for example, Patent Document 1). [Prior art document] [Patent Documents] [Patent Document 1] Patent No. 6164345 [Summary of the Invention] [Problem to be solved by the invention] However, the conventional technology has had the problem that the introduced system is not being effectively utilized. The present invention has been made in view of the above circumstances, and an object of the present invention is to provide a technique for effectively utilizing a system.

[0212] [Means for solving the problem] (1) In order to solve the above-mentioned problems, one aspect of the present invention is a store terminal device that is installed in a store and used by customers in transactions, and is characterized by having a control means that outputs information for installing an application for registering products on the customer terminal device owned by the customer. According to the above configuration, installation support information can be output on the store terminal device 1 used by the customer, so that customers can be efficiently encouraged to install the shopping app. Therefore, the number of customers who use the shopping app can be efficiently increased, and the system related to mobile registration transactions can be effectively utilized.

[0213] (2) In the above configuration (1), the control means may cause the display means to display an image in which the information is coded when transitioning from the product registration screen to another screen. According to the above configuration, when the screen transitions, the shopping app can be easily installed from the display screen, so that the installation of the shopping app can be more efficiently encouraged.

[0214] (3) In the configuration of (1) or (2) above, the control means may be configured to output the amount of charge of the store terminal device and the information on the same screen. According to the above configuration, it is possible to notify the customer whether or not the device can be used depending on the amount of charge, and to encourage the customer to install a shopping app using an unused rental terminal device 30b, thereby making it possible to effectively utilize the unused rental terminal device 30b.

[0215] (4) In the configurations (1) to (3) above, the store terminal device may be a portable terminal device that is lent to customers and has the application installed therein. According to the above configuration, installation support information can be presented to customers who are using a shopping app using the rental terminal device 30b and who are willing to use the app, thereby more efficiently encouraging the installation of the shopping app.

[0216] (5) In the configuration of (4) above, the control means may cause the display means to display an icon that is the same as the icon displayed on the customer terminal device on which the application is installed and that accepts the execution of a support tool that assists the customer in shopping, and when the same icon is selected, cause the display means to display the information. According to the above configuration, it is possible to motivate customers to use the shopping app and to prevent them from missing an opportunity to install the shopping app, thereby more efficiently encouraging the installation of the shopping app.

[0217] (6) In the configuration of (5) above, when the same icon is selected, the control means may cause the display means to display an explanatory image showing an explanation about the support tool. According to the above configuration, it is possible to appeal to customers that the support tool makes shopping more convenient, thereby further encouraging them to install the shopping app.

[0218] (7) In the configuration of (5) or (6) above, the control means may be configured to execute the support tool when the same icon is selected. According to the above configuration, the customer can be made to use the assistance tool, which can motivate the customer to use the shopping app, thereby further encouraging the customer to install the shopping app.

[0219] (8) In order to solve the above-mentioned problems, another aspect of the present invention is an information output method characterized in that a computer used in a store terminal device installed in a store and used by a customer in a transaction executes a process to output information for installing an application for registering products on the customer terminal device owned by the customer. According to the above configuration, installation support information can be output on the store terminal device 1 used by the customer, so that customers can be efficiently encouraged to install the shopping app. Therefore, the number of customers who use the shopping app can be efficiently increased, and the system related to mobile registration transactions can be effectively utilized.

[0220] (9) In order to solve the above-mentioned problems, another aspect of the present invention is a program that executes a process to cause a computer used in a store terminal device installed in a store and used by a customer in a transaction to output information for installing an application for registering products using a customer terminal device owned by the customer into the customer terminal device. According to the above configuration, installation support information can be output on the store terminal device 1 used by the customer, so that customers can be efficiently encouraged to install the shopping app. Therefore, the number of customers who use the shopping app can be efficiently increased, and the system related to mobile registration transactions can be effectively utilized.

[0221] In addition, all or part of the functions (input / output, memory, processing (including judgment)) of the store terminal device 1 (self-checkout device 20, rental terminal device 30b, dual-purpose POS terminal device 40) described above may be realized in a device other than the device described as the entity that executes the function.

[0222] Specifically, the above description has been given of a configuration in which the self-checkout apparatus 20, the rental terminal apparatus 30b, and the dual-purpose POS terminal apparatus 40 are each equipped with a control unit. All or some of the functional units of the control unit may be equipped in another computer device. For example, all or some of the functional units of the control unit may be equipped in the store controller 10, the cloud server SV, or another computer device. Furthermore, the number of computer devices equipped with the functional units of the control unit is not limited to multiple, and may be one. For example, all of the functional units of the control unit may be equipped in a single computer device.

[0223] Specifically, for example, instead of the rental terminal device 30b, the store controller 10 or the cloud server Sv may issue an instruction to output the installation support information.

[0224] In relation to the above, the store terminal device 1 may function as a so-called thin client specialized for the input / output interface when it comes to registering products and settling payments. In other words, the self-checkout device 20, the rental terminal device 30b, and the dual-purpose POS terminal device 40 may accept various inputs (operation by an operator, detection by a device such as a scanner), send the input information (operation information, scan information, etc.) to the cloud server Sv, receive the processing results of the cloud server Sv based on the input information (updated screen information, device control information, etc.), and perform various outputs (display on a display unit, control of a device).

[0225] The program for implementing the above-described store terminal device 1 (self-checkout device 20, rental terminal device 30b, and dual-purpose POS terminal device 40) may be recorded on a computer-readable recording medium and loaded into a computer system for execution. The term "computer system" as used herein includes hardware such as an OS and peripheral devices. The term "computer-readable recording medium" also refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, as well as storage devices such as hard disks built into a computer system. The term "computer-readable recording medium" also includes devices that retain a program for a certain period of time, such as volatile memory (RAM) within a computer system that acts as a server or client when the program is transmitted via a network such as the Internet or a communication line such as a telephone line. The program may also be transmitted from a computer system storing the program in a storage device to another computer system via a transmission medium or by transmission waves within the transmission medium. The term "transmission medium" used to transmit the program refers to a medium capable of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line. The program may also be used to implement some of the functions described above. Furthermore, the above-mentioned functions may be realized in combination with a program already recorded in the computer system, that is, a so-called differential file (differential program). [Explanation of symbols]

[0226] St...Shopping system, Sv...Cloud server, 10...Store controller, 11...Transaction status management device, 20...Self-payment device, 30...Mobile terminal device, 30a...Customer terminal device, 30b...Rental terminal device, 40...Dual-purpose POS terminal device, 201, 401, 1501...CPU, 202, 402, 1502...ROM, 203, 403, 1503...RAM, 204, 1504...Hard disk, 205...Operation display unit, 206...Scanner unit, 216, 407...Camera, 409...Display, 1505...Customer side display unit

Claims

1. A portable store terminal device that is installed in a store and used by customers to register products at the sales floor during transactions, a display means for displaying the image capturing status of the barcode of the product; a control means for causing the display means to display information for installing an application for registering a product using a customer terminal device owned by the customer on the customer terminal device, instead of the image capturing status; A store terminal device characterized by:

2. the control means causes the display means to display an image in which the information is coded when the screen transitions from the product registration screen to another screen.

2. The store terminal device according to claim 1.

3. The store terminal device has the application installed therein.

3. The store terminal device according to claim 1 or 2.

4. the control means causes the display means to display an icon that is the same as the icon displayed on the customer terminal device on which the application is installed and that accepts execution of a support tool that supports the customer's shopping; When the same icon is selected, the information is displayed on the display means.

4. The store terminal device according to claim 3.

5. A portable store terminal computer is installed in a store and used by customers to register products at the sales floor during transactions. a display step for displaying an image capturing status of the barcode of the product; a control step of displaying, in place of the image capturing status, information for installing an application for registering a commodity using a customer terminal device owned by the customer into the customer terminal device in the display step; An information output method comprising:

6. A portable store terminal computer is installed in a store and used by customers to register products at the sales floor during transactions. a display means for displaying the image capturing status of the barcode of the commodity; a control means for displaying, on the display means in place of the image capturing status, information for installing an application for registering a commodity using a customer terminal device owned by the customer into the customer terminal device; A program characterized by functioning as

Images