System, information processor, and program

Abstract

To handle customers efficiently.SOLUTION: A system allows a customer himself / herself to register articles using a portable terminal device. The system includes registration means, determination means, and guidance means. The registration means registers the articles identified by the portable terminal device. The determination means determines whether or not the articles registered by the registration means include a predetermined article that requires the intervention of a clerk. The guidance means performs guidance to the portable terminal device based on a determination result of the determination means. When the determination means determines that the predetermined article is included, the guidance means performs first guidance to encourage the customer to move to a transaction status management device operated by the clerk. When it is determined by the determination means that the predetermined article is not included, the guidance means performs second guidance to prompt the customer to move to a settlement device.SELECTED DRAWING: Figure 4

Description

Technical Field

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

Background Art

[0002] In recent years, in stores and the like, a so-called self-service sales form in which customers register and settle goods has become widespread. For example, a system is known in which a customer registers goods using a portable terminal device held by the customer and then settles the goods at a settlement device (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, in the prior art, there has been a problem that it may not be possible to efficiently handle customers heading for settlement.

[0005] The present invention has been made in view of such circumstances, and an object thereof is to provide a technique capable of efficiently handling customers.

Means for Solving the Problems

[0006] In order to solve the above-described problems, a system according to an aspect of the present invention is a system in which a customer himself / herself uses a portable terminal device to register a product, the system including: a registration unit that registers a product specified by the portable terminal device; a determination unit that determines whether or not a predetermined product that requires the intervention of a store clerk is included in the product registered by the registration unit; and a guidance unit that provides guidance to the portable terminal device based on the determination result of the determination unit. The guidance unit provides a first guidance for prompting movement to a transaction status management device operated by a store clerk when the determination unit determines that the predetermined product is included, and provides a second guidance for prompting movement to a settlement device when the determination unit determines that the predetermined product is not included. The system is characterized by this.

[0007] In order to solve the above-described problems, an information processing apparatus according to an aspect of the present invention is an information processing apparatus in which a customer himself / herself uses a portable terminal device to register a product, the information processing apparatus including: a registration unit that registers a product specified by the portable terminal device; a determination unit that determines whether or not a predetermined product that requires the intervention of a store clerk is included in the product registered by the registration unit; and a guidance unit that provides guidance to the portable terminal device based on the determination result of the determination unit. The guidance unit provides a first guidance for prompting movement to a transaction status management device operated by a store clerk when the determination unit determines that the predetermined product is included, and provides a second guidance for prompting movement to a settlement device when the determination unit determines that the predetermined product is not included. The information processing apparatus is characterized by this.

[0008] In order to solve the above-described problems, a program according to one aspect of the present invention is a program that causes a computer to function as a system in which a customer registers a product using a mobile terminal device. The computer is caused to function as a registration unit that registers a product specified by the mobile terminal device, a determination unit that determines whether or not a predetermined product that requires the intervention of a store clerk is included in the product registered by the registration unit, and a guidance unit that provides guidance to the mobile terminal device based on the determination result of the determination unit. The guidance unit performs a first guidance that prompts movement to a transaction status management device operated by a store clerk when the determination unit determines that the predetermined product is included, and performs a second guidance that prompts movement to a settlement device when the determination unit determines that the predetermined product is not included. This is a characteristic program.

[0009] In order to solve the above-described problems, a program according to one aspect of the present invention is a program that causes a computer to function as an information processing device in which a customer registers a product using a mobile terminal device. The computer is caused to function as a registration unit that registers a product specified by the mobile terminal device, a determination unit that determines whether or not a predetermined product that requires the intervention of a store clerk is included in the product registered by the registration unit, and a guidance unit that provides guidance to the mobile terminal device based on the determination result of the determination unit. The guidance unit performs a first guidance that prompts movement to a transaction status management device operated by a store clerk when the determination unit determines that the predetermined product is included, and performs a second guidance that prompts movement to a settlement device when the determination unit determines that the predetermined product is not included. This is a characteristic program.

Brief Description of the Drawings

[0010]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8A

Figure 8B

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Embodiments for Carrying Out the Invention

[0011] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings.

[0012] (Network Configuration of Shopping System St) FIG. 1 is an explanatory diagram showing the network configuration of a shopping system St according to an embodiment. The shopping system St is an example of a system. The shopping system St can be introduced into various stores such as supermarkets, home centers, convenience stores, and various supply stores. The shopping system St is a system in which customers themselves register products using a portable terminal device 40.

[0013] In FIG. 1, the shopping system St includes a cloud server 1, a store controller 10, a transaction status management device 20, a settlement device 30, and a portable terminal device 40. Each device is a computer device equipped with a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), a communication unit, and the like. Each device is communicably connected via a network. For example, the store controller 10, the transaction status management device 20, and the settlement device 30 are communicably connected via a LAN (Local Area Network) 55, respectively.

[0014] (Cloud Server 1) The cloud server 1 is arranged outside the store. The cloud server 1 is a server device that includes a product registration DB (database) 2 and a usage status DB 3 and manages various types of information. The various types of information include, for example, product registration product data (cart information) based on instructions from the mobile terminal device 40, information indicating the usage status of the settlement device 30, and the like. In addition, the various types of information include various types of information related to customers and stores, product information (product master) related to products for each store, and the like. The product master is a file that stores product information such as product identification information (for example, JAN (Japanese Article Number) code), product name, and selling price for each product. In addition, the product master includes various types of information such as product identification information, product name, and weight unit price for products that require weighing.

[0015] The registered product data is the cart information on the virtual cart. The registered product data is generated as information indicating a virtual cart for each customer. Specifically, the registered product data includes transaction identification information (cart identification information) that identifies one transaction (cart). In addition, the registered product data includes information on the registered products (product name, price, quantity, registration date and time, etc.). The registered product data is updated based on the product code read by the mobile terminal device 40.

[0016] (Store Controller 10) The store controller 10 manages the settlement device 30 and stores various types of information necessary for transactions such as the product master. In addition to the product master, the store controller 10 also stores various types of information such as inventory status, sales history, and deposit and withdrawal records. Note that the store controller 10 may store customer membership information.

[0017] If the synchronization between the cloud server 1 and the store controller 10 is ensured, the mobile terminal device 40, the payment device 30, and the transaction status management device 20 can operate the shopping system St by referring to the data stored in the cloud server 1. The shopping system St is a general-purpose system, and it is possible for the cloud server to be responsible for the storage area for the registration data of the mobile terminal device 40 and the registered data. Also, in the payment process, the payment device 30 may preferentially acquire the product information of the store controller 10 in order to refer to the selling price in the store. Furthermore, if the shopping system St is a small-scale system that closes in one store, a web server for registered products may be placed inside the store, and the system may be operated separately from or in cooperation with the store controller 10.

[0018] (Transaction Status Management Device 20) The transaction status management device 20 can display a confirmation screen for the products registered in the mobile terminal device 40 and a confirmation screen for the content displayed on the payment device 30. A support staff member who supports customers is assigned to the transaction status management device 20. The support staff member supports the customer operating the payment device 30 or, when the store staff confirmation product is included in the registered product, confirms the product. The store staff confirmation product is, for example, an age confirmation product such as an alcoholic beverage.

[0019] Note that the shopping system St may include a portable transaction status management device 20 (store staff terminal device) held by the staff member instead of or in addition to the installed transaction status management device 20. The portable transaction status management device 20, for example, displays the same content as that displayed on the installed transaction status management device 20 or notifies that the staff member is called. Also, the portable transaction status management device 20 may call the staff member to a predetermined location (for example, the location where the customer is) and have the staff member confirm the store staff confirmation product.

[0020] (Payment Device 30) The payment device 30 is a device that is operated by a customer to perform payment (self - payment). The payment device 30 acquires registered product data registered based on the operation of the mobile terminal device 40 and performs payment. Note that the payment device 30 may be provided with a function of registering products in addition to the function of performing payment. In other words, the shopping system St may be provided with a registration - payment device instead of the payment device 30. Also, the registration - payment device may be a full - self - type device in which both product registration and payment are performed by the customer.

[0021] Here, the registration - payment device is supplemented. The registration - payment device may operate in any one of a plurality of operation modes. Specifically, the operation modes include, for example, an accounting - only mode, a full - self mode, and a clerk - registration mode. The accounting - only mode is a mode for performing self - payment. In the accounting - only mode, payment is made by the customer himself / herself based on registration information generated by other devices such as the mobile terminal device 40 or a registration device (registration - payment device in the clerk - registration mode) by which a clerk registers products. The acquisition mode of the registration information includes an acquisition mode by receiving from the cloud server 1, an acquisition mode by receiving from another registration - payment device, and an acquisition mode by reading an accounting ticket (registered trademark) on which a symbol code for acquiring a transaction to be paid is printed. The full - self mode is a mode in which the customer registers products (self - registration) with the device itself and the customer performs payment (self - payment) with the device itself. Note that in the full - self mode, similar to the accounting - only mode, self - payment may be performed based on registration information generated by other devices. The clerk - registration mode is a mode in which a clerk registers products and the customer performs payment (face - to - face payment) with the clerk face - to - face. Also, in the clerk - registration mode, it is possible to transmit payment information to other registration - payment devices in the accounting - only mode or the payment device 30, or to issue an accounting ticket.

[0022] (Mobile terminal device 40) The mobile terminal device 40 is a portable terminal device owned by a customer. The mobile terminal device 40 is, for example, a smartphone, a tablet device, a mobile phone, etc. The mobile terminal device 40 is provided with a communication unit, an imaging unit (camera), a scanner, a touch panel, etc., and is operated by a customer. The mobile terminal device 40 is detachably attached to the shopping cart. Also, the mobile terminal device 40 is a terminal device owned by the customer.

[0023] Note that the mobile terminal device 40 may be a lending terminal device lent by the store to the customer. When not in use, the lending terminal device is connected to a charger installed at the entrance of the store or the like. The lending terminal is attached to the shopping cart when in use. Note that the lending terminal device may be one (non-detachable) installed on the shopping cart.

[0024] An application software (hereinafter referred to as "shopping app") for registering products related to the shopping system St and settling the registered products is installed in the mobile terminal device 40. By starting the shopping app, the mobile terminal device 40 accepts product registration by scanning (reading) the product (barcode) attached to the product. When the mobile terminal device 40 reads the product code attached to the product, it transmits the read code information together with the transaction identification information assigned to the device itself to the cloud server 1. As a result, the product information corresponding to the code information is added and registered in the registered product data of the cloud server 1.

[0025] Also, when the mobile terminal device 40 receives an operation to start settlement, it displays a settlement code obtained by encoding the transaction identification information. The settlement code is represented by, for example, a two-dimensional code (QR code (registered trademark)), but may also be represented by a one-dimensional code (barcode). The code information is a code capable of identifying transaction information, a URL of the transaction information storage destination, transaction information (registered product data, that is, product code and quantity), etc.

