Item management system, sales data processing device, program, and item management method

Abstract

To ensure that a contractor can remember to collect and store goods.SOLUTION: A goods management system includes: storage means for storing goods to be stored or collected; schedule memory means for memorizing a schedule for collecting goods from the storage means or a schedule for storing goods in the storage means; determination means for determining whether a predetermined event is present according to a collection or a storage corresponding to the schedule memorized by the schedule memory means; and notification control means that controls so that notification is made based on the determination result by the determination means.SELECTED DRAWING: Figure 29

Description

[Technical field]

[0001] The present invention relates to an article management system, a sales data processing device, a program, and an article management method. [Background technology]

[0002] For example, a system for transferring cleaning items, which includes a cleaning bag and a locker unit, is known (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2007-296315 A Summary of the Invention [Problem to be solved by the invention]

[0004] In the technology described in Patent Document 1, a provider (business) of the dry cleaning item delivery service collects the dry cleaning bags containing clothes that have been placed in a locker unit by customers (i.e., collects the dry cleaning items before they are cleaned) and stores the dry cleaning items in the locker unit once they have been cleaned. However, the above-mentioned collection and storage work is a manual task, and therefore the cleaning company may forget to collect or store the items such as dry cleaning goods.

[0005] The present invention has been made in view of the above circumstances, and has an object to enable contractors to remember to collect and store items. [Means for solving the problem]

[0006] One aspect of the present invention for solving the above-mentioned problems is an item management system comprising a storage means for storing items to be stored or retrieved, a schedule memory means for storing a schedule for retrieving items from the storage means or a schedule for storing items in the storage means, a judgment means for judging whether or not a specified event has occurred in response to the collection or storage corresponding to the schedule stored by the schedule memory means, and an alarm control means for controlling the system to issue an alarm based on the judgment result by the judgment means.

[0007] One aspect of the present invention is a program for causing a computer in an item management system to function as a schedule storage means for storing a schedule for retrieving items from a storage means for storing items to be stored or retrieved, or a schedule for storing items in the storage means, a judgment means for judging whether or not a specified event has occurred in response to the retrieval or storage corresponding to the schedule stored by the schedule storage means, and an alarm control means for controlling the issuance of an alarm based on the judgment result by the judgment means.

[0008] One aspect of the present invention is an item management method comprising a schedule storage step of storing a schedule for retrieving items from a storage means for storing items to be stored or retrieved, or a schedule for storing items in the storage means, a judgment step of judging whether or not a specified event has occurred in response to the retrieval or storage corresponding to the schedule stored in the schedule storage step, and an alarm control step of controlling so that an alarm is issued based on the judgment result by the judgment step. Effect of the Invention

[0009] According to the present invention, it is possible to obtain an effect that a contractor can remember to collect and store items. [Brief description of the drawings]

[0010] [Figure 1] FIG. 2 is a configuration diagram of a cleaning system according to the present embodiment. [Diagram 2] 1A and 1B are diagrams illustrating an example of the appearance of a locker according to an embodiment of the present invention. [Diagram 3]FIG. 2 is a diagram illustrating an example of the configuration of a POS terminal according to the present embodiment. [Figure 4] 1 is a diagram showing an example of the configuration of a locker (locker exclusively for reception) in this embodiment. FIG. [Diagram 5] 1 is a diagram showing an example of the configuration of a locker (return-only locker) in this embodiment. FIG. [Figure 6] FIG. 2 is a diagram illustrating an example of the configuration of a management device according to the present embodiment. [Figure 7] 10 is a flowchart showing an example of a processing procedure when a product is deposited in the present embodiment. [Figure 8] 13 is an example of a membership card screen in the present embodiment. [Figure 9] 13 is an example of a slip list screen according to the present embodiment. [Figure 10] 13 is an example of a slip details screen (a deposit slip screen, an electronic deposit slip) in the present embodiment. [Figure 11] 4 is an example of various information stored in the cleaning system in the present embodiment. [Figure 12] 4 is an example of various information stored in the cleaning system in the present embodiment. [Figure 13] 4 is an example of various information stored in the cleaning system in the present embodiment. [Figure 14] 4 is an example of various information stored in the cleaning system in the present embodiment. [Figure 15] 4 is an example of information stored in the cleaning system in the present embodiment. [Figure 16] 10 is a flowchart showing an example of a processing procedure relating to a method for specifying an available reservation date in the present embodiment. [Figure 17] 13 is an example of a locker return reservation screen displayed on a store clerk side display unit of the POS terminal in this embodiment. [Figure 18] 13 is an example of a customer locker return reservation screen displayed on a customer display unit of a POS terminal in this embodiment. [Figure 19] 13 is an example of a locker return reservation screen displayed on a store clerk side display unit of the POS terminal in this embodiment. [Figure 20] 4 is an example of information stored in the cleaning system in the present embodiment. [Figure 21] 13 is an example of a slip details screen (a deposit slip screen, an electronic deposit slip). [Figure 22] 10 is a flowchart illustrating an example of a processing procedure for reserving a locker in the present embodiment. [Figure 23] 10 is a flowchart illustrating an example of a processing procedure for reserving a locker in the present embodiment. [Figure 24] 13 is an example of a locker return schedule list screen in the present embodiment. [Diagram 25] 13 is an example of a locker return schedule list slip in this embodiment. [Figure 26] 11 is a flowchart showing an example of a processing procedure executed by the reception-only locker and the management device in this embodiment. [Figure 27] 10 is a flowchart showing a processing procedure executed by a return-only locker in this embodiment. [Figure 28] 10 is a flowchart showing a processing procedure executed by a return-only locker in this embodiment. [Figure 29] 10 is a flowchart showing an example of a process procedure executed by the management device and the POS terminal in the present embodiment in relation to a notification that a product has not been stored. [Diagram 30] 13A and 13B are diagrams showing examples of a non-storage notification screen in the present embodiment. [Diagram 31] 10 is a flowchart illustrating an example of a process performed by the management device in the present embodiment in relation to a notification that a product has not been stored. [Diagram 32] FIG. 13 is a diagram showing an example of a storage error notification screen in a modified example of the present embodiment. [Diagram 33] FIG. 13 is a diagram showing an example of a mis-storage slip in a modified example of this embodiment. [Diagram 34] FIG. 11 is a diagram showing an example of a reservation form setting screen in a modified example of the present embodiment. [Diagram 35] 13 is an example of a locker return schedule list screen according to a modified example of the present embodiment. [Diagram 36] FIG. 13 is a diagram showing an example of a deposit slip in a modified example of this embodiment. [Figure 37] FIG. 13 is a diagram showing an example of a customer information combination screen in a modified example of the present embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] <Embodiment> [Example of schematic configuration of cleaning system] FIG. 1 shows an outline of a configuration example of a cleaning system according to an embodiment of the present invention (hereinafter, "embodiment"). The cleaning system 1 of this embodiment is a system that supports cleaning work. In cleaning work, items such as clothes to be cleaned (hereinafter, also referred to as "goods") are accepted from users (customers) of the cleaning service, the accepted goods are cleaned, for example, at a factory, and the cleaned goods are returned to the user. The business receives a fee from the user, for example, as compensation for having the goods cleaned. In the following explanation, the terms "customer" and "user" are used synonymously.

[0012] The cleaning system 1 includes a management device 10, a POS terminal (business operator terminal) 20, a store portable terminal 30 (business operator terminal), a factory terminal 40, a user terminal 50, and a locker (an example of a storage means). The management device 10, the POS terminal 20, the factory terminal 40, the user terminal 50, and the lockers (100, 200, 300) are connected to a network 90. There are no particular limitations on the network 90. ​​For example, the network 90 may be one that utilizes a wireless LAN, a mobile phone network, the Internet, etc. The store portable terminal 30 can communicate with the POS terminal 20, for example, via a wireless LAN.

[0013] The management device 10 is, for example, a server that manages and provides various information related to the cleaning system 1. As an example, the management device 10 may be a cloud server that provides various services related to cleaning. Note that the management device 10 may be capable of executing push-type communication (notification) to other devices (for example, the user terminal 50). Furthermore, the management device 10 may or may not have a display unit and an operation unit. If the management device 10 does not have an operation unit or a display unit (for example, in the case of a server installed in a data center), maintenance of the management device 10 may be performed via another device (for example, a personal computer, not shown) that can communicate (connect) with the management device 10.

[0014] The POS terminal 20 is installed in a dry cleaning store (a dry cleaning agency) and is operated by a clerk at the dry cleaning store. The POS terminal 20 may be installed in an individual store (a dry cleaning store run by an individual) or in a chain store (each store in a chain). That is, the cleaning system 1 can be applied to both individual stores and chain stores. The store mobile terminal 30 is, for example, a tablet terminal used in a dry cleaning store. The POS terminal 20 may be a store other than a dry cleaning store, such as a convenience store, that handles products to be cleaned.

[0015] For example, the POS terminal 20 can be used to register items entrusted to the customer and process payments, while the store mobile terminal 30 can be used to display a list of items to be handed over to the customer and when the store clerk goes to the back room to retrieve the items to be handed over. For example, the POS terminal 20 may be configured as a portable terminal. In this case, the POS terminal 20 may also have the functions of the store portable terminal 30.

[0016] The factory terminal 40 is installed in a dry cleaning factory and operated by a person in charge of the dry cleaning factory. The factory terminal 40 is used, for example, to check products before cleaning and to report completion after cleaning. The factory terminal 40 may be, for example, a personal computer.

[0017] The user terminal 50 is a terminal operated by a user (for example, a smartphone, a tablet terminal, a personal computer, etc. owned by the user). The user terminal 50 may be configured to be able to download and install an application program from the management device 10 or a device (a server (not shown)) different from the management device 10 via the network 90. In this embodiment, an application program (hereinafter, sometimes simply referred to as a "cleaning app") for users who use the dry cleaning store (various cleaning-related services) in the cleaning system 1 is installed on the user terminal 50, and membership registration is completed using the cleaning app. The cleaning application may include data on various screens and various messages to be displayed on the display unit of the user terminal 50. The cleaning application may be started, executed, and terminated in response to a request from another program (an application program or an OS (Operating System)) in addition to being started, executed, and terminated in response to a user's operation. For example, the cleaning application may be resident on the user terminal 50 without displaying a screen, monitor whether information transmitted from another device (e.g., the management device 10, etc.) has been received, and, if information has been received, display a screen corresponding to the received information on the display unit without the user's operation.

[0018] Fig. 2 shows an example of the appearance of a locker. The lockers used in the cleaning system 1 are classified into lockers used when depositing products (i.e., lockers used for locker reception) and lockers used when handing over products (i.e., lockers used for locker return). FIG. 2A shows a dedicated locker 100 used only at the locker reception (hereinafter, may be referred to as a dedicated reception locker). FIG. 2B shows a locker 200 that is used for both locker reception and locker return (hereinafter, may be referred to as a common locker). FIG. 2(C) shows a dedicated locker 300 used only for locker returns (hereinafter, may be referred to as a dedicated return locker).

[0019] [Reception lockers] As shown in FIG. 2(A), the reception-only locker 100 includes, for example, an insertion slot 101 for inserting merchandise, a collection unit 102 for collecting merchandise inserted from the insertion slot, a card insertion and ejection slot 103 for inserting and ejecting cards, a display unit 104 for displaying various information, an input operation unit 105 for accepting input operations, a code recognition unit 106 for reading and recognizing barcodes and the like, an issuing slot 107 for issuing media such as receipts, a memory unit (not shown), and a control unit (not shown) for controlling the display on the display unit 104 and the locking of the insertion slot door (described below). The reception-only locker 100 does not necessarily have to have all of the above-mentioned components. For example, it may have either the input operation unit 105 or the code recognition unit 106, but not the other.

[0020] A curtain-type door (hereinafter referred to as the drop-in door) is provided at drop-in port 101. The drop-in door can be locked. When the drop-in door is unlocked, the user can insert merchandise (the merchandise to be deposited) into drop-in port 101. On the other hand, when the drop-in door is locked, the user cannot insert merchandise into drop-in port 101. The drop-in door is normally locked, and is unlocked when a predetermined condition is met, and is locked again after the merchandise has been inserted.

[0021] Various conditions can be considered as the predetermined condition for unlocking the insertion slot door. For example, authentication may be performed based on either or both of information on a card (e.g., a membership card, etc.) inserted into the card insertion / ejection slot 103 and information (e.g., a PIN number, etc.) input to the input operation unit 105, and the insertion slot door may be unlocked if the authentication is OK. Also, authentication may be performed based on information recognized by the code recognition unit 106 (e.g., barcode G11 displayed on the membership card screen, barcode information printed on the membership card, etc.), and the insertion slot door may be unlocked if the authentication is OK. Also, authentication may be performed based on information recognized by the code recognition unit 106 and information input to the input operation unit 105, and the insertion slot door may be unlocked if the authentication is OK.

[0022] There are various methods for recognizing the insertion of a commodity. For example, a sensor capable of detecting whether the slot door is in a normal state (a state in which the surface is vertical due to its own weight) or not (in other words, a sensor capable of detecting whether the slot door is pushed to the rear side or not) may be provided, and the insertion of a commodity may be recognized based on the detection result of the sensor. After the commodity is inserted, the slot door that was pushed to the rear side returns to its original state (normal state) due to its own weight, but the slot door may be locked (automatically locked) if the original state is maintained for a predetermined time (a time that can be considered as the end of all insertion operations even if there are multiple insertion operations by the same user, for example, 10 seconds) after returning to the original state.

[0023] A basket with casters can be placed inside the collection section 102. In other words, the product inserted into the insertion port 101 is placed inside the basket with casters. In addition, the product (basket with casters) in the collection section 102 can be removed from either the front or the back.

[0024] The collection section 102 is provided with a door (hereinafter referred to as the collection section door) at a position where products can be removed. The collection section door can be locked. When the collection section door is unlocked, store staff or the like can remove products (baskets with casters) from the collection section 102. On the other hand, when the collection section door is locked, store staff or the like cannot remove products from the collection section 102. The insertion port door is normally locked and is unlocked with a key managed by the store staff or the like, and is locked again after the products have been removed.

[0025] Although it has been explained that the products (baskets with casters) in the collection section 102 can be taken out from both the front and the back, for example, if the front side of the collection section 102 is designed to lead outside the store and the back side to lead inside the store, the baskets with casters can be taken out inside the store, eliminating the need to move the baskets with casters taken out outside the store into the store. In other words, if reception-only lockers 100 are installed so that the front side is outside the store and the back side is inside the store, the products in the collection section 102 can be taken out from both the front and the back, allowing the work of taking out the products to be carried out efficiently.

[0026] In addition, it may be possible to automatically collect products that have been dropped into an opening from outside the store (front) inside the store (rear) (without the need for preparations such as placing a wheeled basket into the collection section 102 or removing the wheeled basket containing the products from the collection section 102). For example, the bottom of the collection section 102 may be inclined so that products dropped in from outside the store naturally move to the inside of the store, and the inside of the store may simply be an opening without a collection door. This allows products dropped in from outside the store to automatically slide down into the opening on the inside of the store, so there is no need to worry about the capacity (volume) of the collection section 102 (for example, customers can drop products in at any time). In addition, the store clerk is no longer required to take out the appropriate products from within the collection section 102). In addition, a large basket with casters or the like can be placed under the opening to catch any items that slide out through the opening.

[0027] To facilitate the movement of merchandise towards the inside of the store, the material of the inclined portion (bottom portion) may be made slippery (material with a low coefficient of friction) (the surface may be plated, coated, etc. to make it slippery). Rotating bodies may be used in place of or in addition to the material (including coating, etc.). For example, cylindrical objects (rollers) or spherical objects may be embedded in part of the inclined portion, or may be embedded in the entire inclined portion (the rollers or balls may form the surface of the inclined portion).

[0028] The collection unit door may not have a key, but may be unlocked when a predetermined condition is met, similar to the input port door provided at input port 101.

[0029] Various conditions can be considered as the predetermined condition for unlocking the collection unit door. For example, authentication may be performed based on either or both of the information of the card inserted into the card insertion / ejection slot 203 (e.g., an administrator card managed by a store clerk or the like) and the information input to the input operation unit 105 (e.g., a PIN number or the like), and the collection unit door may be unlocked if the authentication is successful. For further security, the collection unit door may be unlocked using a key managed by a store clerk or the like in combination with the above authentication.

[0030] The reception-only locker 100 may be capable of communicating with other devices (for example, the POS terminal 20, the management device 10, etc.). In other words, the reception-only locker 100 may be equipped with a communication unit (not shown).

[0031] The management device 10, which is communicatively connected to the reception-only locker 100, may periodically (for example, every day) generate information (PIN number) to be entered into the input operation unit 105 and transmit the generated information to the user terminal 50 and the reception-only locker 100. In other words, as a specified condition for unlocking the deposit slot door, the user inputs information confirmed on the user terminal 50 (a PIN number generated in the management device 10) into the input operation unit 105, and the reception-only locker 100 compares the information sent from the management device 10 with the information input into the input operation unit 105 to perform authentication. As a specific example, the management device 10 may generate information (a personal identification number) to be input to the input operation unit 105 periodically (e.g., every day) and transmit the generated information to the POS terminal 20 and the reception-only locker 100. In other words, as a predetermined condition for unlocking the collection section door, a store clerk or the like may input information (such as a personal identification number generated in the management device 10) confirmed on the POS terminal 20 (or the store mobile terminal 30) into the input operation unit 105, and the reception-only locker 100 may compare the information transmitted from the management device 10 with the information input to the input operation unit 105 and perform authentication.

[0032] In addition, when the reception-only locker 100 can communicate with other devices, for example, as a predetermined condition for unlocking the collection section door, the POS terminal 20 may generate an OTP, generate a barcode by barcoding the OTP, issue a medium on which the barcode is printed (medium for opening the collection section door), and transmit the OTP to the reception-only locker 100 (transmitted to the reception-only locker 100 via the management device 10, or directly to the reception-only locker 100). The reception-only locker 100 may perform authentication based on information recognized by the code recognition unit 106 (specifically, the OTP obtained from the barcode printed on the medium for opening the collection section door) and information received from the outside (OTP received from the POS terminal 20 or the management device 10).

[0033] Furthermore, if the reception-only locker 100 can communicate with other devices, the reception-only locker 100 may request authentication from the other devices and obtain the authentication result from the other devices. When requesting authentication from the other devices, the reception-only locker 100 transmits information required for the other devices to perform authentication (for example, information on the card inserted into the card insertion / ejection slot 103, information entered into the input operation unit 105, information recognized by the code recognition unit 106, etc.) to the other devices.

[0034] [Common Locker] 2B, the common locker 200 includes an insertion slot 201, a collection unit 202, a card insertion and ejection slot 203, a display unit 204, an input operation unit 205, a code recognition unit 206, an issue slot 207, a memory unit (not shown), a control unit (not shown) that controls the display on the display unit 204 and the locking of a return slot door (described later), etc., a plurality of return slots (return units) 210, and a panel unit 210a corresponding to the return slots. Note that the insertion slot 201, collection unit 202, card insertion and ejection slot 203, display unit 204, input operation unit 205, code recognition unit 206, and issue slot 207 of the common locker 200 are similar to the insertion slot 101, collection unit 102, card insertion and ejection slot 103, display unit 104, input operation unit 105, code recognition unit 106, and issue slot 107 of the reception-only locker 100, and therefore description thereof will be omitted. It is not necessary for the common locker 200 to have all of the above-mentioned components. For example, it is acceptable for the common locker 200 to have either the input operation unit 205 or the code recognition unit 206, but not the other.

[0035] The common locker 200 may be capable of communicating with other devices (for example, the POS terminal 20, the management device 10, etc.) In other words, the common locker 200 may be equipped with a communication unit (not shown).

