Mobile sales vehicle

Abstract

To provide a mobile sales vehicle that enables a customer within the shopping area to be reliably captured with a camera, and provide a server.SOLUTION: A mobile sales vehicle has a platform to have a goods management device placed thereon to display a plurality of goods, an opening / closing part that rotates in the vertical direction to open / close the platform, and one or more cameras. The cameras are attached to the opening / closing part. With the opening / closing part rotated upward, the cameras capture the entire of the shopping area continuously from top to bottom. In the shopping area, customers move to purchase the goods displayed on the goods management device placed on the platform. The cameras send the captured images to the goods management device.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] The embodiment of the present invention is a mobile sales In the car Regarding. [Background technology]

[0002] Conventionally, a sales method is known in which products are displayed in a store or a mobile sales vehicle, and a camera captures the display area. In this method, a camera captures the customer taking out a product from the display, identifies the product based on the captured image, and the customer makes a payment by operating the camera (for example, Patent Document 1).

[0003] Recently, mobile sales vehicles have been put into practical use so that when a customer removes a product and moves away from the product, payment is automatically processed. Specifically, when a customer moves away to a distance where the camera cannot capture the customer's image (when the customer moves outside the shopping area), payment is processed for the customer.

[0004] In the case of the above-mentioned sales style using a mobile sales van, the customer may be judged to have left the shopping area and payment may be made even though the customer is still in the middle of shopping. This is often due to the relationship between the camera's image capturing range and the customer's position, as the camera may not be able to capture an accurate image of the customer depending on where the customer is. Summary of the Invention [Problem to be solved by the invention]

[0005] The problem to be solved by the present invention is to provide a mobile sales system that can reliably capture images of customers in a shopping area with a camera. Car The aim is to provide. [Means for solving the problem]

[0006] The mobile sales vehicle of the embodiment has a loading platform for carrying a product management device for displaying a plurality of types of products, and Rotates in the upward direction The loading platform is opened by rotating the loading platform. releaseand a product management device mounted on the loading platform, which, when the opening / closing section is rotated upward, captures an image of an entire shopping area in which a customer moves to purchase the products displayed on the product management device from above to below without interruption. , imaged and one or more cameras that transmit images to the product management device. [Brief description of the drawings]

[0007] [Figure 1] FIG. 1 is an explanatory diagram showing a system according to an embodiment. [Diagram 2] FIG. 2 is a diagram showing the appearance of the mobile sales vehicle. [Diagram 3] FIG. 3 is a perspective view showing the configuration of the mobile sales vehicle. [Figure 4] FIG. 4 is a diagram illustrating a part of the product management device. [Diagram 5] FIG. 5 is a block diagram showing a hardware configuration of the mobile terminal. [Figure 6] FIG. 6 is a block diagram showing the hardware configuration of the reservation management server. [Figure 7] FIG. 7 is a memory map showing the configuration of the reservation management unit. [Figure 8] FIG. 8 is a memory map showing the configuration of the loaded product section. [Figure 9] FIG. 9 is a memory map showing the configuration of the customer master. [Figure 10] FIG. 10 is a memory map showing the configuration of the product master. [Figure 11] FIG. 11 is a block diagram showing a hardware configuration of the product management device. [Figure 12] FIG. 12 is a memory map showing the configuration of the reservation information section. [Figure 13] FIG. 13 is a flowchart showing the control process of the mobile terminal. [Figure 14] FIG. 14 is a diagram showing an example of a display screen of a mobile terminal. [Figure 15] FIG. 15 is a functional block diagram showing the functional configuration of the reservation management server. [Figure 16] FIG. 16 is a flowchart showing the control process of the reservation management server. [Figure 17] FIG. 17 is a functional block diagram showing the functional configuration of the product management device. [Figure 18] FIG. 18 is a flowchart showing the control process of the product management device. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] Hereinafter, the embodiments will be described with reference to the drawings. In the embodiments, a mobile terminal will be described as an example of a reservation device. Also, in the embodiments, a reservation management server will be described as an example of a server. Also, in the embodiments, a mobile terminal, a product management device, and a reservation management server will be described as a system, but a mobile terminal is not essential to the system. Note that the present invention is not limited to the following description of the embodiments.

[0009] Fig. 1 is an explanatory diagram showing a system according to an embodiment. In Fig. 1, a system 10 includes a mobile terminal 1, a reservation management server 3, and a product management device 7. The mobile terminal 1, the reservation management server 3, and the product management device 7 are each connected to a network N via a communication line L, so that they can transmit and receive information to and from each other.

[0010] The mobile terminal 1 is a portable device including a microcomputer, such as a mobile phone, a smartphone, a PDA (Personal Data Assistant), etc. By installing a dedicated application, the mobile terminal 1 becomes capable of communicating with the reservation management server 3 via the network N, and becomes capable of sending and receiving information to and from the reservation management server 3.

[0011] The mobile terminal 1 has a function of accessing a product reservation site and reserving the product to be purchased with the reservation management server 3. The mobile terminal 1 also has a function of specifying the date and time, the place, and the mobile sales vehicle for receiving the reserved product.

[0012] Furthermore, the mobile terminal 1 accesses the above site and makes a request to the reservation management server 3 to cancel all or part of the products that have been reserved.

[0013] The mobile terminal 1 also stores a customer code, which is customer identification information that identifies the person (customer) who carries the mobile terminal 1, and displays, by operation, a symbol G, such as a two-dimensional code or a barcode, on the display unit 21 (see FIG. 5).

[0014] Furthermore, when the user logs in by holding symbol G over a product management device 7 (described later), the mobile terminal 1 displays information about reserved products and information about products retrieved from the product management device 7.

[0015] The reservation management server 3 is composed of a computer (e.g., a cloud server). The reservation management server 3 stores reserved items reserved through the site by customer, associated with a customer code. The reservation management server 3 then transmits the stored information of the reserved items to the product management device 7. Furthermore, when the reservation management server 3 receives cancellation information for a reserved item that has already been reserved, it determines whether cancellation is possible. If cancellation is possible, the reservation management server 3 changes the stored information of the reserved items to modified information that deletes the canceled reserved items. The reservation management server 3 then transmits the modified information to the product management device 7.

[0016] The reservation management server 3 also provides information on reserved items by collating it for each specified mobile sales vehicle 5. The salesperson driving the mobile sales vehicle 5 loads the items into his / her own mobile sales vehicle 5. At that time, the salesperson loads the reserved items picked up from the store based on the provided information. The salesperson also loads regular items other than the reserved items into the mobile sales vehicle 5. The salesperson arranges the loaded items in the item management device 7.

[0017] Furthermore, when a customer acquires a product from a shelf 77 (described later) in the product management device 7, the reservation management server 3 stores the acquired product information in association with customer information. The reservation management server 3 executes payment processing for the product (candidate for purchase) acquired from the shelf by the customer in the product management device 7. Furthermore, the reservation management server 3 tallys up information on products (reserved products and regular products) for which payment processing has been performed, and manages product sales.

[0018] In addition, when a customer forgets to pick up a reserved product from the product management device 7, the reservation management server 3 transmits information about the forgotten product to the mobile terminal 1.

[0019] The mobile sales vehicle 5 is a vehicle such as a mobile automobile. FIG. 2 shows the exterior (side view) of the mobile sales vehicle 5. As shown in FIG. 2, the mobile sales vehicle 5 is equipped with a product management device 7, for example, in the loading platform. Specifically, the mobile sales vehicle 5 loads the product management device 7 on the loading platform 51 (see FIG. 3). When the mobile sales vehicle 5 arrives at a sales point for merchandise, the mobile sales vehicle 5 opens the interior by rotating doors 79 (opening / closing sections) covering both sides of the loading platform 51 upward in a gull-wing manner with the rotation axis 52 (see FIG. 3) as a rotation fulcrum, thereby exposing the product management device 7 and selling the merchandise displayed in the product management device 7.

