Customer service robots and programs

Abstract

We provide customer service robots and programs capable of assisting customers with their shopping in commercial facilities that house multiple stores. [Solution] A customer service robot that moves with a customer within a commercial facility containing multiple stores, comprising: a registration means that processes the registration of products to be purchased by the customer from among the products sold at the destination store; a reception means that accepts the selection of products to be paid for at the store from among the products registered by the registration means; and a payment means that performs payment for the products selected by the reception means, wherein the payment means performs payment for any unpaid products among the products registered by the registration means at any time in response to an operation from the customer.

Description

Technical Field

[0001] Embodiments of the present invention relate to a customer service robot and a program.

Background Art

[0002] Conventionally, robots for serving customers who visit a store (hereinafter referred to as customer service robots) have been proposed. For example, a self-propelled robot that guides a customer to the location of a product has been proposed for a customer who cannot identify the display location of the product in a store.

[0003] However, the above-described conventional customer service robot is only for shopping support in a store and cannot be applied to commercial facilities such as shopping malls having a plurality of stores. For customers and stores using commercial facilities, the realization of a more useful customer service robot is desired.

Summary of the Invention

Problems to be Solved by the Invention

[0004] The problem to be solved by the present invention is to provide a customer service robot and a program capable of supporting customer shopping in a commercial facility where a plurality of stores are located.

Means for Solving the Problems

[0005] The customer service robot according to the embodiment is a customer service robot that moves together with a customer inside a commercial facility where a plurality of stores are located, and includes a registration unit, a reception unit, and a settlement unit. The registration unit performs a registration process of a product that the customer purchases from among the products sold in the store at the destination store. The reception unit receives a selection of a product to be settled at the store from among the products registered by the registration unit. The settlement unit settles the product for which the reception unit has received the selection. Further, the settlement unit settles, at an arbitrary timing according to an operation from the customer, the unsettled products among the products registered by the registration unit.

Brief Description of the Drawings

[0006] [Figure 1] Figure 1 shows an example of the configuration of a customer service support system according to an embodiment. [Figure 2] Figure 2 is a perspective view showing an example of the external configuration of a customer service robot according to this embodiment. [Figure 3] Figure 3 is a perspective view showing an example of the external configuration of a customer service robot according to this embodiment. [Figure 4] Figure 4 shows an example of the hardware configuration of a customer service robot according to the embodiment. [Figure 5] Figure 5 shows an example of the hardware configuration of the store equipment according to the embodiment. [Figure 6] Figure 6 shows an example of the data structure of a product master according to the embodiment. [Figure 7] Figure 7 shows an example of the hardware configuration of a server device according to this embodiment. [Figure 8] Figure 8 shows an example of the data structure of a store management table according to the embodiment. [Figure 9] Figure 9 shows an example of the data structure of the robot management table according to the embodiment. [Figure 10] Figure 10 shows an example of the data structure of a user management table according to the embodiment. [Figure 11] Figure 11 shows an example of the data structure of a transaction management table according to the embodiment. [Figure 12] Figure 12 is a block diagram showing the functional configuration of the customer service robot, store equipment, and server equipment according to the embodiment. [Figure 13] Figure 13 shows an example of a screen displayed on the front display unit of a customer service robot according to an embodiment of this model. [Figure 14] Figure 14 shows an example of a screen displayed on the front display unit of a customer service robot according to an embodiment. [Figure 15] Figure 15 shows an example of a screen displayed on the front display unit of a customer service robot according to this embodiment. [Figure 16] Figure 16 shows an example of a screen displayed on the front display unit of a customer service robot according to an embodiment of this model. [Figure 17] Figure 17 shows an example of a screen displayed on the rear display unit of a customer service robot according to an embodiment. [Figure 18] Figure 18 shows an example of a screen displayed on the front display unit of a customer service robot according to an embodiment of this model. [Figure 19] Figure 19 shows an example of a screen displayed on the front display unit of a customer service robot according to an embodiment of this model. [Figure 20] Figure 20 shows an example of a screen displayed on the front display unit of a customer service robot according to an embodiment of this model. [Figure 21] Figure 21 shows an example of a screen displayed on the front display unit of a customer service robot according to an embodiment. [Figure 22] Figure 22 shows an example of a screen displayed on the front display unit of a customer service robot according to an embodiment of this model. [Figure 23] Figure 23 shows an example of a screen displayed on the front display unit of a customer service robot according to this embodiment. [Figure 24] Figure 24 shows an example of a screen displayed on the front display unit of a customer service robot according to this embodiment. [Figure 25] Figure 25 shows an example of a screen displayed on the front display unit of a customer service robot according to this embodiment. [Figure 26] Figure 26 shows an example of a screen displayed on the rear display unit of a customer service robot according to the embodiment. [Figure 27] Figure 27 shows an example of a screen displayed on the front display unit of a customer service robot according to this embodiment. [Figure 28] Figure 28 is a flowchart showing an example of the main processing performed by the customer service robot of the embodiment. [Figure 29] Figure 29 is a flowchart showing an example of the check-in process performed by the customer service robot of the embodiment. [Figure 30]FIG. 30 is a flowchart showing an example of the personalization process performed by the customer service robot according to the embodiment. [Figure 31] FIG. 31 is a flowchart showing an example of the action plan generation process performed by the customer service robot according to the embodiment. [Figure 32] FIG. 32 is a flowchart showing an example of the store cooperation process performed by the customer service robot and the store device according to the embodiment. [Figure 33] FIG. 33 is a flowchart showing an example of the purchase support process performed by the customer service robot according to the embodiment. [Figure 34] FIG. 34 is a flowchart showing an example of the purchase support process performed by the customer service robot of Modification 1. [Figure 35] FIG. 35 is a diagram showing an example of the screen displayed on the front display unit of the customer service robot according to Modification 1. [Figure 36] FIG. 36 is a diagram showing an example of the screen displayed on the front display unit of the customer service robot according to Modification 1. [Figure 37] FIG. 37 is a diagram showing an example of the screen displayed on the front display unit of the customer service robot according to Modification 1. [Figure 38] FIG. 38 is a flowchart showing an example of the payment support process performed by the customer service robot of Modification 1.

MODE FOR CARRYING OUT THE INVENTION

[0007] Hereinafter, embodiments will be described in detail with reference to the drawings. In the embodiments described below, a form applied to a commercial facility such as a shopping center or a station building in which a plurality of stores are located will be described. Note that the present invention is not limited by the embodiments described below.

[0008] Figure 1 is a diagram showing an example of the configuration of a customer service support system according to an embodiment. As shown in Figure 1, the customer service support system 1 includes a customer service robot 10, store equipment 20, server equipment 30, parking system 40, and customer terminal 50. The customer service robot 10, store equipment 20, server equipment 30, and parking system 40 are connected to a network N such as a LAN (Local Area Network).

[0009] The customer service robot 10 is an autonomous, self-driving robot. Multiple customer service robots 10 are installed in a commercial facility to assist customers using the facility. The number of customer service robots 10 is not limited to the example shown in Figure 1.

[0010] Now, with reference to Figures 2 and 3, the external configuration of the customer service robot 10 will be described. Figures 2 and 3 are perspective views showing an example of the external configuration of the customer service robot 10.

[0011] In Figures 2 and 3, the configuration of the customer service robot 10 is explained using three mutually orthogonal axes: the X, Y, and Z axes. The X axis runs through the customer service robot 10 from front to back, extending from the rear to the front. The Y axis runs through the customer service robot 10 from left to right, extending from the left side to the right side. The Z axis runs through the customer service robot 10 from top to bottom, extending from the bottom to the top. Hereafter, the positive X-axis side of the customer service robot 10 will also be referred to as the front side of the customer service robot 10. The negative X-axis side of the customer service robot 10 will also be referred to as the rear side of the customer service robot 10.

[0012] The customer service robot 10 comprises a main body 11, a mobile unit 12, and an interface unit 13. To provide customers with a sense of psychological security, it is preferable that the customer service robot 10 has an appearance that mimics a character such as an animal. The customer service robot 10 in this embodiment has an appearance that mimics a kangaroo, with the main body 11 and mobile unit 12 corresponding to the kangaroo's body and the interface unit 13 corresponding to the kangaroo's head.

[0013] The main body 11 comprises a roughly cylindrical housing 111, a mounting base 112, and a cover portion 113 that covers the area around the mounting base 112 from the lower rear side to the front side of the housing 111. An opening 114 is provided on the front side of the housing 111, allowing access to the inside of the housing 111 through the opening 114. The mounting base 112 is provided so as to protrude from the inside of the housing 111 to the front side through the opening 114. Items such as goods can be placed on the mounting base 112. Alternatively, a reader / writer portion 157, which will be described later, may be provided on the mounting base 112. Here, the mounting base 112 is designed to correspond to a kangaroo's pouch in the appearance of the customer service robot 10.

[0014] In this embodiment, a portion of the mounting platform 112 is shown protruding from the housing 111. However, the configuration is not limited to this, and the mounting platform 112 may be provided inside the housing 111, allowing items to be stored within the housing 111. Furthermore, while the configuration shows a portion of the upper part of the mounting platform 112 covered by the housing 111, the configuration is not limited to this, and the upper part of the mounting platform 112 may not be covered.

[0015] Furthermore, the opening 114 may be provided with an openable and closable shielding member such as a lid or door to shield the items placed on the mounting platform 112. The shielding member may be made of a light-transmitting material so that the internal state can be seen from the outside. In addition, the closed state of the shielding member may be locked by providing an electronic lock or the like. This prevents items from falling from the mounting platform 112, for example, when the customer service robot 10 is moving. It also prevents items from being inadvertently removed from the mounting platform 112.

[0016] On the other hand, a rear display unit 115 is provided on the back side of the housing 111. The rear display unit 115 is, for example, a touch panel display, and displays various information under the control of the control unit 154, which will be described later. In addition, a tail section 116 corresponding to a kangaroo's tail is provided on the lower rear side of the housing 111.

[0017] The movable part 12 is located below the main body 11 and supports the main body 11 from below. The movable part 12 is equipped with a drive unit 121 (see Figure 4) which has a motor and a rotation mechanism. In addition, multiple drive wheels, auxiliary wheels, etc., which are rotationally driven by the drive unit 121 are provided on the bottom side of the movable part 12 (none of which are shown).

[0018] The drive unit 121, under the control of the control unit 154 (described later), rotates the drive wheels, enabling the robot to travel within the facility. Specifically, the drive unit 121 changes the rotational speed and direction of the drive wheels and the drive source to make the customer service robot 10 travel in any direction and at any speed. In this embodiment, the customer service robot 10 is made to travel with its front facing the direction of travel, but it is not limited to this, and the customer service robot 10 may also be made to travel with its rear facing the direction of travel.

[0019] The interface unit 13 is located on the upper part of the main body unit 11. The interface unit 13 has a housing 131 and a front display unit 132. The front side of the housing 131 has an operating surface that slopes downward from top to bottom, and the front display unit 132 is provided on this operating surface. The front display unit 132 is, for example, a touch panel display and displays various information under the control of the control unit 154, which will be described later. The housing 131 is also provided with ear parts 133 corresponding to kangaroo ears.

[0020] Furthermore, a slit 134 is formed below the operating surface of the housing 111, into which a product card, described later, can be inserted. Inside the slit 134, a reader / writer unit 157 (see Figure 4) capable of reading and writing to wireless tags such as RFID tags is provided. Under the control of the control unit 154, described later, the reader / writer unit 157 reads information that can identify a product from the wireless tag of the product card inserted into the slit 134, and writes information indicating that the product has been purchased to the wireless tag. Note that the position and number of reader / writer units 157 are not limited to those shown. For example, the reader / writer unit 157 may be provided on the mounting base 112.

[0021] Furthermore, the customer service robot 10 is equipped with a light-emitting unit 141 between the main body 11 and the interface unit 13. The light-emitting unit 141 has a light-emitting element such as an LED (Light Emitting Diode) and emits light according to the control of the control unit 154, which will be described later. The light-emitting unit 141 also has multiple colored light-emitting elements and switches the emitted color according to the control of the control unit 154, which will be described later. The light-emitting unit 141 informs various states, such as the status of the customer service robot 10 and the status of product purchases, by emitting light. In this embodiment, an example is shown in which the light-emitting unit 141 is provided in a collar-like shape at a position corresponding to the neck of a kangaroo, but the position and shape of the light-emitting unit 141 are not limited to this.

[0022] Furthermore, the customer service robot 10 is equipped with a stop button 142 on its back. The stop button 142 is an operator used to stop the customer service robot 10 from moving. When the stop button 142 is operated, the customer service robot 10 stops moving. In this embodiment, an example is shown in which the stop button 142 is located at a position corresponding to the kangaroo's neck, but the position in which the stop button 142 is provided is not limited to this.

[0023] Furthermore, the customer service robot 10 is equipped with an imaging unit 143. The imaging unit 143 has an image sensor such as a CCD (Charge Coupled Device) or CMOS (Complementary MOS) and is provided on both the front and back sides of the customer service robot 10. For example, as shown in Figures 2 and 3, the imaging unit 143 is provided in the part corresponding to the neck between the main body 11 and the interface unit 13, and around the rear display unit 115.

[0024] The imaging unit 143 captures images of the area around the customer service robot 10, for example, to capture customers present in the vicinity of the customer service robot 10. The imaging unit 143 located on the front side is used to capture barcodes, QR codes, and other code symbols presented by customers on products, as well as code symbols displayed on the customer terminal 50. In other words, the imaging unit 143 acquires barcodes, QR codes, and other code symbols attached to products. The number and placement of the imaging units 143 on the customer service robot 10 are not limited to the illustrated example. For example, the imaging units 143 may be located around the front display unit 132 or on the side of the customer service robot 10.

[0025] Furthermore, the customer service robot 10 is equipped with a sound-collecting unit 144 such as a microphone and an audio output unit 145 such as a speaker. The sound-collecting unit 144 and the audio output unit 145 are provided, for example, on either the front side and the back side of the customer service robot 10, or both. As an example, the sound-collecting unit 144 and the audio output unit 145 are provided on the interface unit 13 as shown in Figure 2. Note that the number and installation location of the sound-collecting unit 144 and the audio output unit 145 provided on the customer service robot 10 are not limited to the illustrated example.

[0026] Furthermore, the customer service robot 10 is equipped with various sensor units 158 (see Figure 4). For example, the customer service robot 10 is equipped with a distance measuring sensor. The distance measuring sensor is provided, for example, on the front and rear sides of the customer service robot 10, and detects objects around the customer service robot 10 and detects the distance to objects. The sensing results of the distance measuring sensor are output to the control unit 154, which will be described later, and are used for collision avoidance during movement, etc. The distance measuring sensor can be implemented as, for example, a sensor device that detects objects and measures distances using captured images or ultrasound, or a sensor device such as LiDAR (Light Detection and ranging) that detects objects using laser light.

[0027] Furthermore, the customer service robot 10 may be equipped with a vibration detection sensor or the like as a sensor unit 158 ​​capable of detecting contact or impact to the main body 11. The customer service robot 10 may also be equipped with an object detection sensor or weight sensor as a sensor unit 158 ​​capable of detecting whether or not an item is placed on the mounting platform 112. Additionally, the customer service robot 10 may be equipped with a position sensor such as a GPS (Global Positioning System) as a sensor unit 158 ​​or a positioning unit 159 (see Figure 4). The position sensor, for example, detects the location of the customer service robot 10 within the commercial facility.

[0028] Furthermore, the customer service robot 10 is equipped with a battery (not shown) in its main body 11 and mobile unit 12 to supply power for driving its own customer service robot 10.

[0029] The configuration of the customer service robot 10 is not limited to the illustrated example. For example, the interface unit 13 may include a reader device for reading information from card media such as IC cards or credit cards. The customer service robot 10 may also include an automated cash payment machine or a printer.

[0030] Returning to Figure 1, the store equipment 20 consists of information processing devices such as POS terminals and store servers installed in each store within the commercial facility. The store equipment 20 performs various processes related to its own store under the control of a processor (not shown).

[0031] The server device 30 is the server device for the customer service support system 1. The server device 30 is implemented by an information processing device such as a PC (Personal Computer). The server device 30 stores and manages various types of data related to the data processing of the customer service support system 1. For example, the server device 30 manages the location and status of the customer service robot 10. For example, the server device 30 manages products registered and purchased via the customer service robot 10.

[0032] In this embodiment, the server device 30 is implemented by a single information processing device, but it may also be a cloud server implemented by multiple information processing devices connected to a network. Furthermore, if the server device 30 is a cloud server, it may be configured to include store servers for each store and the parking system 40.

[0033] The parking system 40 is installed in the parking lot of a commercial facility and manages the entry and exit status and parking location of vehicles. For example, the parking system 40 has gate devices installed at the entrance and exit of the parking lot, surveillance cameras installed to cover all parking locations, a parking management server, etc. (none of which are shown), and manages parking locations and entry and exit based on the vehicle registration number (information written on the license plate) attached to the vehicle. For example, the parking management server recognizes the vehicle registration number of a vehicle from the image of the vehicle captured by the surveillance camera and stores it in association with information indicating the parking location within the parking lot. The parking management server also stores the time indicating the entry and exit of a vehicle obtained via the gate device, associating it with the vehicle registration number of the corresponding vehicle, and collects fees according to the parking time via the gate device.

[0034] The customer terminal 50 is a portable terminal device such as a smartphone or tablet owned by the customer. In this embodiment, the customer terminal 50 is used, for example, when the customer performs a check-in operation to begin using the customer service robot 10. As an example, the check-in operation is performed by entering a user ID that can identify the customer. It should be noted that the customer service robot 10 can be used even if the user ID is not entered.

[0035] As an example, the customer terminal 50 is equipped with an application program (hereinafter also referred to as the "cooperation program") related to cooperation with the customer service robot 10. The processor of the customer terminal 50 works in cooperation with the cooperation program to perform various processes for cooperating with the customer service robot 10. For example, the processor of the customer terminal 50 displays a code symbol, including the user ID and user settings described later, on the display device provided by the customer terminal 50, in response to customer operations. Furthermore, the processor of the customer terminal 50 is capable of establishing short-range wireless communication with the customer service robot 10 in response to customer operations.

[0036] In the customer service support system 1 described above, customers visiting a commercial facility can enjoy behavioral support from the customer service robot 10. Specifically, customers can receive behavioral support from the customer service robot 10 in conjunction with them by operating the robot. The customer service robot 10 moves with the customer within the commercial facility and performs various processes such as recommending destination stores and providing support related to product purchases.

[0037] The customer service support system 1 is not limited to the configuration shown in Figure 1. For example, the customer terminal 50 may not be included in the customer service support system 1. Furthermore, the customer service support system 1 may include external systems that customers can use, such as e-commerce sites operated by stores located within the commercial facility, e-commerce sites operated by other stores located outside the commercial facility, and various search sites. In this case, the customer service robot 10, server device 30, etc. of the customer service support system 1 may be configured to refer to the purchase history of products purchased by the customer on the e-commerce site, the search history of things the customer searched for on the search site, etc., based on the user ID, etc., as described later.

[0038] The following describes the hardware and functional configurations of the main devices included in Customer Service Support System 1.

[0039] First, let's describe the hardware configuration of the customer service robot 10. Figure 4 shows an example of the hardware configuration of the customer service robot 10. As shown in Figure 4, the customer service robot 10 is equipped with a CPU (Central Processing Unit) 151, a ROM (Read Only Memory) 152, and a RAM (Random Access Memory) 153.

[0040] The CPU 151 is an example of a processor that comprehensively controls each part of the customer service robot 10. The ROM 152 stores various programs. The RAM 153 is a workspace for displaying programs and various data.

[0041] The CPU 151, ROM 152, and RAM 153 are connected via a bus or the like to form a control unit 154 of the computer configuration. In the control unit 154, the CPU 151 operates according to a program stored in the ROM 152 or memory unit 161 and loaded into the RAM 153, thereby executing various processes.