[0026] When the transaction status management device 20 and the settlement device 30 each read the settlement code, they send a request to the cloud server 1 to transmit the registered product data (transaction information) indicated by the transaction identification information. Then, the transaction status management device 20 and the settlement device 30 each receive the registered product data from the cloud server 1 in response to the transmission request. The transaction status management device 20 can list-display the received registered product data to prompt the store clerk to confirm the products to be confirmed. The settlement device 30 can perform self-settlement based on the received registered product data.

[0027] Note that the mobile terminal device 40 is not limited to accepting product registration operations using the shopping app. For example, the mobile terminal device 40 may accept product registration operations using a web browser.

[0028] (Hardware Configuration of Computer Device) FIG. 2 is a block diagram showing the hardware configuration of the computer of each device included in the shopping system St. The computer 200 is implemented in the external cloud server 1, the store controller 10, the transaction status management device 20, the settlement device 30, and the mobile terminal device 40, respectively.

[0029] The computer 200 includes a processor 201, a main memory 202, a storage 203, and an interface 204. The processor 201 reads out various programs stored in the storage 203, expands them in the main memory 202, and executes processing according to the programs. Also, the processor 201 secures a storage area in the main memory 202 according to the programs. Examples of the processor 201 include a CPU (Central Processing Unit), a GPU (Graphic Processing Unit), and a microprocessor.

[0030] Storage 203 includes, for example, a magnetic disk, a magneto-optical disk, an optical disk, and a semiconductor memory. Storage 203 may be an internal medium directly connected to the bus of computer 200, or may be an external medium connected to computer 200 via interface 204 or a communication line. Also, when this program is distributed to computer 200 via a communication line, the receiving computer 200 may expand the program in main memory 202 and execute the processing.

[0031] Interface 204 communicates with each device by communicating with each device via a network such as a LAN (Local Area Network). LANs include wired and wireless (e.g., Wi-Fi (registered trademark), Bluetooth (registered trademark), etc.).

[0032] For store controller 10, transaction status management device 20, settlement device 30, and mobile terminal device 40, input devices and output devices are connected to computer 200 via interface 204. Input devices include, for example, a scanner, a camera, a touch panel, operation buttons, a microphone, etc. Also, in the case of mobile terminal device 40, the input device includes a position detection unit. The position detection unit receives position information from GPS (Global Positioning System) satellites, beacons, etc., and detects the current location of mobile terminal device 40 on map data. Various sensors include, for example, a gyro sensor, an acceleration sensor, a distance sensor, etc. Mobile terminal device 40 can detect, for example, the inclination of mobile terminal device 40 based on the detection results of various sensors. Output devices include, for example, a display, a printer, a speaker, etc.

[0033] (Installation examples of transaction status management device 20 and settlement device 30) FIG. 3 is a diagram showing an installation example of the transaction status management device 20 and the settlement device 30. In FIG. 3, the store 300 includes a product sales area 310 and a settlement area 320. The product sales area 310 is an area where various products such as foodstuffs and sundries are arranged. In the product sales area 310, a customer performs a product registration operation using the mobile terminal device 40.

[0034] The settlement area 320 is an area where settlement is performed. In the settlement area 320, the transaction status management device 20 and a plurality (for example, five) of settlement devices 30 (30-1 to 30-5) are arranged. The transaction status management device 20 is arranged on the upstream side (the product sales area 310 side) of the settlement device 30. A support clerk is arranged at the transaction status management device 20. When the products to be confirmed by the clerk are included in the products purchased by the customer, a confirmation operation is performed by the support clerk.

[0035] As shown in the figure, in the present embodiment, before settlement is started, a confirmation operation by the support clerk is performed for the products to be confirmed by the clerk. In such a mode, if it is assumed that the support clerk checks the presence or absence of the products to be confirmed by the clerk for all customers heading for settlement, it will take time and effort and the customers cannot be handled efficiently. Also, for example, when the support clerk supports a customer performing self-settlement, the confirmation regarding the presence or absence of the products to be confirmed by the clerk will be delayed and congestion will occur.

[0036] Therefore, in the present embodiment, in the mode in which a confirmation operation by the support clerk is performed for the products to be confirmed by the clerk before settlement is started, it is possible to efficiently handle the customers heading for settlement. Hereinafter, with reference to FIG. 4, the customer guidance according to the present embodiment will be described. First, the guidance when the settlement device 30 is idle and the operations of each device will be described.

[0037] (An example of customer guidance in the store 300) FIG. 4 is a diagram showing an example of a customer's path during the idle time of the settlement device 30. As shown in FIG. 4, after finishing the product registration operation, the customer moves from the product sales area 310 to the settlement area 320 via one of the plurality of paths 330a and 330b.

[0038] Path 330a is the route when the product to be registered (registered product data) includes a product for staff confirmation. Specifically, when the registered product includes a product for staff confirmation, the customer is prompted to the transaction status management device 20, and the staff confirmation operation for the product for staff confirmation is performed by the support staff. After the confirmation operation by the support staff is completed, the customer is prompted to the settlement device 30 (settlement device 30-5 in the figure), and self-settlement is performed.

[0039] On the other hand, path 330b is the route when the registered product does not include a product for staff confirmation. Specifically, when the registered product does not include a product for staff confirmation, the customer is prompted to an available settlement device 30 (settlement device 30-1 in the figure) without passing through the transaction status management device 20, and self-settlement is performed.

[0040] (An example of the functional configuration of the shopping system St) FIG. 5 is a block diagram showing the functional configuration of the shopping system St.

[0041] (Identification of products by the mobile terminal device 40) First, the identification of products by the mobile terminal device 40 will be described. The mobile terminal device 40 identifies products. The mobile terminal device 40 is equipped with an imaging unit. The imaging unit captures the product code (barcode) attached to the product. The mobile terminal device 40 performs image analysis on the product code captured by the imaging unit to obtain code information, and identifies the product indicated by the code information. When the mobile terminal device 40 identifies a product, it transmits information (for example, code information) indicating the identified product to the cloud server 1.

[0042] Note that the mobile terminal device 40 can also perform object recognition scanning. Object recognition scanning is a method of identifying a product by extracting feature amounts from a captured image and determining the similarity of the feature amounts. Also, in object recognition scanning, it is also possible to extract character information from a character image attached to a product by means of an OCR (Optical Character Reader) function and identify the product corresponding to the character information.

[0043] Also, the mobile terminal device 40 may be provided with a scanner. When provided with a scanner unit, the mobile terminal device 40 can identify a product based on the code information read by the scanner unit.

[0044] Furthermore, the mobile terminal device 40 may be configured to display a preset key (product selection button) corresponding to the product to be registered. In this case, the mobile terminal device 40 identifies the product by pressing the preset key.

[0045] (Cloud server 1) As shown in FIG. 5, in the shopping system St, the cloud server 1 includes a registration unit 501, a determination unit 502, and a guidance unit 503. Each functional unit is realized by a processor 201 (FIG. 2) included in the cloud server 1. That is, when the processor 201 included in the cloud server 1 executes the guidance program according to the present embodiment, each functional unit is realized.

[0046] (Registration unit 501) The registration unit 501 registers the product identified by the mobile terminal device 40. Specifically, the registration unit 501 registers the product based on the information indicating the product received from the mobile terminal device 40. More specifically, the registration unit 501 generates a transaction ID each time shopping starts, associates it with the app ID of the mobile terminal device 40, and registers the product. For example, even if there was a transaction that was once canceled on the same day, the product is not registered by overwriting that transaction. Instead, virtual shopping cart data is generated for each transaction.

[0047] (Determination Unit 502) The determination unit 502 determines whether the merchandise registered by the registration unit 501 includes merchandise that requires staff confirmation. Merchandise that requires staff confirmation is merchandise that requires the intervention of a staff member and may, for example, be referred to as "pending merchandise." Specifically, merchandise that requires staff confirmation includes age-verification merchandise, high-value merchandise, multiple registrations of the same merchandise, non-file merchandise, and error merchandise. Age-verification merchandise is merchandise for which the sale to minors, such as alcohol and tobacco, is prohibited. High-value merchandise is merchandise that is above a certain amount and requires confirmation by a staff member for safety reasons. Displaying the purchase points for each price range, for example, makes it easier to confirm the purchased merchandise. Multiple registrations of the same merchandise require confirmation by a staff member because there is a possibility of fraud in the registered quantity. Non-file merchandise is merchandise for which product data corresponding to the code information received from the mobile terminal device 40 cannot be obtained. That is, non-file merchandise indicates that the merchandise cannot be identified. Error merchandise includes, for example, merchandise for which an increase in the weight of the shopping basket is detected despite not being scanned (weight error merchandise), or merchandise for which the product code could not be read, such as when there were wrinkles in the packaging of the merchandise (scan error merchandise). Further, the determination unit 502 may determine, through image processing (such as AI processing), that merchandise has been inserted without being scanned even though it is in an imaged state. Further, the determination unit 502 may determine that a failure to read a barcode is error merchandise. Specifically, when the acquisition of code information ultimately fails, for example, when something resembling a barcode is recognized but the barcode information cannot be recognized, the determination unit 502 may determine it as barcode reading error merchandise or basket omission error merchandise.

[0048] In addition, other merchandise that requires staff confirmation includes pharmaceuticals, merchandise with anti-theft tags, and returned merchandise. Pharmaceuticals are merchandise that requires explanation by a pharmacist. Merchandise with anti-theft tags is merchandise that requires removal work by a staff member. Returned merchandise is merchandise that requires a return procedure by a staff member.

[0049] (Internal guidance unit 503) The internal guidance unit 503 guides customers towards settlement. Specifically, the internal guidance unit 503 provides guidance to the mobile terminal device 40 based on the determination result of the determination unit 502. The mobile terminal device 40 displays a guidance screen corresponding to the guidance of the internal guidance unit 503. The guidance by the internal guidance unit 503 includes a first guidance and a second guidance. The first guidance is a guidance that encourages movement to the transaction status management device 20. The second guidance is a guidance that encourages movement to the settlement device 30. Specifically, the second guidance includes a settlement device number.

[0050] When the internal guidance unit 503 is determined by the determination unit 502 to include products for staff confirmation, the internal guidance unit 503 provides the first guidance to the mobile terminal device 40. On the other hand, when the internal guidance unit 503 is determined by the determination unit 502 not to include products for staff confirmation, the internal guidance unit 503 provides the second guidance to the mobile terminal device 40.

[0051] The trigger for the guidance by the internal guidance unit 503 is for the mobile terminal device 40 to receive an operation for completing product registration (for example, pressing a registration completion button). When the mobile terminal device 40 receives an operation for completing product registration, it makes a guidance request (hereinafter referred to as a "guidance request") to the cloud server 1. When there is a guidance request, the cloud server 1 identifies the mobile terminal device 40 that is the source of the guidance request. Then, the cloud server 1 (determination unit 502) determines whether the products registered in the identified mobile terminal device 40 include products for staff confirmation. The internal guidance unit 503 provides the first guidance or the second guidance based on the determination result.