[0020] The product management device 7 includes a computer, and is equipped with shelves 77 on which products are displayed. As shown in Fig. 2, the product management device 7 has multiple rows and multiple tiers of shelves 77. In the example of Fig. 2, shelves 77 configured in four tiers in the vertical direction are installed in two rows in the horizontal direction. In the product management device 7, products are displayed on each shelf 77.

[0021] 3 is a perspective view showing the mobile sales vehicle 5 with the door 79 rotated upward. The doors 79 are provided on both sides of the mobile sales vehicle 5. Each door 79 rotates upward about a rotation shaft 52 as a pivot point. At the same time, a platform 791 located under the door 79 rotates outward and downward to open. When the door 79 and the platform 791 rotate, the loading platform 51 is opened, and the product management device 7 loaded on the loading platform 51 is exposed. The platform 791 serves as a temporary storage area for products removed from the product management device 7.

[0022] When the door 79 is closed, it has a roof portion 792 which corresponds to the roof of the mobile sales vehicle 5, and side portions 793 which correspond to each side surface of the mobile sales vehicle 5. The roof portion 792 and the side portions 793 are bent at approximately 90° to each other. When the door 79 is rotated upward, the side portions 793 are held in a nearly horizontal state.

[0023] Cameras 81 and 86 are fixedly attached to the inside of the doors 79. In this embodiment, three cameras 81 are attached to each door 79. The cameras 81 are attached to the tip of the side portion 793 in a substantially straight line. Furthermore, two cameras 86 are attached to each door 79. The cameras 86 are attached near the bend between the side portion 793 and the roof portion 792. FIG. 3 shows the camera 86 attached to the rear side of the mobile sales vehicle 5, but in reality, the same camera 86 is also attached to the front side of the mobile sales vehicle 5.

[0024] These cameras 81 and 86 capture images from above downward with the door 79 rotated upward. Specifically, the camera 81 captures images of the areas on both sides of the mobile sales vehicle 5. The camera 86 captures images of the front and rear areas of the mobile sales vehicle 5.

[0025] Camera 81 and camera 86 are each capable of capturing an image of an imaging range H corresponding to the camera. In the embodiment, the cameras are arranged such that the imaging areas H of adjacent cameras overlap or contact each other. As a result, cameras 81 and 86 are capable of capturing an image of the entire surrounding area of ​​the mobile sales vehicle 5 without interruption. The entire surrounding area refers to an area (shopping area) where customers who shop in the mobile sales vehicle 5 usually move, which is shopping area Y in FIG. 3. In other words, as long as a customer who shops in the mobile sales vehicle 5 moves in shopping area Y, cameras 81 and 86 are capable of continuously capturing an image of the customer. If the customer leaves the shopping area Y, cameras 81 and 86 cannot capture an image of the customer.

[0026] In order to visually indicate the shopping area Y to the customer, for example, a light that illuminates downward is provided on the door 79, and the light illuminates the entire shopping area Y, thereby allowing the customer to recognize the shopping area Y. Also, the lower position of the door 79 that has been rotated upward may be recognized as the shopping area Y.

[0027] In addition, since the cameras 81, 86 are fixedly attached to the door 79, when the door 79 rotates upward, the cameras 81, 86 are always positioned to capture an image of the entire shopping area Y. Therefore, the mobile salesperson does not need to adjust the positions of the cameras 81, 86 each time. In addition, the door 79 rotated upward also serves as a rain shelter when it rains.

[0028] FIG. 4 is an enlarged perspective view of a portion (a portion surrounded by a rectangle T) of the product management device 7 in FIGS. 2 and 3. In FIG. 4, the product management device 7 includes a shelf 77. The shelf 77 displays products by type. In the example of FIG. 4, the shelf 77 has an area 78 (781) for displaying product A, an area 78 (782) for displaying product B, an area 78 (783) for displaying product C, an area 78 (784) for displaying product D, and an area 78 (785) for displaying product E. Products are placed in areas 781, 782, 784, and 785. In area 783, a product is hung from a hanging rod 7831 for suspending the product.

[0029] Additionally, each area 78 is provided with a weight sensor 82 (see FIG. 11). Areas 781, 782, 784, and 785 have weight sensors 82 attached to the stands on which the products are displayed. Area 783 has weight sensor 82 attached to hanging rod 7831. Weight sensor 82 detects a change in weight when a product displayed in each area is taken out.

[0030] The cameras 81 and 86 attached to the door 79 are electrically connected to the product management device 7. Therefore, all images captured by the cameras 81 and 86 are transmitted to the product management device 7.

[0031] In this embodiment, three cameras 81 and two cameras 86 are installed on one door 79, and are directed downward when the door 79 is rotated upward to capture images of customers from above. These cameras 81, 86 capture images of the entire shopping area Y without any gaps. The shopping area Y is an area that covers the range in which products are displayed and the area in which customers look at the displayed products and take them out. In other words, the cameras 81, 86 can always capture images of customers in the shopping area Y from above. In other words, the cameras 81, 86 cannot capture images of customers who have left the shopping area Y.

[0032] The merchandise management device 7 also includes an ID reading unit 83. The ID reading unit 83 is composed of, for example, a camera, and reads the symbol G by capturing an image of the symbol G displayed on the mobile terminal 1. A customer code, which is customer identification information that identifies a customer, is recorded in the symbol G, and the merchandise management device 7 captures the image of the symbol G displayed on the mobile terminal 1 to obtain the customer code of the customer carrying the mobile terminal 1 (i.e., the customer who has reserved the reserved product). Hereinafter, the merchandise management device 7's operation of the ID reading unit 83 capturing an image of the symbol G displayed on the mobile terminal 1 to obtain the customer code and perform authentication will be referred to as "login."

[0033] Furthermore, when a customer logs in, the merchandise management device 7 captures an image of the customer using cameras 81, 86, and performs lead tracing (leading-line tracing is performed using known technology) to constantly track the movement of the customer as he or she moves within the shopping area Y. When multiple customers are present in the shopping area Y at the same time, the merchandise management device 7 performs lead tracing for each customer, and grasps the movement route of each customer individually.

[0034] The product management device 7 also includes a plurality of light-emitting units 84. The light-emitting units 84 are, for example, configured with LEDs (Light Emitting Diodes). The light-emitting units 84 are provided corresponding to (close to) each of the areas 78. Therefore, it is possible to identify a product displayed in the area 78 where the light-emitting unit 84 emits light.

[0035] In addition, the product management device 7 stores reserved products by customer code, so when a customer logs in, it illuminates the light-emitting unit 84 at a position corresponding to the area 78 where the reserved products related to the read customer code are displayed.

[0036] Furthermore, when a customer picks up an item displayed on shelf 77, product management device 7 recognizes which item has been picked up. Product management device 7 recognizes which item has been picked up based on information on which weight sensor 82 has changed in weight and on the customer's current location information obtained by tracking the customer's path with cameras 81, 86. Product management device 7 transmits information on the item picked up by the customer to reservation management server 3. Reservation management server 3 stores information on the item picked up by the customer from shelf 77 in product management device 7 in association with customer information identified by the customer code.