[0042] The customer service robot 10 also includes the aforementioned drive unit 121, light-emitting unit 141, imaging unit 143, sound-collecting unit 144, and voice output unit 145. The sound-collecting unit 144 collects sounds from the vicinity of the customer service robot 10 (for example, customer speech) and outputs the audio signal of the collected sounds to the CPU 151. The voice output unit 145 outputs sound under the control of the CPU 151.

[0043] The customer service robot 10 also includes a display unit 155, an operation unit 156, a reader / writer unit 157, a sensor unit 158, a positioning unit 159, a communication unit 160, and a storage unit 161, etc.

[0044] The display unit 155 is a display device such as the rear display unit 115 and the front display unit 132 mentioned above. The display unit 155 is composed of, for example, an LCD (Liquid Crystal Display). The display unit 155 displays various information under the control of the CPU 151.

[0045] The operation unit 156 consists of input devices such as touch panels and stop buttons 142, which are provided on the rear display unit 115 and the front display unit 132. The operation unit 156 outputs the operation content input via the input devices to the CPU 151. The operation unit 156 may also output voice (for example, customer speech) input via the sound pickup unit 144 to the CPU 151 as operation content.

[0046] The reader / writer unit 157 is a reader / writer device capable of writing to and reading from wireless tags. The reader / writer unit 157 has an antenna (not shown) that emits radio waves, and writes data to the wireless tag by transmitting the data to be written via this antenna. The reader / writer unit 157 also reads data from the wireless tag by acquiring radio waves emitted by the wireless tag via the antenna.

[0047] The sensor unit 158 ​​consists of various sensor devices such as the distance measuring sensor and GPS sensor mentioned above. The sensor unit 158 ​​outputs the sensing results obtained through sensing to the CPU 151.

[0048] The positioning unit 159 measures the location where the customer service robot 10 is located. The positioning unit 159 can be implemented using positioning technology, such as a GPS sensor. Alternatively, the positioning unit 159 may be implemented using a location measurement device that utilizes positioning technology such as beacon positioning. In this case, by installing terminals compatible with positioning technology such as beacon positioning at various locations in the commercial facility, the positioning system formed by these terminals and the positioning unit 159 can measure (identify) the location where the customer service robot 10 is located.

[0049] The communication unit 160 is a wireless communication interface that can connect to the network N. The communication unit 160 communicates with external devices such as the server device 30 via the network N. The communication unit 160 also has short-range wireless communication capabilities such as Bluetooth (registered trademark). For example, the communication unit 160 performs short-range wireless communication with customer terminals 50 located around the customer service robot 10.

[0050] The memory unit 161 has a storage medium such as an HDD (Hard Disk Drive) or flash memory, and retains its contents even when the power is cut off. The memory unit 161 stores programs that the CPU 151 can execute and various setting information.

[0051] Note that the information stored in the memory unit 161 is not limited to the illustrated example. For example, the memory unit 161 may store map information 3161, store management tables 3162, product masters 2191 for each store, etc., which will be described later.

[0052] Next, the hardware configuration of the store device 20 will be described. Figure 5 is a diagram showing an example of the hardware configuration of the store device 20. As shown in Figure 5, the store device 20 includes a CPU 211, a ROM 212, and a RAM 213.

[0053] The CPU 211 is an example of a processor that comprehensively controls each part of the store equipment 20. The ROM 212 stores various programs. The RAM 213 is a workspace for displaying programs and various data.

[0054] The CPU 211, ROM 212, and RAM 213 are connected via a bus or the like to form a control unit 214 of the computer configuration. In the control unit 214, the CPU 211 operates according to a program stored in the ROM 212 or memory unit 219 and loaded into the RAM 213, thereby executing various processes.

[0055] The store device 20 also includes a display unit 215, an operation unit 216, a communication unit 217, a connection unit 218, and a storage unit 219, etc.

[0056] The display unit 215 has a display device such as an LCD. The display unit 215 displays various information under the control of the CPU 211. The operation unit 216 has an input device such as a keyboard or a pointing device. The operation unit 216 outputs the operation content input via the input device to the CPU 211. The operation unit 216 may be a touch panel provided on the display unit 215.

[0057] The communication unit 217 is a wireless communication interface that can be connected to the network N. The communication unit 217 communicates with external devices such as the customer service robot 10 and the server device 30 via the network N. The communication unit 217 may also have a short-range wireless communication function, and may be configured to communicate with the customer service robot 10 via short-range wireless communication.

[0058] The connection unit 218 is an interface for connecting various devices installed in the store. For example, a reader device capable of reading code symbols, a printer device, etc., may be connected to the connection unit 218. Electronic shelf labels, etc., which are installed at various positions on the store's display shelves, may also be connected to the connection unit 218. When electronic shelf labels are connected, the control unit 214 controls the electronic shelf labels placed at the product display positions to display the product name, price, etc. If the electronic shelf labels are equipped with light-emitting elements such as LEDs, the control unit 214 controls the light-emitting elements on the electronic shelf labels to emit light, etc., based on instructions from external devices such as the operation unit 216 or the customer service robot 10.

[0059] The memory unit 219 has a storage medium such as an HDD or flash memory and retains its contents even when the power is cut off. The memory unit 219 stores programs that the CPU 211 can execute and various setting information.

[0060] Furthermore, the memory unit 219 stores a product master 2191 in which information about products sold at its own store is registered. The product master 2191 is a data table for storing and managing information about products sold at the store.

[0061] Figure 6 shows an example of the data structure of the product master 2191. As shown in Figure 6, the product master 2191 stores product information including the store ID of its own store, the product code of the products sold at its store, the product name, price, additional information, and product image. Here, the store ID is an example of an identifier that can identify each store. The product code is an example of an identifier that can identify the type of product.

[0062] The "Product Name" field stores the name of the product corresponding to the product code. The "Price" field stores the price of the product corresponding to the product code. The "Additional Information" field stores additional information about the product corresponding to the product code. For example, the "Additional Information" field may store the product type, etc. Also, if the product is clothing, the size, color, design, material, brand, etc. will be stored in the "Additional Information" field. The "Product Image" field stores image data representing the product corresponding to the product code.

[0063] Note that the data structure of the product master 2191 is not limited to the example in Figure 6. For example, the product master 2191 may store the inventory quantity of a product in association with its product code. Alternatively, the product master 2191 may store information that identifies the display location of a product, the electronic shelf label placed at that display location, etc., in association with its product code.

[0064] Furthermore, the products registered in product master 2191 are not limited to products that can actually be picked up and taken home from a store (hereinafter also referred to as store products). For example, products registered in product master 2191 may be services.

[0065] Furthermore, in showroom-type stores that only display products, for example, the product code of the displayed product may be read to register and process payment for the product, and the product may be handed over to the customer using a specified delivery method (delivery, pickup at a counter, etc.). In such cases, additional information may be stored indicating whether the product corresponding to the product code is a store product that can be picked up at the store as described above, or a temporary product that cannot be picked up at the store, as described later. Also, for example, if payment for the displayed product is not made on the spot but on the store's e-commerce site, the e-commerce site address may be stored as additional information.

[0066] The data tables held by the store device 20 are not limited to the above example. For example, the store device 20 may hold a data table that records the sales performance of products sold in the store. Such a data table may have a data structure that records the number of units sold (number of units purchased) of each product over a predetermined period, associated with the product code of each product. The sales performance of each store and product may be managed by the server device 30.

[0067] Next, the hardware configuration of the server device 30 will be described. Figure 7 shows an example of the hardware configuration of the server device 30. As shown in Figure 7, the server device 30 includes a CPU 311, a ROM 312, and a RAM 313.

[0068] The CPU 311 is an example of a processor that comprehensively controls all parts of the server device 30. The ROM 312 stores various programs. The RAM 313 is a workspace for displaying programs and various data.

[0069] The CPU 311, ROM 312, and RAM 313 are connected via a bus or the like to form a control unit 314 of the computer configuration. In the control unit 314, the CPU 311 operates according to the program stored in the memory unit 316 and loaded into the RAM 313, thereby executing various processes.

[0070] The server device 30 also includes a communication unit 315 and a storage unit 316, etc. The communication unit 315 is a wired or wireless communication interface that can be connected to the network N. The communication unit 315 communicates with external devices such as the customer service robot 10, store equipment 20, and parking system 40 via the network N.

[0071] The memory unit 316 has a storage medium such as an HDD or flash memory, and retains its contents even when the power is cut off. The memory unit 316 stores programs that the CPU 311 can execute and various setting information.

[0072] Furthermore, the memory unit 316 stores map information 3161, a store management table 3162, a robot management table 3163, a user management table 3164, and a transaction management table 3165.

[0073] Map information 3161 is information that shows a map of a commercial facility. Map information 3161 shows the locations of stores and passageways within the commercial facility, and stores store IDs that can identify each store in relation to its location are stored. For example, if the commercial facility has a multi-story structure, map information 3161 is prepared for each floor. In addition, the locations of common spaces other than stores (e.g., elevators, escalators, restrooms, rest areas, etc.) are also stored in relation to identifiers in map information 3161.

[0074] The store management table 3162 is a data table for storing and managing information about stores located within a commercial facility. Figure 8 shows an example of the data structure of the store management table 3162. As shown in Figure 8, the store management table 3162 stores store information such as store name, store type, keywords, and status, associated with the store ID of each store located within the commercial facility. The store name field stores information indicating the name of the store corresponding to the store ID.

[0075] The "Store Type" field stores information such as the type of business the store operates and the classification of the products it handles. For example, the "Store Type" field can be defined in stages, such as a broad category like restaurants or retail stores, a medium category indicating the classification of the products handled (e.g., Japanese food, Chinese food, clothing stores, electronics stores, etc.), and a more detailed subcategory (e.g., sushi, soba noodles, men's clothing, women's clothing, etc.).

[0076] The keyword field stores one or more keywords that describe the characteristics and features of a store. While keywords can be arbitrarily set for each store, it is preferable to use keywords classified based on indicators derived from customer visit behavior. Furthermore, for stores in the same industry and genre, it is preferable to use keywords classified based on common indicators.

[0077] For example, restaurants can set keywords such as "want to eat," retail stores such as clothing stores can set keywords such as "want to buy," and stores such as arcades can set keywords such as "want to play." Furthermore, based on the characteristics of the products handled by the store, keywords such as "for men," "for women," and "for families" may also be set. These keywords can also be used to explore the customer's purpose in the visit purpose confirmation screen described later. Therefore, it is preferable to set indicators based on customer visit behavior.

[0078] The status field stores information such as the store's congestion level and whether it is open or closed.

[0079] Note that the data structure of the store management table 3162 is not limited to the example in Figure 8. For example, the store management table 3162 may store location information indicating the location of the store corresponding to the store ID, associated with the store ID. Furthermore, the store management table 3162 may also store information about shared spaces other than stores.

[0080] The robot management table 3163 is a data table for storing and managing information about the customer service robots 10. Figure 9 shows an example of the data structure of the robot management table 3163. As shown in Figure 9, the robot management table 3163 stores robot information such as current location, status, user ID, user characteristics, and action plan, associated with the robot ID. Here, the robot ID is an example of an identifier that can identify each of the customer service robots 10.

[0081] The "Current Location" field stores information indicating the current location of the customer service robot 10. The "Status" field stores information indicating the current state of the customer service robot 10 corresponding to the robot ID. For example, it stores information indicating the current operating mode of the customer service robot 10. It also stores information indicating the remaining battery level of the customer service robot 10.

[0082] The User ID field stores the User ID of the customer being served by the customer service robot 10, that is, the customer who has checked in with the customer service robot 10 (hereinafter also referred to as the check-in user). As will be described later, the customer service robot 10 can operate even if the User ID field is empty.

[0083] The "User Characteristics" field stores information that indicates the physical characteristics of the check-in user to the customer service robot 10. For example, the "User Characteristics" field stores images of the customer's face and appearance, as well as feature quantities that indicate the characteristics of the customer's face and appearance. User characteristics are used when recognizing the check-in user from images captured by the imaging unit 143. The "Action Plan" field stores the action plan generated by the customer service robot 10, which will be described later.

[0084] Note that the data structure of the robot management table 3163 is not limited to the example in Figure 9. For example, the robot management table 3163 may store the changes made to the customer service robot 10 by the personalization process described later as user settings, associated with the robot ID. Alternatively, the robot management table 3163 may store images, videos, audio, etc., acquired by the corresponding customer service robot 10, along with the date and time of acquisition, associated with the robot ID.

[0085] The user management table 3164 is a data table for storing and managing customer information. Figure 10 shows an example of the data structure of the user management table 3164. As shown in Figure 10, the user management table 3164 stores user information such as username, characteristic information, vehicle registration number, and user settings, associated with the user ID. Here, the user ID is an example of an identifier that can identify each customer.

[0086] The username field stores information indicating the customer's name. The characteristic information field stores information that identifies the customer corresponding to the user ID. For example, characteristic information may include information indicating the customer's gender, age, preferences, etc. Here, the information indicating preferences may be set by the customer themselves, or it may be derived from the customer's purchase history, search history, etc. In the latter case, for example, the control unit 314 may be configured to extract the customer's purchase history corresponding to the user ID from the transaction management table 3165, etc., described later, and estimate the customer's preferences based on the extracted purchase history. Alternatively, for example, the control unit 314 may obtain the purchase history and search history associated with the user ID from an external system and estimate the customer's preferences based on the obtained information. Note that there are no particular restrictions on the method of estimating preferences, and known technologies can be used.

[0087] The "Vehicle Registration Number" field stores the vehicle registration number of the vehicle owned by the customer. The "User Settings" field stores the settings that the customer has configured for the customer service robot 10 during the personalization process described later.

[0088] Note that the data structure of the user management table 3164 is not limited to the example in Figure 10. For example, the user management table 3164 may include the terminal ID and address information of the terminal (customer terminal 50) used by the customer, associated with the user ID. In addition, for facial recognition of the customer, the user management table 3164 may store a facial image of the customer's face, or feature quantities indicating the characteristics of the face, associated with the user ID.

[0089] Furthermore, the user management table 3164 may store information that identifies the delivery destination of the product, such as the customer's address, in association with the user ID. The user management table 3164 may also store payment information in association with the user ID. Here, payment information refers to account information for using an electronic payment service that the customer has contracted in advance. Electronic payment services include code payments, electronic money payments, and credit card payments. If the electronic payment service is a credit card payment, the payment information may also be the customer's credit card number.

[0090] The transaction management table 3165 is a data table for storing and managing information about transactions conducted through the customer service robot 10. Figure 11 shows an example of the data structure of the transaction management table 3165. As shown in Figure 11, the transaction management table 3165 stores transaction information such as store ID, product code, price, and purchased flag, associated with the robot ID and transaction ID.

[0091] Here, the transaction ID is an identifier that can identify each transaction performed by the customer service robot 10 corresponding to the robot ID. For example, a unique transaction ID is issued by the customer service robot 10 each time a customer checks in, and the same transaction ID is used continuously until the customer performs a checkout operation to indicate the end of using the customer service robot 10 (or the end of customer service by the customer service robot 10).

[0092] In this embodiment, each customer service robot 10 issues a transaction ID, but the configuration is not limited to this, and the server device 30 may issue the transaction IDs. In this case, the control unit 314 of the server device 30 monitors the status of the customer service robots 10 based on the robot management table 3163, and when it detects a customer service robot 10 whose status has switched to customer service mode, it issues a transaction ID to that customer service robot 10. The control unit 314 of the server device 30 then notifies the corresponding customer service robot 10 of the issued transaction ID, allowing the customer service robot 10 to continue using the same transaction ID as long as it remains in customer service mode.

[0093] The Store ID, Product Code, and Price fields store the Store ID, product code, and price of the product registered using the customer service robot 10 corresponding to the robot ID. The Purchased Flag field stores information indicating whether payment (accounting) for the product corresponding to the product code has been completed.

[0094] Note that the data structure of the transaction management table 3165 is not limited to the example in Figure 11. For example, the transaction management table 3165 may store the user ID of the check-in user who checked in to the corresponding customer service robot 10, associated with the robot ID and transaction ID. The transaction management table 3165 may also store information that identifies whether the product corresponding to the product code is a recommended product as described later, associated with the product code. Furthermore, the transaction management table 3165 may also store the date and time when the corresponding product was registered or settled, associated with the product code.

[0095] Furthermore, the transaction management table 3165 is updated each time a product is registered or payment is made by each of the customer service robots 10. The data stored in the transaction management table 3165 may be configured to either clear the data of the corresponding robot ID and transaction ID in response to instructions such as the end of customer service notified by the customer service robot 10 specifying the transaction ID, or to retain the data. In the latter case, the data stored in the transaction management table 3165 can be treated as the purchase history of each customer who uses the commercial facility.

[0096] Furthermore, the data tables held by the server device 30 are not limited to the above example. For example, the server device 30 may be configured to hold the product masters of all stores within the commercial facility as a comprehensive product master in the storage unit 316 or the like.

[0097] Furthermore, for example, the server device 30 may maintain a data table that records the sales performance of products sold at each store. Alternatively, the sales performance data table may be generated from the transaction information of each store stored in the transaction management table 3165. In this case, for example, the control unit 314 of the server device 30 may derive the number of units sold (number of units purchased) of each product purchased during a predetermined period for each store based on the transaction management table 3165, and store this as the sales performance of each store in a storage unit 316 or the like.

[0098] Next, we will describe the functional configuration of the customer service robot 10, store equipment 20, and server equipment 30 mentioned above. Figure 12 is a block diagram showing the functional configuration of the customer service robot 10, store equipment 20, and server equipment 30. First, we will describe the server equipment 30.

[0099] The control unit 314 of the server device 30 functions as an information management unit 3141 and a robot management unit 3142, with the CPU 311 operating according to programs stored in the ROM 312 and memory unit 316. Some or all of these functions may be implemented by hardware such as dedicated circuits.

[0100] The information management unit 3141 updates various data tables stored in the memory unit 316 by cooperating with the customer service robot 10, the store equipment 20, and the parking system 40. For example, the information management unit 3141 acquires information related to the various data tables from the customer service robot 10, the store equipment 20, and the parking system 40, and updates the various data tables based on the acquired information.

[0101] The method of acquiring information is not particularly limited, and various methods can be used. For example, the information management unit 3141 may acquire information in a push-type manner, passively acquiring information transmitted from the customer service robot 10, the store equipment 20, and the parking system 40. Alternatively, the information management unit 3141 may acquire information in a pull-type manner, actively acquiring information by requesting it from the customer service robot 10, the store equipment 20, and the parking system 40.

[0102] For example, when the information management unit 3141 obtains status information from the store device 20, it updates the status related to the store ID of the store device 20 stored in the store management table 3162.

[0103] For example, when the information management unit 3141 obtains location information, status, and action plan information from the customer service robot 10, it updates the corresponding data entry in the robot management table 3163, which is stored in association with the robot ID of the customer service robot 10. Also, when the information management unit 3141 obtains the user ID and user settings of the customer being served from the customer service robot 10, it updates the corresponding data entry in the user management table 3164, which is stored in association with the user ID. Furthermore, for example, when the information management unit 3141 obtains transaction information along with the transaction ID from the customer service robot 10, it adds or deletes data entries, updates the purchased flag, etc., in the transaction management table 3165 based on the robot ID and transaction ID of the customer service robot 10.

[0104] In this embodiment, static information such as user ID, username, characteristic information, and vehicle registration number among the user information stored in the user management table 3164 is assumed to be pre-registered, but is not limited to this. For example, new users may be registered (hereinafter also referred to as member registration) via the customer service robot 10 or customer terminal 50. In this case, the user management table 3164 adds the user information of the new user obtained from the customer service robot 10 or customer terminal 50 to the user management table 3164.