[0052] In addition, the cloud server 1 manages the real-time usage status of the settlement device 30. The usage status indicates either in use or not in use (idle). The internal guidance unit 503 provides guidance to an idle settlement device 30 as the second guidance. Specifically, the internal guidance unit 503 identifies the number of an idle settlement device 30 based on the real-time usage status or status progress (change) of the settlement device 30. Then, the internal guidance unit 503 guides the mobile terminal device 40 to the number of the idle settlement device 30.

[0053] Note that even though the store staff - confirmed items are registered, it is assumed that at the time of settlement, the customer may move directly to the settlement device 30 without moving to the transaction status management device 20. If the customer moves directly to the settlement device 30, the settlement may be prohibited. For example, the mobile terminal device 40 may be configured not to display the settlement code that can be used for settlement on the settlement device 30. Thereby, the settlement device 30 can be prevented from performing the settlement. Also, when the store staff - confirmed items are registered, the mobile terminal device 40 may be controlled to display the settlement code that can be used for settlement on the settlement device 30 after the confirmation by the store staff.

[0054] Also, during the congestion described later, regardless of the presence or absence of the store staff - confirmed items, the first guidance will be provided by the guide unit 503. However, since the store staff - confirmed items are not registered, it is assumed that the customer may move directly to the settlement device 30. During congestion, in order to provide the first guidance to all customers, even if the store staff - confirmed items are not registered, the settlement code that can be used for settlement on the settlement device 30 will not be displayed. Therefore, even if the customer moves directly to the settlement device 30, the settlement cannot be performed.

[0055] (Transaction Status Management Device 20) The transaction status management device 20 includes an acquisition unit 511 and a reception unit 512. Each functional unit is realized by a processor 201 (FIG. 2) included in the transaction status management device 20. That is, when the processor 201 included in the transaction status management device 20 executes the guidance program according to this embodiment, each functional unit is realized.

[0056] (Acquisition Unit 511) The transaction status management device 20 acquires registered product data including products to be verified by the clerk. The case where the first guidance is provided by the guidance unit 503 is the case where the registered product data includes products to be verified by the clerk. Therefore, when the first guidance is provided by the guidance unit 503, the acquisition unit 511 acquires information related to the products to be verified by the clerk. The information related to the products to be verified by the clerk is, for example, the registered product data indicating the products registered by the registration unit 501. Thereby, the acquisition unit 511 acquires the registered product data of the products to be verified by the clerk.

[0057] The mode of acquiring the registered product data by the acquisition unit 511 is a mode of acquisition based on the reading of the settlement code displayed on the mobile terminal device 40. Specifically, when the acquisition unit 511 reads the settlement code displayed on the mobile terminal device 40, it makes a transmission request for the registered product data regarding the mobile terminal device 40 to the cloud server 1. Then, the acquisition unit 511 receives the registered product data from the cloud server 1 in response to the transmission request. When the registered product data is acquired by the acquisition unit 511, the transaction status management device 20 performs a clerk verification process that prompts the verification of the products to be verified by the clerk. In the clerk verification process, a verification screen dedicated to the clerk is displayed.

[0058] (Reception unit 512) The reception unit 512 receives a predetermined verification by the clerk based on the registered product data acquired by the acquisition unit 511. The predetermined verification is, for example, to receive the fact that it has been verified on the verification screen dedicated to the clerk. When the reception unit 512 receives the verification, the transaction status management device 20 transmits a clerk verification completed notification indicating that fact to the cloud server 1.

[0059] (Guidance to the settlement device 30 after clerk verification) The guidance unit 503 issues the second guidance after the predetermined confirmation is received by the reception unit 512. Specifically, when the guidance unit 503 receives a store clerk confirmation notification, it issues the second guidance. The second guidance is issued not only to the mobile terminal device 40 but also to the transaction status management device 20. The mobile terminal device 40 and the transaction status management device 20 each display a guidance screen based on the second guidance. Note that such second guidance (second guidance when routed through the transaction status management device 20) only needs to be issued to at least one of the transaction status management device 20 and the mobile terminal device 40.

[0060] (Reservation of settlement device 30) Here, for customers who purchase clerk-verified products, the cloud server 1 reserves (keeps) the payment terminal 30 when performing clerk verification. This is to prevent the payment terminal 30 from being used by another customer who arrives later, for example, if the payment terminal 30 becomes congested while clerk verification is being performed.

[0061] The timing for reserving the settlement device 30 may be any timing after the timing at which it is determined that the registered product data includes a product that is to be checked by a store clerk. For example, the timing for the reservation is the timing for the first announcement. When the confirmation by the store clerk is completed, that is, when the announcement unit 503 receives a notice of confirmation by the store clerk from the transaction status management device 20, the announcement unit 503 announces the reserved settlement device 30 as the second announcement.

[0062] Note that, when making a reservation, a priority order may be set for the settlement devices 30. The priority order may be, for example, in order of proximity to the transaction status management device 20 (settlement device 30-5, settlement device 30-4, ...). If the settlement device 30-5 is in use, a "pause screen" may be displayed on the settlement device 30-5 as soon as the settlement is completed. Note that the condition for canceling the pause screen may be receipt of an instruction (registered product data) from the transaction status management device 20, or, if a settlement code is displayed on the mobile terminal device 40, reading the settlement code.

[0063] (An example of registered product data stored in the registered product DB2) FIG. 6 is a diagram showing an example of the registered product DB2 stored in the cloud server 1. As shown in FIG. 6, the registered product DB2 includes items of transaction identification information, customer identification information, registration date and time, product information, store clerk confirmed product, and registration completion date and time. The transaction identification information is identification information for identifying the virtual cart. The customer identification information is information (customer ID) for identifying the customer (mobile terminal device 40). The registration date and time indicates the date and time (date and time) when the product was registered based on the operation of the mobile terminal device 40. The product information indicates the product information registered based on the operation of the mobile terminal device 40. Specifically, the product information includes the product name, product code, price, quantity, etc. The store clerk confirmed product is information indicating any one of age confirmation, pharmaceuticals, products with anti-theft tags, return products, etc. When the information is managed by flag for each input, it is a flag (number). Also, in the item of the store clerk confirmed product, when it is not a store clerk confirmed product, that is, when it is normally registered, it is distinguished and managed by inputting information indicating "normal", a flag indicating normal, or "Null", etc. The registration completion date and time indicates the date and time when the mobile terminal device 40 received the operation of completing the product registration. When information is input into each item, the registered product data is stored as a record.

[0064] (An example of usage information stored in the usage status DB3) FIG. 7 is a diagram showing an example of the registered product DB2 stored in the cloud server 1. As shown in FIG. 7, the usage status DB3 includes items of settlement device number and status. The settlement device number is an identification number for identifying the settlement device 30. The status indicates the usage situation. Specifically, the status indicates one of the following statuses: "In use", "Not in use (Standby)", "Guiding", "In use (Settling)", "On hold (Reserved)", "Change machine error", "Printer error", "Communication error", etc. Supplementary explanation for typical statuses: For example, "In use" indicates the state where the settlement device 30 is being used. "Not in use (Standby)" indicates the state where the settlement device 30 is available. "Guiding" indicates the state where the cloud server 1 has assigned a settlement device 30 for the customer to perform settlement processing. "On hold" indicates the state where a reservation (keep) has been made for the customer with the clerk-verified items registered. In the transaction status management device 20, when the number of the settlement device 30 is specified, the customer will move to the settlement device 30 with that number and perform settlement. When information is input into each item, the usage situation information is stored as a record.

[0065] Next, with reference to FIGS. 8A and 9, the process from the start to the end of a transaction in the shopping system St will be described. In FIGS. 8A and 9, the process from when a customer visits a store, registers the items to be purchased using the mobile terminal device 40, and completes the settlement at the settlement device 30 will be described. In the following, it is assumed that the information exchanged between the devices includes customer identification information and transaction identification information.

[0066] (Process of the transaction when the clerk-verified items are not registered) First, with reference to FIG. 8A, the process of the transaction when the clerk-verified items are not registered will be described. FIG. 8A is a sequence diagram showing the process of the transaction when the clerk-verified items are not registered.

[0067] Step S801: The mobile terminal device 40 activates the shopping app and accepts the start of a transaction when the shopping start button is pressed. Also, the mobile terminal device 40 acquires store identification information (store ID). The store identification information is represented by, for example, a store identification code such as a two-dimensional code. The store identification code is displayed, for example, on a display installed near the entrance of the store or on a paper medium pasted near the entrance of the store. The imaging unit of the mobile terminal device 40 reads the store identification code according to the customer's operation. Thereby, the mobile terminal device 40 acquires the store identification information. Note that the information for identifying the store may be any information that can uniquely identify the store, and is not limited to the store identification information. For example, it may be the location information of the mobile terminal device 40. The mobile terminal device 40 that has acquired the store identification information makes a request for starting a transaction to the cloud server 1. The request for starting a transaction includes the acquired store identification information and customer identification information (customer ID) for identifying the mobile terminal device 40 (customer).

[0068] Step S802: When the cloud server 1 receives the customer identification information and the store identification information as a request for starting a transaction from the mobile terminal device 40, it generates a virtual cart (registered product data of the customer) for the transaction.

[0069] Step S803: The mobile terminal device 40 scans the product code according to the customer's operation and displays the product. When the product code is scanned, the mobile terminal device 40 makes a registration request to the cloud server 1. The registration request includes the scanned code information and transaction identification information.

[0070] Step S804: When there is a registration request from the mobile terminal device 40, the cloud server 1 updates the registered product data in the registered product DB2. Also, the cloud server 1 transmits screen data indicating the updated registered product data to the mobile terminal device 40. Thereby, the mobile terminal device 40 updates the product registration screen.

[0071] Step S805: The mobile terminal device 40 repeats the process of Step S803 until the registration of the product is completed. The completion of the product registration is to receive an operation indicating the completion of the product registration (pressing the registration completion button). When the registration of the product is completed, the mobile terminal device 40 makes a guidance request related to settlement to the cloud server 1.

[0072] Step S806: When there is a guidance request from the mobile terminal device 40, the cloud server 1 identifies the registered product data of the mobile terminal device 40 that made the guidance request. Specifically, the cloud server 1 identifies the registered product data based on the customer identification information or transaction identification information included in the request. Then, it determines the presence or absence of the clerk confirmation product among the identified registered product data. In FIG. 8A, it is assumed that there is no clerk confirmation product. For this reason, the cloud server 1 identifies the unused settlement device 30 (settlement device number) based on the usage status information stored in the usage status DB 3. Then, the cloud server 1 gives a guidance (second guidance) to the mobile terminal device 40 to prompt it to move to the settlement device 30 indicated by the identified settlement device number.

[0073] Step S807: The mobile terminal device 40 displays a guidance screen to the settlement device 30 based on the second guidance by the cloud server 1. The customer moves to the settlement device 30 with a predetermined settlement device number by viewing the guidance screen based on the second guidance.