[0037] The product management device 7 also compares the stored reserved products with the products picked up by the customer to determine whether any products have been left behind. If it determines that any products have been left behind, it notifies the reservation management server 3 of the information on the left-behind products. The reservation management server 3 then transmits the information on the left-behind products to the mobile terminal 1.

[0038] Furthermore, the product management device 7 detects that the logged-in customer has moved out of the shopping area Y, and transmits payment request information requesting payment for the product picked up by the customer to the reservation management server 3. Upon receiving the payment request information, the reservation management server 3 executes the payment process for the product.

[0039] In such a system 10, a customer reserves a product via a dedicated application for mobile terminals installed on the mobile terminal 1, or by accessing the website of the operating company using the mobile terminal 1. The customer also specifies the time zone and area in which the reserved product is to be purchased. The reservation management server 3 creates a product list that lists the type and number of reserved products for each mobile sales vehicle 5, for example, based on the information of the reserved product reserved by the customer, the time zone, and the area. The reservation management server 3 determines the mobile sales vehicle 5 to load the products based on the time zone and area information specified by the customer. The product list includes regular products other than the reserved products. Note that in the system 10, the customer may be able to specify the mobile sales vehicle 5 when purchasing the reserved product.

[0040] The mobile salesperson (or a person in charge) picks products from the store based on the created product list and loads them into the mobile sales vehicle 5. The mobile salesperson also displays the loaded products on shelves 77 of the product management device 7 by product type. The products displayed on the shelves 77 are a mixture of pre-order products and regular products.

[0041] A customer heads to the mobile sales van 5 that has arrived at the specified area and logs in. Not only customers who purchase reserved items, but also customers who purchase regular items log in. The customer then takes the item they wish to purchase from the shelf 77. Information about the taken-out item is then sent from the item management device 7 to the customer's mobile terminal 1 via the reservation management server 3. When the customer has finished purchasing the item and leaves the shopping area Y, payment for the item is automatically made.

[0042] From here, the hardware of the mobile terminal 1 will be described. FIG. 5 is a block diagram showing the hardware configuration of the mobile terminal 1. As shown in FIG. 5, the mobile terminal 1 includes a CPU (Central Processing Unit) 11, a ROM (Read Only Memory) 12, a RAM (Random Access Memory) 13, a memory unit 14, and the like. The CPU 11 is the main controller. The ROM 12 stores various programs. The RAM 13 expands programs and various data. The memory unit 14 stores various programs. The CPU 11, the ROM 12, the RAM 13, and the memory unit 14 are connected to each other via a bus 15. The CPU 11, the ROM 12, and the RAM 13 constitute a control unit 100. That is, the control unit 100 executes a control process related to the mobile terminal 1, which will be described later, by the CPU 11 operating according to a control program stored in the ROM 12 or the memory unit 14 and expanded in the RAM 13.

[0043] The RAM 13 has a reservation information section 131 and a taken-out product information section 132. The reservation information section 131 stores information on reserved products reserved by the customer. The information on reserved products is cleared when the payment process is completed. The taken-out product information section 132 stores information on products taken out from the shelf 77.

[0044] The memory unit 14 is composed of a non-volatile memory such as a hard disk drive (HDD) or a flash memory in which stored information is retained even when the power is turned off. The memory unit 14 includes a control program unit 141 and a customer code unit 142. The control program unit 141 stores a control program for controlling the mobile terminal 1. The customer code unit 142 stores a customer code that identifies a customer who carries the mobile terminal 1.

[0045] In addition, the control unit 100 is electrically connected to the display unit 21 and the operation unit 22 via the bus 15 and the controller 16. The display unit 21 is, for example, a liquid crystal display, and displays information to a customer operating the mobile terminal 1. The operation unit 22 is a touch panel provided on the display unit 21, including a code display button 221. The code display button 221 is a button for causing the display unit 21 to display a symbol G including a customer code stored in the customer code section 142.

[0046] The control unit 100 is also connected to a communication unit 24 via a bus 15. The communication unit 24 is connected to a network N via a communication line L, and transmits and receives information to and from the reservation management server 3.

[0047] From here, the hardware of the reservation management server 3 will be described. FIG. 6 is a block diagram showing the hardware configuration of the reservation management server 3. As shown in FIG. 6, the reservation management server 3 includes a CPU 31, a ROM 32, a RAM 33, and a memory unit 34. The CPU 31 is the main controller. The ROM 32 stores various programs. The RAM 33 expands programs and various data. The memory unit 34 stores various programs. The CPU 31, the ROM 32, the RAM 33, and the memory unit 34 are connected to one another via a bus 35. The CPU 31, the ROM 32, and the RAM 33 constitute a control unit 300. That is, the control unit 300 executes control processing related to the reservation management server 3, which will be described later, by the CPU 31 operating in accordance with the control program stored in the ROM 32 or the memory unit 34 and expanded in the RAM 33.

[0048] The RAM 33 has a reservation management unit 331 and a loaded product unit 332. The reservation management unit 331 stores information on reserved products in association with the respective customer codes. The loaded product unit 332 stores information on products listed in a product list. In other words, the loaded product unit 332 stores information on all products loaded into the mobile sales vehicle 5. The reservation management unit 331 will be described in detail later with reference to FIG. 7. The loaded product unit 332 will be described in detail later with reference to FIG. 8.

[0049] The memory unit 34 is composed of a non-volatile memory such as an HDD or a flash memory that retains stored information even when the power is turned off. The memory unit 34 has a control program unit 341, a customer master 342, and a product master 343. The control program unit 341 stores a control program for controlling the reservation management server 3. The customer master 342 stores, for example, various information of customers who have become members (information of customers who log in). The product master 343 stores various information of products in association with product codes that identify the products. The customer master 342 will be described in detail later with reference to FIG. 9. The product master 343 will be described in detail later with reference to FIG. 10.

[0050] In addition, the control unit 300 is electrically connected to a display unit 41 and an operation unit 42 via a bus 35 and a controller 36. The display unit 41 is, for example, a liquid crystal display, and displays information to an operator who operates the reservation management server 3. The operation unit 42 is composed of, for example, a keyboard and a touch panel.

[0051] The control unit 300 is also connected to a communication unit 43 via a bus 35. The communication unit 43 is connected to a network N via a communication line L, and transmits and receives information to and from the mobile terminal 1 and the product management device 7.

[0052] Next, the reservation management unit 331 will be described. FIG. 7 is a memory map showing the configuration of the reservation management unit 331. As shown in FIG. 7, the reservation management unit 331 has a customer code unit 3311, a reserved product unit 3312, a loading information unit 3313, a taken product unit 3314, and a payment information unit 3315. The customer code unit 3311 stores the customer code of the customer who reserved the product. The reserved product unit 3312 stores information on the reserved product reserved by the customer (including a product code that identifies the reserved product) in association with the customer code stored in the customer code unit 3311. The loading information unit 3313 stores information on the mobile sales vehicle 5 that loads the product reserved by the customer, the date and time of receiving the reserved product, the location, etc. in association with the customer code stored in the customer code unit 3311. The taken product unit 3314 stores information on the reserved product and the normal product taken out from the shelf 77. The payment information unit 3315 stores information on whether or not payment has been made for the reserved product.

[0053] Next, the loaded product section 332 will be described. FIG. 8 is a memory map showing the configuration of the loaded product section 332. As shown in FIG. 8, the loaded product section 332 has a mobile sales vehicle section 3321 and a product section 3322. The mobile sales vehicle section 3321 stores information that distinguishes each mobile sales vehicle 5 (for example, information on the model number of the mobile sales vehicle 5). The product section 3322 stores information on all products to be loaded onto the mobile sales vehicle 5 (information on which products are to be loaded and how many of each product are to be loaded) in association with the information on the mobile sales vehicle 5 stored in the mobile sales vehicle section 3321. The information stored in the product section 3322 is the same information as the information on the products listed in the product list.