[0105] Furthermore, the information management unit 3141 provides the map information 3161 and various data tables stored in the storage unit 316 so that they can be accessed by each of the customer service robots 10 and store equipment 20. The method of providing the data is not particularly limited. For example, the information management unit 3141 provides the map information 3161 and various data tables so that they can be accessed by each of the customer service robots 10 using technologies such as file sharing. Alternatively, for example, the information management unit 3141 extracts the relevant data entries from the various data tables in response to queries using robot ID, user ID, store ID, etc. as keys, and provides them to the requesting customer service robot 10.

[0106] The robot management unit 3142 comprehensively manages the operation of the customer service robots 10 within the commercial facility based on their location information, status, etc. For example, if there are customer service robots 10 in standby mode that are not serving customers, the robot management unit 3142 instructs the standby customer service robots 10 on where to move. As an example, the robot management unit 3142 instructs each customer service robot 10 to move to the entrance of the commercial facility or to an area where there are relatively few customer service robots 10, based on their location.

[0107] Next, the functional configuration of the store device 20 will be described. The control unit 214 of the store device 20 includes a store information transmission unit 2141, a robot cooperation unit 2142, and a payment processing unit 2143, which are operated by the CPU 211 according to programs stored in the ROM 212 and the storage unit 219. Some or all of these functions may be implemented by hardware such as dedicated circuits.

[0108] The store information transmission unit 2141 transmits store information relating to its own store to the server device 30. For example, the store information transmission unit 2141 transmits information indicating the store's congestion status and whether it is open or closed, along with its own store ID, to the server device 30. Here, the store's congestion status may be derived, for example, based on the number of customers (customer service robots 10) who visit the store per unit of time. Alternatively, the store's congestion status may be derived, for example, based on the number of people included in images captured by surveillance cameras installed in the store. The store information transmission unit 2141 may also transmit keywords related to the store entered by store staff, etc., along with its own store ID, to the server device 30. The store information transmission unit 2141 may also transmit its own store's product master 2191 to the server device 30.

[0109] The robot collaboration unit 2142 accepts access from the customer service robot 10 via network N or short-range wireless communication. The robot collaboration unit 2142 establishes communication with the customer service robot 10 that initiated the access, thereby realizing collaboration with the customer service robot 10. The robot collaboration unit 2142 provides the collaborated customer service robot 10 with access to the product master 2191 and other information held by the store equipment 20.

[0110] Furthermore, the robot coordination unit 2142 works in cooperation with the customer service robot 10 to control the illumination of electronic shelf labels installed in the store. For example, when the robot coordination unit 2142 receives an illumination instruction from the customer service robot 10 specifying the type of product or a specific product, it illuminates the electronic shelf label of the product of the type specified in the illumination instruction or the display location where the specified product is displayed.

[0111] The payment processing unit 2143 performs payment processing for goods sold in the store. For example, the payment processing unit 2143 calculates the total amount based on the product code and quantity of each product registered by the registration device or customer service robot 10 installed in the store, and then performs the process of settling the total amount with the customer's payment amount. Furthermore, once the payment processing unit 2143 completes the payment processing, it issues a receipt with a breakdown of the payment processing from a printer (not shown). In this embodiment, the payment processing unit 2143 performs cash payment processing, but the available payment methods are not limited to this.

[0112] Next, the functional configuration of the customer service robot 10 will be described. The control unit 154 of the customer service robot 10 functions as a display control unit 1541, an operation reception unit 1542, a read / write control unit 1543, an operation control unit 1544, a personalization processing unit 1545, an action plan generation unit 1546, a store collaboration unit 1547, and a purchase support unit 1548, with the CPU 311 operating according to the program stored in the ROM 312 and the memory unit 316. Some or all of these functions may be implemented by hardware such as dedicated circuits.

[0113] The display control unit 1541 causes the display unit 155 to display various information. Specifically, the display control unit 1541 works in cooperation with the various functions of the customer service robot 10 to display various screens (GUI: Graphical User Interface) on the rear display unit 115 and the front display unit 132. The screens displayed by the display control unit 1541 will be described later.

[0114] The operation reception unit 1542 receives user input via the operation unit 156. For example, the operation reception unit 1542 receives input for the rear display unit 115 and the front display unit 132. The operation reception unit 1542 also receives input for the stop button 142. Furthermore, the operation reception unit 1542 receives voice input via the sound pickup unit 144, such as a wake word.

[0115] The read / write control unit 1543 reads information via the imaging unit 143, the reader / writer unit 157, etc. For example, when a code symbol such as a barcode or a two-dimensional code is captured by the imaging unit 143, the read / write control unit 1543 decodes the code symbol and reads the information held in the code symbol. Also, for example, the read / write control unit 1543 reads information held in the wireless tag by controlling the reader / writer unit 157. Also, for example, the read / write control unit 1543 writes information to the wireless tag by controlling the reader / writer unit 157.

[0116] For example, the read / write control unit 1543 reads the user ID from the code symbol displayed on the customer terminal 50. For example, the read / write control unit 1543 reads the product code from the code symbol attached to the product. The read / write control unit 1543 also reads the product code from the wireless tag attached to the product.

[0117] The motion control unit 1544 comprehensively controls the operation of the customer service robot 10. Specifically, the motion control unit 1544 controls the drive unit 121 and makes the customer service robot 10 move based on images captured by the imaging unit 143 and sensing results from various sensor units 158, thereby enabling the customer service robot 10 to move autonomously.

[0118] Furthermore, the motion control unit 1544 switches the operating mode of the customer service robot 10 according to the state of the customer service robot 10. The customer service robot 10 in this embodiment has three operating modes: a standby mode, a customer service mode, and a post-closing mode. In addition, the customer service robot 10 has two operating modes when in customer service mode: a lead mode and a follow mode.

[0119] Standby mode is the operating mode when the robot is not providing customer service. Customer service mode is the operating mode for providing customer service. Leading mode is the operating mode for leading customers to their destination, such as a store. Follow mode is the operating mode for following customers. After-hours mode is the operating mode for performing tasks other than customer service, such as after a commercial facility has closed.

[0120] Furthermore, in customer service mode, the operation control unit 1544 activates the personalization processing unit 1545, the behavior plan generation unit 1546, the store collaboration unit 1547, and the purchase support unit 1548 to support customer behavior.

[0121] In standby mode, the motion control unit 1544 displays a check-in screen on the front display unit 132 to initiate the use of the customer service robot 10. For example, the motion control unit 1544 displays a check-in screen on the front display unit 132 as shown in Figure 13.

[0122] Furthermore, the operation control unit 1544 may display a message on the rear display unit 115 indicating that check-in is possible, or an advertisement screen for a commercial facility, etc., while in standby mode. In addition, the operation control unit 1544 may output a voice prompt from the voice output unit 145 to encourage the user to perform the check-in operation.

[0123] Furthermore, the motion control unit 1544 may, during standby mode, stop the customer service robot 10 at a predetermined location, make it travel along a predetermined route, or make it travel in response to instructions from the server device 30. When the motion control unit 1544 makes the customer service robot 10 travel during standby mode, it will stop the customer service robot 10 if it detects the presence of a customer in the vicinity of the device or hears a voice calling out to it via the sensor unit 158 ​​or sound collection unit 144.

[0124] Figure 13 shows an example of a screen displayed on the front display unit 132 of the customer service robot 10. As shown in Figure 13, the check-in screen Ga displays an image that mimics a face, including eyes and a nose. The check-in screen Ga also displays a message Gaa prompting the customer to perform the check-in operation.

[0125] The method of performing the check-in operation is not particularly limited, but it is preferable to provide separate methods for customers whose user information is registered in the user management table 3164 (hereinafter also referred to as members) and for non-members whose user information is not registered in the user management table 3164. In this embodiment, the operation of entering a user ID into the customer service robot 10 is considered the check-in operation for members. Furthermore, the check-in operation for non-members is considered to be a touch operation on the check-in screen Ga that does not require entering a user ID. Note that Figure 13 shows an example where the check-in screen Ga displays an image Gab that guides the user to read a code symbol in order to prompt the user to enter a user ID.

[0126] Image Gab may also include information guiding the customer service robot 10 to read the code symbol displayed on the customer terminal 50. Furthermore, if a check-in code symbol is displayed on the check-in screen Ga, Image Gab may include the code symbol and information guiding the customer to read it on the customer terminal 50. In the latter case, it is preferable to include information for establishing pairing with the customer service robot 10 (described later) in the code symbol displayed on the check-in screen Ga. In this case, the operation control unit 1544 may accept user ID input by obtaining the user ID from the customer terminal 50 with which pairing has been established.

[0127] For example, when a code containing a user ID displayed on the customer terminal 50 is held towards the front-facing imaging unit 143, the read / write control unit 1543 reads the user ID from the code symbol. When the operation control unit 1544 receives the user ID input via the read / write control unit 1543, it searches the user management table 3164 for the input user ID to verify whether the user is a member or not. If the input user ID is registered in the user management table 3164, the operation control unit 1544 determines that a check-in operation has been performed by a member and switches from standby mode to customer service mode. The operation control unit 1544 may also issue a transaction ID when it switches to customer service mode.

[0128] Furthermore, the motion control unit 1544 acquires images and features of customers who have performed the check-in operation from the images captured by the imaging unit 143 as user features, and stores them in RAM 153 or the like, associated with the input user ID. The motion control unit 1544 then registers the current operating mode, the input user ID, and the user features in the robot management table 3163, associated with the robot ID of its own device.

[0129] In the case where facial images for facial recognition are stored in the user management table 3164, the operation control unit 1544 may accept user ID input by comparing the customer's facial image captured by the imaging unit 143 with the facial image stored in the user management table 3164 and obtaining the corresponding user ID.

[0130] Furthermore, when the motion control unit 1544 receives a touch operation on the check-in screen Ga, it determines that the check-in operation was performed by a non-member and switches from standby mode to customer service mode. In this case, the motion control unit 1544 locally stores the user characteristics of the customer who performed the check-in operation and registers the current operating mode and user characteristics in the robot management table 3163 in association with the robot ID of its own device. In this case, the personalization processing unit 1545 may also display a screen prompting member registration on the front display unit 132.

[0131] Furthermore, even if a check-in operation is performed via touch, during customer service mode, the user can switch to a member check-in state by entering their user ID at any time.

[0132] Furthermore, the motion control unit 1544 can establish short-range wireless communication (pairing) with the customer terminal 50 regardless of whether the customer who has checked in is a member or not. In this case, for example, the motion control unit 1544 displays setting information for pairing with its own customer service robot 10 in the form of a two-dimensional code or the like on the front display unit 132, or reads information held by the customer terminal 50 via the read / write control unit 1543. Once pairing with the customer terminal 50 is established, the motion control unit 1544 captures the location of the check-in user and the distance to the customer service robot 10 based on RSSI (Received Signal Strength Index), etc., and sends and receives various information.

[0133] Furthermore, the device to be paired (hereinafter also referred to as the pairing device) is not limited to the customer terminal 50, but may be a simpler beacon terminal or remote control terminal, etc. In this case, the pairing device may be lent out by the commercial facility, or it may be attached to the customer service robot 10 in a manner that allows it to be attached or detached. Once pairing with the pairing device is established, the motion control unit 1544 will capture the location of the check-in user and the distance to the customer service robot 10 based on RSSI (Received Signal Strength Indicator), etc., and will send and receive various information. The motion control unit 1544 may also stop the movement of the customer service robot 10 or switch between lead mode and follow mode based on instructions from the pairing device.

[0134] The personalization processing unit 1545 performs personalization processing to change the settings of the customer service robot 10 in response to the check-in user's actions.

[0135] The settings of the customer service robot 10 that can be changed are not particularly restricted as long as they do not interfere with the basic operation of the customer service robot 10. For example, the display color of the light-emitting unit 141, the image of a face displayed on the front display unit 132, the display language of the UI, and the artificial voice (male voice, female voice, spoken language, etc.) emitted by the customer service robot 10 can be changed. In addition, if the customer service robot 10 has a voice assistant function, the wake word used to invoke (activate) the voice assistant function can be changed. Furthermore, various notification methods and payment methods performed by the customer service robot 10 can be set. Note that the initial settings of the customer service robot 10 may be the same or different.

[0136] Furthermore, there are no specific restrictions on how settings can be changed; they can be changed via screen operation or voice control. For example, the personalization processing unit 1545 may display a screen on the front display unit 132 to confirm whether or not to change the settings after the check-in operation. In this case, when the personalization processing unit 1545 is instructed to change the settings, it displays a settings change screen on the front display unit 132 showing the items that can be changed (neither is shown in the diagram). Once the customer has decided on the changed settings, the personalization processing unit 1545 changes the settings of its own device to the changed settings. It should be noted that during customer service mode, settings can be changed at any time.

[0137] Furthermore, when a setting change is made, the personalization processing unit 1545 associates the changed setting with the user ID of the check-in user and registers it as a user setting in the user management table 3164.

[0138] Furthermore, if the check-in user is a member, the personalization processing unit 1545 may read the user settings stored in association with the check-in user's user ID from the user management table 3164 and change the settings of its own device based on those user settings. Also, if the code symbol displayed on the customer terminal 50 includes user settings, the personalization processing unit 1545 may change the settings of its own device based on the user settings read by the read / write control unit 1543 during check-in.

[0139] In this way, the customer service robot 10 allows for customer-specific customization by changing its settings according to customer operations. This allows customers to easily distinguish their own customer service robot 10 from other customer service robots 10. Furthermore, customers can shop and perform other tasks using a customer service robot 10 customized to their preferences.

[0140] In this embodiment, it is possible to change settings regardless of whether the check-in user is a member or not. If the check-in user is not a member, the personalization processing unit 1545 reflects the changes in its own device without registering them in the user management table 3164. Alternatively, the configuration may be set up so that non-members cannot change settings.

[0141] The behavior plan generation unit 1546 performs processing to support the customer's behavior within the commercial facility. Specifically, the behavior plan generation unit 1546 narrows down destinations while confirming the customer's purpose and conditions, generates a planned behavior plan for the customer's destinations within the commercial facility, and presents it to the customer.

[0142] Here, an example of the operation of the action plan generation unit 1546 will be explained with reference to Figures 14 to 16. Figures 14 to 16 show an example of the screen displayed on the front display unit 132 of the customer service robot 10.

[0143] First, the action plan generation unit 1546 displays a visit purpose confirmation screen Gb, as shown in Figure 14, on the front display unit 132 in order to confirm the customer's purpose for visiting the store (hereinafter also simply referred to as purpose). The visit purpose confirmation screen Gb displays options Gba that indicate the type of purpose, which are set based on the store type and keywords of each store registered in the store management table 3162. For example, as shown in Figure 14, general purposes such as "I want to buy," "I want to play," and "I want to eat" are displayed as options Gba. Here, it is possible to select, for example, one of the options Gba. After one of the options Gba is selected, and the selection is confirmed by operating the central operator Gbb, the action plan generation unit 1546 displays a visit purpose confirmation screen Gc on the front display unit 132 in order to further narrow down the purpose of the selected option Gba.

[0144] On the visit purpose confirmation screen Gc, options Gca are displayed that offer more detailed objectives based on the objective selected on the previous visit purpose confirmation screen Gb. Figure 15 shows an example of the visit purpose confirmation screen Gc, illustrating the case where the "I want to buy" option Gba is selected from the visit purpose confirmation screen Gb in Figure 14.

[0145] Here, the options Gca on the visit purpose confirmation screen Gc may display, for example, the names of stores where the product can be purchased. Alternatively, the options Gca on the visit purpose confirmation screen Gc may display the types of products available for purchase at the commercial facility. In the latter case, once the type of product is selected via the options Gca and confirmed by the operation of the operator Gcb, the action plan generation unit 1546 may further display a new visit purpose confirmation screen (not shown) with the names of stores selling the selected type of product as options. In this way, the action plan generation unit 1546 determines a destination store (hereinafter also referred to as the destination store) that matches the customer's purpose by gradually narrowing down the customer's objective.

[0146] There is no particular limit to the number of times the customer can narrow down their search using the visit purpose confirmation screen. For example, the number of times the search is narrowed down may differ depending on the purpose. Also, although the example above shows the customer selecting a destination store at the final stage of the narrowing process, the number of selectable stores is not limited to one; there may be multiple stores.

[0147] Furthermore, the action plan generation unit 1546 may be configured to automatically determine destination stores based on the selected objective conditions, without requiring the customer to directly select a destination store. In this case, the action plan generation unit 1546 may determine one or more destination stores based on characteristic information and purchase history stored in association with the check-in user's user ID.

[0148] Furthermore, on the visit purpose confirmation screen, after deciding on a destination store for a certain purpose, it is possible to return to the initial or previous visit purpose confirmation screen to decide on a destination store for a different purpose.

[0149] When the action plan generation unit 1546 receives an operation to confirm a destination store, it generates an action plan showing the route to the destination store based on the location information of each destination store, the current location of its own customer service robot 10, and the map information 3161. The action plan generation unit 1546 then displays a screen representing the generated action plan (hereinafter also referred to as the action plan screen) on the front display unit 132.

[0150] Here, the action plan includes at least a store ID corresponding to each destination store, sequence information to define the order in which the destination stores are visited, and a visit flag to determine whether or not a destination store has been reached (entered). The action plan may also include information indicating the location of the destination stores (e.g., floor). Furthermore, the action plan may include the distance between destination stores, the time required for travel, the time spent at each destination store, the total time including travel time and time spent at each store.

[0151] In this case, a uniform stay time may be set for each store. Alternatively, the stay time may be set according to the destination store and its type, based on the average stay time calculated in advance for each store or store type. Furthermore, in a configuration where the activity history is recorded in association with the user ID of the check-in user, the stay time for destination stores may be extracted from past activity history, and the average of the extracted stay times may be set as the stay time.

[0152] Furthermore, there are no particular restrictions on the method for determining the order in which destination stores are visited, and known techniques such as route searching can be used. For example, the action plan generation unit 1546 may arrange the destination stores in order of proximity to the current location. Alternatively, the action plan generation unit 1546 may also take into account the congestion status of the destination stores and arrange them in an order that minimizes waiting time.

[0153] Figure 16 shows an example of an action plan screen. The action plan screen Gd displays the names of each destination store specified in the action plan, as well as the order in which the stores will be visited. Figure 16 shows an example where the stores are visited in the order of Store A, Store B, Store C, and Store D. Specifically, in Figure 16, information about the destination stores, such as the floor Gda on which the destination store is located, the icon Gdb indicating the type of destination store, and the name of the destination store Gdc, is arranged from top to bottom of the screen in the order of the destination stores to be visited. Figure 16 also shows an example where the travel time Gdd required to move between destination stores and the total time Gde, which is the sum of the travel time and the time spent at each destination store, are displayed.

[0154] Customers operating the customer service robot 10 can view the action plan screen Gd to confirm their destination stores and their order. The action plan screen Gd also allows customers to change the order of destination stores or delete them based on their actions.

[0155] For example, in the action plan screen Gd of Figure 16, if the user long-presses one destination store and moves to a location between other destination stores, the action plan generation unit 1546 updates the action plan by inserting the long-pressed destination store into the moved location. Also, for example, in the action plan screen Gd of Figure 16, if the user flicks one destination store (for example, store C), the action plan generation unit 1546 deletes the destination store that was the target of the operation and updates the action plan.

[0156] Furthermore, the action plan screen Gd allows for the addition of destination stores in response to customer operations. For example, upon receiving an operation from the operator Gdf, the action plan generation unit 1546 displays a screen on the front display unit 132 that allows for the addition of destination stores. Such a screen may be, for example, a screen displaying a list of store names that allows for direct selection of stores, or it may be the store visit purpose confirmation screen described above.

[0157] Furthermore, the action plan screen Gd is provided with an operator Gdg for displaying a map of the commercial facility. When the action plan generation unit 1546 receives an operation from the operator Gdg, it displays a screen on the front display unit 132 (not shown) that shows the location of each destination store on a map of the commercial facility based on the map information 3161. The action plan generation unit 1546 may also perform processing on the displayed map, such as assigning numbers to each location of the destination stores to indicate the order in which to visit them, or highlighting the travel route between destination stores.

