Cleaning systems, programs, and cleaning management methods

Abstract

To improve operational efficiency related to the use of storage facilities. [Solution] The cleaning system comprises an input means for inputting storage information regarding items to be cleaned by a user, a management means for managing the usage status of the storage unit, a calculation means for calculating the return date using the number of days required for completion based on the storage information and the usage status, and an output means for outputting the return date calculated by the calculation means.

Description

Technical Field

[0001] The present invention relates to a cleaning system, a program, and a cleaning management method.

Background Art

[0002] In cleaning shops, various efforts are being made to improve work efficiency. For example, a cleaning delivery system consisting of a cleaning bag and a locker unit has been proposed (see, for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the technology disclosed in Patent Document 1, there is a problem that the work efficiency regarding the use of storage facilities (such as lockers, etc.) is not sufficiently improved.

[0005] The present invention has been made in view of such circumstances, and its object is to provide a technology for improving the work efficiency regarding the use of storage facilities.

Means for Solving the Problems

[0006] To solve the above-mentioned problems, a cleaning system according to one aspect of the present invention comprises: an input means for inputting information about cleaning items received from a user; a management means for managing the usage status of a storage unit; a determination means for determining whether or not the cleaning items can be returned by the storage unit based on the number of days required for completion based on the information received and the usage status; a display means for displaying the determination result from the determination means; and a printing means for printing a sheet of paper that includes a description indicating that the items have been returned by the storage unit. [Effects of the Invention]

[0007] As described above, the efficiency of operations related to the use of storage facilities can be improved. [Brief explanation of the drawing]

[0008] [Figure 1] This is a schematic diagram of a cleaning system according to an embodiment of the present invention. [Figure 2] This is a functional block diagram of a POS terminal. [Figure 3] This is an example of the various types of information that the cleaning system stores. [Figure 4] This is an example of the various types of information that the cleaning system stores. [Figure 5] This is an example of the various types of information that the cleaning system stores. [Figure 6] This is an example of the various types of information that the cleaning system stores. [Figure 7] This is an example of the various types of information that the cleaning system stores. [Figure 8] This is an example of a verification image (an image showing the defective part). [Figure 9] This flowchart shows an example of the procedures when receiving goods. [Figure 10] This is an example of a membership card screen. [Figure 11] This is an example of a slip list screen. [Figure 12] This is an example of a transaction details screen (receipt screen, electronic receipt screen). [Figure 13] It is a flowchart showing an example of the operation at the time of delivering goods. [Figure 14] It is an example of a slip details screen (deposit slip screen, electronic deposit slip). [Figure 15] It is a flowchart showing an example of other operations at the time of delivering goods. [Figure 16] It is a flowchart showing an example of other operations at the time of delivering goods. [Figure 17] It is a flowchart showing an example of other operations at the time of delivering goods. [Figure 18] It is an external perspective view showing an example of a locker. [Figure 19] It is an example of various information stored in the cleaning system. [Figure 20] It is an example of information stored in the cleaning system. [Figure 21] It is an explanatory diagram for explaining the management of the usage status of the locker. [Figure 22] It is a flowchart showing an example of an operation related to a method for specifying available reservation dates. [Figure 23] It is an explanatory diagram for explaining a method for specifying available reservation dates. [Figure 24] It is an example of a locker return scheduled date calendar screen. [Figure 25] It is an example of a locker return scheduled date calendar screen. [Figure 26] It is an example of information stored in the cleaning system. [Figure 27] It is an example of a slip details screen (deposit slip screen, electronic deposit slip). [Figure 28] It is an example of a file used for determination regarding the adjacency of the return opening. [Figure 29] It is a flowchart showing an example of a method for determining the return opening. [Figure 30] It is a flowchart showing another example of a method for determining the return opening. [Figure 31] It is an explanatory diagram for explaining a method for determining the return opening. [Figure 32]This is an explanatory diagram illustrating other methods for determining the return slot. [Figure 33] This flowchart shows an example of the process when reserving a locker. [Figure 34] This flowchart shows an example of other actions taken when reserving a locker. [Figure 35] This flowchart shows an example of other actions taken when reserving a locker. [Figure 36] This is an example of a locker return reservation confirmation screen (locker return schedule list screen). [Figure 37] This is an example of a printed or issued medium. [Figure 38] This is an example of a printed or issued medium. [Figure 39] This is an example of a screen displayed on the return locker's display panel. [Figure 40] This is an example of a screen displayed on the return locker's display panel. [Figure 41] This is an example of a screen displayed on the return locker's display panel. [Figure 42] A flowchart illustrating an example of how the return locker works. [Figure 43] A flowchart illustrating an example of how the return locker works. [Modes for carrying out the invention]

[0009] Figure 1 is a schematic diagram of the cleaning system 1 according to an embodiment of the present invention. The cleaning system 1 is a system that supports cleaning operations.

[0010] The cleaning system 1 comprises a management device 10, a POS terminal (operator terminal) 20, a store mobile terminal 30 (operator terminal), a factory terminal 40, a user terminal 50, and a locker (described later). The management device 10, POS terminal 20, factory terminal 40, and user terminal 50 are connected to each other via a network 90. ​​The network 90 is not particularly limited. For example, the network 90 may utilize a wireless LAN, a mobile phone network, or the internet. The store mobile terminal 30 can communicate with the POS terminal 20, for example, via a wireless LAN. The locker may also be able to communicate with other devices (for example, the management device 10, the POS terminal 20, etc.) via the network 90.

[0011] In some cases, the configuration of Cleaning System 1 excluding the user terminal 50 may be referred to as Cleaning System 2. In some cases, the configuration comprising any two to five of the following may be referred to as Cleaning System 1: Management device 10, POS terminal 20, store mobile terminal 30, factory terminal 40, and locker. For example, a system consisting of three components: management device 10, POS terminal 20, and locker, or a system consisting of two components: POS terminal 20 and locker, may be referred to as Cleaning System 1 (or Cleaning System 2). In cases where there is no cleaning factory (i.e., where cleaning is performed at a cleaning shop), Cleaning System 1 (Cleaning System 2) does not include at least the factory terminal 40.

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

[0013] The POS terminal 20 is installed in the dry cleaning shop (dry cleaning drop-off shop) and operated by the dry cleaning shop's staff. The POS terminal 20 may be installed in an individual shop (a dry cleaning shop run by an individual) or in a chain shop (each store in a chain). In other words, the dry cleaning system 1 is applicable to both individual shops and chain shops. The store's portable terminal 30 is used inside the dry cleaning shop and is, for example, a tablet terminal.

[0014] The factory terminal 40 is installed in the cleaning factory and operated by the cleaning factory staff. The factory terminal 40 is used, for example, to check items before cleaning and to report completion after cleaning. The factory terminal 40 may also be, for example, a personal computer.

[0015] The user terminal 50 is a terminal operated by the user (for example, a smartphone, tablet, or personal computer owned by the user). The user terminal 50 may be configured to download and install application programs from the management device 10 or a device different from the management device 10 (a server (not shown)) via the network 90. ​​In this embodiment, an application program for users of the cleaning service (various cleaning-related services) in the cleaning system 1 (hereinafter sometimes simply referred to as the "cleaning app") is installed on the user terminal 50, and it is assumed that member registration has been completed using the cleaning app. The cleaning app may include data related to various screens and messages displayed on the display unit of the user terminal 50. In addition to starting, running, and stopping in response to user operations, the cleaning app may also start, run, and stop in response to requests from other programs (application programs or the OS). For example, the cleaning app may reside on the user terminal 50 without displaying a screen, monitor whether it has received information transmitted from other devices (for example, the management device 10), and if information is received, display a screen corresponding to the received information on the display unit without user operation.

[0016] Figure 2 is a functional block diagram of the POS terminal 20. The POS terminal 20 comprises a CPU 21, ROM 22, RAM 23, hard disk 24, display unit 25, input unit 26, printing unit 27, and communication unit 28, and these functional units are connected to each other via a bus 29. The CPU 21 is a central processing unit and controls the operation of the POS terminal 20, for example, by executing a program loaded into the RAM 23.

[0017] ROM22 is a read-only memory that stores various information, such as programs for operating the POS terminal 20. RAM23 is a temporary storage area that temporarily stores information referenced by the CPU 21 (programs, data, etc., read and extracted from ROM22), generated information, information received and transmitted via the communication unit 28, etc. Hard disk 24 is an auxiliary storage device that stores information referenced by the CPU 21, generated information, information received and transmitted via the communication unit 28, etc.

[0018] The display unit 25 is, for example, a liquid crystal display, and displays information to the store clerk operating the POS terminal 20. The input unit 26 is an input device for receiving various operations from the store clerk operating the POS terminal 20, and includes a touchpad, handheld scanner, card reader, etc., located on the display screen of the display unit 25. The printing unit 27 prints and issues various information (for example, various slips, lists of items to be delivered, etc.). The slips issued by the printing unit 27 are, for example, customer copies (also called "deposit slips" or "customer copies"; see Figure 27), factory copies (also called "factory copies"; see Figure 28), etc. The communication unit 28 is a communication interface for communicating with various devices via the network 90.

[0019] Figures 3 to 7 show examples of various types of information stored by the cleaning system 1. Figure 8 shows an example of an image (image data) indicating a defective (abnormal) area. Note that the "..." in each file shown in Figures 3 to 7 indicates that the value has been omitted. The same applies to the other figures.

[0020] (Customer Master File) Figure 3(A) shows an example of a customer master file stored by the management device 10. The customer master file is a file that stores various basic information about the customer (member) who is a user. The customer master file shown in Figure 3(A) stores information such as name (Kanji), name (phonetic), address, communication destination, email, telephone number (1), telephone number (2), application communication identification information, date of birth, membership registration date, and registered store (store code), associated with the customer code. The name (Kanji), name (phonetic), address, etc., are information obtained from the user at the time of membership registration.

[0021] The customer code is information used to identify each user in the cleaning system 1. For example, when a member registers, the management device 10 may assign (number) a unique customer code.

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

[0023] Telephone numbers (1) and (2) are telephone numbers used to make calls to the user. For example, if the user's terminal 50 is a smartphone, telephone number (1) may be the telephone number of the user's terminal 50 (smartphone), and telephone number (2) may be the telephone number of the user's home landline.

[0024] The application communication identification information is information used for communication by the cleaning application running on the user's terminal 50. The application communication identification information only needs to be information that can identify the user's terminal 50 in the communication of the cleaning application, and may be, for example, the IP address of the user's terminal 50, the unique identifier of the user's terminal 50, the telephone number of the user's terminal 50, or identification information different from the unique identifier (such as a token). The application communication identification information may be fixedly assigned to the user's terminal 50, or it may be temporarily assigned to the user's terminal 50 (for example, it may change each time the cleaning application is launched). If the application communication identification information is temporarily assigned, it is sufficient to store the latest application communication identification information.

[0025] In addition to the application communication identification information used to identify the user terminal 50 during communication with the cleaning application, the cleaning application may also store application user identification information (e.g., user ID) to identify the user.

[0026] The registered store is information indicating the store (dry cleaning shop) where the user has registered as a member, and in this embodiment, a store code is used. If the user registers as a member at a location other than a store (for example, if the user registers as a member from home or work via the dry cleaning app using the user terminal 50), the registered store may be the store automatically selected by the dry cleaning app at the time of registration, or it may be a store selected by the user from among the candidates presented by the dry cleaning app at the time of registration, or it may be a store freely selected by the user at the time of registration. At the time of registration, the dry cleaning app may search for the nearest store to the user's home based on the information entered by the user (for example, address, area code, etc.) and automatically select it as the registered store, or present it to the user as a selection candidate.

[0027] In this embodiment, the store code is a four-digit code consisting of the first two digits "TP" and the following two digits a store-specific number (e.g., 00-99).

[0028] (Customer performance summary file) Figure 3(B) shows an example of a customer performance summary file stored by the management device 10. The customer performance summary file stores information about the usage history of each customer (member) of the services (various cleaning services provided by the cleaning system 1). The customer performance summary file shown in Figure 3(B) stores performance information for all stores combined (rank, last usage date, usage frequency, average unit price) and performance information for the primary store used (rank, last usage date, usage frequency, average unit price), associated with the customer code. In this embodiment, the performance is summarized once a month (for example, on a specific day each month), and the summary results are stored in the customer performance summary file.

[0029] The last usage date is the date of the last use. Usage frequency is the number of uses in the past month. Usage amount is the total amount spent in the past month. Rank is information indicating the user's evaluation (contribution) and is calculated based on one or more of the last usage date, usage frequency, and usage amount from the past month or more. For example, a user who has used the service 12 or more times in the past six months and has used it for 24,000 yen or more in the past six months may be given the highest rank (e.g., S rank), and a user who has used the service 0 times in the past 12 months may be given the lowest rank (e.g., D rank). Alternatively, the average unit price for the past month may be calculated and stored in the customer performance summary file, either in lieu of or in addition to the usage amount.

[0030] (Point management file) Figure 3(C) shows an example of a point management file stored by the management device 10. The point management file stores information about points that are awarded according to service usage and can be used in place of cash (for example, 1 point is awarded for every 200 yen spent, and 1 point can be used in place of 100 yen). The point management file shown in Figure 3(C) stores the number of available points, etc., associated with the customer code. The point management file may also manage (store) the expiration date.

[0031] Note that the point management file shown in Figure 3 is configured for cases where the points to be managed are common to all stores in a chain (points awarded at each store are totaled and can be used at any store). However, if points are managed individually at each store in a chain (points awarded at a store can only be used at that store), for example, the number of usable points may be stored in association with the store code and customer code (i.e., separately for each store code and customer code).

[0032] (Coupon sales performance file) Figure 4(A) shows an example of a coupon sales record file stored by the management device 10. The coupon sales record file stores information related to the sales performance of coupons. The coupon sales record file shown in Figure 4(A) stores the sales date (issue date), coupon type, purchaser (customer code), etc., associated with the coupon management number. The management device 10 updates the coupon sales record file (adds new information) when a coupon is sold.

[0033] In this embodiment, the coupons are electronic coupons, and multiple types are available for each target product. Furthermore, the coupons in this embodiment are sold in units of multiple uses, offering a discounted price to the user. For example, in the case of a coupon for a dress shirt, the price for 11 uses (for 11 dress shirts (dry cleaning)) (3300 yen) is sold (issued) for the price of 10 uses (3000 yen). Although the coupons in this embodiment are electronic coupons as described above, in the following explanation, they may be counted as one coupon, two coupons, etc., just like paper coupons.

[0034] The coupon management number is information used in the cleaning system 1 to manage (identify) the sale (issuance) of coupons. For example, when a coupon is sold, the management device 10 may assign (number) a unique coupon management number (last two digits of the year - serial number, etc. The example shown in Figure 4 is the 369th coupon in 201X). The coupon type is information indicating the type (category) of coupon for each eligible product. The purchaser is information indicating the purchaser of the coupon.

[0035] (Coupon usage record file) Figure 4(B) shows an example of a coupon usage record file stored by the management device 10. The coupon usage record file stores information about coupon usage history for each user (by customer code). The coupon usage record file shown in Figure 4(B) stores information such as the purchase date (issue date), coupon type, expiration date, total number of uses, remaining number, and usage details for each use (date of use, number of uses) for each customer code, associated with the coupon management number. The management device 10 updates the coupon usage record file (updating the total number of uses, remaining number, usage details, etc.) when a coupon is used.

[0036] The expiration date indicates the expiration date of the coupon in question (the expiration date common to all 11 coupons). The total number of uses is the total number of uses in each transaction. The remaining number indicates the number of coupons that have not yet been used (i.e., the number that can be used).

[0037] In this embodiment, the expiration date of the coupons is the same regardless of which coupon is issued, as long as the sales date is the same (i.e., the expiration date is the same whether it is the first coupon or the last eleventh coupon). However, the expiration date may be different depending on the coupon number. For example, the expiration date for coupons 1 to 5 out of a total of 11 could be set to 28 days (4 weeks) from the sales date, and the expiration date for coupons 6 to 11 could be set to 56 days (8 weeks) from the sales date.

[0038] Furthermore, in this embodiment, the sales unit for coupons is the same regardless of the type of coupon (i.e., the target product) (11 uses, i.e., a total of 11 coupons), but the sales unit may be different depending on the type of coupon. For example, the sales unit for shirt coupons may be 11, and the sales unit for sweater coupons may be 6, so the sales unit may be smaller for more expensive products (see Figure 7(D)).

[0039] (Electronic document file) Figure 5 shows an example of an electronic slip file stored by the management device 10. The electronic slip file is a file that stores information about electronic slips that show the transaction details related to various cleaning services. The electronic slip file shown in Figure 5 stores information such as the date and time of receipt, store code, employee code, customer code, receipt category, number of items received, total charge, scheduled completion date, delivery completion date, receipt reminder date, and update date, associated with the slip number. The management device 10 updates the electronic slip file (adds new information) when goods are received and updates it as appropriate according to the progress of the service.

[0040] The slip number is information used to identify electronic slips in the cleaning system 1. For example, the POS terminal 20 may assign (number) a slip number when the goods are received. In this embodiment, a store-specific serial number (used cyclically) is assigned as the slip number. Specifically, a nine-digit slip number (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 store-specific number), the next digit being "-", and the next four digits being the serial number (0000 to 9999). Therefore, by referring to the slip number, it is possible to determine which store the electronic slip belongs to, without referring to the store code.

[0041] The "Date and Time of Drop-off" indicates the date and time when the dry cleaner received the item from the customer. Alternatively, the date and time the store employee entered the information into the POS terminal 20 at the time of drop-off may also be used as the date and time of drop-off.

[0042] The storage category is information indicating the method of storing goods. In this embodiment, the following methods of storing goods (methods of accepting goods) are available: regular store storage (sometimes called regular store acceptance), speed storage (sometimes called speed acceptance), collection storage (sometimes called collection acceptance), and locker storage (sometimes called locker acceptance). Storage category "1" indicates regular store storage, storage category "2" indicates speed storage, storage category "3()" indicates collection storage, and storage category "4" indicates locker storage. The part in parentheses in storage category "3()" is information (location code) indicating the collection location in collection storage.

[0043] Regular in-store drop-off is a method where the customer brings their items to the store's reception counter, where the store staff and the customer meet face-to-face for inspection and payment, and the items are accepted as drop-off items. Speed ​​drop-off is a method where the customer drops off their bagged items (items in a bagged state) at the store's reception counter (i.e., the store staff and the customer do not meet face-to-face for inspection or payment), and the drop-off is completed. With speed drop-off, the customer leaves their membership card (a membership card with their customer code and name written on it) along with the bag containing the items (for example, they may use a special speed drop-off bag with a pocket for inserting a card) with the store. The same applies to locker drop-off, which will be described later. Collection drop-off is a method where the dry cleaner goes to a designated collection location (the customer's home, a convenience store, etc.) to pick up the items and accepts them as drop-off items. Locker storage is a method of check-in where the user places their bagged goods (goods in a bagged state) into a designated locker (see Figure 18(A)) (i.e., the check-in process is completed without face-to-face inspection or payment between the store clerk and the user).

[0044] The "Number of Items Stored" indicates the number of items stored. Information about individual items is stored in the stored item information file (see Figure 6). The "Total Fee" indicates the total fee for all stored items.

[0045] The estimated completion date indicates the date on which the items will be finished (cleaned) and ready for handover to the user (the date on which the user can pick up the items). If multiple items are received (two or more items), the estimated completion date indicates the date on which all items will be ready for handover.

[0046] The delivery completion date indicates the date on which the goods were delivered to the user (the date the user received the goods). If multiple items were received, the delivery completion date indicates the date on which all received items were delivered.

[0047] The "Receipt Request Date" indicates 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 date of the last reminder may be managed (remembered) as the receipt request date, or each individual reminder date may be managed as a receipt request date. The method of reminding the user may be via the cleaning app, email, or telephone. The method of reminding may also be managed (remembered) along with the receipt request date.

[0048] The update date and time indicates the date and time when any information in the electronic document was updated. For example, if the delivery completion date is updated (entered), the date and time of that update will be the update date and time.

[0049] (Information file of items held in trust) Figure 6 shows an example of a consigned product information file stored by the management device 10. The consigned product information file is a file that stores information about each consigned product. The consigned product information file shown in Figure 6 stores the tag number, product type, processing type, fee, hold status, progress status, scheduled completion date, reservation status, delivery status, scheduled delivery date, delivery completion date, update date and time, etc., associated with the consigned product number. The management device 10 updates the electronic slip file (adds new information) when a product is consigned and updates it as appropriate according to the progress of the service, etc.

[0050] The item deposit number is information used to identify items deposited in the cleaning system 1. For example, when an item is deposited, the POS terminal 20 or management device 10 may assign (number) an item deposit number. In this embodiment, the item deposit number is obtained by adding a sub-number to the slip number. Specifically, a 13-digit item deposit number (including hyphens) is used, with the first 9 digits being the slip number, the next digit being "-", and the following 2 digits being the sub-number (01-99). Therefore, by referring to the item deposit number, it is possible to determine which electronic slip the item belongs to. Also, as mentioned above, since the store that conducted the transaction can be identified from the slip number, by referring to the item deposit number, it is possible to determine which store's transaction the item belongs to.

[0051] The tag number is information used to identify items received in the cleaning system 1. The tag number is, for example, the number printed on the tag attached to each item by the store clerk at the time of receiving the item, and is entered as the tag number for each item in the POS terminal 20. In this embodiment, the tag number (the number printed on the tag) is a 9-digit tag number (including hyphens) in total, with the first two digits being "TG", the next two digits being the last two digits of the store code (a store-specific number), 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 determine which store the item belongs to.

[0052] Product type indicates the type of product (see Figure 7(A)). Processing type indicates the type of processing (washing, storage, etc.) (see Figure 7(B)). Fee indicates the fee for the stored product (see Figure 7(D)).

[0053] The hold category indicates whether or not the process needs to be put on hold. In this embodiment, if the item being held is a specific item (an item with stains, tears, etc.; see Figure 7(E)), from the perspective of preventing problems, the user is asked to confirm the current condition of the item (stains, tears, etc.) before the cleaning factory actually processes (washes, etc.). A hold category of "0" indicates no need to hold (no reason for holding), a hold category of "1" indicates need to hold (before user confirmation), and a hold category of "2" indicates no need to hold (user confirmation completed).

[0054] The progress status indicates the progress of the process. Progress status "1" indicates the goods are in storage, progress status "2" indicates they are on hold, progress status "3" indicates that the work is completed, progress status "4" indicates that the goods are ready for delivery, progress status "5" indicates that delivery is scheduled, and progress status "6" indicates that delivery has been completed.

[0055] The estimated completion date indicates the date on which the consigned goods will be completed and ready for delivery to the user. Note that the estimated completion date in the consigned goods information file is the estimated completion date for each individual consigned goods, whereas the estimated completion date in the electronic slip file is the date on which all consigned goods within that electronic slip will be ready for delivery. In other words, the estimated completion date in the electronic slip file is the latest estimated completion date among the estimated completion dates for each consigned goods corresponding to that electronic slip, as shown in the consigned goods information file. Furthermore, in this embodiment, the estimated completion date is basically calculated based on the goods consigned date (reception date) and the required number of days (see Figure 7(E)), but the estimated completion date is delayed if the user's confirmation of a particular product is delayed.

[0056] The reservation category indicates whether or not a reservation has been made for the handover of the deposited items. Reservation category "0" indicates no reservation, reservation category "1" indicates a reservation made at the store, reservation category "2" indicates a reservation made by phone, and reservation category "3" indicates a reservation made via the app. The reservation details include the handover date and time and the handover method. Note that if you make a reservation for handover when you drop off your items in person (in cases where the deposit category is "1" or "2"), the reservation category will become "1 (Reservation made at the store)".

[0057] Reservations can be changed. For example, reservations made at the time of product drop-off can be changed by phone or through the cleaning app. When a reservation is changed, the reservation category may be saved to reflect the information at the time of the change. For example, if a reservation made at the time of product drop-off is changed by phone, the reservation category "1" from before the phone change may be updated to [2].

[0058] The delivery category is information indicating the method of delivery of the consigned goods. In this embodiment, the following delivery methods (methods of returning consigned goods) are available: regular store pickup (sometimes called regular store return), delivery pickup (sometimes called delivery return), and locker pickup (sometimes called locker return). Delivery category "0" indicates undecided, delivery category "1()" indicates regular store pickup, delivery category "2()" indicates delivery pickup, and delivery category "3" indicates locker pickup. The part in parentheses of delivery category "1()" is information indicating the pickup store (store code) in the case of regular store pickup. The part in parentheses of delivery category "2()" is information indicating the delivery location (user's home, convenience store, etc.) in the case of delivery pickup (location code). The part in parentheses of delivery category "3()" is information indicating the locker (locker number) in the case of locker pickup.

[0059] Standard store pickup (standard store return) is a method of handing over deposited items at the store's reception counter. Delivery pickup (delivery return) is a method of handing over deposited items at a designated delivery location. Locker pickup (locker return) is a method of handing over deposited items using a designated locker (see Figures 18(B) and 18(C)).

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

[0061] The scheduled delivery date indicates the date on which the deposited goods are scheduled to be delivered. If there is no delivery reservation (reservation type "0"), the scheduled delivery date will be undetermined (e.g., blank). On the other hand, if there is a delivery reservation (reservation types "1" to "3"), the scheduled delivery date will be the date specified by the user in that reservation.

[0062] Even if you do not have a pickup reservation (reservation category "0"), you can still pick up (or return) your item to the store after the scheduled completion date. In other words, as you might expect, customers can simply go to the store and pick up their item without any prior contact after the scheduled completion date.

[0063] The delivery completion date indicates the date on which the goods were delivered to the user (the date the user received the goods). Note that the delivery completion date in the consigned goods information file is the delivery completion date for each individual consigned item, whereas the delivery completion date in the electronic slip file is the date on which all consigned items within that electronic slip were delivered. In other words, the delivery completion date in the electronic slip file is the latest delivery completion date among the delivery completion dates for each consigned item corresponding to that electronic slip shown in the consigned goods information file.

[0064] The update date and time indicates the date and time when any information regarding the consigned item was updated. For example, if the delivery completion date is updated (entered), the date and time of that update will be the update date and time.

[0065] (Product type file) Figure 7(A) shows an example of a product type file stored by the management device 10. The product type file shown in Figure 7(A) stores information such as the type of product, associated with the product type. The POS terminal 20 may receive and store the product type file from the management device 10.

[0066] (Store file) Figure 7(B) shows an example of a store file stored by the management device 10. The store file shown in Figure 7(B) stores the store name, location (address), location (latitude and longitude), etc., associated with the store code. The POS terminal 20 may receive and store the store file from the management device 10.

[0067] (Processing type file) Figure 7(C) shows an example of a processing type file stored by the management device 10. The processing type file shown in Figure 7(C) stores processing types such as washing and storage, associated with each processing type. The POS terminal 20 may receive and store the processing type file from the management device 10.

[0068] (Service Basic File) Figure 7(D) shows an example of a service basic file stored by the management device 10. The service basic file shown in Figure 7(D) stores information such as fees and required days, associated with product type and processing type. The POS terminal 20 may receive and store the service basic file from the management device 10.

[0069] (Specific product management file) Figure 7(E) shows an example of a specific product management file stored by the management device 10. As described above, in this embodiment, if the deposited product is a specific product (a product with stains, fraying, etc.), the store (or cleaning factory) asks the user to confirm the current condition of the product in order to prevent problems. In particular, in the case of speed deposit or locker deposit, it is not possible to inspect the product together with the user at the time of deposit, so it is important to first have the user confirm the current condition from the perspective of preventing problems.

[0070] The specific product management file shown in Figure 7(E) stores information such as the defect category (sometimes called the abnormality category), confirmation image, corrective action, date and time of confirmation request, and confirmation date and time, associated with the received product number (in the specific product management file, this is actually the received product number of the received product, which is a specific product). The POS terminal 20 may store the specific product management file instead of, or in addition to, the management device 10.

[0071] The defect category indicates the nature of the defect that requires user verification. For example, defect category "1" indicates dirt, defect category "2" indicates stains, defect category "3" indicates fraying, defect category "4" indicates a broken button, and defect category "5" indicates a detached button (button falling off).

[0072] The confirmation image is information (e.g., URI; Uniform Resource Identifier) ​​indicating the storage location of an image (photograph, illustration, or other image data; see Figure 8) showing the defective part (location, extent, etc.). The confirmation image may be generated at the store (e.g., POS terminal 20) (by taking an image, scanning a handwritten template for each product, etc.) or at the cleaning factory (e.g., factory terminal 40). The confirmation image generated as described above is sent from the management device 10 to the user terminal 50 as a request for status confirmation. For example, the store may check whether the deposited item is a specific item, and if it is, the POS terminal 20 may generate a confirmation image, and the management device 10 may receive the confirmation image generated by the POS terminal 20 and send it to the user terminal 50. Alternatively, for example, the cleaning factory may check whether the deposited item is a specific item, and if it is, the factory terminal 40 may generate a confirmation image, and the management device 10 may receive the confirmation image generated by the factory terminal 40 and send it to the user terminal 50.

[0073] For requests to check the current status, you may use a cleaning app (you may display a confirmation image on the cleaning app screen, etc.) or email (you may attach a confirmation image to the email, etc.).

[0074] The user terminal 50 displays the confirmation image received from the management device 10 and accepts input from the user who has confirmed the image. For example, the user terminal 50 accepts input regarding confirmation that there is a defect in the entrusted item, and input regarding the countermeasures described later. Subsequently, the user terminal 50 transmits the input information from the user to the management device 10. The confirmation image shown in Figure 8 is an illustration showing that the entrusted item (shirt) has a stain on the right side of the abdomen and a button on the right sleeve is undone. The words such as "stain" and "button undone" were entered by, for example, a store employee (text input or selection from multiple candidate words). In addition, the image of the defective part and the above words can be enlarged on the user terminal 50, for example by touch.

[0075] The "Solution Method" refers to the method of addressing the defective part specified (or selected) by the user. For example, if the defective part is a stain (defect category "2"), this would specify whether or not to perform stain removal. The "Confirmation Request Date and Time" indicates the date and time when the user was requested to confirm the current condition of the specific product. The "Confirmation Date and Time" indicates the date and time when the user completed the current condition confirmation.

[0076] Note that the configuration of the specific product management file is not limited to the configuration shown in Figure 7(E). For example, the specific product management file shown in Figure 7(E) stores one set of defect classification and handling method for one consigned product (consigned product number), but it may store two or more sets of defect classification and handling method. For example, in the case of the shirt shown in Figure 8, the following may be stored in association with the consigned product number: the date and time of the confirmation request, the confirmation image, the defect classification of the first defective part "2 (stain)", the handling method for the first defective part, the date and time of confirmation for the first defective part, the defect classification of the second defective part "5 (button detached)", the handling method for the second defective part, the date and time of confirmation for the second defective part, etc. The shirt shown in Figure 8 is an example of a consigned product with multiple defective parts with different defect classifications, but the same applies to consigned products with multiple defective parts with the same defect classification (for example, a shirt with stains in two places, the collar and the sleeve). Furthermore, the specific product management file may store the date and time when the status check for each defective part is completed, as described above, or it may store a single date and time when the status check for all defective parts (the last one) is completed. Also, if all defective parts of a consigned product are visible to the user, there may be one confirmation image for that consigned product (for example, one image that can be rotated or otherwise manipulated, such as a CAD image), or there may be two or more.

[0077] Furthermore, if a single item being held has multiple defects (regardless of whether they are of the same or different defect category), the user may be able to specify (touch, etc.) each defective part on the confirmation image and specify a method of dealing with each defective part. For example, in the case of the shirt shown in Figure 8, a selection screen with options for dealing with a stain may be displayed based on the user touching the area of ​​a stain, and the user may select a method of dealing with the stain through this selection screen. Subsequently, a selection screen with options for dealing with a detached button may be displayed based on the user touching the area of ​​a detached button, and the user may select a method of dealing with the detached button through this selection screen. The fees for each of the methods presented as options (e.g., stain removal fees) may be displayed for each option. In addition, in order to efficiently respond to individual inquiries from users to stores, etc., regarding specific products, the item number may be displayed on the user terminal 50 (e.g., displayed near the confirmation image, displayed on the screen displaying the confirmation image, etc.). Furthermore, to prevent communication errors during inquiries and to improve efficiency, a shorter number than the stored item number may be used. For example, a unique inquiry number (a number with a simpler system than the stored item number) that can identify each specific item may be stored in the specific item management file, and the inquiry number may be displayed on the user terminal 50 (for example, as shown above).

[0078] As described above, before the actual processing (washing, etc.) of the items at the cleaning factory, the customer is notified of any abnormalities (stains, tears, etc.) in the items using confirmation images. This reduces the likelihood of problems such as customers making complaints after an abnormality has occurred in their items. Furthermore, by viewing the confirmation images, customers can easily understand the current situation, consider and specify appropriate solutions.

[0079] Next, Figures 9 to 12 will be used to explain the processing of items received by the cleaning system 1. In the explanation of Figures 9 to 12, the user terminal 50 will be assumed to be a smartphone.

[0080] Figure 9 is a flowchart illustrating an example of the operations when receiving goods. Specifically, the flowchart in Figure 9 shows an example of the operations when receiving goods from a customer (member) who has come to the store (cleaning shop) (i.e., in the case of normal store drop-off). The left side of Figure 9 shows the operations of the customer terminal 50, the center shows the operations of the POS terminal 20, and the right side shows the operations of the management device 10.

[0081] Figures 10 to 12 are examples of various screens displayed on the user terminal 50. Specifically, Figure 10 shows the membership card screen, Figure 11 shows the slip list screen, and Figure 12 shows the slip details screen (sometimes referred to as the receipt screen or electronic receipt screen). In the explanation of Figures 9 to 12, it is assumed that the cleaning application running on the user terminal 50 (smartphone) displays the above screens (membership card screen, slip details screen, and slip list screen).

[0082] Step S10 in Figure 9: The user terminal 50 displays a membership card screen on its display unit (touch panel) as shown in Figure 10. The membership card screen may also be the initial screen of the cleaning application. In other words, the membership card screen may be the first screen displayed on the display unit when the cleaning application is launched on the user terminal 50. The user terminal 50 may display a membership card screen it has stored on its own display unit, or it may obtain a membership card screen from the management device 10 and display it on its display unit.

[0083] Furthermore, when obtaining the membership card screen from the management device 10 and displaying it on the display unit, the user terminal 50 may transmit application communication identification information (or application user identification information) to the management device 10. In other words, the user terminal 50 may obtain the membership card screen from the management device 10 and display it on the display unit by transmitting application communication identification information (or application user identification information) to the management device 10. Furthermore, the management device 10 may refer to the customer master file, identify the user (customer code) based on the application communication identification information (or application user identification information) obtained from the user terminal 50, and transmit the membership card screen of the identified user to the user terminal 50.

[0084] The membership card screen shown in Figure 10 displays rank information, point information (number of available points), barcode G11, and receipt icon G12. Barcode G11 is a barcode representation of the customer code. The barcode G11 displayed on a user's membership card screen may be one generated by the management device 10 based on that user's customer code. For example, the management device 10 may assign (number) a customer code during member registration, generate a barcode based on the assigned customer code, and store it as the barcode to be displayed on the user's membership card screen.

[0085] The horizontal row at the bottom of the membership card screen, labeled "Membership Card," "Receipt," "Notification," "Coupon," and "Questionnaire," indicates the type of screen currently being displayed. The same applies to the bottom of the slip list screen shown in Figure 11, and the slip details screens shown in Figures 12, 14, and 27. Note that the slip list screen and slip details screen are classified as "Receipt" when the screens are categorized into five types: "Membership Card," "Receipt," "Notification," "Coupon," and "Questionnaire." Therefore, "Receipt" is displayed both when the slip list screen is displayed (Figure 11) and when the slip details screen is displayed (Figures 12, 14, and 27).

[0086] Step S11: The POS terminal 20 reads the barcode on the membership card screen based on the store clerk's operation (action). This allows the POS terminal 20 to recognize the customer code of the customer who has come to the store. Step S12: The POS terminal 20 transmits the customer code recognized by reading the barcode to the management device 10.

[0087] 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 the 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.

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

[0089] Alternatively, the POS terminal 20 may, based on receiving customer information in step S16, display a registration screen (not shown) on the display unit 25, and then display the customer information on the registration screen in step S17. Or, the POS terminal 20 may, based on receiving customer information in step S16, display a customer information display screen (not shown) different from the registration screen on the display unit 25, and then display the customer information on the customer information display screen in step S17.

[0090] Furthermore, the customer information displayed by the POS terminal 20 in step S17 may be only a portion of the information stored in the customer master file, etc. In other words, the POS terminal 20 may display only a portion of the information stored in the customer master file, etc. Also, in step S14, the management device 10 may extract only the information that the POS terminal 20 displays in step S17.

[0091] If the POS terminal 20 has stored the customer information to be displayed in step S17, then querying the management device 10 is unnecessary (i.e., steps S12 to S16 may be omitted).

[0092] Step S18: The POS terminal 20 registers the consigned items through the operation of the store clerk. Specifically, for example, the POS terminal 20 accepts input such as information about each consigned item (product type, processing type) and the tag number of the tag attached to each consigned item on the registration screen. If customer information is displayed on the customer information display screen instead of the registration screen in Step S17, the registration screen will be displayed through the operation of the store clerk, and then the terminal will accept input such as information about each consigned item (product type, processing type) and the tag number of the tag attached to each consigned item.

[0093] Step S19: The POS terminal 20 displays the scheduled completion date. Specifically, the POS terminal 20 obtains the required number of days for each consigned item by referring to the service basic file, calculates the scheduled completion date for each consigned item based on the obtained required number of days, and displays the calculated scheduled completion date for each consigned item on the display unit 25. In addition, the POS terminal 20 may display the latest scheduled completion date among the scheduled completion dates for each consigned item (i.e., the scheduled completion date when all consigned items are completed) on the display unit 25, instead of or in addition to the scheduled completion date for each consigned item.

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

[0095] Step S20: The POS terminal 20 settles the payment. Specifically, the POS terminal 20 refers to the service basic file to obtain the price of each deposited item, calculates a total price by summing the prices of each deposited item, and displays the total price along with the price of each deposited item on the display unit 25. Next, the POS terminal 20 recognizes the deposited amount based on the store clerk's operation (inputting the number of items to be deposited according to the deposit amount), and calculates the change amount from the total price and the deposited amount. Then, the POS terminal 20 displays the deposited amount and the change amount on the display unit 25 (payment settlement is complete). The store clerk then confirms the change amount displayed on the display unit 25, takes out the change, and hands it to the customer.

[0096] In step S20, if the POS terminal 20 does not store the service basic file, it is necessary to inquire about the fees for each consigned item from the management device 10, which stores the service basic file. However, if the POS terminal 20 does store the service basic file, the above inquiry is unnecessary.

[0097] 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 displays the total charge etc. on the display unit 25, then recognizes the amount received through the store clerk's operation (inserting the deposit into the coin slot of the automatic change dispenser), and calculates the amount of change from the total charge and the amount received. The POS terminal 20 then displays the amount received and the amount of change on the display unit 25 and dispenses the change into the coin slot of the automatic change dispenser (payment is completed).

[0098] In step S20, the POS terminal 20 prints and issues slips (the receipt in Figure 37, the factory copy in Figure 38), etc.

[0099] Step S21: The POS terminal 20 transmits the information acquired up to step S20 to the management device 10 as transaction information at the time of product deposit, based on the store clerk's operation. For example, the POS terminal 20 transmits transaction information to the management device 10, including the slip number, deposit date and time, store code, clerk code, customer code, deposit category (specifically deposit category "1 (normal store deposit)"), tag number of each deposited product, product type, processing type, etc. The slip number is assigned (numbered) by the POS terminal 20. The store code and clerk code are stored in the memory unit (RAM 23, hard disk 24) of the POS terminal 20. The clerk code is stored in the memory unit of the POS terminal 20 based on the store clerk's operation (for example, inputting the number of clerk codes, reading the clerk card with a card reader not shown, etc.).

[0100] Although the number of items received is stored in the electronic slip file (see Figure 5), the management device 10 can recognize the number of items received based on the number of items of information (e.g., the number of tag numbers) transmitted from the POS terminal 20. Therefore, the POS terminal 20 does not need to transmit the number of items received to the management device 10. In other words, the POS terminal 20 may transmit transaction information that includes the number of items received, or it may transmit a transaction that does not include the number of items received. Similarly, the POS terminal 20 may transmit transaction information that includes the total charge, or it may transmit a transaction that does not include the total charge.

[0101] Furthermore, while the consigned product information file (see Figure 6) stores the consigned product number, the management device 10 can assign (number) the consigned product number based on the slip number and the number of items consigned. Therefore, the POS terminal 20 does not necessarily have to assign a consigned product number to each consigned product and transmit it to the management device 10. In other words, the POS terminal 20 may transmit transaction information that includes the consigned product number for each consigned product, or it may transmit transactions that do not include the consigned product number for each consigned product.

[0102] Furthermore, the consigned goods information file (see Figure 6) stores information regarding the delivery reservation (reservation category, delivery category). If, before step S20, a store employee makes an input regarding the delivery (input of information corresponding to the delivery category), the POS terminal 20 transmits transaction information, including the input information regarding the delivery, to the management device 10.

[0103] Furthermore, the consigned product information file (see Figure 6) and the specific product management file store information about specific products (such as the hold category in the consigned product information file and the defective category in the specific product management file). If a store employee makes an input regarding a specific product before step S20, the POS terminal 20 transmits transaction information including the input information about the specific product to the management device 10. When the POS terminal 20 transmits transaction information including the input information about a specific product to the management device 10, it may also transmit information indicating the defective part (an image as shown in Figure 8) to the management device 10 (this transmission is unnecessary if the management device 10 has already prepared information indicating the defective part).

[0104] Step S22: The management device 10 receives transaction information from the POS terminal 20 when the goods are received. 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 transaction number information (records) to the electronic transaction file and adds new consigned product number information (records) to the consigned product information file. Furthermore, if the management device 10 receives transaction information that includes input information for a specific product, it also updates the specific product management file.

[0105] Step S24: The management device 10 updates the slip list screen based on the transaction information received in step S22 (i.e., by referring to the various files updated in step S23) (updating the screen information to add slips).

[0106] Step S25: The management device 10 generates a document details screen (generates screen information for the document to be added) based on the transaction information received in step S22 (i.e., by referring to the various files updated in step S23).

[0107] Step S26: The management device 10 transmits 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 to the user terminal 50.

[0108] Step S27: The user terminal 50 receives screen information from the management device 10 and stores the received screen information in the storage unit. Then, the flowchart in Figure 9 ends.

[0109] Furthermore, since the process of attaching tags to individual consigned items is time-consuming, if this process is postponed, the input of the tag number in step S18 will also be postponed. In step S21, it is necessary to send transaction information including the tag number to the management device 10, so the processing in step S21 will also be postponed. In other words, in the processing of steps S10 to S27 described above, it is also possible to perform the processing up to step S20 (in the processing of step S18, the input of the tag number is postponed and the process proceeds to step S19), and instead of immediately proceeding to step S21, the remaining processing of step S18 (input of the tag number) may be performed before proceeding to the processing from step S21 onwards.

[0110] Furthermore, when the receipt icon G12 is operated (tapped, etc.) on the membership card screen shown in Figure 10, the user's mobile device 50 displays a slip list screen as shown in Figure 11. The slip list screen displays an overview of all slips from all stores.

[0111] Furthermore, when the electronic slip column G21, the third row from the top in the slip list screen shown in Figure 11, is operated, the user terminal 50 displays the slip details screen as shown in Figure 12. The slip details screen corresponds to the conventional deposit slip and receipt. The slip details screen displays detailed information about the slip that was operated on the slip list screen.

[0112] Furthermore, when goods are received, instead of performing steps S26 and S27 in Figure 9, the system may be configured so that when a user takes action, the screen information of the updated slip list screen in step S24 and the screen information of the slip details screen generated in step S25 are sent from the management device 10 to the user terminal 50.

[0113] On the invoice details screen, "Currently held" corresponds to progress levels "1" to "5" in the held product information file (Figure 6), indicating that the item is not yet handed over. "Delivered" corresponds to progress level "9" in the held product information file (Figure 6), indicating that the item has been delivered. The user terminal 50 may simply sort items by expected completion date if there are multiple items, but if there is a mix of "Currently held" and "Delivered" items, it may prioritize displaying the "Currently held" items. In the example shown in Figure 12, the "Currently held" items (items in columns G34 and G35) are displayed above the "Delivered" items (item in column G36). The "Delivered" items (item in column G36) are also grayed out. If the items were sorted by expected completion date, the item in column G36 would be above the items in columns G34 and G35. The back icon G31 is a button used to return to the previous screen (the slip list screen (Figure 11)).

[0114] Based on the above, users can grasp an overview of the entire transaction (list of slips) on the slip list screen (Figure 11), and check the details of each transaction (each slip) on the slip details screen (Figure 12).

[0115] The items entrusted to the store are delivered to the cleaning factory for cleaning. When the cleaning is complete, an operator enters information that the items are finished into the factory terminal 40 and transmits it to the management device 10. Upon receiving the information that the items are finished, the management device 10 updates the progress status of the entrusted item information file (Figure 6) (specifically, it updates to "3 (Finished)"). The cleaned items are then delivered to the store. When the items arrive at the store, a store employee enters information that the items have arrived at the store into the POS terminal 20 and transmits it to the management device 10. Upon receiving the information that the items have arrived at the store, the management device 10 updates the progress status of the entrusted item information file (specifically, it updates to "4 (Ready for Pickup)"). Furthermore, when the handover of the items is complete, a store employee enters information that the handover is complete into the POS terminal 20 and transmits it to the management device 10. Upon receiving information that the handover of the goods has been completed, the management device 10 updates the progress status of the held goods information file (specifically, it updates it to "9 (Handover Complete)").

[0116] Furthermore, if the user has not yet confirmed the status of a particular product, the progress status in the stored product information file (Figure 6) will be "2 (On Hold)". When the user has confirmed the status, the management device 10 will update the progress status (specifically, to "1 (Product Stored)"). Also, if the user has made a reservation for the handover of the product, the progress status will be "5 (Handover Reservation Made)". When the handover of the product is completed, the management device 10 will update the progress status (specifically, to "9 (Handed Over)").

[0117] In the example shown in Figure 12, there were two types of information indicating the progress: "In Storage" and "Delivered." However, there are other types of information that can be used to indicate the progress. For example, there could be four types: "Before Finishing," "Finished," "Ready for Delivery," and "Delivered." "Before Finishing" corresponds to progress category "1" or "2" and indicates that the item is in a pre-finishing state at the factory. "Finished" corresponds to progress category "3" and indicates that the item is in a finished state at the factory. "Ready for Delivery" corresponds to progress category "4" and indicates that the item is ready for delivery. "Delivered" corresponds to progress category "9" and indicates that the item has been delivered. As another example, "On Hold" could be displayed, corresponding to progress category "2," indicating that the cleaning work is on hold. Alternatively, "Delivery Reservation in Progress" could be displayed, corresponding to progress category "5," indicating that a delivery reservation is being accepted. In the case of locker returns, for example, "Locker Return Reservation in Progress" could be displayed. When displaying the progress of a reservation, such as "Pickup reservation in progress" or "Locker return reservation in progress," you may also display the reservation date.

[0118] Next, Figures 13 to 16 will be used to explain the process of handing over goods using the cleaning system 1. In the explanation of Figures 13 to 15, the user terminal 50 is assumed to be a smartphone. On the other hand, in the explanation of Figure 16, the user terminal 50 does not necessarily have to be a portable device.

[0119] Figure 13 is a flowchart illustrating an example of the process during product handover. Specifically, the flowchart in Figure 13 shows an example of the process when handing over products to a customer who has come to the store (i.e., in the case of a normal store handover). The left side of Figure 13 shows the operation of the customer terminal 50, the center shows the operation of the POS terminal 20, and the right side shows the operation of the management device 10. Figure 14 is an example of the transaction details screen (receipt screen, electronic receipt screen). Figures 15 and 16 will be described later.

[0120] Step S30 in Figure 13: The user terminal 50 displays the slip details screen on its display unit (touch panel). In other words, when the receipt icon G12 is operated on the membership card screen, the user terminal 50 displays the slip list screen, and when the column for the desired slip is operated (selected) on the slip list screen, the slip details screen for the desired slip is displayed.

[0121] Step S31: The user terminal 50 accepts the selection of delivered goods on the invoice details screen. Specifically, the user terminal 50 selects a product when a product field is operated (tapped, etc.) on the invoice details screen. The user terminal 50 also highlights the product in the operated field (the field for the selected product). In the invoice details screen shown in Figure 14, the top product field G33 is shown as selected. Note that even if a product field for a product that has been delivered (field G36 in Figure 14) is operated, that product cannot be selected (it remains grayed out).

[0122] After selecting one or more items, if the selection completion icon G32 is clicked, the process moves to step S32 (i.e., the selection of items to be delivered is completed).

[0123] Furthermore, the user terminal 50 can select items from different slips at once. For example, if the user selects one or more items on the slip list screen of a certain slip through user operations, and then the back icon G31 is pressed without pressing the selection completion icon G32, the user terminal 50 displays the slip list screen. Subsequently, in response to user operations, the user terminal 50 displays the slip details screen of another slip from the slip list screen, and after selecting one or more items on the slip details screen of that other slip, if the selection completion icon G32 is pressed, the user terminal 50 selects one or more items from the first slip and one or more items from the next slip at once.

[0124] Step S32: The user terminal 50 generates a barcode that can identify the user and the selected product (product to be delivered) chosen by the user. Specifically, the user terminal 50 generates a barcode that contains the customer code and the tag number of each product selected in step S31. Step S33: The user terminal 50 displays the barcode generated in step S32 on its display unit.

[0125] Step S34: The POS terminal 20 reads the barcode displayed on the user terminal 50 based on the store clerk's operation (action). Step S35: The POS terminal 20 identifies the user and the selected products from the barcode read in step S34. Specifically, it identifies the customer code and the tag number of each selected product.

[0126] Step S36: The POS terminal 20 prints and issues a list of items to be picked up using the printing unit 27. Specifically, the POS terminal 20 issues a list of items to be picked up with the tag number of each item printed on it. The POS terminal 20 may also issue a list of items to be picked up with the customer code printed on it in addition to the tag number of each item.

[0127] The store staff then take the list of items to be picked up, issued in step S34, to the back room where the consigned items are stored. While checking the list of items to be picked up, they locate the items and hand them over to the user.

[0128] Step S37: The POS terminal 20 registers the completion of the handover based on the store clerk's operation. The registration of the completion of the handover only needs to be such that the cleaning system 1 can identify which of the deposited items has been handed over. For example, the POS terminal 20 may display a predetermined screen with confirmation buttons corresponding to each item that can be handed over (or each item that the store clerk wishes to handed over), and accept the store clerk's operation (touch) of the confirmation button on the predetermined screen.

[0129] Step S38: The POS terminal 20 transmits the information acquired up to step S20 to the management device 10 as transaction information at the time of product handover, based on the store clerk's operation. For example, the POS terminal 20 transmits transaction information to the management device 10, including the handover date and time, store code, clerk code, customer code, handover category (specifically, handover category "1 (normal store handover)"), and the tag number of each handover product. The store code and clerk code are stored in the memory unit (RAM 23, hard disk 24) of the POS terminal 20, as described above.

[0130] Step S39: The management device 10 receives transaction information from the POS terminal 20 at the time of product delivery. Step S40: The management device 10 updates various files based on the transaction information received in step S39. For example, the management device 10 updates the progress status of the relevant product in the product information file (specifically, to "9 (delivery completed)"), enters the delivery completion date, and updates the update date and time. Also, when the delivery of all consigned goods in the same slip is completed (when the progress status of all goods becomes "9"), the management device 10 enters the delivery completion date in the electronic slip file and updates the update date and time.

[0131] Step S41: The management device 10 updates the slip list screen based on the transaction information received in step S39 (i.e., by referring to the various files updated in step S40). However, if the information displayed on the slip list screen does not change (for example, if there are goods in the slip that have not yet been delivered, and the entire slip remains displayed as "in custody"), the management device 10 does not update the slip list screen.

[0132] Step S42: The management device 10 updates the transaction details screen based on the transaction information received in step S39 (i.e., by referring to the various files updated in step S40). Note that if the delivery of all goods on the transaction details screen is completed, the transaction details screen may be deleted (the screen information for that transaction is deleted).

[0133] Step S43: The management device 10 transmits the screen information of the slip list screen updated in step S41 and the screen information of the slip details screen updated in step S42 to the user terminal 50.

[0134] Step S44: The user terminal 50 receives screen information from the management device 10 and stores the received screen information in the storage unit. Then, the flowchart in Figure 13 ends.

[0135] Furthermore, when goods are delivered, instead of performing steps S43 and S44 in Figure 13, the system may be configured so that, if the user takes action, the screen information of the updated slip list screen in step S41 and the screen information of the updated slip details screen in step S42 are transmitted from the management device 10 to the user terminal 50.

[0136] In cleaning system 1, when products are handed over, as shown in the flowchart in Figure 13, the POS terminal 20 reads the barcode generated by the user terminal 50, making it possible to easily print and issue a list of products to be handed over, thereby improving operational efficiency.

[0137] In particular, cleaning system 1 is effective when a customer comes to the store and wishes to pick up only some of the items among several items that can be picked up. That is, in the technology of Patent Document 1, for example, when such a customer comes to the store, it is necessary to identify the items to be picked up based on the customer's verbal instructions or to write down the tag numbers on a piece of paper in order to find the items in the back room, which significantly reduces operational efficiency. On the other hand, with cleaning system 1, when the customer presents a barcode on the user terminal 50, a list of items to be picked up is output whether the customer wishes to pick up only some of the items or all of them, so there is no need for the customer's verbal instructions or notes, and operational efficiency is improved.

[0138] Furthermore, in the cleaning system 1, when handing over the product, as shown in the flowchart in Figure 13, the POS terminal 20 reads the barcode generated by the user terminal 50, thereby confirming whether the user who wishes to hand over the product has actually come to the store.

[0139] Furthermore, since the printing and issuance of the list of items to be picked up and the confirmation of the customer's visit are handled through a common process (generating a barcode and reading the generated barcode), inefficient situations such as finding an item based on the list of items to be picked up only to discover that the customer who was supposed to pick up the item had not actually shown up for the visit are eliminated.

[0140] Figure 15 is a flowchart illustrating another example of the process during product handover. Note that the flowchart in Figure 15 is a modified version of the flowchart in Figure 13 (dashed line A). Specifically, the difference is that while the flowchart in Figure 13 (part of dashed line A) uses a barcode to verify the customer's visit, the flowchart in Figure 15 (part of dashed line A) uses a one-time password (for example, a string of several digits).

[0141] Step S132 in Figure 15: Following step S31 in Figure 13, the user terminal 50 generates a one-time password (OTP). For example, the user terminal 50 generates a one-time password consisting of a number of any number of digits (e.g., 2 digits). It is assumed that the cleaning application installed on the user terminal 50 has a random number generator implemented.

[0142] Step S133: The user terminal 50 transmits information that can identify the user, information that can identify the selected product (product to be delivered) chosen by the user, and the OTP to the management device 10. Specifically, the user terminal 50 transmits the customer code, the tag number of each product selected in step S31 (see Figure 13), and the OTP generated in step S132 to the management device 10. Step S134: The management device 10 receives and stores information that can identify the user, information that can identify the selected product (product to be delivered) chosen by the user, and the OTP from the user terminal 50. Specifically, the management device 10 receives and stores the customer code, the tag number for each product, and the OTP from the user terminal 50.

[0143] Step S135: The user terminal 50 displays the OTP (e.g., "18") generated in step S133 on its display unit. The user then tells the store clerk the OTP displayed on the user terminal 50's display unit. Methods of telling the store clerk the OTP include, for example, telling the store clerk verbally or showing the store clerk the OTP displayed on the display unit.

[0144] Step S136: Upon operation by the store clerk, the POS terminal 20 obtains the OTP displayed on the display unit of the user terminal 50. For example, the POS terminal 20 may display a predetermined screen having an OTP input field and accept the input of the OTP (OTP provided by the user) by the store clerk into the input field. Step S137: The POS terminal 20 transmits the OTP acquired in step S136 to the management device 10 at the operation of the store clerk. Step S138: The management device 10 receives and stores the OTP from the POS terminal 20.

[0145] Step S139: The management device 10 compares the two OTPs. That is, the management device 10 determines whether the OTP received from the user terminal 50 in step S134 matches the OTP received from the POS terminal 20 in step S138. If they match, the process proceeds to step S140; otherwise, the process ends. Step S140: The management device 10 transmits information that can identify the selected products (products to be delivered) received in step S134 (specifically, the tag number of each product) to the POS terminal 20.

[0146] Step S141: The POS terminal 20 receives information that can identify the selected product (the product to be delivered) from the management device 10 (specifically, the tag number of each product).

[0147] According to the flowchart shown in Figure 15, the management device 10 compares the OTP obtained directly from the user terminal 50 with the OTP obtained via the POS terminal 20 to confirm whether the user who wishes to receive the item has actually come to the store. In other words, in step S136, the POS terminal 20 obtains the OTP displayed on the user terminal 50 through the operation of a store employee, but the process in step S136 is only possible if the user has actually come to the store (the process in step S136 is impossible if the user has not actually come to the store), thus ensuring that the store visit is confirmed.

[0148] If a user selects the desired items before arriving at the store, the user terminal 50 sends an OTP (One-Time Password) to the management device 10, and the management device 10 obtains the OTP from the user terminal 50 before the user arrives at the store. On the other hand, the management device 10 cannot obtain the OTP from the POS terminal 20 until the user arrives at the store. Therefore, if a user selects the desired items before arriving at the store, the management device 10 will stop processing after obtaining the OTP from the user terminal 50 (after executing the process in step S137). To address this, for example, in step S133, the user terminal 50 may send the OTP to the management device 10 only if there is user activity, and may not send the OTP to the management device 10 if there is no user activity. Alternatively, for example, if the management device 10 does not execute the process in step S138 (does not receive an OTP from the POS terminal 20) within a predetermined period (for example, 5 minutes) after executing the process in step S134 (after receiving the OTP from the user terminal 50), the process may be terminated.

[0149] Figure 16 is a flowchart illustrating another example of the process during product delivery. Note that the flowchart in Figure 16 replaces a portion of the flowchart in Figure 13 (dashed line A). When replacing a portion of the flowchart in Figure 13 with the flowchart in Figure 16 (i.e., when combining the flowchart in Figure 13 (with some exceptions) and the flowchart in Figure 16), the user terminal 50 does not need to be a portable device such as a smartphone (i.e., the user terminal 50 may be, for example, a smartphone or a personal computer stationary at home).

[0150] Step S232 in Figure 16: Following step S31 in Figure 13, the user terminal 50 transmits information that can identify the user and information that can identify the selected products (products to be delivered) selected by the user to the management device 10. Specifically, the user terminal 50 transmits the customer code and the tag numbers of each product selected in step S31 (see Figure 13) to the management device 10. Step S233: The management device 10 receives information from the user terminal 50 that can identify the user and the selected product (product to be delivered) selected by the user. Specifically, the management device 10 receives the customer code and the tag number of each product from the user terminal 50.

[0151] Step S234: The management device 10 transmits information that can identify the user and information that can identify the selected product (product to be delivered) chosen by the user to the POS terminal 20. Specifically, the management device 10 transmits the customer code and the tag number of each product, which were received in step S233, to the POS terminal 20. Step S235: The POS terminal 20 receives information from the management device 10 that can identify the user and the selected product (product to be delivered) chosen by the user. Specifically, the POS terminal 20 receives the customer code and the tag number of each product from the management device 10.

[0152] As shown in the flowchart in Figure 16, a list of items to be picked up can be printed and issued before the customer arrives at the store (meaning the items to be picked up can be found in the back room before the customer arrives), thus reducing the customer's waiting time at the store. Furthermore, store staff should put the items found in the back room into bags or other bundles to further reduce the customer's waiting time (it is also good to make it clear who the items are for). Note that the example shown in Figure 16 is a regular store pickup (pickup category "1") with reservation category "3" (reservation made (cleaning app)).

[0153] Figure 17 is a flowchart illustrating an example of other operations during product handover (operations when using the store's portable terminal 30). Note that the flowchart in Figure 17 is a replacement of a part of the flowchart in Figure 13 (dashed line B). The center of Figure 17 shows the operation of the POS terminal 20, and the right side shows the operation of the store's portable terminal 30.

[0154] Step S336 in Figure 17: Following step S35 in Figure 13 (or step S141 in Figure 15, or step S235 in Figure 16), the POS terminal 20 transmits information that identifies the selected products (specifically, the tag number of each product) to the store's portable terminal 30.

[0155] Step S337: The store's mobile terminal 30 receives information that allows it to identify the selected products (specifically, the tag number of each product) from the POS terminal 20. Step S338: The store's mobile terminal 30 displays information that identifies the selected products received in step S337 (specifically, the tag number of each product) on its display unit. For example, it may display information similar to the list of products to be picked up (see S36 in Figure 13) printed and issued by the POS terminal 20 on its display unit.

[0156] According to the flowchart shown in Figure 16, the display unit of the store's portable terminal 30, which can be brought into the back room, can display the same information as the list of items to be picked up that the POS terminal 20 prints and issues in the cleaning system 1. Therefore, just like the cleaning system 1, operational efficiency is improved.

[0157] (Sales promotion activities) In the above embodiment, promotional activities may be conducted for users who meet certain conditions (for example, new users who registered in the previous month, users with rank S, users whose birthday is approaching, etc.).

[0158] For example, the management device 10 may refer to a customer master file (Figure 3(A)) or a customer performance summary file (Figure 3(B)) to extract users who meet specific conditions, and then send messages, emails, or direct mail (DM) to the extracted users using the cleaning app. It may also set a campaign period and award points (points in Figure 3(C)) or coupons (coupons in Figure 4) that can be used in the cleaning system 1.

[0159] Alternatively, instead of sending messages or emails from the management device 10 to the user terminal 50, the POS terminal 20 may send messages, etc., to the user terminal 50 (for example, the user terminal 50 of a customer who has visited the store). In the manner in which the POS terminal 20 sends messages, etc., to the user terminal 50 (the same applies to the manner in which the POS terminal 20 sends advertising information to the user terminal 50), the management device 10 may extract users who meet specific conditions (the additional condition may be that the user is a registered member at the store) and send the extraction results to the POS terminal 20, or the POS terminal 20 itself may extract users who meet specific conditions (the additional condition may be that the user is a registered member at its own store) by accessing the customer master file stored by the management device 10.

[0160] Furthermore, by transmitting advertising information from the administrator device 10, advertisements may be displayed on the user terminal 50 (for example, at least one screen of the membership card screen, receipt list screen, or receipt details screen). Advertisements on the user terminal 50 have a higher exposure rate compared to advertisements on paper receipts, and therefore have a higher advertising effect. The administrator device 10 may also refer to various files (customer master file, customer performance file, point management file, coupon sales performance file, coupon usage performance file, etc.) to decide whether or not to send advertising information to each user, or to send different advertising information to each user.

[0161] Alternatively, instead of sending advertising information from the management device 10 to the user terminal 50, the POS terminal 20 may send the advertising information to the user terminal 50 (for example, the user terminal 50 of a customer who has visited the store).

[0162] Furthermore, if the administrator device 10 transmits advertising information to the user terminal 50 (and the POS terminal 20 does not transmit advertising information to the user terminal 50), the administrator device 10 may transmit information to the POS terminal 20 indicating which user received (or will receive) what kind of advertising information. For example, after transmitting advertising information to a user (or when transmitting or before transmitting), the administrator device 10 may transmit the advertising information transmitted to that user (or information summarizing the advertising information transmitted to that user) to the POS terminal 20 of the store that the user primarily uses (for example, the registered store where the user is a member). This makes it possible for store staff to make calls that are linked to the advertisements, and also makes it less likely that users will only become aware of the advertisements when they inquire about them.

[0163] (Bagged items accepted for storage) In the above embodiment, it is possible to accept goods in bags (bagged goods acceptance). Specifically, the above-mentioned speed acceptance (acceptance category "2") and locker acceptance (acceptance category "4") fall under bagged goods acceptance. Furthermore, if bagged goods are accepted at the collection point, collection acceptance (acceptance category "3") also falls under bagged goods acceptance.

[0164] The advantage of bagged laundry is that it eliminates the need for customers to wait for product inspection and payment. However, because the inspection is not conducted face-to-face with the customer at the time of deposit (the store clerk inspects the items individually when removing them from the bag), there is a risk of misunderstandings between the customer and the store regarding the deposited items. This could lead to problems such as customers claiming that the dry cleaner lost their items due to a misremembering, even though they did not actually deposit them. Such misremembering by the customer is unlikely to occur if not much time has passed since the items were deposited, and even if it does occur, the customer is likely to realize their mistake.

[0165] Therefore, in the above embodiment, when items are stored in bags, as soon as the store clerk inspects the items taken out of the bags and registers them in the POS terminal 20, the transaction information is immediately transmitted from the POS terminal 20 to the management device 10, and various processes (for example, the processes in steps S23 to S26 in Figure 9) are immediately performed in the management device 10. As a result, even in the case of stored items that are stored in bags without inspection at the time of storage, the user can check the details of the stored items on the receipt details screen as soon as possible (if the store clerk takes the items out of the bags and inspects them), which reduces the likelihood of the user misremembering and lowers the risk of trouble.

[0166] (Payment upon delivery of goods) In the case of the bagged goods storage service mentioned above, payment is made at the time of goods handover, not at the time of goods storage. Therefore, the challenge lies in ensuring smooth and reliable collection of payment.

[0167] In the above embodiment, credit card payment, prepaid payment, and point payment are possible. Specifically, when the management device 10 transmits the slip details screen etc. to the user terminal 50 (step S26 in Figure 9), in addition to the slip details screen etc., it transmits a screen that allows the user to select a payment method (credit card payment, prepaid payment, coupon payment, point payment) and receives a response from the user terminal 50 regarding the payment method. The management device 10 may also transmit the screen that allows the user to select a payment method at a different time than when transmitting the slip details screen etc.

[0168] Furthermore, the cleaning process at the cleaning factory may be initiated after the management device 10 receives a response regarding the payment method from the user terminal 50 (after the payment has actually been completed using the payment method selected by the user). In other words, the management device 10 may, at least, send a screen prompting the user to select a payment method before starting the cleaning process at the cleaning factory.

[0169] The management device 10 has a function to communicate with a payment server (not shown), and communicates with the payment server to perform credit card payments. The management device 10 manages information (not shown) related to the prepaid card, checks the available balance, and processes the prepaid payment. The management device 10 manages information related to coupons (Figure 4(A)(B)), checks the remaining number, and processes coupon payments. The management device 10 manages point information (Figure 3(C)), checks the number of available points, and then performs point payment.

[0170] Furthermore, to prepare for situations where payment cannot be processed using the payment method selected by the user (for example, if the user selects a prepaid payment method, and the available balance for the prepaid payment is insufficient or no deposit has been made in the first place; the same applies to coupon payments and point payments), it may be possible to accept the selection of multiple payment methods. In addition, if the selection of multiple payment methods is accepted, it may be possible to accept the user's specification of the priority of the payment methods. For example, if the user specifies the priority as coupon payment → point payment → credit card payment, the system may execute the coupon payment, use point payment for any remaining balance that cannot be recovered by point payment, and then use credit card payment for any remaining balance that cannot be recovered by either coupon payment or point payment.

[0171] In addition, while users can check their available points on the user terminal 50 (for example, as shown on the membership card screen in Figure 10), it is also possible to allow users to check their available prepaid balance and the number of remaining coupons on the user terminal 50.

[0172] (Other methods of storing goods) As an example of how goods are received from customers, the method illustrated in Figure 9 is a method where the customer and the store clerk meet face-to-face at the store (receiving category "1 (normal store receiving)"). However, as mentioned above, the methods of receiving goods from customers are not limited to the method where the customer and the store clerk meet face-to-face at the store. As mentioned above, there are also methods such as receiving bagged goods at the store (receiving category "2 (speed receiving)"), receiving goods at a location other than the store (home, convenience store, etc.) (receiving category "3 (collection receiving)"), and receiving bagged goods via a locker (receiving category "4 (locker receiving)").

[0173] (Other methods of product delivery) The methods of handing over consigned goods to users, as exemplified in Figures 13, 15, 16, and 17, are all methods where the user and store clerk meet face-to-face at the store (handover category "1"). However, as mentioned above, the methods of handing over consigned goods to users are not limited to methods where the user and store clerk meet face-to-face at the store. As mentioned above, there are also delivery handovers where consigned goods are handed over at locations other than the store (home, convenience store, etc.) (handover category "2"), and locker handovers where consigned goods are handed over via lockers (handover category "3").

[0174] Delivery will be made based on the user's delivery instructions (a request indicating a desire for delivery). Alternatively, the store may omit individual delivery instructions if the user specifies that all subsequent deliveries will be by delivery. Store staff will deliver the goods to the designated delivery location on the designated delivery date, based on the delivery instructions.

[0175] When a delivery / pickup instruction is received at the time of store visit, the electronic slip file stores reservation category "1 (reserved at store)" and pickup category "2 (delivery / pickup)" based on the transaction information transmitted from the POS terminal 20 to the management device 10. When a delivery / pickup instruction is received by telephone, the reservation category "2 (reserved by telephone)" and pickup category "2 (delivery / pickup)" are stored. When a delivery / pickup instruction is received via the cleaning app, the reservation category "3 (reserved via app)" and pickup category "2 (delivery / pickup)" are stored.

[0176] Locker retrieval (locker return) is carried out based on the user's instruction for locker retrieval (a request indicating a desire for locker retrieval). Based on the instruction, store staff will place the items to be returned to the locker (items that are to be retrieved in the locker) into the locker and lock it the day before the return date (the day the locker is retrieved), and the user will retrieve the items from the locker on the return date without the assistance of store staff.

[0177] When a customer requests locker pickup upon arrival at the store, the electronic slip file stores reservation category "1 (reserved at the store)" and pickup category "3 (locker pickup)" based on the transaction information transmitted from the POS terminal 20 to the management device 10. When a customer requests locker pickup by phone, the reservation category "2 (reserved by phone)" and pickup category "3 (locker pickup)" are stored. When a customer requests locker pickup via the cleaning app, the reservation category "3 (reserved via app)" and pickup category "3 (locker pickup)" are stored.

[0178] (Confirmation of customer's visit) The method for confirming a user's visit is not limited to the methods described above. For example, unlike the OTP generated each time on the user terminal 50, a predetermined string may be used between the user terminal 50 and the management device 10 to confirm the user's visit.

[0179] Furthermore, if the user terminal 50 is equipped with Bluetooth® functionality, Bluetooth may be used to confirm the user's arrival at the store. For example, a Bluetooth-enabled device may be installed at the store, and by identifying the user terminal 50 connected to the store's Bluetooth-enabled device via Bluetooth, it may be determined that a user possessing the user terminal 50 has arrived at the store. Similarly, a wireless LAN router or leaky coaxial cable may be installed at the store to confirm the user's arrival.

[0180] Furthermore, if the user terminal 50 is equipped with GPS functionality, the GPS functionality may be used to confirm the user's visit to the store. For example, the management device 10 may acquire the location information of the user terminal 50 and compare it with the store's location stored in the store file (Figure 7(B)). If the location information of the user terminal 50 matches (or matches within a certain range) the store's location (latitude and longitude), the management device 10 may determine that the user possessing the user terminal 50 has visited the store.

[0181] In the above embodiment, an example was described in which the user selects the items they wish to receive using the user terminal 50. However, selection may also be made using other devices (for example, the POS terminal 20 or the store's mobile terminal 30). In other words, the store staff may select the items on behalf of the user without having to operate the user terminal 50. This allows for the smooth handover of items even if the user is unfamiliar with operating the cleaning app or is uncomfortable with the store staff touching the user terminal 50.

[0182] Furthermore, in the above embodiment, the user terminal 50 displays both "currently held" and "delivered" slips on the slip list screen (see Figure 11). However, the user may choose to display only "currently held" slips or only "delivered" slips. When only "currently held" slips are displayed, a message or mark indicating that only "currently held" slips are being displayed may be shown. When only "delivered" slips are being displayed, a message indicating that only "delivered" slips are being displayed may be shown.

[0183] Furthermore, in the above embodiment, the user terminal 50 displays both "currently being held" and "delivered" items on the slip details screen (see Figure 12, etc.). However, the user may choose to display only "currently being held" items or only "delivered" items. When only "currently being held" items are displayed, a message or mark indicating that only "currently being held" items are being displayed may be shown. When only "delivered" items are being displayed, a message indicating that only "delivered" items are being displayed may be shown.

[0184] Furthermore, when providing a service to store cleaned items for an extended period (e.g., within six months), it is possible to restrict the selection of items to be handed over in relation to items scheduled for storage or currently in storage. For example, on the invoice details screen, items scheduled for storage or currently in storage may be hidden or grayed out so that users cannot select them as items to be handed over. Alternatively, if an item scheduled for storage or currently in storage is selected, a message may be displayed indicating that the selected item cannot be handed over because it is an item scheduled for storage (or currently in storage). In addition, when an item scheduled for storage or currently in storage is selected, the user may be given the option to either maintain storage (i.e., cancel and invalidate the handover selection) or discontinue storage and hand over (i.e., activate the handover selection), and if the user chooses to discontinue storage and hand over, the handover may be made possible. According to the above, it is possible to prevent users from mistakenly (against their will) taking back items they wish to store, thereby preventing a decrease in user satisfaction.

[0185] Furthermore, the cleaning factory may input comments (additional information) for the user. For example, the factory terminal 40 may input comments related to a specific product (a product with stains, fraying, etc.), such as "A new button has been attached" or "Some stains remain," or it may input comments unrelated to a specific product, such as "There was something in the pocket." The factory terminal 40 transmits the input information (comments) to the management device 10, and the management device 10 transmits it to the user terminal 50. The management device 10 may also transmit the comments to the POS terminal 20 in addition to or instead of the user terminal 50. The management device 10 may also store the comments obtained from the factory terminal 40, for example, in a file containing the received product information.

[0186] Furthermore, an electronic tag is attached to each item after cleaning is complete, and the location of each item is obtained by detecting the electronic tag with a reader and stored as the storage location of each item (for example, the storage location is stored in association with the tag number of each item). When handing over the items, the POS terminal 20 (or store mobile terminal 30) may display the storage location of the item to be handed over on its display unit (for example, displaying the storage location on an image of the backroom floor layout). This makes it easier for store staff to find the desired item (the item to be handed over) from among the many items stored in the backroom.

[0187] Furthermore, lamps (operable by control from the POS terminal 20 or the store's mobile terminal 30) are placed at each of the multiple storage locations in the back room, and the store staff store the storage location of each item that has been cleaned in the POS terminal 20 (or the store's mobile terminal 30) (for example, by associating the storage location with the tag number of each item). When handing over the items, the POS terminal 20 (or the store's mobile terminal 30) may turn on the lamp corresponding to the storage location of the item to be handed over.

[0188] Alternatively, the system may use the camera on the store's mobile terminal 30 to perform image recognition and find the desired product from the back room. For example, when a store employee receives a product from a customer (or returns to the store after cleaning is complete), they can take an image of each product (for example, using the camera on the store's mobile terminal 30) and store it as an image of each product (for example, by associating the image with the tag number of each product). Then, when handing over the product, the camera on the store's mobile terminal 30 can be pointed at the products stored in the back room to acquire a pass-through image, and it can be determined whether it matches the image of the product to be handed over (an image corresponding to the tag number received from the POS terminal 20, etc.). The product from which a pass-through image matching the image of the product to be handed over can be obtained can be identified as the product to be handed over.

[0189] Figure 18 is an external perspective view showing an example of a locker. The lockers used in cleaning system 1 include lockers used when goods are received (i.e., lockers used at the locker reception) and lockers used when goods are returned (i.e., lockers used when returning goods). Figure 18(A) is an external perspective view of a dedicated locker 100 used only at the locker reception (hereinafter sometimes referred to as a reception-only locker). Figure 18(B) is an external perspective view of a locker 200 used for both locker reception and locker return (hereinafter sometimes referred to as a common locker). Figure 18(C) is an external perspective view of a dedicated locker 300 used only for locker return (hereinafter sometimes referred to as a return-only common locker).

[0190] (Reception lockers) The reception locker 100 includes, for example, an input slot 101 for inserting goods, a collection unit 102 for collecting goods inserted from the input slot, a card insertion / discharge slot 103 for inserting and discharging cards, a display unit 104 for displaying various information, an input operation unit 105 for receiving input operations, a code recognition unit 106 for reading and recognizing barcodes, an output slot 107 for issuing receipts and other media, a storage unit (not shown), and a control unit (not shown) for controlling the display on the display unit 104 and locking the input slot door (described later). However, the reception locker 100 does not necessarily have to have all of the above-described components. For example, it may have either the input operation unit 105 or the code recognition unit 106, but not the other.

[0191] The deposit slot 101 is equipped with a curtain-shaped door (hereinafter referred to as the deposit slot door). The deposit slot door is lockable. When the deposit slot door is unlocked, users can deposit goods (items to be deposited) into the deposit slot 101. On the other hand, when the deposit slot door is locked, users cannot deposit goods into the deposit slot 101. The deposit slot door is normally locked, unlocked when predetermined conditions are met, and locked again after goods have been deposited.

[0192] Various conditions can be considered as predetermined conditions for unlocking the card slot door. For example, authentication may be performed based on either or both of the following: information on the card inserted into the card insertion / discharge slot 103 (e.g., a membership card), information entered into the input operation unit 105 (e.g., a PIN), and the card slot door may be unlocked if authentication is successful. Alternatively, 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), and the card slot door may be unlocked if authentication is successful. Furthermore, authentication may be performed based on information recognized by the code recognition unit 106 and information entered into the input operation unit 105, and the card slot door may be unlocked if authentication is successful.

[0193] Various methods can be considered for recognizing the insertion of goods. For example, a sensor capable of detecting whether the input door is in its normal state (with its surface vertical due to its own weight) (in other words, a sensor capable of detecting whether the input door is pushed inward) could be installed, and the insertion of goods could be recognized based on the detection result of the sensor. After goods are inserted, the input door, which was pushed inward, will return to its original state (normal state) due to its own weight. After returning to its original state, the input door may be locked (automatically locked) if it remains in that state for a predetermined time (a time that can be considered as the completion of all insertion operations, even if there are multiple insertion operations by the same user; for example, 10 seconds).

[0194] A basket with casters is designed to fit inside the collection section 102. In other words, products placed in the input opening 101 are placed inside the basket with casters. Furthermore, the products (basket with casters) inside the collection section 102 can be removed from both the front and the back.

[0195] The retrieval unit 102 is equipped with a door (hereinafter referred to as the retrieval unit door) at a position from which the goods can be removed. The retrieval unit door is lockable. When the retrieval unit door is unlocked, store employees can remove goods (baskets with casters) from the retrieval unit 102. On the other hand, when the retrieval unit door is locked, store employees cannot remove goods from the retrieval unit 102. The input door is normally locked and is unlocked with a key managed by store employees, and locked again after the goods have been removed.

[0196] Although it was explained that the items (baskets with casters) in the collection unit 102 can be retrieved from both the front and the back, if, for example, the front of the collection unit 102 is connected to the outside of the store and the back is connected to the inside of the store, the baskets with casters can be retrieved from inside the store, eliminating the need to move the baskets that were retrieved outside the store into the store. In other words, if the reception locker 100 is installed so that the front is connected to the outside of the store and the back is connected to the inside of the store, the items in the collection unit 102 can be retrieved from both the front and the back, making the retrieval of items more efficient.

[0197] Furthermore, the store interior (back) may be designed to automatically collect items that have been placed into the input slot from outside the store (front) (without requiring preparation such as placing a wheeled basket into the collection unit 102 or removing a wheeled basket with items from the collection unit 102). For example, the bottom of the collection unit 102 may be sloped so that items placed from outside the store naturally move towards the inside of the store, and the store interior may simply be an opening without a collection door. This allows items placed from outside the store to automatically slide down into the opening on the inside of the store, eliminating the need to worry about the capacity (volume) of the collection unit 102 (for example, users can put items in at any time, and store staff do not need to take items out of the collection unit 102 as needed). A large wheeled basket or the like can be placed below the opening to catch items that slide down.

[0198] Furthermore, to facilitate the movement of goods into the store, the material of the inclined section (bottom) may be made of a slippery material (a material with a low coefficient of friction) (the surface may be plated, coated, etc. to make it slippery). In addition, a rotating body may be used instead of or in addition to the material (including coatings, etc.). For example, cylindrical objects (rollers) or spherical objects may be embedded in a part of the inclined section, or embedded throughout the entire inclined section (the rollers or spheres may form the surface of the inclined section).

[0199] Furthermore, the collection door may not be locked, but rather unlocked when certain conditions are met, similar to the input door on the input slot 101.

[0200] Various conditions can be considered for unlocking the collection unit door. For example, authentication may be performed based on either or both of the following: information on a card inserted into the card insertion / discharge slot 203 (e.g., an administrator card managed by a store employee, etc.), or information entered into the input operation unit 105 (e.g., a PIN code, etc.). If authentication is successful, the collection unit door may be unlocked. Furthermore, for added security, the collection unit door may be unlocked using a key managed by a store employee, etc., in combination with the aforementioned authentication.

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

[0202] If the reception locker 100 can communicate with other devices (i.e., it is equipped with a communication unit), for example, the management device 10 may periodically (for example, daily) generate information (a PIN code) to be entered into the input operation unit 105 and transmit the generated information to the user terminal 50 and the reception locker 100. In other words, as a predetermined condition for unlocking the deposit slot door, the user may input information confirmed on the user terminal 50 (a PIN code generated by the management device 10) into the input operation unit 105, and the reception locker 100 may compare the information transmitted from the management device 10 with the information entered into the input operation unit 105 and perform authentication. For example, the management device 10 may periodically (for example, daily) generate information (a PIN code) to be entered into the input operation unit 105 and transmit the generated information to the POS terminal 20 and the reception locker 100. In other words, as a predetermined condition for unlocking the collection door, store employees may input information (such as a PIN generated in the management device 10) confirmed on the POS terminal 20 (or store-use mobile terminal 30) into the input operation unit 105, and the reception locker 100 may perform authentication by comparing the information transmitted from the management device 10 with the information entered into the input operation unit 105.

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

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

[0205] (Shared lockers) The common locker 200 includes, for example, an input slot 201, a retrieval unit 202, a card insertion / discharge slot 203, a display unit 204, an input operation unit 205, a code recognition unit 206, an issuance slot 207, a storage unit (not shown), a control unit (not shown) that controls the display on the display unit 204 and the locking of the return slot door (described later), etc., and multiple return slots (return units) 210. Note that the input slot 201, retrieval unit 202, card insertion / discharge slot 203, display unit 204, input operation unit 205, code recognition unit 206, and issuance slot 207 of the common locker 200 are the same as the input slot 101, retrieval unit 102, card insertion / discharge slot 103, display unit 104, input operation unit 105, code recognition unit 106, and issuance slot 107 of the reception-only locker 100, so their explanation is omitted. Note that the common locker 200 does not necessarily have to have all of the above-described configurations. For example, the device may include either the input operation unit 205 or the code recognition unit 206, but not the other.

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

[0207] The common locker 200 shown in Figure 18(B) has a total of 12 return slots 210, arranged in two rows and six columns. In Figure 18(B), the upper left return slot is labeled 210, representing the 12 return slots. Each return slot is assigned a return slot number (sometimes called a "door number") as a management number. For example, as shown in Figure 18(B), the return slot numbers are "H11" for the upper left, "H12" for the lower left, "H21" for the upper second column from the left, "H22" for the lower second column from the left, ..., "H61" for the upper right, and "H62" for the upper right. Alternatively, stickers or other labels indicating the return slot number may be attached to each return slot so that the return slot number can be identified within the common locker 200.

[0208] Each of the return slots 21 is equipped with a door (hereinafter referred to as the return slot door). Each return slot door can be locked individually. When a return slot door is unlocked, store staff can place goods (goods to be returned to the user) into the return slot 21. Also, when a return slot door is unlocked, the user can take goods out of the return slot 21. On the other hand, when a return slot door is locked, the user cannot take goods out of the return slot 21. Also, when a return slot door is locked, store staff cannot place goods into the return slot 21. The return slot doors are normally locked and are unlocked when certain conditions are met. They are locked after goods have been placed in or taken out.

[0209] Various conditions can be considered as predetermined conditions for unlocking the return door. (Specific conditions when storing goods (when store staff unlock the lock)) 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 if authentication is successful, the corresponding return door (the return door for storing the items to be returned to the user) may be unlocked. Details of this unlocking method will be described later. Alternatively, instead of or in addition to the above unlocking method, for example, similar to unlocking the collection unit door, authentication may be performed based on either or both of the following: information on a card inserted into the card insertion / discharge slot 203 (for example, an administrator card managed by a store employee, etc.) or information entered into the input operation unit 205 (for example, a PIN, etc.), and if authentication is successful, the return door may be unlocked.

[0210] (Specific conditions when removing the product (when the user unlocks the lock)) For example, similar to unlocking the card slot door, authentication may be performed based on either or both of the following: information on the card inserted into the card insertion / discharge slot 203 (e.g., a membership card), information entered into the input operation unit 205 (e.g., a PIN). If authentication is successful, the corresponding return slot door (the return slot door containing the items returned by the user) may be unlocked. Alternatively, authentication may be performed based on information recognized by the code recognition unit 206 (e.g., barcode G11 displayed on the membership card screen, barcode information printed on the membership card), and if authentication is successful, the card slot door may be unlocked. Furthermore, authentication may be performed based on the information recognized by the code recognition unit 206 and the information entered into the input operation unit 205, and if authentication is successful, the card slot door may be unlocked. For even greater security, authentication may be performed based on the information on the card inserted into the card insertion / discharge slot 203, the information entered into the input operation unit 205, and the information recognized by the code recognition unit 206, and if authentication is successful, the card slot door may be unlocked.

[0211] Various methods can be considered for recognizing the removal of an item. For example, the return door can be equipped with a sensor capable of detecting whether it is in its normal state (closed) or not (in other words, a sensor capable of detecting whether it is open or not), and the removal of an item can be recognized based on the detection result of the sensor. After an item is removed, the return door may be returned to its original state (normal state) by a biasing force or the like. Furthermore, if the original state is maintained for a predetermined time (a time during which all removal operations can be considered complete, even if there are multiple removal operations by the same user; for example, 1 minute), the return door may be locked (automatically locked).

[0212] Furthermore, a corresponding light-emitting section may be provided for each return slot 210. For example, in the example shown in Figure 18(B), a light-emitting section 211 is provided above each return slot 210. In addition, a rod or hook may be provided inside the return slot 210 to neatly store the items.

[0213] Although the number of return slots for the common locker 200 shown in Figure 18(B) is 12, the number of return slots for the common locker 200 may be other than 12.

[0214] (Lockers for returns only) The return-only locker 300 includes, for example, a card insertion / extraction slot (not shown), a display unit (not shown), an input operation unit (not shown), a code recognition unit (not shown), an issuance slot (not shown), a storage unit (not shown), a control unit (not shown) that controls the display on the display unit and the locking of the return slot door (described later), etc., and multiple return slots (return sections) 310. In the case of the return-only locker 300 shown in Figure 18(C), the card insertion / extraction slot, display unit, input operation unit, code recognition unit, issuance slot, etc. are located in the area 301a of the upper left 301, but for the sake of the drawing, each of them is omitted from the illustration.

[0215] Furthermore, a corresponding light-emitting section may be provided for each return slot 310. For example, in the example shown in Figure 18(C), a light-emitting section 311 is provided above each return slot 310. In addition, a rod or hook may be provided inside the return slot 310 to neatly store the items.

[0216] Although the number of return slots for the return-only locker 300 shown in Figure 18(C) is 5, the number of return slots for the return-only locker 300 may be other than 5.

[0217] Next, Figures 19 to 43 will be used to explain the locker return process in detail. In the following explanation, unless otherwise specified, the common lockers 200 and the return-only lockers 300 that can be used for locker returns will simply be referred to as "return lockers."

[0218] Figure 19 (and similarly Figures 20 and 26) shows an example of the various types of information stored by cleaning system 1 (and similarly by cleaning system 2).

[0219] (Locker management master file) Figure 19(A) shows an example of a locker management master file stored by the management device 10. The locker management master file is a file that stores information about return lockers (300 dedicated return lockers, 200 common lockers). The locker management master file shown in Figure 19(A) stores information such as the installation location and the number of return slots, associated with the locker number. Note that if the number of return slots for all return lockers in the cleaning system 1 is the same (for example, 12), it is not necessary to manage (store) the number of return slots in the locker management master file.

[0220] The locker number is information used to identify 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, or to install return lockers in locations other than stores. Locations other than stores may include supermarkets, convenience stores, specialty stores (clothing stores, pharmacies, etc.), shops inside (or near) train stations, and indoors or outdoors of apartment buildings, etc. (the same applies to the reception locker 100). The number of return slots is the number of return slots available in the return locker.

[0221] In addition, the locker management master file may also manage 100 reception-only lockers (such as the locker numbers of the 100 number reception-only lockers) in addition to the return lockers (300 return-only lockers, 200 shared lockers).

[0222] 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 by the POS terminal 20 may be a file relating to all returned lockers, similar to the file stored by the management device 10, or, as shown in Figure 19(B), it may be a file relating to the returned lockers associated with the store (the store where the POS terminal 20 is installed).

[0223] (Required number of units definition file) Figure 19(C) shows an example of a required number of slots definition file stored by the management device 10. The required number of slots definition file stores information about the number of return slots required when returning items to a locker. The required number of slots definition file shown in Figure 19(C) stores the required number of slots in association with the number of items to be returned. The number of items to be returned is the number of items (quantity) to be returned. The required number of slots is the number of return slots required when returning items to a locker. According to Figure 19(C), for example, if the number of items to be returned is 1 to 4, the required number of slots is 1, and if it is 5 to 8, the required number of slots is 2. If the capacity of the return slots differs for each type of locker, a required number of slots definition file may be stored for each type of locker.

[0224] The required number of units definition file shown in Figure 19(C) simply determines the required number of units based on the number of returned items and does not take into account the type of returned items. However, the required number of units may be determined by taking into account the type of returned items. For example, instead of the required number of units definition file shown in Figure 19(C), a required number of units definition file as shown in Figure 19(D) and a volume number definition file as shown in Figure 19(E) may be stored.

[0225] The required number definition file shown in Figure 19(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 goods to be delivered. According to Figure 19(D), for example, if the number of return volumes is 1 to 4, the required number of units is 1, and if it is 5 to 8, the required number of units is 2.

[0226] The volume count definition file shown in Figure 19(E) stores the volume count in association with the product type (see Figure 7(A)). According to Figure 19(E), for example, the volume count for product type SY01 (shirts) is 1, and for product type SY04 (coats), the volume count is 4.

[0227] For example, if there are two items to be returned, one a shirt (product type "SY01") and the other a coat (product type "SY04"), according to the required number definition file in Figure 19(C), the number of items to be returned is 2, so the required number of units is 1. On the other hand, according to the required number definition file in Figure 19(D) and the volume definition file in Figure 19(E), the total volume of one shirt and one coat is 5, so the required number of units is 2.

[0228] Alternatively, the POS terminal 20 may store a required number of connections definition file as shown in Figure 19(C) instead of or in addition to the management device 10. Furthermore, the POS terminal 20 may store a required number of connections definition file as shown in Figure 19(D) or a volume number definition file as shown in Figure 19(E) instead of or in addition to the management device 10.

[0229] (Required number of units definition file) Figure 20(A) shows an example of a locker-specific reservation status file stored by the management device 10. The locker-specific reservation status file is a file that stores information regarding the reservation status (reservation status) of locker returns for each return locker. The locker-specific reservation status file shown in Figure 20(A) shows the reservation status file for the return locker with locker number "L01," and stores the reservation category, customer code, tag number, number of volumes used, reservation date, reservation number, etc., associated with the return date and return slot number. Note that in Figure 20(A), for the sake of explanation, the sheets (tables) for each return date are shown separately, 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 hand over goods at the return slot, that is, the volume of goods to be handed over at the return slot. The locker-specific reservation status file shown in Figure 20(B) will be described later.

[0230] In addition, the POS terminal 20 may store a locker-specific reservation status file instead of or in addition to the management device 10. The locker-specific reservation status file stored by the POS terminal 20 may be a file relating to all returned lockers, similar to the file stored by the management device 10, or it may be a file relating to returned lockers associated with the store in question (the store where the POS terminal 20 is installed).

[0231] The locker-specific reservation status file stores not only future information (information on future return dates) but also past information (information on past return dates). In other words, the management device 10 (and the same applies when the POS terminal 20 stores the locker-specific reservation status file) continues to retain past information in the locker-specific reservation status file without deleting it. For example, the management device 10 may continue to retain past information without deleting it for a predetermined period (at least the period referenced when determining the return slot (described later)).

[0232] The future information in the individual locker reservation status file shows the future reservation status of each locker (each return slot). However, since lockers are used based on reservations, the past information in the individual locker reservation status file also shows the past usage status of the lockers. In other words, the management device 10 (or the POS terminal 20 if it stores the individual locker reservation status file), or the storage unit of the management device 10 (such as the storage unit of the POS terminal 20's hard disk 24), manages the past and future usage status of lockers (each return slot).

[0233] Figure 21 is an explanatory diagram illustrating the management of locker usage. Figure 21 shows an example of information stored in the locker-specific reservation status file, presented in a modified format for ease of explanation (to show the number of available return dates). In other words, the management device 10 (and the same applies when the POS terminal 20 stores the locker-specific reservation status file) manages the locker usage status as shown in Figure 21. Note that the information for the return date "201X / 4 / 20" in Figure 21 (the information in the row with the arrow) is based on the information for "201X / 4 / 20" in Figure 20(A), but information on return dates other than "201X / 4 / 20" in Figure 21 is not shown in Figure 20(A).

[0234] (Locker reservation availability dates) Figure 22 is a flowchart illustrating an example of the process for determining the available reservation dates (return dates). The flowchart shown in Figure 22 begins when determining the available reservation dates for locker returns (when executing the process related to locker return reservations, for example, when displaying the locker return date calendar screen (described later)). Note that the flowchart in Figure 22 shows the operation of the device that determines the available reservation dates (for example, the management device 10, the POS terminal 20, etc.).

[0235] Step S400 in Figure 22: Calculate the required number of units. Step S401: Determine whether all items to be returned to the locker are finished. If the product is not finished (step S401; NO), proceed to step S402. If the product is finished (step S401; YES), proceed to step S405. Note that if this flowchart is executed when the product is received, since none of the products are finished, proceed to step S402.

[0236] Step S402: Identify the latest scheduled completion date (the latest scheduled completion date among the scheduled completion dates for each item you wish to return to the locker). Step S403: The latest scheduled completion date is used as the reference date. Then proceed to Step S406. Furthermore, the reference dates for steps S403, S405, and S406 refer to the earliest available reservation date, assuming that locker usage is not taken into consideration (ignored). Step S405: Tomorrow is the reference date. Proceed to Step S406.

[0237] Step S406: Determine whether the number of available slots on each day after the reference date is equal to or greater than the required number of slots. If the number of available slots is equal to or greater than the required number of slots, then reservations are possible. Therefore, the process in Step S406 is to determine whether or not a day is available for reservation. In other words, the process in Step S406 calculates the available days for reservation based on the number of available slots on each day after the reference date and the required number of slots. Step S407: Output the judgment result. For example, the management device 10 (POS terminal 20) may display the judgment result. Alternatively, for example, the management device 10 (POS terminal 20) may print the judgment result. Alternatively, for example, the management device 10 may send information indicating the judgment result to the POS terminal 20 (or user terminal 50) (POS 20 (or user terminal 50) may display the judgment result). Alternatively, for example, the management device 10 (POS terminal 20) may print the judgment result. Alternatively, for example, the POS terminal 20 may send information indicating the judgment result to the user terminal 50 (user terminal 50 may display the judgment result). Then, the flowchart in Figure 22 ends.

[0238] Figure 23 is an explanatory diagram illustrating how to determine available reservation dates. Specifically, Figures 23(A) to 23(C) show examples of how to determine available reservation dates when returning the three items marked "Currently in Storage" in Figure 12 (items in columns G33, G34, and G35) to the locker, using the required number definition file in Figure 19(C) (an example determined based on the number of returned items). Figures 23(D) to 23(F) show examples of how to determine available reservation dates when returning the three items marked "Currently in Storage" in Figure 12 (items in columns G33, G34, and G35) to the locker, using the required number definition file in Figure 19(D) and the volume file in Figure 19(E) (an example determined based on the number of returned volumes). Note that today is assumed to be "201X / 4 / 19".

[0239] (Example calculated based on the number of returned items) The upper part of Figure 23(A) (the base of the arrow) shows information (scheduled completion date) regarding the items to be returned via locker return (the three items labeled "Currently in Storage" in Figure 12) (Figure 7(D)). As shown in the upper part of Figure 23(A), there are 3 items to be returned, so in step S400 of Figure 22, the required number of items is calculated as 1, as shown in the lower part of Figure 23(A) (the tip of the arrow) (see Figure 19(C)).

[0240] Next, the scheduled completion dates for each of the three products are "201X / 4 / 11", "201X / 4 / 13", and "201X / 4 / 16", and today is "201X / 4 / 19", so it is determined that all products are completed (Step S401; YES), and tomorrow's date, "201X / 4 / 19", is used as the reference date (Step S405).

[0241] Next, it is determined whether the number of available slots for each day from "201X / 4 / 19" onward is 1 or more (step S406), and for example, as shown in Figure 23(B), the days for which the number of available slots is 1 or more are output (displayed, etc.) as available reservation days (step S407). In Figure 23(B), the number of available slots for each available reservation day is also output (displayed, etc.). Note that in the process of step S407, as shown in Figure 23(C), the availability of reservations, etc., for each day from the reference date onward may also be output (displayed, etc.).

[0242] (Example calculated based on the number of returned volumes) The upper part of Figure 23(D) (the base of the arrow) shows information (volume count, expected completion date) regarding the items to be returned via locker return (the three items labeled "Currently in Storage" in Figure 12) (Figures 19(E) and 7(D)). As shown in the upper part of Figure 23, the total volume count is 6, so in step S400 of Figure 22, the required number of units is calculated to be 2, as shown in the lower part of Figure 23(D) (the tip of the arrow) (see Figure 19(D)).

[0243] Subsequently, since the scheduled completion dates of the three products are "201X / 4 / 11", "201X / 4 / 13", and "201X / 4 / 16" respectively, and today is "201X / 4 / 19", it is determined that all products have been completed (step S401; YES), and "201X / 4 / 19", which is tomorrow's date, is used as the reference date (step S405).

[0244] Subsequently, it is determined whether there are two or more available days on each day after "201X / 4 / 19", which is the required number of days (step S406). For example, as shown in FIG. 23(E), days with two or more available days, which is the required number of days, are output (displayed, etc.) as reservable days (step S407). In FIG. 23(E), the available days of each reservable day are also output (displayed, etc.). In the process of step S407, as shown in FIG. 23(F), it may be possible to output (display, etc.) reservation availability, etc. for each day after the reference date.

[0245] As described above, FIGS. 23(C) and 23(F) show the reservation availability for each day. Therefore, FIG. 22 is a flowchart showing the operation of identifying reservable days (returnable days), and is also a flowchart showing the operation of determining the reservation availability for each day (or a specific day). That is, the management device 10, the POS terminal 20, etc. are devices for identifying reservable days and are also devices for determining reservation availability.

[0246] Note that the output modes shown in FIG. 23 (FIGS. 23(B), 23(C), 23(E), 23(F)) are examples, and for example, the reservable days may be shown on the locker return scheduled date calendar screen described below.

[0247] (Locker return scheduled date calendar screen) FIG. 24 (similarly for FIG. 25) is an example of a locker return scheduled date calendar screen (locker return reservation screen). The locker return scheduled date calendar screen shown in FIG. 24 is displayed, for example, on the POS terminal 20, the user terminal 50, or the management device 10. When 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), a locker return scheduled date calendar screen (similarly for the locker return reservation confirmation screen described later) may be displayed on the display unit of another device (such as a personal computer) that can communicate (connect) with the management device 10.

[0248] When the selection completion icon G32 is operated on the slip details screen (FIGS. 12 and 14) of the user terminal 50, although not described above, for example, a screen for allowing the user to select whether to wish to return the locker is displayed. When it is selected that the user wishes to return the locker, a locker return scheduled date calendar screen as shown in FIG. 24 may be displayed on the display unit. When a single locker cannot be identified from the store (for example, when two or more return lockers are associated with one store), the return locker may be specified to the user.

[0249] Also, when "locker return reservation" is selected on the menu screen (not shown) of the POS terminal 20, for example, a locker return scheduled date calendar screen as shown in FIG. 24 may be displayed on the display unit 25. The same applies to the management device 10.

[0250] When it is the locker return scheduled date calendar screen displayed by the user terminal 50, it is displayed with information automatically input in the locker information column and the customer information column respectively. However, when it is the locker return scheduled date calendar screen displayed by the POS terminal 20 or the management device 10, information may be input by a store clerk or the like in the locker information column and the customer information column respectively.

[0251] The locker return schedule calendar screen shown in Figure 24 includes fields for current date and time (see symbol A), locker information (see symbol B), customer information (see symbol C), number of items to be returned to the locker (see symbol D), message (see symbol E), required number of return slots (see symbol F), adjustment (see symbol G), and calendar (see symbol H).

[0252] The current date and time field (code A) displays the current date and time. The locker information field (code B) displays the locker number and other information of the return locker whose information is displayed on the locker return date calendar screen. The customer information field (code 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 field (code D) displays the number of items that the user wishes to pick up by returning them to the locker. The required number of return slots field (code F) displays the number of return slots required for the user to return the items to the locker. The adjustment field (code G) displays buttons to increase or decrease (adjust) the required number of return slots and the adjustable range. The calendar field (code H) displays the number of available (reservable) return slots (number of empty return slots) for each day. Each day area in the calendar field is a button.

[0253] The following explains some of the information displayed in Figure 24. In the explanation of Figure 24, it is assumed that the user (customer code "KB9876") selected three items—a shirt (tag number "TG01-1372"), a sweater (tag number "TG01-1374"), and a down jacket (tag number "TG01-1375")—as items to be returned to the locker on the slip details screen (Figure 14). The required number of lockers will be calculated considering the volume.

[0254] In Figure 24, the "L01(AAA)" in the locker information column (symbol B) is displayed based on, for example, the stored item information file (Figure 6), the locker management master file (Figure 19(A)), the store file (Figure 7(B)), etc. The "3" in the locker return item count column (symbol D) refers to the three items mentioned above.

[0255] The "2" in the Required Return Quantity column (symbol F) indicates the number of return quantities based on the number of return volumes. In other words, it is displayed based on the product type file (Figure 7(A)), the required quantity definition file (Figure 19(D)), the volume count definition file (Figure 19(E)), etc. Specifically, the number of volumes for a shirt (product type "SY01") is "1", the number of volumes for a sweater (product type "SY02") is "2", and the number of volumes for a down jacket (product type "SY03") is "3", for a total of "6" volumes (number of return volumes). Since the required number of return quantities corresponding to "6" is "2", "2" is displayed in the Required Return Quantity column.

[0256] The adjustable range "1 to 3" in the adjustment column (code G) is a fixed value pre-set for the case where the required number of return items is "2". Alternatively, it may be a fixed value pre-set for the case where the number of return volumes is "6".

[0257] The "4" for 4 / 20 in the calendar column (symbol H) is displayed based on the number of available lockers, "4," in the locker reservation status file (Figure 20(A)). In the locker return date calendar screen shown in Figure 24, the color (background color) of the buttons for each date differs depending on whether the date is a reservable day (a day from tomorrow onwards (excluding store holidays) where the number of available lockers is greater than or equal to the required number of return lockers) or an unreservable day (a day that is not a reservable day). In Figure 24, reservable days (4 / 20, 4 / 23, 4 / 24, 4 / 27, 4 / 28, ...) are plain (white), and unreservable days (4 / 16~4 / 19, 4 / 21, 4 / 22, 4 / 25, 4 / 26, 4 / 30, ...) are indicated by dots.

[0258] Figure 20(B) shows the contents of the updated locker reservation status file, which is updated after the button "4 / 20" is pressed (touched, etc.) on the locker return date calendar screen in Figure 24. Figure 25 is an example of the locker return date calendar screen displayed after the button "4 / 20" is pressed on the locker return date calendar screen in Figure 24.

[0259] Figure 26 shows the contents of the updated stored item information file, which is updated after the button "4 / 20" is pressed (touched, etc.) on the locker return date calendar screen in Figure 24. Figure 27 is an example of the slip details screen that is displayed after the button "4 / 20" is pressed on the locker return date calendar screen in Figure 24.

[0260] (Determination of return location) If the number of available return slots is greater than the required number of return slots, the system will select the required number of return slots from among the available (reservable) slots. In other words, if there is availability (room to choose from the return slots), the system will decide which return slots to use. For example, in the example shown in Figures 20(A) and 20(B), two return slots (return slot numbers "H11" and "H12") are selected from among the four available return slots (return slot numbers "H11", "H12", "H21", and "H22").

[0261] (How to determine the return slot) One method for determining which return slot to reserve from among the available return slots is to select a slot based on its past usage history (past usage status; specifically, past decision results). Specifically, the slots may be selected in a way that prevents any particular slot from being used too frequently (so that all slots are used evenly). Even use of all slots makes it less likely that deterioration or damage will progress at any particular slot. The past usage history of each return slot can be ascertained, for example, by keeping the locker-specific reservation status file (Figure 20) stored for a certain period of time without immediately deleting it after the return date has passed. In other words, the past usage history of each return slot can be ascertained by referring to the locker-specific reservation status file after the return date has passed (past locker-specific reservation status file).

[0262] Alternatively, or in addition to the above method, the return slots may be determined, for example, based on the relative positions (adjacent relationships) of each return slot. Specifically, when the same user reserves two or more return slots (i.e., the user requires two or more return slots), adjacent return slots may be determined as much as possible so that the user can retrieve their deposited items from adjacent slots. By determining adjacent return slots, users will not have to move to return lockers located far apart.

[0263] Figure 28 shows an example of a file used to determine whether return slots are adjacent. Whether each return slot is adjacent can also be determined by storing, for example, a file showing other return slots adjacent to a given return slot (for example, Figure 28(A)) or a file showing patterns (combinations) of adjacent return slots (for example, Figure 28(B)). These files (the files in Figures 28(A) and 28(B)) are stored, for example, by a device that determines the return slots (for example, a management device 10, a POS terminal 20, etc.).

[0264] Figure 28(A) is a file showing other return slots adjacent to a particular return slot (the return slot of interest). Specifically, Figure 28(A) is a file showing other adjacent return slots for each return slot in the common locker 200 (Figure 18(B)). According to the file shown in Figure 28(A), for example, the return slots adjacent to return slot number "H11" are return slots "H12" and "H21". Also, for example, the return slots adjacent to return slot number "H21" are return slots "H11", return slot number "H22", and return slot number "H31".

[0265] Figure 28(B) shows files illustrating patterns of adjacent return slots. Specifically, the file on the left in Figure 28(B) shows a pattern where two return slots are adjacent in the common locker 200. The file on the right in Figure 28(B) shows a pattern where three return slots are adjacent in the common locker 200. Files illustrating patterns where four or more return slots are adjacent in the common locker 200 are omitted from the illustration.

[0266] According to the file shown in Figure 28(B), for example, the combination of three return slots with return slot numbers "H11", "H21", and "H22" exists in the right-hand file of Figure 28(B) (second from the top), indicating that these three return slots constitute a group of three adjacent return slots. On the other hand, the combination of three return slots with return slot numbers "H11", "H21", and "H32" does not exist in the right-hand file of Figure 28(B), indicating that these three return slots do not constitute a group of three adjacent return slots. However, the combination of two return slots with return slot numbers "H11" and "H21" exists in the left-hand file of Figure 28(B) (second from the top), indicating that these two return slots constitute a group of two adjacent return slots.

[0267] Note that while the examples shown in Figures 28(A) and (B) define adjacent relationships as those arranged vertically or horizontally, adjacent relationships may also be defined as those arranged vertically or diagonally. Specifically, in the file shown in Figure 28(A), for example, three return slots with return slot numbers "H12," "H21," and "H22" may be defined as adjacent to return slot number "H11," and in the file on the left side of Figure 28(B), for example, a combination of two return slots with return slot numbers "H11" and "H22" may be added as a pattern where two are adjacent.

[0268] FIG. 29 is a flowchart showing an example of a method for determining a return port. The processing of the flowchart shown in FIG. 29 starts when a reservation operation (operation of a button for a date in the calendar column (symbol H)) is performed on the locker return scheduled date calendar screen. Note that the flowchart shown in FIG. 29 (similarly for the flowchart shown in FIG. 30) shows the operation of a device (for example, the management device 10, the POS terminal 20, etc.) that determines the return port.

[0269] Step S500 in FIG. 29: Determine whether the number of available return ports (the number of available return ports) is greater than the required number (the required number of return ports). That is, determine whether there is a margin in the number of available ports. If the number of available return ports is not greater than the required number (step S500; NO), proceed to step S501. If the number of available return ports is greater than the required number (step S500; YES), proceed to step S502.

[0270] Step S501: Determine all the return ports for the number of available ports (the required number). That is, since there is no margin in the number of available ports and there is no room to select return ports, reserve all the available return ports. Then, the flowchart in FIG. 29 ends.

[0271] Step S502: Determine whether the required number is two or more. If the required number is one (step S502; NO), proceed to step S503. If the required number is two or more (step S502; YES), proceed to step S504.

[0272] Step S503: Determine the least used one. That is, since only one return port will be determined at most, there is no need to check for the presence of adjacent empty spaces (groups of adjacent empty return ports), and from all the available return ports, reserve the least used one so that each return port is evenly used. Then, the flowchart in FIG. 29 ends.

[0273] When making the decision in step S503, if the decision is based solely on usage, there may be multiple candidates, making it impossible to identify the single return slot that should be selected (reserved). For example, if 8 of the 12 return slots were used the day before yesterday but not the day before yesterday, and the remaining 4 return slots were used the day before yesterday but not the day before yesterday, then there would be 4 candidate return slots to select the required number of 1 return slot (because 4 return slots were used the day before yesterday). Therefore, it would be impossible to identify the required number of 1 return slot from among the 4 candidates based solely on usage.

[0274] In the cases described above, one return slot may be randomly selected from among multiple candidates using a random number generator or the like. Alternatively, one return slot may be selected from among multiple candidates based on a predetermined rule. For example, as a predetermined rule, one return slot with the highest priority may be selected from among multiple candidates according to a predetermined priority order (for example, prioritizing the leftmost column, and within the same column, prioritizing the top row, in the order of return slot numbers "H11" → "H12" → "H21" → "H22" → "H31" → "H32", ..., "H61" → "H62"). Alternatively, as a predetermined rule, one return slot may be selected from among multiple candidates such that the number of adjacent empty slots (described later) after the selection is as large as possible. Alternatively, a combination of these methods may be used for the selection.

[0275] In step S503, since at most one return slot will be determined, it is not necessary to check for the presence of adjacent empty slots, and it was explained that the least used return slot from all available slots is selected (reserved). However, it is also possible to check for the presence of adjacent empty slots and then select one return slot. Specifically, when making the decision in step S503, if there are empty return slots that constitute adjacent slots and empty return slots that do not constitute adjacent slots, one return slot may be selected from among the empty return slots that do not constitute adjacent slots. In other words, empty return slots that constitute adjacent slots may be reserved for other reservations (subsequent reservations).

[0276] Step S504: Determine whether there are adjacent empty slots. In other words, since multiple return slots will be determined, check for the presence of adjacent empty slots. If there are no adjacent empty slots (Step S504; NO), proceed to Step S505. If there are adjacent empty slots (Step S504; YES), proceed to Step S506.

[0277] Step S505: Determine the required number of unused slots. In other words, since there are no adjacent slots, reserve the required number of unused slots from all available slots in order to ensure that each slot is used evenly. Then the flowchart in Figure 29 ends.

[0278] Furthermore, when making the decision in step S505, there may be multiple candidates based on usage, making it impossible to identify the return slot that should be selected (reserved). For example, if the required number is 3, and 8 of the 12 return slots were used the day before yesterday but not the day before yesterday, and the remaining 4 return slots were used the day before yesterday but not the day before yesterday, then there will be 4 candidate return slots to determine the required 3 return slots (because 4 return slots were used the day before yesterday). Therefore, judging solely on usage will not allow for the selection of the required 3 from among the 4 candidates. Also, for example, if the usage situation is the same as above, but the required number is 5, after determining 4 of the required 5 return slots (the 4 return slots used the day before yesterday), there will be 8 candidate return slots to determine the remaining 1 return slot (because 8 return slots were used the day before yesterday). Therefore, judging solely on usage will not allow for the selection of the required 1 from among the 8 candidates.

[0279] In the cases described above, the return slot may be randomly selected from among multiple candidates using random numbers or the like. Alternatively, the return slot may be selected from among multiple candidates based on predetermined rules. For example, the predetermined rules may include a predetermined priority order (for instance, prioritizing the leftmost column, and within the same column, prioritizing the top row, in the order of return slot numbers "H11" → "H12" → "H21" → "H22" → "H31" → "H32", ..., "H61" → "H62").

[0280] Step S506: Determine whether the number of adjacent empty spaces is equal to or greater than the required number. The number of adjacent empty spaces is the number of return slots for empty states that make up an adjacent empty space (a group of return slots for adjacent empty states). If the number of adjacent empty spaces is less than the required number (Step S506; NO), proceed to Step S507. If the number of adjacent empty spaces is equal to or greater than the required number (Step S506; YES), proceed to Step S508. If there are multiple adjacent empty spaces, determine whether the largest number of adjacent empty spaces among the adjacent empty spaces of each adjacent empty space is equal to or greater than the required number.

[0281] Step S507: Prioritize adjacent empty spaces and determine the required number. Then, the flowchart in Figure 29 is completed.

[0282] The following explanation details the process in step S507, divided into two cases: one where there is only one adjacent empty space (an adjacent empty space with a number of adjacent empty spaces less than the required number), and another where there are multiple adjacent empty spaces (an adjacent empty space with a number of adjacent empty spaces less than the required number).

[0283] If there is only one adjacent empty slot (an adjacent empty slot with fewer adjacent empty slots than the required number), for example, for the number of adjacent empty slots out of the required number, all empty return slots constituting that adjacent empty slot may be determined regardless of their usage status, and for the remainder, return slots may be determined from all available return slots (all return slots in empty states that do not constitute an adjacent empty slot) in order of least used status. In the determination of the remaining slots as described above, if there are multiple candidates based on the usage status, a return slot may be randomly selected from among the multiple candidates using a random number generator or the like, similar to the determination in step S505. Alternatively, a return slot may be selected from among multiple candidates based on a predetermined rule.

[0284] If there are multiple adjacent empty slots (adjacent empty slots with fewer adjacent empty slots than the required number), for example, the return slot may be determined by prioritizing the adjacent empty slot with the largest number of adjacent empty slots, regardless of its usage status. For example, if the required number is 4, and there is one adjacent empty slot with 2 adjacent empty slots and one adjacent empty slot with 3 adjacent empty slots, all empty return slots (3 slots) constituting the adjacent empty slot with 3 adjacent empty slots may be determined, and the least used return slot from the empty return slots (2 slots) constituting the adjacent empty slot with 2 adjacent empty slots may be determined. If the usage status of the empty return slots (2 slots) constituting the adjacent empty slot with 2 adjacent empty slots is the same, one return slot may be randomly selected from the two using a random number generator, or one return slot may be selected from the two based on a predetermined rule. The same applies when prioritizing the adjacent empty slot with the smallest number of adjacent empty slots to determine the return slot, as explained below.

[0285] If there are multiple adjacent empty slots (adjacent empty slots with fewer adjacent empty slots than the required number), instead of the above, the return slots may be determined by prioritizing the adjacent empty slots with the smallest number of adjacent empty slots, regardless of their usage status. For example, if the required number is 4, and there is one adjacent empty slot with 2 adjacent empty slots and one adjacent empty slot with 3 adjacent empty slots, all empty return slots (2 slots) constituting the adjacent empty slot with 2 adjacent empty slots may be determined, and then 2 return slots may be determined from the empty return slots (3 slots) constituting the adjacent empty slot with 3 adjacent empty slots, in order of least used.

[0286] Furthermore, when determining the return slot by prioritizing adjacent spaces with a large number of adjacent spaces, or by prioritizing adjacent spaces with a small number of adjacent spaces, if there are multiple adjacent spaces with the same number of adjacent spaces, one of the adjacent spaces may be determined based on usage, random numbers, or predetermined rules, and the return slot may be selected from among the empty states that make up the determined adjacent space.

[0287] Furthermore, if the required number is greater than the sum of the number of adjacent spaces to all adjacent spaces, then for the number of adjacent spaces (the total number of adjacent spaces to all adjacent spaces) of the required number, all return slots in the empty state constituting those adjacent spaces (all adjacent spaces) may be determined, and for the remainder, return slots may be determined from all available return slots (all return slots in empty states that do not constitute adjacent spaces) in order of unused status. In the determination of the remaining slots as described above, if there are multiple candidates based on the usage status, return slots may be randomly selected from among the multiple candidates using random numbers or the like, similar to the determination in step S505. Alternatively, return slots may be selected from among multiple candidates based on a predetermined rule.

[0288] Step S508: Determine the required number of adjacent empty spaces. Then, the flowchart in Figure 29 is completed.

[0289] The following explanation details the process in step S508, divided into two cases: one where there are adjacent spaces with the same number of adjacent spaces as required, and another where there are no adjacent spaces with the same number of adjacent spaces as required.

[0290] If there are adjacent spaces with the same number of adjacent spaces as the required number, all return ports for the empty states constituting the adjacent spaces with the same number of adjacent spaces may be determined. For example, if the required number is 3, and there is one adjacent space with 2 adjacent spaces, one adjacent space with 3 adjacent spaces, and one adjacent space with 4 adjacent spaces, all return ports (3) for the empty states constituting the adjacent space with 3 adjacent spaces may be determined. If there are multiple adjacent spaces with the same number of adjacent spaces as the required number, one adjacent space (with the same number of adjacent spaces as the required number) may be determined based on usage, random numbers, or predetermined rules, and all return ports for the empty states constituting the determined adjacent space may be determined. For example, if the required number is 3, and there is one adjacent space with 2 adjacent spaces, two adjacent spaces with 3 adjacent spaces, and one adjacent space with 4 adjacent spaces, one adjacent space with 3 adjacent spaces may be determined based on usage, random numbers, or predetermined rules, and all return ports (3) for the empty states constituting the determined adjacent space may be determined.

[0291] If there are no adjacent spaces with the same number of adjacent spaces as the required number, the required number of return slots may be selected from the empty return slots that make up the smallest adjacent space with a number of adjacent spaces exceeding the required number, in order of unused slots. For example, if the required number is 3, and there is one adjacent space with 2 adjacent spaces, one adjacent space with 4 adjacent spaces, and one adjacent space with 5 adjacent spaces, then 3 return slots may be selected from the empty return slots (4 slots) that make up the adjacent space with 4 adjacent spaces, in order of unused slots. If there are multiple adjacent spaces with the smallest number of adjacent spaces exceeding the required number, one adjacent space (the adjacent space with the smallest number of adjacent spaces exceeding the required number) may be determined based on usage status, random numbers, or predetermined rules, and the required number of return slots may be selected from the empty return slots that make up the determined adjacent space, in order of unused slots. For example, if the required number is 3, and there is one adjacent empty space with 2 adjacent empty spaces, two adjacent empty spaces with 4 adjacent empty spaces, and one adjacent empty space with 5 adjacent empty spaces, then one adjacent empty space with 4 adjacent empty spaces may be determined based on usage, random numbers, or predetermined rules, and then three unused return slots may be selected from the four empty return slots that make up the determined adjacent empty space.

[0292] Furthermore, when determining the return slots in order of unused status (in the example above, when determining the three unused return slots from among the four empty return slots that make up the four adjacent empty slots), if there are multiple candidates based on usage status, the return slots may be randomly selected from among the multiple candidates using random numbers or the like. Alternatively, the return slots may be selected from among multiple candidates based on predetermined rules.

[0293] As shown in the flowchart in Figure 29, if there is sufficient availability relative to the number of reservations (required number) (step S500 (YES)), for users using multiple return slots (step S502 (YES)), if adjacent slots are available (step S504 (YES)), the adjacent return slot will be reserved preferentially.

[0294] As described above, the flowchart in Figure 29 determines the return slot individually for each reservation (determining the return slot each time a reservation is made), but the method of determining the return slot is not limited to this. For example, the return slots for one or more reservations made within a certain period may be determined collectively (determining the return slots all at once after the end of the period).

[0295] Figure 30 is a flowchart showing another example of a method for determining the return slot. The device that determines the return slot (e.g., management device 10, POS terminal 20, etc.) may perform the process shown in the flowchart of Figure 30 instead of the process shown in the flowchart of Figure 29. The process shown in the flowchart of Figure 30 starts, for example, at a predetermined time (e.g., 11pm the day before the reservation date).

[0296] Step S516 in Figure 30: Determine whether all reservations have been extracted. In other words, in the following steps (steps S518 to S528), a return slot will be determined for each individual reservation, but it is determined whether a return slot has been determined for all reservations. If all reservations have been extracted (step S516; YES), the flowchart in Figure 30 ends. If all reservations have not been extracted (step S516; NO), proceed to step S518.

[0297] Step S518: Extract the one reservation with the largest required number from among the undecided reservations. In other words, control the system to determine the return slots in order from the reservations (users) that will be using the most return slots. If there are multiple reservations with the same required number, for example, they may be extracted in order of reservation (earliest reservation time first).

[0298] After the process in step S518 is completed, the process proceeds to step S520. Note that the processes in steps S520 to S528 in Figure 30 are the same as the processes in steps S500 to S508 in Figure 29, so their explanation is omitted. After the process in any of steps S521, S523, S525, S527, or S528 in Figure 30 is completed, the process returns to step S516. Then, as described above, the flowchart in Figure 30 is completed by determining the return slot for all reservations.

[0299] As shown in the flowchart in Figure 30, since the return slots are determined based on the number of reservations that are needed (step S518), adjacent return slots are more likely to be reserved for users who use multiple return slots.

[0300] Figure 31 is an explanatory diagram illustrating the method for determining the return slot. Figure 31(A) schematically shows all 12 return slots (return slot numbers "H11" to "H62") of the common locker 200 in Figure 18(B). In Figure 31(A), the usage status of each return slot is assumed to be as follows: The six return slots with return slot numbers "H11", "H12", "H21", "H22", "H51", and "H52" were used yesterday. The five return slots with return slot numbers "H31", "H32", "H42", "H61", and "H62" were used two days ago (last used two days ago). The return slot with return slot number "H41" was used three days ago (last used three days ago).

[0301] Figure 31(B) shows how each return slot shown in Figure 31(A) is determined by a method that determines the return slot for each individual reservation based on usage (the determination method shown in the flowchart in Figure 29). Figure 31(C) shows how each return slot shown in Figure 31(A) is determined by a method that determines the return slot for multiple reservations at once based on usage (the determination method shown in the flowchart in Figure 30). In Figure 31(B) (and similarly in Figures 31(C), 32(B), and 32(C)), the return slot number for each return slot is omitted.

[0302] (Method for determining the return location for each reservation based on usage status / Figure 31(B)) In the explanation for Figure 31(B), it is assumed that a total of four requests for return slot reservations were received on the same day in the following order. Case 1: Reservation by user A, where the required number of return items is 1. Case 2: Reservation by user B, where the required number of return items is 1. Case 3: Reservation by user C, where the required number of return items is 3. Case 4: Reservation by user d, where the required number of return items is 5. In other words, with this determination method, the return slot is determined in the order of reservation (reservation by user a → reservation by user b → reservation by user c → reservation by user d).

[0303] When the first reservation (by user a) is made, as shown in the top row of Figure 31(B), the return slot with return slot number "H41" is assigned to user a's reservation. In other words, user a needs 1 slot, and the number of reservations at the time of user a's reservation is 0, meaning there are 12 available slots. Therefore, the number of available slots is greater than the required number (step S500 (YES) in Figure 29), and the required number is 1 (step S502 (NO)), so the least used return slot out of all available slots is reserved (step S503). Among all 12 available return slots (return slot numbers "H11" to "H62"), the least used return slot can be identified as the return slot with return slot number "H41" that was used 3 days ago. Therefore, the return slot with return slot number "H41" is assigned.

[0304] Subsequently, if a second reservation (by user b) is made, as shown in the second row of Figure 31(B), the return slot with return slot number "H61" is assigned to user b's reservation. In other words, user b needs 1 slot, and the number of reservations made at the time of user b's reservation is 1, meaning there are 11 available slots. Therefore, the number of available slots is greater than the required number (step S500 (YES)), and the required number is 1 (step S502 (NO)), so the least used return slot from all available slots will be reserved (step S503). Among all 11 available return slots (11 return slots other than return slot number "H41"), the least used return slots are the 5 return slots used two days ago (return slots with return slot numbers "H31", "H32", "H42", "H61", and "H62"), and it is not possible to identify one slot based solely on usage. Therefore, in this case, the return slot with return slot number "H61" is selected so that the number of adjacent empty slots after the decision is as large as possible (in this case, so that the number of adjacent empty slots after the decision is as large as possible for the return slot used two days ago). While the return slot with return slot number "H62" could also be selected, the upper slot is given priority in this case.

[0305] Subsequently, if a third reservation (by user c) is made, as shown in the third row of Figure 31(B), three return slots with return slot numbers "H31", "H32", and "H42" are assigned to user c's reservation. In other words, user c needs 3 slots, and the number of reservations made by user c at the time of the reservation is 2, meaning there are 10 available slots. Therefore, the number of available slots is greater than the required number (step S500(YES)), the required number is 3 (step S502(YES)), there are adjacent available slots (step S504(YES)), and the number of adjacent available slots is 10, which is greater than or equal to the required number (step S506(YES)). Thus, the required number of slots are selected from among the adjacent available slots (step S508). Here, the required number of return slots are selected from among the adjacent available slots in order of their unused status. Of the 10 return slots that make up the adjacent space (return slot numbers "H11", "H12", "H21", "H22", "H31", "H32", "H42", "H51", "H52", and "H62"), four return slots with return slot numbers "H31", "H32", "H42", and "H62" were used two days ago, and six return slots with return slot numbers "H11", "H12", "H21", "H22", "H51", and "H52" were used yesterday. Therefore, three return slots must be selected from the four return slots used two days ago, and these three cannot be identified solely by their usage status. Accordingly, in this case, three return slots with return slot numbers "H31", "H32", and "H42" are selected so that multiple return slots used by user c are adjacent to each other.

[0306] Subsequently, if a fourth reservation (by user d) is made, as shown in the fourth row of Figure 31(B), five return slots with return slot numbers "H11", "H12", "H21", "H22", and "H62" are determined for user d's reservation. In other words, user d needs 5 slots, and the number of reservations made by user d at the time of reservation is 5, meaning there are 7 available slots. Therefore, the number of available slots is greater than the required number (step S500 (YES)), the required number is 5 (step S502 (YES)), there are adjacent available slots (adjacent available slots with 4 adjacent available slots and adjacent available slots with 3 adjacent available slots) (step S504 (YES)), and the maximum number of adjacent available slots is 4, which is greater than or equal to the required number (step S506 (YES)). Thus, the required number of slots are determined from among the adjacent available slots (step S508). Here, the required number of return slots are determined from among the adjacent available slots in order of their unused status. In other words, of the four return slots that make up the adjacent empty space with 4 adjacent empty spaces (return slot numbers "H11", "H12", "H21", and "H22"), and the three return slots that make up the adjacent empty space with 3 adjacent empty spaces (return slot numbers "H51", "H52", and "H62"), first, we determine the one return slot that was used two days ago (return slot number "H62"). Next, we determine four from the six return slots that were used three days ago (return slot numbers "H11", "H12", "H21", "H22", "H51", and "H52"), but we cannot identify four based on usage alone. Therefore, here, we determine the four return slots with return slot numbers "H11", "H12", "H21", and "H22" so that multiple return slots used by user d are adjacent to each other.

[0307] (Method for determining the return location collectively based on usage status / Figure 31(C)) In the explanation for Figure 31(C), it is assumed that a total of four requests for return slot reservations were received prior to the designated time, in the following order. Case 1: Reservation by user A, where the required number of return items is 1. Case 2: Reservation by user B, where the required number of return items is 1. Case 3: Reservation by user C, where the required number of return items is 3. Case 4: Reservation by user d, where the required number of return items is 5. In other words, in this determination method, the return slots are determined in order of the largest number required (reservation by user d → reservation by user c → reservation by user a → reservation by user b) (step S518 in Figure 30).

[0308] At a predetermined time (for example, 11pm the day before the reservation), first, as shown in the top row of Figure 31(C), five return slots with return slot numbers "H31", "H32", "H41", "H42", and "H51" are determined for user d's reservation. In other words, user d needs 5 slots, and the number of reservations made by user d at the time of reservation is 0, meaning there are 12 available slots. Therefore, the number of available slots is greater than the required number (step S520 (YES) in Figure 30), the required number is 5 (step S522 (YES)), adjacent slots exist (step S524 (YES)), and the number of adjacent slots is 12, which is greater than or equal to the required number (step S526 (YES)). Thus, the required number of slots will be determined from among the adjacent slots (step S528). Here, the return slots are determined by prioritizing adjacent return slots while considering the order in which they are not in use among the adjacent slots. Specifically, the least used return slot (return slot number "H41" used 3 days ago) is determined, followed by the three return slots adjacent to the least used slot (return slot number "H41") (return slot numbers "H31", "H42", and "H51"). Then, of the two return slots located diagonally to the least used slot (return slot number "H41") (return slot numbers "H32" and "H52"), the least used return slot (return slot number "H32") is determined.

[0309] Next, as shown in the second row of Figure 31(C), three return slots with return slot numbers "H52", "H61", and "H62" are determined for user c's reservation. In other words, user c needs 3 slots, and the number of reservations made by user c at the time of reservation is 5, meaning there are 7 available slots. Therefore, there are more available slots than needed (step S520(YES)), the number needed is 3 (step S522(YES)), there are adjacent available slots (adjacent available slots with 4 adjacent available slots and adjacent available slots with 3 adjacent available slots) (step S524(YES)), and the maximum number of adjacent available slots is 4, which is greater than or equal to the number needed (step S526(YES)). Thus, the required number of slots will be determined from among the adjacent available slots (step S528). Since there are three adjacent empty slots (adjacent slots with return slot numbers "H51", "H61", and "H62") that are equal to the required number of adjacent empty slots, the three empty return slots that make up these adjacent empty slots (return slots with return slot numbers "H52", "H61", and "H62") are determined here.

[0310] Next, as shown in the third row of Figure 31(C), return slot number "H11" is assigned to user a's reservation. In other words, user a needs 1 item, and the number of reservations made at the time of user a's reservation is 8, meaning there are 4 available slots. Therefore, the number of available slots is greater than the required number (step S520 (YES)), and the required number is 1 (step S522 (NO)), so the least used return slot out of the 4 available slots is reserved (step S523). All 4 available return slots were used yesterday (return slot numbers "H11", "H12", "H21", and "H22"), so it is not possible to identify one slot based solely on usage. Since it is not possible to identify one slot based solely on usage, the return slot number "H11" is assigned here according to a predetermined priority order (for example, prioritizing the leftmost column, and within the same column, prioritizing the top row).

[0311] Next, as shown in the fourth row of Figure 31(C), return slot number "H12" is assigned to user b's reservation. In other words, user b needs 1 item, and the number of reservations at the time of user b's reservation is 9, meaning there are 3 available slots. Therefore, the number of available slots is greater than the required number (step S520 (YES)), and the required number is 1 (step S522 (NO)). Thus, the least used return slot out of the 3 available slots is reserved (step S523). All 3 available return slots were used yesterday (return slot numbers "H12", "H21", and "H22"), so it is not possible to identify one slot based solely on usage. Since it is not possible to identify one slot based solely on usage, the return slot number "H12" is assigned here according to a predetermined priority order (for example, prioritizing the leftmost column, and within the same column, prioritizing the top row).

[0312] As explained above using Figure 31, we have described, with specific examples, a method for determining the return slot for each individual reservation based on usage (the determination method shown in the flowchart in Figure 29), and a method for determining the return slot for multiple reservations at once based on usage (the determination method shown in the flowchart in Figure 30). However, the method for determining the return slot is not limited to these.

[0313] Figure 32 is an explanatory diagram illustrating another method for determining the return slot. The method for determining the return slot explained in Figure 31 (the flowchart method shown in Figures 29 and 30) is a method of determining the return slot by specifically managing and referring to the usage status of each return slot in order to ensure that each return slot is used evenly. However, the method for determining the return slot explained in Figure 32 is a method of determining the return slot by moving the criterion (criteria determination position) for determining which return slot is located, in order to ensure that each return slot is used evenly.

[0314] Figure 32(A) schematically shows all 12 return slots (return slot numbers "H11" to "H62") of the common locker 200 in Figure 18(B). In Figure 32(A), return slot number "H51" is the current standard determination position.

[0315] Figure 32(B) shows how each return slot shown in Figure 32(A) is determined by a method that determines the return slot for each individual reservation based on the reference determination position. Figure 32(C) shows how each return slot shown in Figure 32(A) is determined by a method that determines the return slot for multiple reservations at once based on the reference determination position.

[0316] (Method for determining the return slot for each reservation based on the reference position / Figure 32(B)) In the explanation for Figure 32(B), it is assumed that there were a total of four requests to reserve return slots in the following order. Case 1: Reservation by user A, where the required number of return items is 1. Case 2: Reservation by user B, where the required number of return items is 1. Case 3: Reservation by user C, where the required number of return items is 3. Case 4: Reservation by user d, where the required number of return items is 5. In other words, with this determination method, the return slot is determined in the order of reservation (reservation by user a → reservation by user b → reservation by user c → reservation by user d).

[0317] When the first reservation (by user a) is made, as shown in the top row of Figure 32(B), the return slot with return slot number "H51" is determined for user a's reservation. In other words, the current reference determination position is the return slot with return slot number "H51", and since user a requires one, one slot is determined from the reference determination position (the return slot with return slot number "H51"), i.e., the return slot with return slot number "H51". Also, as shown in the top row of Figure 32(B), the reference determination position changes from the return slot with return slot number "H51" to the return slot with return slot number "H52". In other words, the reference determination position is moved by the number of determined slots (one slot) according to a predetermined order (in the example in Figure 32(B), return slot numbers "H51" → "H52" → "H61" → "H62" → "H11" → "H12" → ...).

[0318] Furthermore, the reference location for determining the first reservation is determined for each reservation date, regardless of usage status such as which return slots were used the day before, two days before, or three days before. Specifically, the reference location is shifted one by one for each reservation date according to a predetermined order (for example, return slot numbers "H11" → "H12" → "H21" → "H22" → ..., "H61" → "H62" → "H11" → "H12" → "H21" → "H22" → ...). For example, for the first reservation on April 20, 201X, the return slot with return slot number "H51" is used as the reference location; for the first reservation on April 21, 201X, the return slot with return slot number "H52" is used as the reference location; and for the first reservation on April 22, 201X, the return slot with return slot number "H61" is used as the reference location.

[0319] Subsequently, if a second reservation (by user b) is made, as shown in the second row of Figure 32(B), the return slot with return slot number "H52" is determined for user b's reservation. In other words, the current reference determination position is the return slot with return slot number "H52", and user b requires one, so one slot is determined from the reference determination position (the return slot with return slot number "H52"), i.e., the return slot with return slot number "H52". Also, as shown in the second row of Figure 32(B), the reference determination position shifts by the number of decisions (one slot), changing from the return slot with return slot number "H52" to the return slot with return slot number "H61".

[0320] Subsequently, if a third reservation (by user c) is made, as shown in the third row of Figure 32(B), three return slots with return slot numbers "H61", "H11", and "H12" are determined for user c's reservation. In other words, the current reference determination position is return slot number "H61", and user c requires three slots, so three slots (in a predetermined order) are determined from the reference determination position (return slot number "H61"), namely return slots "H62", "H61", and "H11". Also, as shown in the third row of Figure 32(B), the reference determination position shifts by the number of determined slots (three slots), changing from return slot number "H61" to return slot number "H12".

[0321] Subsequently, if a fourth reservation (by user d) is made, as shown in the fourth row of Figure 32(B), five return slots with return slot numbers "H12", "H21", "H22", "H31", and "H32" are determined for user d's reservation. In other words, the current reference determination position is return slot number "H12", and user d requires five slots, so five slots (in a predetermined order) are determined from the reference determination position (return slot number "H12"), namely, five return slots with return slot numbers "H12", "H21", "H22", "H31", and "H32". Also, as shown in the fourth row of Figure 32(B), the reference determination position shifts by the number of determined slots (5 slots), changing from return slot number "H12" to return slot number "H41".

[0322] (Method for determining the return slot collectively based on the reference position / Figure 32(C)) In the explanation for Figure 32(B), it is assumed that a total of four requests for return slot reservations were received prior to the designated time, in the following order. Case 1: Reservation by user A, where the required number of return items is 1. Case 2: Reservation by user B, where the required number of return items is 1. Case 3: Reservation by user C, where the required number of return items is 3. Case 4: Reservation by user d, where the required number of return items is 5. In other words, with this determination method, the return slots are determined in order of the largest number needed (reservation by user d → reservation by user c → reservation by user a → reservation by user b).

[0323] At a predetermined time (for example, 11pm the day before the reservation date), first, based on the reference determination position and the total required number, the return slot determination range (the range shown within the thick frame), which is the range of return slots to be determined this time from among the total of 12 return slots, is determined, as shown in the top row of Figure 32(C). In other words, starting from the return slot with return slot number "H51," which is the reference determination position, the return slot determination range is determined according to a predetermined order (in the example in Figure 32(C), return slot numbers "H51" → "H52" → "H61" → "H62" → "H11" → "H12" → ...), for the total required number (5 required by user d, 3 required by user c, 1 required by user a, and 1 required by user b, totaling 10 return slots) (10 return slots with return slot numbers "H51," "H52," "H61," "H62," "H11," "H12," "H21," "H22," "H31," and "H32").

[0324] Next, as shown in the top row of Figure 32(C), five return slots with return slot numbers "H11", "H12", "H21", "H22", and "H31" are determined for user d's reservation. In other words, since user d needs five items, five adjacent return slots (return slot numbers "H11", "H12", "H21", "H22", and "H31") are determined from the range of return slots. Note that there are other combinations of five adjacent slots besides the above combination (return slot numbers "H11", "H12", "H21", "H22", and "H31") (for example, return slot numbers "H11", "H12", "H21", "H22", and "H32"), but in Figure 32(C), they follow a predetermined order (return slot numbers "H11" → "H12", "H21", "H22", "H31", "H32", ...).

[0325] Next, as shown in the second row of Figure 32(C), three return slots with return slot numbers "H51", "H62", and "H61" are determined for user c's reservation. In other words, since user c needs three slots, three adjacent return slots (return slot numbers "H51", "H52", and "H61") are selected from the five undecided return slots within the range of return slot determination (return slot numbers "H32", "H51", "H52", "H61", and "H62").

[0326] Next, as shown in the third row of Figure 32(C), one return slot with return slot number "H32" is assigned to user a's reservation. In other words, since user a needs one item, the return slot with return slot number "H32" is selected from the undecided return slots within the range of return slots (two return slots with return slot numbers "H32" and "H62").

[0327] Next, as shown in the fourth row of Figure 32(C), one return slot with return slot number "H62" is assigned to user b's reservation. In other words, since user b needs 1, one of the unassigned return slots (one return slot with return slot number "H62") is selected from the range of return slots that has not yet been assigned.

[0328] The methods for determining the return slot have been explained using Figures 31 and 32, and each method has the following characteristics, for example.

[0329] In the method of determining the return slot for each reservation based on usage (Figure 31(B)), the return slot is determined each time a reservation is made based on the actual past usage at the time of reservation. This allows for the reservation of adjacent return slots as much as possible, and ensures that return slots are reserved evenly, reflecting the usage at the time of reservation. Furthermore, the user can be notified of the assigned return slot immediately.

[0330] In the method of determining return slots in bulk based on usage (Figure 31(C)), return slots are determined in order of the largest number required at a predetermined time. This makes it easier to determine adjacent return slots and allows for even reservation of return slots, reflecting the usage status at a predetermined time. Furthermore, the process is relatively simpler compared to the method of determining return slots for each individual reservation based on usage. In other words, the method of determining return slots for each individual reservation based on usage involves determining the return slots on the reservation date, and past usage status changes depending on the reservation date, making the process relatively complex. However, in the method of determining return slots in bulk based on usage, the determination date is constant regardless of the reservation date, making the process relatively simpler.

[0331] In the method of determining the return slot for each reservation based on the reference determination position (Figure 32(B)), the return slot is determined using the reference determination position rather than past usage, making the process relatively simpler compared to the method of determining the return slot for each reservation based on usage.

[0332] In the method of determining the return slot in bulk based on the reference position (Figure 32(C)), the return slot is determined using the reference position rather than past usage, making the process relatively simpler compared to the method of determining the return slot in bulk based on usage.

[0333] It should be noted that the method for determining the return slot based on usage is not limited to the examples described above. That is, while the examples shown in Figure 31, etc., manage the specific usage status on a daily basis, the frequency of use over a predetermined period (for example, a weekly, a 10-day, or a monthly basis) may also be managed. For example, in a method of managing the frequency of use on a weekly basis, the frequency of use for each return slot in the previous week may be calculated, and priority may be given to determining the return slot with the lowest frequency of use in the previous week.

[0334] Furthermore, the method of determining the return slot based on the reference determination position is not limited to the examples described above. That is, in the example shown in Figure 32, the reference determination position is moved by one position for each reservation date, but the reference determination position may also be moved by one position at predetermined intervals (for example, in units of one week, one ten-day, one month, etc.).

[0335] Alternatively, a determination method combining a method based on usage (example in Figure 31) and a method based on a reference determination location (example in Figure 32) may be used. For example, the reference determination location may be determined based on usage. The return slot with the lowest usage frequency in the previous predetermined period (e.g., the past week, the past 10 days, the past month, etc.) may be determined as the reference determination location for the current predetermined period.

[0336] Figure 33 is a flowchart illustrating an example of the operation when a locker is reserved. Specifically, the flowchart in Figure 33 shows an example of the operation when a user reserves a locker return (reserves a return locker) using the user terminal 50. Note that the flowchart in Figure 33 (and similarly the flowchart in Figure 34) shows an example of the operation using the method of determining the return slot for each reservation, as explained in Figures 31(B) and 32(B).

[0337] Step S600 in Figure 33: The user terminal 50 requests the management device 10 to display a reservation screen (for example, the locker return date calendar screen in Figure 25). For example, when a user performs an operation on the user terminal 50 to display a reservation screen (for example, selecting that they wish to return the locker), the user terminal 50 requests the management device 10 to display a reservation screen.

[0338] Step S601: The management device 10 receives a request for the reservation screen (locker return date calendar screen) from the user terminal 50. Step S602: The management device 10 generates a reservation screen (a calendar screen showing the latest locker return date 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 stored item information file, the locker management master file, the locker-specific reservation status file, etc. The management device 10 only needs to generate a reservation screen for the return locker installed at the store where the item (the item to be returned to the locker) was stored. Step S603: The management device 10 transmits the screen information of the reservation screen to the user terminal 50.

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

[0340] Step S608: The management device 10 receives reservation information from the user terminal 50. Step S611: The management device 10 determines the return slot based on the reservation information. For example, the return slot is determined by the method described in Figure 31(B) and Figure 32(B). Step S612: The management device 10 updates various files based on the return slot determination result. In other words, the management device 10 reflects the return slot determination result in S611 in the user's electronic slip file, stored item information file, locker management master file, locker-specific reservation status file, etc. Step S613: The management device 10 updates and generates various screens. For example, the management device 10 updates and generates the reservation confirmation screen based on the result of determining the return slot in step S611 (i.e., by referring to the various files updated in step S612). More specifically, the management device 10 generates a slip details screen that reflects the reservation details as shown in Figure 27, and updates the locker return date calendar screen to reflect the reservation details as shown in Figure 25. The management device 10 may also generate a locker return schedule list screen that reflects the reservation details as shown in Figure 36. In other words, in step S613, screen information to be transmitted in subsequent processing (steps S615 and S625) is generated.

[0341] Step S615: The management device 10 transmits screen information to the user terminal 50. For example, it transmits screen information of a reservation confirmation screen (a slip details screen reflecting the reservation details as shown in Figure 27) to the user terminal 50. Step S616: The user terminal 50 receives screen information for the reservation confirmation screen (a detailed receipt screen reflecting the reservation details) from the management device 10. Step S617: The user terminal 50 displays a reservation confirmation screen (a receipt details screen that reflects the reservation details).

[0342] Step S625: The management device 10 transmits screen information to the POS terminal 20. For example, it transmits screen information of a reservation confirmation screen (such as a locker return date calendar screen reflecting reservation details as shown in Figure 25, or a locker return schedule list screen reflecting reservation details as shown in Figure 36) to the POS terminal 20. Step S626: The POS terminal 20 receives screen information from the management device 10 for the reservation confirmation screen (such as a locker return date calendar screen or a locker return schedule list screen that reflects the reservation details), and stores the received screen information in the storage unit. Then the flowchart in Figure 33 ends.

[0343] Alternatively, instead of performing steps S625 and S626 in Figure 33, the management device 10 may send a message to the POS terminal 20 informing it that a locker has been reserved, and the POS terminal 20, upon receiving the message, may display the message on the currently displayed screen. In other words, when determining the return slot when reserving a locker return at the user terminal 50, only minimal information may be sent to the POS terminal 20.

[0344] Furthermore, the processing in steps S625 and S626 may be performed not when the return slot is determined, as shown in Figure 33, but whenever a store employee makes an operation, regardless of whether the above message information has been sent or received. As an example of when the above message information is sent, the management device 10 sends the above message along with small screen information including an OK (display) button and a Cancel (do not display) button to the POS terminal 20. The POS terminal 20, upon receiving the screen information, displays the small screen overlaid on the currently displayed screen, and when the OK (display) button is touched (corresponding to an operation by a store employee), a reservation confirmation screen (locker return date calendar screen, locker return schedule list screen, etc.) is requested and sent from the management device 10 to the POS terminal 20. The same applies to the flowchart in Figure 35.

[0345] Note that the flowchart in Figure 33 is an example of operation in which the management device 10 determines the return slot. However, in the case where the POS terminal 20 determines the return slot, it is sufficient that the result of the POS terminal 20's determination of the return slot is reflected in the various files stored in the management device 10. For example, the following flow may also be used. The user terminal 50 accesses the POS terminal 20 and displays the reservation screen (locker return date calendar screen). The POS terminal 20, upon receiving a request for the reservation screen from the user terminal 50, may access the management device 10 to receive the latest reservation screen information and transmit (transfer) it to the user terminal 50. Subsequently, the user terminal 50, having accepted the reservation operation on the reservation screen, transmits the reservation information to the POS terminal 20. The POS terminal 20, having received the reservation information from the user terminal 50, determines the return slot and transmits information indicating the result of the return slot determination to the management device 10. The management device 10 updates various files based on the information indicating the result of the return slot determination received from the POS terminal 20. Next, the POS terminal 20 receives screen information from the management device 10 for the reservation confirmation screen (a detailed receipt screen reflecting the reservation details as shown in Figure 27) and transmits (transfers) it to the user terminal 50. The processing in S625 and S626 is the same. As a result, the result of the return slot determination by the POS terminal 20 is reflected in the various files stored in the management device 10. The same applies to Figure 35.

[0346] Figure 34 is a flowchart illustrating another example of actions taken when reserving a locker. Specifically, the flowchart shown in Figure 34 illustrates an example of actions taken when a store employee reserves a locker for the return of goods deposited at the store (reserving a return locker) using the POS terminal 20.

[0347] Step S630 in Figure 34: The POS terminal 20 requests the management device 10 to display a reservation screen (for example, the locker return date calendar screen in Figure 25). For example, when a store employee receives a request from a user to return a locker in person or by telephone, and the employee performs an operation on the POS terminal 20 to display the reservation screen, the POS terminal 20 requests the management device 10 to display the reservation screen.

[0348] Step S631: The management device 10 receives a request for the reservation screen (locker return date calendar screen) from the POS terminal 20. Step S632: The management device 10 generates screen information for the reservation screen (the latest locker return date calendar screen based on the current reservation status), similar to step S602 in Figure 33. Step S633: The management device 10 transmits the screen information of the reservation screen to the POS terminal 20.

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

[0350] Step S638: The management device 10 receives reservation information from the POS terminal 20. Step S641: The management device 10 determines the return slot based on the reservation information. For example, the return slot is determined by the method described in Figure 31(B) and Figure 32(B). Step S642: The management device 10 updates various files based on the return slot determination result, similar to step S612 in Figure 33. Step S643: The management device 10 updates and generates various screens, similar to step S613 in Figure 33.

[0351] Step S645: The management device 10 transmits screen information to the POS terminal 20. For example, it transmits screen information of a reservation screen (such as a locker return date calendar screen reflecting reservation details as shown in Figure 25, or a locker return date list screen reflecting reservation details as shown in Figure 36) to the POS terminal 20. Step S646: The POS terminal 20 receives screen information from the management device 10 for the reservation screen (a locker return date calendar screen that reflects the reservation details, and a locker return schedule list screen that reflects the reservation details as shown in Figure 36). Step S647: The POS terminal 20 displays a reservation screen (a locker return date calendar screen that reflects the reservation details).

[0352] Step S655: The management device 10 transmits screen information to the user terminal 50. For example, it transmits screen information of a reservation confirmation screen (a slip details screen reflecting the reservation details, as shown in Figure 27) to the user terminal 50. Step S656: The user terminal 50 receives screen information for the reservation confirmation screen (a detailed receipt screen reflecting the reservation details) from the management device 10 and stores the received screen information in the storage unit. Then, the flowchart in Figure 34 ends.

[0353] Alternatively, instead of performing steps S655 and S656 in Figure 34, the management device 10 may send a message to the user terminal 50 via email or other means informing it that a locker has been reserved. In other words, when determining the return slot when reserving a locker return at the POS terminal 20, only the minimum necessary information may be sent to the user terminal 50.

[0354] Furthermore, the processing in steps S655 and S656 may be performed not when the return slot is determined, as shown in Figure 34, but whenever a user takes action, regardless of whether the above message information has been sent or received. In other words, for example, the information may be sent from the management device 10 to the user terminal 50 when the slip details screen is requested. The same applies to the flowchart in Figure 35.

[0355] Note that the flowchart in Figure 34 is an example of operation in which the management device 10 determines the return slot. However, in the case where the POS terminal 20 determines the return slot, it is sufficient that the result of the return slot determination by the POS terminal 20 is reflected in the various files stored in the management device 10. For example, the following flow may also be used. The POS terminal 20, having received a reservation operation on the reservation screen (the latest reservation screen received by accessing the management device 10, as in the case of Figure 34), determines the return slot and transmits information indicating the result of the return slot determination to the management device 10. The management device 10 updates various files based on the information indicating the result of the return slot determination received from the POS terminal 20. Subsequently, the POS terminal 20 receives screen information from the management device 10 for the reservation confirmation screen (such as the locker return date calendar screen reflecting the reservation details shown in Figure 25, or the locker return schedule list screen reflecting the reservation details shown in Figure 36). Note that the processing in S655 and S656 is the same. As a result of the POS terminal 20 determining the return slot, the results are reflected in the various files stored in the management device 10. The same applies to Figure 35.

[0356] Figure 35 is a flowchart illustrating another example of operations when reserving a locker. Specifically, the flowchart in Figure 35 shows an example of operations using the method of determining the return slot in bulk, as explained in Figures 31(C) and 32(C), when a user reserves a locker return at the user terminal 50, and when a store employee reserves a locker return at the POS terminal 20. In other words, while the flowchart in Figure 33 was used to explain an example of operations when reserving a locker return at the user terminal 50, and the flowchart in Figure 34 was used to explain an example of operations when reserving a locker return at the POS terminal 20, as an example of operations when determining the return slot in bulk, the flowchart in Figure 35 will be used to explain both the example of operations when reserving a locker return at the user terminal 50 and the example of operations when reserving a locker return at the POS terminal 20, as an example of operations when determining the return slot in bulk. Note that the flowchart in Figure 35 is a replacement of a part (dashed line C) of the flowcharts in Figures 33 and 34.

[0357] Step S707 in Figure 35: When a reservation operation by a user is received, the user terminal 50 transmits the reservation information (reservation date, required quantity, etc.) to the management device 10. Step S708: The management device 10 receives reservation information from the user terminal 50 and stores the received reservation information in the storage unit. The management device 10 does not determine the return slot at this time, but updates (subtracts) the number of available return slots based on the reservation information. Step S709: The management device 10 sends reservation confirmation information to the user terminal 50 to confirm that the reservation has been accepted. Step S710: The user terminal 50 receives reservation confirmation information from the management device 10 and stores the received reservation confirmation information in its storage unit. The user terminal 50 may also display the reservation confirmation information.

[0358] Step S737: When a store employee makes a reservation, the POS terminal 20 transmits the reservation information (reservation date, required quantity, etc.) to the management device 10. Step S738: The management device 10 receives reservation information from the POS terminal 20 and stores the received reservation information in the storage unit. The management device 10 does not determine the return slot at this time, but updates (subtracts) the number of available return slots based on the reservation information. Step S739: The management device 10 sends reservation confirmation information to the POS terminal 20 to confirm that the reservation has been accepted. Step S740: The POS terminal 20 receives reservation confirmation information from the management device 10 and stores the received reservation confirmation information in its storage unit. The POS terminal 20 may also display the reservation confirmation information.

[0359] Step S751: If the user terminal 50 has not yet reached the predetermined time, it terminates the process. If it has reached the predetermined time, it proceeds to step S766 in conjunction with the execution of step S765. Step S752: The POS terminal 20 terminates processing if the predetermined time has not yet arrived, and proceeds to step S776 in conjunction with the execution of step S775 if the predetermined time has arrived. Step S753: The control device 10 terminates the process if the predetermined time has not yet arrived, and proceeds to step S761 if the predetermined time has arrived.

[0360] Step S761: The management device 10 determines the return slot based on the reservation information stored in steps S708 and S738. For example, the return slot is determined by the method described in Figures 31(C) and 32(C). Step S762: The management device 10 updates various files based on the return slot determination result, similar to step S612 in Figure 33. Step S763: The management device 10 updates and generates various screens, similar to step S613 in Figure 33.

[0361] Step S765: The management device 10 transmits screen information to the user terminal 50. For example, it transmits screen information of a reservation confirmation screen (a slip details screen reflecting the reservation details as shown in Figure 27) to the user terminal 50. Step S766: The user terminal 50 receives screen information of the reservation confirmation screen (a detailed receipt screen reflecting the reservation details) from the management device 10 and stores the received screen information in the storage unit.

[0362] Step S775: The management device 10 transmits screen information to the POS terminal 20. For example, it transmits screen information of a reservation confirmation screen (such as a locker return date calendar screen reflecting reservation details as shown in Figure 25, or a locker return schedule list screen reflecting reservation details as shown in Figure 36) to the POS terminal 20. Step S776: The POS terminal 20 receives screen information from the management device 10 for the reservation confirmation screen (such as a locker return date calendar screen or a locker return schedule list screen that reflects the reservation details), and stores the received screen information in the storage unit. Then the flowchart in Figure 35 ends.

[0363] Alternatively, instead of performing steps S765 and S766 in Figure 35, the management device 10 may send a message to the user terminal 50 via email or other means informing them that a locker has been reserved. In other words, when the return slots are determined in bulk, only the minimum necessary information may be sent to the user terminal 50. Similarly, instead of performing steps S775 and S776 in Figure 35, the management device 10 may send a message to the POS terminal 20 informing them that a locker has been reserved. In other words, when the return slots are determined in bulk, only the minimum necessary information may be sent to the user terminal 50.

[0364] (Notifying users of the return slot) The return slot determined by the device that determines the return slot (e.g., management device 10, POS terminal 20, etc.) is notified to the user at the latest by the time the user actually retrieves the product from the return slot. In other words, the user only needs to be notified of which return slot to use to retrieve their deposited product at some point during the period between the return slot determination and the product retrieval.

[0365] For example, the slip details screen shown in Figure 27 displays the reserved date (locker reservation date) as the reservation details for locker return, but it may also display the reserved return slot in addition to the reserved date. In other words, the result of determining the return slot (the processing result of steps S611 in Figure 33, S641 in Figure 34, and S761 in Figure 35) may be notified to each individual user. Alternatively, the result of determining the return slot may be notified on another screen, either in lieu of or in addition to the slip details screen. For example, on the locker return reservation confirmation screen (Figure 36) displayed by the user terminal 50, the reserved return slot (the return slot to be used) may be displayed in lieu of or in addition to the number of return slots.

[0366] A device (management device 10, POS terminal 20) that determines a user's return slot (a return slot where the user's deposited items are placed) may immediately transmit the determination result (the return slot where the user's deposited items are placed) to the user's POS terminal 20 after the determination (at the timing of the return slot determination). Therefore, in the case of determining the return slot for each individual reservation (as shown in Figures 29 and 31(B)), the return slot determination result (information indicating the return slot) is transmitted to the POS terminal 20 immediately after each reservation. Alternatively, in the case of determining the return slots in bulk (as shown in Figures 30 and 31(C)), the return slot determination result (information indicating the return slot) is transmitted to the POS terminal 20 immediately after the bulk return slot determination.

[0367] Furthermore, the device that determines a user's return slot may transmit the determination result to the user's POS terminal 20 at a time different from the timing of the return slot determination. For example, the device that determines the return slot (management device 10, POS terminal 20) may transmit the determination result to the user's POS terminal 20 at a predetermined time (for example, 8:00 a.m. on the day of return).

[0368] Furthermore, the device that determined the return slot may transmit the determination result to the user's POS terminal 20 in response to a request from the user terminal 50 (a request for the determination result). The user terminal 50 may, for example, transmit a request for the determination result to the device that determined the return slot based on an operation to confirm the return slot.

[0369] Furthermore, the device that determined the return slot may transmit the determination result to the user's POS terminal 20 at a different timing from the timing of the return slot determination, in response to a request from the return locker (a request for the determination result). The return locker may transmit a request for the determination result to the device that determined the return slot based on user operations (such as inserting a membership card into the card insertion / discharge slot, entering a PIN or the like in the input operation unit, or recognizing a barcode in the code recognition unit). In other words, the user may not be notified of the reserved return slot until the return locker is actually operated, and the user may be made aware of the reserved return slot when the return locker is actually operated.

[0370] Alternatively, instead of or in addition to the POS terminal 20, the return locker may inform the user of the result of determining the return slot (the return slot containing the user's deposited items). For example, the common locker 200 may display information indicating the corresponding return slot 210 (the return slot 210 containing the user's deposited items) on the display unit 204 based on user operations (such as inserting a membership card into the card insertion / discharge slot 203, entering a PIN or the like in the input operation unit 205, or recognizing a barcode by the code recognition unit 206). Alternatively, each individual return slot 210 may be provided with a light-emitting unit (not shown), and the common locker 200 may illuminate (light up, blink, etc.) the light-emitting unit corresponding to the corresponding return slot based on user operations. Furthermore, although it is the simplest configuration, the common locker 200 may open the return slot door of the corresponding return slot 210 (opening it wide enough to indicate that it is the correct return slot) based on user operations. The timing at which the return locker obtains the return slot determination result may be before or after any user operation. In other words, the device that determined the return slot may send the determination result to the return locker without a request from the return locker (for example, immediately after determining the return slot or at a predetermined time), or it may send the determination result to the return locker based on a request from the return locker. In the latter case, the return locker will send a request for the determination result to the device that determined the return slot based on user operation.

[0371] (Locker return schedule screen) Figure 36 shows an example of a locker return reservation confirmation screen. The cleaning system 1 can display various information related to the management of locker returns. For example, the POS terminal 20, user terminal 50, management device 10, and factory terminal 40 may display a locker return reservation confirmation screen (sometimes called a locker return schedule list screen) as shown in Figure 36.

[0372] For example, if "Locker Return Confirmation" is selected on the menu screen (not shown), the POS terminal 20 may display a locker return reservation confirmation screen, as shown in Figure 36, on the display unit 25. The same applies to other devices.

[0373] The locker return reservation confirmation screen shown in Figure 36 includes fields for current date and time (see symbol A), condition setting area (see symbol B), and result display area (see symbol C).

[0374] The condition setting area (code B) is the area for setting (extracting) the targets for checking, such as the locker return reservation status. The condition setting area has a return date setting field (see code B1) and a customer setting field (see code B2). The return date setting field (code B1) has selection buttons for entering the return date (range selection button, previous day button, today button, next day button), and a return date range input field for entering the range of the return date when the range selection button is selected. Note that when the previous day, today, or next day button is selected, the return date range input field will be automatically populated with a range according to the type of button selected. Note that, as can be seen from the presence of the previous day button, past dates can also be set. The customer setting area (code B2) has a return date range input field for entering the range of the user's customer code, a phone number input field for entering the user's phone number, and a phone number input field for entering the user's name.

[0375] The results display area (code C) is the area that displays the extraction results based on the conditions set in the condition setting area. Specifically, the results display area exemplified in Figure 36 displays the return date, acceptance date, slip number, name, telephone number, number of items, number of return slips used, and reissue based on various information.

[0376] For example, the return date "201X / 4 / 20" in the top piece of information (the row indicated by the arrow) is displayed based on the return date "201X / 4 / 20" in the locker reservation status file in Figure 20(B). It may also be displayed based on the delivery date "4 / 20" in the stored item information file in Figure 26. The acceptance date "201X / 4 / 19" is displayed based on the reservation date "4 / 19" in the locker reservation status file in Figure 20(B). It may also be displayed based on the update date and time "4 / 19 18:27" in the stored item information file in Figure 26. The slip number "DN01-5422" is displayed based on the tag number "TG01-1372" etc. in the locker reservation status file in Figure 20(B) and the stored item number "DN01-5422-01" etc. in the stored item information file in Figure 26. The first nine digits of the item number "DN01-5422-01", "DN01-5422", represent the slip number. The customer code "KB9876" is displayed based on the customer code "KB9876" in the locker reservation status file shown in Figure 20(B). The name "...(omitted)" and telephone number "...(omitted)" are displayed based on the customer master file shown in Figure 3(A), etc.

[0377] The item count "3" is displayed based on the number of corresponding items (tag numbers "TG01-1372", "TG01-1373", "TG01-1375") in the consigned item information file shown in Figure 26. More specifically, it is displayed based on the number (specifically 3) of items (tag numbers "TG01-1372", "TG01-1373", "TG01-1375") corresponding to the aforementioned slip number "DN01-5422" in the consigned item information file shown in Figure 26, for example, items (tag numbers "TG01-1372", "TG01-1373", "TG01-1375") with a scheduled delivery date of "4 / 20". Alternatively, it may be displayed based on the number (specifically 3) of items with a scheduled delivery date of "4 / 20" and the same reservation number (specifically 12345). The "2" return slots used are displayed based on the number of return slots (return slot numbers "H11" and "H12") used to return the corresponding items (tag numbers "TG01-1372", "TG01-1373", and "TG01-1375") in the consigned item information file shown in Figure 26 (specifically, 2). The "*" for reissue indicates that a reissue (multiple printouts) has been performed.

[0378] Furthermore, the POS terminal 20 displays (extracts) information related to the store in question on the locker return reservation confirmation screen. In other words, the information that a store's POS terminal 20 displays on the locker return reservation confirmation screen is limited to reservation information for return lockers under the management of that store (for example, return lockers installed in front of the store).

[0379] Alternatively, the POS terminal 20 may display information related to other stores. For example, the locker return reservation confirmation screen may have a store setting field, and the POS terminal 20 may display information related to the store with the store code entered in the store setting field. Alternatively, for example, the locker return reservation confirmation screen may have an "All Stores" button, and when the "All Stores" button is pressed, the POS terminal 20 may display information related to all stores without being limited to a specific store.

[0380] Furthermore, the user terminal 50 displays (extracts) information related to the user on the locker return reservation confirmation screen. In other words, the information displayed on the locker return reservation confirmation screen by a user's terminal 50 is limited to reservation information related to that user.

[0381] The factory terminal 40 (and the management device 10) displays information related to the specified store on the locker return reservation confirmation screen. For example, the locker return reservation confirmation screen may have a store setting field, and the factory terminal 40 may display information related to the store with the store code entered in the store setting field. Alternatively, for example, the locker return reservation confirmation screen may have an "All Stores" button, and when the "All Stores" button is pressed, the factory terminal 40 may display information related to all stores without being limited to a specific store.

[0382] Figures 37 and 38 show examples of printed and issued media. The POS terminal 20 prints and issues various slips when goods are received. Figures 37(A) and 37(B) are receipt slips (customer copies) issued by the store's POS terminal 20 when goods are received. If the user's instructions regarding the method of handing over the finished goods are for in-store handover (corresponding to handover category "1") or undecided (corresponding to handover category "0"), the POS terminal 20 may print and issue a receipt slip like the one shown in Figure 37(A). Also, if the user's instructions regarding the method of handing over the finished goods are for handover via locker (corresponding to handover category "3"), the POS terminal 20 may print and issue a receipt slip like the one shown in Figure 37(B).

[0383] The receipts shown in Figures 37(A) and 37(B) are receipts related to the slip number "DN01-5422" shown in Figure 6, etc. According to Figure 6, the number of items held for slip number "DN01-5422" is 4 ("TG01-1372" to "TG01-1375"), but for the sake of explanation, the above number is assumed to be 3 ("TG01-1372", "TG01-1374", "TG01-1375"). The same applies to Figure 38.

[0384] In the case of in-store pickup, as shown in Figure 37(A), the date on which all (3) of the deposited items will be available for pickup is printed as the completion date. In contrast, in the case of pickup via return locker, as shown in Figure 37(B), the date on which the locker return is reserved is printed as the scheduled locker return date. Note that the locker return reservation can be made before issuing the deposit slip. For example, in the example shown in Figure 9, the POS terminal 20 may be configured to accept the locker return reservation at any point between steps S17 and S21 and before issuing the deposit slip.

[0385] The printed and issued receipt slip is given to the user. For example, if the customer is present in person (for example, in the case of regular store deposit (deposit category "1")), the receipt is given to the user immediately after issuance. If the customer is not present in person (for example, in the case of locker deposit (deposit category "4")), the receipt is given to the user upon return (in the case of locker return, it is placed in the return slot along with the deposited items). The POS terminal 20 may print and issue the receipt slips shown in Figures 37(A) and 37(B) for some users who do not use the user terminal 50, and may normally print and issue a simpler receipt slip than those shown in Figures 37(A) and 37(B) for users who use the user terminal 50.

[0386] Figure 38 shows the factory copy issued by the store's POS terminal 20 when goods are received. If the user's instructions regarding the method of handing over the finished goods are to hand them over by locker (corresponding to handover category "3"), the POS terminal 20 may print and issue a factory copy like the one shown in Figure 38.

[0387] The printed and issued factory copy is sent to the factory along with the consigned goods, and after completion, it is returned from the factory to the store along with the consigned goods. Alternatively, the POS terminal 20 may transmit the information necessary to print the factory copy to the factory terminal 40 via the management device 10 (or directly without going through it), and the factory terminal 40 may print and issue the factory copy based on the information transmitted by the POS terminal 20.

[0388] The factory copy has a readable code (QR code, barcode, etc.) printed on it. The QR code etc. printed on the factory copy can be used for inspection and locker return. Note that the information that is coded and printed will vary depending on whether or not the locker is returned, the timing of the reservation, the timing of the return location, etc.

[0389] For example, if a user requests locker return when depositing goods, and reserves a return date and determines a return location before the factory receipt is issued, the POS terminal 20 may print a QR code that codes the customer code, the return location number of the determined return location, etc. Alternatively, the POS terminal 20 may print a QR code that codes the slip number, tag number, etc. (for example, a QR code that codes the customer code, reservation date, tag number, and return location number) in place of or in addition to the customer code.

[0390] Furthermore, if a user requests locker return at the time of product deposit and reserves a return date but does not decide on a return slot before the factory receipt is issued, the POS terminal 20 may print a QR code or the like that codes the customer code, the required number of return slots, etc. In addition, the POS terminal 20 may print a QR code that codes the slip number, tag number, etc. (for example, a QR code that codes the customer code, reservation date, tag number, and required number of return slots) instead of or in addition to the customer code.

[0391] Furthermore, if the user does not wish to return the locker before the factory receipt is issued, the POS terminal 20 may print a QR code or the like that which encodes the customer code. In addition, the POS terminal 20 may print a QR code or the like that which encodes the slip number, tag number, etc. (for example, a QR code that encodes the customer code and tag number) instead of or in addition to the customer code.

[0392] In addition, the POS terminal 20 may print and issue a store copy (not shown) for store storage, in addition to the customer copy given to the user and the factory copy sent to the factory when the goods are received.

[0393] In the above explanation, the management device 10 and the POS terminal 20 were described as determining the return slot, but the return locker may also determine the return slot. Furthermore, the device that identifies the available reservation dates (the device that determines whether a reservation is possible) and the device that determines the return slot do not necessarily have to be the same. Therefore, as an example, various configurations such as (a) to (f) below can be considered. (a) The management device 10 identifies the available reservation dates and determines the return location. (b) The POS terminal 20 identifies the available reservation dates and determines the return location. (c) The management device 10 identifies the available reservation dates, and the POS terminal 20 determines the return slot. (d) The management device 10 identifies the available reservation dates, and the return locker determines the return slot. (e)POS terminal 20 identifies the available reservation dates, and the return locker determines the return slot. (f) The return locker will specify the available reservation dates and determine the return location.

[0394] In (a) to (f) above, the return location may be determined at the time the available reservation date is specified, or at a different time than when the available reservation date is specified. In other words, the specific return location may be determined at the same time as the date for locker return is reserved, or only the date for locker return may be reserved and the specific return location may be determined separately.

[0395] Figures 39 to 41 show examples of screens displayed on the display unit of the return locker. Note that the screens in Figures 39 to 41 are examples of screens displayed on the display unit of the return-only locker 300 shown in Figure 18(C). Furthermore, the return slot numbers (door numbers) of the five return slots of the return-only locker 300 are assumed to be "01" to "05".

[0396] Figure 39(A) is the standby screen (initial screen). The standby screen in Figure 39(A) displays a message to the operator (user, store clerk, etc.) prompting them to touch the screen. If the operator touches the screen while the standby screen in Figure 39(A) is displayed, the screen transitions to the screen in Figure 39(B).

[0397] Figure 39(B) is the card reading screen that transitions from the standby screen shown in Figure 39(A). The card reading screen in Figure 39(B) displays messages to the user prompting them to read their membership card or enter their password. If the membership card is read by inserting it into the card insertion / exit slot or if the password button is touched and a password input screen (not shown) is displayed after the touch, the screen transitions to Figure 39(C). Alternatively, the screen may be transitioned to Figure 39(C) by other means (for example, by reading barcode G11 displayed on the membership card screen).

[0398] Furthermore, if a store employee performs a predetermined operation while the card reading screen shown in Figure 39(B) is displayed, the system will transition to the employee initial screen (not shown). For example, if an employee barcode printed on the medium (for example, an employee barcode pre-registered to display the employee initial screen) is recognized and read by the code recognition unit, the system will transition to the employee initial screen. The system may also transition to the employee initial screen by other means (for example, by entering an employee password or inserting an employee card into the card insertion / exit slot). Figures 40(A) and 41(B) are screens that the system transitions to from the employee initial screen.

[0399] Figure 39(C) is a notification screen that is accessed from the card reading screen in Figure 39(B) (specifically, when a membership card is read or a password is entered). The notification screen in Figure 39(C) provides notification information to the user (the user identified based on the membership card and password) including the return slot number of the return slot where the user's deposited items are stored (in the example in Figure 39(C), the door numbers "01", "02", and "03").

[0400] For example, the return locker may store the return slot determination result (the return slot number determined for each user) in its memory unit and notify the return slot number as described above by referring to the memory unit. If another device (management device 10, POS terminal 20, etc.) determines the return slot, the return locker may obtain the determination result and store it in its memory unit. The return locker may also notify the return slot number as described above by querying the other device (management device 10, POS terminal 20, etc.) for the return slot determination result (the return slot number determined for the user).

[0401] Furthermore, the return locker may display the customer ID and the number of returned items in addition to the return locker number on the notification screen shown in Figure 39(C).

[0402] The return locker displays a notification screen on its display unit, unlocks the return door of the corresponding return slot (the return slot where the user's deposited items are stored), and flashes the corresponding light (lamp) for the unlocked return slot. The user completes the locker return process by opening the return doors of all the notified return slots (all unlocked return slots), retrieving the deposited items, and closing the return doors, and the screen transitions to Figure 39(D). The return locker locks the closed return doors and turns off the light corresponding to the locked return slot.

[0403] Furthermore, a return locker may determine that a deposited item has been removed by opening or closing the return door, or by installing an optical sensor (camera, photosensor, etc.) inside the return slot. Alternatively, instead of or in addition to an optical sensor, a scale may be used to determine that a deposited item has been removed. Similarly, a deposit may be determined to have been retrieved when it is collected, or to have been stored when it is put away.

[0404] Figure 39(D) is the completion screen that is accessed from the notification screen in Figure 39(C). After a predetermined time (for example, 10 seconds) has elapsed since the start of display of the completion screen in Figure 39(D), the system transitions back to the standby screen in Figure 39(A).

[0405] Furthermore, special points may be awarded to users who return their items to the locker, and the return locker may display the special points awarded for this locker return on the completion screen shown in Figure 39(D). In addition, the system may decide whether or not to award points, or the number of points awarded may differ, depending on whether or not the items have been returned to the locker a predetermined number of times consecutively (i.e., whether or not they were not collected). In other words, users who always come to pick up their stored items on the return date may be given greater rewards.

[0406] Figure 40(A) shows the initial storage screen, which is accessed from the initial screen for store staff (not shown). For example, the initial screen for store staff has various buttons such as a button for storing returned items, a button for retrieving returned items, and a back button. When the button for storing returned items is touched, the system transitions to the initial storage screen. The initial storage screen in Figure 40(A) has buttons for checking available doors and a back button. In addition, the initial storage screen in Figure 40(A) displays a message for store staff prompting them to scan the QR code printed on the factory copy. By touching the button for checking available doors, the current availability status of the return slots can be checked. For example, a schematic image of a return locker, such as the one shown in Figure 31(A) (specifically, an image where each of the five return slots is color-coded according to whether it is empty or stored), may be displayed. Furthermore, in the initial storage screen of Figure 40(A), in order to efficiently determine the return slot (see step S518 in Figure 30), a message recommending that the factory receipts be scanned in order from the one with the most return slots may be displayed (for example, "Please scan the factory receipts in order from the one with the most return slots."). If the QR code printed on the factory receipt is recognized and read by the code recognition unit while the initial storage screen of Figure 40(A) is displayed, the screen will transition to the screen of Figure 40(B).

[0407] Furthermore, the return locker may perform a date check. For example, it may compare the date information contained in the scanned QR code with the current date to determine if they match. If the date check fails (does not match), the return locker may display a message indicating that they do not match (that it is not the original return date). Alternatively, the return locker may display the original return date along with the message indicating that they do not match. The card reading screen in Figure 39(B) above may also perform a date check. For example, it may compare the return date of a user identified by reading a membership card with the current date to determine if they match.

[0408] Figure 40(B) shows the storage instruction screen, which is accessed from the initial storage screen in Figure 40(A). On the storage instruction screen in Figure 40(B), the store staff are notified of the return slot number (in the example in Figure 40(B), door numbers "01" and "02") for the return slot where the customer's (identified based on the QR code) deposited items will be stored. Note that the storage instruction screen in Figure 40(B) also has a back button.

[0409] The following explains the relationship between the information obtainable from the QR code and the notification of the return slot number. (If the return slot number can be obtained from the QR code) The return locker may also announce the return slot number obtained from the QR code (the return slot number of the return slot determined to store the user's deposited items). In other words, since the return slot has been determined and the determination result has been converted into a QR code, the return locker only needs to announce the return slot number obtained from the QR code.

[0410] (If the number of returned items can be obtained from the QR code) The return locker may determine the return slot using the number of return slots obtained from the QR code (the number of return slots required to store the user's deposited items) and notify the user of the return slot number of the determined slot. In other words, although a reservation has been made based on the required number of return slots, the specific return slot has not been determined, so the return slot may be determined in the same way as the management device 10, and the user may notify the user of the return slot number of the determined slot.

[0411] (If customer ID can be obtained from the QR code) The return locker may transmit the customer ID obtained from the QR code to the device that determined the return slot (management device 10, POS terminal 20, etc.), thereby obtaining the return slot number corresponding to the customer ID (the return slot number of the return slot determined to store the user's deposited items) and notifying the device of the obtained return slot number. Alternatively, the management device 10, etc., may, after obtaining the customer ID from the return locker, determine the return slot to store the user's deposited items and transmit (notify) the determination result to the return locker.

[0412] The return locker displays a storage instruction screen on its display unit, unlocks the door of the corresponding return slot (the slot where the user's deposited items are stored), and flashes the corresponding indicator light for the unlocked return slot. The store employee opens the doors of all the indicated return slots (all unlocked return slots), stores the deposited items, and closes the return slot doors to complete the storage process for each slot. The return locker then locks the closed return slot doors and turns off the indicator light for the locked return slot.

[0413] Figure 41(A) shows the initial collection screen, which is accessed from the initial screen for store staff (not shown). For example, the initial screen for store staff has various buttons such as a button to store returned items, a button to collect returned items, and a back button. When the button to collect returned items is touched, the system transitions to the initial collection screen. The initial collection screen in Figure 41(A) has an OK button to start the collection process and a back button. Also, the initial collection screen in Figure 41(A) displays a message for the store staff prompting them to touch the OK button. When the OK button is touched, the system transitions to the screen shown in Figure 41(B).

[0414] Figure 41(B) shows the collection instruction screen, which is accessed from the initial collection screen in Figure 41(A). The collection instruction screen in Figure 41(B) displays all return slot numbers (in the example in Figure 41(B), door numbers "01" to "05") as information to inform the store staff. The collection instruction screen in Figure 41(B) also includes a back button and other buttons.

[0415] The return locker displays a collection instruction screen on its display unit and unlocks all return door slots. The store employee opens the return door for all the indicated return slots (all unlocked return slots), collects any items that have not yet been returned to the locker, and closes the return door to complete the collection process. The return locker then locks the closed return door. The return locker may also flash the indicator light corresponding to the unlocked return slot and turn off the indicator light corresponding to the locked return slot.

[0416] Furthermore, the return lockers may use factory records (or lists of factory records, etc.) to identify the items (users) that were not received.

[0417] The above explanation uses Figures 39 to 41 to describe examples of screens displayed on the locker return unit. The operating mode when displaying screens based on predetermined operations by store staff (the initial screen for store staff (not shown), and the screens shown in Figures 40 and 41) is sometimes referred to as the store staff mode (or store staff mode). In contrast to the store staff mode, the operating mode when displaying screens other than those based on predetermined operations by store staff (the screen shown in Figure 39) is sometimes referred to as the user mode (or user mode). Furthermore, since the transition to the initial screen for store staff (not shown) is made via the screens shown in Figures 39(A) and 39(B) (i.e., both users and store staff operate the screens shown in Figures 39(A) and 39(B)), the term "user mode" may be used specifically when displaying the screens shown in Figures 39(C) and 39(D), excluding the screens shown in Figures 39(A) and 39(B).

[0418] Figures 42 and 43 are flowcharts illustrating an example of the operation of the return locker. The flowchart in Figure 43 shows the operation following S820 in Figure 42. At the start of the flowchart in Figure 42, the display unit of the return locker is assumed to be showing the standby screen (initial screen) shown in Figure 39(B).

[0419] Furthermore, in the flowcharts of Figures 42 and 43, the factory copy has a QR code printed on it that encodes information including the number of returned items. The return locker, as part of its operation when storing items, determines the return slot based on the number of returned items, etc., and stores the determination result in its memory unit. Also, in the flowcharts of Figures 42 and 43, the return locker, as part of its operation when returning items to a user, refers to its memory unit and recognizes the return slot number determined for each user.

[0420] Step S800 in Figure 42: Determine whether the standby screen has been touched. If the standby screen has been touched (Step S800; YES), proceed to Step S801. If the standby screen has not been touched (Step S800; NO), return to Step S800. In other words, the process of Step S800 is repeatedly executed until the standby screen is touched. Step S801: Request the user to scan their membership card, etc. Specifically, display the card reading screen shown in Figure 39(B) and request the user to scan their membership card or enter their password.

[0421] Step S802: Determine whether or not a member card was read. If a member card was read (Step S802; YES), proceed to Step S804. If a member card was not read (Step S802; NO), proceed to Step S810.

[0422] Step S804: Notify the user of the corresponding return slot. Specifically, display the notification screen shown in Figure 39(C) and notify the user of the return slot number where the user's deposited items are stored. Step S805: Unlock the return door of the corresponding return slot and make the light flash. The light may be turned off, for example, after the return door is opened or closed (locked).

[0423] Step S806: Determine whether the locker return (handover of the stored items) has been completed. If the locker return is completed (Step S806; YES), proceed to Step S807. If the locker return is not completed (Step S806; NO), return to Step S806. In other words, the process in Step S806 is repeatedly executed until the locker return is completed.

[0424] Step S807: The system stores return completion information in the storage unit, indicating that the locker has been returned. The return completion information stored in step S807 may include, for example, some or all of the following: customer ID, return slot number, tag number, date and time information. Alternatively, the return locker may transmit the return completion information to the management device 10 instead of storing it in the storage unit, and the management device 10 may update various files based on the return completion information. Furthermore, the management device 10 may update various screens such as the slip details screen (Figure 27, etc.) (e.g., updating the progress status to "9 (delivery completed)") and display the updated screen on the user terminal 50, etc. Step S808: Notify that the locker return is complete. Specifically, display the completion screen shown in Figure 39(D). Then, the flowcharts in Figures 42 and 43 are completed.

[0425] Step S810: Determine whether a prescribed operation was performed by the store clerk (for example, whether the barcode for the store clerk was scanned). If a prescribed operation was performed (Step S810; YES), proceed to Step S820. If no prescribed operation was performed (Step S810; NO), return to Step S802.

[0426] Step S820: An initial screen for store staff (not shown) with various buttons (return item storage button, return item retrieval button, back button, etc.) is displayed. In other words, the system switches to store staff mode. Following step S820, the system proceeds to step S821 in Figure 43.

[0427] Step S821 in Figure 43: Determine whether the back button on the initial screen for the store clerk (not shown) has been touched. If the back button has been touched (Step S821; YES), return to Step S800. Alternatively, if the back button has been touched (Step S821; YES), return to Step S801 instead of Step S800. If the back button has not been touched (Step S821; NO), proceed to Step S822. Step S822: Determine whether the return item storage button on the initial screen for the store clerk (not shown) has been touched. If the return item storage button has been touched (Step S822; YES), proceed to Step S830. If the return item storage button has not been touched (Step S822; NO), proceed to Step S823. Step S823: Determine whether the return item collection button on the initial screen for store staff (not shown) has been touched. If the return item collection button has been touched (Step S823; YES), proceed to Step S840. If the return item collection button has not been touched (Step S823; NO), return to Step S821.

[0428] Step S830: Request the store clerk to scan the QR code printed on the factory copy. Specifically, display the initial storage screen shown in Figure 40(A) and instruct them to scan the QR code. Step S831: Determine whether the back button on the initial storage screen (Figure 40(A)) has been touched. If the back button has been touched (Step S831; YES), return to Step S821. Alternatively, if the back button has been touched (Step S831; YES), return to Step S800 (or Step S801) instead of Step S821. If the back button has not been touched (Step S831; NO), proceed to Step S832.

[0429] Step S832: Determine whether the QR code printed on the factory copy has been scanned. If the QR code has been scanned (Step S832; YES), proceed to Step S833. If the QR code has not been scanned (Step S832; NO), return to Step S831.

[0430] Step S833: Based on the scanned QR code (number of return slots), the return slot is determined using the method shown in Figures 29 to 32. Step S834: Notify the selected return slot. Specifically, display the storage instruction screen shown in Figure 40(B) and notify the return slot number of the selected return slot. Step S835: Unlock the return door of the selected return slot and make the light flash. The light may be turned off, for example, after the return door is opened or closed (locked).

[0431] Step S836: Determine whether the storage of the returned items (consigned goods) is complete. If storage is complete (Step S836; YES), proceed to Step S837. If storage is not complete (Step S836; NO), return to Step S836. In other words, the process in Step S836 is repeated until storage is complete.

[0432] Step S837: The storage completion information indicating that the returned items have been stored is stored in the storage unit. Then, the process returns to step S830. The storage completion information stored in step S837 may include, for example, some or all of the following: customer ID, return slot number, tag number, date and time information. Alternatively, instead of storing the storage completion information in the storage unit, the return locker may also transmit the storage completion information to the management device 10, and the management device 10 may update various files based on the storage completion information. Furthermore, the management device 10 may update various screens such as the slip details screen (Figure 27, etc.) (e.g., update the progress status to "4 (ready for handover)") and display the updated screen on the user terminal 50, etc. In addition to the normal "4 (ready for handover)", a "4A (storage complete)" indicating that the locker return storage has been completed may be provided as a progress status, and the progress status may be updated to "4A (storage complete)".

[0433] The store clerk then sequentially scans the QR code printed on each factory receipt, causing the store clerk to perform the storage process (steps S832-S837) for each receipt in turn. After the store clerk has performed the above process for all factory receipts, they touch the back button (step S831; YES) to finish the storage process.

[0434] Step S840: Request the store clerk to initiate the collection process. Specifically, display the initial collection screen shown in Figure 41(A) and request the clerk to touch the OK button to start the collection process. Step S841: Determine whether the back button on the initial retrieval screen (Figure 41(A)) has been touched. If the back button has been touched (Step S841; YES), return to Step S821. Alternatively, if the back button has been touched (Step S841; YES), return to Step S800 (or Step S801) instead of Step S821. If the back button has not been touched (Step S841; NO), proceed to Step S842.

[0435] Step S842: Determine whether the OK button on the initial retrieval screen (Figure 41(A)) was touched. If the OK button was touched (Step S842; YES), proceed to Step S844. If the Back button was not touched (Step S842; NO), return to Step S841.

[0436] Step S844: Announce all return slots. Specifically, display the collection instruction screen shown in Figure 41(B) and announce the return slot numbers for all return slots. Step S845: Unlock the return door of all return slots and make the light flash. The light may be turned off, for example, after the return door is opened or closed (locked). Step S847: Store collection completion information in the storage unit, indicating that the collection of returned items has been completed. The collection completion information stored in step S847 may include, for example, some or all of the following: customer ID, return slot number, tag number, date and time information. Then, return to step S821. Alternatively, after the completion of step S847, instead of returning to step S821, the system may return to step S800 (or step S801).

[0437] In addition to storing the collection completion information in the storage unit, the return locker may also transmit the collection completion information to the management device 10, and the management device 10 may perform various file updates, etc., based on the collection completion information. For example, in addition to the normal "4 (ready for handover)" as a progress category, a "4B (normal handover possible due to collection)" may be established to indicate that the stored items have been collected without the return of the items via locker return being completed, and the progress category may be updated to "4B (normal handover possible due to collection)".

[0438] In the flowcharts of Figures 42 and 43, the process is explained in the order of return by the user to the user (processing from step S802 (YES) onwards) → storage by the store clerk (processing from step S822 (YES) onwards) → retrieval by the store clerk (processing from step S823 (YES) onwards). However, if we focus on a certain product B held by user A, the order of processing is storage of product B by the store clerk → return of product B to user A by user A → retrieval of product B by the store clerk (however, if product B has been returned to user A, product B is not retrieved). Also, if we focus on the daily movements of store clerk C, the order of processing is retrieval of previously stored products by store clerk C → storage of currently stored products by store clerk C → return of currently stored products to the user by the user.

[0439] Although embodiments of the present invention have been described above, the configuration of the device, the data configuration, the processing flow, the display and output modes, etc., can be changed and modified as appropriate.

[0440] For example, in addition to the display unit 25, the POS terminal 20 may be equipped with a user-facing display unit (a touch display similar to the display unit 25), and the user-facing display unit may show a locker return date calendar screen (Figure 24, etc.), so that customers who visit the store can perform operations related to locker return (such as reserving a return date) on the POS terminal 20.

[0441] For example, the flowcharts shown in Figures 33 to 35 illustrate the operation when reserving a locker for locker return using a return locker installed at the store where the goods were deposited. However, the return locker used for locker return is not limited to the return locker installed at the store where the goods were deposited. In other words, it is possible to return goods using a return locker other than the one installed at the store where the goods were deposited (for example, a return locker installed at a different store than the store where the goods were deposited, or a return locker not installed at any store (a return locker installed at a location far from the store, a store-shared locker, etc.)). When reserving a locker return from the user terminal 50, for example, the user terminal 50 may display a screen where the user can specify (select) a locker, and send the locker number of the locker specified (selected) by the user on that screen to the management device 10 when requesting the reservation screen (i.e., in the process of step S600 in the flowchart of Figure 33). The same applies when reserving a locker return from the POS terminal 20. In other words, the POS terminal 20 may display a screen on which a locker can be specified (selected), and the locker number of the locker specified (selected) by the store clerk on that screen may be transmitted to the management device 10 when requesting the reservation screen (i.e., in the process of step S630 in the flowchart of Figure 34).

[0442] Furthermore, in the above embodiment, when there are available return slots in the locker, a device that determines the return slot (e.g., management device 10, POS terminal 20, return locker, etc.) determines (selects) the return slot. However, in the above case, the user may also determine the return slot. For example, the user terminal 50 may display a screen that allows the user to specify an empty return slot along with information that allows the user to recognize an empty return slot (for example, a schematic image of a return locker as shown in Figure 31(A), which allows the user to visually confirm the availability of each return slot), and the user may decide which return slot to use from among the empty return slots. After the return slot is determined, the user terminal 50 may transmit the determination result to the management device 10, and the management device 10 may perform various file updates, etc.

[0443] The above configuration leaves the decision of the return slot entirely to the individual user. However, the device that determines the return slot (e.g., management device 10, POS terminal 20, return locker, etc.) may also determine the return slot, taking into consideration the individual user's preferences (as a condition for determining the return slot). For example, the device that determines the return slot may, for users who wish to use an adjacent return slot, consider the user's preference (i.e., adjacent vacancies) when determining the return slot (determined by the method shown in Figures 28 to 33), and for users who do not wish to use an adjacent return slot, determine the return slot without considering adjacent vacancies (simply determining the return slot based on the past usage history of each return slot). Whether or not an adjacent return slot is desired may be confirmed by the user during member registration (the results of the confirmation may be stored, for example, in the customer master file), or the user may be asked to input this when making a locker reservation (for example, by providing a checkbox indicating the desire for an adjacent return slot on the reservation screen displayed in S605 of Figure 33).

[0444] In the above embodiment, an example was described in which adjacent spaces and past usage history were considered when determining the return slot. However, instead of or in addition to adjacent spaces and past usage history, the height from the installation surface may also be considered when determining the return slot. For example, if there are still multiple candidates when judging based on adjacent spaces and past usage history (for example, when one is randomly selected in S503 of Figure 29), the device that determines the return slot (e.g., management device 10, POS terminal 20, return locker, etc.) may prioritize determining the upper return slot (for example, the return slots with return slot numbers "H11", "H21", ..., "H61" in Figure 18(B)). Alternatively, for example, the return slot may be determined according to the user's preference, such as whether they prefer an upper return slot or a lower return slot (for example, the return slots with return slot numbers "H12", "H22", ..., "H62" in Figure 18(B)), as described above, by confirming this during member registration or having the user input this preference when reserving a locker.

[0445] In the above embodiment, each item being deposited is tagged, but the tags attached to the deposited items may be purchased by the user. In other words, the user may purchase the tags to be attached to the items being deposited. More specifically, the user may purchase the tags as part of or all of the cleaning fee for the items being deposited. Multiple types of tags with different selling prices for each type may be sold. Specifically, to make the selling price easily visible, the entire tag or part of the tag may be made of a different color or pattern for each type (each selling price). For example, a plain light blue tag may be sold for 300 yen (for shirts (dry cleaned) tags), and a light blue tag with a red line may be sold for 500 yen (for shirts (dry cleaned + sweat removal, etc.) tags). The places where tags are sold are not limited to dry cleaning stores, but may also be supermarkets, convenience stores, specialty stores (clothing stores, pharmacies, etc.), shops inside (or near) train stations, indoors or outdoors of apartment buildings, etc.

[0446] Furthermore, a vending machine may be installed in any of the locations mentioned above, and the tags may be sold through the vending machine. In addition, a vending machine may be installed at a locker location or a collection point for pickup and storage, even if it is not in one of the locations mentioned above. Furthermore, the vending machine that sells the tags may be equipped with a communication function so that purchase information (purchase date and time, purchase location (installation location), purchase quantity, etc.) is transmitted to the management device 10. Furthermore, the vending machine that sells the tags may be made capable of recognizing membership cards so that the customer code of the member who purchased the tags is transmitted to the management device 10. Furthermore, points may be awarded for the purchase of tags.

[0447] In the above embodiment, the tag numbers of each consigned item within a transaction (each consigned item belonging to a certain slip) are sequential (see Figure 6). However, it is sufficient to identify which transaction (slip) each consigned item belongs to, and the tag numbers of each consigned item within a transaction do not need to be sequential. Therefore, when selling tags, it is not necessary to be aware of the tag numbers of the tags being sold (for example, when selling multiple tags to a user, it is not necessary to check whether the tag numbers are sequential). However, it is difficult to sell tags of different types in sequential order. Also, when consuming (using) tags, it is not necessary to be aware of the tag numbers of the tags attached to the consigned items (for example, when consigning multiple items, it is not necessary to check whether the tag numbers of the tags attached to each item are sequential). In the above embodiment, it is possible to use the consigned item number instead of the tag number in various screens (Figures 11, 12, etc.) and various files (Figure 20, etc.). The same applies when tags are not sold, i.e., when store employees attach the tags.

[0448] In cases where tags are sold, if payment is not made at the time of item drop-off, resulting in a delay in fee collection (specifically in the case of bagged items), tags may be sold to expedite collection. For example, in the case of speed drop-off (drop-off category "2") and locker drop-off (drop-off category "4"), customers may be asked to attach tags to items dropped off in bags. The user terminal 50 may also display a list screen of cleaning fees (for example, by receiving and displaying a list screen from the management device 10 or POS terminal 20). Furthermore, the user terminal 50 may also display the location where tags are sold (the nearest sales location, etc.) (for example, the management device 10 or POS terminal 20 may be equipped with a sales location search function, and the user terminal 50 may use this search function to display the sales location).

[0449] Furthermore, if the price on the tag attached to the product by the user does not reach the required amount (price after inspection), the management device 10 (or POS terminal 20) may notify the user's terminal 50 that the amount is insufficient and display a screen allowing the user to select a payment method (credit card payment, prepaid payment, coupon payment, point payment) so that the user's terminal 50 can settle the deficit. On the other hand, if the price on the tag attached to the product by the user exceeds the required amount (price after inspection), the management device (or POS terminal 20) may send the user's terminal 50 a coupon for the excess amount or an electronic exchange voucher that can be redeemed for the excess amount when visiting the store (for example, an exchange screen displaying the amount to be received and a barcode indicating the amount to be received). In addition, the management device (or POS terminal 20) may record (reflect) the excess amount as a deposit in the prepaid payment and notify the user's terminal 50 that the excess amount has been recorded as a deposit in the prepaid payment.

[0450] Furthermore, to promote the sale of tags, preferential treatment may be given to awarding points for tag purchases. For example, if 1 point is awarded for every 200 yen spent with cash payment at a store, 2 points may be awarded for every 300 yen spent on tag purchases. Alternatively, points may be awarded when tags are used, either in addition to or instead of when they are purchased. In addition, an expiration date may be set for purchased tags, and more points may be awarded for using them within that expiration date.

[0451] Furthermore, in the above embodiment, the reception-only locker 100 is equipped with a control unit, and the control unit controls the display on the display unit 104 and the locking of the slot door, etc. However, other devices (for example, a management device 10, a POS terminal 20) may control some (or all) of the displays on the display unit 104 and the locking of the slot door, etc. The same applies to the common locker 200. For example, the common locker 200 may transmit information necessary for authentication (for example, information recognized by the code recognition unit 206) to the management device 10 (or POS terminal 20), the management device 10 (or POS terminal 20) may perform authentication based on the information received from the common locker 200 and transmit the authentication result to the common locker 200, and the common locker 200 may unlock the return door based on the authentication result received from the management device 10 (or POS terminal 20).

[0452] Furthermore, in the above embodiment, a locker as shown in Figure 18 was described as an example of a storage unit, but the storage unit is not limited to the locker type and may be a shelf type (for example, a shape without doors, such as a clothing display shelf). If a shelf-type storage unit is installed, for example, in a store, users can enter the store during business hours and pick up their own items that have been returned to the shelf themselves. This is convenient for both users and store staff, as it eliminates the need for customers to wait in line to receive their items, especially when the store is crowded, and for store staff, it eliminates the need to hand over items to customers when they come in, if the items have been placed on the shelf in advance. It is also possible to take measures to prevent items from being taken away without permission. For example, if the items for one user are placed in a box or similar container and placed on the shelf, a locking mechanism may be provided on the shelf itself, between the shelf and the box, or on the box itself, so that the items cannot be taken out of the box or container without unlocking it.

[0453] Furthermore, storage units can take any form other than lockers or shelves, such as color boxes or hanger racks. Even with the above types of storage units, measures can be taken to prevent unauthorized removal of items. For example, in the case of a hanger rack, a locking mechanism could be installed on the hanger section, preventing the hangers from being removed from the rack without unlocking them.

[0454] Furthermore, the above-mentioned lock function may be released in response to, for example, an operation by a store employee or a member. For example, a shelf-type storage unit (or other types of storage units) may be made capable of recognizing a member card, and when the member card is read, the lock on the relevant section (the section where the user's products are stored) may be released. Alternatively, a shelf-type storage unit (or other types of storage units) may be equipped with a communication function, and a store employee may perform an unlock operation (which may include an operation to specify the target to be unlocked) on the screen of the POS terminal 20 (or store mobile terminal 30), thereby releasing the lock on the relevant section (the section specified by the store employee; the section where the user's products are stored).

[0455] Furthermore, a medium (receipt) for the user to use when returning items to the locker may be printed and issued. For example, in addition to the slips shown in Figures 37 and 38, the POS terminal 20 may print and issue a medium with a barcode that can be recognized by the return locker (such as a barcode printed on the factory copy shown in Figure 38) when a user who does not have a cleaning app or membership card requests a locker return. The medium has information such as the barcode, the deposited items, the settlement amount, and the reservation date (pickup date) printed on it. The medium is a return ticket, pickup ticket, and proof ticket (proof information) for locker returns. The user receives the medium from the staff when reserving the locker and keeps it until the reservation date. On the reservation date, the user can pick up their items by having the return locker recognize the barcode on the medium. In other words, the return locker recognizes the barcode and unlocks the return slot containing the user's items based on the information encoded in the barcode. Alternatively, instead of a barcode, a 10-digit number or similar may be printed on the above medium, and on the day of reservation, the user can retrieve the product from the return locker by entering the number or similar on the medium into the return locker. Furthermore, considering the possibility of the medium being lost, in addition to barcode recognition (input of the number or similar), a password predetermined for each user may be required to unlock the locker. In other words, the return locker may be unlocked by recognizing the barcode printed on the medium (inputting the number printed on the medium) + entering the correct password.

[0456] Furthermore, the cleaning system may allow users to obtain an estimate before submitting their items. For example, the user terminal 50 may display a screen (for example, called an estimate screen) with input (selection) fields for entering (selecting) the type of items to be submitted, processing (dry cleaning, stain removal, etc.), quantity, etc. The information entered by the user on the estimate screen is transmitted to the management device 10, and the management device 10 may refer to the information received from the user terminal 50, a product type file (Figure 7(A)), a processing type file (Figure 7(C)), a basic service file, etc., calculate the fee as an estimate, and send (respond) it to the user terminal 50. In addition to or instead of the fee, the management device 10 may also calculate the number of days required as an estimate and send (respond) it to the user terminal 50. Furthermore, the estimate screen may allow the user to enter (select) the submission date (the date on which the items are scheduled to be submitted), and the management device 10 may calculate the estimated completion date as an estimate based on the submission date and the number of days required, and send (respond) it to the user terminal 50.

[0457] Furthermore, if the user terminal 50 selects to return the locker (for example, if a button to specify locker return is provided on the estimation screen and the user presses that button), the management device 10 (or POS terminal 50) may calculate the locker return availability date as an estimate (for example, information such as that shown in Figures 23(B), 23(C), 23(E), and 23(F)) and send (respond to) the user terminal 50.

[0458] If the user confirms and agrees to the response (quote details) from the management device 10, the information entered during the quotation process may be made available for use in subsequent processes (such as the actual reservation process). For example, a reservation button (or a "proceed" button) may be provided on the screen displaying the quotation details (e.g., the quotation screen, or a screen different from the quotation screen). When this button is pressed, information indicating that the user agrees to the quotation details is sent from the user terminal 50 to the management device 10, and the management device 10 may send the screen information of the reservation screen related to product storage to the user terminal 50. The user terminal 50 sends the information entered by the user on the reservation screen (such as information regarding storage category) to the management device 10, and the management device 10 may use the information already received during the quotation process (such as product type, processing, quantity, and storage date) and the information received this time (at the time of the actual reservation) (such as information regarding storage category) to perform reservation processing related to product storage (such as updating various files). The customer code should be transmitted from the user terminal 50 to the management device 10 at at least one of the following times: during the quotation process or during the actual reservation. The information that the user inputs (selects) on the reservation screen is, for example, the type of storage (Figure 5, etc.), such as regular store storage or speed storage. As described above, the information entered during the quotation process can be used directly in subsequent processes, which is convenient. The storage reservation information is distributed to the POS terminal 20, and store staff can check the reservation details on the POS terminal 50 and use this information to make various preparations (including not only actual preparations but also mental preparations, etc.). The reservation screen for product storage may also be accessible without obtaining a quotation (for example, directly from the membership card screen, etc.).

[0459] Furthermore, although several screens (for example, a receipt details screen, a locker return reservation confirmation screen, etc.) have been described in the above embodiment, other screens may be displayed based on various information stored in the cleaning system. For example, based on the progress status of the deposited item information file (Figure 6), a screen may be displayed for store staff to check the progress (for example, a list screen of deposited items on hold, a list screen of users whose items are ready for handover but the handover process has not yet progressed, etc.).

[0460] Furthermore, for example, performance information regarding locker reservations may be displayed based on the collection completion information explained in Figure 43. As an example, information indicating whether or not the goods were actually received on each past locker reservation date (or whether or not the goods stored in the locker were collected without the return of the goods being completed) may be displayed for each locker, for each month or day of the week, for each user, or a combination of these. Weather information may be obtained and displayed separately or in addition to the above, depending on the weather at the location where the locker is installed. In addition, when a user reserves a locker, the user's past performance (for example, history information such as "return completed for the previous reservation on Month Day," and "return not completed (collected) for the reservation before that on Month Day") may be displayed on the locker return date calendar screen or on a screen displayed by pressing a designated button on the locker return date calendar screen.

[0461] As another example, the percentage of items actually received on each past locker reservation date (or the trend of that percentage) may be classified as described above (by locker, by user, etc.) and displayed. Users with unsatisfactory performance (for example, users whose percentage is lower than a predetermined first threshold) may also be displayed in a list. The same applies to lockers with unsatisfactory performance. Furthermore, in order to improve the situation, for example, when a user with unsatisfactory performance reserves a locker, they may be notified of their unsatisfactory performance on the locker return date calendar screen or on a screen displayed when they press a designated button on the locker return date calendar screen, or a message may be displayed to ensure that they properly receive their items on the reservation date. Additionally, such messages may be sent to users with unsatisfactory performance on the day of or the day before the reservation date via the cleaning app or email.

[0462] Furthermore, a list of users with favorable performance (for example, users whose percentage is higher than a pre-set second threshold) may be displayed. The second threshold may be a value greater than the first threshold. Furthermore, points may be awarded to users with favorable performance.

[0463] Furthermore, users who actually pick up their items early (on the day of the return date (scheduled completion date), or within a few days of the return date) may be awarded higher points, and thereafter, the points awarded may be progressively reduced according to the number of days elapsed since the actual pickup date. Alternatively, after the "early" stage, there may be no further stages, and the overall system may simply be divided into two stages: "early" or "not early." Note that the method of pickup (return category) is not limited to locker return (locker handover). For example, even with face-to-face returns (e.g., regular store handover), as described above, higher points may be awarded for early pickup, and thereafter, the points awarded may be progressively reduced. This will encourage early pickup of products and contribute to reducing inventory in stores. In addition, information that allows users to check how many points will be awarded depending on when they pick up their products (for example, the number of points awarded for each pickup date, a message stating that ×× points will be awarded if you pick up your products by XX day) may be displayed on the user terminal 50 or POS terminal 20.

[0464] In the above embodiment, various scenarios in which points are awarded as a benefit to users have been described, but the benefits to users are not limited to points. For example, instead of awarding points, or in addition to that, a special edition membership card (for example, a card with a different color or design than usual) may be awarded (e.g., in exchange for a regular one), or a special edition membership card screen (for example, a membership card screen with a different color or design than usual) may be displayed.

[0465] Furthermore, the programs for realizing the functions of the cleaning systems 1 and 2, the management device 10, the POS terminal 20, the store's mobile terminal 30, the factory terminal 40, the user terminal 50, the reception locker 100, and the common locker 200 described above may be recorded on a computer-readable recording medium, and the program may be loaded into a computer system and executed. Here, "computer system" includes hardware such as the OS and peripheral devices. Furthermore, "computer-readable recording medium" refers to portable media such as flexible disks, magneto-optical disks, ROMs, CD-ROMs, and storage devices such as hard disks built into computer systems. In addition, "computer-readable recording medium" also includes volatile memory (RAM) inside computer systems that act as servers or clients when a program is transmitted via a network such as the Internet or a communication line such as a telephone line, which retains the program for a certain period of time. Furthermore, the above program may be transmitted from the computer system that stores the program in a storage device, etc., to another computer system via a transmission medium or by transmission waves in the transmission medium. Here, the "transmission medium" used to transmit the program refers to a medium that has the function of transmitting information, such as a network (communication network) like the Internet or a communication line (communication line) like a telephone line. Furthermore, the program described above may be intended to implement only a part of the functions mentioned above. Moreover, it may be a so-called differential file (differential program) that can implement the aforementioned functions in combination with a program already recorded in the computer system.

[0466] The technical concepts described above are presented below as supplementary information.

[0467] (Appendix 1A) An input means (for example, step S18 in Figure 9) for inputting information about the cleaning items received from the user (for example, product type, processing type, etc.), A management means (for example, the storage unit of the management device 10 or the hard disk 24 of the POS terminal 20) for managing the usage status of storage units (for example, lockers shown in Figures 1 and 18, etc., for example, the information shown in Figures 20 and 21, in particular the reservation status for each return date, the number of available return slots, etc.), A calculation means (for example, the process in step S406 of Figure 22) for calculating the return date (reservation date, etc.) from the aforementioned storage information and the aforementioned usage status, An output means that outputs the return date calculated by the calculation means (for example, the process in step S407 of Figure 22), A cleaning system characterized by having the following features.

[0468] According to Appendix 1A, a suitable return date can be determined based on the storage information for the cleaned items and the usage status of the storage facility, thereby improving operational efficiency.

[0469] (Appendix 2A) The cleaning system according to Appendix 1A, characterized by having a display means (for example, the display unit of the user terminal 50, the display unit 25 of the POS terminal 20, the display unit of the management device 10, etc.) that can distinguish between days on which items can be returned and days on which items cannot be returned (for example, in Figures 23(C) and 23(F), reservation availability (return availability) is displayed as "○" or "×", in Figures 24 and 25, reservation availability is displayed as a background color, etc.).

[0470] According to Appendix 2A, for example, it becomes...

Claims

1. A cleaning system comprising a receiving device equipped with a lockable drop-off door through which customers themselves drop off their cleaning items, a POS terminal operated by a store employee, a management device, and a customer's mobile terminal, The aforementioned POS terminal is A first reading means for optically reading customer identification information to identify a customer, A registration method for registering cleaning items received from customers, A transmission means for transmitting transaction information, including the customer identification information read by the first reading means and the information regarding the cleaning items registered by the registration means, to the management device. Equipped with, The aforementioned control device is A transmission means that transmits information regarding the cleaning items that the customer has placed in the storage device to the customer's mobile terminal. Equipped with, The aforementioned storage device is A second reading means for optically reading customer identification information to identify a customer, An unlocking means for unlocking the input door based on the reading by the second reading means, Equipped with, The aforementioned mobile terminal is The POS terminal and the deposit device are display means that display a code from which the customer identification information of the customer can be read. Equipped with, When a customer entrusts items to a store employee for cleaning, The first reading means of the POS terminal is The customer identification information is read optically from the code displayed by the mobile terminal. The registration means of the POS terminal is Register the cleaning items entrusted to us by the customer. When a customer deposits items to be cleaned into the aforementioned deposit device, The second reading means of the deposit device is The customer identification information is read optically from the code displayed by the mobile terminal. The first reading means of the POS terminal is The customer's identification information is read from the card that the customer put into the receiving device along with the items to be cleaned. The registration means of the POS terminal is The cleaning items that the customer has placed in the storage device are registered, When a customer receives their cleaned items, The first reading means of the POS terminal is The customer identification information is read optically from the code displayed by the mobile terminal. A cleaning system characterized by the following features.

2. The display means of the aforementioned mobile terminal is When handing over items to be cleaned to a staff member, The POS terminal displays a code that encodes the customer's customer identification information as a code that can read the customer's customer identification information. When placing items to be cleaned into the aforementioned storage device, The aforementioned deposit device displays a code that encodes the customer's customer identification information as a code that can read the customer's customer identification information. When receiving your cleaned items, The POS terminal displays a code that reads the customer's customer identification information, which is a code that encodes the customer's customer identification information and information that identifies the cleaning items to be received. The cleaning system according to feature 1.

3. It further includes a return device where customers can pick up their own cleaned items, The aforementioned display means is An operator is displayed to accept an operation to retrieve the cleaned items using the return device. The cleaning system according to claim 1 or 2, characterized by the features described above.

4. The aforementioned display means is The individual items to be cleaned are displayed side by side, and for items to be returned by the return device, a message indicating that they will be returned by the return device is displayed. The cleaning system according to feature 3.

5. A cleaning system comprising a receiving device equipped with a lockable opening door through which customers themselves deposit their cleaning items, a POS terminal operated by a store employee, a management device, and a customer's portable terminal equipped with a display unit, wherein a program causes a first computer to function as the POS terminal, a second computer to function as the management device, a third computer to function as the receiving device, and a fourth computer to function as the portable terminal, The first computer, A first reading means for optically reading customer identification information to identify a customer, A registration method for registering cleaning items received from customers. A transmission means transmits to the management device the customer identification information read by the first reading means, the information regarding the cleaning items registered by the registration means, and transaction information including this information. To make it function as, The second computer described above, A transmission means that transmits information regarding the cleaning items that the customer has placed in the storage device to the customer's mobile terminal. To make it function as, The third computer described above, A second reading means for optically reading customer identification information to identify a customer, Unlocking means for unlocking the input slot door based on the reading by the second reading means To make it function as, The fourth computer, Display control means that causes the POS terminal and the deposit device to display a code on the display unit that allows the customer identification information of the customer to be read. To make it function as, When a customer entrusts items to a store employee for cleaning, The first reading means is, The customer identification information is read optically from the code displayed by the mobile terminal. The registration means is, Register the cleaning items entrusted to us by the customer. When a customer deposits items to be cleaned into the aforementioned deposit device, The second reading means is, The customer identification information is read optically from the code displayed by the mobile terminal. The first reading means is, The customer's identification information is read from the card that the customer put into the receiving device along with the items to be cleaned. The registration means is, The cleaning items that the customer has placed in the storage device are registered, When a customer receives their cleaned items, The first reading means is, The customer identification information is read optically from the code displayed by the mobile terminal. A program characterized by the following features.

6. A cleaning management method in a cleaning system that includes a receiving device equipped with a lockable input door through which customers themselves deposit cleaning items, a POS terminal operated by a store employee, a management device, and a customer's portable terminal equipped with a display unit, The POS terminal performs a first reading step of optically reading customer identification information to identify the customer, The aforementioned POS terminal performs a registration step of registering the cleaning items received from the customer, A transmission step that transmits transaction information, including the customer identification information read by the first reading step and the information regarding the cleaning items registered by the registration step, to the management device by the POS terminal, A transmission step by the management device to transmit information regarding the cleaning items that the customer has placed in the storage device to the customer's mobile terminal, A second reading step involves optically reading customer identification information used by the aforementioned storage device to identify the customer, An unlocking step in which the deposit door is unlocked based on the reading by the deposit device in the second reading step, The aforementioned mobile terminal performs a display step in which the POS terminal and the deposit device display a code that allows the customer identification information of the customer to be read. Includes, When a customer entrusts items to a store employee for cleaning, The first reading step of the POS terminal is: The customer identification information is read optically from the code displayed by the mobile terminal. The registration step of the POS terminal is as follows: Register the cleaning items entrusted to us by the customer. When a customer deposits items to be cleaned into the aforementioned deposit device, The second reading step of the storage device is as follows: The customer identification information is read optically from the code displayed by the mobile terminal. The first reading step of the POS terminal is: The customer's identification information is read from the card that the customer put into the receiving device along with the items to be cleaned. The registration step of the POS terminal is as follows: The cleaning items that the customer has placed in the storage device are registered, When a customer receives their cleaned items, The first reading step of the POS terminal is: The customer identification information is read optically from the code displayed by the mobile terminal. A cleaning management method characterized by the following:

Images