[0054] Next, the customer master 342 will be described. FIG. 9 is a memory map showing the configuration of the customer master 342. As shown in FIG. 9, the customer master 342 has a customer code section 3421, a customer information section 3422, an address information section 3423, and a purchased product history section 3424. The customer code section 3421 stores a customer code for each customer. The customer information section 3422 stores information on the customer (such as name, address, telephone number, and information on the medium of payment (e.g., credit card)) in correspondence with the customer code stored in the customer code section 3421. The address information section 3423 stores an address for sending emails and information to the mobile terminal 1 carried by the customer (i.e., the mobile terminal 1 for reserving a product) in correspondence with the customer code stored in the customer code section 3421. The purchased product history section 3424 stores history information on products purchased in the past by the customer in correspondence with the customer code stored in the customer code section 3421.

[0055] Next, the product master 343 will be described. Fig. 10 is a memory map showing the configuration of the product master 343. The product master 343 has a product code section 3431, a product name section 3432, a unit price section 3433, and a cancellation possibility section 3434. The product code section 3431 stores product codes that identify all products sold in the store or mobile sales vehicle 5 for each product. The product name section 3432 stores the product name of the product in association with the product code stored in the product code section 3431. The unit price section 3433 stores the unit price of the product in association with the product code stored in the product code section 3431.

[0056] The cancelability section 3434 stores information on whether the reservation of the product can be cancelled after the reservation of the product in association with the product code stored in the product code section 3431. For example, the cancelability section 3434 stores a flag indicating whether the reservation of the product can be cancelled after the reservation of the product. For a product for which the reservation can be cancelled after the reservation of the product, the cancelability section 3434 stores a flag "1". For a product for which the reservation cannot be cancelled after the reservation of the product, the cancelability section 3434 stores a flag "0". In the example of FIG. 10, the cancelability section 3434 stores a flag "1" for products A and B, and therefore the reservation of the product can be cancelled after the reservation of the product. The cancelability section 3434 stores a flag "0" for products for which the reservation of the product cannot be cancelled after the reservation of the product. In addition, the cancelability section 3434 stores a flag "0" for products C and D, and therefore the reservation of the product cannot be cancelled after the reservation of the product. Products for which the reservation of the product cannot be cancelled after the reservation of the product are, for example, products with a short expiration date, such as fresh food or boxed lunches. In addition, products that are difficult for other customers to purchase, or products that would be disadvantageous to the store if a customer who has made a reservation does not purchase the product, may also become products for which reservations cannot be canceled after they are made.

[0057] From here, the hardware of the product management device 7 will be described. FIG. 11 is a block diagram showing the hardware configuration of the product management device 7. As shown in FIG. 11, the product management device 7 includes a CPU 71, a ROM 72, a RAM 73, and a memory unit 74. The CPU 71 is the main controller. The ROM 72 stores various programs. The RAM 73 loads programs and various data. The memory unit 74 stores various programs. The CPU 71, the ROM 72, the RAM 73, and the memory unit 74 are connected to one another via a bus 75. The CPU 71, the ROM 72, and the RAM 73 constitute a control unit 700. That is, the control unit 700 executes control processing related to the product management device 7, which will be described later, by the CPU 71 operating in accordance with a control program stored in the ROM 72 or the memory unit 74 and loaded in the RAM 73.

[0058] The RAM 73 has a product information section 731, a reservation information section 732, a sales product section 733, and a remaining product quantity section 734. The product information section 731 stores product information (product code, product name, unit price, etc.) of products taken out from the shelf 77 by customers for each customer. The reservation information section 732 stores the product codes of reserved products loaded into the mobile sales vehicle 5 in association with the customer code of the customer for each customer who made the reservation. The reservation information section 732 will be described later in FIG. 12. The information stored in the reservation information section 732 deletes the information of customers for whom payment has been completed. Therefore, the information stored in the reservation information section 732 is the type and number of reserved products for customers for whom payment has not been completed.

[0059] The sold goods section 733 stores the number of goods sold by item code for goods sold by the mobile sales vehicle 5 (goods for which payment has been completed). The remaining item number section 734 stores the type and remaining number of goods currently displayed in the item management device 7. In other words, the remaining item number section 734 stores the number of goods for each item obtained by subtracting the information on the number of goods stored in the sold goods section 733 from the information on the number of goods loaded by the mobile sales vehicle 5 at the store.

[0060] The memory unit 74 is composed of a non-volatile memory such as a HDD or a flash memory that retains stored information even when the power is turned off. The memory unit 74 has a control program unit 741, a product position information unit 742, and a product master 743. The control program unit 741 stores a control program for controlling the product management device 7.

[0061] The product position information section 742 (display position storage section) stores one product code and one light-emitting section 84 in association with each other. That is, when a product code is specified, the light-emitting section 84 provided in the area 78 where the product with the product code is displayed can be specified. Therefore, for example, when a reserved product reserved by a customer is identified, the light-emitting section 84 provided in the area 78 where the reserved product is displayed on the shelf 77 can be made to emit light. Therefore, when a customer who has reserved a product logs in, the control section 700 makes the light-emitting section 84 provided in the area 78 where the product is displayed emit light based on the product code of the reserved product stored in the reservation information section 732 in correspondence with the read customer code. The product master 743 stores the same information as the product master 343.

[0062] Furthermore, the control unit 300 is electrically connected to the cameras 81 (six cameras 81 in this embodiment), the cameras 86 (four cameras 86 in this embodiment), the weight sensor 82, the ID reading unit 83, and the light emitting unit 84 via the bus 35 and the controller 36. The camera 81 captures an image of a customer in the shopping area Y. The weight sensor 82 detects that a product has been removed from the shelf 77 by a change in weight. The ID reading unit 83 captures an image of the symbol G displayed on the mobile terminal 1.

[0063] The control unit 700 is also connected to a communication unit 85 via a bus 75. The communication unit 85 is connected to a network N via a communication line L, and transmits and receives information to and from the reservation management server 3.

[0064] Next, the reservation information section 732 will be described. Fig. 12 is a memory map showing the configuration of the reservation information section 732. As shown in Fig. 12, the reservation information section 732 has a customer code section 7321 and a reserved product section 7322. The customer code section 7321 stores the customer code of a customer who has reserved a product from the mobile terminal 1. The reserved product section 7322 stores product information (including the product code) of the reserved product that the customer has reserved from the mobile terminal 1, in association with the customer code stored in the customer code section 7321.

[0065] From here, the control of the mobile terminal 1 will be described. Fig. 13 is a flowchart showing the control process of the mobile terminal 1. As shown in Fig. 13, the control unit 100 of the mobile terminal 1 judges whether an installed application for reserving a product is running (S11). The control unit 100 waits until the application is running (No in S11), and if it is determined that the application is running (Yes in S11), the control unit 100 enables communication with the reservation management server 3 (S12).