[0074] Step S808: Then, when the mobile terminal device 40 receives an operation indicating the start of settlement (pressing the settlement start button), it generates a settlement code and displays the generated settlement code on the display. Note that the mobile terminal device 40 may perform a display (for example, a display prompting the pressing of the settlement start button) to prompt the display of the settlement code together with the display of the guidance screen based on the second guidance.

[0075] Here, with reference to FIG. 8B, an example of a guidance screen based on the second guidance will be described. FIG. 8B is a diagram showing an example of a guidance screen based on the second guidance. As shown in FIG. 8B, a guidance screen 830 is displayed on the display of the mobile terminal device 40. The guidance screen 830 includes a settlement code 831 and a guidance 832. The settlement code 831 is represented by, for example, a two-dimensional code. The guidance 832 is, for example, a notification prompting settlement at the settlement device 30 of the specified (No. 4).

[0076] Step S809: The settlement device 30 reads the settlement code presented by the customer. Specifically, when the customer holds the settlement code in front of the scanner unit of the settlement device 30, the settlement device 30 reads the settlement code displayed on the mobile terminal device 40.

[0077] Step S810: The settlement code includes an instruction for causing the cloud server 1 to send registration product data to the settlement device 30. Therefore, when the settlement device 30 reads the settlement code, it sends a request to the cloud server 1 to send the registration product data related to the mobile terminal device 40.

[0078] Step S811: When there is a request to send registration product data, the cloud server 1 identifies the registration product data. Specifically, the cloud server 1 identifies the registration product data based on the transaction identification information included in the transmission request. Further, when the cloud server 1 identifies the registration product data, it sends the identified registration product data to the settlement device 30.

[0079] Step S812: When the settlement device 30 receives the registration product data from the cloud server 1, it displays a settlement screen based on the registration product data.

[0080] Step S813: When the cloud server 1 receives a request to send registration product data from the settlement device 30, it updates the status stored in the usage DB 3 for the settlement device 30 (settlement device number) that is the source of the transmission request to "guiding".

[0081] Step S814: The settlement device 30 executes a settlement process (self - settlement) according to the customer's operation. When starting the settlement, the settlement device 30 sends a notification indicating that to the cloud server 1. When receiving the notification, the cloud server 1 updates the status stored in the usage DB3 to "in use".

[0082] In the settlement process, the settlement device 30 accepts the selection of the settlement type, accepts the input of cash or reads various cards (credit cards or electronic money) according to the accepted settlement type, and finally issues a receipt. When the settlement process is completed, the settlement device 30 sends the settlement data to the cloud server 1. The settlement data includes the settlement type, the time of settlement, the deposit, the change, the remaining balance of the electronic money, etc.

[0083] Step S815: When the cloud server 1 receives the settlement data from the settlement device 30, it stores the purchase history including the settlement data and the registered product data corresponding to the settlement data.

[0084] Step S816: Further, the cloud server 1 updates the status stored in the usage DB3 to "not in use" for the settlement device 30 (settlement device number) which is the source of the settlement data.

[0085] Step S817: The cloud server 1 sends a transaction completion notification to the mobile terminal device 40.

[0086] Step S818: When the mobile terminal device 40 receives the transaction completion notification from the cloud server 1, it displays a transaction completion screen. Note that the mobile terminal device 40 can receive the purchase history from the cloud server 1 by making an inquiry to the cloud server 1 and display the received purchase history.

[0087] (Regarding the transaction flow when the clerk - confirmed product is registered) Figure 9 is a sequence diagram showing the transaction flow when the clerk - confirmed product is registered. Step S901: First, the mobile terminal device 40 activates the shopping app and accepts the start of a transaction when the shopping start button is pressed. Also, the mobile terminal device 40 acquires store identification information (store ID).

[0088] Step S902: When the cloud server 1 receives customer identification information and store identification information as a transaction start request from the mobile terminal device 40, it generates a virtual cart for the transaction.

[0089] Step S903: The mobile terminal device 40 scans the product code and displays the product according to the customer's operation. When the product code is scanned, the mobile terminal device 40 makes a registration request to the cloud server 1.

[0090] Step S904: When there is a registration request from the mobile terminal device 40, the cloud server 1 updates the registered product data in the registered product DB2. Also, the cloud server 1 sends screen data indicating the updated registered product data to the mobile terminal device 40. Thereby, the mobile terminal device 40 updates the product registration screen.

[0091] Step S905: The mobile terminal device 40 repeats the process of Step S903 until the registration of the product is completed. The completion of the product registration is to accept an operation indicating the completion of the product registration (pressing the registration completion button). When the registration of the product is completed, the mobile terminal device 40 makes a guidance request to the cloud server 1.

[0092] Step S906: When the cloud server 1 receives a guidance request from the mobile terminal device 40, it identifies the registered product data of the mobile terminal device 40 that made the guidance request. Specifically, the cloud server 1 identifies the registered product data based on the customer identification information or transaction identification information included in the request. Then, it determines whether there is a product for clerk confirmation among the identified registered product data. In FIG. 9, it is assumed that there is a product for clerk confirmation. Therefore, the cloud server 1 provides guidance (first guidance) to the mobile terminal device 40 to prompt it to move to the transaction status management device 20. Also, at this time, although not shown, the cloud server 1 reserves (keeps) the settlement device 30.

[0093] Step S907: Based on the first guidance from the cloud server 1, the mobile terminal device 40 displays a guidance screen for the transaction status management device 20. The customer moves to the transaction status management device 20 by viewing the guidance screen based on the first guidance.

[0094] Step S908: When the mobile terminal device 40 receives an operation indicating the start of clerk confirmation (for example, pressing the settlement start button), it generates a settlement code and displays the generated settlement code on the display.

[0095] Step S909: The transaction status management device 20 reads the settlement code presented by the customer. Specifically, when the customer holds the settlement code in front of the scanner unit of the transaction status management device 20, the transaction status management device 20 reads the settlement code displayed on the mobile terminal device 40.

[0096] Step S910: The settlement code includes an instruction for causing the transaction status management device 20 to send a request for registered product data from the cloud server 1. Therefore, when the transaction status management device 20 reads the settlement code, it sends a request for the registered product data related to the mobile terminal device 40 to the cloud server 1.

[0097] Step S911: When there is a request to send registered product data, the cloud server 1 identifies the registered product data. Specifically, the cloud server 1 identifies the registered product data based on the transaction identification information included in the send request. Further, when the cloud server 1 identifies the registered product data, it sends the identified registered product data to the transaction status management device 20. Note that if only age confirmation products are included as the products to be confirmed by the store clerk, the cloud server 1 may send an age confirmation instruction (an example of information related to a predetermined product) to the transaction status management device 20 instead of the registered product data.

[0098] Step S912: When the transaction status management device 20 receives the registered product data from the cloud server 1, it displays a registered product list based on the registered product data. Note that if only age confirmation products are included as the products to be confirmed by the store clerk, the transaction status management device 20 may display an age confirmation screen by receiving an age confirmation instruction from the cloud server 1 instead of the registered product data.

[0099] Step S913: The transaction status management device 20 performs a store clerk confirmation process. In the store clerk confirmation process, when the transaction status management device 20 accepts "confirmed", it sends a store clerk confirmed notification indicating that to the cloud server 1.

[0100] Step S914: When the cloud server 1 receives the confirmed notification from the transaction status management device 20, it gives a guidance (the second guidance) to prompt a move to the already reserved settlement device 30. The second guidance is given to the transaction status management device 20 and the mobile terminal device 40.

[0101] Step S915: Based on the second guidance by the cloud server 1, the mobile terminal device 40 displays a guidance screen to the reserved settlement device 30.

[0102] Step S916: Based on the second guidance by the cloud server 1, the transaction status management device 20 displays a guidance screen to the reserved settlement device 30.

[0103] Step S917: The transaction status management device 20 transfers the registered product data received from the cloud server 1 in step S912 to the payment device 30 at the destination indicated by the second guidance. Note that the registered product data is not necessarily transferred only from the transaction status management device 20 to the payment device 30. For example, the transaction status management device 20 may give an instruction to the cloud server 1 to transmit the registered product data to the payment device 30 at the destination indicated by the second guidance. The cloud server 1 may transmit the registered product data to the payment device 30 based on the instruction. Even in this case, the payment device 30 can acquire the registered product data.

[0104] Step S918: When the payment device 30 receives the registered product data from the transaction status management device 20, it displays a payment screen based on the registered product data. Note that the payment device 30 may display the registered product data when the customer comes in front of the device. Specifically, the payment device 30 may be equipped with a sensor that detects a person in front of the device, and display the registered product data at the timing when a person is detected by the sensor. Step S919: The payment device 30 transmits a usage notification indicating that the device is in use to the cloud server 1.

[0105] Step S920: When the cloud server 1 receives the usage notification from the payment device 30, it updates the status stored in the usage status DB3 to "in use" for the payment device 30 (payment device number) that sent the usage notification.

[0106] Step S921: The payment device 30 executes a payment process (self - payment) based on the customer's operation. When the payment device 30 completes the payment process, it transmits the payment data to the cloud server 1.

[0107] Step S922: When the cloud server 1 receives the payment data from the payment device 30, it stores a purchase history including the payment data and the registered product data corresponding to the payment data.

[0108] Step S923: Further, the cloud server 1 updates the status stored in the usage DB3 to "not in use" for the settlement device 30 (settlement device number) that is the transmission source of the settlement data.

[0109] Step S924: The cloud server 1 transmits a transaction completion notice to the mobile terminal device 40.

[0110] Step S925: When the mobile terminal device 40 receives the transaction completion notice from the cloud server 1, it displays a transaction completion screen.

[0111] (Regarding congestion) Next, the operation of the conducting wire and each device when considering congestion will be described. FIG. 10 is a diagram showing an example of the customer's conducting wire when the settlement device 30 is congested. As shown in FIG. 10, after the customer finishes the product registration operation, the customer moves from the product sales area 310 to the settlement area 320 via the conducting wire 330c.

[0112] As shown in the conducting wire 330c, when the settlement device 30 is congested, regardless of whether the registered product (registered product data) includes a product to be confirmed by the store clerk, the customer is urged to go to the transaction status management device 20. Then, regardless of whether the registered product includes a product to be confirmed by the store clerk, the transaction status management device 20 reads the settlement code from all the mobile terminal devices 40. As a result, the customer can be guided to the settlement device 30 in the order in which the transaction status management device 20 reads the settlement code. In other words, when guiding the customer to the settlement device 30 during congestion, it is possible to prevent other customers from cutting in.

[0113] Here, the configuration of each functional part (FIG. 5) during congestion will be supplemented. The guiding part 503 performs the first guiding regardless of the determination result of the determination part 502 according to the usage status of the settlement device 30. Specifically, when the settlement device 30 is congested, specifically, when the usage rate of the settlement device 30 is equal to or higher than a predetermined value (for example, 80% or higher), the guiding part 503 performs the first guiding. The predetermined value can be set and changed for each store.