[0158] Furthermore, the action plan screen Gd is equipped with an operator Gdh that instructs the user to begin moving to the destination store. When operator Gdh is operated, the operation control unit 1544 switches the operating mode of its device to lead mode. The operation control unit 1544 may also issue a transaction ID when the action plan is generated or when the user is instructed to begin moving to the destination store.

[0159] Furthermore, on the action plan screen Gd, it is possible to select the name of the destination store displayed and set the processing to be performed when arriving at that destination store. For example, when arriving at the destination store, a task can be set to illuminate the electronic shelf labels displaying the type of product selected on the store visit purpose selection screen. The tasks set for the destination store are executed by the motion control unit 1544 when the customer service robot 10 arrives at that store.

[0160] Here, a task defines the processing requested by the customer and is executed at a predetermined time. For example, a task can be represented as a pair of execution conditions and processing content. In the above example, the execution conditions are defined as a pair of the "store name" of the store where the processing will be performed and "arrival at the store" which defines the timing of the processing. The processing content includes a product code representing the type of product selected on the store visit purpose selection screen, as well as a command to instruct the electronic shelf label to light up. The processing content of a task set for a destination store is executed by the control of the operation control unit 1544 based on the execution conditions of that task. Note that the execution conditions and processing content that can be set as a task are not limited to these.

[0161] When the motion control unit 1544 switches to lead mode, it moves the customer service robot 10 toward the destination store based on the action plan generated by the action plan generation unit 1546. Specifically, the motion control unit 1544 moves the customer service robot 10 toward the destination stores in the order specified in the action plan. For example, in the action plan shown in Figure 16, the motion control unit 1544 first moves the customer service robot 10 toward store A. The motion control unit 1544 also makes the customer service robot 10 travel at a speed corresponding to the travel time between stores specified in the action plan.

[0162] Furthermore, in lead mode, the motion control unit 1544 guides (leads) the customer toward the destination store by moving ahead of the customer while maintaining a predetermined distance from the customer who has checked in. Specifically, based on the customer image stored at the time of check-in, the motion control unit 1544 identifies a person who matches the user characteristics from the images captured by the imaging unit 143, i.e., the check-in user. Then, the motion control unit 1544 moves ahead of the identified customer toward the destination store while maintaining a predetermined distance from that person. At this time, the motion control unit 1544 displays a screen on the rear display unit 115 indicating that it is being guided toward the destination store (hereinafter also referred to as the guidance screen), prompting the customer to follow the device.

[0163] Figure 17 shows an example of a screen displayed on the rear display unit 115 of the customer service robot 10, and illustrates an example of a guidance screen. As shown in Figure 17, the guidance screen Ge displays a message Gea indicating that the robot is guiding the customer to the destination store (store A). The guidance screen Ge also displays an arrow Geb indicating the direction in which the customer service robot 10 is moving, and the distance Geec to the destination store. Furthermore, the guidance screen Ge displays surrounding information Ged at the top of the screen, indicating the shared space around the customer service robot 10's current location. Here, the position where the surrounding information Ged is displayed on the screen corresponds, for example, to the direction of the shared space relative to the customer service robot 10's current location and movement method.

[0164] Furthermore, the operation control unit 1544 may provide guidance not only through screen displays but also through voice output. For example, the operation control unit 1544 may output voice guidance for moving to the destination store along with the guidance screen.

[0165] The screen displayed on the front display unit 132 while the customer service robot 10 is moving is not particularly limited. For example, the motion control unit 1544 may display an image resembling a face, such as eyes and a nose, on the front display unit 132 while the customer service robot 10 is moving, similar to the check-in screen Ga described above. However, unlike the check-in screen Ga, it is preferable to also display information indicating that the robot is guiding a customer.

[0166] This allows customers to easily confirm their destination store and the distance to that store by looking at the guidance screen displayed on the rear display unit 115 of the preceding customer service robot 10. In addition, customers can easily check the surrounding common areas while on their way to their destination store, and can go to those common areas if necessary.

[0167] If a customer moves away from the customer service robot 10, for example by heading towards a common area, the customer will move in a direction different from the direction of movement of the customer service robot 10, and the distance to the customer service robot 10 will deviate from a predetermined value, resulting in an action outside the action plan. When the motion control unit 1544 detects the customer's action outside the action plan based on the image from the imaging unit 143, it cancels the leading mode and switches to a follow mode in which it moves following the customer. Also, if a customer enters a common area, the motion control unit 1544 waits, for example, at a predetermined waiting area near the common area, until the customer leaves the common area. Here, the motion control unit 1544 may temporarily switch the operation mode of its customer service robot 10 to standby mode while waiting at the waiting area. Then, when a customer matching the user characteristics leaves the common area, the motion control unit 1544 switches to the leading mode and continues guiding the customer to the destination store.

[0168] Furthermore, if a customer decides to go to another store while being led, the motion control unit 1544 will deactivate the leading mode and switch to the following mode. In this case, the motion control unit 1544 will continue the following mode until the customer leaves the store, and when it detects that the customer has left the store based on the location information of the positioning unit 159, it will switch back to the leading mode and continue guiding the customer to the destination store. In this case, the motion control unit 1544 may also be configured to cooperate with the action plan generation unit 1546 to update the action plan, such as by changing the order in which destination stores are visited.

[0169] Furthermore, the motion control unit 1544 can accept customer input even while operating in lead mode. For example, if the motion control unit 1544 receives an input from the stop button 142 while the customer service robot 10 is moving, it will stop the customer service robot 10 from moving. Also, for example, if the motion control unit 1544 receives an input from touching the rear display unit 115, knocking on the main unit 11, or calling out a wake word, it will stop the customer service robot 10 from moving. Also, for example, the motion control unit 1544 will stop the customer service robot 10 from moving in response to instructions from the pairing device. The motion control unit 1544 will then display the action plan screen Gd, etc., on the front display unit 132, making it possible to accept various operations. Furthermore, if the motion control unit 1544 receives an instruction from a customer, for example, that they want to go to a common space, while moving according to a set movement route, it will change the action plan and lead the customer to the specified common space. At that time, the action plan generation unit 1546 will reset the movement route.

[0170] Furthermore, when the motion control unit 1544 stops the customer service robot 10 from moving, it may stop it with the front display unit 132 facing the customer.

[0171] When the motion control unit 1544 determines that the customer service robot 10 has reached its destination store by moving in lead mode, it switches the robot's operation mode from lead mode to follow mode. For example, the motion control unit 1544 determines that the customer service robot 10 has reached its destination store when its current position enters a predetermined area based on the destination store's location information.

[0172] Here, the area used for determining arrival at the destination store can be arbitrarily set. For example, the entire premises of the store may be used as the area for determining arrival. Alternatively, for example, if the destination store is a specific store (restaurant) located in a food court, the entire food court may be used as the area for determining arrival.

[0173] Furthermore, the method for determining arrival at a store is not limited to location information; the operation control unit 1544 may also detect arrival at the destination store by coordinating with gate terminals or beacon terminals installed at the entrance (or exit) of the store. In this case, the operation control unit 1544 determines arrival at the destination store based, for example, on a store ID notified by the gate terminal or beacon terminal.

[0174] When the motion control unit 1544 switches to follow mode, it controls the movement of the customer service robot 10 to follow the customer. For example, the motion control unit 1544 detects the check-in user from the image captured by the front-facing imaging unit 143, and moves the robot behind the detected check-in user while maintaining a predetermined distance from the user. In this way, the motion control unit 1544 makes the customer service robot 10 move to follow the customer while the customer stays at the destination store.

[0175] Furthermore, when the motion control unit 1544 switches to follow mode, it may notify the customer of the switch to follow mode via screen display or voice. For example, when the motion control unit 1544 switches to follow mode, it may turn the front of the customer service robot 10 towards the customer and output information from the front display unit 132 or voice output unit 145 to notify the customer that they have arrived at the destination store, or to notify them of follow actions such as "I will accompany you." In addition, the rear display unit 115 may display information notifying the customer that it is operating in follow mode, or it may display other information. For example, the motion control unit 1544 may display information such as advertisements for the destination store that has been arrived at or advertisements encouraging the use of the customer service robot 10 on the rear display unit 115.

[0176] When the motion control unit 1544 determines that the destination store has been reached, it activates the store coordination unit 1547 and coordinates its own customer service robot 10 with the store equipment 20 installed at the destination store. The store coordination unit 1547 accesses the store equipment 20 via network N or short-range wireless communication, thereby enabling the customer service robot 10 to operate in coordination with the store equipment 20 at the destination store. For example, when the customer service robot 10 reaches the destination store, the store coordination unit 1547 accesses the store equipment 20 at that destination store, enabling it to refer to the product master 2191, etc., held by the store equipment 20.

[0177] Furthermore, the motion control unit 1544 can also work in cooperation with the store equipment 20 to illuminate electronic shelf labels. For example, if a task is set for the destination store reached by the customer service robot 10 to illuminate the electronic shelf labels at the display locations of a specific type of product, the motion control unit 1544 will work in cooperation with the store equipment 20 to illuminate the electronic shelf labels at the corresponding display locations.

[0178] Specifically, the store coordination unit 1547 searches the product master 2191 for products that match the type set in the task and identifies the display location of those products. Then, the store coordination unit 1547 works in cooperation with the store device 20 to control the illumination of the electronic shelf labels placed at the identified display location.

[0179] As a result, when a customer arrives at their destination store guided by the customer service robot 10, they can easily find the display location of the product they intend to purchase. Therefore, the customer service robot 10 can efficiently assist customers in purchasing the product they intend to buy. If the light-emitting color of the light-emitting unit 141 is set by the user, the store communication unit 1547 may be controlled to illuminate the electronic shelf label with the light-emitting color set by the user.

[0180] The purchase support unit 1548 is an example of a registration means, reception means, payment means, and recommendation means. The purchase support unit 1548 performs processing to support the purchase of goods at the store to which its customer service robot 10 has moved. For example, the purchase support unit 1548 performs processing to register the goods corresponding to the product code as a purchase target based on the product code read from the code symbol or wireless tag. Specifically, when the purchase support unit 1548 reads the product code from the product master 2191 when the product code is read by the read / write control unit 1543, it reads product information such as the product name and price of the goods corresponding to that product code and registers it in a data table (hereinafter also called the local transaction management table) stored in RAM 153, etc. Here, the local transaction management table may have a data structure similar to that of the transaction management table 3165, or it may have a data structure that excludes the robot ID from the transaction management table 3165.

[0181] Furthermore, the purchase support unit 1548 executes settlement processing for products registered in the local transaction management table in response to customer operations. Specifically, the purchase support unit 1548 executes settlement processing to settle the total amount of products registered in the local transaction management table with the amount paid by the customer. Once the settlement processing is complete, the purchase support unit 1548 assigns a purchased flag to the product code of the settled product registered in the local transaction management table, associating it with the product code.

[0182] Furthermore, there are no specific restrictions on the payment method; credit card payments, electronic money payments, QR code payments, and other electronic payment methods are all possible. Additionally, if the customer service robot 10 is equipped with an automated cash payment machine, cash payments will also be available.

[0183] If the customer service robot 10 is not equipped with an automated cash payment machine, the purchase support unit 1548 will transmit payment data to an external device capable of cash payment via network N or short-range wireless communication, thereby causing the device to perform the cash payment. For example, the purchase support unit 1548 will transmit payment data to the store's store equipment 20, causing the store equipment 20 to perform the cash payment. Note that the destination of the payment data is not limited to the store equipment 20; the payment data may also be transmitted to an accounting machine for cash payments installed within the commercial facility.

[0184] Furthermore, the purchase support unit 1548 may determine the destination external device based on the status of the external device capable of cash payment. For example, the destination external device may be determined based on the amount of change available in the external device or the usage status of the external device. In addition, when the payment is to be made by an external device, it is preferable for the purchase support unit 1548 to work in cooperation with the operation control unit 1544 to guide the customer to the destination external device.

[0185] Furthermore, upon completion of the payment processing, the purchase support unit 1548 outputs a receipt showing the details of the transaction. For example, if the customer service robot 10 is equipped with a printer, or if a printer is connected to the customer service robot 10, the purchase support unit 1548 controls the printer to output a receipt from it.

[0186] The purchase support unit 1548 may also print a receipt in the form of an electronic receipt. In this case, the purchase support unit 1548 may send the electronic receipt to the customer terminal 50 with which pairing has been established. Alternatively, the purchase support unit 1548 may send the electronic receipt to an address stored in the user management table 3164.

[0187] In this case, the purchase support unit 1548 may print a receipt each time a payment is processed, or it may print a receipt for each store. In the latter case, the purchase support unit 1548 may print a receipt when the customer service robot 10 leaves the store. Furthermore, the purchase support unit 1548 may print a collection of receipts for all the payment processes performed at each store once the visit to all stores specified in the action plan has been completed. The timing of receipt printing can be selected by the customer. The timing of receipt printing can also be set through a personalization process.

[0188] Furthermore, when the purchase support unit 1548 updates the local transaction management table upon registration of a product or completion of payment processing, it sends the updated content along with its robot ID and the transaction ID of the transaction to the server device 30, thereby updating the transaction management table 3165 of the server device 30. As a result, the latest status of transactions performed by each customer service robot 10 is reflected in the transaction management table 3165 of the server device 30. In this embodiment, the transaction status is stored in the transaction management tables of both the customer service robot 10 and the server device 30, but this is not limited to this configuration, and the status may be stored in either one of the transaction management tables.

[0189] Furthermore, the purchase support unit 1548 is equipped with functions to assist customers in selecting potential purchase items. Specifically, the purchase support unit 1548 has a recommendation function that selects and presents products that are suitable for the customer's preferences.

[0190] For example, in a clothing store or similar establishment, when a standard product is selected as the basis for recommendations by reading the product code, the purchase support unit 1548 selects products suitable for combination (or substitution) as recommended products based on additional information such as size, color, and design included in the product's supplementary information. The purchase support unit 1548 then presents the selected recommended products to the customer by displaying them on the front display unit 132. The customer can then instruct the system to register the presented recommended products as items to purchase or to reject them.

[0191] Furthermore, there are no particular restrictions on the method of selecting recommended products, and it is possible to use publicly known recommendation technologies. For example, the purchase support unit 1548 may select products as recommended products that match the customer's purchasing trends and preferences based on the customer's purchase history, search history, etc., associated with the customer's user ID. In this embodiment, the recommended products to be selected are store products sold in stores that are registered in the product master 2191, but are not limited to these.

[0192] Here, we will explain an example of the operation of the purchase support unit 1548 with reference to Figures 18 to 25. Figures 18 to 25 show an example of the screen displayed on the front display unit 132 of the customer service robot 10. Note that Figures 18 to 25 show an example of operation in a clothing store.

[0193] First, when the customer service robot 10 switches to follow mode, the purchase support unit 1548 displays the screen shown in Figure 18 (hereinafter also referred to as the basic operation screen) on the front display unit 132 and waits for customer input.

[0194] Figure 18 shows an example of the basic operation screen. As shown in Figure 18, the basic operation screen Gf displays a message prompting the user to scan the product and an image Gfa. Above the basic operation screen Gf, there is a store name area Gfb that displays the name of the store the user is currently in, and an operator Gfc, which will be described later.

[0195] Additionally, images Gfd and Gfe are displayed below the basic operation screen Gf. Image Gfd is an icon indicating that code symbols can be read, and image Gfe is an icon indicating that wireless tags can be read.

[0196] Furthermore, the image Gfd and Gfe may also be operators for activating the hardware configuration related to the reading function. For example, when either the image Gfd or Gfe icon is touched, the purchase support unit 1548 may perform control to activate the imaging unit 143 or the reader / writer unit 157 according to the touched icon.

[0197] Additionally, the basic operation screen Gf displays the operators Gff, Gfg, and Gfh. Operator Gff is used to contact store staff. Operator Gfg is used to check registered products. Operator Gfh is used to initiate payment processing.

[0198] When the operator Gff is operated, the purchase support unit 1548 works in cooperation with the store device 20 to perform a process to request assistance from a store employee. For example, the purchase support unit 1548 requests assistance from a store employee by sending inquiry information to the store device 20, including the location of its own customer service robot 10, information specifying the product to be inquired about, and the user ID of the check-in user. In this case, the store device 20 notifies the store employee's terminal of the location of the customer service robot 10, prompting the employee to assist the customer.

[0199] During follow-up mode, when the purchase support unit 1548 receives input of a product code by reading a code symbol or wireless tag, it displays, for example, the screen shown in Figure 19 (product screen) on the front display unit 132. Figure 19 is a diagram showing an example of a product screen.

[0200] The product screen Gg has various controls as described in the basic operation screen Gf. In addition, a region Gga for displaying product images is provided in the center of the product screen Gg. Specifically, the purchase support unit 1548 reads product information for the product corresponding to the entered product code from the product master 2191 and displays the product image included in the read product information in region Gga.

[0201] Figure 19 shows the state after product AAA has been read, with the product image of product AAA displayed in area Gga. Figure 19 also shows an example where the product name, price, etc. of product AAA are displayed.

[0202] Furthermore, the product screen Gg is provided with operators Ggb, Ggc, and Ggd. Here, operator Ggd is an operator used to instruct the registration of the product displayed in area Gga, that is, the product corresponding to the entered product code. When the purchase support unit 1548 receives an operation from operator Ggd, it executes a registration process (hereinafter also simply referred to as registration) to register the product information of the corresponding product in the local transaction management table based on the entered product code.

[0203] In this example, the system registers the product corresponding to the entered product code in response to the operation of the operator Ggd, but it is not limited to this configuration. For example, when a product code is entered, the purchase support unit 1548 may immediately register the corresponding product. In this case, the purchase support unit 1548 may display a product screen without the operator Ggd.

[0204] Furthermore, the purchase support unit 1548 registers transaction information in the transaction management table 3165 by sending the record from the local transaction management table relating to the registered product, along with the robot ID of its customer service robot 10 and the transaction ID of the transaction, to the server device 30. The purchase support unit 1548 may also notify the store device 20 of information (e.g., product code) about the product registered with its customer service robot 10.

[0205] The operator Ggb is used to instruct the user to try on the product displayed in area Gga. When the purchase support unit 1548 receives an operation from the operator Ggb, it displays the customer's image captured by the imaging unit 143 on the front display unit 132. This allows the customer who has tried on the product to operate the operator Ggb to have their image captured and then confirm their appearance by viewing the image displayed on the front display unit 132.

[0206] In this embodiment, the customer actually tries on the product, but this is not the only option. For example, the system may be configured to allow virtual try-on using known AR (augmented reality) or VR (virtual reality) technologies. In this case, the purchase support unit 1548 generates a composite image by superimposing the product image of the product displayed in area Gga onto the image of the customer captured by the imaging unit 143. The purchase support unit 1548 then displays the generated composite image on the front display unit 132 to realize virtual try-on.

[0207] Furthermore, the operator Ggc is an operator used to request the display of recommended products. When the purchase support unit 1548 receives an operation from the operator Ggc, it selects products that can be combined with the standard product from the product master 2191 as recommended products, based on additional information of the product displayed in area Gga, that is, the product corresponding to the entered product code (standard product). In addition, if the check-in user is a member, the purchase support unit 1548 selects recommended products from the product master 2191 based on the purchase history and search history associated with the user ID. Then, based on the product information of the selected recommended products, the purchase support unit 1548 displays a screen (hereinafter also referred to as the recommendation screen) showing the product image of the product on the front display unit 132.