[0066] Next, the control unit 100 judges whether or not an operation to start a product reservation has been performed on the operation unit 22 of the mobile terminal 1 (S21). When it is judged that an operation to start a product reservation has been performed (Yes in S21), the control unit 100 displays products that can be reserved. When the customer specifies the product to be reserved, the control unit 100 selects the specified product as a reserved product (S22). Then, the control unit 100 stores the product information (including the product code) of the reserved product and the information such as the pick-up location and pick-up time specified by the customer in the reservation information unit 131 (S23). Then, the control unit 100 transmits the information of the reserved product, the pick-up location and the pick-up time stored in the reservation information unit 131 to the reservation management server 3 in association with the customer code stored in the customer code unit 142 (S24). Then, the control unit 100 returns to S21. Note that, when the customer can select the mobile sales vehicle 5, the information of the mobile sales vehicle 5 is also transmitted to the reservation management server 3 in association with the customer code.

[0067] Also, if it is determined that the operation is not an operation to start a product reservation (No in S21), the control unit 100 determines whether the operation is an operation to cancel the reserved product through the operation unit 22 (S31). If it is determined that the operation is an operation to cancel the reserved product (Yes in S31), the control unit 100 inquires of the reservation management server 3 whether the product is a cancelable product (S32). Then, the control unit 100 determines whether reservation change information has been received from the reservation management server 3 (S33). If it is determined that reservation change information has been received from the reservation management server 3 (Yes in S33), the control unit 100 deletes the product information of the canceled product from the reserved products stored in the reservation information unit 131 (S34). Then, the control unit 100 displays on the display unit 21 that the product has been canceled (S35). Then, the control unit 100 returns to S21.

[0068] If it is determined that reservation change information has not been received (No in S33), the control unit 100 then determines whether reservation change unavailability information has been received from the reservation management server 3 (S36). If it is determined that reservation change unavailability information has been received from the reservation management server 3 (Yes in S36), the control unit 100 displays on the display unit 21 a message indicating that the product cannot be canceled (S37). Then, the control unit 100 returns to S21. If it is determined that reservation change unavailability information has not been received (No in S36), the control unit 100 returns to S33.

[0069] Furthermore, if it is determined that the operation is not for canceling the reserved item (No in S31), the control unit 100 determines whether the code display button 221 has been operated (S41). If it is determined that the code display button 221 has been operated (Yes in S41), the control unit 100 displays a symbol G including a customer code stored in the customer code section 142 on the display unit 21 (S42). The code display button 221 is operated by a customer when the customer causes the ID reading unit 83 to read the symbol G. Then, the control unit 100 displays the product information (product name, etc.) of the reserved item stored in the reservation information section 131 at a position different from the symbol G on the display unit 21 (S43). Then, the control unit 100 returns to S21.

[0070] Furthermore, if it is determined that the operation has not been performed on the code display button 221 (No in S41), the control unit 100 determines whether the information is for a product to be taken out from the shelf 77 from the reservation management server 3 (S51). If it is determined that the information is for a product to be taken out (Yes in S51), the control unit 100 updates the information for the product to be taken out displayed on the display unit 21 (S52). Then, the control unit 100 returns to S21.

[0071] Fig. 14 shows symbol G displayed on display unit 21 in S42, reserved items 211 displayed on display unit 21 in S43, and taken-out items 212 displayed on display unit 21 in S52. In Fig. 14, the display of reserved items 211 indicates that the reserved items are items A, B, and C. Moreover, the display of taken-out items 212 indicates that the taken-out items are items A, B, and D. In the display of reserved items 211, the characters displayed for reserved items A and B are in bold, which indicates that of the reserved items, items A and B have been taken out. Item C is not in bold, and has not yet been taken out.

[0072] Return to the description of FIG. 13. If it is determined that the information is not for a product to be taken out (No in S51), the control unit 100 determines whether or not information for payment for the product to be taken out has been received from the reservation management server 3 (S53). If it is determined that information for payment for the product to be taken out has been received (Yes in S53), the control unit 100 determines whether or not the customer has operated the operation unit 22 and approved the payment (S54). The control unit 100 waits until the payment is approved (No in S54), and if it is determined that the payment is approved (Yes in S54), the control unit 100 transmits approval information to the reservation management server 3 (S55). Then, the control unit 100 deletes information for the reserved product for which the payment has been approved from the reservation information unit 131. If the payment is approved, all information shown in FIG. 14 is cleared. Then, the control unit 100 returns to S21.

[0073] Furthermore, if it is determined that the received information is not for payment for the picked-up product (No in S53), the control unit 100 determines whether information of a reserved product that was left behind on the shelf 77 has been received from the reservation management server 3 (S61). If it is determined that information of a reserved product that was left behind on the shelf 77 has been received (Yes in S61), the control unit 100 displays the information of the product that was left behind on the display unit 21 (S62). The customer looks at the displayed product information and determines at that point whether or not it is necessary to purchase the product, and if it is determined that it is not necessary, performs a reservation cancellation operation on the operation unit 22 to indicate that the purchase of the product is not necessary.

[0074] The control unit 100 judges whether a cancellation operation for the reservation has been performed (S63). If it is judged that a cancellation operation has been performed (Yes in S63), the control unit 100 inquires of the reservation management server 3 whether the product can be cancelled. The reservation management server 3 judges whether the reservation for the product can be cancelled based on the flag information stored in the cancellation permission unit 3434 for the product, and responds to the mobile terminal 1.

[0075] The control unit 100 judges whether the reservation of the canceled reserved item can be cancelled based on the response information received from the reservation management server 3 (S65). If it is judged that the reservation can be cancelled (Yes in S65), the control unit 100 transmits payment request information to the reservation management server 3 to settle the payment excluding the canceled item (S66). Then, the control unit 100 returns to S21. If it is judged that the reservation cannot be cancelled (No in S65), the control unit 100 displays a display indicating that the reservation of the reserved item cannot be cancelled (S67). Then, the control unit 100 returns to S62. If the customer wishes to purchase the left-behind item, the customer returns to the mobile sales vehicle 5 and takes out the item from the shelf 77. Therefore, if the cancellation operation was not performed in S63 (No in S63), the control unit 100 returns to S51 and judges whether the left-behind item has been taken out.

[0076] Furthermore, in S61, if it is determined that the received information is not about a reserved product that was left behind on the shelf 77 (No in S61), the control unit 100 determines whether the application for reserving the product has been closed (S13). If it is determined that the application for reserving the product has been closed (Yes in S13), the control unit 100 ends the process. If it is determined that the application has not been closed (No in S13), the control unit 100 returns to S21.

[0077] From here, we will explain the functional configuration of the reservation management server 3. Fig. 15 is a functional block diagram showing the functional configuration of the reservation management server 3. The control unit 300 of the reservation management server 3 functions as a second storage unit 301, a first transmission unit 302, a third transmission unit 303, a cancellation determination unit 304, a fourth transmission unit 305, a reception unit 306, and a settlement unit 307 by following the control programs stored in the ROM 32 and the control program unit 341 of the memory unit 34.

[0078] The second storage unit 301 stores reserved items reserved from the mobile terminal 1, which is a reservation device. Specifically, the second storage unit 301 stores the reserved items reserved from the mobile terminal 1 in the reservation management unit 331 in association with a customer code received at the same time.

[0079] The first transmission unit 302 transmits information about the reserved item to the product management device 7 in association with the customer code of the customer who reserved the reserved item. Specifically, the first transmission unit 302 transmits information about the reserved item stored in the reservation management unit 331 to the product management device 7 in association with the customer code stored in the reservation management unit 331.

[0080] The third transmission unit 303 transmits the product information of the taken-out product received from the product management device 7 to the mobile terminal 1. Specifically, when the product management device 7 receives information of a product taken out from the shelf 77, the third transmission unit 303 transmits the product information of the taken-out product to the mobile terminal 1.