[0114] After the first guidance, the guidance unit 503 provides second guidance to prompt the movement to the settlement device 30 that has become unused (idle). The guidance unit 503 provides the second guidance in the order in which information (for example, registered product data) related to a predetermined product is acquired by the acquisition unit 511 (transaction status management device 20). The second guidance is provided to the transaction status management device 20 and the mobile terminal device 40. The transaction status management device 20 transfers the registered product data to the settlement device 30 that is the guidance destination in the second guidance.

[0115] (Regarding the processing of Cloud Server 1 considering congestion) Next, with reference to FIGS. 11 to 13, the processing of Cloud Server 1 considering congestion will be described. FIG. 11 is a flowchart showing an example of the processing of Cloud Server 1 considering congestion.

[0116] In FIG. 11, Cloud Server 1 determines whether there is a guidance request (a request for guidance of the settlement device 30) from the mobile terminal device 40 (step S1101). The guidance request is made by the mobile terminal device 40 receiving an operation indicating completion of product registration (pressing the registration completion button).

[0117] Cloud Server 1 waits until there is a guidance request from the mobile terminal device 40 (step S1101: NO). When there is a guidance request from the mobile terminal device 40 (step S1101: YES), Cloud Server 1 identifies the registered product data of the mobile terminal device 40 that made the guidance request (step S1102).

[0118] Then, Cloud Server 1 determines whether the clerk confirmation product is included in the identified registered product data (step S1103). If the clerk confirmation product is included in the identified registered product data (step S1103: YES), Cloud Server 1 performs the processing at the time of clerk confirmation (FIG. 13) (step S1104) and proceeds to step S1116.

[0119] On the other hand, if the registered product data identified in step S1102 does not include the products to be confirmed by the store clerk (step S1103: NO), the cloud server 1 determines whether the payment device 30 is congested (whether the usage rate is equal to or higher than a predetermined value) based on the usage information stored in the usage status DB3 (step S1105).

[0120] If the payment device 30 is not congested (step S1105: NO), in other words, if the usage rate of the payment device 30 is less than the predetermined value, the cloud server 1 identifies the unused payment device 30 (payment device number) (step S1106). Then, the cloud server 1 provides a guidance (second guidance) to the mobile terminal device 40 to prompt it to move to the payment device 30 indicated by the identified payment device number (step S1107). As a result, the customer moves to the payment device 30 with the payment device number indicated by the second guidance. Note that the mobile terminal device 40 may display a guidance screen based on the second guidance and also display a prompt for displaying the payment code (for example, a prompt for pressing a payment start button).

[0121] Then, the cloud server 1 determines whether there is a request to transmit the registered product data from the payment device 30 when the payment device 30 reads the payment code (step S1108). The cloud server 1 waits until there is a request to transmit the registered product data from the payment device 30 (step S1108: NO).

[0122] On the other hand, when there is a request to transmit the registered product data from the payment device 30 (step S1108: YES), the cloud server 1 identifies the registered product data based on the transaction identification information included in the transmission request and transmits the identified registered product data to the payment device 30 (step S1109). After that, the cloud server 1 proceeds to step S1116.

[0123] In step S1105, when the settlement device 30 is congested (step S1105: YES), in other words, when the usage rate of the settlement device 30 is equal to or higher than a predetermined value, the cloud server 1 provides guidance (first guidance) to the mobile terminal device 40 to prompt it to move to the transaction status management device 20 (step S1110). As a result, the customer moves to the transaction status management device 20.

[0124] Then, when the transaction status management device 20 reads the settlement code, the cloud server 1 determines whether there is a request to send registered product data from the transaction status management device 20 (step S1111). The cloud server 1 waits until there is a request to send registered product data from the transaction status management device 20 (step S1111: NO).

[0125] On the other hand, when there is a request to send registered product data from the transaction status management device 20 (step S1111: YES), the cloud server 1 identifies the registered product data based on the transaction identification information included in the transmission request, and transmits the identified registered product data to the transaction status management device 20 (step S1112).

[0126] Then, the guidance order of the mobile terminal device 40 corresponding to the transmission order of the registered product data (or the order in which the request to send the registered product data was made) is stored (step S1113). At this time, the cloud server 1 may issue a guidance number corresponding to the mobile terminal device 40 and transmit the guidance number to the mobile terminal device 40. The mobile terminal device 40 may display the guidance number received from the cloud server 1.

[0127] Then, based on the usage information stored in the usage DB 3, the cloud server 1 determines whether any one of the plurality of settlement devices 30 is unused (idle) (step S1114). The cloud server 1 waits until any one of the settlement devices 30 becomes unused (step S1114: NO). When any one of the settlement devices 30 becomes unused (step S1114: YES), according to the guidance order stored in step S1113, a guidance (second guidance) to prompt the movement of the mobile terminal device 40 to be guided to the settlement device 30 is given (step S1115).

[0128] Note that in step S1115, the cloud server 1 gives the second guidance not only to the mobile terminal device 40 but also to the transaction status management device 20. Based on the second guidance, the transaction status management device 20 transfers the registered product data transmitted from the cloud server 1 in step S1112 to the settlement device 30 indicated by the second guidance. Also, in the second guidance to the transaction status management device 20, the cloud server 1 may transmit a guidance number. In this case, the transaction status management device 20 may display a guidance screen including the guidance number and the settlement device number.

[0129] Next, the cloud server 1 executes the processing after the settlement transfer (FIG. 12) (step S1116) and ends a series of processing.

[0130] (Regarding the processing by the cloud server 1 at the time of clerk confirmation) FIG. 12 is a flowchart showing an example of the processing by the cloud server 1 at the time of clerk confirmation. In FIG. 12, the cloud server 1 gives a guidance (first guidance) to prompt the movement to the transaction status management device 20 (step S1201). As a result, the customer moves to the transaction status management device 20. Also, the cloud server 1 reserves (keeps) one settlement device 30 (step S1202).

[0131] If there is no current unused settlement device 30, then later, the most recently unused settlement device 30 may be reserved. Also, the timing for reserving (keeping) the settlement device 30 is not limited to the timing in step S1202, and may be the timing before or after step S1204.

[0132] Then, the cloud server 1 determines whether there is a request to transmit registered product data from the transaction status management device 20 by the transaction status management device 20 reading the settlement code (step S1203). The cloud server 1 waits until there is a request to transmit registered product data from the transaction status management device 20 (step S1203: NO).

[0133] On the other hand, when there is a request to transmit registered product data from the transaction status management device 20 (step S1203: YES), the cloud server 1 identifies the registered product data based on the transaction identification information included in the transmission request, and transmits the identified registered product data to the transaction status management device 20 (step S1204).

[0134] Then, in the clerk confirmation process of the transaction status management device 20, the cloud server 1 determines whether it has received a clerk confirmed notification from the transaction status management device 20 by the transaction status management device 20 accepting that it has been confirmed (step S1205). The cloud server 1 waits until it receives a clerk confirmed notification from the transaction status management device 20 (step S1205: NO).

[0135] When the cloud server 1 receives a clerk confirmed notification from the transaction status management device 20 (step S1205: YES), it issues a guidance (second guidance) to prompt a move to the already reserved settlement device 30 (step S1206), and proceeds to step S1116 (FIG. 11). Note that the second guidance is issued to the transaction status management device 20 and the mobile terminal device 40. Based on the second guidance, the transaction status management device 20 transfers the registered product data transmitted from the cloud server 1 in step S1204 to the settlement device 30 at the guidance destination indicated by the second guidance.

[0136] (Regarding the processing after the billing migration performed by the cloud server 1) FIG. 13 is a flowchart showing an example of the processing after the billing migration performed by the cloud server 1. In FIG. 13, the cloud server 1 updates the status stored in the usage DB 3 to "in use" for the billing device 30 at the destination indicated by the second guidance (step S1301). Then, the cloud server 1 determines whether it has received billing data from the billing device 30 when the billing process is completed in the billing device 30 (step S1302).

[0137] The cloud server 1 waits until it receives the billing data from the billing device 30 (step S1302: NO). When the cloud server 1 receives the billing data from the billing device 30 (step S1302: YES), it stores the purchase history including the billing data and the registered product data corresponding to the billing data (step S1303).

[0138] Then, the cloud server 1 updates the status stored in the usage DB 3 to "not in use" for the billing device 30 that is the transmission source of the billing data (step S1304). Next, the cloud server 1 transmits a transaction completion notification to the mobile terminal device 40 (step S1305) and ends a series of processes.

[0139] (Screen of the transaction status management device 20 during congestion) In addition, when all customers are to be settled via the transaction status management device 20 during congestion, the transaction status management device 20 may display a screen according to the presence or absence of the clerk-verified item. On this screen, the transaction status management device 20, for example, displays "Normal" indicating that no clerk-verified item is registered, and also displays a reservation button corresponding to the unused settlement device 30. Note that on this screen, the transaction status management device 20 displays the reservation button so that only the unused settlement device 30 can be selected, but may also display other information (for example, status). The other information is information that can grasp the progress status of operations such as being in the process of paying change or being in the process of selecting settlement for settlement devices 30 other than errors. Even when no clerk-verified item is registered, a registered item list may be displayed so that registered items can be confirmed, or the registered item list may be skipped.

[0140] Also, when a clerk-verified item is registered, the transaction status management device 20 displays "Abnormal" indicating that a clerk-verified item is registered, and also displays a product registration list. The product registration list lists up the clerk-verified item at the top and displays it. In this way, during congestion, the transaction status management device 20 can display screens with different display modes (presence or absence of a product registration list, display position of the clerk-verified item) according to the reading result of the settlement code (presence or absence of the clerk-verified item).

[0141] As described above, when the shopping system St according to the present embodiment includes a store employee confirmation item among the items registered using the mobile terminal device 40 held by a customer, a first guidance for prompting movement to the transaction status management device 20 is provided. On the other hand, when the store employee confirmation item is not included in the registered items, a second guidance for prompting movement to the settlement device 30 is provided. As a result, in a mode where the support store employee performs a confirmation operation on the store employee confirmation item before settlement is started, for a customer who conducts a transaction that does not include a store employee confirmation item, the customer can be guided to the settlement device 30 without passing through the transaction status management device 20. Therefore, customers can be efficiently sorted, and congestion can be prevented. Thus, according to the present embodiment, customers heading for settlement can be efficiently processed.

[0142] Further, in the shopping system St according to the present embodiment, when the first guidance (guidance to the transaction status management device 20) is provided, the transaction status management device 20 acquires registered item data from the cloud server 1 and accepts a predetermined confirmation by the store employee based on the registered item data. Thereby, when the store employee confirmation item is included in the items registered using the mobile terminal device 40 held by the customer, the transaction status management device 20 can cause the store employee to perform a confirmation. Therefore, for transactions related to store employee confirmation items, appropriate transactions can be supported.