[0208] Figure 20 shows an example of a recommendation screen. The recommendation screen Gh has a screen configuration similar to, for example, the product screen Gg, and has various controls as described in the basic operation screen Gf. In addition, a region Gha for displaying product images is provided in the center of the recommendation screen Gh. Specifically, the purchase support unit 1548 displays the product image of the selected recommended product (product BBB) in region Gha. The purchase support unit 1548 also displays the product name, price, etc. of the recommended product below region Gha. Furthermore, the purchase support unit 1548 displays a message Ghb recommending the product above region Gha.

[0209] Furthermore, the recommendation screen Gh is provided with an operator Ghc for instructing registration. When the purchase support unit 1548 receives an operation from the operator Ghc, it executes the product registration process based on the product code of the recommended product displayed in area Gha. In this case, the purchase support unit 1548 may also register flag information indicating that the registered product is a recommended product, associating it with the product code, in order to record that the registered product is a recommended product.

[0210] In this way, the purchase support unit 1548 suggests products that can be combined with the product selected by the customer as recommended products. If the customer likes the suggested recommended products, they can register them as products to purchase. The recommendation screen Gh may also be equipped with controls for instructing the customer to try on items, similar to the product screen.

[0211] Furthermore, the purchase support unit 1548 may also use another recommendation method, which is to present recommended products after the customer has tried them on. Here, other recommendation methods will be explained with reference to Figures 21 and 22. In the recommendation methods described below, the customer tries on products corresponding to the product code they have entered, and can choose whether or not to register them based on the results of the try-on.

[0212] Figure 21 shows a screen representing a customer trying on a product (hereinafter also referred to as the "try-on screen"), and is an example of a screen displayed after the operator Ggb in Figure 19 is operated. The try-on screen Gi has a region Gia. Region Gia displays an image of the customer who tried on the product. Specifically, the purchase support unit 1548 displays the image of the customer captured by the imaging unit 143 in region Gia. In Figure 21, the product displayed in region Gga of Figure 19 is shown in the state of trying it on.

[0213] Furthermore, the fitting screen Gi is equipped with operators Gib, Gic, and Gid. Here, operator Gid is used to signal the end of the fitting. When the purchase support unit 1548 receives an operation on operator Gid, it terminates the display of the fitting screen Gi by, for example, returning to the screen shown in Figure 19. Operator Gic is used to signal that an item should be purchased. When the purchase support unit 1548 receives an operation on operator Gic, it executes the product registration process corresponding to the previously entered product code. This allows the customer to choose whether or not to purchase the item based on their appearance while trying it on.

[0214] The operator Gib, like the operator Ggc mentioned above, is an operator used to request the presentation of recommended products. When the purchase support unit 1548 receives an operation on operator Gib, it selects recommended products from the product master 2191 based on additional information of the products displayed in area Gia, that is, the products corresponding to the entered product code (base products). In this case, the purchase support unit 1548 may also select recommended products based on the customer's appearance (wearing appearance) displayed in area Gia. For example, the purchase support unit 1548 extracts physical characteristics such as the customer's height, body shape, and hair color from the try-on image and selects recommended products taking these extracted characteristics into consideration.

[0215] The purchase support unit 1548 then displays a recommendation screen on the front display unit 132, showing product images of the selected recommended products, based on the product information of those products. The displayed recommendation screen may be in the same form as the recommendation screen Gh in Figure 20, or it may be another recommendation screen Gj, as shown in Figure 22, which includes image images of a person wearing the standard product and the recommended product.

[0216] Figure 22 shows another example of a recommendation screen. The recommendation screen Gj has a first area Gja and a second area Gjb. Here, the first area Gja displays image images of a person wearing the standard product and the recommended product. Figure 22 shows an example in which three different recommended products are selected based on the standard product, and for each recommended product, an image image of a person wearing the recommended product and the standard product is displayed.

[0217] The image may be one that has been created in advance for each combination of products sold in the store, or it may be one that has been automatically generated based on a standard product and a recommended product. In the latter case, for example, the recommended product may be virtually superimposed on a previously captured image of the customer using known VR technology, or the basic image and the recommended image may be superimposed on a virtual model.

[0218] In the first area Gja, it is possible to select a desired recommended product based on an image. For example, in the first area Gja, it is possible to select one image from three displayed images by sliding the image in the direction of the arrow in the figure. Specifically, if an image containing the desired recommended product is placed in the center, images of the reference product and the recommended product included in that image will be displayed in the second area Gjb. Figure 22 shows an example in which images of the reference product Gjc (product AAA) and the recommended product Gjd (product BBB) included in the image displayed in the center of the first area Gja are displayed in the second area Gjb.

[0219] Furthermore, customers can instruct the registration process for products by flicking a product displayed in the second area Gjb towards a cart-shaped operator Gje displayed below the second area Gjb. For example, when a standard product Gjc and a recommended product Gjd are both flicked towards the operator Gje, the purchase support unit 1548 executes the registration process for the standard product Gjc and the recommended product Gjd, respectively.

[0220] Furthermore, if another image is centered by a slide operation in the first area Gja, the images of the other recommended products represented in that other image and the reference product will be displayed in the second area Gjb. As described above, it is possible to instruct the registration process from this state, but if the reference product is already registered, it is preferable for the purchase support unit 1548 to add information such as an icon indicating that it is already registered to the image of the reference product and display it.

[0221] Furthermore, if a customer does not like the recommended product, they can return to the screen shown in Figure 19 or the previous screen by, for example, swiping the recommendation screen Gj.

[0222] Furthermore, the recommended products selected by the purchase support unit 1548 are products that the customer has not yet physically held in their hands at that time. In this case, it is anticipated that some customers may request to physically examine the product to check its color and other details. Therefore, for example, when a store product sold within the store is selected as a recommended product, as in this embodiment, the purchase support unit 1548 may provide control to guide the customer to the location where the recommended product is displayed, in response to customer input.

[0223] For example, the purchase support unit 1548 may work in cooperation with the store coordination unit 1547 and the store equipment 20 to display an in-store map showing the location of recommended products on the front display unit 132. Alternatively, the purchase support unit 1548 may work in cooperation with the motion control unit 1544 to guide the customer service robot 10 to the display location of the recommended products. Furthermore, for example, the purchase support unit 1548 may work in cooperation with the store coordination unit 1547 and the store equipment 20 to illuminate electronic shelf labels placed at the display location of recommended products.

[0224] In this embodiment, it is possible to register recommended products, but the system is not limited to this; recommended products may be provided only for reference, and registration may be prohibited.

[0225] Furthermore, while the above example demonstrates that the base product is selected by entering a product code, the method of selecting the base product is not limited to this. For example, the base product may be selected from among the registered products displayed by operating the operator Gfg described later.

[0226] Furthermore, while the above example illustrates a method of selecting recommended products based on a standard product, the system is not limited to this, and may also select recommended products from a state where no product has been selected. In this case, the purchase support unit 1548 may select recommended products based on the purchase history, search history, etc., associated with the user ID of the check-in user. In addition, if the check-in user is not a member, the purchase support unit 1548 may disable the recommendation function, or select recommended products based on popular products in the store, etc.

[0227] Furthermore, when the purchase support unit 1548 receives an operation from the operator Gfg on the screen shown in Figure 19 or the like, it displays, for example, the screen shown in Figure 23 (hereinafter also referred to as the virtual cart screen) on the front display unit 132.

[0228] Figure 23 shows an example of a virtual shopping cart screen. The virtual shopping cart screen Gk has the same controls as the basic operation screen Gf described above. In addition, an area Gka is provided in the center of the virtual shopping cart screen Gk for displaying the product image, product name, price, etc. of each registered product. The purchase support unit 1548 displays the product image, product name, price, etc. of each registered product in area Gka based on the product information of each product registered in the local transaction management table.

[0229] Figure 23 shows the state in which product AAA, described in Figure 19 or Figure 22, and product BBB, a recommended product described in Figure 20 or Figure 22, have been registered. By viewing this virtual cart screen Gk, customers can check the list of products registered using the customer service robot 10.

[0230] Furthermore, the products displayed on the virtual cart screen are not limited to unpaid items; products for which payment has been completed may also be displayed. In this case, it is preferable that the purchase support unit 1548 displays whether or not a product has been paid for based on the presence or absence of a purchased flag. For example, the purchase support unit 1548 may display a mark indicating that a product has been paid for on the product image of a product that has been paid for.

[0231] Below area Gka, area Gkb is provided for displaying the total amount of registered products. The purchase support unit 1548 displays the total amount calculated based on the price of each product registered in the local transaction management table in area Gkb. If the set includes products that have already been settled, it is preferable to display the total amount of unsettled products and the total amount of settled products separately.

[0232] Furthermore, when the operator Gfh is operated on any of the screens described above, the purchase support unit 1548 processes the payment based on the total amount of unpaid items among the registered products. Here, the purchase support unit 1548 may also display a screen for selecting a payment method, such as credit card payment or code payment (the payment method selection screen shown in Figure 25, which will be described later), on the front display unit 132. This allows the purchase support unit 1548 to settle all unpaid items among the registered products at once.

[0233] Furthermore, in the customer service robot 10 of this embodiment, it is also possible to individually process payments for unpaid items by selecting them in area Gka of the virtual cart screen Gk. For example, when the selection operation for item BBB is received in the virtual cart screen Gk shown in Figure 23, the purchase support unit 1548 displays, for example, the screen shown in Figure 24 (hereinafter also referred to as the selected item screen) on the front display unit 132.

[0234] Figure 24 shows an example of the product selection screen. As shown in Figure 24, the product selection screen Gl displays the product image, product name, price, etc., of the product (product BBB) selected on the virtual cart screen Gk. The operator controls Gla, Glb, and Glc are also displayed on the product selection screen Gl.

[0235] Here, operator Gla, like operator Ggc mentioned above, is an operator used to request product recommendations. When the purchase support unit 1548 receives an operation of operator Gla, it uses the selected product as the base product and displays the recommendation screen Gh or recommendation screen Gj mentioned above. Also, operator Glb, like operator Gff mentioned above, is an operator used to make inquiries to store staff. When the purchase support unit 1548 receives an operation of operator Gff, it notifies the store device 20 of the inquiry information, including the current location of its customer service robot 10 and the product code of the selected product, thereby requesting assistance from a store staff member.

[0236] The operator Glc is an operator used to instruct the payment of the selected product. When the purchase support unit 1548 receives an operation on the operator Glc, it processes the payment based on the price of the selected product. The purchase support unit 1548 may also display a screen for selecting a payment method (hereinafter referred to as the payment method selection screen) on the front display unit 132 prior to the payment processing. If a product that has already been paid for is selected, it is preferable for the purchase support unit 1548 to disable or hide the operator Glc to prevent duplicate payment processing.

[0237] Figure 25 shows an example of a payment method selection screen. As shown in Figure 25, the payment method selection screen Gm displays operators Gma, Gmb, Gmc, and Gmd that allow users to select various payment methods. The total amount of the items to be paid for is also displayed on the payment method selection screen Gm.

[0238] Here, operator Gma is an operator for instructing credit card payment. Operator GmbH is an operator for instructing cash payment. Operator Gmc is an operator for instructing electronic money payment. Operator Gmd is an operator for instructing code payment. When one of operators Gma, GmbH, Gmc, or Gmd is selected, the purchase support unit 1548 executes a payment process to settle the total amount of the items to be paid for using the payment method corresponding to the selected operator.

[0239] Furthermore, if the customer service robot 10 is not equipped with an automatic cash payment machine, the operator GmbH that instructs cash payment may be hidden. Also, as described above, if the configuration is such that cash payment is made by an external device such as the store equipment 20, the operator GmbH may be displayed. In this case, the display and hiding of the operator GmbH may be switched depending on the amount of change available in the external device and the usage status of the external device.

[0240] When the purchase support unit 1548 completes the payment processing for a product, it assigns a "purchased" flag to the product code of that product stored in the local transaction management table. The purchase support unit 1548 also sends the record from the local transaction management table relating to the product for which payment processing has been completed, along with the robot ID of its customer service robot 10 and the transaction ID of that transaction, to the server device 30, thereby assigning a "purchased" flag to the transaction information of the corresponding product stored in the transaction management table 3165.

[0241] Furthermore, the purchase support unit 1548 may also notify the store device 20 of information (e.g., product code) regarding products for which payment has been completed. In this case, the control unit 214 of the store device 20 will perform controls such as reducing the inventory quantity of the products for which payment has been completed. In this case, the robot coordination unit 2142 may also notify each of the customer service robots 10 linked to the store device 20 of the product code of the product in question when the inventory quantity of the product falls below a threshold. In addition, when the purchase support unit 1548 of the customer service robot 10 receives information from the store device 20 regarding products whose inventory quantity has fallen below a threshold, it may display the product information and inventory quantity of the relevant product on the front display unit 132 or on the rear display unit 115. This allows the customer service robot 10 to notify the customer operating its own customer service robot 10 and other customers in the store of products with low inventory quantities.

[0242] In this embodiment, the operation of the customer service robot 10 is restricted so that products registered within the store cannot be taken outside the store until payment is completed within the store. Specifically, the purchase support unit 1548 restricts the operation of the customer service robot 10 until payment for the products registered in the store is completed within the store.

[0243] For example, the purchase support unit 1548, in cooperation with the motion control unit 1544, restricts the range in which the customer service robot 10 can move within the store until payment is completed for all registered products, thereby restricting the customer service robot 10 from leaving the store. Alternatively, the purchase support unit 1548 may restrict the customer service robot 10 from leaving the store by disabling the operator Gfc. Furthermore, if an exit gate or the like is provided at the exit of the store to manage customer departures, the purchase support unit 1548 may, in cooperation with the store cooperation unit 1547 and the store equipment 20, take control measures such as blocking the exit gate when it detects a customer moving towards the exit.

[0244] Here, the method for detecting the exit action is not particularly specified. For example, the purchase support unit 1548 may, in cooperation with the motion control unit 1544, detect when a customer moves to the exit as an exit action based on the position information of its own customer service robot 10 that follows the customer. Alternatively, for example, the purchase support unit 1548 may, in cooperation with the motion control unit 1544, detect when a customer moves to the exit as an exit action based on images captured by the imaging unit 143.

[0245] Furthermore, for example, if the purchase support unit 1548 detects that the customer service robot 10 has moved outside the store without payment being made for the products registered in the store, the range in which the customer service robot 10 can move outside the store can be arbitrarily set, but it is preferable that it be within the range in which short-range wireless communication with the store equipment 20 is possible.

[0246] Furthermore, the purchase support unit 1548 may notify store staff or customers themselves if there are unpaid items among the registered items. For example, the purchase support unit 1548 may notify that there are unpaid items by changing the color of the light-emitting unit 141 or by making the light-emitting unit 141 blink. In addition to the presence of unpaid items, if there are other conditions that should be notified, such as low battery, the unit may alternately emit light in the appropriate color for each condition, or it may emit light individually by separating the areas to be illuminated.

[0247] Furthermore, the purchase support unit 1548 may, for example, display the registration and payment status of the product on the rear display unit 115, as shown in Figure 26, to draw the attention of the store staff.

[0248] Figure 26 shows an example of a screen displayed on the rear display unit 115 of the customer service robot 10. As shown in Figure 26, the purchase support unit 1548 displays a screen Gn on the rear display unit 115 that shows the number of unpaid items and the number of items that have been paid for, based on the registration status in the local transaction management table. Here, area Gna is the area where the number of unpaid items is displayed, indicating that 2 items are unpaid. Area Gnb is the area where the number of paid items is displayed, indicating that 1 item has been paid for. Area Gnc is a free display space where various information can be displayed, such as store advertisements or the time elapsed since the customer arrived at the store.

[0249] In this way, by displaying the product registration status and payment status on the rear display unit 115, store staff or employees of commercial facilities can easily grasp the status of transactions, such as whether or not there are any unpaid items.

[0250] Furthermore, if the purchase support unit 1548 detects that the customer service robot 10 has moved out of the store without payment being made for the items registered in the store, or if it detects that the customer is leaving the store, it may notify the customer by voice or display to prompt them to make a payment. Alternatively, the purchase support unit 1548 may be configured to notify the store staff if it detects that the customer service robot 10 has moved out of the store without payment being made for the items registered in the store, or if it detects that the customer is leaving the store.

[0251] Furthermore, when the user arrives at a store specified in the action plan, the operation control unit 1544 sets the "visited" flag in the action plan, which is associated with the store ID of that store, to "visited". The operation control unit 1544 also starts timing the elapsed time at the moment of arrival at the store. When the elapsed time being timed approaches or reaches the time allotted for staying at that store as specified in the action plan, the operation control unit 1544 notifies the customer, either visually or audibly, that it is time to move to the next store.

[0252] For example, in the action plan screen Gd shown in Figure 16, when the elapsed time since arriving at store A reaches the stay time specified in the action plan, the operation control unit 1544 issues a notification prompting the customer to move to the next store B. Upon receiving the notification, the customer can, for example, instruct the customer service robot 10 to move to the next destination store by operating an operator Gfc on the basic operation screen Gf.

[0253] Here, operator Gfc is an operator used to instruct the robot to move to the next destination store specified in the action plan. When the motion control unit 1544 receives an operation from operator Gfc, it switches the customer service robot 10 to lead mode and starts moving to the next destination store specified after the store it is currently staying at.

[0254] Furthermore, the Gfc operator can be operated not only when a notification prompting movement is issued, but also if the elapsed time since arrival at the store is less than the stay time specified in the action plan. In addition, notifications based on stay time can be enabled or disabled, for example, by setting the personalization process. Moreover, at the last destination store specified in the action plan (e.g., store D), the system may be configured not to issue a notification even if the stay time is reached.

[0255] Furthermore, the method for instructing the robot to move to the next destination store is not limited to the operation of the operator Gfc. For example, when the motion control unit 1544 detects the customer leaving the store, it may switch the customer service robot 10 to lead mode and start moving to the next destination store. Alternatively, the robot may be instructed to move to the next destination store by voice command or operation from a paired terminal.

[0256] In this way, under the control of the motion control unit 1544, the customer service robot 10 will move from store to store in the order specified in the action plan, switching between leading mode and following mode.

[0257] By the way, some of the stores specified in the action plan may be located beyond the range of movement of the customer service robot 10. For example, in the action plan shown in Figure 16, the customer service robot 10 will move to store A on the first floor and then to store B on the second floor, so the customer service robot 10 needs to move between floors. In such a case, if the customer service robot 10 is not designed to ride elevators or escalators, the customer service robot 10, which is traveling on the first floor, will not be able to move to store B on the second floor.

[0258] As described above, if the action plan includes stores that cannot be reached by one customer service robot 10, the motion control unit 1544 continues to support the customer's actions by transferring the settings to another customer service robot 10 that can reach the store.

[0259] Specifically, based on the action plan, the motion control unit 1544 determines whether the floor on which its customer service robot 10 is located is the same as the floor on which the destination store is located. If the floors are the same, the motion control unit 1544 guides the customer to the destination store in the lead mode described above.

[0260] Furthermore, if the floors are different, the motion control unit 1544 refers to the robot management table 3163 and searches for other customer service robots 10 that are on the same floor as the destination store and whose status is in standby mode.Then, the motion control unit 1544 transfers various data such as the user ID, user characteristics, user settings, action plan, and local transaction management table of the check-in user held in its own customer service robot 10 to the other customer service robot 10 that was found, and moves the other customer service robot 10 to the location of the transfer point.

[0261] Here, the method of data transfer is not particularly specified. For example, the motion control unit 1544 may directly send data to other customer service robots 10. Alternatively, for example, the motion control unit 1544 may notify other customer service robots 10 of its own robot ID, the user ID of the check-in user, etc., so that the other customer service robots 10 can read the data necessary for the transfer from the various data tables of the server device 30.

[0262] Furthermore, the handover points are, for example, around elevator entrances or escalator entrances, and the motion control unit 1544 instructs the other customer service robot 10 to use the handover point closest to its own position. The motion control unit 1544 then moves in lead mode to the handover point, such as around an elevator or escalator that will be used to get to the floor where the destination store is located, and displays a screen on the front display unit 132 informing the other customer service robot 10 that it will take over customer service on the destination floor.