[0081] When the cancellation determination unit 304 receives cancellation information for a reservation of a reserved item from the mobile terminal 1, it determines whether the reservation of the reserved item can be canceled. Specifically, when the cancellation determination unit 304 receives cancellation information for a reservation of a reserved item from the mobile terminal 1, it checks the state of the flag stored in the cancellation possibility unit 3434 for that item, and if the flag is "1", it determines that the reservation of the reserved item can be canceled. In addition, the cancellation determination unit 304 checks the state of the flag stored in the cancellation possibility unit 3434 for that item, and if the flag is "0", it determines that the reservation of the reserved item cannot be canceled.

[0082] When the cancellation determination unit 304 determines that the reservation of the reserved item can be canceled, the fourth transmission unit 305 transmits information that allows the reservation of the reserved item for which the cancellation information was received to be canceled to the product management device 7. Specifically, when the cancellation determination unit 304 determines that the reservation of the reserved item can be canceled, the fourth transmission unit 305 creates new change information for the reserved item by deleting the information about the reserved item for which the reservation can be canceled from the reserved items stored in the reservation management unit 331 (this change information corresponds to "information that allows the item for which the cancellation information was received to be canceled") and transmits it to the mobile terminal 1 and the product management device 7.

[0083] The receiving unit 306 receives payment request information indicating that a customer has left the shopping area Y from the product management device 7 in the mobile sales vehicle 5, which is equipped with a loading platform 51 on which a product management device 7 displaying multiple types of products is loaded, a door 79 that opens and closes the loading platform 51 by rotating up and down, and one or more cameras 81, 86 that are attached to the door 79 and, when the door 79 is rotated upward, capture continuous images from above to below of the entire shopping area Y through which customers move to purchase products displayed on the product management device 7 loaded on the loading platform 51 and transmit the images to the product management device.

[0084] The settlement unit 307 executes a settlement process for the product that the customer picked up from the displayed products based on the received settlement request information.

[0085] From here, the control process of the reservation management server 3 will be described. FIG. 16 is a flowchart showing the control process of the reservation management server 3. As shown in FIG. 16, the control unit 300 of the reservation management server 3 judges whether reservation information of a product has been received from the mobile terminal 1 (S71). When it is judged that reservation information of a product has been received from the mobile terminal 1 (Yes in S71), the second storage unit 301 associates the received information of the reserved product with the customer code received at the same time and stores it in the reservation management unit 331 (S72). Then, the first transmission unit 302 transmits the information of the reserved product stored in the reservation management unit 331 together with the associated customer code to the product management device 7 (S73). Then, the control unit 300 ends the process and returns to S71.

[0086] Also, if it is determined that the reservation information of the product is not received from the mobile terminal 1 (No in S71), the control unit 300 determines whether or not information is received from the mobile terminal 1 indicating that the reservation of all or part of the reserved product that was once reserved is to be cancelled (S81). This determination of whether or not the reservation is received is performed based on the processing of S32 and S63 of the mobile terminal 1. If it is determined that the reservation cancellation information of the reserved product is received (Yes in S81), the cancellation determination unit 304 determines whether or not the reservation of the reserved product can be cancelled based on the state of the flag stored in the cancellation possibility unit 3434 (S82). If it is determined that the reservation of the reserved product can be cancelled (Yes in S82), the control unit 300 creates new reservation product information by deleting the information of the product to be cancelled from the reservation product stored in the reservation management unit 331 (S83). Then, the fourth transmission unit 305 transmits the new reservation product information to the product management device 7 as change information (S84). The control unit 300 also transmits the change information to the mobile terminal 1. Then, the control unit 300 ends the process and returns to S71.

[0087] Moreover, if it is determined that the reserved item cannot be canceled (No in S82), the control unit 300 transmits information indicating that the reservation of the item cannot be canceled to the mobile terminal 1 (S85). Then, the control unit 300 ends the process and returns to S71.

[0088] Furthermore, if it is determined that the received information is not a request to cancel the reservation of a reserved item (No in S81), the control unit 300 determines whether product information (including the product code) of the product taken out from the shelf 77 has been received from the product management device 7 (S86). If it is determined that product information of the product taken out from the shelf 77 has been received (Yes in S86), the third transmission unit 303 stores the received product information of the taken out product in the taken out product unit 333 and transmits it to the mobile terminal 1 (S87). Then, the control unit 300 ends the process and returns to S71.

[0089] Furthermore, if it is determined that the received message is not product information of a product taken out from the shelf 77 (No in S86), the receiving unit 306 determines whether payment request information for requesting payment for the product taken out from the shelf 77 has been received together with the customer code from the product management device 7 (S91). If it is determined that payment request information has been received (Yes in S91), the address information unit 3423 is searched based on the received customer code, and information for payment for the taken out product is transmitted to the address of the mobile terminal 1 of the customer (S92). The mobile terminal 1 approves the payment based on this information.

[0090] Next, the control unit 300 judges whether or not information approving the payment for the taken-out product is received from the mobile terminal 1 (S93). The control unit 300 waits until the information approving the payment is received (No in S93), and if it is judged that the information approving the payment for the taken-out product is received (Yes in S93), the payment unit 307 executes the payment process based on the product information stored in the taken-out product section 3314 (S94). The payment process is automatically performed based on the information of the medium to be paid (e.g., credit card number) stored in the customer information section 3422. Then, the control unit 300 stores the payment information in the purchased product history section 3424, and stores the information of the payment in the payment information section 3315 corresponding to the customer code (S95). The control unit 300 also records the payment information in the RAM 33 as the sales information of the store. Then, the control unit 300 ends the process and returns to S71.

[0091] Furthermore, if it is determined that the payment request information has not been received (No in S91), the control unit 300 determines whether information about a forgotten reserved item has been received from the product management device 7 (S101). If it is determined that information about a forgotten reserved item has been received (Yes in S101), the control unit 300 transmits the information about the forgotten reserved item to the mobile terminal 1 (S102). Then, the control unit 300 ends the process and returns to S71.

[0092] Furthermore, if it is determined that the received information is not about a reserved item being left behind (No in S101), the control unit 300 determines whether or not resume information to resume shopping for the left-behind item has been received from the mobile terminal 1 (S103). If it is determined that resume information has been received (Yes in S103), the control unit 300 transmits the resume information to the item management device 7 (S104). Then, the control unit 300 ends the process and returns to S71.

[0093] Furthermore, if it is determined that resumption information has not been received (No in S103), the control unit 300 determines whether payment request information has been received from the mobile terminal 1 (S105). If it is determined that payment request information has been received from the mobile terminal 1 (Yes in S105), the control unit 300 executes the processes from S94 onwards. That is, the control unit 300 executes the payment process with the forgotten item canceled. Furthermore, if it is determined that payment request information has not been received (No in S105), the control unit 300 ends the process and returns to S71.

[0094] From here, we will explain the functional configuration of the product management device 7. Fig. 17 is a functional block diagram showing the functional configuration of the product management device 7. The control unit 700 of the product management device 7 functions as a first storage unit 701, an acquisition unit 702, a display control unit 703, a removal determination unit 704, a second transmission unit 705, and a cancellation unit 706 by following a control program stored in the ROM 72 or a control program unit 741 of the memory unit 74.

[0095] The first storage unit 701 stores reserved items by customer code that identifies a customer in association with the customer code. Specifically, when the first storage unit 701 receives information about reserved items from the reservation management server 3, the first storage unit 701 stores the information about the reserved items in the reservation information unit 732 by customer code received at the same time in association with the customer code.