[0036] The shared locker 200 shown in FIG. 2(B) has a total of 11 return slots 210, excluding the panel portion 210a in the first left column of the upper row, in two rows and six columns. In FIG. 2(B), the return slot at the bottom left is given the reference number 210 to represent the 11 return slots. Each return slot is assigned a return slot number (sometimes called a "door number") as a management number. For example, specifically, as shown in FIG. 2(B), the return slot numbers are "H12" at the bottom left, "H21" at the top second row from the left, "H22" at the bottom second row from the left, ..., "H61" at the top right, and "H62" at the bottom right. Figure 2(B) shows an example of a case in which the return port units in the shared locker 200 are configured by connecting two units: one including return ports with return port numbers H12, H21, H22, H31, and H32, and the other including return ports with return port numbers H41, H42, H51, H52, H61, and H62. Each return port may be marked, for example by attaching a sticker indicating the return port number, so that the return port number of each return port in the common locker 200 can be identified.

[0037] Each of the return slots 210 is provided with a door (hereinafter referred to as the return slot door). Each of the return slot doors can be locked individually. When the return slot door is unlocked, a store employee or the like can store products (products to be returned to the user) in the return slot 210. When the return slot door is unlocked, the user can remove products from the return slot 210. On the other hand, when the return slot door is locked, the user cannot remove products from the return slot 210. Furthermore, when the return slot door is locked, store staff cannot store products in the return slot 210. The return slot door is normally locked and is unlocked when a predetermined condition is met. The door is locked again after products are stored or removed.

[0038] Various conditions can be considered as the predetermined condition for unlocking the return door. [Prescribed conditions for storing products (when store staff unlock the door)] For example, authentication may be performed based on information recognized by the code recognition unit 206 (information obtained from a barcode printed on a medium issued to each user who wishes to return items to a locker), and the corresponding return door (the return door of the return slot for storing items to be returned to the user) may be unlocked if the authentication is OK. The details of the unlocking method will be described later. Also, instead of or in addition to the above unlocking method, for example, authentication may be performed based on either or both of information on a card inserted into the card insertion / ejection slot 203 (e.g., an administrator card managed by a store clerk or the like) and information input into the input operation unit 205 (e.g., a PIN number), as in the case of unlocking the collection unit door, and the return door may be unlocked if the authentication is OK.

[0039] [Prescribed conditions for taking out the product (when the user unlocks the door)] For example, similar to the case of unlocking the insertion slot door, authentication may be performed based on either or both of the information of the card (membership card, etc.) inserted into the card insertion and ejection slot 203 and the information (personal identification number, etc.) input into the input operation unit 205, and the corresponding return slot door (the return slot door of the return slot storing the product to be returned by the user) may be unlocked if the authentication is OK. Also, authentication may be performed based on the information recognized by the code recognition unit 206 (the barcode G11 displayed on the membership card screen, the barcode information printed on the membership card, etc.), and the insertion slot door may be unlocked if the authentication is OK. Also, authentication may be performed based on the information recognized by the code recognition unit 206 and the information input into the input operation unit 205, and the insertion slot door may be unlocked if the authentication is OK. Note that, for further security, authentication may be performed based on the information of the card inserted into the card insertion and ejection slot 203, the information input into the input operation unit 205, and the information recognized by the code recognition unit 206, and the insertion slot door may be unlocked if the authentication is OK.

[0040] There are various possible methods for recognizing the removal of a product. For example, a sensor capable of detecting whether the return door is in a normal state (closed state) or not (in other words, a sensor capable of detecting whether the return door is in an open state or not) may be provided, and the removal of a product may be recognized based on the detection result of the sensor. After the product is removed, the return door may be returned to its original state (normal state) by a biasing force or the like. Furthermore, the return door may be locked (automatically locked) if the original state is maintained for a predetermined time (a time during which all removal operations are considered to be completed even if there are multiple removal operations by the same user, for example, one minute) after the return to the original state.

[0041] It is also possible to provide a light emitting unit corresponding to each return slot 210. For example, in the example shown in Fig. 2(B), a light emitting unit 211 is provided above each return slot 210. Also, a rod or hook may be provided inside the return slot 210 to store the products neatly.

[0042] Although the common locker 200 shown in FIG. 2(B) has 12 return slots, the common locker 200 may have a number other than 12 return slots.

[0043] [Return lockers] The return-only locker 300 includes, for example, a card insertion / ejection port (not shown), a display unit (not shown), an input operation unit (not shown), a code recognition unit (not shown), an issue port (not shown), a memory unit (not shown), a control unit (not shown) that controls the display on the display unit and locking of the return port door (described later) and the like, and multiple return ports (return units) 310. In the case of the return-only locker 300 shown in Fig. 2(C), the card insertion / ejection port, display unit, input operation unit, code recognition unit, issue port, and the like are arranged on the panel unit 301a in the upper left portion 301, but are not shown for convenience of the drawing.

[0044] It is also possible to provide a light emitting unit corresponding to each return slot 310. For example, in the example shown in Fig. 2(C), a light emitting unit 311 is provided above each return slot 310. Also, a rod or hook may be provided inside the return slot 310 to store the products neatly.

[0045] Although the return-only locker 300 shown in FIG. 2(C) has five return slots, the return-only locker 300 may have a number other than five.

[0046] [Example of POS terminal configuration] An example of the configuration of the POS terminal 20 will be described with reference to Fig. 3. The POS terminal 20 in the figure includes a CPU (Central Processing Unit) 21, a RAM (Random Access Memory) 22, a storage unit 23, an input unit 25, a communication unit 24, an input unit 25, a store clerk display unit 26, a customer display unit 27, and a printing unit 28.

[0047] The CPU 21 is a central processing unit of the POS terminal 20, and controls the operation of the POS terminal 20 by reading out a program stored in the storage unit 23, expanding the program in the RAM 22, and executing each step of the expanded program. The RAM 22 is a main storage device of the POS terminal 20, and stores information used by the CPU 21 for calculations. The storage unit 23 is an auxiliary storage device of the POS terminal 20 and stores various information corresponding to the POS terminal 20.

[0048] The communication unit 24 communicates via a network. This allows the POS terminal 20 to communicate with, for example, other POS terminals and management devices installed in the store, and further with terminal devices and servers installed at the headquarters or the like. The communication unit 24 may be capable of short-range wireless communication, for example. This allows the POS terminal 20 to communicate with a store mobile terminal 30 carried by a store clerk or the like via short-range wireless communication. The POS terminal 20 may also be capable of communicating with a user terminal 50 carried by a user in the store via short-range wireless communication.

[0049] The input unit 25 is a section that accepts various inputs to the POS terminal 20. The input unit 25 may include physical keys, buttons, and other operators provided on the POS terminal 20. Furthermore, when the display units (clerk-side display unit 26, customer-side display unit 27) are configured as touch panels, the input unit 25 may include a touch pad arranged on the display surface of the display units. Furthermore, the input unit 25 may include a scanner for reading code information and the like, a card reader for reading information from various cards, and the like.

[0050] The store clerk display unit 26 is provided in the POS terminal 20 so that the display can be visually confirmed by the store clerk who operates the POS terminal 20, and displays various information according to the control of the CPU 21.

[0051] The customer-side display unit 27 is provided in the POS terminal 20 so that a user (customer) who is served by a store clerk who operates the POS terminal 20 can view the display, and displays various information according to the control of the CPU 21.

[0052] The store clerk display unit 26 and the customer display unit 27 may be external display devices connected, for example, by wire or wirelessly, to the main body of the POS terminal 20. In this case, the external display device may have a display surface configured as a touch panel, for example, so that operations can be performed on the display surface.

[0053] The printing unit 28 prints on the loaded paper. In this embodiment, the printing unit 28 can print store receipts, factory receipts, customer receipts, etc., during accounting. In other words, the issuance of various slips by the POS terminal 20 is realized by the printing unit 28 printing.

[0054] [Example of locker configuration for reception use] An example of the configuration of the reception-only locker 100 will be described with reference to Fig. 4. In this figure, the same parts as those in Fig. 2(A) are given the same reference numerals and the description will be omitted as appropriate. The reception-only locker 100 in the figure includes a CPU 121, a RAM 122, a storage unit 123, a communication unit 124, a card reader 125, a printing unit 126, and a collection unit sensor 127. The CPU 121 is the central processing unit of the reception-only locker 100, and controls the operation of the reception-only locker 100 by reading out a program stored in the memory unit 123, expanding it into the RAM 122, and executing each step of the expanded program. The RAM 122 is the main memory device of the reception locker 100, and stores information used by the CPU 121 for calculations. The storage unit 123 is an auxiliary storage device of the reception-only locker 100 and stores various information corresponding to the reception-only locker 100. The communication unit 124 communicates via a network. This allows the reception-only locker 100 to communicate with, for example, the management device 10. The communication unit 124 may be capable of short-range wireless communication. In this case, the reception-only locker 100 may be capable of communicating with a store mobile terminal 30 carried by a store clerk or a user terminal 50 carried by a user in the vicinity via short-range wireless communication.

[0055] The card reader 125 reads information on a card inserted into the card insertion / ejection slot 103 . The printing unit 126 prints on the loaded paper and ejects slips such as receipts from the issuing port 107. The collection section sensor 127 detects a predetermined state of the collection section 102. For example, the collection section sensor 127 may detect the state of the collection section door (e.g., open / closed, locked / unlocked, etc.). The collection section sensor 127 may also detect the volume, weight, etc. of the articles placed in the collection section 102.

[0056] [Example of return locker configuration] An example of the configuration of the return locker 300 will be described with reference to Fig. 5. In this figure, the same parts as those in Fig. 2(C) are given the same reference numerals and the description thereof will be omitted as appropriate. The reception-only locker 100 in the figure includes a CPU 321, a RAM 322, a storage unit 323, a communication unit 324, a card reader 325, a printing unit 326, and a return port sensor 327. The CPU 321 is the central processing unit of the return-only locker 300, and controls the operation of the return-only locker 300 by reading out a program stored in the memory unit 323, expanding it into the RAM 322, and executing each step of the expanded program. The RAM 322 is the main memory device of the return locker 300, and stores information used by the CPU 321 for calculations. The memory unit 323 is an auxiliary memory device of the return locker 300 and stores various information corresponding to the return locker 300. The communication unit 324 communicates via a network. This allows the return locker 300 to communicate with, for example, the management device 10. The communication unit 324 may be capable of short-range wireless communication. In this case, the return locker 300 may be capable of communicating with a store mobile terminal 30 carried by a store clerk or a user terminal 50 carried by a user in the vicinity via short-range wireless communication.

[0057] The card reader 325 reads information on a card inserted into a card insertion / ejection slot provided in the panel section 301a. The printing unit 326 prints on the loaded paper and ejects slips such as receipts from an issuing port provided in, for example, the panel unit 301a.

[0058] The return port sensor 327 is provided corresponding to each return port 310, and detects a predetermined state of the corresponding return port 310. For example, the return port sensor 327 may detect the state of the collection section door (e.g., open / closed, locked / unlocked, etc.). The collection section sensor 127 may detect the weight of the items placed in the collection section 102, etc.

[0059] The common locker 200 may have a configuration that combines the configurations of Figures 4 and 5. When combining the configurations of Figures 4 and 5, parts having the same functions may be appropriately made common.

[0060] [Example of management device configuration] An example of the configuration of the management device 10 will be described with reference to Fig. 6. The management device 10 in Fig. 6 includes a CPU 11, a RAM 12, a storage unit 13, and a communication unit 14. The CPU 11 is a central processing unit of the management device 10, and controls the operation of the management device 10 by reading out a program stored in the storage unit 13, loading it into the RAM 12, and executing each step of the loaded program. The RAM 12 is a main storage device of the management device 10, and stores information that the CPU 11 uses for calculations. The storage unit 13 is an auxiliary storage device of the management device 10 and stores various types of information corresponding to the management device 10. The communication unit 14 performs communication via a network, which allows the management device 10 to communicate with the POS terminal 20, the factory terminal 40, the user terminal 50, the lockers (100, 200, 300), and the like.

[0061] The management device 10 may also be provided with an operation unit and a display unit. In this case, the management device 10 may be configured to allow the same operations as those performed by a store clerk on the POS terminal 20 to be performed. Accordingly, the display unit of the management device 10 may be configured to display various screens similar to those displayed on the POS terminal 20.

[0062] Next, a basic process for accepting an item by the cleaning system 1 will be described with reference to Figures 7 to 10. In the description of Figures 7 to 10, a case where the user terminal 50 is a smartphone will be taken as an example.

[0063] Fig. 7 is a flowchart showing an example of a processing procedure for an operation when depositing an item. Specifically, the flowchart in Fig. 7 shows an example of an operation when depositing an item from a user (member) who visits a store (cleaning store) (i.e., in the case of normal deposit at the store).

[0064] Fig. 8 to Fig. 10 are examples of various screens displayed on the user terminal 50. Specifically, Fig. 8 shows a membership card screen, Fig. 9 shows a slip list screen, and Fig. 10 shows a slip details screen (sometimes called a deposit slip screen or electronic deposit slip). In the explanation of Fig. 7 to Fig. 10, a cleaning app executed on the user terminal 50 (smartphone) displays the above screens (membership card screen, slip details screen, slip list screen).

[0065] Each step in the flowchart of FIG. 7 will be described below with reference to FIGS. 8 to 10 as appropriate. Step S10: The user terminal 50 displays a membership card screen as shown in Fig. 8 on the display unit (touch panel). The membership card screen may be an initial screen of the cleaning app. In other words, the membership card screen may be the screen that is first displayed on the display unit when the cleaning app is launched on the user terminal 50. The user terminal 50 may display a membership card screen that it stores on the display unit, or may obtain a membership card screen from the management device 10 and display it on the display unit.

[0066] When acquiring a membership card screen from management device 10 and displaying it on the display unit, user terminal 50 may transmit app communication identification information (or app user identification information) to management device 10. That is, user terminal 50 may acquire a membership card screen from management device 10 and display it on the display unit by transmitting app communication identification information (or app user identification information) to management device 10. Management device 10 may refer to the customer master file, identify a user (customer code) based on the app communication identification information (or app user identification information) acquired from user terminal 50, and transmit a membership card screen of the identified user to user terminal 50.

[0067] The membership card screen shown in Fig. 8 displays rank information, point information (number of available points), a barcode G11, a deposit slip icon G12, and the like. The barcode G11 is a barcoded version of a customer code. The barcode G11 displayed on a membership card screen for a certain user may be generated by the management device 10 based on the customer code of that user. For example, the management device 10 may assign (number) a customer code when registering as a member, generate a barcode based on the assigned customer code, and store it as the barcode to be displayed on the membership card screen for that user.

[0068] The horizontal row at the bottom of the membership card screen - "Membership card," "Deposit slip," "Notice," "Coupon," and "Survey" - indicates the type of screen currently being displayed. The same is true for the slip list screen shown in Figure 9 and the bottom row of the slip details screen shown in Figure 10. Note that if the screens are categorized into the five types "Membership card," "Deposit slip," "Notice," "Coupon," and "Survey," the slip list screen and slip details screen are categorized as "Deposit slips," so they are labeled "Deposit slips" both when the slip list screen is displayed (Figure 9) and when the slip details screen is displayed (Figure 10).

[0069] Step S11: The POS terminal 20 reads the barcode on the membership card screen through an operation (motion) of a store clerk, thereby allowing the POS terminal 20 to recognize the customer code of the user who has visited the store. Step S12: The POS terminal 20 transmits to the management device 10 the customer code recognized by reading the barcode.

[0070] Step S13: The management device 10 receives the customer code from the POS terminal 20. Step S14: The management device 10 extracts customer information corresponding to the customer code received in step S13 from a customer master file or the like. Step S15: The management device 10 transmits the customer information extracted in step S14 to the POS terminal 20.

[0071] Step S16: The POS terminal 20 receives the customer information from the management device 10. Step S17: The POS terminal 20 displays the customer information received in step S16 on the store clerk display unit 26.

[0072] The POS terminal 20 may display a registration screen (not shown) on the store clerk display unit 26 based on receiving the customer information in step S16, and display the customer information on the registration screen in step S17. Alternatively, the POS terminal 20 may display a customer information display screen (not shown) different from the registration screen on the store clerk display unit 26 based on receiving the customer information in step S16, and display the customer information on the customer information display screen in step S17.

[0073] The customer information displayed by the POS terminal 20 in step S17 may be a part of the information stored in a customer master file, etc. In other words, the POS terminal 20 may display a part of the information stored in a customer master file, etc. In addition, in step S14, the management device 10 may extract only the information displayed by the POS terminal 20 in step S17.

[0074] If the POS terminal 20 stores the customer information to be displayed in step S17, there is no need to inquire of the management device 10 (that is, the processes in steps S12 to S16 may be omitted).

[0075] Step S18: The POS terminal 20 registers the deposited products through the operation of the store clerk. Specifically, for example, the POS terminal 20 accepts input of information on each deposited product (product type, processing type) and the tag number of the tag attached to each deposited product on the registration screen. In addition, if customer information is displayed on a customer information display screen rather than the registration screen in step S17, the registration screen is displayed by the store clerk's operation, and then input of information about each deposited item (item type, processing type), tag numbers of tags attached to each deposited item, etc. is accepted.

[0076] Step S19: The POS terminal 20 displays the scheduled completion date. Specifically, the POS terminal 20 refers to the service basic file to obtain the number of days required for each of the deposited products, calculates the scheduled completion date for each of the deposited products based on the obtained number of days required for each of the deposited products, and displays the calculated scheduled completion date for each of the deposited products on the store clerk side display unit 26. In addition, the POS terminal 20 may display the latest scheduled completion date among the scheduled completion dates of each of the deposited items (i.e., the scheduled completion date when all of the deposited items will be completed) on the store clerk display unit 26 instead of or in addition to the scheduled completion date of each of the deposited items.

[0077] In step S19, if the POS terminal 20 does not store the service basic file, it is necessary to inquire of the management device 10, which stores the service basic file, about the number of days required for each of the stored items. However, if the POS terminal 20 stores the service basic file, the above inquiry is not necessary.

[0078] Step S20: The POS terminal 20 settles the payment. Specifically, the POS terminal 20 refers to the service basic file to obtain the fees for each of the deposited products, calculates the total fee by adding up the obtained fees for each of the deposited products, and displays the total fee together with the fees for each of the deposited products on the store clerk side display unit 26. Next, the POS terminal 20 recognizes the deposit amount through the clerk's operation (inputting the amount to be deposited according to the deposit amount) and calculates the amount of change from the total fee and the deposit amount. The POS terminal 20 then displays the deposit amount and the amount of change on the clerk's display unit 26 (the payment is completed). The clerk checks the amount of change displayed on the clerk's display unit 26, takes out the change, and hands it to the customer.

[0079] In step S20, if the POS terminal 20 does not store the service basic file, it is necessary to inquire about the price of each of the deposited items from the management device 10 that stores the service basic file, but if the POS terminal 20 stores the service basic file, the above inquiry is not necessary.

[0080] Furthermore, in step S20, if the POS terminal 20 is equipped with an automatic change dispenser (or if an automatic change dispenser is connected to the POS terminal 20), the POS terminal 20 will display the total charge etc. on the clerk's display unit 26, and then recognize the deposited amount through the clerk's operation (inserting the deposit into the coin slot of the automatic change dispenser), and calculate the change amount from the total charge and the deposited amount.The POS terminal 20 will then display the deposited amount and the change amount on the clerk's display unit 26, and dispense the change into the coin slot of the automatic change dispenser (closing the price).

[0081] In step S20, the POS terminal 20 prints and issues receipts such as a receipt slip and a factory copy.