[0263] Furthermore, if goods or other items are placed on the display stand 112, the operation control unit 1544 may display a screen prompting the customer to move, or a screen instructing them to move to a pick-up counter or the like. In the latter case, upon receiving the instruction to move, the operation control unit 1544 moves the items placed on the display stand 112 to the pick-up counter.

[0264] Meanwhile, the motion control unit 1544 on the other customer service robot 10, upon receiving instructions for a handover point from the customer service robot 10, moves to the instructed handover point while maintaining standby mode. Furthermore, the motion control unit 1544 on the other customer service robot 10 reflects the handover instruction data to its own customer service robot 10, causing, for example, the light-emitting unit 141 to illuminate in a color specified by the user settings.

[0265] The motion control unit 1544 on the other customer service robot 10, upon receiving a check-in operation from a customer who has moved to a different floor, switches its own customer service robot 10 to customer service mode (leading mode) with the transferred data reflected. Furthermore, once the motion control unit 1544 switches to customer service mode, it notifies the original customer service robot 10 that the transfer is complete. Upon receiving the transfer completion notification, the original customer service robot 10 clears various data such as the user ID, user settings, action plan, and local transaction management table held within its own customer service robot 10, and then switches to standby mode. In the case of moving items from a storage unit to a receiving counter, it is preferable that the motion control unit 1544 moves to the destination and then, in response to an operation by an employee, switches to standby mode.

[0266] As a result, even if a customer service robot 10's action plan includes a store that it cannot reach on its own, it can continue to support the customer's actions based on the action plan by coordinating with other customer service robots 10.

[0267] Furthermore, data transfer between customer service robots 10 is not limited to cases where the robots move across floors. For example, if the floors that customer service robots 10 can move to are restricted, the system may be configured to transfer data between customer service robots 10 responsible for each floor. Also, if different customer service robots 10 are responsible for the commercial facility and the parking lot, the system may be configured to transfer data between customer service robots 10 when they move between the commercial facility and the parking lot.

[0268] Furthermore, if a customer service robot 10 is unable to reach its destination store due to physical reasons such as low battery power, the system may be configured to transfer data to a replacement customer service robot 10. In this case, when the battery level of the customer service robot 10 falls below a threshold, the motion control unit 1544 selects another customer service robot 10 located on the same floor as the customer service robot 10, in standby mode, and with a battery level above the threshold, as the data transfer destination. The motion control unit 1544 also instructs the other customer service robot 10 to use the current location or a transfer point set within the range that the customer service robot 10 can move to. This allows customer service robot 10 to continue providing support based on an action plan, even if it runs out of battery power while serving a customer, through cooperation with another customer service robot 10.

[0269] Furthermore, once the motion control unit 1544 has completed moving to all stores specified in the action plan, it terminates customer support based on the action plan, for example, in response to a checkout operation instructed by the customer. After terminating the support, the motion control unit 1544 clears various data held in its customer service robot 10, such as the user ID, user settings, action plan, and local transaction management table, and switches to standby mode. Note that the checkout operation may be performed at any time, not limited to when the movement to all stores specified in the action plan has been completed.

[0270] The customer service robot 10 that has shifted to the standby mode moves to a predetermined position within the commercial facility under the control of, for example, the operation control unit 1544. The predetermined position may be the entrance of the commercial facility where the customer service robots 10 are gathered, or may be a charging area for charging the battery of the customer service robot 10 after use.

[0271] Also, an employee may remotely operate the customer service robot 10 to return it to the predetermined position. In this case, the remote operation to return the customer service robot 10 to the predetermined position may be performed separately for each individual customer service robot 10, or may be an operation to return a plurality of customer service robots 10 to the predetermined position collectively.

[0272] Also, the customer service robot 10 in the standby mode may be configured to move to a designated position according to instructions from the store device 20 or the server device 30. In this case, the instructions from the store device 20 or the server device 30 may be given to each individual customer service robot 10, or may be given to a plurality of customer service robots 10 at once.

[0273] By the way, the goods purchased at each store can be transported to the customer service robot 10 by placing them on the placement table 112 provided in the customer service robot 10. On the other hand, depending on the form of the goods and the intention of the customer, it is also assumed that the purchased goods may not be received on the spot but at another opportunity or location. For example, if the store is a showroom store, the goods in the store are display items, so the actual goods cannot be received on the spot. Also, for example, when there are luggage or other goods placed on the placement table 112 of the customer service robot 10, there may be cases where newly purchased goods cannot be placed on the placement table 112.

[0274] Therefore, the purchase support unit 1548 may cause the front display unit 132 to display a screen on which the method of receiving the goods for which the settlement process has been completed can be selected. For example, as shown in FIG. 27, the purchase support unit 1548 causes the front display unit 132 to display a screen (hereinafter also referred to as a receipt method selection screen) on which the receipt method can be selected.

[0275] Figure 27 shows an example of a screen displayed on the front display unit 132 of the customer service robot 10, and shows an example of a screen for selecting the method of receiving goods. As shown in Figure 27, the receiving method selection screen Go is provided with operators Goa to God as operators for selecting the method of receiving goods.

[0276] The Goa control is used to instruct the device to be sent by mail or other means. The Gob control is used to instruct the device to be picked up at a pickup counter located within the commercial facility. The Goc control is used to instruct the device to be picked up via a locker located within the commercial facility. The God control is used to instruct the device to be transported to the exit of the commercial facility.

[0277] When the purchase support unit 1548 receives an operation from the operator Goa, it displays a screen on the front display unit 132 for entering destination information, such as the shipping address, and prompts the customer to enter the destination. Once the destination is entered, the purchase support unit 1548 generates shipping information that associates the destination with information that can identify the product to be shipped, and sends it to the store device 20 or server device 30. When the store device 20 or server device 30 receives the shipping information from the customer service robot 10, it notifies the terminal of the person in charge of shipping the product or the vendor, and arranges for shipping. As a result, the customer can receive the purchased product at the specified destination.

[0278] Furthermore, if the customer's address is registered in the customer management table in association with the customer's user ID, the purchase support unit 1548 may use the registered address as the destination.

[0279] Furthermore, when the purchase support unit 1548 receives an operation from the operator Gob, it transmits to the store device 20 or server device 30 information that identifies the target product, information that identifies the customer, and destination information (first destination information) specifying the transfer to the pick-up counter. When the store device 20 or server device 30 receives the first destination information from the customer service robot 10, it notifies the store clerk or the terminal in charge of transporting the product to the pick-up counter of the first destination information, thereby arranging the transfer to the pick-up counter. As a result, the customer can pick up the purchased product at a pick-up counter located within the commercial facility.

[0280] If there are multiple pickup counters, the purchase support unit 1548 may, for example, specify the pickup counter closest to the customer's current location and transmit the first pickup destination information. Alternatively, the purchase support unit 1548 may work in cooperation with the operation control unit 1544 to guide the customer to the pickup counter.

[0281] Furthermore, when the purchase support unit 1548 receives an operation from the operator Goc, it transmits information that can identify the target product, information that can identify the customer, and delivery destination information (second delivery destination information) specifying that the product should be transferred to a locker to the store device 20 or server device 30. When the store device 20 or server device 30 receives the second delivery destination information from the customer service robot 10, it notifies the store clerk or the terminal in charge of storing the product in the locker of the second delivery destination information, thereby arranging for the product to be stored in the locker. In addition, when the purchase support unit 1548 obtains information that identifies the locker to which the product will be stored via the store device 20 or server device 30, it notifies the customer by displaying it on the front display unit 132 or by other means. As a result, the customer can pick up the purchased product in the locker where it will be stored.

[0282] If there are multiple lockers, the purchase support unit 1548 may, for example, specify the locker closest to the customer's current location and send the second pickup location information. The purchase support unit 1548 may also work in cooperation with the operation control unit 1544 to guide the customer to the location of the locker. Alternatively, the customer terminal 50 may be notified of the location of the locker by including the customer's phone number or address in the second pickup location information and sending it.

[0283] Furthermore, when the purchase support unit 1548 receives an operation from the operator God, it transmits to the store device 20 or server device 30 information that identifies the target product, information that identifies the customer, and destination information (third destination information) specifying the destination for transport to the exit. When the store device 20 or server device 30 receives the third destination information from the customer service robot 10, it notifies the store clerk or the terminal in charge of transporting the product to the exit, thereby arranging for the product to be transported to the exit. As a result, the customer can pick up the purchased product at the exit of the commercial facility.

[0284] If there are multiple exits, the purchase support unit 1548 may, for example, specify the exit closest to the current location and transmit the third receiving destination information. Alternatively, the purchase support unit 1548 may work in cooperation with the operation control unit 1544 to guide the customer to the receiving destination exit.

[0285] Thus, the customer service robot 10 of this embodiment can hand over the goods to the customer in the manner desired by the customer after payment has been completed.

[0286] Furthermore, when selecting the above-mentioned delivery method, the system may be configured to allow customers to request the inclusion of a paper receipt. In this case, the store employee or other person in charge of transporting the goods will include a paper receipt related to the transaction. This allows customers to receive their purchased goods along with the receipt related to the transaction.

[0287] Furthermore, while the above example uses a pick-up counter, lockers, and exit as locations for receiving goods within a commercial facility, the system is not limited to these, and users may specify any location they wish. For example, the system may allow users to specify their current location or the parking spot of their vehicle.

[0288] For example, when specifying a parking location, the purchase support unit 1548 displays a screen on the front display unit 132 for the customer to input the vehicle registration number of the parked vehicle. The purchase support unit 1548 identifies the parking location corresponding to the entered vehicle registration number based on the relationship between the vehicle registration number managed by the vehicle system via the server device 30, etc., and the parking location. The purchase support unit 1548 then requests transport to the parking location by transmitting third-party delivery information specifying the identified parking location. This allows the customer to receive the purchased goods at the vehicle's parking location. The purchase support unit 1548 may also work with the operation control unit 1544 to guide the customer to the parking location. Furthermore, if the vehicle registration number is registered in association with the customer's user ID, the parking location may be identified using that vehicle registration number.

[0289] Furthermore, while the above example assumes that the goods will be transported to the pick-up location by staff such as store employees, this is not limited to this, and the customer service robot 10 may also transport the goods.

[0290] For example, in a customer service robot 10 that has goods loaded onto a display stand 112, when a checkout operation is performed, the motion control unit 1544 may be configured to move to a previously designated handover location within the commercial facility, thereby handling the transfer of the goods.

[0291] Furthermore, for example, a store device 20 or server device 30 that has received a designated pick-up location within a commercial facility may use the customer service robot 10 as a means of transport by calling the customer service robot 10, which is in a standby state, back to the store or other location from which it was transported, and then instructing it to move to the designated pick-up location.

[0292] In addition, the customer service robot 10 operates in a post - closing mode different from the above - described operation modes outside business hours such as after the business hours of a commercial facility. Specifically, when the current date and time reaches outside the business hours of the commercial facility, the operation control unit 1544 shifts the customer service robot 10 to the post - closing mode.

[0293] The customer service robot 10 in the post - closing mode performs operations different from the above - described standby mode and customer service mode. For example, the operation control unit 1544 makes it travel within the commercial facility along a predetermined route and uses the imaging unit 143 to image the surrounding environment, thereby performing a patrol operation of the commercial facility and the stores.

[0294] Also, for example, the customer service robot 10 may be configured to assist in the inventory - taking operation in a preset store. In this case, for example, the operation control unit 1544 operates the reader - writer unit 157 while traveling within the store to read the product code and individual item code from the wireless tags of the products existing in the store. Then, the operation control unit 1544 totals the number of products for each type based on the reading results and transmits the inventory - taking results to the store device 20, etc.

[0295] When the customer service robot 10 is set to the post - closing mode, for example, after the end of the patrol operation, all the customer service robots 10 may be collectively moved to a predetermined position automatically or by the operation of a store clerk or the like.

[0296] Hereinafter, an example of the processing performed by the above - described customer service robot 10 will be described.

[0297] FIG. 28 is a flowchart showing an example of the main processing performed by the customer service robot 10 of the present embodiment. It is assumed that the customer service robot 10 is in the standby mode as a premise of this processing (step S11).

[0298] First, the motion control unit 1544 waits for a customer to check in by displaying a check-in screen (see Figure 13) or the like on the front display unit 132. When the motion control unit 1544 receives a customer's check-in request, it executes the check-in process (step S12) and switches the customer service robot 10 into customer service mode (step S13).

[0299] In customer service mode, the personalization processing unit 1545 performs personalization processing in response to customer operations (step S14). The action plan generation unit 1546 interacts with the customer via the visit purpose confirmation screen (see Figures 14 and 15) and performs action plan generation processing to generate an action plan indicating the destination store (destination store) (step S15). Although Figure 28 shows an example where personalization processing is performed before action plan generation processing, the timing of personalization processing is not limited to this and can be performed at any time during customer service mode.

[0300] Next, when the motion control unit 1544 receives an operation to instruct the customer service robot 10 to start moving to the destination store based on the action plan generated in step S15, it switches the customer service robot 10 to lead mode (step S16).

[0301] Next, the motion control unit 1544 determines whether its customer service robot 10 can reach the first destination store specified in the action plan (step S17). For example, the motion control unit 1544 determines that it can reach the store if the floor number of its customer service robot 10 and the floor number of the destination store are the same, and that it cannot reach the store if the floor numbers are different. Also, for example, the motion control unit 1544 determines that it cannot reach the store if the distance that its customer service robot 10 can travel with its remaining battery power is less than the distance to the destination store.

[0302] If it is determined in step S17 that the robot can move (step S17; Yes), the motion control unit 1544 moves the customer service robot 10 to the destination store (step S18). If the customer service robot 10 has not yet arrived at the destination store (step S19; No), the motion control unit 1544 returns to step S17. This ensures that even if the customer service robot 10 becomes unable to reach the destination store due to unforeseen circumstances after starting to move to the destination store, it can hand over to another customer service robot 10.

[0303] Next, when the destination store is reached (step S19; Yes), the motion control unit 1544 switches the customer service robot 10 to follow mode (step S20). Then, the store coordination unit 1547 performs store coordination processing to coordinate with the store equipment 20 (step S21). In addition, the purchase support unit 1548 performs purchase support processing to assist in the purchase of goods (step S22).

[0304] Next, when the customer service robot 10 leaves the store due to customer operation or other reasons, the motion control unit 1544 determines whether or not it has visited all the stores specified in the action plan (step S23). Here, for example, when the motion control unit 1544 receives a checkout operation, it determines that it has visited all the stores. If it determines that it has visited all the stores (step S23; Yes), the motion control unit 1544 proceeds to step S27.

[0305] On the other hand, if it is determined that there are stores that have not been visited (step S23; No), the motion control unit 1544 returns to step S16 to switch the customer service robot 10 to lead mode. Next, in step S17, the motion control unit 1544 determines whether it is possible to reach the next destination store, and if it is determined that it is not possible to reach it (step S17; No), it proceeds to step S24.

[0306] In step S24, the motion control unit 1544 searches the robot management table 3163 for other customer service robots 10 that can reach the destination store. Next, the motion control unit 1544 transfers various data such as the user ID, user characteristics, user settings, action plan, and local transaction management table held by its own customer service robot 10 to the other customer service robot 10, and moves the other customer service robot 10 to the transfer point location (step S24).

[0307] Next, the motion control unit 1544 moves in lead mode to the handover point (step S25). At this point, the motion control unit 1544 displays a screen on the front display unit 132, etc., informing the customer that another customer service robot 10 will take over the customer service. Then, the motion control unit 1544 waits until it is notified that the handover is complete from the other customer service robot 10 (step S26; No), and when it is notified that the handover is complete (step S26; Yes), it proceeds to step S27. The motion control unit 1544 of the other customer service robot 10 continues to support the customer's actions based on the action plan by performing the processing that proceeds to step S16 based on the data it has taken over.

[0308] In the following step S27, the motion control unit 1544 clears the various data held by its customer service robot 10 and switches it to standby mode (step S27). Then, the motion control unit 1544 moves to a predetermined location within the commercial facility (step S28) and terminates this process.

[0309] Next, we will explain the various processes performed in the main process described above.

[0310] First, let's explain the check-in process performed in step S12 of Figure 28. Figure 29 is a flowchart showing an example of the check-in process performed by the customer service robot 10.

[0311] The operation control unit 1544 displays the check-in screen on the front display unit 132 (step S121). Next, the operation control unit 1544 waits until a check-in operation is performed (step S122; No → step S123; No). At this point, when the operation control unit 1544 receives input of a user ID (step S122; Yes), it compares it with the user ID registered in the user management table 3164 (step S124) to determine whether or not the user is a legitimate member (step S125).

[0312] In step S125, if the entered user ID is not registered in the user management table 3164 (step S125; No), the operation control unit 1544 determines that a check-in operation by a non-member has been accepted (step S126), and proceeds to step S13 in Figure 28. Also, in step S123, if a touch operation on the check-in screen is accepted (step S123; Yes), the operation control unit 1544 determines that a check-in operation by a non-member has been accepted (step S126), and proceeds to step S13 in Figure 28.

[0313] Furthermore, if a check-in operation is accepted by a non-member, the operation control unit 1544 may display a message to that effect on the front display unit 132, or a message prompting member registration on the front display unit 132.

[0314] On the other hand, if the entered user ID is registered in the user management table 3164 in step S125 (step S125; Yes), the operation control unit 1544 determines that it has accepted the check-in operation by the member (step S127) and proceeds to step S13 in Figure 28.

[0315] Furthermore, when a member checks in, the motion control unit 1544 stores the entered user ID and customer user characteristics in the robot management table 3163, associating them with the robot ID of its own customer service robot 10. In addition, after receiving a check-in operation from a member or non-member, the motion control unit 1544 may perform pairing with a pairing terminal such as a customer terminal 50.

[0316] Next, with reference to Figure 30, the personalization process performed in step S14 of Figure 28 will be described. Figure 30 is a flowchart showing an example of the personalization process performed by the customer service robot 10.

[0317] First, the personalization processing unit 1545 determines whether the customer (check-in user) who checked in with the customer service robot 10 is a member or not (step S141). If it is determined that the check-in user is a member who entered a valid user ID (step S141; Yes), the personalization processing unit 1545 refers to the user management table 3164 and determines whether an existing user setting associated with the user ID exists or not (step S142).

[0318] If no existing user settings exist, the personalization processing unit 1545 proceeds to step S144. If existing user settings exist, the personalization processing unit 1545 confirms with the check-in user whether or not to use the existing user settings and waits for instructions from the check-in user (step S143). For example, the personalization processing unit 1545 confirms with the check-in user whether or not to use the existing user settings by displaying a screen on the front display unit 132.

[0319] If you choose to use existing user settings (step S143; Yes), proceed to step S147 to reflect the changes specified in the user settings. If you choose not to use existing user settings, proceed to step S144.

[0320] In step S144, the personalization processing unit 1545 determines whether or not it has received a customization operation from the check-in user to change the settings of the customer service robot 10 (step S144). For example, the personalization processing unit 1545 displays on the front display unit 132 a screen that allows the user to change the light color of the light-emitting unit 141 or a screen that allows the user to change various settings related to the operation of the customer service robot 10, and accepts the customer's customization operation. If no customization operation is performed (step S144; No), the personalization processing unit 1545 terminates this process and proceeds to step S15 in Figure 28.

[0321] Furthermore, if a customization operation is accepted in step S144 (step S144; Yes), the personalization processing unit 1545 stores the modified settings as user settings, associates them with the user ID of the checked-in user, and stores them in the user management table 3164 (step S145). Next, the personalization processing unit 1545 proceeds to step S147 to reflect the modified settings.