[0143] Further, the shopping system St according to the present embodiment provides a second guidance (guidance to the settlement device 30) after a predetermined confirmation by the store employee is accepted in the transaction status management device 20. Thereby, after the store employee confirms the store employee confirmation item, the customer can be efficiently guided to the settlement device 30.

[0144] In addition, when the shopping system St according to the present embodiment includes items to be confirmed by a store clerk, the mobile terminal device 40 is caused to display a screen prompting movement to the transaction status management device 20, and when there are no items to be confirmed by a store clerk, a settlement code is displayed. As a result, for customers conducting transactions without items to be confirmed by a store clerk, they can be guided to the settlement device 30 without going through the transaction status management device 20. Therefore, customers can be efficiently allocated, and congestion can be prevented.

[0145] Moreover, the shopping system St according to the present embodiment provides a first guidance (guidance to the transaction status management device 20) regardless of the determination result of the presence or absence of items to be confirmed by a store clerk, according to the usage status of the settlement device 30. As a result, during congestion, customers (mobile terminal devices 40) can be guided from the transaction status management device 20 to the settlement device 30 via the transaction status management device 20 once. Therefore, for example, under the supervision of support clerks, customers can be appropriately guided to the settlement device 30 according to the waiting order.

[0146] In the shopping system St according to the present embodiment, the transaction status management device 20 acquires registered product data from the cloud server 1 for each mobile terminal device 40 guided to the transaction status management device 20 by the first guidance. Further, the cloud server 1 provides a second guidance according to the order in which the registered product data is acquired by the transaction status management device 20. As a result, during congestion, customers (mobile terminal devices 40) can be appropriately guided to the settlement device 30 in the order in which the settlement codes are read in the transaction status management device 20. In other words, when guiding customers to the settlement device 30, it is possible to prevent other customers from cutting in.

[0147] (Modification of the embodiment) Next, a modification of the embodiment will be described. In the following modifications, the description of the content described in the above-described embodiment will be omitted as appropriate. Also, it is possible to appropriately combine the following modifications and the above-described embodiment.

[0148] (Modification 1) First, Modification Example 1 will be described. In the above-described embodiment, an example in which, even when there is no item for the store clerk to confirm, during congestion, the transaction status management device 20 is used before settlement was described. In Modification Example 1, an example in which, even during congestion, when there is no item for the store clerk to confirm, the transaction status management device 20 is not used before settlement will be described.

[0149] (Regarding the processing performed by the cloud server 1 according to Modification Example 1) FIG. 14 is a flowchart showing an example of the processing performed by the cloud server 1 according to Modification Example 1. Note that the processing shown in FIG. 14 is different from the processing shown in FIG. 11 in that, instead of the processing of steps S1110 to S1115, the processing of steps S1401 to S1403 is executed. Hereinafter, the processing of steps S1401 to S1403 will be described.

[0150] In step S1105 of FIG. 14, when the settlement device 30 is congested (step S1105: YES), in other words, when the usage rate of the settlement device 30 is equal to or higher than a predetermined value, the cloud server 1 stores the guidance order of the mobile terminal device 40 corresponding to the guidance request order in step S1101 (step S1401).

[0151] Note that when the settlement device 30 is congested, the cloud server 1 may cause the mobile terminal device 40 to perform various notifications. The various notifications include a notification indicating to wait for a while, a notification indicating the waiting order, a notification indicating the usage rate of the settlement device 30, and the like. Also, depending on the waiting order, there are customers who want to shop again. Therefore, the mobile terminal device 40 may be configured to accept cancellation of the guidance request when the settlement device 30 is congested. In this case, the mobile terminal device 40 may be configured to transition to a screen before the registration completion button is pressed (for example, a registration screen) by accepting the cancellation.

[0152] From the perspective of preventing the mobile terminal device 40 in standby from interrupting the payment process, the cloud server 1 may control the mobile terminal device 40 to prohibit payment at the payment device 30. Regarding the control performed by the cloud server 1 to prohibit payment, examples are given in (1) to (4) below. (1) The cloud server 1 controls the mobile terminal device 40 so that the payment code cannot be displayed. (2) The cloud server 1 controls the payment device 30 so that it does not make a transmission request for transaction data. (3) When there is a transmission request for transaction data from the payment device 30, the cloud server 1 does not transmit the transaction data to the payment device 30. (4) Although the cloud server 1 transmits the transaction data to the payment device 30, it controls the payment device 30 so that payment cannot be made.

[0153] After the process of step S1401, the cloud server 1 determines whether the payment device 30 has become unused (whether there is an available slot) based on the usage status information stored in the usage status DB 3 (step S1402). The cloud server 1 waits until the payment device 30 becomes unused (step S1402: NO). When the payment device 30 becomes unused (step S1402: YES), according to the guidance order stored in step S1401, a guidance (second guidance) to prompt the movement of the mobile terminal device 40 to be guided to the payment device 30 is given to the mobile terminal device 40 to be guided (step S1403). As a result, the customer moves to the payment device 30 with the payment device number indicated by the second guidance. After this, the cloud server 1 proceeds to the process of step S1108.

[0154] Note that the mobile terminal device 40 may perform a display (for example, a display prompting the pressing of a payment start button) that prompts the display of the payment code together with the display of the guidance screen based on the second guidance. Also, when the cloud server 1 performs the control to prohibit payment exemplified in (1) to (4) above, after the process of step S1403, the control to prohibit payment is released.

[0155] In this way, in Modification Example 1, even during congestion, when the registered products do not include the products to be confirmed by the store clerk, settlement can be performed without going through the transaction status management device 20. As a result, during congestion, customers (portable terminal devices 40) can be guided to the settlement device 30 in the order in which the guidance requests are made. That is, when guiding a customer to the settlement device 30, it is possible to prevent other customers from cutting in.

[0156] (Modification Example 2) Next, Modification Example 2 will be described. In the above-described embodiment, an example (an example of performing the second guidance) in which after guiding a customer through the transaction status management device 20, the customer is automatically guided to the settlement device 30 has been described. In Modification Example 2, an example in which after guiding a customer through the transaction status management device 20, the customer is guided to the settlement device 30 based on the operation of a store clerk will be described.

[0157] Specifically, in the above-described embodiment, the following examples have been described. · An example of guiding to a reserved settlement device 30 after performing a store clerk confirmation process in the transaction status management device 20 (step S913 in FIG. 9) (step S916 in FIG. 9 and step S1206 in FIG. 12). · An example of waiting for a customer with the transaction status management device 20 during congestion (step S1110 in FIG. 11) and guiding to a settlement device 30 that has become unused (steps S1114 and S1115 in FIG. 11).

[0158] In Modification Example 2, after the transaction status management device 20 performs a store clerk confirmation process or after waiting for a customer with the transaction status management device 20 during congestion, the transaction status management device 20 displays a reception screen (hereinafter referred to as the "settlement device designation screen") for receiving the designation (settlement device number) of the settlement device 30 from the support store clerk. On the settlement device designation screen, the support store clerk visually checks, for example, the available settlement device 30 and designates the settlement device number of the available settlement device 30.

[0159] When the transaction status management device 20 receives the designation of the settlement device number, it transfers the registered product data that has already been received from the cloud server 1 (step S912 in FIG. 9) to the settlement device 30 with the designated settlement device number. Also, in this case, the store clerk orally notifies the customer of the received settlement device number. As a result, the customer can move to the settlement device 30 with the notified settlement device number.

[0160] Here, with reference to FIGS. 15 and 16, the screen displayed on the transaction status management device 20 according to Modification 2 will be described. FIG. 15 is a diagram showing an example of a confirmation screen in the store clerk confirmation process displayed on the transaction status management device 20 according to Modification 2. As shown in FIG. 15, a confirmation screen 1500 is displayed on the display of the transaction status management device 20. The confirmation screen 1500 includes a registered product list 1501, a confirmation button 1502, and a settlement device selection button 1503. In the registered product list 1501, the store clerk confirmation product (○○ beer) is displayed at the top. When the store clerk selects the store clerk confirmation product and presses the confirmation button 1502, the transaction status management device 20 accepts that it has been confirmed. Also, when it has been confirmed, the transaction status management device 20 enables the settlement device selection button 1503. Then, when the settlement device selection button 1503 is pressed, the transaction status management device 20 transitions to a settlement device designation screen (FIG. 16).

[0161] FIG. 16 is a diagram showing an example of a settlement device designation screen displayed on the transaction status management device 20 according to Modification 2. As shown in FIG. 16, a settlement device designation screen 1600 is displayed on the display of the transaction status management device 20. The settlement device designation screen 1600 includes settlement device selection buttons 1601 (1601-1 to 1601-5). The status (available, in use, reserved, etc.) is displayed on the settlement device selection button 1601. In the illustration, it shows that the first and fourth settlement devices 30 (settlement device selection buttons 1601-1 and 1601-4) are not in use, and the second, third, and fifth settlement devices 30 (settlement device selection buttons 1601-2, 1601-3, and 1601-5) are not available for use.

[0162] In addition, the transaction status management device 20 enables (makes it valid) the pressing of the settlement devices 30 that are not in use (settlement device selection buttons 1601-1 and 1601-4), and disables (makes it invalid) the pressing of the settlement devices 30 that are not in use (settlement device selection buttons 1601-2, 1601-3, and 1601-5). When a store clerk selects a settlement device selection button 1601 indicating that it is not in use, the transaction status management device 20 changes the selected button 1601 to, for example, display "In use" and makes it invalid. Further, in this case, the store clerk verbally notifies the customer of the selected settlement device number.

[0163] (For the dedicated settlement device 30) A dedicated settlement device 30 that can be used only in response to a designation from the transaction status management device 20 may be provided. That is, a dedicated settlement device 30 that cannot perform settlement except when designated by the transaction status management device 20 and can perform settlement only when designated by the transaction status management device 20 may be provided. In this case, on the settlement device designation screen, the support store clerk may designate the settlement device number of the dedicated settlement device 30.

[0164] (Display of the settlement device number on the mobile terminal device 40) In this case, it is also possible to display the settlement device number on the mobile terminal device 40. Specifically, the transaction status management device 20 may transmit the settlement device number received on the settlement device designation screen to the mobile terminal device 40 via the cloud server 1. Thereby, the mobile terminal device 40 can display the settlement device number received by the transaction status management device 20.

[0165] (When the designated settlement device 30 is in use) In addition, since the store clerk visually designates the payment device 30, there may be cases where the designated payment device 30 is in use (during the payment process for the previous customer). Specifically, it may happen that the store clerk intentionally designates the in-use payment device 30 when judging that the payment process is almost finished. In other words, it may happen that the payment device 30 receives the registered product data of the next customer transferred from the transaction status management device 20 during the payment process for the previous customer. In this case, the payment device 30 prevents interfering with the payment process of the previous customer. Specifically, the payment device 30 continues the payment process of the previous customer as it is. Then, when the payment process of the previous customer is completed, the payment device 30 may be made capable of executing the payment process of the next customer.