[0082] Step S21: The POS terminal 20, in response to an operation by a store clerk, transmits the information acquired up to step S20 as transaction information at the time of depositing the goods to the management device 10. For example, the POS terminal 20 transmits transaction information to the management device 10, including a slip number, deposit date and time, store code, store clerk code, customer code, deposit category (specifically, deposit category "1 (normal store deposit)"), tag numbers of each deposited goods, product type, processing type, and the like. The slip number may be assigned (numbered) by the POS terminal 20. The store code and the clerk code are stored in a memory unit (RAM 22 or memory unit 23) of the POS terminal 20. The clerk code is stored in the memory unit of the POS terminal 20 by an operation of the clerk (for example, inputting the number of clerk codes, reading a clerk card with a card reader (not shown), etc.).

[0083] Although the deposit points are stored in the electronic slip file (see FIG. 12), the management device 10 can recognize the deposit points based on the number of pieces of information about the deposited items (e.g., the number of tag numbers) sent from the POS terminal 20. Therefore, the POS terminal 20 does not have to send the deposit points to the management device 10. In other words, the POS terminal 20 may send transaction information that includes the deposit points, or may send transaction information that does not include the deposit points. Similarly, the POS terminal 20 may send transaction information that includes the total fee, or may send transaction information that does not include the total fee.

[0084] Furthermore, the deposited item number is stored in the deposited item information file (see FIG. 13), but the management device 10 can assign (number) the deposited item number based on the slip number and the deposited item amount. Therefore, it is not necessary for the POS terminal 20 to assign a deposited item number to each deposited item and transmit it to the management device 10. In other words, the POS terminal 20 may transmit transaction information including the deposited item number of each deposited item, or may transmit transaction information that does not include the deposited item number of each deposited item.

[0085] In addition, the deposited product information file (see Figure 13) stores information regarding the delivery reservation (reservation category, delivery category), and if the store clerk inputs information regarding the delivery (input of information corresponding to the delivery category) before step S20, the POS terminal 20 transmits transaction information including the input information regarding the delivery to the management device 10.

[0086] Step S22: The management device 10 receives from the POS terminal 20 the transaction information at the time of depositing the product. Step S23: The management device 10 updates various files based on the transaction information received in step S22. Specifically, the management device 10 adds new slip number information (record) to the electronic slip file, and adds new deposited product number information (record) to the deposited product information file. When the management device 10 receives transaction information including input information related to a specific product, it also updates the specific product management file.

[0087] Step S24: The management device 10 updates the slip list screen (updates the screen information to add a slip) based on the transaction information received in step S22 (that is, by referencing the various files updated in step S23).

[0088] Step S25: The management device 10 generates a slip details screen (generates screen information for the slip to be added) based on the transaction information received in step S22 (that is, by referencing the various files updated in step S23).

[0089] Step S26: The management device 10 transmits to the user terminal 50 the screen information for the slip list screen updated in step S24 and the screen information for the slip details screen generated in step S25.

[0090] Step S27: The user terminal 50 receives the screen information from the management device 10, and stores the received screen information in the storage unit. Then, the flow chart of FIG.

[0091] Since the task of attaching a tag to each deposited item takes time, if this task is postponed, the input of the tag number in step S18 will also be postponed. In step S21, transaction information including the tag number needs to be transmitted to management device 10, so the processing of step S21 will also be postponed. In other words, in the processing of steps S10 to S27 described above, the processing up to step S20 (the processing of step S18 is temporarily terminated with the input of the tag number pending and proceeds to step S19) may be performed, and the remaining processing of step S18 (input of the tag number) may be performed before proceeding to the processing of step S21 and subsequent steps, rather than immediately proceeding to step S21.

[0092] Here, the transitions between the membership card screen in FIG. 8, the slip list screen in FIG. 9, and the slip details screen in FIG. 10 will be described. When the deposit slip icon G12 is operated (e.g., tapped) on the membership card screen shown in Fig. 8, the user terminal 50 displays a slip list screen as shown in Fig. 9. The slip list screen displays a list of slip summaries for all stores.

[0093] Furthermore, when an operation is performed on the electronic slip field G21 in the third row from the top on the slip list screen shown in Fig. 9, the user terminal 50 displays a slip details screen as shown in Fig. 10. The slip details screen corresponds to a conventional deposit slip and receipt. The slip details screen displays detailed information about the slip operated on the slip list screen.

[0094] When depositing goods, the processing of steps S26 and S27 in FIG. 7 may not be performed, and instead, when the user performs an operation, the screen information of the slip list screen updated in step S24 and the screen information of the slip details screen generated in step S25 may be sent from the management device 10 to the user terminal 50.

[0095] On the slip details screen, "In custody" corresponds to the progress categories "1" to "5" in the held product information file (Fig. 13) and indicates that the item is not yet delivered. "Delivered" corresponds to the progress category "9" in the held product information file (Fig. 13) and indicates that the item has been delivered. When there are multiple products, the user terminal 50 may simply sort them in order of expected completion date, but when there is a mixture of "in storage" and "delivered" products, the user terminal 50 may display "in storage" products with priority. In the example shown in FIG. 10, "in storage" products (products in columns G34 and G35) are displayed above "delivered" products (products in column G36). Also, "delivered" products (products in column G36) are displayed grayed out. When sorted in order of expected completion date, the product in column G36 will be above the products in columns G34 and G35. The back icon G31 is a button for returning to the previous screen (the slip list screen (FIG. 9)). Users can get an overview of the entire transaction (list of vouchers) on the voucher list screen (Figure 9), and can check the details of each transaction (each voucher) on the voucher details screen (Figure 10).

[0096] The deposited goods are delivered to a dry cleaning factory and cleaned. When the cleaning is completed, an operator inputs information that the goods are finished into the factory terminal 40, and this information is transmitted to the management device 10. The management device 10, which has received the information that the goods are finished, updates the progress category of the deposited goods information file (FIG. 13) (specifically, updates it to "3 (finished)"). The deposited goods that have been cleaned are delivered to the store. When the goods arrive at the store, a store clerk inputs information that the goods have arrived at the store into the POS terminal 20, and this information is transmitted to the management device 10. The management device 10, which has received the information that the goods have arrived at the store, updates the progress category of the deposited goods information file (specifically, updates it to "4 (available)"). Furthermore, when the delivery of the goods is completed, the store clerk inputs information that the goods have arrived at the store into the POS terminal 20, and this information is transmitted to the management device 10. The management device 10, which has received the information that delivery of the product has been completed, updates the progress category of the deposited product information file (specifically, updates it to "9 (delivery completed)").

[0097] Furthermore, when the user has not yet completed checking the current status of a specific product, the progress category in the stored product information file (FIG. 13) is "2 (on hold)", and when the user has completed checking the current status, the management device 10 updates the progress category (specifically, updates it to "1 (stored product)"). When a reservation for product delivery is being accepted from a user, the progress category is "5 (delivery reservation made)", and when delivery of the product is completed, the management device 10 updates the progress category (specifically, updates it to "9 (delivery)").

[0098] In the example shown in FIG. 10, the information indicating the progress status is of two types, "in custody" and "delivered", but the information indicating the progress status does not have to be of two types. As an example, the information may be of four types, "not yet finished", "finished", "available for delivery", and "delivered". "Not yet finished" corresponds to the progress category "1" or "2", and indicates that the item is not yet finished at the factory. "Finished" corresponds to the progress category "3", and indicates that the item is finished at the factory. "Available for delivery" corresponds to the progress category "4", and indicates that the item is available for delivery. "Delivered" corresponds to the progress category "9", and indicates that the item has been delivered. As another example, "on hold", which corresponds to the progress category "2", and indicates that the cleaning work is on hold, may be displayed. Also, "reserved for delivery", which corresponds to the progress category "5", and indicates that a reservation for delivery is being accepted, may be displayed. In addition, in the case of locker return, a message such as "Locker return reserved" will be displayed (Figure 21). When displaying the progress of a reservation, such as "reserved for delivery" or "reserved for locker return," the reservation date may also be displayed.

[0099] An example of information stored in the cleaning system 1 of the present embodiment will be described below with reference to FIGS. [Customer master file] 11A shows an example of a customer master file. The customer master file may be stored in the management device 10, the POS terminal 20, etc. In this embodiment, the case where the management device 10 stores the customer master file is taken as an example. The customer master file is a file that stores various basic information about customers (members) who are users. The customer master file stores, in association with the customer code, the name (in kanji), name (in hiragana), address, contact information, email address, phone number (1), phone number (2), application communication identification information, birthday, membership registration date, registered store (store code), etc. The name (in kanji), name (in hiragana), address, etc. are information obtained from the user when registering as a member.

[0100] The customer code is information for identifying each user in the cleaning system 1. For example, when a member is registered, the management device 10 may assign (number) a unique customer code.

[0101] The email address is the email address of the email to be sent to the user. For example, it may be the email address of the user terminal 50 of the user, or it may be the email address of a terminal (not shown) of the user different from the user terminal 50.

[0102] The telephone number (1) and the telephone number (2) are telephone numbers for calling the user. For example, if the user terminal 50 of the user is a smartphone, the telephone number (1) may be the telephone number of the user terminal 50 (smartphone) of the user, and the telephone number (2) may be the telephone number of the home landline of the user.

[0103] The application communication identification information is information for performing communication of a cleaning application executed on the user terminal 50 of the user. The application communication identification information may be any information capable of identifying the user terminal 50 of the user in communication of the cleaning application, and may be, for example, an IP address of the user terminal 50, individual identification information of the user terminal 50, a telephone number of the user terminal 50, or identification information (such as a token) different from the individual identification information. The application communication identification information may be fixedly assigned to the user terminal 50, or may be temporarily assigned to the user terminal 50 (for example, may change every time the cleaning application is started). In the case where the application communication identification information is temporarily assigned, the latest application communication identification information may be stored.

[0104] In addition, in addition to the application communication identification information for identifying the user terminal 50 in communication of the cleaning application, application user identification information (for example, a user ID, etc.) for identifying a user in the cleaning application may be stored.

[0105] The registered store is information indicating the store (cleaning store) where the user has registered as a member, and in this embodiment, a store code is used. If the user has registered as a member at a location other than a store (for example, if the user has registered as a member from home or work via the cleaning app using the user terminal 50), the registered store may be the store automatically selected by the cleaning app when registering as a member, or the store selected by the user from among the candidates presented by the cleaning app when registering as a member, or the store selected freely by the user when registering as a member. When registering as a member, the cleaning app may search for the store closest to the user's home based on information input by the user (for example, address, area code, city code, etc.), and may automatically select the registered store as the registered store, or may present the store to the user as a selection candidate.

[0106] In this embodiment, the store code is a four-digit code in total, with the upper two digits being "TP" and the following two digits being a store-specific number (00 to 99, etc.).

[0107] [Customer performance summary file] 11B shows an example of a customer performance tally file. The customer performance tally file may be stored in the management device 10, the POS terminal 20, etc. In this embodiment, the case where the management device 10 stores the customer performance tally file is taken as an example. The customer performance tally file is a file that stores information regarding the usage record of services (various cleaning-related services provided by the cleaning system 1) for each customer (member) who is a user. The customer performance tally file shown in Fig. 11(B) stores, in association with a customer code, performance information (rank, last date of use, frequency of use, average unit price) totaling all stores and performance information (rank, last date of use, frequency of use, average unit price) of a main store. In this embodiment, the performance is tallied once a month (for example, on a specific day of each month), and the tally result is stored in the customer performance tally file.

[0108] The last usage date is the date of the last usage. The usage frequency is the number of times in the past month. The usage amount is the total usage amount in the past month. The rank is information indicating the user's evaluation (degree of contribution) and is calculated based on one or more of the last usage date, usage frequency, and usage amount in the past month or more. As an example, a user who has used the service 12 times or more in the past 6 months and whose usage amount in the past 6 months is 24,000 yen or more may be ranked at the highest (e.g., S rank), and a user who has used the service zero times in the past 12 months may be ranked at the lowest (e.g., D rank). Note that instead of or in addition to the usage amount, the average unit price for the past month may be calculated and stored in the customer performance summary file.

[0109] [Point management file] 11C shows an example of a point management file. The point management file may be stored in the management device 10, the POS terminal 20, etc. In this embodiment, the case where the management device 10 stores the point management file is taken as an example. The points management file is a file that stores information regarding points that are awarded based on the service usage history and can be used in place of cash (for example, 1 point is awarded for every 200 yen, and 1 point can be used as 100 yen in place of cash). 11C stores the number of available points and the like in association with a customer code. The point management file may also be used to manage (store) the expiration date.

[0110] The point management file shown in Fig. 11 has a configuration in which the points to be managed are common to all stores in a chain (points awarded at each store are added together and can be used at any store). However, in cases where points are managed individually at each store in a chain (points awarded at a store can only be used at that store), the number of available points and the like may be stored in association with the store code and customer code (i.e., by store code and customer code), for example.

[0111] [Electronic voucher file] 12 shows an example of an electronic slip file. The electronic slip file may be stored in either the management device 10 or the POS terminal 20. In this embodiment, an example is given in which the management device 10 stores the electronic slip file. The electronic invoice file is a file that stores information about electronic invoices that show transaction details for various cleaning services. 12 stores, in association with the slip number, the receipt date and time, store code, clerk code, customer code, receipt category, number of items received, total fee, expected completion date, delivery completion date, receipt reminder date, update date and time, etc. The management device 10 updates the electronic slip file (adds new information) when the product is received, and updates it as appropriate according to the progress of the service, etc.

[0112] The slip number is information for identifying an electronic slip in the cleaning system 1. For example, the POS terminal 20 may assign (number) a slip number when an item is deposited. In this embodiment, a serial number (used cyclically) for each store is assigned as the slip number. Specifically, a slip number of nine digits (including hyphens) is used, with the first two digits being "DN", the next two digits being the last two digits of the store code (a number unique to the store), the next digit being "-", and the next four digits being a serial number (0000 to 9999). Therefore, by referring to the slip number, it is possible to determine which store's transaction the electronic slip is for, without referring to the store code.

[0113] The date and time of receipt is information indicating the date and time when the dry cleaning store received the product from the customer. Note that the date and time when the store clerk inputs the information into the POS terminal 20 when the product is received may be regarded as the date and time of receipt.

[0114] The deposit category is information indicating the method of depositing goods. In this embodiment, the following methods of depositing goods (methods of accepting goods) are available: normal store deposit (sometimes referred to as normal store reception), speed deposit (sometimes referred to as speed reception), collection deposit (sometimes referred to as collection reception), and locker deposit (sometimes referred to as locker reception). Deposit category "1" indicates normal store deposit, deposit category "2" indicates speed deposit, deposit category "3()" indicates collection deposit, and deposit category "4" indicates locker deposit. The part in parentheses of deposit category "3()" is information (location code) indicating the collection location for collection deposit.