[0322] On the other hand, if in step S141 it is determined that the check-in user is not a member (step S141; No), the personalization processing unit 1545 determines whether or not it has received a customization operation from the check-in user to change the settings of the customer service robot 10 (step S146). Here, the personalization processing unit 1545 may accept the customization operation by displaying a screen similar to that in step S144, or it may accept the customization operation by displaying a screen for non-members that is different from the one for members. For example, the screen for non-members may have a limited number of changeable settings compared to the screen for members.

[0323] If no customization operation is performed in step S146 (step S146; No), the personalization processing unit 1545 terminates this process and proceeds to step S15 in Figure 28. If a customization operation is accepted (step S146; Yes), the personalization processing unit 1545 proceeds to step S147 to reflect the changed settings.

[0324] In step S147, the personalization processing unit 1545 controls the operation of the customer service robot 10 based on the changed settings to reflect the changed settings, and then proceeds to step S15 in Figure 28.

[0325] The personalization processing unit 1545 stores the changed settings as user settings in the storage unit 161, etc., but it may also store them in the robot management table 3163 in association with the robot ID of its own customer service robot 10. Furthermore, if pairing with the customer terminal 50 has been established, the personalization processing unit 1545 may provide the user settings to the customer terminal 50.

[0326] Next, with reference to Figure 31, the action plan generation process performed in step S15 of Figure 28 will be explained. Figure 31 is a flowchart showing an example of the action plan generation process performed by the customer service robot 10.

[0327] First, the action plan generation unit 1546 displays the purpose of visit screen on the front display unit 132 (step S151). Here, the purpose of visit confirmation screen displays options to confirm the customer's purpose of visit, as explained in Figures 14 and 15. The purpose of visit confirmation screen displayed initially displays general purposes of visit as options, such as "I want to buy," "I want to play," or "I want to eat."

[0328] Next, the action plan generation unit 1546 determines whether or not a purpose of visit has been selected based on the check-in user's actions (step S152). If no purpose of visit is selected (step S152; No), the process proceeds to step S156.

[0329] When the action plan generation unit 1546 receives the selection of the purpose of visit (step S152; Yes), it determines whether it is possible to narrow down the destination stores based on the selected purpose of visit (step S153). For example, if the number of destination stores derived from the selected purpose of visit is less than or equal to a threshold (e.g., 3), the action plan generation unit 1546 determines that it is possible to narrow down the destination stores, and if it exceeds the threshold, it determines that it is not possible to narrow down the destination stores.

[0330] If it is not possible to narrow down the destination store (step S153; No), the action plan generation unit 1546 updates the options to allow for a more detailed confirmation of the purpose of visit based on the purpose of visit selected in step S152 (step S154), and returns to step S151. As a result, the purpose of visit confirmation screen including the updated options is displayed on the front display unit 132. The action plan generation unit 1546 also repeatedly executes the processes from steps S151 to S154 until it becomes possible to narrow down the destination store. The updated options may include selecting the type of product, the product itself, or the store itself.

[0331] Furthermore, if it is possible to narrow down the destination stores (step S153; Yes), the action plan generation unit 1546 determines the stores derived by the narrowing down as destination stores (step S155) and proceeds to step S156. At this time, the action plan generation unit 1546 may display a list of destination stores that have been determined so far.

[0332] Next, the action plan generation unit 1546 determines whether or not it has received an operation from the check-in user to confirm the destination store that has been decided so far (step S156). If no confirmation operation is performed (step S156; No), the action plan generation unit 1546 returns to step S151 and displays the store visit purpose confirmation screen. In this case, the action plan generation unit 1546 may display a store visit purpose confirmation screen that includes a general purpose of visit as an option, similar to the store visit purpose confirmation screen displayed initially.

[0333] Furthermore, when the action plan generation unit 1546 receives a confirmation operation (step S156; Yes), it generates an action plan that specifies the order in which to visit the destination stores based on the destination stores that have been determined so far (step S157). Then, the action plan generation unit 1546 displays the generated action plan on the front display unit 132 (step S158) and proceeds to step S16 in Figure 28.

[0334] Furthermore, if the confirmation operation is accepted without the destination store being determined, it is preferable for the action plan generation unit 1546 to display a message such as "Destination store not set" on the front display unit 132 and return the process to step S151. In addition, the customer can set tasks for the destination store specified in the action plan, such as notifying the display location of the type or product selected on the store visit purpose selection screen.

[0335] Next, with reference to Figure 32, the store coordination process performed in step S21 of Figure 28 will be described. Figure 32 is a flowchart showing an example of the store coordination process performed by the customer service robot 10 and the store equipment 20. As a prerequisite for this process, the product master 2191 of the store equipment 20 is assumed to store information that identifies the display location of a product and the electronic shelf label placed at that display location, associated with the product code.

[0336] When the customer service robot 10 arrives at the destination store, the store coordination unit 1547 accesses the store equipment 20 installed in that store and executes a process to establish communication with the store equipment 20. Also, when the robot coordination unit 2142 of the store equipment 20 receives an access request from the customer service robot 10, it executes a process to establish communication with the customer service robot 10 that initiated the access. Through this process, coordination is achieved between the customer service robot 10 and the store equipment 20 (steps S211, S31).

[0337] When the store linkage unit 1547 establishes linkage with the store device 20, it determines whether a task has been set for that store as defined in the action plan (step S212). If no task has been set (step S212; No), the system proceeds to step S22 in Figure 28.

[0338] Furthermore, if a task is set (step S212; Yes), the store linkage unit 1547 executes processing according to the task settings. For example, if a task is set to notify the display location of a product type or product selected on the store visit purpose selection screen, the store linkage unit 1547 refers to the product master 2191 and determines the product type or product to be notified at that store (step S213). Next, the store linkage unit 1547 sends a light emission instruction specifying the determined product type or product (product code) to the store device 20 (step S214), and proceeds to step S22 in Figure 28.

[0339] Meanwhile, the robot coordination unit 2142 of the store device 20 waits until it receives instructions from the customer service robot 10 based on a task (in this example, an instruction to light up), and if there are no instructions (step S32; No), it terminates processing. Also, when the robot coordination unit 2142 receives an instruction to light up from the customer service robot 10 (step S32; Yes), it identifies the display location of the instructed product from the product master 2191 (step S33). Then, the robot coordination unit 2142 lights up the electronic shelf label placed at the identified display location (step S34) and terminates processing.

[0340] This allows customers visiting a store to easily find the display location of the product they have chosen. Alternatively, the store coordination unit 1547 may identify the display location of the product to be notified from the product master 2191 and transmit the identified display location as a light emission instruction to the store device 20.

[0341] Next, with reference to Figure 33, the purchase support process performed in step S22 of Figure 28 will be described. Figure 33 is a flowchart showing an example of the purchase support process performed by the customer service robot 10.

[0342] When the customer service robot 10 reaches the destination store, the purchase support unit 1548 prompts the customer to enter a product code by displaying the basic operation screen (see Figure 18) etc. on the front display unit 132.

[0343] When a customer enters a product code (Step S2201; Yes), the purchase support unit 1548 reads the product information associated with the product code from the product master 2191 and displays a product screen (see Figure 19) showing the product corresponding to that product code on the front display unit 132 (Step S2202). Next, the purchase support unit 1548 determines whether the customer has instructed the customer to try on the product corresponding to the entered product code (Step S2203). If the customer has not instructed the customer to try on the product (Step S2203; No), the unit proceeds to Step S2209.

[0344] Furthermore, if the customer instructs to try on the product in step S2203 (step S2203; Yes), the purchase support unit 1548 displays a try-on screen (see, for example, Figure 21) on the front display unit 132 representing the customer who tried on the product corresponding to the product code (step S2204). Next, the purchase support unit 1548 determines whether or not the customer has requested the presentation of recommended products (step S2205).

[0345] If no recommended products are requested (step S2205; No), the process proceeds to step S2208. In this case, the purchase support unit 1548 determines in step S2208 whether or not the customer has instructed the registration of the product corresponding to the entered product code (step S2208).

[0346] If registration is not instructed (step S2207; No), the purchase support unit 1548 returns to step S2201. If registration is instructed (step S2208; Yes), the purchase support unit 1548 registers the product corresponding to the entered product code (step S2209) and returns to step S2201. In addition, the purchase support unit 1548 may, in cooperation with the store linkage unit 1547, etc., perform control to illuminate the electronic shelf labels placed at the display location of the recommended products when step S2207 or step S2208 is executed.

[0347] Furthermore, in step S2209, the purchase support unit 1548 may notify the store equipment 20 of the store selling the product of information (e.g., product code) regarding the product to be registered. In this case, for example, the control unit 214 of the store equipment 20 may perform control to reduce the inventory quantity of the product when it is notified of the product registration. Alternatively, the control unit 214 of the store equipment 20 may send a notification to a store employee's terminal, etc., when it is notified of the product registration, such as reserving the product.

[0348] Furthermore, if the customer requests the presentation of recommended products in step S2205 (step S2205; Yes), the purchase support unit 1548 selects recommended products from the products registered in the product master 2191 based on the product corresponding to the entered product code (reference product) (step S2206). Next, the purchase support unit 1548 displays a recommendation screen (see, for example, Figure 22) showing the recommended products on the front display unit 132 (step S2207) and proceeds to step S2208. In this case, the purchase support unit 1548 determines in step S2208 whether or not the customer has requested the registration of the recommended products (step S2208).

[0349] If registration is not instructed (step S2208; No), the purchase support unit 1548 returns to step S2201. If registration is instructed (step S2208; Yes), the purchase support unit 1548 registers the recommended product (step S2209) and returns to step S2201.

[0350] In this process, if product registration is not instructed (step S2208; No), and if product registration is performed (step S2209), the process returns to step S2201. However, the process is not limited to these cases; it may also proceed to step S2226.

[0351] Furthermore, if no product code is entered in step S2201 (step S2201; No), the purchase support unit 1548 determines whether the customer has instructed the display of the virtual cart (step S2210). If the customer has instructed the display of the virtual cart (step S2210; Yes), the purchase support unit 1548 displays a virtual cart screen (see, for example, Figure 23) listing the products registered so far (registered products) on the front display unit 132 (step S2211). Next, the purchase support unit 1548 determines whether the customer has requested to select a specific product from the registered products (step S2212).

[0352] If, for example, the user exits the virtual shopping cart screen, the purchase support unit 1548 determines that no product selection will be made (step S2212; No). In this case, the purchase support unit 1548 returns to the basic operation screen or the previous screen, and then proceeds to step S2217.

[0353] Furthermore, in step S2212, when the product selection operation is accepted (step S2212; Yes), the purchase support unit 1548 displays a selected product screen (see, for example, Figure 24) representing the selected product on the front display unit 132 (step S2213).

[0354] Next, the purchase support unit 1548 determines whether or not it has received an operation from the customer requesting the presentation of recommended products (step S2214). If the presentation of recommended products is requested (step S2214; Yes), the purchase support unit 1548 proceeds to step S2206 to select recommended products based on the product (reference product) selected in step S2212. If the presentation of recommended products is not requested (step S2214; No), the purchase support unit 1548 determines whether or not it has received an operation from the customer requesting to inquire with a store clerk (step S2215).

[0355] If a request for assistance from a store employee is made (step S2215; Yes), the purchase support unit 1548 proceeds to step S2225 to make an inquiry regarding the selected product. Specifically, the purchase support unit 1548 transmits inquiry information to the store device 20, including information specifying the product selected in step S2212 and the location of its own customer service robot 10 (step S2225), and then proceeds to step S2226.

[0356] Furthermore, if no inquiry to a store employee is requested in step S2215 (step S2215; No), the purchase support unit 1548 determines whether or not the customer has instructed the customer to make a payment (step S2216).

[0357] If the user is instructed to make a payment (step S2216; Yes), the purchase support unit 1548 proceeds to step S2218 to execute the payment processing for the selected product. Specifically, the purchase support unit 1548 displays a payment method selection screen (see, for example, Figure 25) on the front display unit 132, where the user can select a payment method (step S2218). Next, when the purchase support unit 1548 receives the payment method selection operation (step S2219), it executes the payment processing for the product selected in step S2212 using the selected payment method (step S2220), and then proceeds to step S2221.

[0358] Furthermore, in step S2220, the purchase support unit 1548 may notify the store equipment 20 of the store selling the product of information (e.g., product code) regarding the product subject to payment. In this case, for example, the control unit 214 of the store equipment 20 may perform control to reduce the inventory quantity of the paid-for product. The control unit 214 of the store equipment 20 may also send a notification to a store employee's terminal, such as that the paid-for product has been reserved.

[0359] If the customer does not instruct the payment to be made in step S2216 (step S2216; No), the purchase support unit 1548 proceeds to step S2226.

[0360] On the other hand, if the virtual cart is not instructed to be displayed in step S2210 (step S2210; No), the purchase support unit 1548 determines whether or not the customer has instructed the customer to make a payment (step S2217).

[0361] If the user is instructed to make a payment (step S2217; Yes), the purchase support unit 1548 displays a payment method selection screen (see, for example, Figure 25) on the front display unit 132, allowing the user to select a payment method (step S2218). Upon receiving the payment method selection operation (step S2219), the purchase support unit 1548 executes the payment process for all unpaid registered products using the selected payment method (step S2220), and then proceeds to step S21.

[0362] Next, the purchase support unit 1548 determines whether or not it has received an instruction from the customer to select a method of receiving the goods (step S2221). If no selection of a receiving method is given (step S2221; No), the purchase support unit 1548 proceeds to step S2226.

[0363] Furthermore, when instructed to select a delivery method (step S2221; Yes), the purchase support unit 1548 displays a delivery method selection screen (see, for example, Figure 27) on the front display unit 132, allowing the customer to select how to receive the goods (step S2222). Once a delivery method is selected from the delivery method selection screen, the purchase support unit 1548 arranges for the delivery of the goods by transmitting the delivery destination information generated based on the selected delivery method to the store device 20 or server device 30 (step S2223), and then proceeds to step S2226.

[0364] On the other hand, if payment is not instructed in step S2217 (step S2217; No), the purchase support unit 1548 determines whether or not the customer has requested to contact a store employee (step S2224). If no inquiry to a store employee is requested (step S2224; No), the purchase support unit 1548 proceeds to step S2226.

[0365] Furthermore, if a request for assistance from a store employee is made (step S2224; Yes), the purchase support unit 1548 transmits inquiry information, including the location of its own customer service robot 10, to the store device 20 (step S2225), and proceeds to step S2226.

[0366] Furthermore, the store device 20, upon receiving the inquiry information, for example, through the control of the robot coordination unit 2142, notifies the store employee of the location of the customer service robot 10, etc., via a terminal held by the employee, thereby prompting the employee to respond to the customer.

[0367] In step S2226, the purchase support unit 1548 determines whether or not the customer has instructed the customer to leave the store (step S2226). For example, the purchase support unit 1548 may accept an operation to instruct the customer to move to the next store as an operation to instruct the customer to leave the store. Alternatively, for example, the purchase support unit 1548 may, in cooperation with the operation control unit 1544, determine that the customer has been instructed to leave the store when it is detected that the customer has moved to the exit.

[0368] If the customer is not instructed to leave the store (step S2226; No), the purchase support unit 1548 returns to step S2201. If the customer is instructed to leave the store (step S2226; Yes), the purchase support unit 1548 determines whether payment processing has been completed for all registered products (step S2227).

[0369] If there are unpaid items (step S2227; No), the purchase support unit 1548 displays an alert message on the front display unit 132 indicating that there are unpaid items (step S2228), and returns to step S2201. In step S2228, the purchase support unit 1548 may also display the alert message on the rear display unit 115. The purchase support unit 1548 may also provide notification by the color of the light emitted by the light-emitting unit 141 or by outputting sound. Furthermore, the purchase support unit 1548 may work in cooperation with the motion control unit 1544 to restrict the range in which the customer service robot 10 can move or to stop its movement.

[0370] Furthermore, if all registered items have been paid for (step S2227; Yes), the purchase support unit 1548 proceeds to step S23 in Figure 28.

[0371] In this process, the store linkage unit 1547 stores the record in the local transaction management table relating to the transaction of a product in the transaction management table 3165, associating it with the robot ID of its own customer service robot 10, each time it registers and settles a product. However, this configuration is not limited to this. For example, the store linkage unit 1547 may store the record in the local transaction management table relating to the transaction that took place at the store in the transaction management table 3165 when it moves to step S23.

[0372] Furthermore, the store linkage unit 1547 may perform a process to disconnect from the store device 20 when it moves to step S23.

[0373] As described above, the customer service robot 10 of the above embodiment assists customer behavior in a commercial facility with multiple stores, either leading or following the customer. Specifically, the customer service robot 10 interacts with the customer through a screen confirming the purpose of visit, deriving destination stores according to the customer's purpose of visit and preferences, and generating an action plan that defines the order in which the destination stores should be visited. The customer service robot 10 then moves in leading mode to each destination store in the order defined in the action plan. As a result, the customer service robot 10 can efficiently guide the customer to a store that best suits the customer's needs from among the stores located within the commercial facility.

[0374] Furthermore, the customer service robot 10 moves within the destination store in a follow-me mode, assisting the customer with purchasing products. This allows the customer service robot 10 to provide the customer with an environment where they can register products and make payments at their destinations within the store.

[0375] Furthermore, the customer service robot 10 provides customer support, such as suggesting recommended products, upon request from the customer within the store at the destination. The customer service robot 10 also selects recommended products based on the products the customer has chosen and the customer's appearance when trying on those products. As a result, the customer service robot 10 can present customers with recommended products based on their preferences and body type, thereby efficiently assisting them in purchasing products.

[0376] The embodiments described above can also be modified and implemented as appropriate by changing some of the configurations or functions of each of the devices described above. Therefore, several modifications of the embodiments described above will be described below as other embodiments. In the following, we will mainly describe the differences from the embodiments described above, and will omit detailed explanations of points that are common with what has already been described. Furthermore, the modifications described below may be implemented individually or in combination as appropriate.

[0377] [Example 1] In the above-described embodiment, once products are registered in the store, the operation of the customer service robot 10 is restricted until payment for all registered products is completed, thereby preventing unpaid products from being taken out of the store. However, the embodiment is not limited to this one.

[0378] For example, some customers visiting a shopping mall may have a shopping style where they visit multiple stores, compare products, and then decide which items to purchase. Others may prioritize purchasing items they want to buy first, and then decide whether or not to purchase lower-priority items after browsing various stores. For customers with these shopping styles, a system where they cannot leave the store until payment for all registered items is completed, as in the above-mentioned implementation, may be perceived as lacking flexibility and convenience. It could also lead to lost sales opportunities.

[0379] Therefore, in this modified example, we will describe a configuration of a customer service robot 10 that allows payment to be made at any time inside or outside the store while the customer service robot 10 is providing customer service.

[0380] In this modified configuration, the purchase support unit 1548 of the customer service robot 10 functions as a registration means, reception means, payment means, and recommendation means, as well as an example of a reception means. Specifically, the purchase support unit 1548 accepts the selection of products to be paid for at the store from among the products registered at the store, and performs payment for the selected products.

[0381] Furthermore, even if there are unpaid items when the customer leaves the store, the purchase support unit 1548 does not restrict the operation of the customer service robot 10 and allows it to move outside the store, such as to the next store.

[0382] In this modified version, products registered at the store will not be taken outside the store, but will be delivered to the customer via mail or at a designated pick-up counter as specified at the time of payment. This does not apply to products for which payment has already been completed at the store.

[0383] For example, store-bought items purchased at a store may be handed over to the customer at the store after payment. Furthermore, items purchased at a store but not available for pickup at that store (hereinafter referred to as "temporary items") will be delivered to the customer by mail or at a designated pickup counter as specified at the time of payment. Examples of temporary items include items displayed in showroom stores (display items). Additionally, items that are not in stock at the store but are presented as recommended items, or items registered at one store but purchased at another store, will also be considered temporary items that cannot be received on the spot.