[0166] (Regarding presenting the unused payment device 30 on the payment device designation screen) In addition, the transaction status management device 20 can present the payment device numbers of the available payment devices 30 on the payment device designation screen. Specifically, when the transaction status management device 20 receives confirmation in the store clerk confirmation process (step S913 in FIG. 9), it may inquire of the cloud server 1 about the availability status of the payment device 30 and display a payment device designation screen reflecting the availability status received from the cloud server 1. Thereby, the store clerk can grasp the available payment device 30 without having to perform a visual check. Also, the transaction status management device 20 may accept only the designation of the payment device numbers of the unused payment devices 30 as possible.

[0167] According to Modification Example 2, after passing the customer through the transaction status management device 20, based on the operation of the store clerk, the customer can be appropriately guided to the payment device 30.

[0168] (Modification Example 3) Next, Modification Example 3 will be described. In the above-described embodiment, an example in which the shopping system St includes the transaction status management device 20 has been described. In Modification Example 3, instead of or in addition to such an example, an example in which the shopping system St includes a manned cash register will be described.

[0169] In Modification 3, the manned cash register is a registration and settlement device where a store clerk is stationed. Hereinafter, the manned cash register will be referred to as the "registration and settlement device". In the registration and settlement device, products are registered by the store clerk. In the registration and settlement device, settlement may be performed by the store clerk or by the customer. The registration and settlement device includes a store clerk side display unit and a customer side display unit. For example, the registration and settlement device is the registration and settlement device in the accounting dedicated mode described above.

[0170] The first guidance according to Modification 3 is guidance that encourages movement to the registration and settlement device. That is, in Modification 3, when the determination unit 502 determines that the store clerk confirmation product is included, the guidance unit 503 gives the first guidance to the mobile terminal device 40 to encourage movement to the registration and settlement device.

[0171] The registration and settlement device can read the settlement code of the mobile terminal device 40. When the registration and settlement device reads the settlement code, it sends a transmission request for the registered product data to the cloud server 1. When the registration and settlement device receives the registered product data from the cloud server 1, it displays a registered product list.

[0172] After performing the store clerk confirmation process, the registration and settlement device can perform the settlement process by itself. In the settlement process, the registration and settlement device displays a settlement screen on the customer side display unit or the store clerk side display unit. When the settlement process is completed, the registration and settlement device sends the settlement data to the cloud server 1.

[0173] Note that, similar to the transaction status management device 20 of the embodiment, after performing the store clerk confirmation process, the registration and settlement device may display a screen based on the second guidance. Specifically, the registration and settlement device may display a guidance screen to the actuarial device 30 on the customer side display unit based on the second guidance by the cloud server 1. Also, in this case, the registration and settlement device may transfer the registered product data received from the cloud server 1 to the actuarial device 30 at the guidance destination indicated by the second guidance.

[0174] According to Modification 3, in the registration and settlement device, it is possible to perform the store clerk confirmation process and also to perform the settlement.

[0175] (Modification Example 4) Next, Modification Example 4 will be described. In the above-described embodiment, as a mode of acquiring registered product data of the transaction status management device 20, a mode of reading an accounting code displayed on the mobile terminal device 40 has been described. In Modification Example 4, another example of the mode of acquiring registered product data by the transaction status management device 20 will be described.

[0176] In Modification Example 4, the transaction status management device 20 may display an acquisition code (for example, a two-dimensional code) indicating a request for acquiring registered product data to the device itself. The acquisition code may be displayed on the display of the transaction status management device 20, or may be pasted on the transaction status management device 20 on a paper medium or the like. When the mobile terminal device 40 reads the acquisition code, it makes a transmission request to the cloud server 1 to transmit the registered product data related to the device itself to the transaction status management device 20.

[0177] When the cloud server 1 receives the transmission request from the mobile terminal device 40, it transmits the registered product data related to the mobile terminal device 40 to the settlement device 30. Thereby, the transaction status management device 20 can acquire the registered product data and display the registered product list.

[0178] Also, as another mode of acquiring the accounting code, the transaction status management device 20 can also acquire the registered product data by a button operation on the mobile terminal device 40. For example, one transaction status management device 20 is arranged in the store. The cloud server 1 stores the address of the transaction status management device 20. When the mobile terminal device 40 receives a button operation for transmitting the registered product data to the transaction status management device 20, it makes a transmission request to the cloud server 1 to transmit the registered product data to the transaction status management device 20. Even in this way, the transaction status management device 20 can acquire the registered product data and display the registered product list.

[0179] (Modification Example 5) Next, Modification Example 5 will be described. In Modification Example 5, an example of preventing a reserved payment device 30 from being used by other customers will be described. In Modification Example 5, the reserved payment device 30 is controlled to make it impossible to read the payment code. Specifically, when the cloud server 1 reserves the payment device 30 (step S1202 in FIG. 12), the cloud server 1 gives an instruction to the payment device 30 to prohibit reading the payment code. As a result, the payment device 30 performs read prohibition control for the payment code.

[0180] Furthermore, the cloud server 1 causes the read prohibition control to be released. Specifically, when the cloud server 1 receives a store clerk confirmed notification from the transaction status management device 20 (step S1205: YES), the cloud server 1 gives an instruction to the payment device 30 to release the read prohibition control for the payment code.

[0181] In the read prohibition control, the payment device 30 displays a screen such as "Reading prohibited". In a normal standby state, the payment device 30 displays a screen such as "Please read the payment code". Also, in the read prohibition control, the payment device 30 may prohibit the reading function of the scanner unit (reading unit). However, since it can be expected that no reading operation will be performed by the customer when the screen of "Reading prohibited" is displayed, the payment device 30 may not prohibit the reading function of the scanner unit (reading unit).

[0182] According to Modification Example 5, it is possible to prevent a reserved payment device 30 from being used by other customers. That is, when guiding a customer from the transaction status management device 20 to the payment device 30, it is possible to prevent other customers from butting in.

[0183] (Modification Example 6) Next, Modification Example 6 will be described. In the above-described embodiment, an example in which the cloud server 1 automatically reserves the payment device 30 when there is a store clerk confirmed item has been described. In Modification Example 6, an example in which the payment device 30 is reserved based on the operation of a store clerk when there is a store clerk confirmed item will be described.

[0184] In Modification 6, when the transaction status management device 20 makes a request to transmit registered product data to the cloud server 1 (step S910 in FIG. 9), for example, it displays a confirmation screen for the store clerk to confirm whether to reserve the settlement device 30. When receiving an acceptance of the reservation of the settlement device 30 on the confirmation screen, the transaction status management device 20 requests the cloud server 1 to reserve the settlement device 30. The cloud server 1 reserves the settlement device 30 upon receiving the request. When receiving the reservation request, the cloud server 1 transmits the status of each settlement device 30 to the transaction status management device 20.

[0185] Here, with reference to FIG. 17, the screen displayed on the transaction status management device 20 according to Modification 6 will be described. FIG. 17 is a diagram showing an example of a settlement device reservation screen displayed on the transaction status management device 20 according to Modification 6. As shown in FIG. 17, a settlement device reservation screen 1700 is displayed on the display of the transaction status management device 20. The settlement device reservation screen 1700 includes settlement device selection buttons 1701 (1701-1 to 1701-5). The status (available, in use, reserved, etc.) is displayed on the settlement device selection buttons 1701. In the illustration, it shows that the first and fourth settlement devices 30 (settlement device selection buttons 1701-1 and 1701-4) are each not in use, and the second, third, and fifth settlement devices 30 (settlement device selection buttons 1701-2, 1701-3, and 1701-5) are each shown as not available.

[0186] In addition, the transaction status management device 20 enables (makes valid) the pressing of the settlement devices 30 that are not in use (settlement device selection buttons 1701-1 and 1701-4), and disables (makes invalid) the pressing of the settlement devices 30 that are not not in use (settlement device selection buttons 1701-2, 1701-3, and 1701-5). When the store clerk selects a settlement device selection button 1701 indicating not in use, the transaction status management device 20 changes the display of the selected button 1701 to, for example, "reserved" and makes it invalid. Further, in this case, the store clerk verbally notifies the customer of the selected settlement device number.

[0187] According to Modification Example 6, the cashier device 30 can be reserved according to instructions from a store clerk and in response to congestion conditions and the like. Thereby, regarding the reservation of the cashier device 30, convenience can be further improved.

[0188] Hereinafter, a summary of the embodiments will be described. [Title of the Invention] System, Information Processing Apparatus, and Program [Technical Field] The present invention relates to a system, an information processing apparatus, and a program. [Background Art] In recent years, in stores and the like, a so-called self-service sales form in which customers register and settle goods has become widespread. For example, a system is known in which a customer registers goods using a portable terminal device the customer possesses and the customer settles the goods at a cashier device (see, for example, Patent Document 1). [Prior Art Documents] [Patent Documents] [Patent Document 1] Japanese Unexamined Patent Application Publication No. 2016-219034 [Summary of the Invention] [Problems to be Solved by the Invention] However, in the prior art, there has been a problem that it may not be possible to efficiently handle customers heading for settlement. The present invention has been made in view of such circumstances, and an object thereof is to provide a technique capable of efficiently handling customers.

[0189] [Means for Solving the Problems] (1) To solve the above problems, a system according to one aspect of the present invention is a system in which a customer registers a product using a portable terminal device, the system including: a registration means for registering a product specified by the portable terminal device; a determination means for determining whether a predetermined product that requires the intervention of a store clerk is included in the product registered by the registration means; and a guidance means for guiding the portable terminal device based on the determination result of the determination means. The guidance means performs a first guidance to prompt movement to a transaction status management device operated by a store clerk when the determination means determines that the predetermined product is included, and performs a second guidance to prompt movement to a settlement device when the determination means determines that the predetermined product is not included. A system characterized by this. According to the above configuration, in a mode where a confirmation operation by a support clerk is performed on a store clerk confirmation product before settlement is started, a customer who conducts a transaction not including a store clerk confirmation product can be guided to the settlement device 30 without passing through the transaction status management device 20. Therefore, since customers can be efficiently sorted, the occurrence of congestion can be prevented. Therefore, according to the present embodiment, customers heading for settlement can be efficiently handled.

[0190] (2) In the configuration of (1) above, the transaction status management device may include an acquisition means for acquiring registration product data indicating the product registered by the registration means when the first guidance is performed by the guidance means, and a reception means for receiving a predetermined confirmation by the store clerk based on the registration product data. According to the above configuration, when a store clerk confirmation product is included in the product registered using the portable terminal device 40 held by the customer, the transaction status management device 20 can cause the store clerk to perform a confirmation. Therefore, it is possible to support an appropriate transaction regarding a transaction related to a store clerk confirmation product.

[0191] (3) In the configuration of (2) above, the guidance means may perform the second guidance after the reception means receives the predetermined confirmation. According to the above configuration, for the products to be confirmed by the store clerk, after the confirmation by the store clerk, the customer can be efficiently guided to the settlement device 30.