[0096] The acquiring unit 702 acquires a customer code. Specifically, the acquiring unit 702 reads the symbol G displayed on the mobile terminal 1 using the ID reading unit 83 to acquire the customer code.

[0097] The display control unit 703 specifies the display position of the reserved item stored in the first storage unit 701 in association with the acquired customer code based on the information stored in the product position information unit 742, and causes the light emitting unit 84 provided at the specified display position to emit light (i.e., displays the specified display position on the display unit). Specifically, the display control unit 703 searches the reservation information unit 732 based on the customer code included in the symbol G read by the ID reading unit 83, acquires information on the reserved item stored in association with the customer code, and causes the light emitting unit 84 at the display position of the reserved item stored in the product position information unit 742 to emit light. Note that, when multiple customers log in at the same time, the light emitting unit 84 may be changed in light color for each logged-in customer. The light emitting unit 84 may be configured to emit light in multiple colors.

[0098] The removal determination unit 704 determines whether a product displayed on the shelf 77 has been removed. Specifically, the removal determination unit 704 determines whether a product displayed on the shelf 77 has been removed based on information on whether the weight sensor 82 has detected a weight change and whether the camera 81 has captured an image of the product being removed.

[0099] The second transmitting unit 705 transmits to the reservation management server 3 product information (including the product code) indicating the product that the removal determining unit 704 has determined to have been removed.

[0100] The cancellation unit 706 receives information that allows the reservation of a reserved item to be cancelled, and cancels the reservation of the reserved item from the reserved items stored in the reservation information unit 732. Specifically, the cancellation unit 706 receives change information from the reservation management server 3 that deletes the product information of the item whose reservation has been cancelled, and overwrites the change information on the original reserved item stored in the reservation information unit 732. In this way, the cancellation unit 706 cancels the reservation of the reserved item from the reserved items stored in the first storage unit 701.

[0101] From here, the control process of the product management device 7 will be described. Fig. 18 is a flowchart showing the control process of the product management device 7. The control unit 700 of the product management device 7 judges whether information on reserved products and customer codes has been received from the reservation management server 3 (S111). If it is judged that information on reserved products and customer codes has been received from the reservation management server 3 (Yes in S111), the first storage unit 701 stores the information on the reserved products in association with the customer code in the reservation information unit 732 (S112). The control unit 700 then ends the process and returns to S111.

[0102] Furthermore, if it is determined that the information received is not information on the reserved item and customer code from the reservation management server 3 (No in S111), the control unit 700 determines whether change information related to the cancellation of the reservation of the reserved item has been received from the reservation management server 3 (S113). If change information has been received, the cancellation unit 706 overwrites the change information over the original reserved item information stored in the reservation information unit 732, changing the reservation information of the reserved item (S114). The control unit 700 then ends the process and returns to S111.

[0103] Furthermore, if it is determined that the received change information is not related to the cancellation of the reserved item (No in S113), the control unit 700 determines whether the ID reading unit 83 has read the symbol G (whether the customer has logged in) (S121). If it is determined that the symbol G has been read, the acquisition unit 702 uses the ID reading unit 83 to read the symbol G displayed on the mobile terminal 1 and stores the customer code (acquires the customer code) (S122). Then, the control unit 700 determines whether the customer code is the customer code of the customer who reserved the reserved item (S123). This determination is made based on whether the acquired customer code is included in the customer code stored in the reservation information unit 732. If the acquired customer code is included in the customer code stored in the reservation information unit 732, the control unit 700 determines that the customer code is the customer code of the customer who reserved the reserved item. If the acquired customer code is not included in the customer code stored in the reservation information unit 732, the control unit 700 determines that the customer code is not the customer code of the customer who reserved the reserved item.

[0104] When it is determined that the customer code is that of a customer who has reserved a reserved item (Yes in S123), the control unit 700 reads out the product information (including the product code) of the reserved item associated with the corresponding customer code from the reservation information unit 732 (S124). Then, the display control unit 703 specifies the light-emitting unit 84 provided at the display position of the reserved item stored in the product position information unit 742 based on the read product information, and causes the light-emitting unit 84 to emit light (S125). For example, in FIG. 4, when the product information read out in S124 is product A, product B, and product C (i.e., when the reserved items are product A, product B, and product C), the display control unit 703 specifies the light-emitting unit 84 (light-emitting unit 841, light-emitting unit 842, light-emitting unit 843) provided at the display area (area 781, area 782, area 783) of product A, product B, and product C stored in the product position information unit 742, and causes the light-emitting unit 84 to emit light. Next, the control unit 700 starts tracing the path of the customer who has logged in (S126). Then, the control unit 700 ends the process and returns to S111.

[0105] Furthermore, if it is determined that the customer has not logged in (No in S121), the removal determination unit 704 determines whether an item displayed on the shelf 77 has been removed (S131) ​​based on whether the weight sensor 82 detects a weight change and whether the camera 81 captures an image of the item being removed. If it is determined that an item displayed on the shelf 77 has been removed (Yes in S131), it determines whether the removed item is a reserved item for the logged-in customer (S132). If the removed item is stored in the reservation information unit 732 in association with the logged-in customer code, it is determined that the removed item is a reserved item for the logged-in customer. If the removed item is not stored in the reservation information unit 732 in association with the logged-in customer code, it is determined that the removed item is not a reserved item for the logged-in customer.

[0106] When it is determined that the taken-out product is a reserved product of the logged-in customer (Yes in S132), the control unit 700 stores the product in the product information section 731 (S134). The product information section 731 stores product information of the reserved product taken out by the customer by customer code. The second transmission unit 705 then transmits product information (including the product code) indicating the taken-out product to the reservation management server 3 (S135). The control unit 700 then updates the product by subtracting the stock quantity of the product stored in the remaining product quantity section 734 (S136). In addition, in the process of S136, the control unit 700 deletes information of the reserved product taken out from the shelf 77 from the reservation information section 732. In addition, the control unit 700 adds the sales quantity of the product stored in the sales product section 733. The control unit 700 then ends the process and returns to S111.

[0107] Furthermore, if it is determined that the taken-out product is not a reserved product of the logged-in customer (No in S132) (in this case, the customer took out a regular product), the control unit 700 compares the stock number (remaining number of the product stored in the product remaining number section 734) of the taken-out product with the number of reserved products (the number of reserved products that have not yet been picked up by the customer who made the reservation among the reserved products stored in the reservation information section 732) to determine whether the stock of the product is greater than the number of reserved products (S133). If it is determined that the stock of the product is greater than the number of reserved products (Yes in S133), the control unit 700 executes the processes of S134 to S136 for regular products. Furthermore, if it is determined that the stock of the product is equal to or less than the number of reserved products (No in S133), the control unit 700 notifies information indicating that the product is a reserved product and cannot be sold (S137). This notification can be, for example, displayed on a nearby signage or the like, or the light-emitting unit 84 can be made to emit light in a different color or blink. Then, the control unit 700 ends the process and returns to S111.

[0108] Furthermore, in S131, when it is determined that the customer is not removing products displayed on the shelf 77 (No in S131), the control unit 700 determines whether it is no longer possible to trace the path of the logged-in customer (S151). When the logged-in customer leaves the shopping area Y in FIG. 2, it becomes impossible to trace the path of the customer by the cameras 81 and 86. Therefore, when it becomes impossible to trace the path of the logged-in customer, it can be determined that the customer has left the shopping area Y. When it is determined that it is no longer possible to trace the path of the logged-in customer (Yes in S151), the control unit 700 determines whether the customer is a customer who has reserved reserved products based on the customer code (S152). When it is determined that the customer is a customer who has reserved products (Yes in S152), the control unit 700 determines whether all reserved products have been removed by the customer (S153). In the process of S136, information on the reserved items taken out from shelf 77 is deleted from reservation information section 732, so if there are no reserved items stored in reservation information section 732 corresponding to the customer code, it is determined that all reserved items have been taken out. If there are still reserved items stored in reservation information section 732 corresponding to the customer code, it is determined that all reserved items have not been taken out.