[0115] Regular store deposit is a method in which the customer brings the goods to the store's reception desk, where the customer and the store clerk meet to inspect and settle the payment, and the goods are accepted as deposited goods. Speed ​​deposit is a method in which the customer leaves the bagged goods (goods in a bag) at the store's reception desk (i.e., without the customer and the store clerk meeting to inspect and settle the payment). With speed deposit, the customer leaves the bag containing the goods (for example, a bag specially designed for speed deposit with a pocket for inserting the card may be used) along with their membership card (membership card with customer code, name, etc. written on it) with the store. The same applies to locker deposit, which will be described later. Collection deposit is a method in which the dry cleaning store goes to a designated collection location (the customer's home, a convenience store, etc.) to pick up the goods and accepts them as deposited goods. Locker deposit is a method in which the acceptance is completed when the customer places the bagged goods (goods in a bag) into the collection section of a designated locker (i.e., without the store clerk and the customer meeting face-to-face to inspect the goods or settle the payment).

[0116] The number of items deposited is information indicating the number of items deposited. Information regarding each item is stored in the deposited item information file (see FIG. 13). The total fee is information indicating the total fee for all the deposited items.

[0117] The expected completion date is information that indicates the date when the deposited items will be completed (cleaning will be completed) and the items will be available for delivery to the customer (the date when the customer will be able to receive the items). When multiple items are deposited (when the number of items deposited is two or more), the expected completion date indicates the date when all of the deposited items will be available for delivery.

[0118] The delivery completion date is information indicating the date on which delivery of the product to the user was completed (the date on which the user received the product). Note that when multiple products are received, the delivery completion date indicates the date on which delivery of all the received products is completed.

[0119] The receipt reminder date is information indicating the date on which the user was reminded to receive the product. If there are multiple dates on which the user was reminded to receive the product, only the last reminder date may be managed (stored) as the receipt reminder date, or each reminder date may be managed as a receipt reminder date. The method of reminding the user may be a reminder via a cleaning app, an e-mail, or a telephone call. The method of reminding may be managed (stored) together with the receipt reminder date.

[0120] The update date and time is information that indicates the date and time when any information on the electronic slip was updated. For example, if the delivery completion date is updated (input), the date and time of the update becomes the update date and time.

[0121] [Deposit product information file] 13 shows an example of a deposited product information file. The deposited product information file may be stored in any one of the management device 10, the POS terminal 20, etc. In this embodiment, an example is given in which the management device 10 stores the deposited product information file. The deposited product information file is a file that stores information about each deposited product. 13 stores, in association with the deposited product number, the tag number, product type, processing type, fee, pending classification, progress classification, expected completion date, reservation classification, delivery classification, expected delivery date, delivery completion date, update date and time, storage completion flag, etc. The management device 10 updates the electronic slip file (adds new information) when the product is deposited, and updates it appropriately according to the progress of the service, etc.

[0122] The deposited item number is information for identifying a deposited item in the cleaning system 1. For example, when a product is deposited, the POS terminal 20 or the management device 10 may assign (number) a deposited item number. In this embodiment, the deposited item number is the slip number with a branch number added. Specifically, the deposited item number is 13 digits in total (including hyphens), with the first 9 digits being the slip number, the next digit being "-", and the next 2 digits being a branch number (01 to 99). Therefore, by referring to the deposited item number, it is possible to determine which electronic slip the deposited item belongs to. Also, as described above, since the slip number can be used to identify the store at which the transaction took place, by referring to the deposited item number, it is possible to determine which store the deposited item belongs to.

[0123] The tag number is information for identifying the deposited goods in the cleaning system 1. For example, when depositing goods, the store clerk inputs the tag number of each deposited item into the POS terminal 20 by the store clerk, which is the number printed on the tag attached to each deposited item. In this embodiment, the tag number (the number printed on the tag) is a total of nine digits (including hyphens), with the first two digits being "TG", the next two digits being the last two digits of the store code (a number unique to the store), the next digit being "-", and the next four digits being a serial number (0000 to 9999). Therefore, by referring to the tag number, it is possible to know which store the deposited goods are from.

[0124] The product type is information indicating the type of product. The processing type is information indicating the type of processing (washing, storage, etc.). The fee is information indicating the fee for the deposited product.

[0125] The hold category is information indicating whether or not progress needs to be put on hold. In this embodiment, the condition of the deposited item is a specific item (item that is dirty, frayed, etc.) and is checked by the customer. Hold category "0" indicates no hold is necessary (no reason for hold), hold category "1" indicates hold is necessary (before user confirmation), and hold category "2" indicates no hold is necessary (user confirmation completed).

[0126] The progress category is information that indicates the progress status. A progress category "1" indicates that the product is in custody, a progress category "2" indicates that it is on hold, a progress category "3" indicates that it has been completed, a progress category "4" indicates that it is ready for delivery, a progress category "5" indicates that delivery is scheduled, and a progress category "6" indicates that delivery has been completed.

[0127] The scheduled completion date is information indicating the date on which the deposited product will be completed and can be handed over to the user. The scheduled completion date in the deposited product information file is the scheduled completion date for each deposited product, whereas the scheduled completion date in the electronic voucher file is the date on which all deposited products in the electronic voucher will be able to be handed over. In other words, the scheduled completion date in the electronic voucher file is the latest scheduled completion date among the scheduled completion dates for each deposited product corresponding to the electronic voucher shown in the deposited product information file. In this embodiment, the scheduled completion date is basically calculated based on the product deposit date (reception date) and the required number of days, but if the user's confirmation of a specific product is delayed, the scheduled completion date is delayed.

[0128] The reservation category is information that indicates whether or not a reservation has been made for the pick-up of the deposited goods. Reservation category "0" indicates that there is no reservation, reservation category "1" indicates that a reservation has been made at the store, reservation category "2" indicates that a reservation has been made by phone, and reservation category "3" indicates that a reservation has been made via the app. The reservation details include the delivery date and time and the delivery method. Note that if a reservation for pick-up is made when visiting the store to pick up the goods (in cases where the reservation category would be "1" or "2"), the reservation category will be "1 (reservation made at the store)".

[0129] Reservations can be changed. For example, a reservation made at the time of receiving an item can be changed by phone or through a cleaning app. When a reservation is changed, the reservation classification at the time of the change may be stored. For example, when a reservation made at the time of receiving an item is changed by phone, the reservation classification "1" before the change by phone may be updated to [2].

[0130] The delivery category is information indicating the delivery method of the deposited goods. In this embodiment, the following delivery methods (methods of returning the deposited goods) are available for the deposited goods: regular store delivery (sometimes called regular store return), delivery by delivery (sometimes called delivery return), and locker delivery (sometimes called locker return). The delivery category "0" indicates undecided, the delivery category "1()" indicates regular store delivery, the delivery category "2()" indicates delivery by delivery, and the delivery category "3" indicates locker delivery. The parentheses in the delivery category "1()" are information (store code) indicating the delivery store in the case of regular store delivery. The parentheses in the delivery category "2()" are information (location code) indicating the delivery location (user's home, convenience store, etc.) in the case of delivery by delivery. The parentheses in the delivery category "3()" are information (locker number) indicating the locker in the case of locker delivery. Also, although not shown in the figure, in the case of delivery category "3()", a return port number (identification information) indicating the return port of the locker indicated by the locker number may further be included.

[0131] Regular store pick-up (regular store return) is a method in which the product is handed over at the store's reception desk. Delivery pick-up (delivery return) is a method in which the product is handed over at a specified delivery location. Locker pick-up (locker return) is a method in which the product is handed over using a locker.

[0132] If there is no delivery reservation (reservation category "0"), the delivery method will be undecided (delivery category "0"). On the other hand, if there is a delivery reservation (reservation category "1" to "3"), the delivery method will be the method specified by the user in the reservation (delivery category "1" to "3").

[0133] The scheduled delivery date is information indicating the date on which the deposited goods are scheduled to be delivered. If there is no delivery reservation (reservation category "0"), the scheduled delivery date will be undecided (e.g., left blank). On the other hand, if there is a delivery reservation (reservation category "1" to "3"), the scheduled delivery date will be the date specified by the user in the reservation.

[0134] Even if there is no delivery reservation (reservation category "0"), delivery (return) to a regular store is possible after the scheduled completion date. In other words, it goes without saying that the user can suddenly go to the store and pick up the product without any prior notice, as long as it is after the scheduled completion date.

[0135] The delivery completion date is information indicating the date on which delivery of the product to the user was completed (the date on which the user received the product). Note that the delivery completion date in the deposited product information file is the delivery completion date for each deposited product, whereas the delivery completion date in the electronic voucher file is the date on which delivery is completed for all deposited products in that electronic voucher. In other words, the delivery completion date in the electronic voucher file is the latest delivery completion date among the delivery completion dates for each deposited product corresponding to that electronic voucher shown in the deposited product information file.

[0136] The update date and time is information that indicates the date and time when any information of the deposited product was updated. For example, if the delivery completion date is updated (input), the date and time of the update becomes the update date and time.

[0137] The storage completion flag is a flag that indicates whether or not the store clerk has finished storing the product in the return slot of the locker when the delivery category of the corresponding product is locker delivery.

[0138] Next, information related to the operation of the lockers stored by the cleaning system 1 will be described with reference to Figures 14 and 15. The information shown in Figures 14 and 15 may be stored by either the management device 10 or the POS terminal 20, but in this embodiment, the case where the information is stored by the management device 10 will be taken as an example.

[0139] [Locker management master file] Fig. 14(A) shows an example of a locker management master file. The locker management master file is a file that stores information about return lockers (return-only lockers 300, common lockers 200). The locker management master file shown in Fig. 14(A) stores the installation location, the number of return slots, etc. in association with the locker number. If all return lockers in cleaning system 1 have the same number of return slots, the number of return slots does not need to be managed (stored) in the locker management master file.

[0140] The locker number is information for identifying each return locker in the cleaning system 1. The installation location is the location where the return locker is installed. It is possible to install two or more return lockers in one store, and to install return lockers in locations other than stores. Examples of locations other than stores include supermarkets, convenience stores, specialty stores (clothing stores, pharmacies, etc.), shops in train stations (or near train stations), and return lockers (the same applies to the reception-only lockers 100) that may be installed indoors or outdoors in apartment buildings, etc. The number of return slots is the number of return slots that the return locker has.

[0141] In addition, the locker management master file may manage the reception lockers 100 (locker number of the reception lockers 100, etc.) in addition to the return lockers (return lockers 300, common lockers 200).

[0142] The POS terminal 20 may store the locker management master file instead of or in addition to the management device 10. The locker management master file stored in the POS terminal 20 may be a file related to all return lockers, like the file stored in the management device 10, or may be a file related to the return lockers related to the store (the store where the POS terminal 20 is installed) as shown in Fig. 14(B).

[0143] [Required number of shares definition file] FIG. 14(C) is an example of a required number of units definition file stored by the management device 10. The required number of units definition file is a file that stores information regarding the number of return units required for locker return. The required number of units definition file shown in FIG. 14(C) stores the required number of units in association with the number of items to be returned. The return number of items is the number (quantity) of items to be delivered. The required number of units is the number of return units required for locker return. According to FIG. 14(C), for example, if the number of items to be returned is 1 to 4, the required number of units is 1, and if the number is 5 to 8, the required number of units is 2. Note that if the capacity of the return unit differs depending on the type of locker, a required number of units definition file may be stored for each type of locker.

[0144] The required number of units definition file shown in Fig. 14(C) determines the required number of units simply based on the number of return products and does not take into account the type of return products, but the required number of units may be determined taking into account the type of return products. For example, instead of the required number of units definition file shown in Fig. 14(C), a required number of units definition file as shown in Fig. 14(D) and a volume number definition file as shown in Fig. 14(E) may be stored.

[0145] The required number of units definition file shown in Fig. 14(D) stores the required number of units in association with the number of return volumes. The number of return volumes is the volume (size) of the product to be delivered. According to Fig. 14(D), for example, if the number of return volumes is 1 to 4, the required number of units is 1, and if the number is 5 to 8, the required number of units is 2.

[0146] The volume number definition file shown in Fig. 14(E) stores the volume number in association with the product type (see Fig. 7(A)). According to Fig. 14(E), for example, the volume number of a product of product type SY01 (shirts) is 1, and the volume number of a product of product type SY04 (coats) is 4.

[0147] For example, if there are two items desired for delivery, one of which is a shirt (product type "SY01") and the other is a coat (product type "SY04"), then according to the required number of units definition file in Fig. 14(C), the number of items to be returned is two, so the required number of units is 1. On the other hand, according to the required number of units definition file in Fig. 14(D) and the volume number definition file in Fig. 14(E), the total volume number of one shirt and one coat is five, so the required number of units is two.

[0148] The POS terminal 20 may store a required number of ports definition file as shown in Fig. 14(C) instead of or in addition to the management device 10. The POS terminal 20 may store a required number of ports definition file as shown in Fig. 14(D) or a volume number definition file as shown in Fig. 14(E) instead of or in addition to the management device 10.

[0149] [Locker reservation status file] Fig. 15(A) is an example of a locker-specific reservation status file stored in the management device 10. The locker-specific reservation status file is a file that stores information regarding the reservation status (reservation state) of locker returns for each return locker. The locker-specific reservation status file shown in Fig. 15(A) shows a reservation status file for the return locker with locker number "L01", and includes the reservation category, customer code, tag number, number of volumes used, reservation date, reservation number, etc., in association with the return date and return slot number. In Fig. 15(A), for convenience of explanation, a separate sheet (table) is shown for each return date, but it is not necessary to separate the sheets for each return date. The number of volumes used is the number of volumes used to deliver the product at the return port, that is, the volume of the product to be delivered at the return port. The reservation status file by locker in Fig. 15(B) will be described later.

[0150] Note that the POS terminal 20 may store the locker-specific reservation status file instead of or in addition to the management device 10. Note that the locker-specific reservation status file stored in the POS terminal 20 may be a file related to all return lockers, like the file stored in the management device 10, or may be a file related to the return lockers related to the store (the store where the POS terminal 20 is installed).

[0151] The locker-specific reservation status file stores past information (information on past return dates) in addition to future information (information on future return dates). In other words, the management device 10 (the same applies when the POS terminal 20 stores the locker-specific reservation status file) continues to store past information in the locker-specific reservation status file without erasing it. For example, the management device 10 may continue to store past information without erasing it for a predetermined period (at least a period that is referenced when determining the return port (described later)).

[0152] The future information in the locker reservation status file is a file that shows the future reservation status of the lockers (each return entrance), but since the lockers are used based on reservations, the past information in the locker reservation status file is also a file that shows the past usage status of the lockers. Therefore, by storing the locker reservation status file in the cleaning system 1, the cleaning system 1 can manage the past usage status of the return entrance in addition to the future reservation status of the return entrance.

[0153] [Locker return reservation] The following describes the locker return reservation performed in the cleaning system 1 of this embodiment. Here, "locker return reservation" refers to reserving a date for a user (customer) to use a locker to return cleaned products, rather than having the products handed over to them by a store clerk at the store, and to have the products stored in the locker's return slot. A locker return reservation can be made by a store clerk operating the POS terminal 20 while speaking with the user at the store (store reservation). Alternatively, a locker return reservation can be made by the user operating a cleaning application on the user terminal 50 (application reservation). In the case of application reservation, the user does not need to go to the store and be served by a store clerk. The results of locker reservations made through store reservations and through application reservations are reflected in the locker reservation status file (Figure 15).

[0154] In both the case of store reservation and application reservation, when reserving a locker, the management device 10 specifies the reservation possible date (return possible date) according to the completion date of the product and the reservation status of the return slot. The flowchart in FIG. 16 shows an example of a process performed by the management device 10 in relation to identifying a reservation possible date (return possible date). The process in FIG. 11 is started when identifying the available date for locker return reservation (when executing the process related to locker return reservation, for example, when displaying the locker return reservation screen (described later)). For example, in the case of a store reservation, when a store clerk is accepting a cleaning request from a user in person and is requesting a locker return, the store clerk performs a locker return reservation declaration operation on the POS terminal 20. In addition, the store clerk may also perform a locker return reservation declaration operation on the POS terminal 20 when a store clerk receives a locker return request from a user by telephone or the like. The POS terminal 20 transmits a locker return reservation setting request to the management device 10 in response to the locker return reservation declaration operation. Furthermore, as an application reservation, the user performs an operation on the cleaning application running on his / her POS terminal 20 to transition to an operation screen corresponding to the application reservation. In response to the operation, the POS terminal 20 requests a locker return reservation setting request to the management device 10. In response to receiving the locker return reservation setting request transmitted as described above, the management device 10 may start the process shown in the figure. The process in FIG. 1 may be executed by the POS terminal 20 when handling store reservations.

[0155] Step S400: The management device 10 calculates the number of return slots required for return (required number of slots) based on the number, type, etc. of products to be returned. Step S401: The management device 10 judges whether or not all the products to be returned to the locker have been completed. If the items have not been completed (step S401; NO), the process proceeds to step S402. If the items have been completed (step S401; YES), the process proceeds to step S405. Note that when this flowchart is executed at the time of product deposit, none of the items have been completed, so the process proceeds to step S402.

[0156] Step S402: The management device 10 identifies the latest scheduled completion date (the latest scheduled completion date among the scheduled completion dates of the products to be returned to the locker). Step S403: The management device 10 sets the latest scheduled completion date as the reference date, and then proceeds to step S406. The reference date in steps S403, S405, and S406 is the earliest possible reservation date when the locker usage status is not taken into consideration (when ignored). Step S405: The management device 10 sets tomorrow as the reference date, and then proceeds to step S406.

[0157] Step S406: The management device 10 judges whether or not the number of vacancies on each day after the reference date is equal to or greater than the required number. If the number of vacant seats is equal to or greater than the required number, reservations are possible, so the process in step S406 is a process for determining whether or not the reservation is possible on that day. The management device 10 can calculate the reservation possible days from the number of vacant seats and the required number of seats for each day after the base date. Step S407: The management device 10 outputs the result of the determination in step S406. The output of the determination result indicates whether or not a reservation can be made for each day. Therefore, the process in the figure can be said to determine whether or not a reservation can be made for each day (or a specific day) when specifying the reservation possible day (return possible day). The determination result of step S406 is reflected in the locker reservation status file (FIG. 22). At this time, the management device 10 may, for example, cause the POS terminal 20 to display and output information based on the contents of the locker reservation status file in which the determination result of step S406 is reflected.

[0158] [Locker return reservation screen] In this embodiment, for example, when a locker return reservation is made by a store reservation, the output of the determination result in step S407 in FIG. In this case, the management device 10 transmits a locker-specific reservation status file reflecting the judgment result of step S407 in FIG. 16 to the POS terminal 20, and the POS terminal 20 displays a locker return reservation screen (locker return reservation screen) based on the transmitted locker-specific reservation status file.

[0159] Fig. 17 shows an example of a locker return reservation screen displayed on the store clerk display unit 26 of the POS terminal 20. The locker return reservation screen is a screen on which operations related to locker return reservations are performed. The locker return reservation screen in the same figure corresponds to the contents of the locker reservation status file in Fig. 15(A).

[0160] The locker return reservation screen shown in the same figure has a current date and time column (see symbol A), locker information column (see symbol B), customer information column (see symbol C), number of items to be returned to the locker column (see symbol D), message column (see symbol E), number of return slots required column (see symbol F), adjustment column (see symbol G), calendar column (see symbol H), etc.

[0161] The current date and time column (symbol A) displays the current date and time. The locker information field (symbol B) displays the locker number and other information of the return locker whose information is displayed on the locker return reservation screen. The customer information field (symbol C) displays the customer code and other information of the user (the user making the locker return reservation). The number of items to be returned to the locker column (D) displays the number of items that the user wishes to have delivered by returning to the locker. The required number of return slots field (symbol F) displays the number of return slots required when the user returns the locker. In the adjustment column (symbol G), buttons for increasing or decreasing (adjusting) the required number of return slots and the adjustable range are displayed. The calendar section (symbol H) displays the number of return slots (vacant return slots) that can be used (reserved) on each day. Each date area in the calendar section is a button.

[0162] To explain this figure, we will use an example where a customer (customer code "KB9876") selects three items on the slip details screen (Figure 14) that he / she wishes to have delivered when returning the items to the locker: a shirt (tag number "TG01-1372"), a sweater (tag number "TG01-1374"), and a down jacket (tag number "TG01-1375"). The required number of items is calculated taking into account the volume.

[0163] "L01 (AAA)" in the locker information column (symbol B) in the figure is displayed based on, for example, the stored product information file (Fig. 13), the locker management master file (Fig. 14(A)), and information about the store. "3" in the locker return product quantity column (symbol D) refers to the three items mentioned above.

[0164] The "2" in the required number of return ports field (symbol F) indicates the number of return ports based on the number of volumes to be returned. In the cleaning system 1, the number of volumes is defined corresponding to each product type, and for example, the management device 10 stores information defining the number of volumes for each product type. Also, in the cleaning system 1, the number of return ports required according to the number of volumes to be returned (required number of return ports) is defined, and for example, the management device 10 stores information defining the required number of ports according to the number of volumes to be returned. In the figure, the volume number of the shirt (product type "SY01") is "1", the volume number of the sweater (product type "SY02") is "2", and the volume number of the down jacket (product type "SY03") is "3", so the total volume number (return volume number) is "6". The required number of units corresponding to the return volume number "6" is "2", so "2" is displayed in the required return units column.

[0165] The adjustable range "1 to 3" in the adjustment column (symbol G) is preset as a fixed value when the required number of return ports column is "2." It may also be preset as a fixed value when the number of return volumes is "6."

[0166] The "4" displayed on the 4 / 20 date button in the calendar column (symbol H) corresponds to the number of vacancies "4" in the locker reservation status file (Figure 15(A)). In other words, the date button in the calendar column shows the number of vacancies in the return slot on the corresponding date. In the locker return reservation screen shown in Fig. 17, the color (background color) of each date button is different depending on whether the date is a reservation available date (a day from tomorrow onwards (excluding store holidays) where the number of available slots is equal to or exceeds the required number of return slots) or a reservation unavailable date (a day where reservations are not available). Fig. 17 shows an example in which the date buttons corresponding to reservation available dates (4 / 20, 4 / 23, 4 / 24, 4 / 27, 4 / 28, ...) and the date buttons for reservation unavailable dates (4 / 16-4 / 19, 4 / 21, 4 / 22, 4 / 25, 4 / 26, 4 / 29, ...) are grayed out.

[0167] When the locker return reservation screen of FIG. 17 is displayed on the store clerk display unit 26, the POS terminal 20 may also display a locker return reservation screen (customer locker return reservation screen) for the customer on the customer display unit 27. 18 shows an example of a customer locker return reservation screen. The customer locker return reservation screen in the figure corresponds to the customer locker return reservation screen in FIG. In the figure, an area for each date (date area) is arranged in the calendar section. In addition, a cross or a circle is arranged in the date area. A cross indicates that the corresponding date is unavailable for reservation because there are not enough return slots available for the required number of slots, whereas a circle indicates that the corresponding date is available for reservation because there are more than the required number of return slots available.

[0168] The manner in which reservation is possible or not possible for each date is not limited to the above circle and cross mark. For example, the manner in which reservation is possible or not possible may be indicated by icons imitating a locker with an available return slot or a locker with no available return slot. Such a customer locker return reservation screen may be displayed on the customer display unit 27 as an external display device connected to the main body of the POS terminal 20. The customer display unit 27 as an external display device can easily secure a large screen, so that the customer locker return reservation screen can be displayed in a large size. This makes it easier for customers to see the customer locker return reservation screen. For example, if the customer display unit 27 is provided on the main body of the POS terminal 20 but the screen size is small, an external display device may be provided as another customer display unit 27, and the external display device may be used, or the customer display unit 27 of the main body and the external display device may be used together. When the customer display unit 27 of the main body and the external display device are used together, the display destination may be switched between the customer display unit 27 of the main body and the external display device depending on the content to be displayed to the customer.

[0169] The customer looks at the customer's locker return reservation screen displayed in this way, selects a reservation date from the available dates, and notifies the store clerk of the selected reservation date. The store clerk then operates the date button in the calendar column (symbol H) that corresponds to the notified reservation date. Alternatively, the date area on the customer side locker return reservation screen may also be a button that can be operated by the user (customer side date button). In this case, the user can select a reservation date from the available reservation dates and operate the customer side date button that corresponds to the selected reservation date.

[0170] Here, we will take as an example a case where the "4 / 20" date button or the customer's date button is operated. In response to the operation of the "4 / 20" date button or the customer date button, the locker return reservation screen displayed on the clerk display unit 26 changes to that shown in Fig. 17 to Fig. 19. That is, on the locker return reservation screen, the "4 / 20" date button is highlighted, for example, by changing to a specific background color compared to the other date buttons. This indicates that April 20th is currently specified as the reservation date. Although not shown in the figure, the customer's locker return reservation screen may also be configured in a similar manner so that the date area "4 / 20" in the date area (customer's date button) is highlighted. With the date button for "4 / 20" highlighted as shown above, the store clerk operates, for example, the "Register" button. In response to the operation of the "Register" button, April 20th is confirmed as the reservation date.

[0171] In response to the reservation date being confirmed, for example, the management device 10 updates the locker-specific reservation status file, the deposited product information file, and the deposited product information file. FIG. 15(B) shows an example of the contents of the locker reservation status file updated in response to April 20th being confirmed as the reservation date. FIG. 20 shows an example of the contents of the on-hold product information file updated from that shown in FIG. 13 in response to April 20 being confirmed as the reservation date.

[0172] In addition, after the reservation date is confirmed, the status of the locker return reservation may be reflected on the screen of the cleaning application on the user terminal 50. FIG. 21 shows an example of the contents of the invoice details screen displayed on the user terminal 50 after the reservation date has been confirmed. In the same figure, an example is shown in which in the column for products that are eligible for locker return, it is indicated that the product will be returned to a locker, for example, "Locker return reserved," and the reservation date is also displayed.

[0173] Furthermore, when the number of available return slots is greater than the required number, the management device 10 determines (selects) a return slot (reserved return slot) to store the product from among the available (reservable) return slots. In other words, when there is a surplus in the number of available return slots (room to select a return slot), it determines which return slot to use. There are several possible methods for determining the reserved return port. In one example, the management device 10 may determine the reserved return port based on the past usage of each return port. As a specific example, the management device 10 may determine the reserved return port so that a specific return port is not used frequently (so that each return port is used evenly). By using each return port evenly, a situation in which deterioration or damage progresses at a specific return port is less likely to occur. The management device 10 can grasp the past usage status of each return slot, for example, by continuing to store the locker-specific reservation status file (Figure 15) for a certain period of time without deleting it even after the return date has passed.

[0174] Also, instead of or in addition to the above method, the management device 10 may determine the reserved return port based on, for example, the positional relationship (adjacency) of each return port. As a specific example, when the same user reserves two or more return ports (when the number of return ports required by the user is two or more), the management device 10 may determine adjacent return ports as much as possible so that the user can pick up the product from the adjacent return port. By determining adjacent return ports, the user does not need to move to a return locker located far away.

[0175] An example of a process procedure executed by the management device 10 in relation to a locker return reservation will be described with reference to the flowchart of Fig. 22. The flowchart of Fig. 22 shows an example of a process procedure corresponding to a case where a locker return reservation is made by a store reservation.

[0176] Step S630: The POS terminal 20 requests a reservation screen (for example, a locker return reservation screen) from the management device 10. That is, the POS terminal 20 transmits to the management device 10 a locker return reservation setting request in response to the locker return reservation declaration operation performed by the store clerk.

[0177] Step S631: The management device 10 receives a request for a reservation screen (locker return reservation screen) from the POS terminal 20. Step S632: The management device 10 generates a reservation screen (the latest locker return reservation screen based on the current reservation status). Specifically, the management device 10 generates the reservation screen by referring to the latest electronic slip file of the user, the deposited product information file, the locker management master file, the locker-specific reservation status file, etc. The management device 10 may generate a reservation screen for the return locker installed in the store where the product (the product desired to be returned to the locker) was deposited. Step S633: The management device 10 transmits screen information of the reservation screen to the POS terminal 20.

[0178] Step S634: The POS terminal 20 receives screen information (screen information of the latest locker return reservation screen) from the management device 10. Step S635: The POS terminal 20 displays a reservation screen (the latest locker return reservation screen). Step S636: The POS terminal 20 accepts a reservation operation on the reservation screen (for example, touching a button for a day on which a reservation is available in the calendar section (symbol H)). Step S637: The POS terminal 20 transmits the reservation information (reservation date, required quantity, etc.) to the management device 10.

[0179] Step S638: The management device 10 receives the reservation information from the POS terminal 20. Step S641: The management device 10 determines a return port (reservation return port) based on the reservation information in accordance with a predetermined method.

[0180] Step S642: The management device 10 updates various files based on the result of determining the return port. That is, the management device 10 reflects the result of determining the return port in S641 in the corresponding user's electronic slip file, the deposited product information file, the locker management master file, the locker reservation status file, etc.

[0181] In step S642, when returning a product to a customer by locker return, the above-mentioned various files and the like are reflected with information on the storage schedule including the date when the product should be stored in the return-only locker 300 (scheduled delivery date, start date of scheduled storage date) together with the result of determining the return port. That is, in step S642, the storage schedule of the product is stored.

[0182] Step S643: The management device 10 updates and generates various screens. For example, the management device 10 updates and generates a reservation confirmation screen based on the result of the return port determination in step S642. Specifically, the management device 10 updates the locker scheduled return date calendar screen to reflect the reservation details as shown in FIG. 19. The management device 10 also generates a slip details screen reflecting the reservation details as shown in FIG. 21. The management device 10 may also generate a locker scheduled return list screen reflecting the reservation details as shown in FIG. 24 described below. That is, in step S643, screen information to be transmitted in subsequent processes (steps S645 and S655) is generated.

[0183] Step S645: The management device 10 transmits screen information to the POS terminal 20. For example, the management device 10 transmits screen information of a reservation screen (locker return reservation screen reflecting the reservation contents as shown in FIG. 19, locker return schedule list screen reflecting the reservation contents as shown in FIG. 24, etc.) to the POS terminal 20. Step S646: The POS terminal 20 receives from the management device 10 screen information of a reservation screen (locker return reservation screen reflecting the reservation contents, locker return schedule list screen reflecting the reservation contents as shown in FIG. 24). Step S647: The POS terminal 20 displays a reservation screen (locker return reservation screen reflecting the reservation contents).

[0184] Step S655: The management device 10 transmits screen information to the user terminal 50. For example, screen information of a reservation confirmation screen (a slip details screen reflecting the reservation contents as shown in FIG. 21) is transmitted to the user terminal 50. Step S656: The user terminal 50 receives screen information for the reservation confirmation screen (a slip detail screen reflecting the reservation contents) from the management device 10, and stores the received screen information in the storage unit. Then, the flow chart of FIG. 22 ends.

[0185] 22, the management device 10 may send message information to the user terminal 50 by e-mail or the like to notify the user that the locker has been reserved. In other words, when reserving a locker return at the POS terminal 20, the management device 10 may send a minimum amount of information to the user terminal 50 when the return port is determined.

[0186] Furthermore, the processing of steps S655 and S656 may be performed when the user operates the device, regardless of whether the message information is sent or received, instead of when the return port is determined as shown in Fig. 22. In other words, for example, the message information may be sent from the management device 10 to the user terminal 50 when a slip details screen is requested.

[0187] The flowchart in FIG. 22 is an example of an operation in which the management device 10 determines the return port, but in the case of the mode in which the POS terminal 20 determines the return port, the result of the determination of the return port by the POS terminal 20 may be reflected in various files stored in the management device 10. As an example, the flow may be as follows. The POS terminal 20 that has accepted a reservation operation on the reservation screen (the latest reservation screen received by accessing the management device 10 as in the case of FIG. 22) determines the return port and transmits information indicating the result of the determination of the return port to the management device 10. The management device 10 updates various files based on the information indicating the result of the determination of the return port received from the POS terminal 20. Next, the POS terminal 20 receives screen information of a reservation confirmation screen (such as a locker return reservation screen reflecting the reservation contents as shown in FIG. 19, a locker return schedule list screen reflecting the reservation contents as shown in FIG. 24 described later, etc.) from the management device 10. The processes of S655 and S656 are the same. As a result of the above, the result of the determination of the return port by the POS terminal 20 is reflected in various files stored in the management device 10.

[0188] Next, an example of a process procedure executed by the management device 10 in relation to a locker return reservation as an application reservation will be described with reference to a flowchart of FIG. 23, step S600: The user terminal 50 on which the cleaning application runs requests a reservation screen from the management device 10. For example, when a user performs an operation on the user terminal 50 to display a reservation screen (for example, a selection to indicate a desire to return the item to a locker), the user terminal 50 requests the reservation screen from the management device 10.

[0189] Step S601: The management device 10 receives from the user terminal 50 a request for a reservation screen (for example, a locker return reservation screen). Step S602: The management device 10 generates a reservation screen (the latest locker return reservation screen based on the current reservation status) in the same manner as in step S632 of FIG. Step S603: The management device 10 transmits screen information of the reservation screen to the user terminal 50.

[0190] Step S604: The user terminal 50 receives the screen information from the management device 10. Step S605: The user terminal 50 displays a reservation screen. Step S606: The user terminal 50 accepts a reservation operation on the reservation screen (for example, touching a button for a day on which a reservation is available in the calendar section (symbol H)). Step S607: The user terminal 50 transmits the reservation information (reservation date, required number, etc.) to the management device 10.

[0191] Step S608: The management device 10 receives the reservation information from the user terminal 50. Step S611: The management device 10 determines a return port (reservation return port) based on the reservation information in accordance with a predetermined method. Step S612: The management device 10 updates various files based on the result of determining the return port, similarly to step S642 in FIG. Step S613: The management device 10 updates and generates various screens in the same manner as in step S643 of Fig. 22. In step S613, the management device 10 generates screen information to be transmitted in steps S615 and S625 described later.

[0192] Step S615: The management device 10 transmits screen information to the user terminal 50. For example, screen information of a reservation confirmation screen (a slip details screen reflecting the reservation contents as shown in FIG. 27) is transmitted to the user terminal 50. Step S616: The user terminal 50 receives from the management device 10 screen information for the reservation confirmation screen (a slip detail screen reflecting the reservation contents). Step S617: The user terminal 50 displays a reservation confirmation screen (a slip detail screen reflecting the reservation contents).

[0193] Step S625: The management device 10 transmits screen information to the POS terminal 20. For example, the management device 10 transmits screen information of a reservation confirmation screen (locker return reservation screen reflecting the reservation contents as shown in FIG. 19, locker return schedule list screen reflecting the reservation contents as shown in FIG. 24 described later, etc.) to the POS terminal 20. Step S626: The POS terminal 20 receives screen information of a reservation confirmation screen (such as a locker return reservation screen reflecting the reservation contents or a locker return schedule list screen) from the management device 10, and stores the received screen information in the storage unit. Then, the flowchart in FIG. 23 ends.

[0194] The processes in steps S625 and S626 in FIG. 23 may be omitted. 23, the management device 10 may transmit message information to the POS terminal 20 informing that the locker has been reserved, and the POS terminal 20, which has received the message information, may display the message on the currently displayed screen. In other words, when reserving a locker return at the user terminal 50, a minimum amount of information may be transmitted to the POS terminal 20 when the return slot is determined.

[0195] 23, the processes of steps S625 and S626 may be performed when a store clerk operates the device, regardless of whether the message information is sent or received. As an example of sending the message information, the management device 10 may send screen information of a small screen including an OK (display) button and a Cancel (do not display) button to the POS terminal 20 together with the message, and the POS terminal 20 that receives the screen information may display the small screen superimposed on the currently displayed screen, and when the OK (display) button is touched (corresponding to a store clerk's operation), a reservation confirmation screen (locker return reservation screen, locker return schedule list screen, etc.) is requested and sent from the management device 10 to the POS terminal 20.

[0196] Note that the processing procedure example in Figure 23 corresponds to the case where the management device 10 determines the return port, but in the case where the POS terminal 20 determines the return port, the result of the return port determination by the POS terminal 20 should be reflected in various files stored in the management device 10.

[0197] When the store clerk wishes to check the current locker return reservation status, the store clerk can operate the POS terminal 20 to cause the store clerk's display unit 26 to display a locker return reservation confirmation screen. 24 shows an example of a locker return reservation confirmation screen. The locker return reservation confirmation screen in the figure includes a current date and time field (see symbol A), a condition setting area (see symbol B), and a result display area (see symbol C).

[0198] The condition setting area (symbol B) is an area for setting (extracting) confirmation targets such as locker return reservation status. The condition setting area has a scheduled return date setting field (symbol B1) and a customer setting field (symbol B2). The scheduled return date setting field (symbol B1) has selection buttons for inputting the scheduled return date (range specification button, previous day button, today button, next day button), and a scheduled return date range input field for inputting the range of the scheduled return date when the range specification button is selected. When the previous day button, today button, or next day button is selected, a range is automatically input in the scheduled return date range input field according to the type of button selected. As can be seen from the previous day button, it is also possible to set a past date. The customer setting field (symbol B2) has a scheduled return date range input field for inputting the range of the user's customer code, a phone number input field for inputting the user's phone number, and a phone number input field for inputting the user's name.

[0199] The result display area (symbol C) is an area that displays the extraction results based on the conditions set in the condition setting area. Specifically, the result display area shown in FIG. 24 displays the expected return date, receipt date, slip number, name, phone number, number of items, return slot used, and reissue based on various information.

[0200] For example, the expected return date "201X / 4 / 20" in the topmost information (line indicated by an arrow) is displayed based on the return date "201X / 4 / 20" in the locker reservation status file in Fig. 15(B). Alternatively, the expected return date "201X / 4 / 20" may be displayed based on the expected delivery date "4 / 20" in the deposited product information file in Fig. 20. The receipt date "201X / 4 / 19" is displayed based on the reservation date "4 / 19" in the locker reservation status file in Fig. 15(B). Alternatively, the receipt date "201X / 4 / 19" may be displayed based on the update date and time "4 / 19 18:27" in the stored product information file in Fig. 20. The slip number "DN01-5422" is displayed based on the tag number "TG01-1372" etc. in the locker reservation status file in Figure 15(B) and the deposited product number "DN01-5422-01" etc. in the deposited product information file in Figure 20. The first nine digits "DN01-5422" of the deposited product number "DN01-5422-01" indicate the slip number. The customer code "KB9876" is displayed based on the customer code "KB9876" in the locker reservation status file in Figure 15(B). The name "... (omitted)" and phone number "... (omitted)" are displayed based on the customer master file in Figure 11(A) and so on.

[0201] The number of items "3" is displayed based on the number of corresponding items (tag numbers "TG01-1372", "TG01-1373", "TG01-1375") in the deposited item information file of Fig. 20. Specifically, for example, the number of items "3" may be displayed based on the number (specifically, 3) of items (tag numbers "TG01-1372", "TG01-1373", "TG01-1375") with a scheduled delivery date of "4 / 20" among the items (tag numbers "TG01-1372" to "TG01-1375") corresponding to the above-mentioned slip number "DN01-5422" in the deposited item information file of Fig. 20. Alternatively, the number of items "3" may be displayed based on the number (specifically, 3) of items with a scheduled date of "4 / 20" and the same reservation number (specifically, 12345).

[0202] The return port to be used "H31, H32" may be displayed based on the return port number ("H21", "H22") to be used for returning the corresponding products (tag numbers "TG01-1372", "TG01-1373", "TG01-1375") in the deposited product information file of Figure 20. The item "return slot in use" is provided in response to the case where the return slot in which the product is to be stored is determined when the return reservation is made. In the case where the return slot in use is determined when the product is stored in the return locker, an item "number of return slots in use" may be provided instead of the item "return slot in use". The item "number of return slots in use" indicates the number of return slots required to store the corresponding product. Reissue "*" is displayed based on the fact that a reissue (multiple printings) has been performed.

[0203] The POS terminal 20 displays (extracts) information related to the store on the locker return reservation confirmation screen. In other words, the information displayed on the locker return reservation confirmation screen by the POS terminal 20 of a certain store is limited to reservation information for return lockers under the management of the store (for example, return lockers installed in front of the store).

[0204] Alternatively, the POS terminal 20 may display information related to other stores. For example, a store setting field may be provided on the locker return reservation confirmation screen, and the POS terminal 20 may display information related to the store of the store code entered in the store setting field. Also, for example, an All Stores button may be provided on the locker return reservation confirmation screen, and when the All Stores button is operated, the POS terminal 20 may display information related to all stores without any limitation on the store.

[0205] Furthermore, the user terminal 50 may display a locker return reservation confirmation screen in a predetermined manner, the locker return reservation confirmation screen being limited to information related to the user.

[0206] The factory terminal 40 (as well as the management device 10) displays information related to the specified store on the locker return reservation confirmation screen. For example, a store setting field may be provided on the locker return reservation confirmation screen, and the factory terminal 40 may display information related to the store with the store code entered in the store setting field. Also, for example, an all stores button may be provided on the locker return reservation confirmation screen, and when the all stores button is operated, the factory terminal 40 may display information related to all stores without limiting the store.

[0207] When storing an item in the return slot whose scheduled storage date falls on the current day (the scheduled delivery date in the stored item information file (FIG. 20)), the store clerk causes the POS terminal 20 to display the locker return reservation confirmation screen of FIG. 24. The store clerk operates the locker return reservation confirmation screen to display in the result display area a list of items whose scheduled storage date falls on the current day. The store clerk then operates the print button. In response to the print button being operated, the POS terminal 20 issues a scheduled storage list slip for the items whose scheduled storage date falls on the current day.

[0208] Fig. 25 shows an example of a storage schedule list slip. The storage schedule list slip in this figure shows storage schedule information that corresponds to the current scheduled storage date. In the storage schedule list slip, storage product unit areas AR1 corresponding to each storage product unit are arranged sequentially from top to bottom. One storage product unit corresponds to a common product with a common slip number and a scheduled storage date starting date of the current day.

[0209] One stored product unit area AR1 includes a customer information area AR11, a storage instruction information area AR12, a tag number area AR13, and a code information area AR14.

[0210] In the customer information area AR11, information (customer information) about the customer (user) is displayed. Specifically, in the figure, the customer number and name are displayed as the customer information.

[0211] The storage instruction information area AR12 shows information indicating storage instructions for the corresponding product. As a specific example, the storage instruction information area AR12 in the figure shows the reservation number, the start date of the scheduled storage date, the number of products to be stored, and the number of return slots (number of doors).

[0212] In addition, when the return port is decided at the stage when the locker return reservation is made, information indicating the return port may be displayed instead of the number of return ports in the storage instruction information area AR12. That is, when a return port number is assigned to each return port and a number is displayed for each return port on the locker, the return port number may be displayed as the information indicating the return port. Alternatively, the location of the return slot may be indicated as the information indicating the return slot. As an example, if the locker is the shared locker 200 shown in FIG. 2B, the location of the return slot can be indicated as follows: The return port side of the common locker in the figure is connected to one locker unit on the left side having a panel unit 210a, return ports H12, H21, H22, H31, and H32, and one locker unit on the right side having return ports H41, H42, H51, H52, H61, and H62. In the case where the locker with the panel unit 210a on the left side is the parent locker and the one on the right side is the child locker, the information indicating the return port is specifically indicated as "2-lower-middle". The "2" in "2-lower-middle" indicates the locker number when the parent locker is assigned as "1" and the child locker is assigned as "2". The "lower" in "2-lower-middle" indicates that it is the lower level of the return ports stacked in two tiers. The "middle" in "2-lower-middle" indicates the center position of the three positions in the horizontal direction of the child lockers. In this case, the positions of the three rows in the horizontal direction are indicated by "left", "middle", and "right". The manner in which the positions of the return slots are indicated is not limited to the above example. For example, the arrangement of the return slots may be printed, and the corresponding return slots may be indicated in a manner that allows them to be distinguished from other return slots.

[0213] The tag number area AR13 shows the tag number of the product to be stored. The tag number in the tag number area AR13 is printed in a more emphasized manner than other characters. As a specific example, the tag number in the figure is printed in a larger size than the other characters. In the code information area AR14, code information indicating predetermined information among the information indicated in the corresponding stored commodity unit area AR1 is printed. In the figure, an example in which a barcode is printed as the code information is shown, but it may be a two-dimensional code such as a QR code (registered trademark).

[0214] The clerk takes the issued storage schedule list slip to the back yard and removes the products tagged with the tag numbers shown in tag number area AR13 as storage items. When doing this, the clerk checks the tag numbers in tag number area AR13, but because the tag numbers in tag number area AR13 are emphasized more than other characters, it is easier for the clerk to check the tag numbers in tag number area AR13. This makes it easier for the clerk to find the products that correspond to the tag numbers in tag number area AR13. Next, the store clerk takes the storage schedule list slip and the products to be stored that he or she has taken out of the back yard and goes to the location where the lockers are installed. In the following explanation, we will use as an example a case where return lockers 300 are installed as lockers for customers to return products. When the store clerk arrives at the return locker 300, he or she first operates the code recognition unit of the return locker 300 to read the code information printed in the code information area AR14 in one storage item unit area AR1 on the storage schedule list slip.

[0215] The return-only locker 300 transmits the read code information to the management device 10. The code information indicates a reservation number. The management device 10 identifies the return port number associated with the reservation number indicated by the code information from the management device 10, and notifies the return-only locker 300 of the identified return port number. The return locker 300 unlocks the return port of the notified return port number. When unlocking, for example, a display unit of the return locker 300 may display a message informing a store clerk of the return port number of the unlocked return port. The store clerk then places the corresponding product in the unlocked return slot and locks it. After that, the store clerk repeats the same procedure, having the code recognition unit of the return locker 300 read the code information for each storage product unit area AR1 on the storage schedule list slip to unlock the return slot and place the product in the slot.

[0216] The unlocking of the return slot in response to the return locker 300 reading the code information printed in the code information area AR14 may be controlled as follows. The return-only locker 300 transmits the read code information to the management device 10. The management device 10 compares the reservation number indicated by the code information with the contents of the locker-specific reservation status file to determine whether the reservation number indicated by the code information is correct. Here, "determining whether the reservation number is correct (OK or NG)" means "determining whether the planned storage date indicated by the reservation number corresponds to the current date and time." The management device 10 transmits reservation number valid / invalid information to the return locker 300, which indicates the result of the determination as to whether the reservation number is valid or invalid (OK or NG). If the received reservation number validity information indicates NG, the planned storage date of the corresponding product does not correspond to the current date and time, and the product should not be stored in the return slot. In this case, the return locker 300 does not unlock the return slot, and notifies the user that the corresponding product should not be stored, for example. On the other hand, if the received reservation number validity information indicates OK, the current date and time corresponds to the planned storage date for the corresponding product, so the corresponding product may be stored. In this case, the return locker 300 determines, according to a predetermined rule, which return slot to store the corresponding product in from among the currently available return slots. The return locker 300 unlocks the determined return slot. Also, the return-only locker 300 may obtain a locker-specific reservation status file from, for example, the management device 10 and store it in the device itself. In this case, the return-only locker 300 does not need to communicate with the management device 10 because it only needs to refer to the read code information and the locker-specific reservation status file stored by itself when determining the return exit in response to reading the code information.

[0217] In addition, instead of the code information on the storage schedule list slip, the return port number of the return port where the storage target products should be stored can be identified and the return port can be unlocked in the same manner as described above by reading code information such as a QR code printed on the factory copy attached to the storage target products.

[0218] [Example of processing procedures related to product recall] As described above, in the cleaning system 1 of this embodiment, products that customers have placed in the locker's collection section can be accepted as products to be cleaned. At some stage, a store clerk will collect the products that have been placed in the locker's collection section. If the store clerk forgets to collect the products that have been placed in the locker's collection section, the collection section may become full at some point, causing problems such as customers being unable to place products in the collection section. Therefore, in the cleaning system of this embodiment, a notification for collecting products is given to store clerks so that they do not forget to collect products from the collection section, as will be described below. In the following description, an example will be given in which the reception locker 100 is used as the locker into which a customer deposits goods.

[0219] An example of a process procedure executed by the reception-only locker 100 and the management device 10 in relation to setting the collection schedule flag as collection schedule setting will be described with reference to the flowchart in FIG. 26(A). Step S101: The reception-only locker 100 determines whether or not a collection trigger has occurred for the products to be cleaned stored in the collection section 102. The occurrence of a collection trigger indicates that the products stored in the collection section 102 have reached a capacity that requires collection. The collection trigger may be generated when the number of times that customers deposit products in the collection unit 102 reaches a predetermined number, and the amount of products in the collection unit 102 reaches a level that requires collection. Specifically, the reception-only locker 100 may determine that a collection trigger has occurred when the number of times it has been unlocked reaches or exceeds a predetermined threshold, for example, based on the detection output of a sensor that detects the unlocking of the deposit port 101 of the collection section 102. Also, for example, when a customer inserts an item into the collection section 102, the customer performs an operation to have the code recognition section 106 or the card reader 125 read the membership card information in order to unlock the insertion slot 101. The reception-only locker 100 may determine that a collection trigger has occurred when the number of times that the code recognition section 106 or the card reader 125 has read the membership card information reaches a predetermined number or more. In this case, for example, if the membership card information of the same customer is read multiple times in succession, the reception-only locker 100 may not include the second and subsequent readings of the membership card information in the number of times that corresponds to the occurrence of a collection trigger.

[0220] Alternatively, the collection trigger may be generated based on the amount of products stored in collection section 102. In this case, collection section 102 is provided with a sensor that detects the amount of items stored in collection section 102. Such a sensor may be one that detects the height or weight of the items stored in collection section 102, for example. The reception-only locker 100 may determine that a collection trigger has occurred when the height or weight detected by the sensor reaches or exceeds a predetermined threshold value.

[0221] Alternatively, the reception-only locker 100 may determine that a collection trigger has occurred when a predetermined time has arrived. The reception-only locker 100 may determine whether or not a predetermined time has been reached based on the time it keeps. Alternatively, the management device 10 or the POS terminal 20 may keep time to determine whether or not a predetermined time has been reached, and notify the reception-only locker 100 that the predetermined time has been reached.

[0222] Step S102: If it is determined in step S101 that a collection trigger has occurred, the reception-only locker 100 transmits a collection trigger occurrence notification to the management device 10.

[0223] Step S201: The management device 10 waits for receipt of the collection trigger occurrence notification transmitted in step S102. Step S202: The management device 10 sets a collection schedule flag in response to receiving the collection trigger occurrence notification. Specifically, the management device 10 sets the collection schedule flag stored in the RAM 122 (an example of a storage unit) or the storage unit 123 (an example of a storage unit) to a value indicating that collection is scheduled. Setting such a collection schedule flag corresponds to storing a schedule for collection of the product.

[0224] Next, with reference to the flowchart in FIG. 26(B), an example of a processing procedure executed by the reception-only locker 100 and the management device 10 in relation to clearing the collection schedule flag as collection schedule setting will be described. Step S111: The reception-only locker 100 waits for the products stored in the collection unit 102 to be collected. The reception-only locker 100 may determine whether or not an item has been collected as follows. When a store clerk collects an item, the store clerk unlocks the collection door of the collection unit 102 according to a predetermined procedure, and locks the collection door when the collection of the item is completed. Thus, the reception-only locker 100 may determine that an item has been collected when it detects, as an event, that the collection door has been unlocked and then locked. Alternatively, the reception-only locker 100 may determine that an item has been collected when the detection output of a sensor that detects the weight or volume of the items contained in the collection section 102 changes from a value corresponding to a state in which the items are contained to a value corresponding to a state in which the items are not contained.

[0225] Step S112: In response to determining in step S111 that the product has been collected, the reception-only locker 100 transmits a collection confirmation notice to the management device 10. The collection confirmation notice notifies the management device 10 that the product has been collected from the collection unit 102.

[0226] Step S211: The management device 10 waits for receipt of the collection confirmation notification transmitted from the reception-only locker 100 in step S112. Step S212: When the collection confirmation notice is received, the management device 10 determines whether or not the collection schedule flag is currently set. Step S213: If it is determined in step S212 that the collection schedule flag is set, the management device 10 resets the value of the collection schedule flag to a value indicating that collection is not scheduled. On the other hand, if it is determined in step S212 that the collection schedule flag is not set, the process of step S213 may be skipped and the process of the figure may be terminated.

[0227] 26(A) and 26(B), the collection schedule flag is set, for example, when a situation arises in which it is necessary to collect a product from the collection section 102. In addition, the set collection schedule flag is reset when the product is collected from the collection section 102.

[0228] An example of a process performed by the management device 10 and the POS terminal 20 in relation to a collection notification will be described with reference to the flowchart of FIG. 26(C). Step S221: The management device 10 judges whether a certain period of time has elapsed while the collection schedule flag is set. In this case, the certain period of time may be set to zero or a value close to zero so that a notification is given immediately in response to the collection schedule flag being set. Alternatively, in step S221, the management device 10 may determine whether or not a predetermined time has arrived in a state in which the collection schedule flag is set.

[0229] Step S222: If a certain period of time has elapsed while the collection schedule flag remains set, the management device 10 transmits a product collection notification instruction to the POS terminal 20. The notification instruction is a command by which the management device 10 instructs the POS terminal 20 to execute a notification (collection instruction notification) to instruct a store clerk to collect the product.

[0230] Step S321: The POS terminal 20 waits to receive the product withdrawal notification instruction transmitted from the management device 10 in step S122. Step S322: In response to receiving the instruction to collect the product, the POS terminal 20 issues a collection instruction notification. The POS terminal 20 may issue a collection instruction notification in a predetermined manner, for example, on the store clerk display unit 26. By issuing a collection instruction notification in this manner, the store clerk can know that the product should be collected from the reception-only locker 100. This can prevent the store clerk from forgetting to collect the product from the reception-only locker 100.

[0231] In addition, when a collection instruction notification is issued, there may be cases where the store clerk cannot immediately collect the product because, for example, other work such as customer service must be given priority. Therefore, the collection instruction notification may be temporarily stopped in response to, for example, an operation to declare that collection will be postponed (a collection postponement declaration operation). In this case, the POS terminal 20 may issue a collection instruction notification again, for example, when a certain time has elapsed since the collection postponement declaration operation was performed.

[0232] [Example of processing procedures related to product storage] 27 and 28 show an example of a process executed by a locker in response to the return of an item. Here, an example is given of the process executed by the return locker 300. First, FIG. 27 will be described. Step S800: The return locker 300, for example, while displaying a standby screen on the display unit 304, waits for an operation to be performed on the standby screen. Step S801: When an operation is performed on the standby screen, the return locker 300 displays a guide screen in a predetermined format, for example, to request the user to read the membership card and enter a password.

[0233] Step S802: The return-only locker 300 determines whether or not the member card has been read in response to the request in step S801. If the member card has been read (step S802; YES), the process proceeds to step S804. If the member card has not been read (step S802; NO), the process proceeds to step S810.

[0234] Step S804: The return locker 300 notifies the user of the corresponding return bay. Specifically, the return locker 300 notifies the user of the return bay number where the user's deposited product is stored by displaying a notification screen in a predetermined format on the display unit 304. Step S805: The return locker 300 unlocks the return door of the corresponding return slot and blinks the light emitting unit. Note that the light emitting unit may be turned off after the return door is opened and closed (locked), for example. Step S806: The return locker 300 waits for the locker return (handover of the deposited goods) to be completed. The return locker 300 may determine that the locker return is complete when it detects that the door of the return opening, which was unlocked and opened in step S805, is closed and locked. Alternatively, a sensor may be provided at the return opening to detect the presence or absence of contents, and the locker return may be determined to be complete when the sensor detects a transition from a state with contents to a state without contents.

[0235] Step S807: When the locker return is completed, the return-only locker 300 stores return completion information in the storage unit 323 (which may be the RAM 322). The return completion information may include, for example, some or all of the customer ID, return slot number, tag number, date and time information, etc. In addition, the return locker may transmit the return completion information to the management device 10 instead of storing the return completion information in the memory unit, and the management device 10 may perform updates of various files, etc. based on the return completion information. Furthermore, the management device 10 may update various screens such as the slip details screen (FIG. 21, etc.) (e.g., update the progress category to "9 (delivery completed)") and cause the user terminal 50, etc. to display the updated screen. Step S808: The return locker 300 notifies the user that the locker return has been completed, for example by displaying a notification screen in a predetermined format on the display unit 304.

[0236] Step S810: If it is determined in step S802 that the member card or the like has not been read, the return locker 300 determines whether or not a predetermined operation has been performed by the store clerk (for example, whether or not the store clerk barcode has been read). If it is determined that the predetermined operation has not been performed, the process returns to step S802.

[0237] Step S820: If it is determined in step S810 that a predetermined operation has been performed by the store clerk, the return locker 300 displays an initial screen for store clerk (not shown) on which various buttons (return item storage button, return item collection button, back button, etc.) are arranged on the display unit 304. That is, the return locker 300 transitions to the store clerk mode.

[0238] Next, FIG. 28 will be described. Step S821: After transitioning to the store clerk mode in step S820, the return locker 300 determines whether or not the back button arranged on the store clerk initial screen (not shown) has been operated. If the back button has been operated (step S821; YES), the process returns to step S800. Note that if the back button has been operated (step S821; YES), the process may be configured to return to step S801 instead of returning to step S800.

[0239] Step S822: If the return button has not been operated, the return locker 300 determines whether or not the return item storage button arranged on the initial screen for store clerk (not shown) has been operated. The return item storage button is a button that is operated by a store clerk to transition the return locker 300 to a storage mode in the store clerk mode when the store clerk is working to store the items to be returned in the return slot of the return locker 300. If the return item storage button is operated (step S822; YES), the process proceeds to step S830. If the return item storage button is not operated (step S822; NO), the process proceeds to step S823.

[0240] Step S823: The return locker 300 determines whether or not the return item collection button on the initial screen for store clerk (not shown) has been operated. If the return item collection button has been operated (step S823; YES), the process proceeds to step S840. If the return item collection button has not been operated (step S823; NO), the process returns to step S821.

[0241] Step S830: The return locker 300 transitions to a storage mode. Then, the return locker 300 displays a specified storage guidance screen, requesting the store clerk to read the code information. The code information to be read here is the code information printed on the storage schedule list slip (FIG. 25). The code information to be read may also be the code information printed on the factory copy attached to the product.

[0242] Step S831: The return-only locker 300 determines whether or not the back button arranged on the storage guide screen has been operated. If the back button has been operated (step S831; YES), the process returns to step S821. If the back button has been operated (step S831; YES), the process may return to step S800 (or step S801) instead of returning to step S821. If the back button has not been operated (step S831; NO), the process proceeds to step S832.

[0243] Step S832: The return locker 300 judges whether or not the code information has been read. If the code information has been read (Step S832; YES), proceed to Step S833. If the code information has not been read (Step S832; NO), return to Step S831.

[0244] Step S833: The return locker 300 identifies the return bay where the product should be stored. For this purpose, the return locker 300 transmits, for example, code information (or the reservation number indicated by the code information) to the management device 10. The management device 10 identifies, for example, the return bay number associated with the reservation number indicated by the received code information from the locker-specific reservation status file, and notifies the return locker 300 of the identified return bay number. The return locker 300 receives a notification of the return port number from the management device 10 and thereby identifies the return port in which the product should be stored.

[0245] Alternatively, the return bay where the product should be stored may not be determined when the locker return is reserved, but may be determined when the product is stored in the return locker 300. In such a case, the return locker 300 specifies the return bay where the product should be stored in step S833 by determining the return bay according to a predetermined rule.

[0246] Step S834: The return locker 300 notifies the user of the return opening identified in step S833. The return opening is notified by display on the display unit 304. Step S835: The return locker 300 unlocks the door of the identified return slot and blinks the light emitting unit. Note that the light emitting unit may be turned off after the return slot door is opened and closed (locked), for example.

[0247] Step S836: The return locker 300 waits for the storage of the product (deposited product) to be completed. The return locker 300 may determine that the storage of the product is completed when it is determined that the return slot door of the return slot 310 has been opened and closed once (unlocked and locked after the unlocking). In addition, it may be determined that the storage is not completed for a return slot that has been unlocked but not subsequently locked. This makes it possible to notify the store clerk in cases where the return slot door has been unlocked but the product has been forgotten to be placed inside and the door remains unlocked, or where the product has been placed inside but the lock has been forgotten to be placed inside. Step S837: When the storage of the product is completed, the return locker 300 stores storage completion information in the storage unit 323 (which may be the RAM 322). The storage completion information stored in step S837 may include, for example, some or all of the customer ID, return slot number, tag number, date and time information, etc.

[0248] Step S838: The return locker 300 also transmits a storage completion notification to the management device 10. The storage completion notification includes information that can identify the stored product. For example, the storage completion notification may include some or all of the information that can identify the stored product, such as the customer ID, return slot number, tag number, date and time information, as with the storage completion information.

[0249] The store clerk sequentially reads the code information in the code information area AR14 corresponding to each storage item unit area AR1 printed on the storage schedule list slip, and stores the items in the unlocked return slot. The processing of steps S830 to S838 is repeated for each of these tasks. Then, when the store clerk has finished storing all the items to be returned in the return slot, he or she operates the back button. In response to the operation of the back button, the storage mode is ended, and the process transitions from step S831 to step S821.

[0250] Step S840: The store clerk collects from the return slot any products that have not been picked up by the user and are still stored in the return locker 300 even after the delivery deadline has passed. At this time, the store clerk operates the return item collection button. If it is determined in step S823 that the return item collection button has been operated, the return-only locker 300 sets the return item collection mode and requests the store clerk to operate to start collection. Specifically, for example, a return item collection initial screen corresponding to the return item collection mode is displayed on the display unit 304, and the store clerk is requested to operate the OK button displayed on the return item collection initial screen.

[0251] Step S841: After executing the process of step S840, the return-only locker 300 judges whether or not the back button arranged on the return item collection initial screen has been operated. If the back button has been operated (step S841; YES), the return item collection mode is ended and the process returns to step S821. If the back button is operated (step S841; YES), the process may return to step S800 (or step S801) instead of returning to step S821. If the back button is not operated (step S841; NO), the process proceeds to step S842.

[0252] Step S842: The return locker 300 judges whether or not the OK button arranged on the return item collection initial screen has been operated. If the OK button has been operated (step S842; YES), the process proceeds to step S844. If the back button has not been operated (step S842; NO), the process returns to step S841.

[0253] Step S844: If the OK button is operated in step S842, it is confirmed that the store clerk intends to collect the returned items. In this case, the return locker 300 notifies all return ports. For example, the return locker 300 displays a collection instruction screen in a predetermined format and notifies the return port numbers of all return ports on the collection instruction screen.

[0254] Step S845: The return-only locker 300 unlocks the return door of all return slots and blinks the light-emitting units. Note that the light-emitting units may be turned off after the return doors are opened and closed (locked), for example. Step S847: The return-only locker 300 stores collection completion information indicating that collection of the return item has been completed in the memory unit 323. The collection completion information stored in step S847 may include, for example, some or all of the customer ID, return port number, tag number, date and time information, etc. After the processing of step S847, the process returns to step S821. Note that after the completion of step S847, the process may return to step S800 (or step S801) instead of returning to step S821.

[0255] In addition, instead of storing the collection completion information in the memory unit, the return locker may also transmit the collection completion information to the management device 10, and the management device 10 may perform updates of various files, etc. based on the collection completion information.

[0256] An example of a process procedure executed by the management device 10 in relation to management of the storage completion flag will be described with reference to the flowchart of FIG. 29(A). Step S231: The management device 10 waits to receive the storage completion notification transmitted from the return locker 300 in step S838 of FIG. Step S232: When the management device 10 receives the storage completion notification, it refers to, for example, the tag number, etc., indicated in the received storage completion notification to identify the product indicated in the deposited product information file that has been stored in accordance with the currently received storage completion notification. The management device 10 sets a value indicating storage completion (for example, "1") to the storage completion flag corresponding to the identified product in the deposited product information file (FIGS. 13 and 20). As can be understood from the explanations in Figures 27, 28, and 29(A), the storage completion notice is sent from the return locker 300 in response to an event in which the return door is opened or closed (unlocked, and locked following unlocking) in response to a storing operation performed by a store clerk. The storage completion flag is set in response to receiving the storage completion notice.

[0257] Next, an example of a process procedure executed by the management device 10 and the POS terminal 20 in relation to notification of unstored commodities will be described with reference to a flowchart of FIG. 29(B). Step S241: The management device 10 waits until it is time to check whether or not there is an unstored commodity. The confirmation timing may be, for example, a predetermined time determined in accordance with the business schedule of the store. In this case, for example, when a predetermined time arrives on a business day, if there are any products that should be stored that day but have not been stored, a notification of the unstored products can be made. Alternatively, the confirmation timing may be a certain amount of time that has elapsed since the last storage completion notification was received by the management device 10. In this case, the notification can be made at a timing that a certain amount of time has elapsed since the store clerk finished the storage work for that day.

[0258] Step S242: When it is determined that the confirmation timing has arrived, the management device 10 determines whether or not there are any unstored products. For this purpose, the management device 10 determines whether or not there are any products among the products indicated in the deposited product information file (FIGS. 13 and 20) for which the current day is the scheduled delivery date (i.e., the date on which the product should be stored at the return slot) and whose storage completion flag indicates that the product has not been stored (for example, "0"). If it is determined that there are no unstored products, the process in the figure ends.

[0259] Step S243: If it is determined in step S242 that there are unstored products, the management device 10 transmits an instruction to notify the POS terminal 20 of the unstored products. The instruction to notify the POS terminal 20 of the unstored products is a command from the management device 10 to instruct the POS terminal 20 to notify the POS terminal 20 that there are unstored products among the products that should be stored in the return slot on that day, and to execute an instruction to store the unstored products in the return slot (unstored product notification).

[0260] Step S341: The POS terminal 20 waits to receive the instruction to notify the management device 10 of the unstored products transmitted in step S243. Step S322: In response to receiving the instruction to notify the user of the non-stored product, the POS terminal 20 executes the non-stored product notification. The POS terminal 20 may notify the user of the non-stored product in a predetermined manner on the store clerk display unit 26, for example.

[0261] 30 is a diagram showing an example of a non-storage notification screen displayed as a non-storage commodity notification on the store clerk-side display unit 26. The non-storage notification screen in the same figure shows a message that there are non-storage commodities, a message instructing to store the non-storage commodities, and a list of the non-storage commodities.

[0262] By notifying the unstored product in this manner, the store clerk can realize that he or she should put away an item if the item has been forgotten to be put away. Also, by notifying the unstored product, the store clerk can understand that there was an item that was forgotten to be put away if the store clerk performed the storage work but forgot to put away some items. In addition, in the case of the unstored product notification screen of FIG. 30, for example, the store clerk can immediately know which products have not been stored by looking at the unstored product list.

[0263] As in the case of a collection instruction notification, when a non-stored commodity notification is made, the non-stored commodity notification may be temporarily stopped in response to a storage postponement declaration operation being performed. In this case, the POS terminal 20 may again perform a non-stored commodity notification, for example, when a certain time has elapsed since the storage postponement declaration operation was performed.

[0264] [Prohibition of closure] When the store clerk has finished business, he or she causes the POS terminal 20 to execute a closing process. However, if the closing process is executed before the products have been collected from the storage section of the locker and stored in the return slot, it will cause a disruption to business the next day. Therefore, in this embodiment, if the collection and storage of products according to the business of the day has not been completed, the closing process by the POS terminal 20 is prohibited (an example of a restriction) as described below.

[0265] The flowchart in FIG. 31 is a flowchart showing an example of a process procedure executed by the POS terminal 20 in relation to the closing process. Step S251: The POS terminal 20 waits for an operation to instruct execution of a closing process (a closing process instruction operation). Step S252: When the closing process instruction operation is performed, the POS terminal 20 determines whether the collection schedule flag is set as the current status of the collection schedule flag. For example, even if a collection notification is performed, the collection schedule flag remains set if the collection postponement declaration operation is repeated and the store clerk performs the closing process instruction operation without performing the collection work. Step S253: The POS terminal 20 also refers to the current deposited product information file to determine whether or not there is any unstored product.

[0266] Step S254: The POS terminal 20 judges whether or not the condition (restriction condition) for activating the restriction on the closing process is satisfied based on the judgment results of steps S252 and S253. If the judgment result of step S252 that the collection schedule flag is set and / or the judgment result of step S253 that there are unstored products are obtained, the restriction condition is satisfied.

[0267] Step S255: If it is determined in step S254 that the restrictive condition is satisfied, the POS terminal 20 prohibits the closing process. Specifically, the POS terminal 20 does not execute the closing process, and executes an error notification that the closing process cannot be executed. The error notification that the closing process cannot be executed may be displayed on the store clerk display unit 26 (or the customer display unit 27). In addition, the error notification may include a reason why the closing process is prohibited. Specifically, if the restriction condition is satisfied because the collection schedule flag is set, the error notification may include a notification that the collection schedule flag is set. In this case, the error notification may include a message instructing the store clerk to collect the product. In addition, when the limiting condition is satisfied due to the presence of an unstored product, the fact that there is an unstored product may be notified. In this case, the error notification may include a message that instructs the store clerk to store the unstored product.

[0268] Step S256: If it is determined in step S254 that the restrictive condition is not satisfied, the POS terminal 20 executes a closing process.

[0269] In the process of the figure, the closing process is prohibited in step S255 in response to the restriction condition being satisfied in step S254. That is, the POS terminal 20 controls so as not to start the closing process itself in step S255. However, the POS terminal 20 may execute, for example, certain predetermined process items among the process items to be executed as the closing process in step S254, but not execute other process items. That is, the POS terminal 20 may restrict the closing process so as not to execute certain process items in the closing process.

[0270] <Modification> A modification of this embodiment will now be described.

[0271] [First Modification] In the above embodiment, with regard to storing the product, a notification is given when an unstored state occurs, which corresponds to the case where the product has been forgotten to be stored in the return slot of the locker. In addition to not putting away the product, other mistakes made by store staff regarding the putting away of products (storage mistakes) include, for example, putting a product that should already be put away in a return bay into a different bay. In this modified example, a notification regarding the storage of a product is made not only when the product is not stored, but also when the product is stored in the wrong place. In this modified example, a notification regarding the wrong storage place is made when the product is stored in a return port of the locker other than the return port where it should be stored. For this purpose, the locker sends a confirmation request to the management device 10 (which may be the POS terminal 20) including the tag number indicated in the code information that the store clerk has the code recognition unit read to unlock the return port in response to the storage of the item, and the return port number of the unlocked return port. The management device 10 determines whether the return port number associated with the same tag number included in the received confirmation request in the locker reservation status file matches the return port number included in the received confirmation request. The management device 10 transmits the determination result to the locker. When the locker receives a determination result that the return port number does not match, it notifies the store clerk performing the storage operation that the storage location is incorrect. The notification that the storage location is incorrect may be made, for example, by a display on a display unit provided on the locker, or by a sound, etc. Also, a notification may be made by a combination of a display and a sound. Furthermore, when notifying that the storage location is incorrect, the correct return port number, etc. may also be notified.

[0272] [Second modified example] The notification of the incorrect storage location may be made by the POS terminal 20. In this modification, the POS terminal 20 is configured to be able to notify the incorrect storage location in addition to notifying the non-storage. In this modified example, the notification may be made on different occasions for the incorrect storage location and for the non-storage, or may be made on the same occasion for the incorrect storage location and for the non-storage. In the following explanation, an example is given of a case where the notification of the incorrect storage location and for the non-storage is possible at the stage when the closing process is started.

[0273] To start the closing process, the store clerk performs a closing process instruction operation on the POS terminal 20 as described above. In response to the closing process instruction operation being performed, the POS terminal 20 of this modified example displays a closing process screen on the store clerk display unit 26. Then, if at least one of the following has occurred at the current time: the product has not been stored in the return slot of the locker or the product has been stored in the wrong place, a storage error notification screen is displayed so as to be superimposed on the closing process screen.

[0274] In this modified example, in response to a closing process instruction operation being performed, for example, the management device 10 determines whether or not there is an unstored product, as well as whether or not there is an incorrectly stored product. In this modified example, in the deposited product information file shown in FIG. 13, for example, in addition to the storage completion flag, return port usage information indicating the number of the return port where the product was stored is provided. Then, in response to the closing process instruction operation being performed, the management device 10 determines whether the return port number indicated in the return port usage information is the same as the return port number associated with the tag number of the relevant product indicated in the locker-specific reservation status file (FIG. 15). If the management device 10 determines that the two are not the same, it transmits a storage error notification instruction to the POS terminal 20. The storage error notification instruction includes information about the product corresponding to the incorrect storage location, information about the corresponding customer, the return port number of the return port where the product is currently stored, the return port number of the correct return port, etc. In addition to determining whether or not there are products stored in the wrong place as described above, the management device 10 also determines whether or not there are unstored products by processing similar to that shown in Figure 29, and if it determines that there are unstored products, it sends a storage error notification instruction for the unstored products to the POS terminal 20.

[0275] When the storage error notification instruction is received, the POS terminal 20 displays a storage error notification screen. Fig. 32 shows an example of the storage error notification screen WD1. The storage error notification screen WD1 in the figure is displayed in a pop-up window format superimposed on the closing process screen. The storage error notification screen WD1 in the figure shows examples of storage errors such as forgetting to put something away and not putting something away.

[0276] The storage error notification screen WD1 in the same figure displays messages such as "There has been a locker storage error" and "Please check your receipt" to notify the store clerk that a storage error has occurred and to encourage the store clerk to check the storage error list slip.

[0277] In addition, as a message to notify the store clerk that a storage error has occurred on the storage error notification screen WD1, if the storage error is that an item has not been put away but that an incorrect storage location has not occurred, for example, "Something has been forgotten to be put away in the locker," the content may be such that the store clerk is notified by clearly indicating that an item has not been put away. Conversely, if the storage error is that an item has not been put away but that an incorrect storage location has occurred, for example, "Something has been put away in the locker," the content may be such that the store clerk is notified by clearly indicating that an incorrect storage location has occurred.

[0278] The store clerk who sees the display of the storage error notification screen WD1 can recognize that a storage error has occurred. The store clerk then operates the confirmation button BT1 arranged on the storage error notification screen WD1. In response to the operation of the Confirm button BT1, the storage error notification screen WD1 is cleared and the closing process screen is displayed in the foreground, making it possible to operate the closing process screen. Furthermore, in response to the operation of the Confirm button BT1, the POS terminal 20 issues a storage error list slip.

[0279] A slip listing storage errors is a slip showing a list of items that have been stored incorrectly. FIG. 33 shows an example of a slip listing storage errors. The slip listing storage errors in the figure shows an example of a case where a return slot has been assigned in advance for items to be stored, for example, through a locker reservation. The figure also shows an example of a slip listing storage errors showing a total of three list items: two items not stored (forgot to be stored) and one item stored in the wrong place.

[0280] In the uncollected item, customer information (customer number, name, phone number, etc.) of the customer corresponding to the corresponding product, the slip number corresponding to the corresponding product, the reception date, the score, the number of return slots in the locker, the return slot number, the tag number of the tag attached to the corresponding product, code information (an example of a barcode is shown in the figure), etc. The code information may include, for example, the slip number, as at least a part of the above information printed in the corresponding item.

[0281] Similarly to the not-put-away items, the incorrect storage item shows customer information about the customer who owns the item, the slip number, receipt date, score, number of locker return slots, tag number of the tag attached to the item, and code information for the item. Additionally, the incorrect storage item shows the return slot number where the item is currently incorrectly stored, and the correct return slot number where the item should be stored. Specifically, the example in the figure shows that the item is currently incorrectly stored in return slot number 6, and that it should be stored in return slot number 1.

[0282] The store clerk checks the details of each item printed on the mis-storage slip and searches for any unstored items, for example in the back yard using tag numbers, unlocks and opens the corresponding return slot, and stores the items. The store clerk also removes any items that were stored in the wrong place from the return slot, and then unlocks and opens the door to the correct return slot and stores the items. When performing this task, the store clerk can unlock the return slot by having the code information printed on the mis-storage slip read by the locker's code recognition unit. When the store clerk has corrected the storage error as described above, he or she can return to the POS terminal 20, for example, and perform the closing process by operating the closing process screen displayed on the POS terminal 20.

[0283] The management device 10 may also transmit the storage error notification instruction to the locker. For example, the return-only locker 300 may display a storage error notification screen on the display unit 304 in a format similar to that shown in FIG. 32 in response to receiving the storage error notification instruction. As a result, for example, if a store clerk is performing some task or operation near return locker 300 during closing operations, the clerk can learn of the occurrence of a storage error from the storage error notification screen displayed on display unit 304 of return locker 300. In this case, return locker 300 may be configured to be able to issue a storage error list slip by printing unit 326. As a result, a store clerk who notices a storage error from the display on return locker 300 does not have to return to POS terminal 20 to pick up the storage error list slip.

[0284] In the above example, the management device 10 is configured to determine whether or not a storage error has occurred, but the POS terminal 20 or the locker may be configured to obtain the information necessary for the determination from the management device 10, etc., and then determine whether or not a storage error has occurred.

[0285] In addition to the above-mentioned incorrect storage location and non-storage, storage errors may also include incorrect storage dates. An incorrect storage date is a storage error in which an item with a return date different from the return date corresponding to the current date and time is mistakenly stored in the return slot. Such storage errors can occur, for example, when a locker is designed to unlock the return slot when the code information for an item is read, even if the code information for the item has a return date that differs from the return date that corresponds to the current date and time. In this case, the fact that the product was stored in the return slot of the locker on the wrong storage date can be determined by, for example, the management device 10 or the POS terminal 20, etc., comparing information (storage result information) that associates the return slot in the locker with the code information of the product stored in the return slot with the locker reservation status file.

[0286] Furthermore, a slip issued at the time of the closing process, such as the slip listing storage errors in the lockers shown in FIG. 33, may be made to be able to be registered in advance by a store clerk. As a specific example, when the store clerk wishes to register a form to be issued at the time of closing processing, the store clerk performs a predetermined operation on the POS terminal 20 to cause the store clerk side display unit 26 to display a reservation form setting screen.

[0287] Fig. 34 shows an example of a reservation slip setting screen. In the figure, as slips to be issued (printed) during the closing process, a list of customer deposits and withdrawals by register (one for each of the "total" and "details" contents (two sheets in total), a list of customer deposits and withdrawals by staff member (one for each of the "total" and "details" contents (two sheets in total), and a list of customer deposits and withdrawals by customer (one for each of the "total" and "details" contents (two sheets in total) are registered. In addition, as slips to be issued (printed) during the closing process, an example is shown in which one each of a locker storage schedule list slip and a locker storage error list slip is registered.

[0288] In the above description of this modified example, the storage error notification screen is displayed when the closing process instruction operation is performed and the display of the closing process screen starts. In this case, the storage error notification screen is displayed before the closing process starts. However, the storage error notification screen may be displayed, for example, when an operation is performed on the displayed closing process screen and the closing process reaches a predetermined stage. Also, for example, in the reservation slip setting screen of FIG. 34, it may be possible to specify the timing of issuing various slips, including the mis-delivery slip, during the closing process.

[0289] [Third Modification] In the above embodiment, an example was given in which the management device 10 is connected to the POS terminal 20 and the lockers so as to be able to communicate with each other, and the management device 10 executes control to realize notifications regarding the collection of products from the lockers and notifications regarding the storage of products in the lockers. However, the control of notifications regarding the collection and storage of products in the lockers as described above may be appropriately performed by a device in the cleaning system 1. For example, in an environment where the POS terminal 20, the store mobile terminal 30, the lockers, etc. are connected to be able to communicate with each other, the POS terminal 20 may control the notification to be made on its own device or the store mobile terminal 30. Conversely, the store mobile terminal 30 may control the notification to be made on its own device or the POS terminal 20, etc. The POS terminal 20, the management device 10, the store mobile terminal 30, etc. may control the notification to be made on the factory terminal 40.

[0290] [Fourth Modification] In the above embodiment, an example was given of a case where the lockers are communicatively connected to the management device 10 (which may be the POS terminal 20). In this modified example, products are collected and stored as follows in an environment where the lockers are not connected to the management device 10 or the POS terminal 20. The following explanation takes as an example a case where a reception-only locker 100 and a return-only locker 300 are used.

[0291] First, regarding the collection of products from the collection unit 102 of the reception-only locker 100, the POS terminal 20 displays a collection instruction screen showing a message instructing the collection of the products on the store clerk's display unit 26 when a predetermined time arrives. Then, when the store clerk performs an operation to acknowledge the instruction to collect the products in response to the display of the collection instruction screen, the POS terminal 20 and the management device 10 process the collection as having been performed.

[0292] Regarding storing products in the return slot 310 of the return locker 300, the POS terminal 20 causes the store clerk display unit 26 to display a product storage instruction screen when a specified time corresponding to the closing time of the business day arrives.

[0293] Fig. 35 shows an example of a product storage instruction screen. The product storage instruction screen in the figure is an example of a screen similar to the locker return schedule list screen. Note that, for example, if the return slot is determined by having the locker read code information, an item indicating the number of return slots in which the product should be stored may be provided instead of the "return slot in use" item indicating the number of the return slot in which the product should be stored.

[0294] The store clerk checks the products to be stored in the return slot 310 based on the list of products to be stored, which is shown in the product list area marked C on the product storage instruction screen, and stores the confirmed products in the return slot 310 for each list item in the product list area. When the store clerk stores a product corresponding to one list item, he or she performs a touch operation on the corresponding list item in the product list area. For the list item for which the touch operation was performed, the storage confirmation area changes to a display indicating that the item has been stored. The same figure shows an example in which the storage confirmation area has changed from a state in which no particular object or the like was placed to a state in which a circled object has been placed.

[0295] In addition, there is no particular limitation on the manner in which the status of "not stored" or "stored" in the storage confirmation area is represented. For example, each status may be represented by text, such as "not stored" or "stored."

[0296] By displaying such a product storage instruction screen, the store clerk can grasp the unstored products that need to be stored, the return slots into which the unstored products should be placed (or the number of return slots required to store the unstored products), etc. In addition, while the clerk is working to store the products in the return slot one by one, he or she operates the confirmation area of ​​the list item corresponding to the stored product, so that the clerk can grasp the products that have already been stored and the products that are yet to be stored while working.

[0297] Even in this modified example, when storing an item in the return slot of the locker, the store clerk may, for example, issue a storage schedule list slip (Figure 25) using the POS terminal 20, and then have the locker read the code information printed on the issued storage schedule list slip to unlock the return slot. Alternatively, when storing an item in the return slot of a locker, a store clerk can unlock the locker by having the locker read the code information printed on the factory receipt attached to the item to be stored.

[0298] In an environment where the locker is not connected to the management device 10 or the POS terminal 20, as in this modified example, the locker cannot determine whether any storage errors have occurred with respect to the products stored in the return slot by communicating with the management device 10 or the POS terminal 20. Therefore, in this modified example, the code information of the product that is read by the locker includes the start date of the planned storage date, and the locker is capable of obtaining the current date and time (which may be up to the current date) by, for example, having a timing function.

[0299] When a store clerk puts an item into the return slot of a locker, the clerk operates the locker to read the code information of the item to be put into the return slot (item to be put into storage). The locker determines whether the start date of the planned storage date included in the read code information is the same as the date indicated by the current date and time. If the start date of the planned storage date is the same as the date indicated by the current date and time, the locker determines that the item to be stored is available and unlocks the return opening. In addition, the code information may also include information on the number of return slots required to store the target products. In this case, when the start date of the planned storage date is the same as the date indicated by the current date and time, the locker can unlock the number of return slots corresponding to the number of return slots indicated in the code information.

[0300] On the other hand, if the start date of the planned storage date differs from the date indicated by the current date and time, the date on which the product to be stored should be stored is not the current day. In this case, the locker will not unlock the return opening to prevent storage. At this time, the locker may display a notice that storage is not possible because the start date of the planned storage date for the product to be stored differs from the current date.

[0301] The locker may also store a storage history in response to the storage of a product in an unlocked return slot. The storage history includes, for example, an identifier (return slot number) indicating the return slot in which the product is stored, and a transaction identifier obtained from the code information read when unlocking the return slot. In this case, if the product is stored in multiple return slots, multiple return slot numbers may be indicated in the storage history. In this case, the customer who comes to collect the product has the code information printed on the deposit slip or the code information displayed on the electronic deposit slip read by the code recognition unit of the locker. The locker can search for a storage history that contains the same transaction identifier as the read code information, and unlock the return slot with the return slot number indicated by the searched storage history. In this case, if the searched storage history indicates multiple return slot numbers, the return slots with each return slot number are unlocked. In this way, in this modified example, the locker stores the storage history, so that product returns (storing items in the return slot and customers removing them from the return slot) can be handled appropriately.

[0302] [Fifth Modification] In the above embodiment, the POS terminal 20 can issue a deposit slip as a paper receipt together with a factory copy, for example, when making payment (step S20 in FIG. 7). In addition, if the customer specifies locker return, the deposit slip can be used for authentication when picking up the product from the locker. Therefore, as this modified example, an example of a deposit slip issued in response to a locker return specification will be described.

[0303] FIG. 36 shows an example of a receipt ticket issued in response to a request for locker return. The deposit slip in the same figure has printed thereon information about the product to be deposited, such as the product name, tag number, amount, and return category (in this case, "locker return"). In addition, the deposit slip in the same figure has a code information area AR31 and a collection information area AR32. Note that in deposit slips issued in cases where locker return is not specified, the code information area AR31 and collection information area AR32 are omitted.

[0304] The code information area AR31 is an area where code information is printed. The code information printed in the code information area AR31 may include a predetermined number of pieces of information (authentication information) required for authentication at the locker depending on operation, etc., from among information such as a transaction number, a customer code (customer ID), a store code, the number of return slots used, the return slot number used, a PIN number, a locker storage date, and the number of items stored.

[0305] The pick-up information area AR32 is an area where information (pick-up information) regarding product pick-up instructions is printed. In the example shown in the figure, the pick-up information indicates the date and time range during which pick-up from the locker is possible, and the number of return slots in which the products to be picked up are stored (number of lockers in use). The content of the pick-up information in the pick-up information area AR32 is not particularly limited. For example, the pick-up information may indicate the return slot number of the return slot in which the products to be picked up are stored.

[0306] In addition, the positions of the code information area AR31 and the collection information area AR32 on the deposit slip are not particularly limited and may be changed as appropriate. For example, by placing the collection information area AR32 on the upper side of the deposit slip so that it is easily noticeable to the customer, it is expected that the customer will be able to more reliably understand the range of dates and times when collection is possible.

[0307] When a customer retrieves an item stored in the return slot of a locker, the customer brings the receipt and has the code information in the code information area AR31 read by a code recognition unit of the locker. The locker identifies a return port (return port for pick-up) in which a product associated with the same authentication information as that included in the read code information is stored. For example, if the authentication information is a transaction number, the locker identifies a return port in which a product associated with the same transaction number as that included in the read code information is stored as a return port for pick-up. The locker unlocks the identified return port for pick-up. On the other hand, if the return port for collection is not specified, the locker will not unlock any of the return ports. By controlling the unlocking of the lockers in this manner, customers can reliably collect their own items without mistaking them for items belonging to other customers.

[0308] [Sixth Modification] As explained in the previous embodiment, for products that are left stored in the return slot without being collected by a customer even after the delivery deadline has passed (uncollected products), a store clerk will collect the products. When the locker is connected to the management device 10 and the POS terminal 20 so as to be able to communicate with them, the locker can transmit to the management device 10 and the POS terminal 20 a storage history showing the results of storing the product at the return slot, a collection history showing the results of the product being picked up by the customer from the return slot, and so on. The storage history includes a history of opening and closing the return slot door when an item is stored corresponding to each return slot number, and a history of operations performed by the store staff in response to the storage. The collection history also includes a history of opening and closing the return door when the product is collected for each return port number, and a history of operations performed by the customer in response to the collection. The management device 10 and the POS terminal 20 can check the status of uncollected products (whether there are any untransacted products, the return slot where the untransacted products are stored, the time elapsed since the delivery deadline, etc.) by referring to the storage history and collection history received from the lockers and the locker-specific reservation status file, etc. Therefore, the management device 10 and the POS terminal 20 are configured to check the status of the uncollected products before the time when the store clerk should collect the uncollected products, and output the confirmed details to the store clerk, for example. For example, when a store clerk puts dry-cleaned products in a locker, the current status of uncollected products may be displayed on the locker return reservation confirmation screen displayed on the POS terminal 20. This allows the store clerk to smoothly proceed with the work by knowing in advance which products are currently uncollected and then collecting and storing these products in the locker. Furthermore, when a customer corresponding to the confirmed uncollected product is using the user terminal 50, the POS terminal 20 or the management device 10 may notify the cleaning app that there is an uncollected product. Furthermore, the notification that there is an uncollected product may be sent by SMS (Short Message Service) or email.

[0309] Furthermore, in the case where the locker is not communicatively connected to the management device 10 and the POS terminal 20, uncollected products may be handled as follows. In this case, when a store clerk operates the locker to switch to store clerk mode or the like (for example, this may be an operation on the return item collection button described above), the locker displays a list of unclaimed items on the display unit. The locker may also issue a slip showing the list of unclaimed items. The contents of the list of unclaimed items may be generated based on the storage history and collection history stored by the locker. The store clerk can collect the uncollected items from the lockers while checking the list of uncollected items output from the lockers as described above. Then, the store clerk registers the uncollected products by having the POS terminal 20 read the code information printed on the factory receipt attached to the collected uncollected products. The registration of the uncollected products (i.e., storing a list of the uncollected products) may be performed by the POS terminal 20, or may be performed by the management device 10 via the POS terminal 20. By registering uncollected items in this manner, the POS terminal 20 or management device 10 can notify the customer that there are uncollected items by sending a notification to the cleaning app on the user terminal 50, or by sending an email, SMS, etc.

[0310] [Seventh Variation] There are cases where the same user (customer) who uses a store corresponding to the cleaning system 1 of this embodiment is, for some reason, registered as a member multiple times. For example, a user who was a member and used the store in the past may not have used the store for a while, but when he or she resumes use of the store, may not remember whether or not he or she had previously registered as a member, and may register as a member again. In such a case, the current membership registration is performed for the same user without deleting the previous membership registration. As a result, the same user may be registered as a member multiple times. Customer information (customer master file (Figure 11(A)), customer performance summary file (Figure 11(B)), and point management file (Figure 11(C)) are managed for each registered member. Therefore, if there are multiple membership registrations for the same user, multiple pieces of customer information will exist for the same user.

[0311] The fact that a membership registration has been duplicated as described above may become apparent, for example, when a store clerk assists a customer and calls up customer information. In such a case, it is preferable to consolidate the membership registrations corresponding to the user into one, and also consolidate the customer information into one. Therefore, in this modified example, although multiple pieces of customer information exist for the same user as described above, it is possible to integrate the customer information into one piece as follows.

[0312] In this case, the store clerk specifies common information (such as name) about the membership registration details of the customers, and then performs an operation to declare the integration of the customer information on the POS terminal 20. In response to this operation, the POS terminal 20 displays a customer information integration screen on the store clerk side display unit 26. The customer information integration screen is a screen on which an operation to integrate multiple customer information having the specified common information is performed.

[0313] FIG. 37 shows an example of a customer information integration screen. The customer information integration screen in the figure shows a state in which two overlapping pieces of customer information for the same user are integrated. That is, the customer information integration screen in the figure shows two customer information areas AR21-1 and AR21-2 corresponding to "customer information 1" and "customer information 2", respectively, as the two overlapping pieces of customer information. In each of the customer information areas AR21-1 and AR21-2, predetermined items included in the customer information are arranged in the same order. In the following description, when there is no particular distinction between the customer information areas AR21-1 and AR21-2, they will be referred to as customer information area AR21.

[0314] An integrated operation area AR22 is arranged to the right of the customer information area AR21-2. In the integrated operation area AR22, an integrated button is arranged corresponding to each item of customer information arranged in the customer information area AR21. For example, two integration buttons, button "1" and button "2", are provided corresponding to the "Customer Number" item in customer information area AR21. When integrating customer information, the store clerk performs an operation to select the use of one of the customer numbers in customer information area AR21-1 or AR21-2. That is, the store clerk operates button "1" when selecting "Customer Number" in customer information area AR21-1, and operates button "2" when selecting "Customer Number" in customer information area AR21-2. Of button "1" and button "2", the selected integration button may be highlighted. In this way, for customer information items where two integration buttons, button "1" and button "2," are located, the store clerk can operate either button "1" or button "2" to specify the information used in either "Customer Information 1" or "Customer Information 2" for the integrated item. Specifically, when the store clerk operates button "1" in response to "Customer Number," "0000000003," which is the "Customer Number" in "Customer Information 1," is used as the integrated "Customer Number." Furthermore, for the "points," "unpaid balance," "deposit balance," etc. in the customer information area AR21, three buttons are provided in the integrated operation area AR22: a "1" button, a "2" button, and an "Add" button. In this case, the clerk can operate the "1" button or the "2" button to set the point balance of either "Customer Information 1" or "Customer Information 2" as the integrated point balance. Alternatively, the clerk can operate the "Add" button to set the number of points obtained by adding up the point balances of "Customer Information 1" and "Customer Information 2" as the integrated point balance.

[0315] After performing the operations for each item as described above, the store clerk operates the "Execute" button. In response to the operation of the "Execute" button, the management device 10 executes a process of integrating "Customer Information 1" and "Customer Information 2" into contents that reflect the search results in the integrated operation area AR22.

[0316] For example, one of the customer information areas AR21 may be set as the default content after integration. For example, if "customer information 1" out of "customer information 1" and "customer information 2" is set as the default content, the store clerk does not need to operate the "1" button when selecting an item in "customer information 1", but can operate the "1" button or the "add" button when selecting an item in "customer information 1" or adding to it. In addition, there are several examples of which of the multiple customer information should be set as the default. For example, the oldest or newest customer information can be set as the default for any of the date-related items such as the expiration date, the first acceptance date, the last acceptance date at the store, the last use date at the store, etc. Alternatively, the customer information with the largest point balance indicated in the "points" item can be set as the default. The number of pieces of customer information to be integrated is not limited to two, and a larger number of pieces of customer information may be integrated.

[0317] [Eighth Modification] The configuration of the present embodiment regarding the collection and storage of items using lockers is not limited to cleaning services. For example, the configuration of the present embodiment can be applied to a service of accepting requests for delivery of packages (one example of an item) from customers and receiving packages by customers, using lockers, boxes, etc. for managing packages provided by a delivery service company.

[0318] <Summary of the embodiment> (1) As described above, one aspect of this embodiment is an item management system (e.g., cleaning system 1) that includes a storage means (e.g., lockers 100, 200, 300) for storing items to be stored or retrieved, a schedule memory means for storing a schedule for retrieving items (e.g., dry-cleaning products) from the storage means or a schedule for storing items in the storage means, a determination means for determining whether or not a specified event has occurred in response to the collection or storage corresponding to the schedule stored in the schedule memory means, and an alarm control means for controlling the issuing of an alarm based on the determination result by the determination means. According to the above configuration, a notification is given when there are products left uncollected in a locker or when products that should be stored in a locker are not stored in a locker. This allows a store clerk (an example of a service provider) in the cleaning system 1 to remember to collect or store the products to be cleaned in the lockers.

[0319] (2) One aspect of this embodiment is that the above-mentioned item management system further includes a closing process restriction means for restricting the closing process of a terminal device (e.g., POS terminal 20) in which the item is registered as a storage target when the determination means determines that the specified operation has not been performed. According to the above configuration, it is possible to prevent the closing process of the POS terminal 20, etc. from being performed while there are still uncollected products in the locker or while the locker is still in a state where products that should be stored are not stored.

[0320] (3) One aspect of this embodiment is the above-mentioned item management system, wherein the notification control means, when issuing a notification corresponding to a case where a specified storage operation is not performed, notifies information about an item for which a specified storage operation has not been performed. According to the above configuration, when a notification is given in response to a fact that a product that should be stored in a locker is not stored, information about the product that is not stored can also be displayed. This allows the store clerk not only to realize that a product should be stored when the notification is received, but also to understand which product should be stored.

[0321] (4) One aspect of this embodiment is the above-mentioned item management system, wherein the determination means determines whether or not a specified event corresponding to storage has occurred by determining whether or not storage has been performed as indicated by the contents of the stored schedule, and the notification control means issues a notification based on the determination result of whether or not storage has been performed as indicated by the contents of the stored schedule. According to the above configuration, the cleaning system 1 can determine whether storage is completed as indicated by the stored schedule, for example, on the scheduled delivery date, and whether the stored product is correctly stored in the designated return slot. The cleaning system 1 can then issue a notification according to the result of the determination. In other words, if storage is not completed on the scheduled delivery date, the cleaning system 1 can notify the store clerk that the product has not been stored, and if the product has not been stored in the designated return slot, the cleaning system 1 can notify the store clerk that the product has been stored in the wrong place.

[0322] (5) One aspect of this embodiment is a sales data processing device including the notification control means of any of the item management systems (1) to (4) above. The sales data processing device of this embodiment may be any of the management device 10, the POS terminal 20, the store mobile terminal 30, and the factory terminal 40.

[0323] (6) One aspect of this embodiment is a program for causing a computer in an item management system to function as a schedule storage means for storing a schedule for retrieving items from a storage means for storing items to be stored or retrieved, or a schedule for storing items in the storage means, a judgment means for judging whether or not a specified event has occurred in response to the retrieval or storage corresponding to the schedule stored by the schedule storage means, and an alarm control means for controlling the issuance of an alarm based on the judgment result by the judgment means.

[0324] (7) One aspect of this embodiment is an item management method including a schedule storage step for storing a schedule for retrieving items from a storage means for storing the items to be stored or retrieved, or a schedule for storing items in the storage means, a determination step for determining whether or not a specified event has occurred in response to the retrieval or storage corresponding to the schedule stored in the schedule storage step, and an alarm control step for controlling to issue an alarm based on the determination result made by the determination step.

[0325] In addition, a program for implementing the functions of the above-mentioned management device 10, POS terminal 20, store mobile terminal 30, factory terminal 40, user terminal 50, locker (100, 200, 300), etc. may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read into a computer system and executed to perform processing as the above-mentioned management device 10, POS terminal 20, store mobile terminal 30, factory terminal 40, user terminal 50, locker (100, 200, 300), etc. Here, "reading a program recorded on a recording medium into a computer system and executing it" includes installing the program into a computer system. The "computer system" here includes hardware such as an OS and peripheral devices. In addition, the "computer system" may include multiple computer devices connected via a network including a communication line such as the Internet, a WAN, a LAN, or a dedicated line. In addition, the "computer-readable recording medium" refers to a portable medium such as a flexible disk, an optical magnetic disk, a ROM, a CD-ROM, etc., and a storage device such as a hard disk built into a computer system. In this way, the recording medium storing the program may be a non-transient recording medium such as a CD-ROM. The recording medium also includes a recording medium installed inside or outside the distribution server and accessible from the distribution server in order to distribute the program. The code of the program stored in the distribution server's recording medium may be different from the code of the program in a format executable by the terminal device. In other words, the format in which the program is stored in the distribution server does not matter as long as it can be downloaded from the distribution server and installed in a format executable by the terminal device. Note that the program may be divided into multiple parts, each of which may be downloaded at a different time and then combined in the terminal device, or each of the divided programs may be distributed by a different distribution server. Furthermore, the "computer-readable recording medium" includes a memory that holds the program for a certain period of time, such as a volatile memory (RAM) in a computer system that is a server or client when the program is transmitted via a network.The program may be for implementing some of the above-mentioned functions, or may be a so-called differential file (differential program) that can implement the above-mentioned functions in combination with a program already recorded in the computer system. [Explanation of symbols]

[0326] 1 cleaning system, 10 management device, 20 POS terminal, 26 store clerk display unit, 27 customer display unit, 28 printing unit, 30 store mobile terminal, 40 factory terminal, 50 user terminal, 90 network, 100 reception locker, 101 insertion slot, 102 collection unit, 200 common locker, 300 return locker, 310 return slot

Claims

1. a schedule storage unit that stores a schedule for retrieving an article from a storage means that stores an article to be stored or retrieved, or a schedule for storing an article in the storage means; a determination unit that determines whether or not a predetermined event occurs in response to collection or storage corresponding to the schedule stored in the storage unit by the schedule storage unit; a display unit that displays, when the determination unit determines that the predetermined event has not occurred, a message indicating that the predetermined event has not occurred on the POS terminal; a printing unit that prints a list of the absence of the predetermined event on the POS terminal as information related to the absence of the predetermined event in response to an operation after the display of the absence of the predetermined event on the display unit; An article management system comprising:

2. The list of storage errors of the items in the storage means printed by the printing unit includes code information used to unlock the storage area in the storage means that is associated with the items. The article management system according to claim 1 .

3. A computer as a POS terminal in an article management system, a schedule storage means for storing in a storage unit a schedule for retrieving articles from a storage means for storing articles to be stored or retrieved, or a schedule for storing articles in the storage means; a determination means for determining whether or not a predetermined event occurs in response to collection or storage corresponding to the schedule stored in the storage unit by the schedule storage means; a display means for displaying, when the determination means determines that the predetermined event does not occur, that the predetermined event does not occur; a printing means for printing a list of the absence of the predetermined event as information relating to the absence of the predetermined event in response to an operation after the display means has displayed the absence of the predetermined event; A program to function as a

4. An article management method in an article management system, comprising: a schedule storage step of causing a schedule storage unit to store in the storage unit a schedule for retrieving an article from a storage means for storing an article to be stored or retrieved, or a schedule for storing an article in the storage means; a determination step in which a determination unit determines whether or not a predetermined event occurs in response to collection or storage corresponding to the schedule stored in the storage unit by the schedule storage step; a display step of displaying, when the determination unit determines that the predetermined event does not occur, a display unit displaying, at the POS terminal, that the predetermined event does not occur; a printing step in which a printing unit prints a list of the absence of the predetermined event on the POS terminal as information related to the absence of the predetermined event in response to an operation after the display step in which the absence of the predetermined event is displayed; An article management method comprising:

5. a schedule storage means for storing in a storage unit a schedule for retrieving articles from a storage means for storing articles to be stored or retrieved, or a schedule for storing articles in the storage means; a determination means for determining whether or not a predetermined event occurs in response to collection or storage corresponding to the schedule stored in the storage unit by the schedule storage means; a display means for displaying, when the determination means determines that the predetermined event does not occur, a display indicating that the predetermined event does not occur; a printing means for printing a list of the absence of the predetermined event as information relating to the absence of the predetermined event in response to an operation after the display means has displayed the absence of the predetermined event; A POS terminal comprising:

Images