[0192] (4-1) In the configuration of the above (1) or (2), when the determination means determines that the predetermined product is included, the guiding means may display a screen prompting movement to the transaction status management device, and when the determination means determines that the predetermined product is not included, a settlement code used in the settlement device may be displayed. According to the above configuration, for a customer who conducts a transaction not including the products to be confirmed by the store clerk, the customer can be guided to the settlement device 30 without passing through the transaction status management device 20. Therefore, since the customers can be efficiently sorted, the occurrence of congestion can be prevented.

[0193] (4-2) In the configuration of the above (1) or (2), the guiding means may perform the first guiding regardless of the determination result according to the usage status of the settlement device. According to the above configuration, during congestion, the customer (portable terminal device 40) can be guided from the transaction status management device 20 to the settlement device 30 via the transaction status management device 20 once. Therefore, for example, under the supervision of the support store clerk, the customers can be appropriately guided to the settlement device 30 according to the waiting order.

[0194] (5) In the configuration of the above (4), the transaction status management device includes an acquisition means for acquiring registration product data indicating the products registered by the registration means for each portable terminal device guided to the transaction status management device by the first guiding, and the guiding means may perform the second guiding according to the order in which the registration product data is acquired by the acquisition means. According to the above configuration, during congestion, the customers (portable terminal devices 40) can be appropriately guided to the settlement device 30 in the order in which the settlement codes are read in the transaction status management device 20. In other words, when guiding the customers to the settlement device 30, it is possible to prevent other customers from cutting in line.

[0195] (6) To solve the above problems, an information processing apparatus according to an aspect of the present invention is an information processing apparatus for a customer to register a product using a portable terminal device, including a registration means for registering a product specified by the portable terminal device, a determination means for determining whether a predetermined product that requires the intervention of a store clerk is included in the product registered by the registration means, and a guidance means for guiding the portable terminal device based on the determination result of the determination means. The guidance means performs a first guidance to prompt movement to a transaction status management device operated by a store clerk when the determination means determines that the predetermined product is included, and performs a second guidance to prompt movement to a settlement device when the determination means determines that the predetermined product is not included. The information processing apparatus is characterized by this. According to the above configuration, in an aspect where confirmation work by a support clerk is performed on a store clerk confirmation product before settlement is started, for a customer who conducts a transaction without including a store clerk confirmation product, it is possible to guide the customer to the settlement device 30 without passing through the transaction status management device 20. Therefore, since customers can be efficiently sorted, the occurrence of congestion can be prevented. Thus, according to the present embodiment, customers heading for settlement can be efficiently handled.

[0196] (7) To solve the above problems, a program according to an aspect of the present invention is a program that causes a computer to function as a system in which a customer registers a product using a portable terminal device. The program causes the computer to function as a registration means for registering a product specified by the portable terminal device, a determination means for determining whether a predetermined product that requires the intervention of a store clerk is included in the product registered by the registration means, and a guidance means for guiding the portable terminal device based on the determination result of the determination means. The guidance means performs a first guidance to prompt movement to a transaction status management device operated by a store clerk when the determination means determines that the predetermined product is included, and performs a second guidance to prompt movement to a settlement device when the determination means determines that the predetermined product is not included. The program is characterized by this. According to the above configuration, in the mode where the support staff performs the confirmation work on the staff confirmation products before the settlement starts, for customers who conduct transactions not including the staff confirmation products, they can be guided to the settlement device 30 without passing through the transaction status management device 20. Therefore, customers can be efficiently sorted, so that the occurrence of congestion can be prevented. Thus, according to the present embodiment, customers heading for settlement can be efficiently handled.

[0197] (8) In order to solve the above-described problems, a program according to an aspect of the present invention is a program that causes a computer to function as an information processing device in which a customer registers products by using a portable terminal device, the computer comprising: a registration unit that registers products specified by the portable terminal device; a determination unit that determines whether or not predetermined products that require the intervention of a staff member are included in the products registered by the registration unit; and a guidance unit that guides the portable terminal device based on the determination result of the determination unit. The guidance unit performs a first guidance that prompts movement to a transaction status management device operated by a staff member when the determination unit determines that the predetermined products are included, and performs a second guidance that prompts movement to a settlement device when the determination unit determines that the predetermined products are not included. This is a program characterized by the above. According to the above configuration, in the mode where the support staff performs the confirmation work on the staff confirmation products before the settlement starts, for customers who conduct transactions not including the staff confirmation products, they can be guided to the settlement device 30 without passing through the transaction status management device 20. Therefore, customers can be efficiently sorted, so that the occurrence of congestion can be prevented. Thus, according to the present embodiment, customers heading for settlement can be efficiently handled.

[0198] Note that all or part of each function (input / output, storage, processing (including judgment)) in the shopping system St (cloud server 1, transaction status management device 20, settlement device 30, and portable terminal device 40) described above may be realized in another device different from the device described as the execution subject of the function.

[0199] Specifically, in the above description, the configuration in which the cloud server 1 and the transaction status management device 20 include each functional unit shown in FIG. 5 has been described. All or part of each functional unit may be provided in other computer devices. For example, all or part of each functional unit may be provided in the cloud server 1, may be provided in the store controller 10, or may be provided in computer devices other than these. Also, the computer devices in which each functional unit is provided are not limited to a plurality of units, and may be one unit. For example, one computer device may include all of each functional unit.

[0200] Specifically, for example, instead of the cloud server 1, the mobile terminal device 40 may perform a first guidance to prompt movement to the transaction status management device 20 when the registered product includes a store clerk confirmation product, and perform a second guidance to prompt movement to the settlement device 30 when the store clerk confirmation product is not included.

[0201] In relation to the above, the transaction status management device 20, the settlement device 30, and the mobile terminal device 40 may function as so-called clients specialized for the input / output interface part with respect to various displays and the like. That is, the transaction status management device 20, the settlement device 30, and the mobile terminal device 40 may receive various inputs (operations of an operator and detections of devices), transmit input information (operation information, detection information, etc.) to the cloud server 1, receive the processing results of the cloud server 1 (update screen information, device control information, etc.) based on the input information, and perform various outputs (display to a display unit, control of a device).

[0202] Note that, in order to implement the shopping system St (cloud server 1, transaction status management device 20, settlement device 30, and mobile terminal device 40) described above, a program may be recorded on a computer-readable storage medium, and the program may be read into a computer system and executed. Here, the "computer system" is assumed to include hardware such as an OS and peripheral devices. Also, the "computer-readable storage medium" refers to a portable medium such as a USB (Universal Serial Bus) flash memory, SSD (Solid State Drive), flexible disk, magneto-optical disk, ROM, CD-ROM, or a storage device such as a hard disk built into a computer system. Furthermore, the "computer-readable storage medium" also includes a volatile memory (RAM) inside a computer system that serves as a server or client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line, and holds the program for a certain period of time. Also, the above program may be transmitted from a computer system storing the program in a storage device or the like to another computer system via a transmission medium or by a transmission wave in the transmission medium. Here, the "transmission medium" for transmitting the program refers to a medium having a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line. Also, the above program may be for realizing a part of the functions described above. Furthermore, it may be a so-called difference file (difference program) that can realize the functions described above in combination with a program already recorded in the computer system.

Explanation of Signs

[0203] St... Shopping system, 1... Cloud server, 2... Registered product DB, 3... Usage status DB, 10... Store controller, 20... Transaction status management device, 30... Settlement device, 40... Mobile terminal device, 300... Store, 310... Product sales area, 320... Settlement area, 501... Registration section, 502... Judgment section, 503... Guidance section, 511... Acquisition section, 512... Reception section

Claims

1. A system in which a customer registers a product using a mobile terminal device, comprising: registration means for registering the product specified by the mobile terminal device; determination means for determining whether a predetermined product that requires the intervention of a store clerk is included in the product registered by the registration means; guidance means for guiding the mobile terminal device based on the determination result of the determination means; characterized in that it comprises: The guidance means: when the determination means determines that the predetermined product is included, performs a first guidance to prompt the store clerk to move to a transaction status management device; when the determination means determines that the predetermined product is not included, performs a second guidance to prompt the store clerk to move to a settlement device. A system characterized by the above.

2. The transaction status management device: acquisition means for acquiring registration product data indicating the product registered by the registration means when the first guidance is performed by the guidance means; reception means for receiving a predetermined confirmation by the store clerk based on the registration product data. The system according to claim 1, characterized in that it comprises the above.

3. The guidance means performs the second guidance after the reception means receives the predetermined confirmation. The system according to claim 2, characterized by the above.

4. When the determination means determines that the predetermined product is included, the guidance means displays a screen prompting the store clerk to move to the transaction status management device; when the determination means determines that the predetermined product is not included, the guidance means displays a settlement code to be used in the settlement device. The system according to claim 1 or 2, characterized by the above.

5. Depending on the usage status of the settlement device, the guidance means performs the first guidance regardless of the determination result; The transaction status management device comprises acquisition means for acquiring information related to the predetermined product for each mobile terminal device guided to the transaction status management device by the first guidance; The guidance means performs the second guidance according to the order in which the information related to the predetermined product is acquired by the acquisition means. The system according to claim 4, characterized by the above.

6. An information processing device in which a customer registers a product using a mobile terminal device, comprising: registration means for registering the product specified by the mobile terminal device; determination means for determining whether a predetermined product that requires the intervention of a store clerk is included in the product registered by the registration means; Based on the determination result of the determination means, guidance means for guiding the mobile terminal device, comprising, the guidance means, when it is determined by the determination means that the predetermined product is included, performs a first guidance to prompt movement to a transaction status management device operated by a store clerk, when it is determined by the determination means that the predetermined product is not included, performs a second guidance to prompt movement to a settlement device, an information processing apparatus characterized by the above.

7. A program that causes a computer to function as a system in which a customer registers products using a mobile terminal device, the computer, registration means for registering the product specified by the mobile terminal device, determination means for determining whether or not the registered product includes a predetermined product that requires the intervention of a store clerk, guidance means for guiding the mobile terminal device based on the determination result of the determination means, functioning as, the guidance means, when it is determined by the determination means that the predetermined product is included, performs a first guidance to prompt movement to a transaction status management device operated by a store clerk, when it is determined by the determination means that the predetermined product is not included, performs a second guidance to prompt movement to a settlement device, a program characterized by the above.

8. A program that causes a computer to function as an information processing apparatus in which a customer registers products using a mobile terminal device, the computer, registration means for registering the product specified by the mobile terminal device, determination means for determining whether or not the registered product includes a predetermined product that requires the intervention of a store clerk, guidance means for guiding the mobile terminal device based on the determination result of the determination means, functioning as, the guidance means, when it is determined by the determination means that the predetermined product is included, performs a first guidance to prompt movement to a transaction status management device operated by a store clerk, when it is determined by the determination means that the predetermined product is not included, performs a second guidance to prompt movement to a settlement device, a program characterized by the above.

Images