[0384] Furthermore, the purchase support unit 1548 can process payments for unpaid registered items at any time in response to customer requests, while assisting the customer, that is, until the checkout process is completed. In this case as well, the purchase support unit 1548 can accept the selection of items to be paid for and process the payment for the selected items. This allows customers to visit multiple stores and then decide which items to purchase (pay for) by comparing the items they have registered at each store.

[0385] Furthermore, after the payment for any outstanding items is processed, the Purchase Support Unit 1548 accepts the customer's request for a delivery method and arranges for the items to be delivered using the specified method. This allows the customer to receive the purchased (paid-for) items using the specified delivery method.

[0386] Furthermore, if there are unpaid items when the purchase support unit 1548 receives a checkout operation, it may, in cooperation with the operation control unit 1544, maintain the operating mode of the customer service robot 10 and notify the customer by voice or display that there are unpaid items. Alternatively, even if there are unpaid items when the checkout operation is received, the system may be configured so that no notification is given, and the registered items are cleared along with other data by the control of the operation control unit 1544.

[0387] The following describes an example of the processing performed by the purchase support unit 1548 of this modified version, with reference to Figures 34 to 38. First, with reference to Figure 34, the purchase support processing performed by the purchase support unit 1548 of this modified version in step S21 of Figure 28 will be described.

[0388] Figure 34 is a flowchart showing an example of the purchase support process performed by the customer service robot 10 in Modification Example 1. Note that the processes in steps S4201 to S4209 are the same as steps S2201 to S2209 in Figure 33, so their explanation is omitted.

[0389] In step S4209, the purchase support unit 1548 registers a product corresponding to the entered product code, and then displays a payment confirmation screen on the front display unit 132 to confirm whether or not to proceed with payment for that product (step S4210).

[0390] Here, Figure 35 shows an example of a screen displayed on the front display unit 132 of the customer service robot 10, and shows an example of a payment confirmation screen. The payment confirmation screen Gp is ​​an example of a first selection screen.

[0391] As shown in Figure 35, the payment confirmation screen Gp has a first area Gpa and a second area Gpb, dividing the screen into two parts. A circular operator Gpc, which displays the product image of the registered product, is placed at the boundary between the first area Gpa and the second area Gpb.

[0392] On the payment confirmation screen Gp, the operator Gpc can be dragged within the screen. The first area Gpa at the top of the screen is for indicating an intention to make a payment. When the purchase support unit 1548 detects that the operator Gpc has been dragged into the first area Gpa, it determines that an instruction to make a payment has been given. The second area Gpb at the bottom of the screen is for indicating an intention not to make a payment. When the purchase support unit 1548 detects that the operator Gpc has been dragged into the second area Gpb, it determines that an instruction not to make a payment has been given.

[0393] The screen layout of the payment confirmation screen Gp is ​​not limited to this. For example, the configuration may be such that the user is instructed whether or not to make a payment by touch operation on the first area Gpa or the second area Gpb without displaying the operator Gpc. Alternatively, the configuration may be such that information about the corresponding product is displayed in association with the operator Gpc, for example, as with the operator Gqc on the payment target selection screen Gq described later. It is also preferable to allow the user to configure whether or not to display the payment confirmation screen Gp each time a product is registered. For example, the setting of whether or not to display the payment confirmation screen Gp may be made possible by personalization processing.

[0394] Returning to Figure 34, the purchase support unit 1548 determines, based on the payment confirmation screen, whether or not payment has been instructed (step S4211). If the purchase support unit 1548 determines that payment has not been instructed (step S4211; No), it returns to step S4201. Note that the processing in steps S4212 to S4218 is the same as the processing in steps S2210 to S2216 explained in Figure 33, so the explanation is omitted.

[0395] Furthermore, if the purchase support unit 1548 determines that payment has been instructed in step S4211 (step S4211; Yes), it displays a payment method selection screen (see, for example, Figure 25) for the registered product on the front display unit 132 in step S4209 (step S4222). Note that the processing in steps S4222 to S4229 is the same as the processing in steps S2218 to S2225 explained in Figure 33, so the explanation is omitted.

[0396] Furthermore, if the purchase support unit 1548 determines in step S4219 that it has been instructed to make a payment (step S4219; Yes), it displays a payment target selection screen on the front display unit 132, which allows the user to select the product to be paid for from among the registered unpaid products (step S4220).

[0397] Figure 36 shows an example of a screen displayed on the front display unit 132 of the customer service robot 10, and shows an example of a payment target selection screen. The payment target selection screen Gq is an example of a second selection screen.

[0398] As shown in Figure 36, the payment target selection screen Gq has a first area Gqa and a second area Gqb, which divide the screen into two parts. In addition, the payment target selection screen Gq displays a circular operator Gqc that represents the product image of the registered unpaid product.

[0399] In the initial state when the payment selection screen Gq is displayed, the operator Gqc is assumed to be located in the second area Gqb. Furthermore, the operator Gqc will display not only products registered at the store the user is currently visiting, but also unpaid products registered at other stores. In other words, it is possible to pay for unpaid products registered at other stores as well as products registered at the store the user is currently visiting.

[0400] Here, the operator Gqc can be dragged within the screen. The first area Gqa at the top of the screen is for indicating the intention to make a payment. On the other hand, the second area Gqb at the bottom of the screen is for indicating that the intention to make a payment is not present. The customer can select the item to be paid for by dragging the operator Gqc of the item they wish to pay for from the operator Gqc displayed on the payment item selection screen Gq to the first area Gqa.

[0401] Then, for example, when an operator Gqc that has been moved to the first area Gqa is confirmed by an operator such as a confirmation button (not shown), the purchase support unit 1548 determines that the products corresponding to each operator Gqc in the first area Gqa are subject to payment.

[0402] Furthermore, the payment target selection screen Gq also allows for the deletion of registered products. For example, each of the operation units Gqc may be provided with an operation unit Gqd to instruct the deletion of a registered product, and the operation of the operation unit Gqd may delete the registered product from the local transaction management table. Note that the operation unit Gqd may not be displayed at all times, but may be configured to be displayed by long-pressing the operation unit Gqc or similar operation.

[0403] Note that the screen layout of the payment item selection screen Gq is not limited to this. For example, as shown in Figure 37, information about the corresponding product may be displayed in association with the operator Gqc. Here, Figure 37 is a diagram showing an example of a screen displayed on the front display unit 132 of the customer service robot 10, and shows another example of a payment item selection screen.

[0404] The payment target selection screen Gr shown in Figure 37 has a first area Gqa and a second area Gqb, similar to the payment target selection screen Gq. In addition, the payment target selection screen Gr displays the same operator Gqc as the payment target selection screen Gq.

[0405] Furthermore, the operator Gqc on the payment target selection screen Gr displays associated information about the product associated with that operator Gqc. For example, Figure 37 shows an example of displaying product inventory information Gra. Inventory information Gra is displayed based on, for example, the number of items in stock of the corresponding product stored in the store's product master 2191. In the example in Figure 37, it is shown that there are 3 items remaining for the product associated with operator Gqc located in the second area Gpd. This allows customers to easily check how many items of the product corresponding to operator Gqc are remaining by looking at inventory information Gra.

[0406] The inventory information Gra may be displayed for all Gqc operators, or it may be displayed only for Gqc operators of products with inventory quantities below a threshold. For example, inventory information Gra may be displayed only for products with inventory quantities of 5 or less (as shown in Figure 37).

[0407] Furthermore, for unsettled items registered at other stores, inventory information Gra may also be displayed by referring to the product master 2191 of those other stores. In this case, the purchase support unit 1548 may collaborate with the store linkage unit 1547 to access the store equipment 20 of the relevant store via the network N and refer to the product master 2191. Also, if the server equipment 30 holds a comprehensive product master, the purchase support unit 1548 can check the inventory quantity by referring to the comprehensive product master.

[0408] Furthermore, for products with zero stock, the system may be configured to allow only deletion by displaying the aforementioned operator Gqd, or it may be configured to allow instructing payment to be made for reserved products. In the latter case, it is preferable to display the restocking date etc. in association with the operator Gqc by coordinating with the store device 20, etc.

[0409] Furthermore, the information displayed in association with the Gqc operator is not limited to the inventory information described above. For example, information such as the store name, product name, and price may be displayed based on the product information of the registered product.

[0410] Furthermore, based on the sales performance of registered products, information regarding sales performance may be displayed in association with the corresponding operator Gqc. For example, messages or images corresponding to sales performance, such as "It's selling well now!", may be displayed in association with the operator Gqc. This allows customers to be aware of the sales status of registered products, thereby encouraging them to take action to make a payment. Note that product sales performance may be obtained from the store device 20 or from the server device 30.

[0411] Returning to Figure 34, when the purchase support unit 1548 receives a selection of products to be paid for from the payment target selection screen (step S4221), it displays a payment method selection screen (see, for example, Figure 25) on the front display unit 132, where the payment method for the product can be selected (step S4222).

[0412] Furthermore, in step S4230, the purchase support unit 1548 determines whether or not the customer has instructed it to leave the store (step S4230). If the customer has not instructed it to leave the store (step S4230; No), the purchase support unit 1548 returns to step S4201. If the customer has instructed it to leave the store (step S4230; Yes), the process proceeds to step S23 in Figure 28.

[0413] After moving to step S23, any unpaid items registered with the customer service robot 10 will remain even after the customer leaves the store. Furthermore, if the customer leaves each of the destination stores with unpaid items, the items registered at multiple stores will remain unpaid.

[0414] Therefore, the purchase support unit 1548 can process the payment for any remaining unpaid items by performing the payment support process shown in Figure 38.

[0415] Here, Figure 38 is a flowchart showing an example of the payment support process performed by the customer service robot 10 in Modification 1. It should be noted that this process can be executed at any time in response to customer interaction, as long as the robot is operating in customer service mode.

[0416] For example, if the customer service robot 10 is stopped by a customer operation such as the stop button 142 while driving in lead mode, the purchase support unit 1548 displays the aforementioned operator Gfg etc. on the front display unit 132, making it possible to confirm the transaction details of the product (registration, payment status).

[0417] The purchase support unit 1548 waits until it receives an instruction from the customer to confirm the transaction details (Step S51; No). When the purchase support unit 1548 receives an instruction to confirm the transaction details, for example, by instructing the display of the virtual cart as described above (Step S51; Yes), it refers to the local transaction management table and determines whether or not there are any unsettled items (Step S52). Specifically, the purchase support unit 1548 determines whether or not the payment has been made based on the status of the purchased flag.

[0418] If all registered products have been paid for (Step S52; No), the purchase support unit 1548 displays a list of registered products on the front display unit 132 (Step S53) and proceeds to Step S63.

[0419] On the other hand, if it is determined that there are unpaid items (Step S52; Yes), the purchase support unit 1548 displays a screen on the front display unit 132 that lists the paid items and the unpaid items in a way that allows them to be identified (Step S54).

[0420] The screens displayed in steps S53 and S54 will be displayed in a similar format to the virtual cart screen shown in Figure 23, for example. Furthermore, paid-for items will be identifiable by adding information such as an icon indicating that they have been paid for.

[0421] Next, the purchase support unit 1548 determines whether or not the customer has instructed it to make a payment (step S55). If the customer has not instructed it to make a payment (step S55; No), the purchase support unit 1548 proceeds to step S63.

[0422] Furthermore, if the user is instructed to make a payment in step S55 (step S55; Yes), the purchase support unit 1548 displays a payment target selection screen (see, for example, Figure 36) for unpaid items on the front display unit 132 (step S56). When the purchase support unit 1548 receives a selection of items to be paid for from the payment target selection screen (step S57), it displays a payment method selection screen (see, for example, Figure 25) on the front display unit 132, where the user can select a payment method (step S58). Next, when the purchase support unit 1548 receives a payment method selection operation (step S59), it executes the payment process for the unpaid items using the selected payment method (step S60).

[0423] Furthermore, if the purchase support unit 1548 completes payment for the goods in step S60, it may notify the store equipment 20 of the store selling the goods of information (e.g., product code) regarding the goods that were paid for. In this case, for example, the control unit 214 of the store equipment 20 may perform control to reduce the inventory quantity of the paid goods.

[0424] Next, the purchase support unit 1548 displays a delivery method selection screen (see, for example, Figure 27) on the front display unit 132, which allows the user to select how to receive the goods (step S61). Once a delivery method is selected from the delivery method selection screen, the purchase support unit 1548 sends the delivery destination information generated based on the selected delivery method to the store device 20 or server device 30 to arrange for the transport of the goods (step S62), and then proceeds to step S63.

[0425] Next, the purchase support unit 1548 determines whether or not to terminate the verification of the transaction details (step S63). If the verification of the transaction details is to be continued (step S63; No), the purchase support unit 1548 returns to step S52. If it receives an instruction to terminate the verification of the transaction details (step S63; Yes), the purchase support unit 1548 terminates this process.

[0426] Thus, the customer service robot 10 according to this modified version can process payments for registered products at each store it visits, at any time, whether inside or outside the store. This allows the customer service robot 10 to flexibly respond to customers with various shopping styles, thereby supporting their shopping. Furthermore, the customer service robot 10 can improve opportunities for product registration and purchase, contributing to increased sales for the entire commercial facility.

[0427] [Differentiation 2] In the embodiment described above, the purchase support unit 1548 is configured to select recommended products from among the products sold at the destination store. However, it is not limited to this configuration, and recommended products may be selected from products sold at stores other than the destination store.

[0428] In this case, the purchase support unit 1548 selects recommended products by referring to the product masters 2191 of other stores in addition to the product master 2191 of the destination store. In this case, the purchase support unit 1548 may collaborate with the store linkage unit 1547 to access the store equipment 20 of other stores via the network N and refer to the product master 2191. Alternatively, if the server equipment 30 holds a comprehensive product master, the purchase support unit 1548 may be configured to refer to the comprehensive product master.

[0429] Furthermore, when the purchase support unit 1548 presents products from other stores as recommended products, it may either add the registration of such recommended products or allow registration. In the latter case, the registered recommended products will be temporary products that cannot be received on the spot.

[0430] [Difference 3] In the above embodiment, the customer service robot 10 is described as being configured to exchange various information by coordinating with the store's equipment 20 upon arriving at the store. However, the store equipment 20 that can be coordinated is not limited to the store equipment 20 that the robot is currently staying at.

[0431] For example, when the purchase support unit 1548 registers and processes payment for products at a store the customer is visiting, it may, in cooperation with the store collaboration unit 1547, etc., transmit product information for the product and user information about the check-in user, along with its own robot ID, to the store equipment 20 of another store as reference information. In addition, the purchase support unit 1548 may transmit product information of the products the customer tried on, the customer's appearance while trying on the clothes, and the customer's physical characteristics extracted during the try-on, along with its own robot ID, to the store equipment 20 of another store as reference information.

[0432] Furthermore, the products to be transmitted as reference information may include both store products and temporary products, or either one or the other. Also, the store device 20 to which the reference information is transmitted is not particularly limited and can be set arbitrarily. For example, the purchase support unit 1548 may transmit reference information to all stores in the commercial facility. The purchase support unit 1548 may also transmit reference information to stores of the same type as the store the customer is currently visiting. The purchase support unit 1548 may also transmit reference information to destination stores that have not yet been reached among the destination stores specified in the action plan.

[0433] Furthermore, when a customer (customer service robot 10) visits the store where the store equipment 20 (robot coordination unit 2142) has received the reference information, the store equipment 20 may advertise or recommend products to the customer service robot 10 based on the reference information of the corresponding robot ID. Specifically, once the robot coordination unit 2142 has completed coordination with the store coordination unit 1547 of the customer service robot 10, it provides the customer service robot 10 with product information regarding recommended products selected based on the reference information of the corresponding robot ID. Here, the recommended products may be selected using the same selection method as the purchase support unit 1548 described in the above embodiment, or they may be selected by the store staff.

[0434] Meanwhile, when the customer service robot 10 receives product information from the store equipment 20, the purchase support unit 1548 displays the product related to that product information as a recommended product on the front display unit 132. For example, the purchase support unit 1548 displays the recommended product notified by the store equipment 20 on the basic operation screen (see Figure 18).

[0435] In this way, the customer service robot 10 can efficiently provide purchasing support when a customer visits another store by transferring the history of customer transactions conducted at that store to other stores. Furthermore, the store equipment 20 can efficiently promote products by presenting customers with products that match their preferences based on the reference information transmitted from the customer service robot 10.

[0436] [Differentiation Example 4] In the above-described embodiment, each of the customer service robots 10 operates independently due to the various functional configurations it possesses. However, the embodiment is not limited to this configuration, and the server device 30 may be configured to comprehensively control the operation of the customer service robots 10.

[0437] In this case, the server device 30 may include, for example, one or all of the following functional configurations: an operation control unit 1544, a personalization processing unit 1545, an action plan generation unit 1546, a store collaboration unit 1547, and a purchase support unit 1548, and the operation of the customer service robot 10 may be individually controlled by the functions of these functional configurations.

[0438] In the above embodiment, the programs executed by the customer service robot 10, the store equipment 20, the server equipment 30, and the customer terminal 50 may be provided by recording them on a computer-readable recording medium such as a CD-ROM. Alternatively, the programs executed by each of the above devices may be stored on a computer connected to a network such as the Internet and provided by downloading them via the network, or they may be provided via a network such as the Internet.

[0439] Although embodiments of the present invention have been described above, these embodiments are presented as examples only and are not intended to limit the scope of the invention. The above embodiments can be implemented in various other forms, and various omissions, substitutions, modifications, and combinations can be made without departing from the spirit of the invention. These embodiments and their variations are included in the scope and spirit of the invention, as well as in the claims of the invention and its equivalents. [Explanation of symbols]

[0440] 1. Customer service support system 10 Customer service robots 20 Store Equipment 30 Server Devices 40 Parking Management Systems 50 Customer terminals 1541 Display Control Unit 1542 Operation Reception Unit 1543 Read / Write Control Unit 1544 Operation Control Unit 1545 Personalization Processing Unit 1546 Action Plan Generation Unit 1547 Store Liaison Department 1548 Purchasing Support Department 2141 Store Information Transmission Department 2142 Robot Collaboration Department 2143 Payment Processing Unit 3141 Information Management Department 3142 Robot Management Department [Prior art documents] [Patent Documents]

[0441] [Patent Document 1] Japanese Patent Publication No. 2021-111128

Claims

1. A customer service robot that moves with customers within a commercial facility containing multiple stores, A registration means that processes the registration of the products that the customer will purchase from among the products sold at the destination store, A receiving means that accepts the selection of products to be paid for at the store from among the products registered by the registration means, The aforementioned receiving means is a payment means that processes payment for the selected product, Equipped with, The payment means will process payments for unpaid items among the items registered by the registration means at any time in response to an operation from the customer. Customer service robot.

2. The receiving means displays a first selection screen on the display unit each time the registration means registers a product, allowing the user to choose whether or not to pay for the product, and accepts the selection of the product to be paid for via the first selection screen. The customer service robot according to claim 1.

3. The receiving means displays a second selection screen on the display unit that allows the user to select whether or not each of the products registered by the registration means should be subject to payment, and accepts the selection of products to be subject to payment via the second selection screen. The customer service robot according to claim 1.

4. The receiving means displays information about the product in association with the product registered by the registration means. The customer service robot according to claim 2 or 3.

5. The system further includes a recommendation mechanism that recommends products that the customer may purchase from among the products sold at the destination store or other stores. The registration means performs the registration process of the products recommended by the recommendation means in response to the customer's operation. The customer service robot according to claim 1.

6. The computer for a customer service robot that moves around with customers within a commercial facility containing multiple stores, A registration means that processes the registration of the products that the customer will purchase from among the products sold at the destination store, A receiving means that accepts the selection of products to be paid for at the store from among the products registered by the registration means, The aforementioned receiving means is a payment means that processes payment for the selected product, and make it work The payment means will process payments for unpaid items among the items registered by the registration means at any time in response to an operation from the customer. program.

Images