[0109] If it is determined that all reserved items have been removed (Yes in S153), payment request information based on the product information of the items stored in the product information section 731 is transmitted to the reservation management server 3 (S155). Then, the control section 700 erases the information related to the customer stored in the product information section 731 and the reservation information section 732 (S156). Then, the control section 700 ends the process and returns to S111.

[0110] If the control unit 700 determines that the customer has not picked up all the reserved items (No in S153), the control unit 700 sends information indicating that the customer has left some reserved items behind to the reservation management server 3, along with the customer code of the customer (S154).Then, the control unit 700 ends the process and returns to S111.If the control unit 700 determines in S152 that the customer is not the person who made the reservation (No in S152), the control unit 700 executes the processes of S155 and S156.

[0111] Furthermore, if it is determined in S151 that it is possible to trace the path of a logged-in customer (No in S151), the control unit 700 determines whether the customer code has been read (S161). This process is for determining whether a customer who has once left shopping area Y has logged in again to retrieve a reserved item that they forgot to pick up. If it is determined that the customer code has been read (Yes in S161), the control unit 700 returns to S131 and determines whether to retrieve the item. If it is determined that the customer code has not been read (No in S161), the control unit 700 ends the process and returns to S111.

[0112] As described above, the mobile sales vehicle 5 of the embodiment comprises a loading platform 51 for carrying a product management device 7 that displays multiple types of products, a door 79 that opens and closes the loading platform 51 by rotating up and down, and one or more cameras 81, 86 that are attached to the door 79 and, when the door 79 is rotated upward, capture continuous images from above to below of the entire shopping area Y through which customers move to purchase products displayed on the product management device 7 loaded on the loading platform 51 and transmit the images to the product management device 7.

[0113] The mobile sales vehicle 5 of this embodiment can constantly capture images of customers moving through the shopping area Y to make purchases in the mobile sales vehicle 5. Therefore, customers in the shopping area can be reliably captured by the camera.

[0114] In addition, the reservation management server 3 of the embodiment is equipped with a loading platform 51 for carrying a product management device 7 which displays multiple types of products, a door 79 which opens and closes the loading platform 51 by rotating up and down, and one or more cameras 81, 86 which are attached to the door 79 and which, when the door 79 is rotated upward, continuously capture images from above to below of the entire shopping area Y where customers move to purchase products displayed on the product management device 7 loaded on the loading platform 51 and transmit the images to the product management device 7, a receiving unit 306 which receives payment request information indicating that a customer has left the shopping area Y from the product management device 7 in the mobile sales vehicle 5, and a payment unit 307 which executes payment processing for a product that the customer has picked up from the displayed products based on the received payment request information.

[0115] In such an embodiment of the reservation management server 3, the number of times the receiving unit 306 receives payment request information from the product management device 7 is reduced in order to prevent customers from frequently (unintentionally) straying from the shopping area Y due to the uninterrupted shopping area Y in the mobile sales vehicle 5, and the number of payment processes executed by the payment unit 307 can be reduced, thereby reducing the load on the reservation management server 3.

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

[0117] For example, in the embodiment, three cameras 81 and two cameras 86 are attached to each door 79. However, the present invention is not limited to this, and any number of cameras may be used as long as the imaging ranges of adjacent cameras are in contact with or overlap each other.

[0118] In the embodiment, the camera 86 is attached to the front and rear doors 79 of the mobile sales vehicle 5. However, the present invention is not limited to this, and the camera 86 may be attached to the front or rear of the mobile sales vehicle 5 itself.

[0119] In the embodiment, the door 79 that opens and closes in a gull-wing manner has been described as an example of the opening and closing part. However, the present invention is not limited to this, and the door 79 does not have to be of the gull-wing manner as long as it rotates in the vertical direction. In addition, something other than the door 79 that rotates in the vertical direction (for example, a top) may be used as the opening and closing part.

[0120] The program executed by the product management device 7 of the embodiment is provided in an installable or executable format file recorded on a computer-readable recording medium such as a CD-ROM, a flexible disk (FD), a CD-R, or a DVD (Digital Versatile Disc).

[0121] The program executed by the product management device 7 of the embodiment may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network. The program executed by the product management device 7 of the embodiment may be provided or distributed via a network such as the Internet.

[0122] Furthermore, the programs executed by the product management device 7 of the embodiment may be provided by being pre-installed in a ROM or the like. [Explanation of symbols]

[0123] 1. Mobile devices 3. Reservation Management Server 5 Mobile Sales Truck 7 Product management device 10. System 51 Cargo Bed 77 Shelf 78 Area 81 Camera 82 Weight Sensor 83 ID reader 84 Light emitting part 86 Camera 100 Control section 131 Reservation Information Department 132 Extracted product information department 142 Customer Code Department 221 Chord display button 300 Control section 301 2nd memory section 302 First Transmission Unit 303 Third Transmission Unit 304 Cancellation Judgment Department 305 4th Transmission Unit 306 Receiving unit 307 Payment Department 331 Reservation Management Department 332 Loading Products Department 333 Extraction product department 342 Customer Master 343 Product Master 700 Control section 701 1st memory section 702 Acquisition Department 703 Display control unit 704 Removal judgment unit 705 Second Transmission Unit 706 Cancellation Department 731 Product Information Department 732 Reservation Information Department 733 Sales Department 734 remaining units 742 Product location information department 743 Product Master 792 Roof 793 Side 3311 Customer Code Department 3312 Pre-orders 3313 Loading Information Department 3314 Extracted products department 3315 Payment Information Department 3321 Mobile Sales Vehicle Division 3322 Product Department 3421 Customer Code Department 3422 Customer Information Department 3423 Address information section 3424 Purchase History Section 3431 Product Code Section 3434 Cancellation 7321 Customer Code Department 7322 Pre-orders Y area [Prior art documents] [Patent documents]

[0124] [Patent Document 1] JP 2019-150123 A

Claims

1. a loading platform for carrying a product management device for displaying a plurality of types of products; an opening / closing unit that rotates vertically and also rotates upward to open the loading platform; one or more cameras attached to the opening / closing unit, which, when the opening / closing unit is rotated upward, continuously captures images from above to below of an entire shopping area through which customers move to purchase the products displayed in the product management device loaded on the platform, and transmits the captured images to the product management device; A mobile sales vehicle equipped with the following:

2. The camera is provided in a plurality of the opening and closing parts, The areas captured by adjacent cameras among the plurality of cameras are in contact with or overlap each other, The area constitutes the shopping area. The mobile sales vehicle according to claim 1.

3. The opening / closing section is opened upward by rotating upward around a rotation shaft provided on the upper part of the loading platform.

3. A mobile sales vehicle as claimed in claim 1 or 2.

4. The opening / closing portion is provided on both sides of the loading platform, The shopping area is the entire perimeter of the mobile sales vehicle.

3. A mobile sales vehicle as claimed in claim 1 or 2.

5. The cameras are further provided at the front and rear of the mobile sales vehicle.

5. A mobile sales vehicle as claimed in claim 1.

Images