Program and commodity sales data processing device

Abstract

To provide service using a portable terminal which can be easily used even by a beginner.SOLUTION: A program allows a computer to function as a commodity sales data processing device. The program allows the computer to function as: imaging means for imaging a commodity to be purchased; guiding means for guiding a procedure to an operator using guide images for guiding the procedure; and display means for enabling a captured image by the imaging means to be displayed. The display means displays a part or all of a first guide image as one of the guide images on a captured image display area for displaying the captured image. The guide means completes the guide using the first guide image on the basis of predetermined conditions.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a program and a product sales data processing device.

Background Art

[0002] A self-system has been proposed in which customers themselves register products using a mobile terminal. On the other hand, a system for displaying guidance for an imaging target product is known (see, for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, there are also customers who are not accustomed to the self-system as described above. In the system as described above, such customers cannot be supported.

[0005] The present invention has been made in view of such circumstances, and an object thereof is to provide a technique that enables even beginners to easily use a service using a mobile terminal.

Means for Solving the Problems

[0006] One aspect of the present invention for solving the above-described problems is a program that causes a computer to function as a product sales data processing device, the program causing the computer to function as imaging means for imaging a product to be purchased, guidance means for guiding an operator using a guidance image for guiding a procedure, and display means capable of displaying an image captured by the imaging means, the display means displaying a part or all of a first guidance image that is one of the guidance images in an imaging image display area for displaying the captured image, and the guidance means ending guidance using the first guidance image based on a predetermined condition.

Brief Description of the Drawings

[0007]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

[0008] Fig. 1 is a conceptual diagram of a network for explaining a sales system 1 of this embodiment. The sales system 1 shown in Fig. 1 includes a headquarters server 10, a cloud server 20, a store controller 30 (e.g., a server, etc.), a transaction status management device 40 (e.g., a personal computer, etc.), a settlement device 50, a registered settlement device 51, and a mobile terminal 60.

[0009] The store controller 30, the transaction status management device 40, the settlement device 50, and the registration settlement device 51 are communicatively connected via a LAN 19 (which may be wired or wireless). The sales system 1 can be introduced in various stores (supermarkets, convenience stores, drug stores, home centers, home appliance retailers, etc.).

[0010] In Fig. 1, the number of each device (terminal) is an example. For example, in Fig. 1, "..." is illustrated to the right of the transaction status management device 40, but the number of transaction status management devices 40 installed in one store may be one or more. Also, for example, in Fig. 1, two mobile terminals 60 are illustrated, but the number of mobile terminals 60 used in the store changes depending on the number of customers.

[0011] Sales system 1 provides a self-service (hereinafter, sometimes referred to as service A) in which a customer uses a mobile terminal 60 to register a product and uses a settlement device 50 to settle the payment. In other words, service A is a self-service in which a customer registers a product and settles the payment by himself / herself, using mobile terminal 60 for product registration and using settlement device 50 for settlement.

[0012] In addition to Service A, the sales system 1 also provides other services. For example, as other services, the sales system 1 can provide services in such modes as customers registering and settling accounts for products using the registration and settlement device 51, or services in such modes as store clerks registering products using a registration device (not shown) and customers settling accounts using a settlement device (not shown).

[0013] The head office server 10 is installed outside the store (e.g., at the head office, data center, etc.) and is a server that manages the entire sales system 1. The head office server 10 stores various types of information necessary for the operation of services including Service A (e.g., product master, special sale file, etc.) and performance information of services in the store (e.g., sales performance information, product sales performance information, etc.). The head office server 10 communicates with the cloud server 20 and the store controller 30. The head office server 10 may communicate with other devices (e.g., transaction status management device 40, settlement device 50, etc.). The head office server 10 may be composed of multiple servers.

[0014] The cloud server 20 is installed outside the store (e.g., at a data center, etc.) and is a server that provides Service A. The cloud server 20 stores various types of information necessary for the operation of Service A (e.g., product master, transaction information (also referred to as cart information), etc.). The cloud server 20 communicates with the head office server 10 and the mobile terminal 60. The cloud server 20 may communicate with other devices (e.g., store controller 30, transaction status management device 40, etc.). The cloud server 20 may be composed of multiple servers.

[0015] The store controller 30 is a device that controls the part of the sales system 1 related to the store. The store controller 30 communicates with each device within the LAN 19 (e.g., settlement device 50, etc.) and each device outside the LAN 19 (e.g., head office server 10). For example, the store controller 30 receives the product master and special sale file from the head office server 10 and supplies them to the settlement device 50.

[0016] The transaction status management device 40 is a device that mainly manages (monitors and controls) each device within the LAN 19. For example, the transaction status management device 40 communicates with each device within the LAN 19 and monitors, for example, the processing status, operation status, etc. of each device within the LAN 19. Also, the transaction status management device 40 may communicate with each device outside the LAN 19 (for example, the head office server 10, the cloud server 20) (it may communicate directly or communicate via the store controller 30). For example, the transaction status management device 40 may refer to transaction information (cart information) stored in the cloud server 20.

[0017] The mobile terminal 60 is a terminal used when registering a product in Service A. That is, a customer uses the mobile terminal 60 when registering a product in Service A.

[0018] The mobile terminal 60 may be owned by a customer (member) who uses Service A or may be lent by the store side. In this embodiment, the mobile terminal 60 will be described as being owned by a customer who uses Service A. Also, in this embodiment, the mobile terminal 60 executes a predetermined application program (hereinafter, may also be referred to as a specific app) and registers a product in Service A. That is, a customer who intends to use Service A installs the specific app in their own mobile terminal 60 in advance and activates the specific app before using Service A. Note that the mobile terminal 60 may access a predetermined server (for example, the cloud server 20 or a dedicated server (not shown), etc.) and download and install the specific app from the server.

[0019] Also, in this embodiment, the mobile terminal 60 will be described as being used while attached to a shopping cart (not shown). For example, near the entrance of the store (if the entrance and exit are separate, the entrance), prepare a shopping cart equipped with a mobile terminal installation unit (holder) for setting the mobile terminal 60 in addition to the shopping cart installation unit for installing the shopping basket. A customer who uses Service A, when coming to the store, sets the shopping basket in the shopping cart installation unit of the shopping cart, sets the mobile terminal 60 in the mobile terminal installation unit, and enters the store.

[0020] The settlement device 50 is a device used for settlement in Service A. That is, when a customer settles the products registered using the mobile terminal 60, the settlement device 50 is used.

[0021] The registration settlement device 51 is mainly used by customers. The registration settlement device 51 includes a scanner unit and a settlement unit, and is used for product registration and settlement.

[0022] Figure 2 is a configuration example of the cloud server 20. The cloud server 20 includes a CPU 201, a ROM 202, a RAM 203, and a hard disk 204. These can communicate with each other via a bus.

[0023] The CPU 201 is a central processing unit, and controls the operation of the cloud server 20 by reading and executing the programs stored in the ROM 202. The ROM 202 is a read-only memory, and stores various types of information used by the CPU 201, including programs. The RAM 203 is a read-write memory, and stores various types of information as the main memory device. For example, the RAM 203 stores information read from the ROM 202 or the hard disk 204, information acquired from the outside, information generated during processing, and the like. The hard disk 204 stores various information (see, for example, FIG. 3) as an auxiliary storage device. The hard disk 204 may store, for example, programs executed by the CPU 201 instead of the ROM 202. Further, the hard disk 204 may store information read from the ROM 202, information acquired from the outside, information generated in the process, etc. instead of the RAM 203. The communication unit 215 transmits and receives information to and from other devices (for example, the mobile terminal 60, the head office server 10, etc.).

[0024] FIG. 3 is an example of information stored in the cloud server 20. FIG. 3(A) is an example of transaction information (cart information) stored in the cloud server 20. The cloud server 20 generates transaction information at the start of a transaction. Further, the cloud server 20 updates the transaction information as the transaction progresses. The transaction information shown in FIG. 3(A) includes transaction identification information (cart identification information), transaction start date and time, transaction end date and time, member identification information, and registered product information.

[0025] The transaction identification information is identification information that uniquely identifies the transaction information. For example, the transaction identification information may be composed of store identification information, a date, and a serial number (for example, a serial number for each store and date). The transaction start date and time is the start date and time of the transaction (for example, the generation date and time of the cart information, or the registration date and time of one item of product (the date and time when the registration information (product 1) in FIG. 3(A) was stored)). The transaction end date and time is the end date and time of the transaction (for example, the completion date and time of settlement).

[0026] The member identification information is information that uniquely identifies a customer (member). The member identification information may be determined when a specific application is downloaded. As an example, the member identification information may be generated (numbered) by a predetermined server (cloud server 20, dedicated server). For example, when the predetermined server receives a request to download a specific application from the mobile terminal 60, the predetermined server may generate the member identification information. When the dedicated server generates the member identification information, the dedicated server may notify the cloud server 20 of the member identification information. As another example, the member identification information may be determined by the customer. For example, the mobile terminal 60 may be the one input by the customer when sending a request to download a specific application to the predetermined server (after sending, it is confirmed by the predetermined server that it does not duplicate other member identification information). When the dedicated server obtains the member identification information, the dedicated server may notify the cloud server 20 of the member identification information.

[0027] Note that the mobile terminal 60 may store the member identification information. For example, when the member identification information is generated by a predetermined server, the mobile terminal 60 may receive and store the member identification information from the predetermined server. Also, for example, when the member identification information is input by the member, the mobile terminal 60 may store the member identification information input by the member.

[0028] The registration information (total) is information that is updated each time a product is registered. The registration information (total) includes the quantity (number of products), subtotal amount, etc. The registration information (product N; N is an integer) is the registration information of the Nth item of product. The registration information (product N) includes the product code, product name, quantity, price, etc.

[0029] FIG. 3(B) is an example of member performance information stored in cloud server 20. Cloud server 20 generates member performance information, for example, after determining member identification information. Also, cloud server 20 updates member performance information, for example, each time a transaction using Service A is conducted. The member performance information shown in FIG. 3(B) includes transaction identification information, the number of app launches, the date and time of the first app launch, and the date and time of the previous app launch.

[0030] The member identification information is information that uniquely identifies a customer (member) as described above. The number of app launches is the number of launches of a specific app. The initial value of the number of launches of the specific app is "0 (times)". The first app launch date is the date and time of the first launch of the specific app (the date and time when the specific app was launched for the first time). The previous app launch date is the date and time of the previous launch of the specific app (the date and time when the specific app was last launched (the most recent launch date and time)).

[0031] Note that the member performance information may include information other than the above information. For example, the member performance information may include the number of points, the member rank, the previous (most recent) purchase date (which may be the previous purchase date using Service A), the frequency of store visits within a predetermined period (which may be the frequency of store visits and use of Service A), and the total purchase amount within a predetermined period (which may be the total purchase amount using Service A).

[0032] Note that the information stored in the cloud server 20 is not limited to the product master (not shown), transaction information (Fig. 3(A)), and member performance information (Fig. 3(B)). For example, the cloud server 20 may store (generate, update) the member master. For example, in a request for downloading a specific application, the cloud server 20 may acquire information for identifying the mobile terminal 60 (e.g., MAC address, phone number, etc.) and information input by the customer (e.g., name, date of birth, address, gender, etc.), and store (generate) the member master based on the acquired information. When the dedicated server acquires the above information, the dedicated server supplies the acquired information to the cloud server 20, and the cloud server 20 may store (generate) the member master based on the supplied information. Note that instead of or in addition to the cloud server 20, the head office server 10 may store the member master.

[0033] Fig. 4 is a configuration example of the mobile terminal 60. The mobile terminal 60 includes a CPU 301, a ROM 302, a RAM 303, a storage 304, a display unit 305, an audio output unit (speaker, speaker terminal) 314, a communication unit 315, an imaging unit (camera) 316, and an audio input unit (microphone, microphone terminal) 318. These can communicate with each other via a bus.

[0034] The CPU 301 is a central processing unit, and controls the operation of the mobile terminal 60 by reading and executing programs stored in the ROM 302 and programs stored in the storage 304 (e.g., a downloaded specific application). For example, when the imaging unit 316 is imaging the barcode attached to the product, the CPU 301 extracts feature points in the captured image (an image acquired as a through image (live view)) captured by the imaging unit 316 and recognizes the barcode as an object. The ROM 302 is a read-only memory and stores various kinds of information used by the CPU 301 including programs. The RAM 303 is a read / write memory and stores various information as the main memory device. For example, the RAM 303 stores information read from the ROM 302 or the storage 304, information acquired from the outside, information generated in the process, and the like. The storage 304 stores various information (e.g., specific applications) as an auxiliary storage device. Instead of the RAM 303, the storage 304 may store information read from the ROM 302, information acquired from the outside, information generated in the process, and the like.

[0035] The display unit 305 is a touch display, which displays various information and accepts various inputs. The voice output unit 314 outputs voice. For example, the voice output unit 314 outputs confirmation sounds, warning sounds, voice guidance, etc. Also, the voice output unit 314 may be related to a call and output a calling sound and the voice of the other party. Note that the voice output unit 314 may be linked to the display (display timing) of each screen related to guidance (guidance information) (tutorial screen, menu screen, initial registration screen, 2D code display screen for settlement, 2D code reading completion screen for settlement, transaction completion screen, status confirmation screen, etc.) and output the character string (text) of the guidance as voice (voice guidance). When the screen is maintained for a certain period of time, the voice guidance may be repeated at regular intervals (the number of repetitions may be limited to a predetermined number (e.g., 1 - 2 times)). When the guidance is in a foreign language notation, the voice guidance may be given in that foreign language.

[0036] The communication unit 315 transmits and receives information to and from other devices (e.g., the cloud server 20). Also, the communication unit 315 may be related to a call and transmit and receive voice information to and from other mobile terminals 60, etc. Note that the communication by the communication unit 315 may be wireless communication by a method according to the regulations defined by the International Telecommunication Union (ITU) (4G, 5G, etc.), or may be wireless communication by a method according to the regulations defined by a wireless LAN organization (Wi-Fi (registered trademark), etc.). The imaging unit 316 captures images. For example, the imaging unit 316 captures various codes (e.g., barcodes, 2D codes). The voice input unit 318 inputs voice. For example, the voice input unit 318 inputs voice in an operation by voice recognition. Also, the voice input unit 318 inputs voice related to a call and to be transmitted to the other party.

[0037] Note that the mobile terminal 60 may further include a position measurement unit (GPS function), a motion determination unit (e.g., an acceleration sensor, an angular velocity sensor, etc.), a short-range wireless communication unit (Bluetooth (registered trademark), an infrared sensor), and the like.

[0038] FIG. 5 is a configuration example of the settlement device 50. The settlement device 50 includes a CPU 101, a ROM 102, a RAM 103, a hard disk 104, a display unit 105, a scanner unit 106, a card payment unit (non-cash payment unit) 108, a change machine (cash payment unit) 109, a printing unit 113, a voice output unit 114, a communication unit 115, an imaging unit 116, and a signature pole 117. These can communicate with each other via a bus.

[0039] The CPU 101 is a central processing unit, and controls the operation of the settlement device 50 by reading and executing the programs stored in the ROM 102. The ROM 102 is a read-only memory, and stores various kinds of information used by the CPU 101 including programs. The RAM 103 is a read / write memory, and stores various kinds of information as a main memory device. For example, the RAM 103 stores information read from the ROM 102 or the hard disk 104, information acquired from the outside, information generated in the process, and the like. The hard disk 104 stores various kinds of information as an auxiliary storage device. The hard disk 104 may store, for example, programs executed by the CPU 101 instead of the ROM 102. Also, instead of the RAM 103, it may store information read from the ROM 102, information acquired from the outside, information generated in the process, and the like. Note that a storage device such as an SSD (Solid State Drive) may be provided instead of the hard disk 104. The display unit 105 is a touch display that displays various information and accepts various inputs.

[0040] The scanner unit 106 optically reads various information. Specifically, the scanner unit 106 scans the code (the two-dimensional code GA631 for settlement, to be described later) that the mobile terminal 60 displays on the display unit, and reads the information necessary for the settlement process. Also, the scanner unit 106 may scan the codes attached to vouchers (gift vouchers, coupon vouchers, discount vouchers), various cards (for example, membership cards, point cards, etc.), and read their respective information. Further, the scanner unit 106 may scan the code attached to the name tag of the store clerk or the like and read the store clerk code. Additionally, the scanner unit 106 may scan the code attached to the merchandise and read the merchandise code (JAN code, etc.).

[0041] The card payment unit 108 is a settlement mechanism using various cards (credit cards, prepaid cards such as transportation cards, cash cards at the time of debit payment, point cards at the time of point payment, etc.). The card payment unit 108 includes a card recognition unit (reading unit), a display unit, and an operation unit, but it suffices as long as it includes at least a card recognition unit. Note that the card recognition unit may recognize various cards (for example, point cards, membership cards, shareholder cards, etc.) for privilege granting, discount, etc. The change dispenser 109 is a settlement mechanism using cash. It has an inlet for banknotes and coins and an outlet for banknotes and coins, calculates the amount of money inserted into the inlet, calculates the change amount which is the difference between the inserted amount and the purchase amount, and discharges the change from the outlet. When banknotes or coins are inserted into the inlet, they are detected by sensors (detection of insertion, detection of the number of each denomination, etc.).

[0042] The printing unit 113 prints and issues various media (receipts, etc.). The voice output unit 114 outputs voice. For example, the voice output unit 114 outputs confirmation sounds, warning sounds, voice guidance, etc. The communication unit 115 transmits and receives information to and from other devices (e.g., the store controller 30, the transaction status management device 40, etc.). The imaging unit 116 images, for example, a customer. Note that the settlement device 50 may include two or more imaging units 116 and may simultaneously image the face and the hands (near the insertion slot or the discharge port of the coin changer 109). The sign pole 117 has a light-emitting part at its tip and notifies various information (such as a clerk call, an operation status, etc.) according to the light-emitting mode of the light-emitting part.

[0043] Note that the settlement device 50 may further include a key operation unit composed of various keys (buttons). Further, the settlement device 50 may further include a sensor (such as a human presence sensor) for detecting the presence of a person. Further, the settlement device 50 may further include a sensor for detecting that various media printed and issued by the printing unit 113 have been removed (extracted).

[0044] (Display of the mobile terminal 60) Hereinafter, the display on the mobile terminal 60 will be described. FIGS. 6 to 9 are display examples of the mobile terminal 60. FIG. 10 is a display of the mobile terminal 60 or the like. FIGS. 6 to 10 (excluding FIG. 10(D)) sequentially show screens related to service A after the start of a specific application. Specifically, when the start of the current specific application is the first (the first time) start, the mobile terminal 60 displays as follows after the start of the specific application: FIG. 6(A) → FIG. 6(B) → FIG. 6(C) → FIG. 6(D) → FIG. 7(A) → FIG. 7(B) → FIG. 7(C) → FIG. 7(D) → FIG. 8(A) → FIG. 8(B) → FIG. 8(C) → FIG. 8(D) → FIG. 9(A) → FIG. 9(B) → FIG. 9(C) → FIG. 9(D) → FIG. 10(A) → FIG. 10(B) → FIG. 10(C). When the start of the current specific application is the second or subsequent start, the mobile terminal 60 displays as follows after the start of the specific application: FIG. 6(D) → FIG. 7(A) → FIG. 7(B) → FIG. 7(C) → FIG. 7(D) → FIG. 8(A) → FIG. 8(B) → FIG. 8(C) → FIG. 8(D) → FIG. 9(A) → FIG. 9(B) → FIG. 9(C) → FIG. 9(D) → FIG. 10(A) → FIG. 10(B) → FIG. 10(C).

[0045] Figures 6(A) to 6(C) are the tutorial screens of Service A. Figure 6(D) is the menu screen (start screen) of Service A. The tutorial screen is displayed when the startup of the specific app this time is the first startup, but is not displayed when the startup of the specific app this time is not the first startup (the startup is the second or later startup).

[0046] (When the startup of the specific app this time is the first startup) When the startup of the specific app this time is the first startup, the mobile terminal 60 displays the menu screen as shown in Figure 6(D) after sequentially displaying the tutorial screens as shown in Figures 6(A) to 6(C).

[0047] The tutorial screen shown in Figure 6(A) is the first tutorial screen to be displayed when the startup of the specific app this time is the first startup. That is, when the member starts the specific app and the startup is the first startup, the mobile terminal 60 displays the tutorial screen as shown in Figure 6(A). On the tutorial screen shown in Figure 6(A), an image GA601a introducing shopping (concept) by Service A and a message MS602a are displayed. Also, on the tutorial screen shown in Figure 6(A) (similarly for the tutorial screen shown in Figure 6(B)), a Next button BT603 is arranged.

[0048] The tutorial screen shown in Figure 6(B) is displayed following the tutorial screen shown in Figure 6(A). When the member operates the Next button BT603 on the tutorial screen shown in Figure 6(A), the mobile terminal 60 displays the tutorial screen as shown in Figure 6(B). On the tutorial screen shown in Figure 6(B), an image GA601b introducing shopping (product registration part) by Service A and a message MS602b are displayed.

[0049] The tutorial screen shown in FIG. 6(C) is displayed following the tutorial screen shown in FIG. 6(B). When the member operates the Next button BT603 on the tutorial screen shown in FIG. 6(B), the mobile terminal 60 displays a tutorial screen as shown in FIG. 6(C). On the tutorial screen shown in FIG. 6(C), an image GA601c introducing shopping (the accounting part) by Service A and a message MS602c are displayed. Also, on the tutorial screen shown in FIG. 6(C), a service start button BT604 declaring the start of the service is arranged.

[0050] Note that the images GA601a to GA601c may be collectively referred to as the tutorial image GA601. Also, the messages MS602a to MS602c may be collectively referred to as the message MS602.

[0051] The menu screen shown in FIG. 6(D) is displayed following the tutorial screen. When the member operates the service start button BT604 on the tutorial screen shown in FIG. 6(C), the mobile terminal 60 displays a menu screen as shown in FIG. 6(D). On the menu screen shown in FIG. 6(D), various buttons related to Service A are arranged. For example, on the menu screen shown in FIG. 6(D), a shopping start button BT610 declaring the start of shopping is arranged. Note that the "member number" on the menu screen shown in FIG. 6(D) is member identification information.

[0052] (If the activation of the specific application this time is the second or subsequent activation) If the activation of the specific application this time is the second or subsequent activation, the mobile terminal 60 displays the menu screen as shown in FIG. 6(D) without displaying the tutorial screens as shown in FIGS. 6(A) to 6(C). That is, when the member activates the specific application and the activation is the second or subsequent activation, the mobile terminal 60 first displays the menu screen as shown in FIG. 6(D).

[0053] Figs. 7(A) to 9(C) are registration screens. The registration screen shown in Fig. 7(A) is displayed following the menu screen shown in Fig. 6(D). When a member operates the shopping start button BT610 on the menu screen shown in Fig. 6(D), the mobile terminal 60 displays a registration screen as shown in Fig. 7(A). The registration screen shown in Fig. 7(B) is displayed following the registration screen shown in Fig. 7(A). When a predetermined time (for example, 0.5 seconds) elapses without a product being registered (without the barcode attached to the product being read) on the registration screen shown in Fig. 7(A), the mobile terminal 60 displays a registration screen as shown in Fig. 7(B). The registration screen shown in Fig. 7(C) is displayed following the registration screen shown in Fig. 7(B). When a predetermined time (for example, 0.5 seconds) elapses without a product being registered on the registration screen shown in Fig. 7(B), the mobile terminal 60 displays a registration screen as shown in Fig. 7(C).

[0054] Also, when a predetermined time (for example, 0.5 seconds) elapses without a product being registered on the registration screen shown in Fig. 7(C), the mobile terminal 60 displays the initial registration screen shown in Fig. 7(A). Similarly, when a further predetermined time elapses, the mobile terminal 60 displays the initial registration screen shown in Fig. 7(B). Similarly, when a further predetermined time elapses, the mobile terminal 60 displays the initial registration screen shown in Fig. 7(C). Similarly, when a further predetermined time elapses, the mobile terminal 60 displays the initial registration screen shown in Fig. 7(A) (hereinafter the same). That is, the mobile terminal 60 repeatedly displays the product scan guide image GA624 (described later) on the initial registration screen (described later).

[0055] The registration screens shown in Figs. 7(A) to 7(C) (the same applies to the registration screen shown in Fig. 7(D)) are registration screens in a state where no products have been registered yet (before registering the first product). In the following description, the registration screen in a state where no products have been registered yet may be referred to as the initial registration screen to distinguish it from the registration screen in a state where one or more products have already been registered.

[0056] The upper part of the registration screen is mainly an imaging image display area HR621 for displaying the captured image. The central part of the imaging image display area HR621 is a barcode reading area suitable for barcode reading (a rectangular area with a message "Please hold the barcode in front of the device" displayed in the center). The lower part of the registration screen is mainly a registration information display area HR622 for displaying the registration information of the product. The lowermost part of the registration screen is a related information display area HR623 for displaying other related information.

[0057] On the initial registration screen, the method of registering a product is explained. For example, on the initial registration screen shown in FIGS. 7(A) to 7(C), images (image GA624a, image GA624b, image GA624c) explaining the method of registering a product are displayed. The image GA624a on the initial registration screen shown in FIG. 7(A) shows a state in which the barcode attached to the product is brought close to the mobile terminal 60 so that the barcode attached to the product is imaged by the mobile terminal 60 (the mobile terminal 60 set in the mobile terminal installation part (holder)). The image GA624b on the initial registration screen shown in FIG. 7(B) shows a state of imaging the barcode. The image GA624c on the initial registration screen shown in FIG. 7(C) shows a state in which the barcode has been read. Note that the images GA624a to GA624c may be collectively referred to as the product scan guide image GA624.

[0058] As shown in FIGS. 7(A) to 7(C), the mobile terminal 60 displays a product scan guide image GA624 at a position straddling the captured image display area HR621 and the registration information display area HR622 (the front surface of the captured image display area HR621 and the registration information display area HR622). More specifically, the mobile terminal 60 has the upper part of the product scan guide image GA624 located on the front surface of the area below the barcode reading area of the captured image display area HR621, and the remaining part of the product scan guide image GA624 located on the front surface of the area excluding the lower area of the registration information display area HR622, thereby displaying the product scan guide image GA624. Note that the upper part of the product scan guide image GA624 has a shape like a speech bubble. The product scan guide image GA624 indicates the barcode reading area of the captured image display area HR621 by means of the speech bubble (reference symbol f in FIG. 7(A)).

[0059] The member can cause the barcode attached to the product to be read regardless of which initial registration screen shown in FIGS. 7(A) to 7(C) is being displayed (that is, regardless of which of the images GA624a to GA624c is being displayed).

[0060] FIG. 7(D) is an initial registration screen when a certain brand of bread is captured as one item of product. In the captured image display area HR621 (barcode reading area) of the initial registration screen shown in FIG. 7(D), the barcode attached to the certain brand of bread is displayed as a through image. Note that FIG. 7(D) shows an example where the member is causing the barcode to be read in the initial registration screen shown in FIG. 7(C) (while the image GA624c is being displayed). However, as described above, the member can also cause the barcode to be read in the initial registration screen shown in FIG. 7(A) (while the image GA624a is being displayed) or in the initial registration screen shown in FIG. 7(B) (while the image GA624b is being displayed).

[0061] The registration screen shown in Fig. 8(A) is displayed following the initial registration screen shown in Fig. 7(D). Specifically, the registration screen shown in Fig. 8(A) is the registration screen after the registration of one item of product (〇〇 Food Bread) is completed. In the registration information display area HR622 of the registration screen shown in Fig. 8(A), the product name "〇〇 Food Bread", quantity "1", and price "￥220" are displayed (reference sign a). Also, in the registration information display area HR622, the estimated total "1 item ￥220" is displayed (reference sign b). Further, in front of the imaging image display area HR621 of the registration screen shown in Fig. 8(A), a small screen SG625 showing the product name "〇〇 Food Bread" and price "￥220" is displayed.

[0062] The process from the initial registration screen shown in Fig. 7(D) to the display of the registration screen shown in Fig. 8(A) will be described. The mobile terminal 60 transmits the product code obtained from the barcode to the cloud server 20. The cloud server 20 refers to the product master and obtains the product name "〇〇 Food Bread" and price "￥220" based on the product code. The cloud server 20 stores, as registration information in the transaction information of the said transaction, the product code, product name "〇〇 Food Bread", quantity "1", price "￥220", etc. Also, the cloud server 20 transmits the registration information (product name "〇〇 Food Bread", price "￥220", etc.) to the mobile terminal 60. The mobile terminal 60 displays the registration information received from the cloud server 20 in the registration information display area HR622 and the small screen SG625.

[0063] Note that the mobile terminal 60 displays a part of the registration information (quantity) as a quantity button. The quantity button is a button for changing the quantity. Also, after the registration of the product (one item of product), the mobile terminal 60 operably displays a "Proceed to Accounting" button BT626 declaring that the registration of the product is to be completed and proceed to accounting (settlement).

[0064] The registration screen shown in FIG. 8(B) is displayed following the registration screen shown in FIG. 8(A). When a predetermined time (for example, 2 seconds) has elapsed on the registration screen shown in FIG. 8(A), the mobile terminal 60 displays a registration screen as shown in FIG. 8(B). On the registration screen shown in FIG. 8(B), the small screen SG625 displayed on the registration screen shown in FIG. 8(A) has been erased. Also, on the registration screen shown in FIG. 8(B), an image GA627 (message "Touch here when proceeding to payment") explaining the button BT626 to proceed to the payment is displayed.

[0065] The registration screen shown in FIG. 8(C) is the registration screen after more time has elapsed from the registration screen shown in FIG. 8(B). In the imaging image display area HR621 of the registration screens shown in FIGS. 7(D) to 8(B), the ○○ Food Bread was displayed as a skipped image, but it is not displayed in the imaging image display area HR621 of the registration screen shown in FIG. 8(C). That is, since the registration of the ○○ Food Bread is completed, when the member puts the ○○ Food Bread into the cart (shopping basket), etc., the ○○ Food Bread moves outside the imaging range of the imaging unit 316, so the mobile terminal 60 displays a registration screen as shown in FIG. 8(C). Before the small screen SG625 is erased (while being displayed), if the member puts the ○○ Food Bread into the cart (shopping basket), etc., the state of the registration screen shown in FIG. 8(B) does not occur, so it transitions from FIG. 8(A) → FIG. 8(C).

[0066] The registration screen shown in FIG. 8(C) is the same as the initial registration screens shown in FIGS. 7(A) to 7(C) in that no product is imaged, but the registration screen shown in FIG. 8(C) is different from the initial registration screens shown in FIGS. 7(A) to 7(C) in that the product scan guide image GA624 explaining the product registration method is not displayed. That is, the mobile terminal 60 displays an image (product scan guide image GA624) explaining the product registration method on the registration screen (initial registration screen) when no product has been registered yet, but does not display an image explaining the product registration method on the registration screen when one or more products have already been registered.

[0067] FIG. 8(D) is a registration screen when the XX oolong tea is imaged as a two-item product. In the imaging image display area HR621 (barcode reading area) of the registration screen shown in FIG. 8(D), the barcode attached to the XX oolong tea is displayed as a through image.

[0068] The registration screen shown in FIG. 9(A) is displayed following the registration screen shown in FIG. 8(D). Specifically, the registration screen shown in FIG. 9(A) is the registration screen after the registration of the two-item product (XX oolong tea) is completed. In the registration information display area HR622 of the registration screen shown in FIG. 9(A), the product name "XX oolong tea", the quantity "1", and the price "￥150" are additionally displayed. Also, in the registration information display area HR622, the updated estimated total "2 items ￥370" is displayed. Further, in front of the imaging image display area HR621 of the registration screen shown in FIG. 9(A), a small screen SG625 showing the product name "XX oolong tea" and the price "￥150" is displayed.

[0069] The registration screen shown in FIG. 9(B) is displayed following the registration screen shown in FIG. 9(A). When a predetermined time (for example, 2 seconds) has elapsed in the registration screen shown in FIG. 9(A), the mobile terminal 60 displays a registration screen as shown in FIG. 9(B).

[0070] The registration screen shown in FIG. 9(C) is the registration screen after further time has elapsed from the registration screen shown in FIG. 9(B). In the imaging image display area HR621 of the registration screens shown in FIGS. 8(D) to 9(B), the XX oolong tea was displayed as a through image, but it is not displayed in the imaging image display area HR621 of the registration screen shown in FIG. 9(C). Note that if the member puts the XX oolong tea into the cart (shopping basket) before the small screen SG625 is erased (while it is being displayed), the state of the registration screen shown in FIG. 9(B) does not occur, so the transition is from FIG. 9(A) → FIG. 9(C).

[0071] FIG. 9(D), FIG. 10(A) and FIG. 10(B) are the payment two-dimensional code display screens. The payment two-dimensional code display screen shown in FIG. 9(D) is displayed, for example, following the registration screen shown in FIG. 9(C). When the member operates the button BT626 to proceed to the payment on the registration screen shown in FIG. 9(C), the mobile terminal 60 displays a payment two-dimensional code display screen as shown in FIG. 9(D). The payment two-dimensional code display screen shown in FIG. 10(A) is displayed following the payment two-dimensional code display screen shown in FIG. 9(D). When a predetermined time (for example, 0.5 seconds) has elapsed without allowing the payment two-dimensional code GA631 (described later) to be read by the payment device 50 on the payment two-dimensional code display screen shown in FIG. 9(D), the mobile terminal 60 displays a payment two-dimensional code display screen as shown in FIG. 10(A). The payment two-dimensional code display screen shown in FIG. 10(B) is displayed following the payment two-dimensional code display screen shown in FIG. 10(A). When a predetermined time (for example, 0.5 seconds) has elapsed without allowing the payment two-dimensional code GA631 (described later) to be read by the payment device 50 on the payment two-dimensional code display screen shown in FIG. 10(A), the mobile terminal 60 displays a payment two-dimensional code display screen as shown in FIG. 10(B).

[0072] Also, when a predetermined time has elapsed without allowing the payment two-dimensional code GA631 (described later) to be read by the payment device 50 on the payment two-dimensional code display screen shown in FIG. 10(B), the mobile terminal 60 displays the payment two-dimensional code display screen shown in FIG. 9(D). Similarly, when a further predetermined time has elapsed, the mobile terminal 60 displays the payment two-dimensional code display screen shown in FIG. 10(A). Similarly, when a further predetermined time has elapsed, the mobile terminal 60 displays the initial registration screen shown in FIG. 10(B). Similarly, when a further predetermined time has elapsed, the mobile terminal 60 displays the initial registration screen shown in FIG. 9(D) (hereinafter the same). That is, the mobile terminal 60 repeatedly displays the payment two-dimensional code scan guide image GA633 (described later) on the payment two-dimensional code display screen and on the initial registration screen (described later).

[0073] On the payment two-dimensional code display screen, a payment two-dimensional code GA631 and a message MS632 are displayed. Also, on the payment two-dimensional code display screen, a button BT639 for returning to shopping is arranged. When the button BT639 for returning to shopping is operated on the mobile terminal 60, the registration screen (the registration screen immediately before operating the button BT639 for returning to shopping) is displayed.

[0074] The payment two-dimensional code GA631 is obtained by encoding into a two-dimensional code the information necessary for executing the payment process. For example, the payment two-dimensional code GA631 is obtained by encoding into a two-dimensional code the transaction identification information for identifying the transaction information of the transaction from among a plurality of transaction information stored in the cloud server 20. Note that the information to be encoded into a two-dimensional code does not have to be the transaction identification information as long as the transaction information of the transaction can be acquired after reading. For example, the payment two-dimensional code GA631 may be obtained by encoding into a two-dimensional code the location information (storage location in the sales system 1, such as a URI (Uniform Resource Identifier)) of the transaction information of the transaction.

[0075] Also, on the payment two-dimensional code display screen, images (images GA633a, GA633b, GA633c) for explaining how to have the payment two-dimensional code GA631 read by the payment device 50 are displayed. The image GA633a shown in FIG. 9(D) shows a state where the payment two-dimensional code GA631 is displayed on the display unit 305. The image GA633b shown in FIG. 10(A) shows a state where the payment two-dimensional code GA631 is brought close to the payment device 50 so as to be read by the payment device 50 (scanner unit 106). The image GA633c shown in FIG. 10(B) shows a state where the angle of the payment two-dimensional code GA631 (mobile terminal 60) is changed so as to be read by the payment device 50 (scanner unit 106). Note that the images GA633a to GA633c may be collectively referred to as the payment two-dimensional code scan guide image GA633.

[0076] As shown in FIGS. 9(D) to 10(B), on the payment two-dimensional code display screen, the payment two-dimensional code scan guide image GA633 is displayed below the payment two-dimensional code GA631. Since the payment two-dimensional code scan guide image GA633, which occupies a relatively large area, is displayed below (the wrist side, the hand side) the payment two-dimensional code GA631, the member can have the payment two-dimensional code GA631 read by the payment device 50 without difficulty (ergonomically, for example, with natural movements without twisting the wrist too much).

[0077] The member can have the payment two-dimensional code GA631 read by the payment device 50 regardless of which payment two-dimensional code display screen shown in FIGS. 9(D) to 10(B) is being displayed (that is, regardless of which of the images GA633a to GA633c is being displayed).

[0078] FIG. 10(C) is a payment two-dimensional code reading completion screen. The payment two-dimensional code reading completion screen shown in FIG. 10(C) is displayed following the payment two-dimensional code display screen. When the member has the payment two-dimensional code GA631 displayed on the payment two-dimensional code display screen read by the payment device 50, the mobile terminal 60 displays a payment two-dimensional code reading completion screen as shown in FIG. 10(C). On the payment two-dimensional code reading completion screen shown in FIG. 10(C), there are displayed messages indicating that the payment machine (payment device 50) has read the accounting code (payment two-dimensional code GA631) and messages indicating that payment should be made by the payment machine.

[0079] (Display of the payment device 50) During standby, the settlement device 50 displays an initial screen (not shown). On the initial screen, there is a message instructing the mobile terminal 60 to read the 2D code GA631 for settlement and an image (e.g., an image similar to the 2D code scan guide image GA633 for settlement) explaining how to read the 2D code GA631 displayed on the mobile terminal 60. Additionally, on the initial screen, buttons such as a staff call button, a balance inquiry button, and a language switch button may be arranged. The staff call button is for calling a staff member. The balance inquiry button is for inquiring about the balances of various cards. The language switch button is for switching the display (text) on the settlement device 50 from Japanese to another language (such as English).

[0080] When the settlement device 50 reads the 2D code GA631 for settlement, it acquires transaction information from the cloud server 20 and displays a product list screen as shown in Fig. 10(D). The product list screen is provided with a product list display area, a product quantity display area by price range, and a total display area. The product list display area is for listing products to be settled, etc. In the example shown in Fig. 10(D), XX food bread and XX oolong tea are displayed. The product quantity display area by price range is for displaying the quantity of products by price range (1000 yen or more, 500 yen or more and less than 1000 yen, 200 yen or more and less than 500 yen, less than 200 yen) of the products to be settled. In the example shown in Fig. 10(D), 1 is displayed as the quantity of products in the range of 200 yen or more and less than 500 yen, and 1 is displayed as the quantity of products less than 200 yen. The total display area is for displaying the total of the transaction. In the example of Fig. 10(D), 2 is displayed as the total points and 370 yen is displayed as the approximate total amount.

[0081] Also, on the product list screen, a staff call button and a checkout button are arranged. The checkout button is for confirming that there are no problems with the content displayed on the product list screen and proceeding with the process. When the checkout button is operated, the settlement device 50 displays, for example, a payment type selection screen (not shown).

[0082] (Operations of Mobile Terminal 60, etc.) FIG. 11 is a sequence diagram showing an example of the processing of the mobile terminal 60 and the cloud server 20. Specifically, FIG. 11 shows an example of the processing of the mobile terminal 60 and the cloud server 20 from when the mobile terminal 60 starts a specific application until a menu screen is displayed. The left side of FIG. 11 (and FIGS. 12, 13, 14, and 15 as well) shows the processing of the mobile terminal 60, and the right side shows the processing of the cloud server 20. It is assumed that the start of the specific application on the mobile terminal 60 is the first time (the first start). That is, at the start of the flowchart in FIG. 11, in the member performance information (FIG. 3(B)) stored in the cloud server 20, "0 (times)" is stored as the application start count corresponding to the member identification information of the member using the mobile terminal 60.

[0083] Step S1: The mobile terminal 60 starts a specific application based on a member's operation. For example, when the mobile terminal 60 downloads a specific application, it displays a startup icon on the screen, and starts the specific application based on the member's operation of the startup icon. Step S2: The mobile terminal 60 transmits application startup information for notifying (informing) that the specific application has started. The application startup information includes member identification information.

[0084] Step S3: The cloud server 20 receives the application startup information. Step S4: The cloud server 20 determines that the startup of the specific application is the first time. Specifically, the cloud server 20 refers to the application startup count corresponding to the member identification information included in the application startup information. Since the application startup count is "0 times", the cloud server 20 determines that the startup of the specific application is the first time.

[0085] Step S5: The cloud server 20 transmits display instruction information for the tutorial screen. That is, when the cloud server 20 determines that the startup of the specific application is the first time (when it determines that it is the first startup), it transmits display instruction information for the tutorial screen. Note that when the cloud server 20 determines that the startup of the specific application is not the first time (when it determines that it is the startup for the second time or later), it transmits display instruction information for the menu screen (step S31 in FIG. 12).

[0086] Step S6: The mobile terminal 60 receives the display instruction information for the tutorial screen. Step S7: The mobile terminal 60 displays the tutorial screen. That is, the mobile terminal 60 displays the tutorial screen based on the instruction from the cloud server 20 (display instruction information for the tutorial screen) (FIGS. 6(A) to 6(C)). Note that the screen information regarding the tutorial screen (the same applies to the screen information regarding other screens displayed by the mobile terminal 60) is stored in the mobile terminal 60 as a part of the specific application or information attached to the specific application. Step S8: The mobile terminal 60 receives an operation instructing the start of the service from the member. For example, the mobile terminal 60 receives an operation of the service start button BT604 on the tutorial screen shown in FIG. 6(C). Step S9: The mobile terminal 60 transmits service start instruction information notifying (informing) that there has been an operation instructing the start of the service. The service start instruction information includes member identification information.

[0087] Step S10: The cloud server 20 receives the service start instruction information. Step S11: The cloud server 20 transmits display instruction information for the menu screen. That is, when the cloud server 20 receives the service start instruction information, it transmits display instruction information for the menu screen. Note that as described above, when the cloud server 20 determines that the startup of the specific application is not the first time (when it determines that it is the startup for the second time or later), it also transmits display instruction information for the menu screen (step S31 in FIG. 12). Step S12: The cloud server 20 updates the number of app launches. Specifically, the cloud server 20 adds 1 to the number of app launches corresponding to the member identification information (updating from "0 (times)" to "1 (time)"). In addition, the cloud server 20 further stores the current date and time in the first app launch date and time and the previous app launch date and time corresponding to the member identification information.

[0088] Step S13: The mobile terminal 60 receives display instruction information for the menu screen. Step S14: The mobile terminal 60 displays the menu screen instead of the tutorial screen (erases the tutorial screen). That is, the mobile terminal 60 displays the menu screen based on the instruction from the cloud server 20 (display instruction information for the menu screen) (Fig. 6(D)). In addition, the mobile terminal 60 may obtain information to be displayed on the menu screen (for example, the point number) from the cloud server 20 and display it on the menu screen.

[0089] Fig. 12 is a sequence diagram showing an example of the processing of the mobile terminal 60 and the cloud server 20. Specifically, Fig. 12 shows an example of the processing of the mobile terminal 60 and the cloud server 20 from when the mobile terminal 60 starts a specific app until the menu screen is displayed. It is assumed that the start of the specific app on the mobile terminal 60 is not the first time this time (it is the second or later start). That is, at the start of the flowchart in Fig. 12, it is assumed that a value other than "0 (times)" is stored in the member performance information (Fig. 3(B)) stored by the cloud server 20 as the number of app launches corresponding to the member identification information of the member using the mobile terminal 60.

[0090] Step S21: The mobile terminal 60 starts a specific app based on the member's operation, similar to step S1 in Fig. 11. Step S22: The mobile terminal 60 transmits app launch information, similar to step S2 in Fig. 11.

[0091] Step S23: The cloud server 20 receives the app launch information, similar to step S3 in Fig. 11. Step S24: The cloud server 20 determines that the startup of the specific application is not the first time. Specifically, the cloud server 20 refers to the number of times the application has been started corresponding to the member identification information included in the application startup information. Since the number of times the application has been started is not "0", the cloud server 20 determines that the startup of the specific application is not the first time.

[0092] Step S31: The cloud server 20 sends display instruction information for the menu screen. That is, when the cloud server 20 determines that the startup of the specific application is not the first time (when it is determined to be the second or subsequent startup), it sends display instruction information for the menu screen. Note that when the cloud server 20 determines that the startup of the specific application is the first time (when it is determined to be the first startup), it sends display instruction information for the tutorial screen (step S5 in FIG. 11). Also, when the cloud server 20 receives service start instruction information, it also sends display instruction information for the menu screen (step S11 in FIG. 11). Step S32: The cloud server 20 updates the number of times the application has been started. Specifically, the cloud server 20 adds 1 to the number of times the application has been started corresponding to the member identification information. In addition, the cloud server 20 further stores the current date and time in the previous application startup date and time corresponding to the member identification information.

[0093] Step S33: The mobile terminal 60 receives display instruction information for the menu screen in the same way as in step S13 of FIG. 11. Step S34: The mobile terminal 60 displays the menu screen in the same way as in step S14 of FIG. 11 (FIG. 6(D)). In this way, when the startup of the specific application is the second or subsequent startup, the mobile terminal 60 displays the menu screen without displaying the tutorial screen.

[0094] FIG. 13 is a sequence diagram showing an example of the processing of the mobile terminal 60 and the cloud server 20. Specifically, FIG. 13 shows an example of the processing following FIG. 11 or FIG. 12, which is the processing from when the mobile terminal 60 receives an operation to start shopping until it displays the initial registration screen. Note that at the start of the flowchart in FIG. 13, it is assumed that the mobile terminal 60 is displaying the menu screen.

[0095] Step S40: The mobile terminal 60 receives an operation to start shopping. For example, the mobile terminal 60 receives an operation of the shopping start button BT610 on the menu screen shown in FIG. 6(D). Step S41: The mobile terminal 60 transmits shopping start instruction information notifying (informing) that there has been an operation to instruct the start of shopping. The shopping start instruction information includes member identification information.

[0096] Step S42: The cloud server 20 receives the shopping start instruction information. Step S43: The cloud server 20 generates (assigns a serial number to) transaction identification information. Also, the cloud server 20 generates transaction information for the transaction (the registration information (such as "Product 1" etc. is empty)).

[0097] Step S44: The cloud server 20 determines that no item of product has been registered yet. For example, since the registration information (Product 1) is not stored in the transaction information of the transaction, the cloud server 20 determines that no item of product has been registered yet. Step S45: The cloud server 20 transmits display instruction information for the initial registration screen and transaction identification information for identifying the transaction. That is, when the cloud server 20 determines that no item of product has been registered yet, it transmits display instruction information for the initial registration screen and transaction identification information for identifying the transaction. Note that when the cloud server 20 determines that an item of product has already been registered, it transmits display instruction information for the registration screen (not the initial registration screen) (Steps S53, S63 in FIG. 14).

[0098] Step S46: The mobile terminal 60 receives the display instruction information and the transaction identification information of the initial registration screen. Step S47: The mobile terminal 60 stores the transaction identification information. When the transaction is completed (when the settlement in the settlement device 50 is completed), the mobile terminal 60 may delete the transaction identification information. Step S48: The mobile terminal 60 displays the initial registration screen instead of the menu screen. Also, the mobile terminal 60 displays the product scan guide image GA624 in front of the initial registration screen. That is, the mobile terminal 60 displays the initial registration screen based on the instruction from the cloud server 20 (display instruction information of the initial registration screen), and displays the product scan guide image GA624 in front of the initial registration screen (Figs. 7(A) to 7(C)). Note that the mobile terminal 60 may store the product scan guide image GA624 as part of a specific application or information attached to the specific application, and display it in front of the initial registration screen. Also, the mobile terminal 60 may acquire the product scan guide image GA624 from the cloud server 20 and display it in front of the initial registration screen.

[0099] FIG. 14 is a sequence diagram showing an example of the processing of the mobile terminal 60 and the cloud server 20. Specifically, FIG. 14 shows the processing following FIG. 13, and shows an example of the processing of the mobile terminal 60 and the cloud server 20 from when the mobile terminal 60 reads the barcode attached to one item of product until the operation to proceed to accounting is performed. At the start of the flowchart of FIG. 14, it is assumed that the mobile terminal 60 is displaying the initial registration screen.

[0100] Step S50: The mobile terminal 60 reads the barcode attached to one item of product. Specifically, as shown in FIG. 7(D), the mobile terminal 60 reads the barcode by imaging the barcode attached to the product. The mobile terminal 60 acquires the product code of the product from the above barcode. Step S51: The mobile terminal 60 transmits the transaction identification information of the transaction and the product code of the product.

[0101] Step S52: The cloud server 20 receives the transaction identification information and the product code. Step S53: The cloud server 20 updates the transaction information of the transaction. Specifically, the cloud server 20 identifies the product based on the received product code, and stores the product information of the product in the "Registration Information (Product 1)". In addition, the cloud server 20 stores the product information (price) of the product in the "Registration Information (Total)". Step S54: The cloud server 20 determines that the product of one item has already been registered. For example, since the "Registration Information (Product 1)" is stored in the transaction information of the transaction, the cloud server 20 determines that the product of one item has already been registered. Step S55: The cloud server 20 sends display instruction information for the registration screen (not the initial registration screen). That is, when the cloud server 20 determines that the product of one item has already been registered, it sends display instruction information for the registration screen (not the initial registration screen).

[0102] Step S56: The mobile terminal 60 receives the display instruction information for the registration screen (not the initial registration screen). Step S57: The mobile terminal 60 displays (updates the display content) the registration screen. That is, the mobile terminal 60 displays the registration screen based on the instruction of the cloud server 20 (display instruction information for the registration screen) (Figs. 8(A) to 8(C)). As shown in Figs. 8(A) to 8(C), the mobile terminal 60 does not display (erases) the product scan guide image GA624 on the registration screen. The mobile terminal 60 obtains the information to be displayed on the registration screen (for example, product name, amount) from the cloud server 20 and displays it on the registration screen.

[0103] Note that after this step S57 (the same applies to step S67 described later), it is also possible to read the barcodes attached to the products of two or more items (products of two items, products of three items, etc.) (step S60), and it is also possible to accept an operation to proceed to accounting (operation of the button BT626 to proceed to accounting) (step S68).

[0104] Step S60: The mobile terminal 60 reads the barcodes attached to the products from the second item onwards. Specifically, as shown in FIG. 8(D), the mobile terminal 60 reads the barcode by imaging the barcode attached to the product. The mobile terminal 60 acquires the product code of the product from the above barcode. Step S61: Similar to step S51, the mobile terminal 60 transmits the transaction identification information of the transaction and the product code of the product.

[0105] Step S62: Similar to step S52, the cloud server 20 receives the transaction identification information and the product code. Step S63: The cloud server 20 updates the transaction information of the transaction. Specifically, the cloud server 20 identifies the product based on the received product code, and stores the product information of the product in the "registration information (product N (N is the Nth item))". Also, the cloud server 20 adds the product information (price) of the product to the "registration information (total)". Step S64: Similar to step S54, the cloud server 20 determines that the product of the first item has already been registered. Step S65: Similar to step S55, the cloud server 20 transmits display instruction information for the registration screen (not the initial registration screen).

[0106] Step S66: Similar to step S56, the mobile terminal 60 receives the display instruction information for the registration screen (not the initial registration screen). Step S67: Similar to step S57, the mobile terminal 60 displays (updates the display content) the registration screen. That is, the product scan guide image GA624 is not displayed (remains non-displayed).

[0107] Step S68: The mobile terminal 60 accepts an operation to proceed to checkout. Specifically, the mobile terminal 60 accepts an operation of the button BT626 to proceed to checkout.

[0108] FIG. 15 is a sequence diagram showing an example of the processing of the mobile terminal 60 and the cloud server 20. Specifically, FIG. 15 shows an example of the processing of the mobile terminal 60 and the cloud server 20 in the processing following FIG. 14, from when the mobile terminal 60 receives an operation to proceed to accounting until the payment two-dimensional code display screen is displayed. Note that at the start of the flowchart of FIG. 15, it is assumed that the mobile terminal 60 has received an operation to proceed to accounting (operation of the button BT626 to proceed to payment).

[0109] Step S69: The mobile terminal 60 transmits accounting instruction information for notifying (informing) that there has been an operation instructing progress to payment. The accounting instruction information includes transaction identification information.

[0110] Step S70: The cloud server 20 receives the accounting instruction information. Step S71: The cloud server 20 generates a payment two-dimensional code GA631. Step S72: The cloud server 20 transmits display instruction information for the payment two-dimensional code display screen.

[0111] Step S73: The mobile terminal 60 receives the display instruction information for the payment two-dimensional code display screen. Step S74: The mobile terminal 60 displays the payment two-dimensional code display screen instead of the registration screen (erases the registration screen). That is, the mobile terminal 60 displays the payment two-dimensional code display screen based on the instruction of the cloud server 20 (display instruction information for the payment two-dimensional code display screen) (FIGS. 9(D) to 10(B)). Note that the mobile terminal 60 acquires the information to be displayed on the payment two-dimensional code display screen (for example, the payment two-dimensional code GA631) from the cloud server 20 and displays it on the payment two-dimensional code display screen.

[0112] FIG. 16 is a sequence diagram showing an example of the processing of the settlement device 50, the cloud server 20, and the mobile terminal 60. Specifically, FIG. 16 shows an example of the processing of the settlement device 50, the cloud server 20, and the mobile terminal 60 from when the settlement device 50 reads the settlement two-dimensional code GA631 until the product list screen is displayed (until the mobile terminal 60 displays the settlement two-dimensional code reading completion screen). The left side of FIG. 16 shows the processing of the settlement device 50, the center shows the processing of the cloud server 20, and the right side shows the processing of the mobile terminal 60.

[0113] Step S80: The settlement device 50 reads the settlement two-dimensional code GA631 displayed on the settlement two-dimensional code display screen by the mobile terminal 60. The settlement device 50 acquires transaction identification information for identifying the transaction information of the transaction from the settlement two-dimensional code GA631. Step S81: The settlement device 50 transmits transaction information request information for requesting the transaction information of the transaction. The transaction information request information includes transaction identification information for identifying the transaction. Step S82: The cloud server 20 receives the transaction information request information.

[0114] Step S83: The cloud server 20 transmits the transaction information of the transaction. Step S84: The settlement device 50 receives and stores the transaction information of the transaction. Step S85: The settlement device 50 displays a product list screen based on the transaction information (FIG. 10(D)).

[0115] Step S86: The cloud server 20 transmits display instruction information for the settlement two-dimensional code reading completion screen.

[0116] Step S87: The mobile terminal 60 receives the display instruction information for the settlement two-dimensional code reading completion screen. Step S88: The mobile terminal 60 displays a payment two-dimensional code reading completion screen instead of the payment two-dimensional code display screen (erases the payment two-dimensional code display screen). That is, the mobile terminal 60 displays the payment two-dimensional code reading completion screen based on the instruction of the cloud server 20 (display instruction information of the payment two-dimensional code reading completion screen) (Fig. 10(C)).

[0117] As described above, although the embodiments have been explained, according to the embodiments, even beginners can easily use them. For example, as guidance (guidance information) for guiding the procedures (operations, actions) of the mobile terminal 60, guidance images (tutorial image GA601, product scan guide image GA624, payment two-dimensional code scan guide image GA633) are displayed, so even beginners can easily operate the mobile terminal 60 and the like. Note that the image GA627 may also be one of the images for guiding the procedure.

[0118] In the above embodiment, guidance regarding the product registration method (product scan guide image GA624) is displayed in the scene where the product is actually registered (Fig. 7). Since the guidance regarding the product registration method is displayed in the scene where the product is actually registered, for example, compared with the case of displaying it in a scene where the product is not actually registered (for example, the tutorial screen shown in Figs. 6(A) to 6(C) or the menu screen shown in Fig. 6(D)), the customer can efficiently learn the product registration method. That is, since the guidance is provided not in advance but in a timely manner, the customer can practice (register the product) while looking at the guidance and efficiently learn the product registration method. In addition, since the necessary information is presented in a timely manner, the stress on the customer is small. In this regard, in the mode of providing guidance in advance, the customer has to remember the content of the guidance provided in advance until the necessary scene occurs, or perform operations such as switching pages when the necessary scene occurs to confirm the content of the guidance provided in advance, so the stress on the customer is large.

[0119] In the above-described embodiment, an area for displaying a captured image (captured image display area HR621) and an area for displaying registration information of a product (registration information display area HR622) are provided on the same screen (Figs. 7 to 9). As a result, a customer can comfortably register a product (realize a comfortable shopping experience for the customer). In this regard, instead of providing the area for displaying the captured image and the area for displaying the registration information of the product on the same screen, if an area for displaying the captured image is provided on one screen and an area for displaying the registration information of the product is provided on another screen, a screen transition for moving back and forth between the two screens will occur automatically every time a product is registered or based on the intention (instruction) of the customer. And whether the screen transition occurs automatically every time a product is registered or the screen transition occurs based on the intention of the customer, visual fatigue is likely to occur in the customer due to the screen transition. Further, when the screen transition occurs based on the intention of the customer, a button operation or the like by the customer himself / herself is also required, which is a burden or at least troublesome. In any case, it will at least hinder a comfortable shopping experience. On the other hand, in the embodiment, since the area for displaying the captured image and the area for displaying the registration information of the product are provided on the same screen, the above-described problems do not occur, and a comfortable shopping experience can be realized.

[0120] From the perspective of realizing a comfortable shopping experience, it is necessary to pay attention to information overload, which may also lead to difficulty in viewing and indigestion. Since providing all the guidance required for each scene in a series of processes together in one scene at the same time will result in information overload, in the above-described embodiment, the guidance required for each scene is provided in each scene. Also, the timing for erasing (or making non-display) the guidance that is no longer necessary is important. In the above-described embodiment, the product scan guide image GA624 is erased immediately after the product is read (Fig. 7(D) → Fig. 8(A)), or the product scan guide image GA624 is made non-display from the second item (Fig. 8(C)).

[0121] (Modification example, etc.) The above describes the embodiments. However, the configuration of the device, the configuration of the data, the processing flow, the display and output modes, etc. can be appropriately changed as shown in, for example, the following (1), (2), …. Also, the following (1), (2), … can be appropriately combined with each other.

[0122] (1) In the above embodiment, an example was described in which the tutorial screen (tutorial image GA601) is advanced based on an operation (operation of the next button BT603). However, the tutorial screen may be advanced based on other conditions. For example, similar to the product scan guide image GA624 and the settlement two-dimensional code scan guide image GA633, the tutorial screen may be advanced based on the passage of time.

[0123] (2) In the above embodiment, an example was described in which the presence or absence (necessity) of the display of the tutorial screen (tutorial image GA601, etc.) is determined based on whether the startup of a specific application is the first time (the first time). However, the number of times of determining the presence or absence of the display of the tutorial screen is not limited to the first time. As an example, the tutorial screen may be displayed until the third startup, and not displayed after the fourth startup.

[0124] (3) In the above embodiment, an example was described in which three types (images GA601a, GA601b, GA601c) of tutorial images GA601 are displayed on the tutorial screen. However, the number of types of the tutorial images GA601 does not have to be three. That is, one type of tutorial image GA601 may always be displayed on the tutorial screen, or two or four or more types of tutorial images GA601 may be displayed in order on the tutorial screen.

[0125] (4) In the above embodiment, when the tutorial screen is displayed, the amount of information provided (guided) is constant, but the amount of information provided by the tutorial screen may be varied. For example, in relation to the above (2) and (3), depending on the conditions (the number of startups, member attributes, purchase history, etc.), when explaining the service at the normal level using a normal number (for example, three types) of tutorial images GA601, when explaining the service at a more detailed level than the normal level using a large number (for example, five types) of tutorial images GA601, and when explaining the service at a more concise level than the normal level using a small number (for example, one type) of tutorial images GA601 may also be possible.

[0126] (5) In the above embodiment, an example was described in which, in relation to the presence or absence of the display of the tutorial screen, it is determined whether the startup of the specific application is the first time based on the time point (starting point) when the specific application was introduced (downloaded, etc.). However, it may be determined whether the startup of the current specific application is the first time based on another time point. For example, instead of or in addition to the time point when the specific application was introduced, when a predetermined period (for example, three months) has elapsed since the startup or non-startup from the previous (previous) startup, it may be determined whether the startup of the current specific application is the first time based on the time point when the predetermined period has elapsed. That is, when the specific application has been started in the past but has not been started for a while (when it is a long-awaited startup), the tutorial screen (tutorial image GA601, etc.) may be displayed. The same applies not only to the first time but also to the case of determining the second time and subsequent times. Also, for example, instead of or in addition to the time point when the specific application was introduced or the time point when the above predetermined period has elapsed, when the version of the specific application is updated (for example, addition of functions, change of UI), it may be determined whether the startup of the current specific application is the first time based on the time point when the version update was performed.

[0127] (6) In the above embodiment, an example of determining whether to display the tutorial screen based on the startup record of a specific application (specifically, the number of past startups) has been described. However, conditions may be set for the startup record of the specific application. For example, conditions regarding the startup time of the specific application may be set. As an example, when the specific application is launched during a predetermined time (for example, the business hours of the store), the launch may be counted as a startup record, and when the specific application is launched at a time different from the predetermined time, the launch may not be counted as a startup record. Also, for example, conditions regarding the startup location of the specific application may be set. As an example, when the specific application is launched at a predetermined location (for example, inside the store or within the store premises), the launch may be counted as a startup record, and when the specific application is launched at a location different from the predetermined location, the launch may not be counted as a startup record. The startup location may be determined by GPS. Also, if the mobile terminal 60 is connected to the wireless LAN of a certain store, the mobile terminal 60 may be determined to be present at the predetermined location. Note that the launch may be counted as a startup record only when the specific application is launched at a predetermined time and at a predetermined location.

[0128] (7) In the above embodiment, an example of determining whether to display the tutorial screen based on the startup record of a specific application (specifically, the number of past startups) has been described. However, the presence or absence of the tutorial screen may be determined based on other conditions. For example, the presence or absence of the tutorial screen may be determined as follows in (a) to (c) below. (a) Determine the presence or absence of the tutorial screen based on the display record of the tutorial screen (for example, the number of past displays of the first displayed image GA601a, the number of past displays of the last displayed image GA601b). (b) Determine the presence or absence of the tutorial screen based on the barcode reading record (number of readings) of the product or the registration record of the product (number of registered products). Based on the transaction completion record by Service A (for example, the number of settlement completions in the settlement device 50), it is determined whether to display the tutorial screen.

[0129] (8) In the above embodiment, as the screens displayed on the mobile terminal 60, the tutorial screen (Figs. 6(A) to 6(C)), the menu screen (Fig. 6(D)), the initial registration screen (Figs. 7(A) to 7(D)), the registration screen (Figs. 8(A) to 9(C)), the two-dimensional code display screen for settlement (Figs. 9(D), 10(A), 10(B)), and the two-dimensional code reading completion screen for settlement (Fig. 10(C)) have been described. However, the screens displayed on the mobile terminal 60 are not limited to the above screens.

[0130] (Transaction completion screen) The mobile terminal 60 may display a transaction completion screen (not shown) for notifying that the transaction has been completed. For example, when the settlement process is completed in the settlement device 50 (for example, when the receipt printed and issued by the printing unit 113 is removed), the settlement device 50 transmits information indicating that the settlement process has been completed to the cloud server 20. When the cloud server 20 receives the information indicating that the settlement process has been completed from the settlement device 50, the cloud server 20 transmits display instruction information for the transaction completion screen to the mobile terminal 60. When the mobile terminal 60 receives the above instruction information from the cloud server 20, the mobile terminal 60 may display the transaction completion screen. Note that, similar to other screens, the mobile terminal 60 may display an image (animation, slide) on the transaction completion screen (similarly for the status confirmation screen).

[0131] In a mode where the transaction completion screen is not displayed (that is, a mode where the last display in the transaction is the completion screen for reading the two-dimensional code for settlement), the mobile terminal 60 may display, on the completion screen for reading the two-dimensional code for settlement, that the operation by the mobile terminal 60 has ended or that the role of the mobile terminal 60 in the transaction has been completed. For example, the mobile terminal 60 may display, on the completion screen for reading the two-dimensional code for settlement, a message such as "Thank you. The operation on the mobile terminal 60 has been completed, so you can put it away. Subsequent transactions will be performed by the settlement device. Please perform the settlement process using the settlement device." Note that the mobile terminal 60 may transition from the completion screen for reading the two-dimensional code for settlement to the menu screen. For example, the mobile terminal 60 may display, on the completion screen for reading the two-dimensional code for settlement, a message such as "The operation on the mobile terminal 60 has been completed. Return to the menu screen. Subsequent transactions will be performed by the settlement device. Please perform the settlement process using the settlement device." instead of the above-described message, and automatically transition from the completion screen for reading the two-dimensional code for settlement to the menu screen after a predetermined time has elapsed. Also, for example, on the completion screen for reading the two-dimensional code for settlement, a message such as "The operation on the mobile terminal 60 has been completed. Do you want to return to the menu screen?" may be displayed instead of the above-described message, and a button for confirming whether to return to the menu screen may be provided, and when there is an operation of the button to return, the mobile terminal 60 may transition from the completion screen for reading the two-dimensional code for settlement to the menu screen.

[0132] In the mode of displaying the transaction completion screen (that is, the mode in which the last display in the transaction is the transaction completion screen), the mobile terminal 60 displays, on the settlement 2D code reading completion screen, that the operation by the mobile terminal 60 has ended, and after the transaction is completed, separately notifies the completion of the transaction. On the transaction completion screen, it may display that the role of the mobile terminal 60 in the transaction has been completed, including confirmation of the transaction completion (settlement completion). For example, the mobile terminal 60 may display on the settlement 2D code reading completion screen a message such as "Thank you. The operation on the mobile terminal 60 has been completed. Subsequent transactions will be performed by the settlement device. Please perform the settlement process with the settlement device. A message will be displayed after the transaction is completed.", and on the transaction completion screen, a message such as "Since the transaction has been completed, it's okay if you put it away." etc. may be displayed. Note that the mobile terminal 60 may transition from the transaction completion screen to the menu screen. For example, the mobile terminal 60 may display on the transaction completion screen a message such as "The transaction has been completed. Return to the menu screen." etc. instead of the above-mentioned message, and automatically transition from the transaction completion screen to the menu screen after a predetermined time has elapsed. Also, for example, on the transaction completion screen, display a message such as "The transaction has been completed. Do you want to return to the menu screen?" etc. instead of the above-mentioned message, and provide a button to confirm whether to return to the menu screen, and when there is an operation of the button to return, transition from the transaction completion screen to the menu screen.

[0133] The mobile terminal 60 may display that the settlement is in progress in the settlement device 50 (for example, a message such as "Settling with the settlement device"). For example, the mobile terminal 60 may display on the settlement 2D code reading completion screen that the settlement is in progress in the settlement device 50 during the period from receiving the display instruction information of the settlement 2D code reading completion screen (Fig. 16) to receiving the display instruction information of the transaction completion screen.

[0134] Instead of or in addition to the mobile terminal 60 displaying that the settlement in the settlement device 50 is in progress, the settlement device 50 itself may display that the settlement is in progress. For example, on the condition that the settlement two-dimensional code GA631 has been read, the settlement device 50 may display a message such as "The settlement process will start on this device. It's okay if you put away the mobile terminal." (which may also be an animation or a slide). Thereby, a trigger for the customer to put away the mobile terminal 60 can be provided to the customer.

[0135] Also, the settlement device 50 may display that the settlement has been completed. For example, on the condition of the removal of change or receipt (detection of the removal of change, detection of the removal of receipt, etc.), the settlement device 50 may display a message such as "The settlement process has been completed." (which may also be an animation or a slide). In the mode where the mobile terminal 60 displays a transaction completion screen, the settlement device 50 may display a message such as "The settlement process has been completed. The mobile terminal 60 will also be notified of the transaction completion." (which may also be an animation or a slide).

[0136] Note that when the mobile terminal 60 is not the customer's property (customer mobile terminal) but a lent item (store mobile terminal, lent-type mobile terminal) lent by the store side to the customer, or in the case of a shopping cart such as a charging cart (described later), the settlement device 50 may display information regarding return or charging. For example, in the case of a lent-type mobile terminal 60, the settlement device 50 may display a message such as "Please return the lent terminal to the charging stand. Please check the screen of the lent terminal for the return method (charging method)." (which may also be an animation or a slide). Also, in the case of a charging cart (described later) or the like, the settlement device 50 may display a message such as "Please return the cart to the specified location. Please check the screen of the cart for the return method (charging method)." (which may also be an animation or a slide).

[0137] That is, the settlement device 50 can appropriately use messages according to whether the mobile terminal 60 is a customer mobile terminal or a store mobile terminal. Note that by storing information for identifying the store mobile terminal (for example, a contractor-specific ID or a MAC address) in a location accessible to the settlement device 50 (which may be within the device itself or within another device), the settlement device 50 may identify whether the mobile terminal 60 in use (used for product registration) is a customer mobile terminal or a store mobile terminal.

[0138] As described above, in order to display necessary messages (guidance) on both the mobile terminal 60 and the settlement device 50, the customer can concentrate on operating one of the devices (terminals). That is, the customer no longer needs to direct their attention to both devices (terminals), reducing the burden. Therefore, this leads to shortening of processing time (such as settlement time), enabling efficient operation for the store as well.

[0139] (Situation confirmation screen) The mobile terminal 60 may display a situation confirmation screen (not shown) for confirming the situation. Although it has been described that the mobile terminal 60 may include a movement determination unit, for example, the mobile terminal 60 may display the situation confirmation screen when there is no movement and no operation for a predetermined time. On the situation confirmation screen, a message prompting an action (such as product registration or transaction interruption) may be displayed.

[0140] (9) In the above embodiment, the language of the tutorial screen (messages MS602, etc.) is Japanese, but it may be displayed in a foreign language. For example, language specification (setting) may be enabled when downloading (or installing) a specific application or after downloading (or installing), and the tutorial screen may be displayed in the specified language. The same applies to the languages in the menu screen, registration screen (including the initial registration screen and the product scan guide image GA624), 2D code display screen for settlement, 2D code reading completion screen for settlement, transaction completion screen, and situation confirmation screen.

[0141] (10) In the above-described embodiment, an example in which the initial registration screen (product scan guide image GA624) is advanced based on the passage of time has been described. However, the initial registration screen may be advanced based on other conditions. For example, the initial registration screen may be advanced based on operations in the same way as the tutorial screen (tutorial image GA601).

[0142] (11) In the above-described embodiment, an example in which three types (image GA624a, image GA624b, image GA624c) of product scan guide images GA624 are displayed on the initial registration screen has been described. However, the number of types of product scan guide images GA624 does not have to be three. That is, one type of product scan guide image GA624 may always be displayed on the initial registration screen, or two or four or more types of product scan guide images GA624 may be displayed in sequence on the initial registration screen.

[0143] (12) In the above-described embodiment, an example in which the product scan guide image GA624 is displayed on the initial registration screen and not displayed on registration screens other than the initial registration screen has been described. That is, in the above-described embodiment, an example in which the presence or absence (necessity) of the display of the product scan guide image GA624 is determined based on whether it is the first (item) reading in the transaction has been described. However, the number of times of determining the presence or absence of the display of the product scan guide image GA624 is not limited to the first (item). As an example, the product scan guide image GA624 may be displayed until the third (item), and not displayed after the fourth (item).

[0144] (13) In the above-described embodiment, an example in which the product scan guide image GA624 is displayed on the initial registration screen has been described. That is, in the above-described embodiment, an example in which the product scan guide image GA624 is always displayed if it is the first (item) reading in the transaction has been described. However, there may be a case where the product scan guide image GA624 is not displayed in the first (item) reading in the transaction. For example, the presence or absence of the display of the product scan guide image GA624 may be determined as follows in (a) to (c) below. (a) Determine whether to display the product scan guide image GA624 based on whether this transaction is the first time (the first time) to start a specific application. That is, it is displayed only for the first time. (b) Determine whether to display the product scan guide image GA624 based on the reading record (number of readings) of the barcode attached to the product or the registration record (number of registered products) of the product. That is, it is displayed only when the record is less than a predetermined number (quantity). (c) Determine whether to display the product scan guide image GA624 based on the transaction completion record by Service A (for example, the number of settlements completed in the settlement device 50). That is, it is displayed only when the record is less than a predetermined number.

[0145] (14) In the above embodiment, an example in which the product scan guide image GA624 is displayed at a position straddling the imaging image display area HR621 and the registration information display area HR622 (in front of the imaging image display area HR621 and the registration information display area HR622) on the initial registration screen has been described. Specifically, an example in which the upper part of the product scan guide image GA624 is located in front of the area below the barcode reading area of the imaging image display area HR621, and the remaining part of the product scan guide image GA624 is located in front of the area excluding the lower area of the registration information display area HR622 has been described (FIGS. 7(A) to 7(C)). However, the display mode of the product scan guide image GA624 is not limited to this. For example, the product scan guide image GA624 may be displayed as follows in (a) and (b) below. (a) Display all of the product scan guide image GA624 in front of the imaging image display area HR621 (that is, do not display the product scan guide image GA624 in front of the registration information display area HR622). For example, by making the product scan guide image GA624 smaller than the example shown in FIG. 7(A) etc., display all of the product scan guide image GA624 in front of the imaging image display area HR621 (the area excluding the barcode reading area (for example, the area below the barcode reading area)). Note that the position of the barcode reading area in the imaging image display area HR621 may be higher than the example shown in FIG. 7(A) etc. Also, the imaging image display area HR621 may be made wider than the example shown in FIG. 7(A) etc. (the registration information display area HR622 may be made narrower). (b) Display the product scan guide image GA624 in front of the imaging image display area HR621, the registration information display area HR622, and the related information display area HR633 (that is, also display a part of the product scan guide image GA624 in front of the related information display area HR633). For example, by making the product scan guide image GA624 larger than the example shown in FIG. 7(A) etc., or by making the related information display area HR633 wider than the example shown in FIG. 7(A) etc., display the product scan guide image GA624 in front of the imaging image display area HR621, the registration information display area HR622, and the related information display area HR633.

[0146] (15) In the above embodiment, an example of providing the imaging image display area HR621, the registration information display area HR622, and the related information display area HR633 as the configuration of the registration screen (including the initial registration screen) has been described, but the configuration of the registration screen (including the initial registration screen) is not limited to this. For example, the registration screen (including the initial registration screen) may be configured as follows in (a) and (b) below. (a) Provide the imaging image display area HR621 and the registration information display area HR622 on the registration screen (do not provide the related information display area HR633). In the case of this configuration, buttons may be arranged on the registration screen, and information to be displayed in the related information display area HR633 based on the operation of the buttons may be displayed on a separate screen (or a small screen on the registration screen). (b) On the registration screen, only provide the captured image display area HR621 (do not provide the registration information display area HR622 or the related information display area HR633). In the case of such a configuration, when a barcode is read, registration information that would be displayed in the registration information display area HR622 as a separate screen may be displayed. Note that the screen with only the captured image display area HR621 provided may be referred to as the first registration screen, and the above-mentioned separate screen (the screen that displays the registration information to be displayed in the registration information display area HR622) may be referred to as the second registration screen. For example, the mobile terminal 60 may switch from the first registration screen to the second registration screen in response to barcode reading, and switch from the second registration screen to the first registration screen in response to an operation. Note that the mobile terminal 60 may switch from the first registration screen to the second registration screen in response to an operation instead of or in addition to barcode reading.

[0147] (16) In the above embodiment, an example of providing the captured image display area HR621, the registration information display area HR622, and the related information display area HR633 as the configuration of the registration screen (including the initial registration screen) has been described. However, the entire display area of the registration screen (including the initial registration screen) may be referred to as the imaging area. That is, when the through-image of imaging by the imaging unit 316 is displayed in at least a part of the display area of the display unit 305 (the captured image display area HR621 in the above embodiment), the entire display area of the display unit 305 (in the above embodiment, the captured image display area HR621, the registration information display area HR622, and the related information display area HR633) may be referred to as the imaging area. That is, in this embodiment, the lower part of the registration screen may be regarded as a state where the through-image on the back is hidden by the front registration information display area HR622 and the related information display area HR633.

[0148] (17) In the above embodiment, an example of advancing the settlement two-dimensional code display screen (the settlement two-dimensional code scan guide image GA633) based on the passage of time has been described. However, the initial registration screen may be advanced based on other conditions. For example, the settlement two-dimensional code display screen may be advanced based on an operation in the same manner as the tutorial screen (the tutorial image GA601).

[0149] (18) In the above embodiment, an example in which three types of product scan guide images GA624 (image GA633a, image GA633b, image GA633c) are displayed on the settlement two-dimensional code display screen has been described. However, the number of types of the settlement two-dimensional code scan guide image GA633 does not have to be three. That is, one type of settlement two-dimensional code scan guide image GA633 may always be displayed on the settlement two-dimensional code display screen, or two or more than four types of settlement two-dimensional code scan guide images GA633 may be displayed in order on the settlement two-dimensional code display screen.

[0150] (19) In the above embodiment, an example in which the settlement two-dimensional code GA631 is displayed below the message MS632 on the settlement two-dimensional code display screen has been described. However, the settlement two-dimensional code GA631 may be displayed above the message MS632. That is, on the settlement two-dimensional code display screen, as long as at least the settlement two-dimensional code scan guide image GA633 that occupies a relatively large area is displayed below (wrist side, hand side) the settlement two-dimensional code GA631, the member can have the settlement two-dimensional code GA631 read by the settlement device 50 without difficulty.

[0151] (20) Related to the above (19), in the case of the mobile terminal 60 with an elongated display unit 305 (aspect ratio (vertical: horizontal) being, for example, 21:9, etc.), even if the payment 2D code scan guide image GA633 is displayed below the payment 2D code GA631, the distance between the upper end of the payment 2D code display screen and the upper end of the payment 2D code GA631 may become long. Therefore, in the case of the mobile terminal 60 with an elongated display unit 305, the payment 2D code GA631 may be arranged to be packed at the upper end of the payment 2D code display screen so as to shorten the above distance. That is, regardless of the model (type) of the mobile terminal 60, the layout of the payment 2D code display screen may be varied according to the type of the mobile terminal 60 so that the member can easily read the payment 2D code GA631 by the payment device 50. Specifically, the more elongated the mobile terminal 60 is, the more the arrangement position of the payment 2D code scan guide image GA633 on the payment 2D code display screen may be shifted upward.

[0152] (21) In the above embodiment, it has been described that the mobile terminal 60 may include a motion determination unit. However, when the payment 2D code display screen is being displayed, for example, the rotation (change between portrait and landscape screens) of the payment 2D code display screen by an acceleration sensor (gyro sensor) may be prohibited (that is, always displayed in portrait as shown in FIG. 9(D) etc. regardless of movement). Thereby, the payment 2D code display screen will not rotate unnecessarily, so that the member can easily read the payment 2D code GA631 by the payment device 50. Note that the rotation control of the screen (not limited to the payment 2D code display screen, the entire screen) by the acceleration sensor may be prohibited on the condition that the application (specific application) has been launched.

[0153] (22) Although not shown in the above embodiment, information related to settlement (such as the total amount) may be displayed on the two-dimensional code display screen for settlement. For example, the mobile terminal 60 may display "2 items ￥370" as the estimated total on the two-dimensional code display screen for settlement shown in FIGS. 9(D) to 10(B). Note that on the two-dimensional code display screen for settlement, the total amount and the like may be displayed below the two-dimensional code GA631 for settlement (between the two-dimensional code GA631 for settlement and the two-dimensional code scan guide image GA633 for settlement, or between the two-dimensional code scan guide image GA633 for settlement and the button BT639 to return to shopping).

[0154] (23) Although not shown in the above embodiment, a store clerk call button may be displayed on the two-dimensional code display screen for settlement. The store clerk call button may be displayed, for example, below the two-dimensional code GA631 for settlement (for example, between the two-dimensional code scan guide image GA633 for settlement and the button BT639 to return to shopping, or below the button BT639 to return to shopping). Note that when there is an operation of the store clerk call button, the store clerk may be able to identify the mobile terminal 60 related to the store clerk call. For example, the mobile terminal 60 transmits store clerk call information (including member identification information, etc.) based on the operation of the store clerk call button, and the terminal carried by the store clerk or the transaction status management device 40 receives the store clerk call information (for example, receives it via the cloud server 20 or the head office server 10), and may identify the mobile terminal 60 related to the store clerk call (the location information may be transmitted by the mobile terminal 60). Note that the mobile terminal 60 may always display the store clerk call button on the two-dimensional code display screen for settlement, or may display the store clerk call button when a predetermined time (for example, 30 seconds) has elapsed after the start of the two-dimensional code display screen for settlement (or after the operation of the button BT626 to proceed to the cashier arranged on the registration screen) (it may be displayed in a non-operable mode before the elapse of the predetermined time and in an operable mode after the elapse).

[0155] (24) In the above embodiment, an example in which the cloud server 20 generates the settlement two-dimensional code GA631 has been described, but the mobile terminal 60 may generate it. That is, when the mobile terminal 60 receives an operation (operation of the "Proceed to Accounting" button BT626 on the registration screen) declaring that the registration of the product has been completed and proceeding to accounting, it may generate the settlement two-dimensional code GA631 based on the transaction identification information. Note that a device different from both the cloud server 20 and the mobile terminal 60 may generate the settlement two-dimensional code GA631 based on a request from the mobile terminal 60.

[0156] (25) In the above embodiment, an example in which the cloud server 20 determines whether the startup of the specific application is the first time (the first time) has been described, but the mobile terminal 60 may determine it. For example, when starting the specific application, the mobile terminal 60 may inquire of the cloud server 20 about the number of times the application has been started (obtain the number of times information) and determine whether the current startup is the first startup. Also, for example, the mobile terminal 60 itself may store (hold) the number of times the application has been started, and when starting the specific application, refer to the number of times the application has been started stored by itself and determine whether the current startup is the first startup.

[0157] (26) In the above embodiment, an example in which the mobile terminal 60 displays the tutorial screen based on the instruction of the cloud server 20 (instruction information for displaying the tutorial screen) has been described, but the mobile terminal 60 may display the tutorial screen based on its own judgment (control). For example, also related to the above (25), when starting the specific application, the mobile terminal 60 determines whether the current startup is the first startup, and when it is determined that it is the first startup, it may display the tutorial screen.

[0158] (27) In the above embodiment, an example where the mobile terminal 60 displays a menu screen based on an instruction from the cloud server 20 (display instruction information for the menu screen) has been described. However, the mobile terminal 60 may display a menu screen based on its own judgment (control). For example, although it is also related to the above (25)(26), the mobile terminal 60 determines whether the current startup is the first startup when a specific application is started. If it determines that it is not the first startup, it may display a menu screen. Also, for example, the mobile terminal 60 determines whether an operation instructing the start of a service (operation of the service start button BT604 on the tutorial screen) has been received. If it determines that the operation has been received, it may display a menu screen instead of the tutorial screen.

[0159] (28) In the above embodiment, an example where the cloud server 20 determines whether a single item of merchandise has already been registered has been described. However, the mobile terminal 60 may make the determination. For example, the mobile terminal 60 may refer to the merchandise information it stores (merchandise information obtained from the cloud server 20 after reading the merchandise) and determine whether a single item of merchandise has already been registered.

[0160] (29) In the above embodiment, an example where it is determined whether to display an initial registration screen (merchandise scan guide image GA624) based on whether a single item of merchandise has already been registered has been described. However, the determination may be made based on other conditions. For example, the determination may be made as follows in (a) and (b) below. (a) When the cloud server 20 receives shopping start instruction information (step S42 in FIG. 13), it determines to display an initial registration screen (merchandise scan guide image GA624). When the cloud server 20 receives a merchandise code or the like (steps S52, S62 in FIG. 14), it determines not to display an initial registration screen (merchandise scan guide image GA624) (simply determines to display a registration screen). (b) When the mobile terminal 60 receives an operation for declaring the start of shopping (operation of the shopping start button BT610 on the menu screen) (step S40 in FIG. 13), it determines to display the initial registration screen (product scan guide image GA624). When the mobile terminal 60 reads a product code (steps S50 and S60 in FIG. 14), it determines not to display the initial registration screen (product scan guide image GA624) (simply determines to display the registration screen). Note that the above (a) is a mode in which the mobile terminal 60 displays the initial registration screen (product scan guide image GA624) and the registration screen based on the instruction of the cloud server 20. The above (b) is a mode in which the mobile terminal 60 displays the initial registration screen (product scan guide image GA624) and the registration screen based on its own judgment.

[0161] (30) In the above embodiment, an example in which the mobile terminal 60 displays the settlement two-dimensional code display screen based on the instruction of the cloud server 20 (display instruction information of the settlement two-dimensional code display screen) has been described. However, the mobile terminal 60 may display the settlement two-dimensional code display screen based on its own judgment (control). For example, the mobile terminal 60 determines whether or not to receive an operation for declaring the completion of product registration and proceeding to accounting (operation of the proceed to accounting button BT626 on the registration screen). When it determines that the operation has been received, it may display the settlement two-dimensional code display screen instead of the registration screen.

[0162] In the above embodiment, an example has been described in which the mobile terminal 60 stores screen information and displays a screen based on the screen information and the like stored by itself. However, the mobile terminal 60 does not necessarily store the screen information. For example, the mobile terminal 60 may display various screens based on the screen information generated (updated) by the cloud server 20 without storing the screen information. As an example, the tutorial screen will be described. The processes shown in steps S5 to S7 in FIG. 11 may operate as follows. The cloud server 20 generates screen information for the tutorial screen and transmits it to the mobile terminal 60. The mobile terminal 60 displays the tutorial screen based on the screen information received from the cloud server 20. As another example, the initial registration screen will be described. The processes shown in steps S45 to S47 in FIG. 13 may operate as follows. The cloud server 20 generates screen information for the initial registration screen (the product information and the like are empty), and transmits the generated image information to the mobile terminal 60 together with the product scan guide image GA624. The mobile terminal 60 displays the initial registration screen based on the screen information received from the cloud server 20, and displays the product scan guide image GA624 in front of the initial registration screen. Note that the screens such as the tutorial screen and the registration screen may be WEB pages provided by the cloud server 20 and browsed by the mobile terminal 60. Note that the format of the image such as the product scan guide image GA624 is not limited, and for example, it may be GIF (animated GIF). The reproduction (display) of the image may be reproduction after download or reproduction during download (streaming reproduction).

[0163] (32) In the above embodiment, the tutorial screen (tutorial image GA601) is erased with the display of the menu screen (step S14 in FIG. 11), the initial registration screen (product scan guide image GA624) is erased with the display of the registration screen (step S57 in FIG. 14), and the payment two-dimensional code display screen (payment two-dimensional code scan guide image GA633) is erased with the display of the payment two-dimensional code reading completion screen (step S88 in FIG. 16). That is, in the above embodiment, an example of erasing the guidance image (tutorial image GA601, product scan guide image GA624, payment two-dimensional code scan guide image GA633) from the screen is described as an aspect when the necessity for guidance disappears or weakens. However, as an aspect when the necessity for guidance disappears or weakens, it is only necessary to substantially stop the guidance, and it is not limited to the aspect of erasing the guidance image. For example, instead of erasing the guidance image, the guidance image may be displayed in a small size (for example, displayed in an iconized form). Further, instead of or in addition to displaying the guidance image in a small size, the guidance image may be displayed at an inconspicuous position.

[0164] (33) In the above embodiment, an example of using the mobile terminal 60 by attaching it to the shopping cart has been described, but it is not necessary to attach the mobile terminal 60 to the shopping cart for use. For example, the mobile terminal 60 may be used while being held in the hand. Note that some of the images (for example, the image GA601b in FIG. 6(B) and the image GA624a in FIG. 7(A)) are images adapted to the mode of using the mobile terminal 60 by attaching it to the shopping cart. Therefore, when the mobile terminal 60 is used while being held in the hand, an image adapted to the mode of using it while being held in the hand is used.

[0165] (34) In the above-described embodiment, the mobile terminal 60 was mainly described as being the customer's possession (customer mobile terminal). However, as described above, it may be a lent item (store mobile terminal) lent by the store side to the customer. By storing information (for example, a contractor-specific ID or MAC address) for identifying the mobile terminal 60 (store mobile terminal) lent by the store side, it is possible to distinguish whether the mobile terminal 60 being used or having been used is a store mobile terminal (that is, whether it is a customer mobile terminal or a store mobile terminal). In the case of a store mobile terminal, it may be configured to request the input of a membership number and determine whether it is the first startup or a subsequent startup.

[0166] (35) In the above-described embodiment, an example in which the customer registers a product using the mobile terminal 60 was described. However, any mobile (portable) device capable of registering a product at the product display location may be used instead of the mobile terminal 60. For example, a tablet terminal (possession, lent) or a shopping cart equipped with a display unit (or a display detachable from the shopping cart) may be used to register a product. That is, the above-described shopping cart (equipped with a display unit or having a detachable display) may display a tutorial screen (FIGS. 6(A) to 6(C)), a menu screen (FIG. 6(D)), an initial registration screen (FIGS. 7(A) to 7(D)), a registration screen (FIGS. 8(A) to 9(C)), a 2D code display screen for settlement (FIGS. 9(D), 10(A), 10(B)), a 2D code reading completion screen for settlement (FIG. 10(C)), a transaction completion screen (not shown), and a status confirmation screen (not shown). The above-described shopping cart (equipped with a display unit or having a detachable display) may have the same configuration as the mobile terminal 60 (the configuration shown in FIG. 4) (each member of the configuration may be detachable).

[0167] The above shopping cart (a shopping cart equipped with a display unit or a display device that is detachable) may be equipped with an electronic tag recognition unit that recognizes the information of the electronic tag (hereinafter referred to as an electronic tag recognition cart). Further, the above shopping cart (which may be an electronic tag recognition cart) may be equipped with a battery (a battery that powers the display unit or the display device) and be rechargeable (hereinafter referred to as a rechargeable cart). The charging of the rechargeable cart is performed, for example, at a cart storage area (a place where at least one of lending out the shopping cart and returning the shopping cart is carried out). For example, a charging device (charging facility) may be installed at the cart storage area, and the rechargeable cart may be charged by the charging device. The charging method (system) may be contact (contact charging) or non-contact (non-contact charging). In the case of contact charging, for example, a cable or the like is connected to the rechargeable cart for charging. At the cart storage area, the same number of cables or the like as the number of rechargeable carts that can be stored (the maximum number of standby carts before lending) are prepared (arranged at their respective storage positions if storage positions are set). In the case of non-contact charging, for example, a non-contact charging system (a power supply (transmission) unit and a power reception (reception) unit) is provided on the rechargeable cart side and the cart storage area (charging facility) side respectively, and the power transmitted from the power supply unit on the cart storage area side is received by the power reception unit on the rechargeable cart side for charging. At the cart storage area, the same number of power supply units as the number of rechargeable carts that can be stored are provided as in the case of contact charging, and they may be arranged in pairs for power supply and reception, or a large power supply unit capable of transmitting power to a plurality of rechargeable carts (power reception units) collectively may be arranged. Note that for the withdrawal of the rechargeable cart, the return of the rechargeable cart, and the charging of the rechargeable cart (contact charging, non-contact charging) at the cart storage area, it may be performed by a store clerk or by a customer (requested by the store side to the customer). When charging is entrusted to the customer, the store clerk may periodically check the charging status (such as whether it is being charged correctly).

[0168] In the case of a shopping cart not equipped with a battery (a shopping cart that is not a charging cart, which may be an electronic tag recognition cart), charging to the display unit or the display may be performed on the display unit or the display. Note that, unlike a shopping cart equipped with a detachable display, in the case of a shopping cart equipped with a non-detachable display unit and charging is performed on the display unit, it is also understood that charging is performed on a part (display unit) of the shopping cart. Therefore, a shopping cart equipped with a display unit on which charging is performed may be referred to as a "charging cart".

[0169] When leaving the return of the charging cart to the customer, it may be communicated to the customer regarding the return. For example, the charging cart (the program of the charging cart) may display guidance information (guidance) regarding the return on the display unit (or the display) on the condition that the transaction information has been transferred to the settlement device 50 (the settlement device 50 has read the settlement two-dimensional code GA631) or the settlement has been completed in the settlement device 50. As an example, the charging cart may display guidance for returning to the cart collection area on the display unit (or the display) on the settlement two-dimensional code reading completion screen (Figure 10(C)) or the transaction completion screen (not shown). The above guidance may include map information (floor information) indicating the return destination (cart collection area). Note that the same applies to a shopping cart not equipped with a battery (which may be an electronic tag recognition cart) regarding the return.

[0170] When leaving the charging of the charging cart to the customer, it may be communicated to the customer regarding the charging. For example, the charging cart (the program of the charging cart) may display guidance information (guidance) regarding the charging on the display unit (or the display) on the condition that the transaction information has been transferred to the settlement device 50 or the settlement has been completed in the settlement device 50. As an example, the charging cart may display guidance regarding the connection method of a cable or the like and guidance regarding the non-contact charging method on the display unit (or the display) on the settlement two-dimensional code reading completion screen or the transaction completion screen.

[0171] Guidance on the connection method of cables or the like may guide one or more of the following (a) to (c), for example. (a) Available cables or the like. For example, the foremost (nearest) unused cable or the like among a plurality of cables or the like prepared at the cart storage (b) Connection method of cables or the like. For example, regarding the insertion port of the cable or the like, for example, the position of the insertion port on the charging cart, the insertion direction, and the depth (c) Confirmation that the cable or the like is correctly connected (charging has started). For example, the cart device displays that power is being supplied on the screen. Or, the cart device is provided with a light-emitting unit (LED) that notifies that power is being supplied, and the light-emitting unit displays that power is being supplied. Note that, although also related to the above (c), on the cart storage side, an LED corresponding to each cable or the like may be provided (for example, provided for each cable or the like) so that it is possible to confirm that power is being supplied.

[0172] Guidance on the non-contact charging method may guide one or more of the following (a) to (c), for example. (a) Available parking areas. For example, the foremost (nearest) unused parking area among a plurality of parking areas provided at the cart storage (places where non-contact charging of each charging cart is possible) (b) Parking position. The parking position (positioning) in the parking area (c) Confirmation that the parking position is appropriate (charging has started) (similar to the guidance on the connection method of cables or the like) Note that, in relation to the above (b), in the case of non-contact power supply, since there is no physical connection, for example, an illustration of "△" or the like is described on the power supply unit, and an illustration of "▽" or the like corresponding to "△" of the power supply unit is described on the power receiving unit, and it may be indicated on the display unit (or display) to park so that the vertices of "▽" and "△" overlap. Since the actual illustration or the like is also displayed on the screen, the customer can intuitively grasp the parking position.

[0173] The same applies when the mobile terminal 60 is not the customer's property (customer mobile terminal) but a lent item (store mobile terminal, lent-type mobile terminal) lent by the store side to the customer. As an operation of the lent-type mobile terminal 60, an operation of leaving the return to the customer is assumed. However, when leaving the return of the lent-type mobile terminal 60 to the customer, similar to the case of leaving the return of the charging cart to the customer, guidance on the return method of the lent-type mobile terminal 60 may be displayed, for example, on the settlement two-dimensional code reading completion screen or the transaction completion screen. The above guidance may include map information (floor information) indicating the return destination (the return location of the lent-type mobile terminal 60, return device, etc.). Also, as an operation of the lent-type mobile terminal 60, when leaving the charging of the lent-type mobile terminal 60 to the customer, similar to the case of leaving the charging of the charging cart to the customer, guidance on the charging method of the lent-type mobile terminal 60 may be displayed, for example, on the settlement two-dimensional code reading completion screen or the transaction completion screen. The above guidance may include operation information indicating the charging method (operation method of the charging device which is the return device, etc.).

[0174] By displaying the above guidance (guidance information), the store staff can reduce the troublesome work burden such as the collection and charging of the charging cart and the portable lending device, and can realize store operation with a small number of people.

[0175] In the above-described embodiment, the transaction status management device 40 was described as a device that mainly manages (monitors and controls) each device within the LAN 19. However, the transaction status management device 40 may also manage (monitor and control) a cart aggregation station or the like. That is, the transaction status management device 40 can communicate with a device installed at the cart aggregation station or the shopping cart itself existing at the cart aggregation station. For example, it may display on the management screen the number of shopping carts existing at the cart aggregation station (regardless of whether they are electronic tag recognition carts or charging carts; in the case where the cart aggregation station is a lending / return location or a lending location, the number of waiting carts). Further, when the shopping cart is a charging cart, the transaction status management device 40 may display on the management screen the charging status (such as battery remaining amount) of each charging cart at the cart aggregation station, the number of available charging carts (charging carts with a battery remaining amount equal to or greater than a reference value), and so on. Instead of or in addition to the charging status of each charging cart at the cart aggregation station, the transaction status management device 40 may display on the management screen the charging status of charging carts within the store (during lending), etc. In this case, the charging cart may transmit information regarding the battery remaining amount to the transaction status management device 40 via wireless communication. Note that the transaction status management device 40 may similarly manage (monitor and control) the return locations (return devices, charging devices) of the lent portable terminals 60.

[0176] (37) The transaction status management device 40 may display the operation history information of each device. For example, the transaction status management device 40 may display the operation history information of each device within the LAN 19, the mobile terminal 60 (including the lent mobile terminal 60), and the shopping cart (which may be an electronic tag recognition cart or a charging cart). The operation history includes, for example, the usage start time, the registration time of each product, the registration completion time, the settlement start time, the settlement end time, the transaction completion time, the lending time and return time if the mobile terminal 60 is a lent item, information regarding screen transitions, information regarding operations (including changes in the registered quantity of products, etc.), and the registration information of products. The operation history information includes both the history information regarding the operations of transactions after completion and the history information regarding the operations of transactions before completion (the operations of the current transaction up to the present). Therefore, a store employee (monitoring employee) can, using the transaction status management device 40, confirm, for example, on which screen and for how long a certain mobile terminal 60 (a certain customer) has stayed.

[0177] (38) The transaction status management device 40 may remotely control the display of guidance information in the mobile terminal 60 (including the lent mobile terminal 60), the shopping cart (which may be an electronic tag recognition cart or a charging cart), etc. In other words, the mobile terminal 60, etc. may display the guidance information according to the remote control by the transaction status management device 40. For example, the transaction status management device 40 may be able to accept an operation of selecting (designating) the target device (customer) and the target guidance (type of guidance), and based on the selection operation by the store employee, transmit information for causing the selected guidance to be displayed to the selected terminal.

[0178] According to the above (37) and (38), for example, a store clerk can infer the situation (such as a troubled situation) of each customer (each device) in the transaction situation management device 40 and provide suitable guidance to the necessary customers by remote operation. That is, a plurality of customers can be efficiently supported (guided) at a predetermined location (if there is one transaction situation management device 40, it is one location). In addition, the transaction situation management device 40 may transmit map information (floor information) in which the service counter position and the installation position of the transaction situation management device 40 are clearly shown to the necessary customers (devices) as guidance (or separately from the guidance) to guide the customers. Note that the mobile terminal 60 or the like may display map information based on the operation of the customer (for example, the operation of a help button or the like) so that the customer can appropriately confirm the service counter position or the like regardless of whether transmission is performed. Note that the mobile terminal 60 or the like may store the map information and display the stored map information based on the operation of the customer, or may request the transaction situation management device 40 for the map information based on the operation of the customer and display it. In the former case, the mobile terminal 60 or the like may notify the transaction situation management device 40 that an operation such as a help button has been performed.

[0179] <Summary of the Embodiment> [Technical Field] The present invention relates to a program and a product sales data processing device. [Background Art] A self-service system in which a customer registers a product using a mobile terminal has been proposed. On the other hand, a system for displaying guidance for an imaging target product is known (see, for example, Patent Document 1). [Prior Art Document] [Patent Document] [Patent Document 1] Japanese Patent Application Laid-Open No. 2015-53030 [Summary of the Invention] [Problems to be Solved by the Invention] However, there are also customers who are not accustomed to the self-service system as described above. Such a system cannot support such customers. The present invention has been made in view of such circumstances, and an object thereof is to provide a technology that enables even beginners to easily use services using a mobile terminal. [Means for Solving the Problems]

[0180] (1) A program that causes a computer to function as a product sales data processing device (for example, a mobile terminal 60, a shopping cart, etc.), the computer being an imaging means (for example, an imaging unit 316) for imaging a product to be purchased, a guiding means for guiding an operator using a guiding image (for example, a tutorial image GA601, a product scan guide image GA624, a settlement two-dimensional code scan guide image GA633, an image GA627) for guiding a procedure, and a display means (for example, a display unit 305) capable of displaying an imaging image captured by the imaging means, wherein the display means displays a part or all of a first guiding image (for example, a product scan guide image GA624) that is one of the guiding images in an imaging image display area (for example, an imaging image display area HR621) for displaying the imaging image, and the guiding means ends the guidance using the first guiding image based on a predetermined condition (for example, registration of one item of product). (1) According to the program of (1), even beginners can easily use it.

[0181] (2) The display means is capable of displaying detailed information of a product to be purchased, and the first guiding image (for example, a product scan guide image GA624) is displayed across a detailed information display area (for example, a registration information display area HR622) for displaying the detailed information and the imaging image display area (for example, an imaging image display area HR621). The program according to (1). (2) According to the program of (2), even beginners can easily use it.

[0182] (3) Cause the computer to function as operation reception means (for example, button BT626 to proceed to the payment) capable of receiving an operation to proceed to the payment. The operation reception means does not receive the operation before the guidance using the first guidance image ends (see Fig. 7(D)), and receives the operation after the guidance using the first guidance image ends (see Fig. 8(A)). The program according to (1) or (2) is characterized in this regard. (3) According to the program of (3), even a beginner can easily use it.

[0183] (4) The display means can display a payment code (for example, two-dimensional payment code GA631) for paying for the purchased product. When displaying the payment code, a second guidance image (for example, two-dimensional payment code scan guide image GA633) different from the first guidance image (for example, product scan guide image GA624) among the guidance images is displayed below the payment code. The program according to any one of (1) to (3) is characterized in this regard. (4) According to the program of (4), even a beginner can easily use it.

[0184] (5) The guidance image is displayed on a mobile terminal (for example, mobile terminal 60) used by a customer who purchases a product. The guidance means varies the mode of guidance using the guidance image (for example, tutorial image GA601) based on the number of times the customer uses the mobile terminal (for example, the number of startups). The program according to any one of (1) to (4) is characterized in this regard. (5) According to the program of (5), the guidance image can be suitably displayed.

[0185] (6) An imaging means for imaging a product to be purchased, a guiding means for guiding an operator using a guiding image for guiding a procedure, and a display means capable of displaying an imaging image obtained by the imaging means, wherein the display means displays part or all of a first guiding image which is one of the guiding images in an imaging image display area for displaying the imaging image, and the guiding means ends the guidance using the first guiding image based on a predetermined condition, and is a product sales data processing device (for example, a mobile terminal 60, a shopping cart, etc.). (6) According to the product sales data processing device, even a beginner can easily use it.

[0186] (7) A program for causing a computer to function as a product sales data processing device (for example, a mobile terminal 60, a shopping cart, etc.), causing the computer to function as an imaging means for imaging a product and a display means for displaying a guiding image for guiding an operator through a procedure, and the display means overlays and displays part or all of the guiding image on the imaging image during imaging by the imaging means (see FIG. 7(D)), and the guidance of the procedure by the guiding image ends based on a predetermined condition. (7) According to the program, even a beginner can easily use it.

[0187] Note that, in order to implement the functions of each of the devices described above (head office server 10, store controller 30, transaction status management device 40, settlement device 50, registered settlement device 51, mobile terminal 60, shopping cart, etc.), a program (for example, a specific application in the mobile terminal 60, etc.) may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be read into a computer system and executed to perform the processing of each of the above devices. Here, "reading the program recorded on the recording medium into the computer system and executing it" includes installing the program in the computer system. The "computer system" as used herein shall include hardware such as an OS and peripheral devices. Further, the "computer system" may include a plurality of computer devices connected via a network including a communication line such as the Internet, WAN, LAN, dedicated line, etc. Also, the "computer-readable recording medium" refers to a portable medium such as a flexible disk, magneto-optical disk, ROM, CD-ROM, etc., and a storage device such as a hard disk built into the computer system. Thus, the recording medium storing the program may be a non-transitory recording medium such as a CD-ROM. Also, the recording medium includes an internal or external recording medium provided and accessible from a distribution server for distributing the program. The code of the program stored in the recording medium of the distribution server may be different from the code of the program in a form executable by the terminal device. That is, as long as it can be downloaded from the distribution server and installed in a form executable by the terminal device, the form stored in the distribution server does not matter. Note that the program may be divided into a plurality of parts, downloaded at different timings, and then combined in the terminal device, or the distribution servers for distributing each of the divided programs may be different. Furthermore, the "computer-readable recording medium" shall also include a volatile memory (RAM) inside a computer system that becomes a server or a client when a program is transmitted via a network and holds the program for a certain period of time. Also, the above program may be for realizing a part of the functions described above.Furthermore, it may be a so-called differential file (differential program) that can be realized in combination with a program already recorded in the computer system to perform the above-described functions.

Description of Signs

[0188] 1…Sales system 10…Headquarters server 20…Cloud server 30…Store controller 40…Transaction status management device 50…Settlement device 51…Registered settlement device 60…Mobile terminal

Claims

1. A program that causes a computer to function as a product sales data processing device, The computer Imaging means for capturing an image of the product; a display means capable of displaying an image captured by the imaging means; a registration means for registering the product imaged by the imaging means; It functions as The display means A guide image for guiding the procedure can be displayed to guide the operator through the procedure, A program characterized by displaying a first guide image, which is one of the guide images, to provide guidance on how to register a product, and when the guidance on the registration method has been completed, displaying a second guide image, which is also one of the guide images, to provide guidance on how to proceed to checkout.

2. The display means When the guidance on the registration method is completed, detailed information of the product registered by the registration means is displayed.

2. The program according to claim 1 .

3. The computer: functioning as a declaration means for declaring the start of product registration by the registration means; The display means When the start of product registration is declared by the declaration means, the first guide image is displayed to provide guidance on how to register the product.

3. The program according to claim 1 or 2.

4. The display means The manner of guidance using the guidance image is varied based on the number of times the operator has used the product sales data processing device.

4. The program according to claim 1, wherein the program is a program for executing a program for executing a program for executing a program.

5. Imaging means for capturing an image of a product; a display means capable of displaying an image captured by the imaging means; a registration means for registering the product imaged by the imaging means; Equipped with The display means A guide image for guiding the procedure can be displayed to guide the operator through the procedure, A first guide image, which is one of the guide images, is displayed to provide guidance on how to register the product, and when the guidance on the registration method is completed, a second guide image, which is one of the guide images, is displayed to provide guidance on how to proceed to checkout. A product sales data processing device characterized by:

Images