Cleaning system, program, and cleaning management method

Abstract

To improve business efficiency associated with use of a storage.SOLUTION: A cleaning system comprises: input means for inputting reception information associated with an object of cleaning to be received from a user; management means for managing a use state of a storage; calculation means for using the number of days required for finishing based upon the reception information and the use state to calculate a returnable day when the object can be returned; and output means for outputting the returnable day that the calculation means calculates.SELECTED DRAWING: Figure 1

Description

[Technical field]

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

[0002] Dry cleaning shops have been making various efforts to improve the efficiency of their operations. For example, a dry cleaning delivery system consisting of a dry cleaning bag and a locker unit has been proposed (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

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

[0004] However, the technology disclosed in Patent Document 1 has a problem in that it does not sufficiently improve the efficiency of operations related to the use of storage facilities (for example, lockers, etc.).

[0005] The present invention has been made in view of the above circumstances, and has an object to provide a technique for improving the operational efficiency regarding the use of storage units. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems, a cleaning system which is one aspect of the present invention comprises an input means for inputting deposit information regarding items to be cleaned from a user, a management means for managing the usage status of the storage facility, a determination means for determining whether or not the day has arrived when the items can be returned by the storage facility based on the number of days required for finishing based on the deposit information and the usage status, a display means for displaying the determination result by the determination means, and a printing means for printing a paper including a description indicating return by the storage facility. Effect of the Invention

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

[0008] [Figure 1] 1 is a schematic configuration diagram of a cleaning system according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a functional block diagram of a POS terminal. [Diagram 3] 4 is an example of various information stored in the cleaning system. [Figure 4] 4 is an example of various information stored in the cleaning system. [Diagram 5] 4 is an example of various information stored in the cleaning system. [Figure 6] 4 is an example of various information stored in the cleaning system. [Figure 7] 4 is an example of various information stored in the cleaning system. [Figure 8] 1 is an example of a confirmation image (an image showing a defective portion). [Figure 9] 13 is a flowchart showing an example of an operation when a product is deposited. [Figure 10] 13 is an example of a membership card screen. [Figure 11] 13 is an example of a slip list screen. [Figure 12] 13 is an example of a slip details screen (a deposit slip screen, an electronic deposit slip). [Figure 13] 13 is a flowchart showing an example of an operation at the time of product delivery. [Figure 14] 13 is an example of a slip details screen (a deposit slip screen, an electronic deposit slip). [Figure 15] 13 is a flowchart showing an example of another operation at the time of product delivery. [Figure 16] 13 is a flowchart showing an example of another operation at the time of product delivery. [Figure 17] 13 is a flowchart showing an example of another operation at the time of product delivery. [Figure 18] FIG. 2 is an external perspective view showing an example of a locker. [Figure 19] 4 is an example of various information stored in the cleaning system. [Figure 20] 11 is an example of information stored in the cleaning system. [Figure 21] FIG. 11 is an explanatory diagram for explaining management of locker usage status. [Figure 22] 13 is a flowchart showing an example of an operation relating to a method for specifying an available reservation date. [Diagram 23] FIG. 11 is an explanatory diagram for explaining a method for identifying available reservation dates. [Figure 24] 13 is an example of a locker return date calendar screen. [Diagram 25] 13 is an example of a locker return date calendar screen. [Figure 26] 13 is an example of information stored in the cleaning system. [Figure 27] 13 is an example of a slip details screen (a deposit slip screen, an electronic deposit slip). [Figure 28] 13 is an example of a file used to determine whether return slots are adjacent to each other. [Figure 29] 13 is a flowchart showing an example of a method for determining a return port. [Diagram 30] 13 is a flowchart showing another example of a method for determining a return port. [Diagram 31] FIG. 11 is an explanatory diagram for explaining a method for determining a return port. [Diagram 32]FIG. 13 is an explanatory diagram illustrating another method for determining the return port. [Diagram 33] 13 is a flowchart showing an example of an operation when reserving a locker. [Diagram 34] 13 is a flowchart showing an example of another operation when reserving a locker. [Diagram 35] 13 is a flowchart showing an example of another operation when reserving a locker. [Diagram 36] 13 is an example of a locker return reservation confirmation screen (locker return schedule list screen). [Figure 37] This is an example of a medium that is printed or issued. [Figure 38] This is an example of a medium that is printed or issued. [Figure 39] 13 is an example of a screen displayed on a display unit of a return locker. [Diagram 40] 13 is an example of a screen displayed on a display unit of a return locker. [Diagram 41] 13 is an example of a screen displayed on a display unit of a return locker. [Diagram 42] 13 is a flowchart showing an example of the operation of a return locker. [Diagram 43] 13 is a flowchart showing an example of the operation of a return locker. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

[0010] The cleaning system 1 includes a management device 10, a POS terminal (business operator terminal) 20, a store mobile terminal 30 (business operator terminal), a factory terminal 40, a user terminal 50, and a locker (described later). The management device 10, the POS terminal 20, the factory terminal 40, and the 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 be one that utilizes a wireless LAN, a mobile phone network, the Internet, or the like. The store mobile terminal 30 is capable of communicating with the POS terminal 20, for example, via a wireless LAN. The lockers may also be capable of communicating with other devices (for example, the management device 10, the POS terminal 20, etc.) via the network 90, for example.

[0011] A configuration excluding the user terminal 50 from the cleaning system 1 may be referred to as cleaning system 2. A configuration including any two to five of the management device 10, POS terminal 20, store mobile terminal 30, factory terminal 40, and lockers may be referred to as cleaning system 1. As an example, a system consisting of three components, the management device 10, the POS terminal 20, and lockers, or a system consisting of two components, the POS terminal 20 and lockers, may be referred to as cleaning system 1 (or cleaning system 2). In a configuration that does not have a cleaning factory (i.e., a configuration in which products are cleaned 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. As an example, the management device 10 may be a cloud server that provides various services related to cleaning. The management device 10 is assumed to be capable of performing push-type communication (notification) to other devices (for example, a 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, in the case of a server installed in a data center), maintenance of the management device 10 may be performed via another device (for example, a personal computer, not shown) that can communicate (connect) with the management device 10.

[0013] The POS terminal 20 is installed in a dry cleaning store (a dry cleaning agency) and is operated by a dry cleaning store employee. The POS terminal 20 may be installed in an individual store (a dry cleaning store run by an individual) or in a chain store (each store in a chain). That is, the dry cleaning system 1 is applicable to both an individual store and a chain store. The store mobile terminal 30 is, for example, a tablet terminal used in the dry cleaning store.

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

[0015] The user terminal 50 is a terminal operated by a user (for example, a smartphone, tablet terminal, personal computer, etc. owned by a user). The user terminal 50 may be configured to be able to download and install an application program from the management device 10 or a device (server (not shown)) different from the management device 10 via the network 90. ​​In this embodiment, an application program (hereinafter, sometimes simply referred to as a "cleaning app") for a user who uses a dry cleaning shop (various services related to cleaning) in the cleaning system 1 is installed on the user terminal 50, and the user has completed membership registration by the cleaning app. The cleaning app may include data related to various screens and various messages displayed on the display unit of the user terminal 50. In addition to starting, executing, and ending the cleaning app in response to a user's operation, the cleaning app may also start, execute, and end in response to a request from another program (application program or OS). For example, the cleaning app may be resident on the user terminal 50 without displaying a screen, monitor whether information transmitted from another device (for example, the management device 10, etc.) has been received, and when information has been received, a screen corresponding to the received information may be displayed on the display unit without the user's operation.

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

[0017] The ROM 22 is a read-only memory, and stores various information such as programs for operating the POS terminal 20. The RAM 23 is a temporary storage area, and temporarily stores information referenced by the CPU 21 (programs, data, etc. read from the ROM 22 and expanded), generated information, information received via the communication unit 28, information to be transmitted, etc. The hard disk 24 is an auxiliary storage device, and stores information referenced by the CPU 21, generated information, information received via the communication unit 28, information to be transmitted, 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 touch pad, a handy scanner, a card reader, etc., arranged on the display screen of the display unit 25. The printing unit 27 prints and issues various information (for example, various slips, a list of products desired for delivery, etc.). The slips issued by the printing unit 27 are, for example, customer copies (also called "deposit slips" or "customer copies"; see FIG. 27), factory copies (also called "factory copies"; see FIG. 28), etc. The communication unit 28 is a communication interface for communicating with various devices via the network 90.

[0019] 3 to 7 are examples of various information stored in the cleaning system 1. Fig. 8 is an example of an image (image data) showing a defective part (abnormal part). Note that "..." in each file shown in Figs. 3 to 7 indicates that a value has been omitted. The same applies to the other figures.

[0020] (Customer master file) Fig. 3(A) is 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 related to customers (members) who are users. The customer master file shown in Fig. 3(A) stores, in association with a customer code, name (kanji), name (furigana), address, communication destination, email, telephone number (1), telephone number (2), application communication identification information, birthday, membership registration date, registered store (store code), etc. The name (kanji), name (furigana), address, etc. are information acquired from the user when registering as a member.

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

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

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

[0024] The application communication identification information is information for performing communication of a cleaning application executed on the user terminal 50 of the user. The application communication identification information may be any information capable of identifying the user terminal 50 of the user in communication of the cleaning application, and may be, for example, an IP address of the user terminal 50, individual identification information of the user terminal 50, a telephone number of the user terminal 50, or identification information (such as a token) different from the individual identification information. Note that the application communication identification information may be fixedly assigned to the user terminal 50, or may be temporarily assigned to the user terminal 50 (for example, may change each time the cleaning application is started). When the application communication identification information is temporarily assigned, it is sufficient to store the latest application communication identification information.

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

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

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

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

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

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

[0031] The point management file shown in Figure 3 is configured in such a way that the points being managed are common to all stores in a chain (points awarded at each store are added together and can be used at any store). However, in such a case where points are managed individually at each store in the chain (points awarded at a store can only be used at that store), the number of available points, etc. may be stored, for example, in correspondence with the store code and customer code (i.e., by store code and customer code).

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

[0033] The coupons in this embodiment are electronic coupons, and multiple types are prepared for different target products. The coupons in this embodiment are sold in units of multiple uses, and are priced at a discount for the user. For example, in the case of a coupon for a target product of dress shirts, the price (3,300 yen) for 11 uses (use of 11 dress shirts (dry)) is sold (issued) for the price (3,000 yen) for 10 uses. The coupons in this embodiment are electronic coupons as described above, but in the following explanation, they may be counted as one, two, etc., like paper coupons.

[0034] The coupon management number is information for managing (identifying) the sale (issuance) of a coupon in the cleaning system 1. For example, when selling a coupon, the management device 10 may assign (assign) a unique coupon management number (the last two digits of the year - a serial number, etc. The example shown in FIG. 4 is the 369th coupon for the year 201X). The coupon type is information indicating the type (kind) of coupon for each applicable product that can be used. The purchaser is information indicating the purchaser of the coupon.

[0035] (Coupon usage record file) FIG. 4(B) is an example of a coupon usage history file stored by management device 10. The coupon usage history file is a file that stores information regarding coupon usage history by user (by customer code). The coupon usage history file shown in FIG. 4(B) stores, by customer code, the purchase date (issue date), coupon type, expiration date, total number of uses, remaining number, each usage history (usage date, number of uses), etc., in association with the coupon management number. Note that management device 10 updates the coupon usage history file (updates the total number of uses, remaining number, usage history, etc.) when a coupon is used.

[0036] The expiration date is information indicating the expiration date of the coupon (the expiration date common to all 11 coupons). The total number of uses is the total number of uses in each instance. The remaining number is information indicating 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 coupon is the same regardless of the number of coupons if they are sold on the same day (i.e., the expiration date is the same whether it is the first coupon or the last coupon, 11th coupon), but the expiration date may be different depending on the number of coupons. As an example, the expiration dates of coupons 1 to 5 out of the total 11 coupons may be 28 days (4 weeks) from the sale date, and the expiration dates of coupons 6 to 11 may be 56 days (8 weeks) from the sale date.

[0038] In this embodiment, the sales unit of the coupon is the same (11 uses, i.e., 11 coupons in total) regardless of the type of coupon (i.e., the target product), but the sales unit may be different depending on the type of coupon. As an example, the sales unit of a coupon for dress shirts may be 11 coupons, and the sales unit of a coupon for sweaters may be 6 coupons, and so on, so that the sales unit for higher-priced products (see FIG. 7(D)) may be smaller.

[0039] (Electronic document file) Fig. 5 is 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 transaction details for various cleaning services. The electronic slip file shown in Fig. 5 stores, in association with the slip number, the date and time of deposit, store code, clerk code, customer code, deposit category, number of items deposited, total fee, expected completion date, delivery completion date, receipt reminder date, update date and time, etc. The management device 10 updates the electronic slip file (adds new information) when the product is deposited, and updates it as appropriate according to the progress of the service, etc.

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

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

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

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

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

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

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

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

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

[0049] (Deposit product information file) Fig. 6 is an example of a deposited product information file stored by management device 10. The deposited product information file is a file that stores information about each deposited product. The deposited product information file shown in Fig. 6 stores, in association with the deposited product number, the tag number, product type, processing type, fee, pending classification, progress classification, expected completion date, reservation classification, delivery classification, expected delivery date, delivery completion date, update date and time, etc. The management device 10 updates the electronic slip file (adds new information) when the product is deposited, and updates it as appropriate according to the progress of the service, etc.

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

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

[0052] The product type is information indicating the type of product (see FIG. 7(A)). The processing type is information indicating the type of processing (washing, storage, etc.) (see FIG. 7(B)). The fee is information indicating the fee for the deposited product (see FIG. 7(D)).

[0053] The hold category is information indicating whether or not progress needs to be put on hold. In this embodiment, if the deposited item is a specific item (item that is dirty, frayed, etc.; see FIG. 7(E)), in order to prevent any trouble, the customer is asked to check the current state of the item (such as dirt or fraying) before it is actually processed (washed, etc.) at the dry cleaning factory. Hold category "0" indicates no need to hold (no reason for holding), hold category "1" indicates need to hold (before user confirmation), and hold category "2" indicates no need to hold (user confirmation completed).

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

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

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

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

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

[0059] Regular store pick-up (regular store return) is a method in which the product is handed over at the store's reception desk. Delivery pick-up (delivery return) is a method in which the product is handed over at a designated delivery location. Locker pick-up (locker return) is a method in which the product is handed over using a designated locker (see Figures 18(B) and 18(C)).

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

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

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

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

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

[0065] (Product type file) Fig. 7(A) is an example of a product type file stored in the management device 10. The product type file shown in Fig. 7(A) stores product types and the like in association with product types. The POS terminal 20 may receive the product type file from the management device 10 and store it.

[0066] (Store File) Fig. 7(B) is an example of a store file stored in the management device 10. The store file shown in Fig. 7(B) stores store names, locations (addresses), locations (latitude and longitude), etc. in association with store codes. The POS terminal 20 may receive the store file from the management device 10 and store it.

[0067] (Processing type file) Fig. 7(C) is an example of a process type file stored in the management device 10. The process type file shown in Fig. 7(C) stores, for example, washing and storing in association with the process type. The POS terminal 20 may receive the process type file from the management device 10 and store it.

[0068] (Service basic file) Fig. 7(D) is an example of a service basic file stored in the management device 10. The service basic file shown in Fig. 7(D) stores charges, number of days required, etc. in association with product types and processing types. The POS terminal 20 may receive the service basic file from the management device 10 and store it.

[0069] (Specific product management file) 7(E) is an example of a specific product management file stored by the management device 10. As described above, in this embodiment, when the deposited product is a specific product (a product with dirt, fraying, etc.), the store (or dry cleaning factory) has the user check the current state of the product in order to prevent any trouble. In particular, in the case of speed deposit or locker deposit, etc., it is not possible to inspect the product together with the user when the product is deposited, so it is important in order to prevent any trouble to have the user check the current state first.

[0070] 7(E) stores the defect category (sometimes called the abnormal category), confirmation image, countermeasure, confirmation request date and time, confirmation date and time, etc. in association with the deposited product number (the deposited product number of the deposited product, which is actually a specific product, since the specific product management file manages the specific product), etc. Instead of or in addition to the management device 10, the POS terminal 20 may store the specific product management file.

[0071] The defect category is information that indicates the type of defect that requires confirmation by the user. 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 button that has come off.

[0072] The confirmation image is information (e.g., URI; Uniform Resource Identifier) ​​indicating the storage location of an image (image data such as a photograph or illustration; see FIG. 8) showing a defective part (location, degree, etc.). The confirmation image may be generated (e.g., by taking an image, scanning a handwritten template for each product, etc.) on the store side (e.g., the POS terminal 20) or may be generated in a dry cleaning factory (e.g., the factory terminal 40). The confirmation image generated as described above is transmitted from the management device 10 to the user terminal 50 as a request for current status confirmation. For example, the store may confirm whether the deposited product is a specific product, and if it is a specific product, the POS terminal 20 may generate a confirmation image, and the management device 10 may receive the confirmation image generated in the POS terminal 20 and transmit it to the user terminal 50. Also, for example, the dry cleaning factory may confirm whether the deposited product is a specific product, and if it is a specific product, the factory terminal 40 may generate a confirmation image, and the management device 10 may receive the confirmation image generated in the factory terminal 40 and transmit it to the user terminal 50.

[0073] In addition, the request for confirmation of the current situation may be made using the cleaning app (a confirmation image may be displayed on the screen of the cleaning app, etc.) or may be made using email (a confirmation image may be attached 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 the deposited product had a defect and input regarding a countermeasure, which will be described later. Next, the user terminal 50 transmits the input information from the user to the management device 10. The confirmation image shown in FIG. 8 is an illustrated image showing that the deposited product (shirt) has a stain on the right abdomen and that the button on the right sleeve is undone. The words "stain" and "button undone" are, for example, input by a store clerk or the like (text input, or selection from a plurality of candidate words, etc.). The image of the defect and the words can be enlarged on the user terminal 50 or the like, for example, by touch.

[0075] The method of dealing with the defect is the method of dealing with the defect specified (or selected) by the user. For example, if the defect is a stain (defect category "2"), it is whether or not to remove the stain. The confirmation request date and time is information indicating the date and time when the user was requested to confirm the current state of the specific product. The confirmation date and time is information indicating the date and time when the user completed the confirmation of the current state.

[0076] The configuration of the specific product management file is not limited to the configuration shown in FIG. 7(E). For example, the specific product management file shown in FIG. 7(E) stores one set of defect classification and countermeasure for one deposited product (deposited product number), but may store two or more sets of defect classification and countermeasure. For example, in the case of the shirt shown in FIG. 8, the confirmation request date and time, the confirmation image, the defect classification "2 (stain)" of the first defective part, the countermeasure for the first defective part, the confirmation date and time for the first defective part, the defect classification "5 (missing button)" of the second defective part, the countermeasure for the second defective part, the confirmation date and time for the second defective part, etc. may be stored in association with the deposited product number. The shirt shown in FIG. 8 is an example of a deposited product having multiple defective parts with different defect classifications, but the same applies to a deposited product having multiple defective parts with the same defect classification (for example, a shirt with two stains on the collar and arm). The specific product management file may store the date and time when the current status check was completed for each defective part as described above, or may store one date and time when the current status check was completed for all defective parts (for the last defective part). If the user can visually confirm all the defective parts of a certain deposited product, the confirmation image for the deposited product may be one (for example, one image that can accept operations such as rotation, such as a CAD image), or two or more images.

[0077] In addition, when a single deposited product has multiple defective parts (regardless of whether they are classified as defective or not), the user may specify (by touching, 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 FIG. 8, a selection screen with options for dealing with the stain may be displayed based on the user's touch on the stained area, and the selection of the method of dealing with the stain may be accepted from the user via the selection screen, and then a selection screen with options for dealing with the button coming off may be displayed based on the user's touch on the button coming off area, and the selection of the method of dealing with the button coming off may be accepted from the user via the selection screen. The fees for each of the options presented as options (e.g., stain removal fees, etc.) may be displayed for each option. In addition, in order to efficiently respond to individual inquiries from users to the store, etc. regarding a specific product, the deposited product 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.). In order to prevent miscommunication during inquiries and to improve efficiency, a number shorter than the deposited product number may be used. For example, an inquiry number (a number with a simpler system than the deposited product number) that can uniquely identify each specific product may be stored in the specific product management file, and the inquiry number may be displayed on the user terminal 50 (for example, as shown above).

[0078] As described above, the confirmation image is used to notify the customer that there is an abnormality (stains, fraying, etc.) in the deposited goods before the actual processing (washing, etc.) is performed at the dry cleaning factory, so that, for example, a customer is less likely to complain that an abnormality has occurred after depositing the goods. Also, by looking at the confirmation image, the customer can easily grasp the current situation and consider and specify how to deal with it.

[0079] Next, the process of product deposit by cleaning system 1 will be described with reference to Figures 9 to 12. In the description of Figures 9 to 12, it is assumed that user terminal 50 is a smartphone.

[0080] Fig. 9 is a flow chart showing an example of the operation when depositing goods. Specifically, the flow chart shown in Fig. 9 shows an example of the operation when depositing goods from a user (member) who visits a store (cleaning store) (i.e., normal store deposit). Note that the left side of Fig. 9 shows the operation of the user terminal 50, the center shows the operation of the POS terminal 20, and the right side shows the operation of the management device 10.

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

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

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

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

[0085] The horizontal row at the bottom of the membership card screen, which lists "Membership card," "Deposit slip," "Notice," "Coupon," and "Survey," indicate the type of screen currently being displayed. The same is true for the slip list screen shown in Fig. 11 and the bottom row of the slip detail screens shown in Figs. 12, 14, and 27. Note that if the screens are categorized into five types, "Membership card," "Deposit slip," "Notice," "Coupon," and "Survey," the slip list screen and slip detail screen are categorized as "Deposit slips," so they are referred to as "Deposit slips" both when the slip list screen is displayed (Fig. 11) and when the slip detail screen is displayed (Figs. 12, 14, and 27).

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

[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 a customer master file or the like. Step S15: The management device 10 transmits the customer information extracted in step S14 to the POS terminal 20.

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

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

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

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

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

[0093] Step S19: The POS terminal 20 displays the scheduled completion date. Specifically, the POS terminal 20 refers to the service basic file to obtain the number of days required for each deposited product, calculates the scheduled completion date for each deposited product based on the obtained number of days required, and displays the calculated scheduled completion date for each deposited product on the display unit 25. Note that the POS terminal 20 may display the latest scheduled completion date among the scheduled completion dates for each deposited product (i.e., the scheduled completion date when all of the deposited products are completed) on the display unit 25 instead of or in addition to the scheduled completion dates for each deposited product.

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

[0095] Step S20: The POS terminal 20 settles the payment. Specifically, the POS terminal 20 refers to the service basic file to obtain the fees for each deposited item, calculates the total fee by adding up the fees for each deposited item, and displays the total fee on the display unit 25 together with the fees for each deposited item. Next, the POS terminal 20 recognizes the deposit amount through the operation of the store clerk (inputting the number of items to be deposited according to the deposit amount), and calculates the amount of change from the total fee and the deposit amount. The POS terminal 20 then displays the deposit amount and the amount of change on the display unit 25 (payment settlement is complete). The store clerk checks the amount of change displayed on the display unit 25, takes out the change, and hands it to the user.

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

[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 will display the total charge etc. on the display unit 25, and then recognize the deposited amount through the operation of the store clerk (inserting the deposit into the coin slot of the automatic change dispenser), and calculate the change amount from the total charge and the deposited amount.The POS terminal 20 will then display the deposited amount and the change amount on the display unit 25, and dispense the change into the coin slot of the automatic change dispenser (closing the price).

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

[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 depositing the goods, by the operation of the store clerk. For example, the POS terminal 20 transmits transaction information to the management device 10, including a slip number, deposit date and time, store code, store clerk code, customer code, deposit category (specifically, deposit category "1 (normal store deposit)"), tag numbers of each deposited product, product type, processing type, and the like. The slip number is assigned (numbered) by the POS terminal 20. The store code and store clerk code are stored in the storage unit (RAM 23, hard disk 24) of the POS terminal 20. The store clerk code is stored in the storage unit of the POS terminal 20 by the operation of the store clerk (for example, inputting the number of items to be deposited using the store clerk code, reading the store clerk card using a card reader not shown, etc.).

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

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

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

[0103] Furthermore, information about the specific product (such as the reserved category of the deposited product information file and the defective category of the specific product management file) is stored in the deposited product information file (see FIG. 6) and the specific product management file, but if the store clerk has made an input about the 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 the specific product to the management device 10, the POS terminal 20 may further transmit information indicating the defective part (an image as shown in FIG. 8) to the management device 10 (this transmission is not necessary if the management device 10 prepares information indicating the defective part).

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

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

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

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

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

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

[0110] When the deposit slip icon G12 is operated (e.g., tapped) on the membership card screen shown in Fig. 10, the user's mobile phone 50 displays a slip list screen as shown in Fig. 11. The slip list screen displays a list of slip summaries for all stores.

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

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

[0113] In the slip details screen, "In custody" corresponds to the progress categories "1" to "5" in the custody product information file (FIG. 6) and indicates a state before delivery. "Delivered" corresponds to the progress category "9" in the custody product information file (FIG. 6) and indicates a state after delivery. In addition, the user terminal 50 may simply arrange the products in order of the expected completion date when there are multiple products, but when "In custody" and "Delivered" are mixed, the "In custody" product may be displayed with priority. In the example shown in FIG. 12, the "In custody" product (products in columns G34 and G35) is displayed above the "Delivered" product (products in column G36). In addition, the "Delivered" product (products in column G36) is displayed in gray. In addition, if the products are arranged in order of the expected completion date, the product in column G36 will be above the products in column G34 and column G35. The back icon G31 is a button for returning to the previous screen (the slip list screen (FIG. 11)).

[0114] According to the above, the user can get an overview of the entire transaction (list of vouchers) on the voucher list screen (Figure 11), and can check the details of each transaction (each voucher) on the voucher details screen (Figure 12).

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

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

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

[0118] Next, the process of product delivery by the cleaning system 1 will be described with reference to Fig. 13 to Fig. 16. In the description of Fig. 13 to Fig. 15, the user terminal 50 is assumed to be a smartphone. On the other hand, in the description of Fig. 16, the user terminal 50 does not necessarily have to be a portable terminal.

[0119] Fig. 13 is a flow chart showing an example of the operation when handing over a product. Specifically, the flow chart shown in Fig. 13 shows an example of the operation when handing over a product to a user who visits the store (i.e., normal store handover). Note that the left side of Fig. 13 shows the operation of the user terminal 50, the center shows the operation of the POS terminal 20, and the right side shows the operation of the management device 10. Fig. 14 is an example of a slip details screen (deposit slip screen, electronic deposit slip). Figs. 15 and 16 will be described later.

[0120] 13, step S30: The user terminal 50 displays a slip details screen on the display unit (touch panel). That is, the user terminal 50 displays a slip list screen when the deposit slip icon G12 is operated on the membership card screen, and the slip details screen of the desired slip is displayed when the field of the desired slip is operated (selected) on the slip list screen.

[0121] Step S31: The user terminal 50 accepts the selection of a product to be delivered on the slip details screen. Specifically, the user terminal 50 selects the product in the operated field by operating (e.g., tapping) the product field on the slip details screen. The user terminal 50 also highlights the product in the operated field (the field for the selected product). Note that the slip details screen shown in FIG. 14 shows that the top product field G33 has been selected. Note that even if the "delivered" product field (field G36 in FIG. 14) is operated, that product cannot be selected (it remains grayed out).

[0122] When the selection completion icon G32 is operated after one or more products are selected, the process proceeds to step S32 (that is, the selection of products to be delivered is completed).

[0123] The user terminal 50 is capable of selecting products in different slips at one time. For example, when the user operates the back icon G31 without operating the selection completion icon G32 after selecting one or more products on the slip list screen of a certain slip, the user terminal 50 displays the slip list screen. Next, in response to the user's operation, the user terminal 50 displays the slip details screen of another slip from the slip list screen, and when the selection completion icon G32 is operated after selecting one or more products on the slip details screen of the other slip, one or more products in the first slip and one or more products in the next slip are selected at one time.

[0124] Step S32: The user terminal 50 generates a barcode that can identify the user and the selected product (product desired for delivery) selected by the user. Specifically, the user terminal 50 generates a barcode that is a barcode of 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 the display unit.

[0125] Step S34: The POS terminal 20 reads the barcode displayed on the display unit of the user terminal 50 by an operation (motion) of the store clerk. Step S35: The POS terminal 20 identifies the user and the selected products selected by the user from the barcode read in step S34. Specifically, the POS terminal 20 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 products to be delivered by the printing unit 27. Specifically, the POS terminal 20 issues a list of products to be delivered on which the tag number of each product is printed. The POS terminal 20 may also issue a list of products to be delivered on which the customer code is printed in addition to the tag number of each product.

[0127] The store clerk then takes the list of products to be delivered issued in step S34 to the back room where the products are kept, and while checking the list of products to be delivered, searches for the products to be delivered and delivers them to the customer.

[0128] Step S37: The POS terminal 20 registers the completion of the delivery by the store clerk. The registration of the completion of the delivery may be made in any manner as long as it is possible to identify which of the deposited products has been delivered in the cleaning system 1. As an example, the POS terminal 20 may display a predetermined screen having confirmation buttons corresponding to each product that can be delivered (or each product to be delivered), and may accept the operation (touch) of the confirmation button on the predetermined screen by the store clerk.

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

[0130] Step S39: The management device 10 receives the transaction information from the POS terminal 20 at the time of delivery of the product. 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 category of the relevant product in the product information file (specifically, updates it to "9 (delivery completed)"), inputs the delivery completion date, and updates the update date and time. Furthermore, when delivery of all deposited products in the same slip has been completed (when the progress category for all products has become "9"), the management device 10 inputs 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 referencing the various files updated in step S40). Note that if the information displayed on the slip list screen does not change (for example, if the slip contains a product that has not been delivered, and the slip as a whole continues to display "In custody"), the management device 10 does not update the slip list screen.

[0132] Step S42: The management device 10 updates the slip 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 when delivery of all products in the slip details screen is completed, the slip details screen may be deleted (screen information of the slip may be deleted).

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

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

[0135] At the time of product delivery, the processing of steps S43 and S44 in FIG. 13 may not be performed, and in response to a user operation, 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 may be transmitted from the management device 10 to the user terminal 50.

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

[0137] In particular, the cleaning system 1 is effective when a customer who wishes to have some of the multiple deliverable products delivered visits the store. In other words, for example, in the technology of Patent Document 1, when a customer like the above visits the store, the customer needs to specify the product to be delivered by verbal instruction or to write down the tag number on a notepad to find the product to be delivered from the backyard, which significantly reduces business efficiency. On the other hand, in the cleaning system 1, if the customer presents a barcode on the user terminal 50, a list of the products to be delivered is output in the case where the customer wishes to have all the products delivered as well as when the customer wishes to have some of the products delivered, so that verbal instructions or notes from the user are not necessary, improving business efficiency.

[0138] Furthermore, in the cleaning system 1, when the product is handed over, the POS terminal 20 reads the barcode generated by the user terminal 50, as shown in the flowchart of Figure 13, thereby making it possible to confirm whether the user wishing to hand over the product has actually come to the store.

[0139] In addition, since the printing and issuing of the list of products desired for delivery and the confirmation of visit are achieved through a common process (the common process of generating barcodes and reading the generated barcodes), inefficient situations such as, for example, finding products based on the list of products desired for delivery only to find that the user to whom the products should be delivered has not actually visited the store are eliminated.

[0140] Fig. 15 is a flow chart showing an example of another operation when handing over a product. The flow chart shown in Fig. 15 replaces a part (dashed line A) of the flow chart shown in Fig. 13. Specifically, the flow chart shown in Fig. 13 (dashed line A part) uses a barcode to confirm the visit, whereas the flow chart shown in Fig. 15 (dashed line A part) uses a one-time password (for example, a character string of several digits, etc.).

[0141] Step S132 in Fig. 15: Following step S31 in Fig. 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 (for example, two digits). Note that a random number generator is implemented in the cleaning app installed in the user terminal 50.

[0142] Step S133: The user terminal 50 transmits information capable of identifying the user, information capable of identifying the selected products (products desired for delivery) selected by the user, and the OTP to the management device 10. Specifically, the user terminal 50 transmits to the management device 10 the customer code, the tag numbers of the products selected in step S31 (see FIG. 13), and the OTP generated in step S132. Step S134: The management device 10 receives and stores information capable of identifying the user, information capable of identifying the selected product (product desired for delivery) selected by the user from the user terminal 50. Specifically, the management device 10 receives and stores the customer code, the tag number of 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 the display unit. The user then notifies the store clerk of the OTP displayed on the display unit of the user terminal 50. The method of notifying the store clerk of the OTP may be, for example, a method of verbally telling the store clerk, or a method of showing the store clerk the OTP displayed on the display unit.

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

[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, but if they do not match, the process ends. Step S140: The management device 10 transmits to the POS terminal 20 information capable of identifying the selected products (products desired to be delivered) received in step S134 (specifically, the tag numbers of the products).

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

[0147] According to the flowchart shown in Fig. 15, the management device 10 collates the OTP acquired directly from the user terminal 50 with the OTP acquired via the POS terminal 20, and checks 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 acquires the OTP displayed on the display unit of the user terminal 50 by the operation of the store clerk, and since the process of step S136 is possible only because the user has actually come to the store (the process of step S136 is impossible if the user has not actually come to the store), the visit confirmation is performed reliably.

[0148] In addition, if the user selects a product to be delivered before coming to the store, the user terminal 50 transmits the OTP or the like to the management device 10, so that the management device 10 acquires the OTP from the user terminal 50 of the user before coming to the store. On the other hand, the management device 10 cannot acquire the OTP from the POS terminal 20 until the user arrives at the store. Therefore, if the user selects a product to be delivered before coming to the store, the management device 10 stops the process after acquiring the OTP or the like from the user terminal 50 (after executing the process of step S137). To deal with this, for example, in step S133, the user terminal 50 may transmit the OTP or the like to the management device 10 when there is an operation by the user, and may not transmit the OTP or the like to the management device 10 when there is no operation by the user. Also, for example, if the management device 10 does not execute the process of step S138 (does not receive the OTP from the POS terminal 20) within a predetermined period (for example, 5 minutes) after executing the process of step S134 (after receiving the OTP or the like from the user terminal 50), the process may be terminated.

[0149] Fig. 16 is a flowchart showing an example of another operation at the time of product delivery. The flowchart shown in Fig. 16 replaces a part (dashed line A) of the flowchart shown in Fig. 13. When a part of the flowchart shown in Fig. 13 is replaced with the flowchart shown in Fig. 16 (i.e., a flowchart combining the flowchart shown in Fig. 13 (excluding a part) and the flowchart shown in Fig. 16), the user terminal 50 does not need to be a portable terminal such as a smartphone (i.e., the user terminal 50 may be, for example, a smartphone or a personal computer installed at home, etc.).

[0150] 16, step S232: Following step S31 in Fig. 13, the user terminal 50 transmits information capable of identifying the user and information capable of identifying the selected products (products desired for delivery) selected by the user to the management device 10. Specifically, the user terminal 50 transmits the customer code and the tag numbers of the products selected in step S31 (see Fig. 13) to the management device 10. Step S233: The management device 10 receives information capable of identifying the user and information capable of identifying the selected product (product desired for delivery) selected by the user from the user terminal 50. 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 capable of identifying the user and information capable of identifying the selected product (product desired for delivery) selected by the user to the POS terminal 20. Specifically, the management device 10 transmits to the POS terminal 20 the customer code and the tag number of each product received in step S233. Step S235: The POS terminal 20 receives information capable of identifying the user and information capable of identifying the selected product (product desired for delivery) selected by the user from the management device 10. Specifically, the POS terminal 20 receives a customer code and a tag number of each product from the management device 10.

[0152] According to the flowchart shown in FIG. 16, a list of products to be delivered can be printed and issued before the customer arrives at the store (i.e., the products to be delivered can be found in the back room before the customer arrives), which can reduce the customer's waiting time at the store. Note that the store staff should organize the products found in the back room by putting them in a bag or other container to further reduce the customer's waiting time (it should also be clear immediately who the products are to be delivered to). Note that the example shown in FIG. 16 is a regular store delivery (delivery category "1") with reservation category "3 (reservation included (cleaning app)).

[0153] Fig. 17 is a flowchart showing an example of another operation (operation when using the store portable terminal 30) during product delivery. The flowchart shown in Fig. 17 replaces a part (dashed line B) of the flowchart shown in Fig. 13. The center of Fig. 17 shows the operation of the POS terminal 20, and the right side shows the operation of the store portable terminal 30.

[0154] Step S336 in FIG. 17: Following step S35 in FIG. 13 (or step S141 in FIG. 15, or step S235 in FIG. 16), the POS terminal 20 transmits information capable of identifying the selected products (specifically, the tag numbers of each product) to the store mobile terminal 30.

[0155] Step S337: The store portable terminal 30 receives from the POS terminal 20 information capable of identifying the selected products (specifically, the tag number of each product). Step S338: The store mobile terminal 30 displays on the display unit information that can identify the selected products received in step S337 (specifically, the tag numbers of each product). For example, the display unit may display information similar to the list of products to be delivered that is printed and issued by the POS terminal 20 (see S36 in FIG. 13).

[0156] According to the flowchart shown in FIG. 16, the display unit of the store portable terminal 30, which can be brought into the back room, can display information similar to the list of products to be delivered that is printed and issued by the POS terminal 20 in the cleaning system 1, thereby improving business efficiency, similar to that of the cleaning system 1.

[0157] (Promotional Activities) In the above embodiment, promotional activities may be conducted for users who meet certain conditions (for example, new users who registered as members in the previous month, users with rank S, users whose birthdays are coming up, etc.).

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

[0159] Instead of sending a message or e-mail from the management device 10 to the user terminal 50, a message or the like may be sent from the POS terminal 20 to the user terminal 50 (for example, the user terminal 50 of a user who has visited the store). In the mode of sending a message or the like from the POS terminal 20 to the user terminal 50 (similar to the mode of sending advertising information from the POS terminal 20 to the user terminal 50), the management device 10 may extract users who satisfy a specific condition (an additional condition may be that the user is a registered member at the store) and send the extraction result to the POS terminal 20, or the POS terminal 20 itself may access a customer master file stored in the management device 10 and extract users who satisfy a specific condition (an additional condition may be that the user is a registered member at the store).

[0160] Also, by sending advertising information from the administrator device 10, advertisements may be displayed on the user terminal 50 (for example, at least one of the membership card screen, slip list screen, and slip details screen). Advertisements on the user terminal 50 are exposed more frequently than advertisements on paper receipts, and therefore are more effective than paper receipts. The administrator device 10 may refer to various files (customer master file, customer record file, point management file, coupon sales record file, coupon usage record file, etc.) to determine whether or not to send advertising information for each user, or to send advertising information with different content for each user.

[0161] Instead of transmitting the advertising information from the management device 10 to the user terminal 50, the advertising information may be transmitted from the POS terminal 20 to the user terminal 50 (for example, the user terminal 50 of a user who visits the store).

[0162] In addition, when the administrator device 10 transmits advertising information to the user terminal 50 (when the POS terminal 20 does not transmit advertising information to the user terminal 50), the administrator device 10 may transmit to the POS terminal 20 information indicating what content of advertising information was transmitted (or will be transmitted) to which user. For example, after transmitting advertising information to a certain user (or when transmitting or before transmitting), the administrator device 10 may transmit the advertising information transmitted to the user (or information summarizing the advertising information transmitted to the user) to the POS terminal 20 of the store (e.g., a registered store where the user has registered as a member) that the user mainly uses. This allows the store clerk to speak to the user in conjunction with the advertisement, and makes it less likely that a situation will occur in which the user becomes aware of the advertisement for the first time due to an inquiry about the advertisement from the user.

[0163] (Bag deposit) In the above embodiment, it is possible to store products in bags (bagged storage). Specifically, the above-mentioned speed storage (deposit category "2") and locker storage (deposit category "4") correspond to bagged storage. Note that when bagged products are accepted at the collection location, collection storage (deposit category "3()") also corresponds to bagged storage.

[0164] The advantage of bagged storage is that the customer does not have to wait for the inspection of the products or payment. However, because the inspection is not done face-to-face with the customer when the products are deposited (the store clerk inspects the products by himself when taking them out of the bag), there is a risk of a misunderstanding between the customer and the store about the deposited products, and the customer may mistakenly remember and complain that the dry cleaning store has lost the products, even though they have not actually deposited them. If not much time has passed since the product was deposited, the above-mentioned customer mistake in memory is generally unlikely to occur, and even if it does occur, there is a high possibility that the mistake will be noticed.

[0165] Therefore, in the above embodiment, in the case of bagged deposit, when the store clerk inspects the products removed from the bag 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 of steps S23 to S26 in FIG. 9) are immediately performed in the management device 10. As a result, even in the case of bagged deposit where inspection is not performed when the products are deposited, the user can check the details of the deposited products on the slip details screen early (when the store clerk removes the products from the bag and inspects them), which makes it less likely that the user will misremember and reduces the risk of trouble.

[0166] (Settlement at the time of product delivery) In the case of the above-mentioned bagged delivery, payment is made when the goods are handed over, not when they are deposited. Therefore, the smooth and reliable collection of payment becomes an issue.

[0167] In the above embodiment, credit card payment, prepaid payment, and points payment are possible. Specifically, when the management device 10 sends the slip details screen etc. to the user terminal 50 (step S26 in FIG. 9), it sends a screen for selecting a payment method (credit card payment, prepaid payment, coupon payment, points payment) in addition to the slip details screen etc., and receives a response regarding the payment method from the user terminal 50. Note that the management device 10 may send a screen for selecting a payment method at a timing separate from the timing of sending the slip details screen etc.

[0168] Furthermore, cleaning at the dry cleaning factory may be started after the management device 10 receives a response regarding the payment method from the user terminal 50 (after the payment is actually completed using the payment method selected by the user). In other words, the management device 10 may be configured to transmit a screen for allowing the user to select a payment method at least before starting cleaning at the dry cleaning factory.

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

[0170] Note that a selection of multiple payment methods may be accepted in preparation for a situation in which payment cannot be made using the payment method selected by the user (for example, if the payment method selected by the user is prepaid payment, there may be insufficient available balance for prepaid payment or there may be no prepaid deposit in the first place, the same applies to coupon payment and point payment). Furthermore, when a selection of multiple payment methods is accepted, a specification of the priority of the payment methods may be accepted. Note that if the user specifies the priority as coupon payment → point payment → credit card payment, coupon payment may be executed, point payment may be executed for the shortfall that cannot be recovered by point payment, and credit card payment may be executed for the shortfall that cannot be recovered by coupon payment or point payment.

[0171] It should be noted that the user can check the available points on the user terminal 50 (for example, this is displayed on the membership card screen as shown in FIG. 10), but the user may also be able to check the available prepaid balance and the remaining number of coupons on the user terminal 50.

[0172] (Other product storage methods) The manner in which goods are received from a user, as exemplified in Fig. 9, is a manner in which the user and a store clerk meet face-to-face at a store (deposit category "1 (normal store deposit)"), but as described above, the manner in which goods are received from a user is not limited to a manner in which the user and a store clerk meet face-to-face at a store. As described above, there are also other manners in which bagged goods are received at a store (deposit category "2 (speed deposit)"), goods are received at a location other than a store (e.g., at home, a convenience store) (deposit category "3 (collection deposit)"), and bagged goods are received via a locker (deposit category "4 (locker deposit)").

[0173] (Other product delivery methods) 13, 15, 16, and 17 show examples of the manner in which the deposited goods are handed over to the user in a store in which the user and the store clerk meet face-to-face (handover category "1"), but as described above, the manner in which the deposited goods are handed over to the user is not limited to the manner in which the user and the store clerk meet face-to-face in a store. As described above, there is also delivery handover (handover category "2") in which the deposited goods are handed over at a location other than a store (such as a home or a convenience store), and locker handover (handover category "3") in which the deposited goods are handed over via a locker.

[0174] Delivery is made based on a delivery instruction (a request for delivery) from the user. Note that the user may omit the instruction to deliver the product each time by receiving an instruction to have all subsequent product deliveries be delivered by delivery. Based on the delivery instruction, the store staff delivers the product to the specified delivery location on the specified delivery date.

[0175] If a delivery / handover instruction is received when the customer visits the store, the reservation category "1 (reservation at store)" and handover category "2 (delivery / handover)" are stored in the electronic slip file based on the transaction information sent from the POS terminal 20 to the management device 10. If a delivery / handover instruction is received by phone, the reservation category "2 (reservation by phone)" and handover category "2 (delivery / handover)" are stored. If a delivery / handover instruction is received via a cleaning app, the reservation category "3 (reservation via app)" and handover category "2 (delivery / handover)" are stored.

[0176] Locker delivery (locker return) is performed based on the customer's locker delivery instruction (a request for locker delivery). Based on the locker delivery instruction, the store staff places the locker return item (the item that is being held and subject to locker delivery) in the locker on the day before the return date (the day of locker delivery) and locks it, and the customer retrieves the item from the locker on the return date without the help of the store staff.

[0177] If a locker delivery instruction is received when the customer visits the store, the reservation category "1 (reservation at store)" and delivery category "3 (locker delivery)" are stored in the electronic slip file based on the transaction information sent from the POS terminal 20 to the management device 10. If a locker delivery instruction is received by phone, the reservation category "2 (reservation by phone)" and delivery category "3 (locker delivery)" are stored. If a locker delivery instruction is received via the cleaning app, the reservation category "3 (reservation via app)" and delivery category "3 (locker delivery)" are stored.

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

[0179] Furthermore, if the user terminal 50 has a Bluetooth (registered trademark) function, the store may use Bluetooth to confirm the arrival of a user. For example, a Bluetooth-enabled device may be installed on the store side, and the store may identify the user terminal 50 connected to the Bluetooth-enabled device of the store via Bluetooth, thereby determining that the user who possesses the user terminal 50 has arrived at the store. A wireless LAN router or a leaky coaxial cable may be installed on the store side to similarly confirm the arrival of a user.

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

[0181] In the above embodiment, an example has been described in which the product to be delivered is selected on the user terminal 50, but the product may also be selected on other devices (for example, the POS terminal 20 or the store mobile terminal 30). In other words, the store clerk may select the product on behalf of the user without operating the user's user terminal 50. This allows the delivery of the deposited product smoothly even in cases where the user is unfamiliar with operating the cleaning app or is uncomfortable with the store clerk touching the user terminal 50.

[0182] In the above embodiment, the user terminal 50 displays both "in custody" and "delivered" slips on the slip list screen (see FIG. 11), but the user may operate the screen to display only "in custody" slips or only "delivered" slips. When only "in custody" slips are displayed, a message (a mark, etc.) indicating that only "in custody" slips are being displayed may be displayed, and when only "delivered" slips are displayed, a message indicating that only "delivered" slips are being displayed may be displayed.

[0183] In the above embodiment, the user terminal 50 displays both "in custody" and "delivered" products on the slip details screen (see FIG. 12, etc.), but the user may operate the screen to display only "in custody" products or only "delivered" products. When only "in custody" products are displayed, a message (a mark, etc.) indicating that only "in custody" products are being displayed may be displayed, and when only "delivered" products are displayed, a message indicating that only "delivered" products are being displayed may be displayed.

[0184] In addition, when providing a service of storing the cleaned goods for a long period of time (for example, within six months), restrictions may be placed on the selection operation of the goods to be delivered in relation to the goods to be stored or the goods in storage. For example, the goods to be stored or the goods in storage may be hidden or grayed out on the slip details screen so that the user cannot select them as the goods to be delivered. Alternatively, when a goods to be stored or the goods in storage is selected, a message may be displayed to the effect that the selected goods cannot be delivered because they are goods to be stored (or the goods in storage). In addition, when a goods to be stored or the goods in storage is selected, the user may be prompted to select whether to maintain the storage (i.e., to cancel and invalidate the selection of delivery) or to stop the storage and deliver the goods (i.e., to validate the selection of delivery), and if the selection of stopping the storage and delivering the goods is made, the goods may be delivered. According to the above, the user will not mistakenly (against his / her will) pick up the goods that he / she wants to be stored, and therefore it is possible to prevent a decrease in user satisfaction.

[0185] A comment (additional information) to the user may be input at the dry cleaning factory. For example, a comment such as "a new button was attached" or "some stains remain" may be input to the factory terminal 40 as a comment related to a specific product (a product with dirt, fraying, etc.), or a comment such as "there was something in the pocket" may be input unrelated to the specific product. The factory terminal 40 transmits the input information (comment) to the management device 10, which then transmits it to the user terminal 50. The management device 10 may transmit the comment to the POS terminal 20 instead of or in addition to the user terminal 50. The management device 10 may also store the comment acquired from the factory terminal 40 in, for example, a deposited product information file.

[0186] After cleaning, electronic tags are attached to the stored goods, and the location of each stored goods is obtained by detecting each electronic tag with a reader, and stored as the storage location of each stored goods (for example, storing the storage location in association with the tag number of each stored goods). When handing over the goods, the POS terminal 20 (or the store mobile terminal 30) may display the storage location of the goods to be handed over on the display unit (for example, displaying the storage location on an image of the floor layout of the back yard). This makes it easier for the store clerk to find the desired goods (the goods to be handed over) among the many stored goods in the back yard.

[0187] Furthermore, lamps (lamp operable by control of the POS terminal 20 or the store mobile terminal 30) are provided at each of a plurality of storage locations in the back yard, and the store clerk stores in the POS terminal 20 (or the store mobile terminal 30) the storage location of each of the deposited products that have been cleaned (for example, stores the storage location in association with the tag number of each of the deposited products). Then, when handing over the products, the POS terminal 20 (or the store mobile terminal 30) may turn on the lamp corresponding to the storage location of the product to be handed over.

[0188] Also, a camera provided in the store mobile terminal 30 may be used to perform image recognition to find desired products in the backyard. For example, when a store clerk receives products from a user (or when returning to the store after completing cleaning), the clerk takes an image of each product (for example, takes an image using the camera of the store mobile terminal 30) and stores the image of each product (for example, stores the captured image in association with the tag number of each product). When handing over the products, the clerk may aim the camera provided in the store mobile terminal 30 at the products stored in the backyard to obtain a through image, and determine whether the through image matches an image of the product desired to be handed over (an image corresponding to the tag number, etc. received from the POS terminal 20, etc.), and specify the product for which a through image matching the image of the product desired to be handed over is the product desired to be handed over.

[0189] FIG. 18 is an external perspective view showing an example of a locker. The lockers used in the cleaning system 1 are classified into lockers used when depositing products (i.e., lockers used at locker reception) and lockers used when handing over products (i.e., lockers used at locker return). FIG. 18(A) is an external perspective view of a dedicated locker 100 used only at locker reception (hereinafter, may be referred to as a dedicated locker). FIG. 18(B) is an external perspective view of a locker 200 used both at locker reception and locker return (hereinafter, may be referred to as a shared locker). FIG. 18(C) is an external perspective view of a dedicated locker 300 used only at locker return (hereinafter, may be referred to as a dedicated return locker).

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

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

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

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

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

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

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

[0197] Also, inside the store (back side), products that are inserted into the insertion opening from outside the store (front side) may be automatically collected (without preparation such as placing a basket with casters inside the collection section 102 or removing the basket with casters with products from inside the collection section 102). For example, the bottom of the collection section 102 may be inclined so that products inserted from outside the store naturally move inside the store, and the inside of the store may simply be an opening without a collection door. This makes it unnecessary to worry about the capacity (volume) of the collection section 102, since products inserted from outside the store automatically slide down into the opening inside the store (for example, users can insert products at any time, and store staff do not need to take out products from the collection section 102 as needed). It is only necessary to place a large basket with casters or the like under the opening to catch products that slide down from the opening.

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

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

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

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

[0202] In the case where the reception-only locker 100 can communicate with other devices (when it has a communication unit), for example, the management device 10 may generate information (PIN) to be input to the input operation unit 105 periodically (for example, every day) and transmit the generated information to the user terminal 50 and the reception-only locker 100. In other words, as a predetermined condition for unlocking the deposit slot door, the user may input information confirmed at the user terminal 50 (PIN generated in the management device 10) to the input operation unit 105, and the reception-only locker 100 may compare the information transmitted from the management device 10 with the information input to the input operation unit 105 and perform authentication. For example, the management device 10 may generate information (PIN) to be input to the input operation unit 105 periodically (for example, every day) and transmit the generated information to the POS terminal 20 and the reception-only locker 100. In other words, as a specified condition for unlocking the collection section door, a store clerk or the like may input information (such as a PIN number generated in the management device 10) confirmed on the POS terminal 20 (or the store's mobile terminal 30) into the input operation unit 105, and the reception-only locker 100 may compare the information sent from the management device 10 with the information input into the input operation unit 105 to perform authentication.

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

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

[0205] (Common locker) 18(B), the common locker 200 includes an insertion slot 201, a collection unit 202, a card insertion and ejection slot 203, a display unit 204, an input operation unit 205, a code recognition unit 206, an issue slot 207, a memory unit (not shown), a control unit (not shown) that controls the display on the display unit 204 and locking of a return slot door (described later), and multiple return slots (return units) 210. The insertion slot 201, collection unit 202, card insertion and ejection slot 203, display unit 204, input operation unit 205, code recognition unit 206, and issue slot 207 of the common locker 200 are the same as the insertion slot 101, collection unit 102, card insertion and ejection slot 103, display unit 104, input operation unit 105, code recognition unit 106, and issue slot 107 of the reception-only locker 100, and therefore description thereof will be omitted. The common locker 200 does not necessarily have to include all of the above-mentioned configurations. For example, it is possible to have either the input operation unit 205 or the code recognition unit 206, but not the other.

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

[0207] The common locker 200 shown in FIG. 18(B) has a total of 12 return slots 210 in two rows and six columns. In FIG. 18(B), the upper left return slot is designated by the reference number 210 as a representative of the 12 return slots. Each return slot is assigned a return slot number (sometimes called a "door number") as a management number. For example, specifically, as shown in FIG. 18(B), the return slot numbers are "H11" at the upper left, "H12" at the lower left, "H21" at the top of the second row from the left, "H22" at the bottom of the second row from the left, ..., "H61" at the upper right, and "H62" at the upper right. The return slot numbers of each return slot may be identified in the common locker 200 by attaching a sticker or the like indicating the return slot number to each return slot.

[0208] A door (hereinafter, referred to as the return door) is provided at each of the return slots 21. Each return slot door can be locked individually. When the return slot door is unlocked, a store employee or the like can store products (products to be returned to the user) in the return slot 21. When the return slot door is unlocked, the user can take out products from the return slot 21. On the other hand, when the return slot door is locked, the user cannot take out products from the return slot 21. When the return slot door is locked, the store employee or the like cannot store products in the return slot 21. The return slot door is normally locked, and is unlocked when a predetermined condition is met. The door is locked again after the products have been stored or removed.

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

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

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

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

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

[0214] (Lockers for returns only) The return-only locker 300 includes, for example, a card insertion / ejection slot (not shown), a display unit (not shown), an input operation unit (not shown), a code recognition unit (not shown), an issue slot (not shown), a memory unit (not shown), a control unit (not shown) that controls the display on the display unit and locking of the return slot door (described later) and the like, and multiple return slots (return units) 310. In the case of the return-only locker 300 shown in Fig. 18(C), the card insertion / ejection slot, display unit, input operation unit, code recognition unit, issue slot, and the like are located in area 301a in the upper left 301, but are not shown for convenience of the drawing.

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

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

[0217] Next, locker return will be described in detail with reference to Figures 19 to 43. In the following description, when there is no particular distinction between the common lockers 200 and the return-only lockers 300 that can be used for locker return, they will simply be referred to as return lockers.

[0218] FIG. 19 (as well as FIGS. 20 and 26) shows an example of various information stored in the cleaning system 1 (as well as the cleaning system 2).

[0219] (Locker management master file) Fig. 19(A) is an example of a locker management master file stored in the management device 10. The locker management master file is a file that stores information about return lockers (return-only lockers 300, common lockers 200). The locker management master file shown in Fig. 19(A) stores the installation location, number of return slots, etc. in association with the locker number. Note that if all return lockers in the cleaning system 1 have the same number of return slots (e.g., 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 for identifying each return locker in the cleaning system 1. The installation location is the location where the return locker is installed. It is possible to install two or more return lockers in one store, and it is also possible to install return lockers in locations other than stores. Examples of locations other than stores include supermarkets, convenience stores, specialty stores (clothing stores, pharmacies, etc.), shops inside (or near) train stations, and return lockers may be installed indoors or outdoors in apartment buildings (the same applies to the reception-only lockers 100). The number of return slots is the number of return slots that the return locker has.

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

[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 in the POS terminal 20 may be a file related to all return lockers, like the file stored in the management device 10, or may be a file related to the return lockers related to the store (the store where the POS terminal 20 is installed) as shown in Fig. 19(B).

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

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

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

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

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

[0228] Note that the POS terminal 20 may store a required number of ports definition file as shown in Fig. 19(C) instead of or in addition to the management device 10. Also, the POS terminal 20 may store a required number of ports definition file as shown in Fig. 19(D) or a volume number definition file as shown in Fig. 19(E) instead of or in addition to the management device 10.

[0229] (Required number of shares definition file) FIG. 20(A) is 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 about the reservation status (reservation state) of locker return for each return locker. The locker-specific reservation status file shown in FIG. 20(A) shows a 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. in association with the return date and return port number. Note that in FIG. 20(A), for convenience of explanation, a separate sheet (table) is shown for each return date, but the sheets may or may not be separated for each return date. The number of volumes used is the number of volumes used to deliver the product at the return port, that is, the volume of the product to be delivered at the return port. Note that the locker-specific reservation status file in FIG. 20(B) will be described later.

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

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

[0232] The future information in the locker reservation status file is a file showing the future reservation status of the locker (each return port), but since the lockers are used based on reservations, the past information in the locker reservation status file is also a file showing the past usage status of the locker. In other words, the management device 10 (similar to the case where the POS terminal 20 stores the locker reservation status file) or the memory unit of the management device 10 (a memory unit such as the hard disk 24 of the POS terminal 20) manages the past to future usage status of the lockers (each return port).

[0233] FIG. 21 is an explanatory diagram for explaining management of locker usage. FIG. 21 shows an example of information stored in a locker-specific reservation status file in a different format for ease of explanation (so that the number of available items for multiple return dates can be understood). In other words, the management device 10 (the same applies when the POS terminal 20 stores the locker-specific reservation status file) manages the locker usage as shown in FIG. 21. Note that the information on the return date "201X / 4 / 20" in FIG. 21 (information on the line indicated by the arrow) is based on the information on "201X / 4 / 20" in FIG. 20(A), but information on return dates other than the return date "201X / 4 / 20" in FIG. 21 is not shown in FIG. 20(A).

[0234] (Locker reservation available days) Fig. 22 is a flowchart showing an example of the operation relating to a method for identifying a reservation possible date (return possible date). The process of the flowchart shown in Fig. 22 starts when identifying a reservation possible date for locker return (when executing a process related to a reservation for locker return, for example, when displaying a scheduled locker return date calendar screen (described later)). Note that the flowchart shown in Fig. 22 shows the operation of a device (for example, the management device 10, the POS terminal 20, etc.) that identifies the reservation possible date.

[0235] Step S400 in FIG. 22: The required number of shares is calculated. Step S401: It is determined whether or not all the products to be returned to the locker have been completed. If the items are not yet finished (step S401; NO), the process proceeds to step S402. If the items are yet finished (step S401; YES), the process proceeds to step S405. Note that when this flowchart is executed at the time of product deposit, none of the items are yet finished, so the process proceeds to step S402.

[0236] Step S402: The latest scheduled completion date (the latest scheduled completion date among the scheduled completion dates of the products to be returned to the locker) is identified. Step S403: The latest scheduled completion date is set as the reference date. Then, the process proceeds to step S406. It should be noted that the reference date in steps S403, S405, and S406 is the earliest possible reservation date when the locker usage status is not taken into consideration (when ignored). Step S405: Tomorrow is set as the reference date, and the process proceeds to step S406.

[0237] Step S406: Determine whether the number of vacant seats on each day after the base date is equal to or greater than the required number. If the number of vacant seats is equal to or greater than the required number, reservations are possible, so the process of step S406 is to determine whether the day is available for reservations. In other words, the process of step S406 calculates the available days for reservations from the number of vacant seats on each day after the base date and the required number of seats. Step S407: Output the judgment result. For example, the management device 10 (POS terminal 20) may display the judgment result. Also, for example, the management device 10 (POS terminal 20) may print the judgment result. Also, for example, the management device 10 may transmit information indicating the judgment result to the POS terminal 20 (or the user terminal 50) (the POS 20 (or the user terminal 50) may display the judgment result). Also, for example, the management device 10 (POS terminal 20) may print the judgment result. Also, for example, the POS terminal 20 may transmit information indicating the judgment result to the user terminal 50 (the user terminal 50 may display the judgment result). Then, the flowchart of FIG. 22 ends.

[0238] FIG. 23 is an explanatory diagram for explaining a method for identifying a reservation possible date. Specifically, FIG. 23(A) to FIG. 23(C) are examples of reservation possible dates when three products (products in columns G33, G34, and G35) in "in storage" shown in FIG. 12 are returned to a locker, obtained by using the required number of units definition file in FIG. 19(C) (examples obtained based on the number of items to be returned). FIG. 23(D) to FIG. 23(F) are examples of reservation possible dates when three products (products in columns G33, G34, and G35) in "in storage" shown in FIG. 12 are returned to a locker, obtained by using the required number of units definition file in FIG. 19(D) and the volume file in FIG. 19(E) (examples obtained based on the number of volumes to be returned). It is assumed that today is "201X / 4 / 19".

[0239] (Example based on number of returned items) The top row (base of the arrow) of Fig. 23(A) shows information (scheduled completion date) regarding the items to be delivered by locker return (the three items "in custody" shown in Fig. 12) (Fig. 7(D)). As the number of items to be returned is three as shown in the top row of Fig. 23(A), in the process of step S400 of Fig. 22, the required number is calculated as 1 as shown in the bottom row (tip of the arrow) of Fig. 23(A) (see Fig. 19(C)).

[0240] Next, since the scheduled completion dates for the three products are "4 / 11 / 201X," "4 / 13 / 201X," and "4 / 16 / 201X," and today is "4 / 19 / 201X," it is determined that all products have been completed (step S401; YES), and tomorrow's date, "4 / 19 / 201X," is set as the base date (step S405).

[0241] Next, it is determined whether the number of available spaces for each day after "201X / 4 / 19" is equal to or greater than the required number (1) (step S406), and for example, as shown in FIG. 23(B), the days for which the number of available spaces is equal to or greater than the required number (1) are output (displayed, etc.) as available reservation dates (step S407). In FIG. 23(B), the number of available spaces for each available reservation date is also output (displayed, etc.). Note that in the processing of step S407, the availability of reservations, etc. for each day after the base date may be output (displayed, etc.) as shown in FIG. 23(C).

[0242] (Example based on number of returned volumes) The upper part of Fig. 23(D) (base of the arrow) shows information (number of volumes, expected completion date) regarding the products to be delivered when returned to the locker (the three products "in custody" shown in Fig. 12) (Figs. 19(E), 7(D)). As the total number of volumes is 6 as shown in the upper part of Fig. 23, in the processing of step S400 of Fig. 22, the required number of units is calculated as 2 as shown in the lower part of Fig. 23(D) (tip of the arrow) (see Fig. 19(D)).

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

[0244] Next, it is determined whether the number of available spaces for each day after "201X / 4 / 19" is equal to or greater than the required number of 2 (step S406), and for example, as shown in FIG. 23(E), the days for which the number of available spaces is equal to or greater than the required number of 2 are output (displayed, etc.) as available reservation dates (step S407). In FIG. 23(E), the number of available spaces for each available reservation date is also output (displayed, etc.). Note that in the processing of step S407, the availability of reservations, etc. for each day after the base date may be output (displayed, etc.) as shown in FIG. 23(F).

[0245] As Fig. 23(C) and Fig. 23(F) show whether reservation is possible for each day as described above, Fig. 22 is a flowchart showing the operation of identifying reservation possible days (return possible days) and also a flowchart showing the operation of determining whether reservation is possible for each day (or a specific day). In other words, the management device 10, the POS terminal 20, etc. are devices that identify reservation possible days and also devices that determine whether reservation is possible.

[0246] Note that the output format shown in Figure 23 (Figure 23(B), Figure 23(C), Figure 23(E), Figure 23(F)) is just one example, and the reservation available dates may be displayed, for example, on the locker return date calendar screen described below.

[0247] (Locker return date calendar screen) Fig. 24 (similar to Fig. 25) is an example of a locker return date calendar screen (locker return reservation screen). The locker return 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. Note that if the management device 10 does not have an operation unit or a display unit (for example, in the case of a server installed in a data center), the locker return date calendar screen (as well as a locker return reservation confirmation screen described later) may be displayed on the display unit of another device (personal computer, etc.) 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), the user terminal 50 may display a screen that allows the user to select whether or not to return the item to a locker, and when the user selects to return the item to a locker, a locker return scheduled date calendar screen as shown in FIG 24 may be displayed on the display unit, although this has not been described above. Note that if a locker cannot be identified from the store (for example, if two or more return lockers are associated with one store), the user may be allowed to specify a return locker.

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

[0250] In the case of the locker return date calendar screen displayed by the user terminal 50, information is automatically entered into the locker information column and customer information column, but in the case of the locker return date calendar screen displayed by the POS terminal 20 or the management device 10, information may be entered into the locker information column and customer information column by a store clerk or the like.

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

[0252] The current date and time column (symbol A) displays the current date and time. The locker information column (symbol B) displays the locker number of the return locker whose information is displayed on the locker return date calendar screen. The customer information column (symbol C) displays the customer code of the user (the user making the reservation for the locker return). The number of items to be returned to the locker column (symbol D) displays the number of items that the user wishes to have delivered when returning to the locker. The number of return slots required column (symbol F) displays the number of return slots required when the user returns to the locker. The adjustment column (symbol G) displays a button to increase or decrease (adjust) the number of return slots required, as well as the range of adjustment. The calendar column (symbol H) displays the number of return slots (free return slots) available (available for reservation) on each day. The areas for each date in the calendar column are buttons.

[0253] Some of the information displayed in Fig. 24 will be explained. In the explanation of Fig. 24, it is assumed that the user (customer code "KB9876") has selected three items on the slip details screen (Fig. 14) that he / she wishes to have delivered when returning the items to the locker: a shirt (tag number "TG01-1372"), a sweater (tag number "TG01-1374"), and a down jacket (tag number "TG01-1375"). The required number of items will be calculated taking into account the volume number.

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

[0255] The "2" in the Required Number of Return Units field (symbol F) indicates the number of return units based on the number of return volumes. That is, it is displayed based on the product type file (Fig. 7(A)), the required number of units definition file (Fig. 19(D)), the number of volumes definition file (Fig. 19(E)), etc. That is, the number of volumes of a shirt (product type "SY01") is "1", the number of volumes of a sweater (product type "SY02") is "2", the number of volumes of a down jacket (product type "SY03") is "3", and the total number of volumes (number of return volumes) is "6". Since the required number of units corresponding to the return volume number "6" is "2", "2" is displayed in the Required Number of Return Units field.

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

[0257] The "4" for 4 / 20 in the calendar column (symbol H) is displayed based on the number of vacant slots "4" in the locker reservation status file (Fig. 20(A)). In the locker return date calendar screen shown in Fig. 24, the button color (background color) for each date is different depending on whether the date is a reservation-available day (a day from tomorrow onwards (excluding store holidays) with the number of vacant slots equal to or greater than the required number of return slots) or a reservation-unavailable day (a day that is not a reservation-available day). In Fig. 24, the reservation-available days (4 / 20, 4 / 23, 4 / 24, 4 / 27, 4 / 28, ...) are shown in solid color (white), and the reservation-unavailable days (4 / 16-4 / 19, 4 / 21, 4 / 22, 4 / 25, 4 / 26, 4 / 30, ...) are shown in dots.

[0258] Fig. 20(B) shows the contents of the updated locker reservation status file that is updated after the button "4 / 20" is operated (e.g., touched) on the locker scheduled return date calendar screen in Fig. 24. Fig. 25 is an example of the locker scheduled return date calendar screen that is displayed after the button "4 / 20" is operated on the locker scheduled return date calendar screen in Fig. 24.

[0259] Fig. 26 shows the contents of the stored product information file after updating, which is updated after operating (e.g., touching) the button "4 / 20" on the locker scheduled return date calendar screen in Fig. 24. Fig. 27 is an example of a slip details screen that is displayed after operating the button "4 / 20" on the locker scheduled return date calendar screen in Fig. 24.

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

[0261] (How to determine the return port) As a method for determining which return port to reserve from among the available return ports, for example, the return port may be determined based on the past usage status (past usage state; specifically, past determination results) of each return port. Specifically, the return port may be determined so that a specific return port is not used frequently (so that each return port is used evenly). By using each return port evenly, a situation in which deterioration or damage progresses at a specific return port is unlikely to occur. Note that the past usage status of each return port can be grasped, for example, by continuing to store the locker-specific reservation status file (FIG. 20) for a certain period of time without immediately deleting it even if the return date has passed. In other words, the past usage status of each return port may be grasped by referring to a locker-specific reservation status file (past locker-specific reservation status file) whose return date has passed.

[0262] Also, instead of or in addition to the above method, the return ports may be determined based on the relative positions (adjacency) of the respective return ports. Specifically, when the same user reserves two or more return ports (when the user requires two or more return ports), adjacent return ports may be determined so that the user can retrieve the deposited items from adjacent return ports. By determining adjacent return ports, the user does not have to move to a return locker located far away.

[0263] Fig. 28 is an example of a file used to determine whether return ports are adjacent to each other. Whether or not each return port is adjacent to another return port may be determined by storing, for example, a file (e.g., Fig. 28(A)) showing other return ports adjacent to a certain return port, or a file (e.g., Fig. 28(B)) showing patterns (combinations) of adjacent return ports. The above files (files in Figs. 28(A) and 28(B)) are stored, for example, by a device that determines the return ports (e.g., the management device 10, the POS terminal 20, etc.).

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

[0265] Fig. 28(B) is a file showing a pattern of adjacent return slots. Specifically, the file on the left side of Fig. 28(B) is a file showing a pattern in which two return slots are adjacent in the common locker 200. The file on the right side of Fig. 28(B) is a file showing a pattern in which three return slots are adjacent in the common locker 200. Files showing patterns in which four or more return slots are adjacent in the common locker 200 are not shown.

[0266] According to the file shown in FIG. 28(B), for example, the combination of three return ports with return port numbers "H11", "H21", and "H22" exists in the file on the right side of FIG. 28(B) (second from the top), so it can be seen that these three return ports form three adjacent return port groups. Also, the combination of three return ports with return port numbers "H11", "H21", and "H32" does not exist in the file on the right side of FIG. 28(B), so it can be seen that these three return ports do not form three adjacent return port groups. However, the combination of two return ports with return port numbers "H11" and "H21" exists in the file on the left side of FIG. 28(B) (second from the top), so it can be seen that these two return ports form two adjacent return port groups.

[0267] In the examples shown in Figures 28(A) and (B), adjacent relationships are defined as relationships arranged vertically or horizontally, but adjacent relationships may also be defined as relationships arranged diagonally in addition to vertically or vertically. Specifically, in the file of Figure 28(A), for example, three return ports with return port numbers "H12", "H21", and "H22" may be defined as return ports adjacent to the return port with return port number "H11", and in the file on the left side of Figure 28(B), a combination of two return ports with return port numbers "H11" and "H22" may be added as a pattern in which two return ports are adjacent to each other.

[0268] Fig. 29 is a flowchart showing an example of a method for determining a return port. The process of the flowchart shown in Fig. 29 is started by performing a reservation operation (operation of a date button in the calendar column (symbol H)) on the locker return date calendar screen. The flowchart shown in Fig. 29 (as well as the flowchart shown in Fig. 30) shows the operation of a device (e.g., 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 slots (number of return slots that can be used) is greater than the required number (required number of return slots). In other words, determine whether there is a surplus of available slots. If the number of available return slots is not greater than the required number (step S500; NO), proceed to step S501. If the number of available return slots is greater than the required number (step S500; YES), proceed to step S502.

[0270] Step S501: Determine all available return slots (required number). In other words, since there are not enough available slots to select a return slot, reserve all available return slots. Then, the flow chart in FIG. 29 ends.

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

[0272] Step S503: Determine the least used one. In other words, since at most one return port is determined, there is no need to check for adjacent vacancies (group of adjacent vacant return ports), and reserve the least used one return port from among all available return ports so that each return port is used evenly. Then, the flow chart in FIG. 29 ends.

[0273] In determining step S503, there may be multiple candidates based on usage, and it may not be possible to identify the one return port to be determined (reserved). For example, if 8 of the 12 return ports were not used the day before yesterday but were used the day before, and the remaining 4 return ports were not used the day before yesterday but were used the day before, there will be 4 return ports that are candidates for determining the required number of 1 return port (because 4 return ports were used the day before yesterday), and it is not possible to identify the required number of 1 return port from the 4 candidates based only on usage.

[0274] In the above-mentioned case, one return port may be randomly selected from among the multiple candidates using a random number or the like. Also, one return port may be selected from among the multiple candidates based on a predetermined rule. For example, as a predetermined rule, one return port with the highest priority among the multiple candidates may be selected according to a predetermined priority order (for example, the order of return port numbers "H11" → "H12" → "H21" → "H22" → "H31" → "H32", ..., "H61" → "H62", with the left column being prioritized and the upper row being prioritized in the same column). Also, as a predetermined rule, one return port may be selected from among the multiple candidates so that the number of adjacent vacancies (described later) is as large as possible after the selection. Also, these may be combined to select the return port.

[0275] In step S503, since at most one return port is determined, there is no need to check whether there is an adjacent vacant port, and the least used return port is determined (reserved) from among all available return ports. However, it is also possible to check whether there is an adjacent vacant port and determine one return port. Specifically, when determining in step S503, if there are an empty return port that constitutes an adjacent vacant port and an empty return port that does not constitute an adjacent vacant port, one return port may be determined from among the empty return ports that do not constitute an adjacent vacant port. In other words, the empty return port that constitutes an adjacent vacant port may be reserved for other reservations (subsequent reservations).

[0276] Step S504: Determine whether there is an adjacent vacant lot. In other words, since multiple return slots will be determined, check whether there is an adjacent vacant lot. If there is no adjacent vacant lot (Step S504; NO), proceed to Step S505. If there is an adjacent vacant lot (Step S504; YES), proceed to Step S506.

[0277] Step S505: Determine the required number of return slots in the order of unused slots. In other words, since there are no adjacent slots, reserve the required number of return slots in the order of unused slots so that each return slot is used evenly among all the available slots. Then, the flow chart in FIG. 29 ends.

[0278] In addition, when determining in step S505, there may be cases where a plurality of candidates exist and the return outlet to be determined (reserved) cannot be identified based on the determination based on the usage status. For example, if the required number is three, and eight of the total 12 return outlets were not used the day before yesterday but were used the day before, and the remaining four return outlets were not used the day before yesterday but were used the day before yesterday, then there will be four return outlets that are candidates for determining the required number of three return outlets (because there were four return outlets used the day before yesterday), and the required number of three cannot be identified from the four candidates based on the determination based on the usage status alone. Also, for example, if the usage status is the same as above and the required number is five, after determining four return outlets (the four return outlets used the day before yesterday) out of the required number of five return outlets, there will be eight return outlets that are candidates for determining the remaining one return outlet out of the required number of five return outlets (because there were eight return outlets used the day before yesterday), and the required number of one return outlet cannot be identified from the eight candidates based on the determination based on the usage status alone.

[0279] In the above-mentioned case, the return port may be randomly selected from among multiple candidates using random numbers or the like. Also, the return port may be selected from among multiple candidates based on a predetermined rule. For example, as the predetermined rule, the return port may be selected according to a predetermined priority order (for example, the left column is prioritized, and in the same column, the upper rows are prioritized, in the order of return port numbers "H11" → "H12" → "H21" → "H22" → "H31" → "H32", ..., "H61" → "H62").

[0280] Step S506: Determine whether the number of adjacent vacancies is equal to or greater than the required number. The number of adjacent vacancies is the number of vacant return ports that make up adjacent vacancies (a group of adjacent vacant return ports). If the number of adjacent vacancies is less than the required number (Step S506; NO), proceed to Step S507. If the number of adjacent vacancies is equal to or greater than the required number (Step S506; YES), proceed to Step S508. If there are multiple adjacent vacancies, determine whether the maximum number of adjacent vacancies among the respective adjacent vacancies is equal to or greater than the required number.

[0281] Step S507: The required number is determined, with priority given to adjacent spaces, and the flow chart in FIG. 29 ends.

[0282] Below, the processing of step S507 will be explained separately for a case where there is only one adjacent vacant space (the number of adjacent vacant spaces is less than the required number) and a case where there are multiple adjacent vacant spaces (the number of adjacent vacant spaces is less than the required number).

[0283] If there is only one adjacent vacant lot (adjacent vacant lot with less than the required number), for example, for the number of adjacent vacant lots among the required number, all return ports in an empty state that make up the adjacent vacant lot may be determined regardless of their usage status, and for the remaining return ports, a return port may be determined in the order of least used from among all available return ports (all return ports in an empty state that do not make up an adjacent vacant lot). In addition, in determining the remaining return ports, if there are multiple candidates based on the usage status, a return port may be determined randomly from among the multiple candidates using random numbers, as in the determination in step S505. Also, a return port may be determined from among the multiple candidates based on a predetermined rule.

[0284] In the case where there are multiple adjacent vacancies (adjacent vacancies with a number of adjacent vacancies less than the required number), for example, the return port may be determined by giving priority to the adjacent vacancies with a larger number of adjacent vacancies regardless of the usage status. For example, if the required number is four and there is one adjacent vacancy with a number of adjacent vacancies of two and one adjacent vacancy with a number of adjacent vacancies of three, all the empty return ports (three) that make up the adjacent vacancies with a number of adjacent vacancies of three may be determined, and the least used return port may be determined from the empty return ports (two) that make up the adjacent vacancies with a number of adjacent vacancies of two. In addition, if the usage status of the empty return ports (two) that make up the adjacent vacancies with a number of adjacent vacancies of two are the same, one return port may be randomly determined from the two using random numbers, or one return port may be determined from the two based on a predetermined rule. The same applies to the case where a return port is determined by giving priority to the adjacent vacancies with a smaller number of adjacent vacancies, as described below.

[0285] If there are multiple adjacent vacancies (adjacent vacancies with fewer adjacent vacancies than the required number), instead of the above, the return outlet may be determined by prioritizing the adjacent vacancies with the smaller number of adjacent vacancies regardless of usage. For example, if the required number is 4 and there is one adjacent vacancy with 2 adjacent vacancies and one adjacent vacancy with 3 adjacent vacancies, all of the empty return outlets (2 outlets) that make up the adjacent vacancies with 2 adjacent vacancies may be determined, and then from among the empty return outlets (3 outlets) that make up the adjacent vacancies with 3 adjacent vacancies, the two least recently used return outlets may be determined.

[0286] In addition, when determining a return port by giving priority to adjacent vacant spaces with a larger number of adjacent vacant spaces as described above, or when determining a return port by giving priority to adjacent vacant spaces with a smaller number of adjacent vacant spaces as described above, if there are multiple adjacent vacant spaces with the same number of adjacent vacant spaces, one of the adjacent vacant spaces may be determined based on usage status, a random number, or a predetermined rule, and a return port may be selected from among the empty return ports that make up the determined adjacent vacant spaces.

[0287] Also, if the required number is greater than the total number of adjacent vacancies of all adjacent vacancies, for the number of adjacent vacancies (the number of adjacent vacancies of all adjacent vacancies) among the required number, all return ports in an empty state that constitute the adjacent vacancies (all adjacent vacancies) may be determined, and for the remaining, a return port may be determined in the order of least used from among all available return ports (all return ports in an empty state that do not constitute adjacent vacancies). In addition, in determining the remaining return ports, if there are multiple candidates based on the judgment based on the usage status, a return port may be determined randomly from among the multiple candidates using random numbers, as in the determination in step S505. Also, a return port may be determined from among the multiple candidates based on a predetermined rule.

[0288] Step S508: The required number of adjacent spaces is determined, and the flow chart in FIG. 29 ends.

[0289] The process of step S508 will be described below separately for a case where there are adjacent vacancies with a number equal to the required number, and a case where there are no adjacent vacancies with a number equal to the required number.

[0290] If there are adjacent vacancies with the same number of adjacent vacancies as the required number, all return ports in the vacant state that constitute the adjacent vacancies with the same number of adjacent vacancies as the required number may be determined. For example, if the required number is 3 and there is one adjacent vacancy with 2 adjacent vacancies, one adjacent vacancy with 3 adjacent vacancies, and one adjacent vacancy with 4 adjacent vacancies, all return ports in the vacant state that constitute the adjacent vacancies with 3 adjacent vacancies (3 ports) may be determined. If there are multiple adjacent vacancies with the same number of adjacent vacancies as the required number, any one adjacent vacancy (adjacent vacancies with the same number of adjacent vacancies as the required number) may be determined based on the usage situation, random numbers, or a predetermined rule, and all return ports in the vacant state that constitute the determined adjacent vacancies may be determined. For example, if the required number is 3 and there is one adjacent vacancy with 2 adjacent vacancies, two adjacent vacancies with 3 adjacent vacancies, and one adjacent vacancy with 4 adjacent vacancies, any one adjacent vacancy with 3 adjacent vacancies may be determined based on the usage situation, random numbers, or a predetermined rule, and all return ports in the vacant state that constitute the determined adjacent vacancies (3 ports) may be determined.

[0291] If there are no adjacent vacancies with the same number of adjacent vacancies as the required number, the required number of return ports may be determined in the order of least used from among the vacant return ports that make up the adjacent vacancies with the minimum number of adjacent vacancies exceeding the required number. For example, if the required number is three and there is one adjacent vacancy with two adjacent vacancies, one adjacent vacancy with four adjacent vacancies, and one adjacent vacancy with five adjacent vacancies, three return ports may be determined in the order of least used from among the vacant return ports (four) that make up the adjacent vacancies with four adjacent vacancies. If there are multiple adjacent vacancies with the minimum number of adjacent vacancies exceeding the required number, one of the adjacent vacancies (the adjacent vacancy with the minimum number of adjacent vacancies exceeding the required number) may be determined based on the usage status, random numbers, or a predetermined rule, and the required number of return ports may be determined in the order of least used from among the vacant return ports that make up the determined adjacent vacancies. For example, if the required number is three and there is one adjacent vacancy with two adjacent vacancies, two adjacent vacancies with four adjacent vacancies, and one adjacent vacancy with five adjacent vacancies, one of the adjacent vacancies with four adjacent vacancies may be determined based on usage status, random numbers, or predetermined rules, and three return ports that are least recently used may be selected from the four empty return ports that make up the determined adjacent vacancies.

[0292] When determining the return ports in the order of least used (in the above example, when determining the three least used return ports from the four vacant return ports that make up the four adjacent vacancies), if there are multiple candidates based on the usage status, the return port may be selected randomly from the multiple candidates using a random number or the like. Also, the return port may be selected from the multiple candidates based on a predetermined rule.

[0293] According to the flowchart in Figure 29, when there are vacant spaces available relative to the number of reservations (required number) (step S500 (YES)), for a user using multiple return exits (step S502 (YES)), if there is an adjacent vacant space (step S504 (YES)), the adjacent return exit will be reserved with priority.

[0294] As described above, the process of the flowchart shown in Fig. 29 is a mode in which a return port is determined individually for each reservation (a return port is determined each time a reservation is made), but the mode of determining the return port is not limited to this. For example, a return port may be determined collectively for one or more reservations made within a certain period (a return port is determined collectively after the end of the period).

[0295] Fig. 30 is a flowchart showing another example of the method for determining the return port. A device for determining the return port (e.g., the management device 10, the POS terminal 20, etc.) may execute the process of the flowchart shown in Fig. 30 instead of the process of the flowchart shown in Fig. 29. The process of the flowchart shown in Fig. 30 starts, for example, at a predetermined time (e.g., 11:00 p.m. on the day before the reservation date).

[0296] Step S516 in Fig. 30: Determine whether all reservations have been extracted. That is, in the following process (steps S518 to S528), a return port is determined for each reservation, and a determination is made as to whether a return port has been determined for all reservations. If all reservations have been extracted (step S516; YES), the flowchart in Fig. 30 ends. If all reservations have not been extracted (step S516; NO), proceed to step S518.

[0297] Step S518: Extract one reservation with the largest required quantity from among the pending reservations. In other words, control is performed so that the return port is determined in order of the reservation (user) that uses the most return port. Note that if there are multiple reservations with the same required quantity, they may be extracted in the order of reservation (earliest reservation time), for example.

[0298] After executing step S518, the process proceeds to step S520. Note that steps S520 to S528 in Fig. 30 are similar to steps S500 to S508 in Fig. 29, and therefore will not be described. After executing any one of steps S521, S523, S525, S527, and S528 in Fig. 30, the process returns to step S516. Then, as described above, the flow chart in Fig. 30 ends when return ports are determined for all reservations.

[0299] As described above, according to the flowchart in FIG. 30, the return exit is determined in order of the reservation with the greatest number of required items (step S518), so that adjacent return exits are more likely to be reserved for a user who uses multiple return exits.

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

[0301] Figure 31(B) shows how each return outlet shown in Figure 31(A) is determined by a method of determining a return outlet for each reservation based on usage (the determination method in the flowchart shown in Figure 29). Figure 31(C) shows how each return outlet shown in Figure 31(A) is determined by a method of determining a return outlet for multiple reservations collectively based on usage (the determination method in the flowchart shown in Figure 30). In Figure 31(B) (as well as Figures 31(C), 32(B), and 32(C)), the return outlet numbers of each return outlet are omitted.

[0302] (Method of determining the return port for each reservation based on the usage status / Figure 31 (B)) In the explanation of FIG. 31(B), it is assumed that a total of four return slot reservation requests are made on the same day in the following order. 1st: Reservation by user A with 1 required return slot (required number) 2nd Reservation: Reservation by User B with the required number of return slots (required number) being 1 3rd Reservation: Reservation for user c with the required number of return slots (required number) of 3 4th: Reservation for user d with a required number of return slots (required number) of 5 That is, in this determination method, the return port is determined in the order of reservations (reservation by user a → reservation by user b → reservation by user c → reservation by user d).

[0303] When the first reservation (user a) is made, as shown in the top row of FIG. 31(B), the return port with return port number "H41" is determined for the reservation of user a. In other words, the required number for user a is 1, and the reserved number at the time of reservation for user a is 0, i.e., the available number is 12, so the available number is greater than the required number (step S500 (YES) in FIG. 29), and the required number is 1 (step S502 (NO)), so the least used return port among all available return ports is reserved (step S503). The least used return port among all 12 available return ports (return port numbers "H11" to "H62") can be identified as the return port with return port number "H41" that was used three days ago. Therefore, the return port with return port number "H41" is determined.

[0304] After that, when a second reservation (by user b) is made, the return slot with return slot number "H61" is determined for the reservation by user b, as shown in the second row of FIG. 31(B). In other words, the required number for user b is 1, and the reserved number at the time of user b's reservation is 1, i.e., the available number is 11, so the available number is greater than the required number (step S500(YES)), and the required number is 1 (step S502(NO)), so the least used return slot among all available return slots is reserved (step S503). The least used return slots among all 11 available return slots (the 11 return slots other than return slot number "H41") are the five 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 return slot based on the usage status alone. Therefore, the return port with the return port number "H61" is selected so that the number of adjacent vacancies after the selection will be as large as possible (here, the number of adjacent vacancies after the selection will be as large as possible for the return port used two days ago). It is also possible to select the return port with the return port number "H62", but here the upper row is selected with priority.

[0305] After that, when a third reservation (user c) is made, three return ports with return port numbers "H31", "H32", and "H42" are determined for the reservation of user c, as shown in the third row of FIG. 31(B). In other words, the required number of user c is 3, and the number of reserved items at the time of reservation of user c is 2, i.e., the number of available items is 10, so the number of available items is more than the required number (step S500(YES)), the required number is 3 (step S502(YES)), there are adjacent available items (step S504(YES)), and the number of adjacent available items is 10, i.e., more than the required number (step S506(YES)), so the required number is determined from the adjacent available items (step S508). Here, the required number of return ports are determined from the adjacent available items in the order of least used. Of the 10 return slots (return slots with return slot numbers "H11", "H12", "H21", "H22", "H31", "H32", "H42", "H51", "H52", and "H62") that make up the adjacent spaces, the four return slots with return slot numbers "H31", "H32", "H42", and "H62" are return slots that were used two days ago, and the six return slots with return slot numbers "H11", "H12", "H21", "H22", "H51", and "H52" are return slots that were used yesterday. Therefore, three of the four return slots used two days ago are selected, and the three cannot be identified based on the usage status alone. Therefore, here, the three return slots with return slot numbers "H31", "H32", and "H42" are selected so that the multiple return slots used by user c are adjacent to each other.

[0306] After that, when a fourth reservation (user d) is made, five return ports with return port numbers "H11", "H12", "H21", "H22", and "H62" are determined for the reservation of user d, as shown in the fourth row of FIG. 31(B). In other words, the required number of return ports for user d is 5, and the number of reserved ports at the time of reservation for user d is 5, i.e., the number of vacant spaces is 7, so the number of vacant spaces is greater than the required number (step S500(YES)), the required number is 5 (step S502(YES)), there are adjacent vacant spaces (adjacent vacant spaces with an adjacent vacant number of 4 and adjacent vacant spaces with an adjacent vacant number of 3) (step S504(YES)), and the adjacent vacant number (maximum) is 4, i.e., greater than the required number (step S506(YES)), so the required number is determined from the adjacent vacant spaces (step S508). Here, the required number of return ports are determined from the adjacent vacant spaces in the order of least used. That is, among the four return slots (return slots with return slot numbers "H11", "H12", "H21", and "H22") that make up the adjacent number of vacancies of 4, and the three return slots (return slot numbers "H51", "H52", and "H62") that make up the adjacent number of vacancies of 3, the one return slot used two days ago (return slot with return slot number "H62") is determined first. Next, four return slots are determined from the six return slots used three days ago (return slots with return slot numbers "H11", "H12", "H21", "H22", "H51", and "H52"), but the four cannot be identified based on the usage status alone. Therefore, here, the four return slots with return slot numbers "H11", "H12", "H21", and "H22" are determined so that the multiple return slots used by user d are adjacent to each other.

[0307] (Method of determining return ports collectively based on usage status / Fig. 31(C)) In the explanation of FIG. 31(C), it is assumed that a total of four requests for reservation of return slots are made in the following order before a predetermined time. 1st: Reservation by user A with 1 required return slot (required number) 2nd Reservation: Reservation by User B with the required number of return slots (required number) being 1 3rd Reservation: Reservation for user c with the required number of return slots (required number) of 3 4th: Reservation for user d with a required number of return slots (required number) of 5 That is, in this determination method, the return port is determined in descending order of the required number (reservation of user d→reservation of user c→reservation of user a→reservation of user b) (step S518 in FIG. 30).

[0308] At a predetermined time (for example, 23:00 on the day before the reservation), first, as shown in the top row of FIG. 31(C), five return ports with return port numbers "H31", "H32", "H41", "H42", and "H51" are determined for the reservation of user d. That is, the required number for user d is 5, and the number of reserved items at the time of reservation of user d is 0, i.e., the number of available items is 12, so the number of available items is more than the required number (step S520 (YES) in FIG. 30), the required number is 5 (step S522 (YES)), there are adjacent available items (step S524 (YES)), and the number of adjacent available items is 12, i.e., more than the required number (step S526 (YES)), so the required number is determined from the adjacent available items (step S528). Here, the return ports are determined by giving priority to adjacent available items while considering the order of the least used items among the adjacent available items. Specifically, the system determines the least used return port (return port with return port number "H41" that was used three days ago), then determines the three return ports adjacent to the least used return port (return port with return port number "H41") (return ports with return port numbers "H31", "H42", and "H51"), and then determines the least used return port (return port with return port number "H32") among the two return ports (return ports with return port numbers "H32" and "H52") diagonally located from the least used return port (return port with return port number "H41").

[0309] Next, as shown in the second row of Fig. 31(C), three return ports with return port numbers "H52", "H61", and "H62" are determined for the reservation of user c. In other words, the required number for user c is 3, and the number of reserved ports at the time of reservation by user c is 5, i.e., the number of vacant ports is 7, so the number of vacant ports is more than the required number (step S520 (YES)), the required number is 3 (step S522 (YES)), there are adjacent vacant ports (adjacent vacant ports with an adjacent vacant number of 4 and adjacent vacant ports with an adjacent vacant number of 3) (step S524 (YES)), and the adjacent vacant number (maximum) is 4, i.e., more than the required number (step S526 (YES)), so the required number is determined from the adjacent vacant ports (step S528). Since there are the same number of adjacent vacancies as the required number (specifically, three) (adjacent vacancies with return port numbers "H51", "H61", and "H62"), here we have determined the three vacant return ports (return ports with return port numbers "H52", "H61", and "H62") that make up the adjacent vacancies.

[0310] Next, as shown in the third row of FIG. 31(C), the return slot with the return slot number "H11" is determined for the reservation of user a. That is, the required number for user a is 1, and the reserved number at the time of reservation for user a is 8, i.e., the available number is 4, so the available number is greater than the required number (step S520 (YES)), and the required number is 1 (step S522 (NO)), so the least used one of the four available return slots is reserved (step S523). All of the four available return slots are return slots used yesterday (return slots with the return slot numbers "H11", "H12", "H21", and "H22"), so it is not possible to identify one by the usage status alone. Since it is not possible to identify one by the usage status alone, here, the return slot with the return slot number "H11" is determined according to a predetermined priority order (for example, a priority order that gives priority to the left column and the upper row in the same column).

[0311] Next, as shown in the fourth row of FIG. 31(C), the return slot with the return slot number "H12" is determined for the reservation of user b. That is, the required number for user b is 1, and the reserved number for user b at the time of reservation is 9, i.e., the available number is 3, so the available number is greater than the required number (step S520 (YES)), and the required number is 1 (step S522 (NO)). Therefore, the least used one of the three available return slots is reserved (step S523). The three available return slots are all return slots used yesterday (return slots with the return slot numbers "H12", "H21", and "H22"), so it is not possible to identify one by the usage status alone. Since it is not possible to identify one by the usage status alone, here, the return slot with the return slot number "H12" is determined according to a predetermined priority order (for example, a priority order that gives priority to the left column and the upper row in the same column).

[0312] Above, Figure 31 has been used to explain, using specific examples, a method for determining a return port for each individual reservation based on usage (the determination method in the flowchart shown in Figure 29), and Figure 31 (C) has been used to explain a method for determining a return port collectively for multiple reservations based on usage (the determination method in the flowchart shown in Figure 30).However, the methods for determining a return port are not limited to these.

[0313] Fig. 32 is an explanatory diagram for explaining another method of determining a return slot. The method of determining a return slot explained in Fig. 31 (the method of determining a return slot in the flow charts shown in Fig. 29 and Fig. 30) is a method of determining a return slot by specifically managing and referring to the usage status of each return slot so that each return slot is used evenly, but the method of determining a return slot explained in Fig. 32 is a method of determining a return slot by moving the standard (standard determination position) for determining the position of the return slot so that each return slot is used evenly.

[0314] Fig. 32(A) shows a schematic diagram of all 12 return slots (return slot numbers "H11" to "H62") of the common locker 200 of Fig. 18(B). In Fig. 32(A), return slot number "H51" is the current reference determined position.

[0315] Fig. 32(B) shows how each return port shown in Fig. 32(A) is determined by a method of determining a return port for each reservation based on a reference determination position. Fig. 32(C) shows how each return port shown in Fig. 32(A) is determined by a method of determining a return port for multiple reservations collectively based on a reference determination position.

[0316] (Method of determining the return port for each reservation based on the reference determination position / Figure 32(B)) In the explanation of FIG. 32(B), it is assumed that there are requests to reserve a total of four return slots in the following order. 1st: Reservation by user A with 1 required return slot (required number) 2nd Reservation: Reservation by User B with the required number of return slots (required number) being 1 3rd Reservation: Reservation for user c with the required number of return slots (required number) of 3 4th: Reservation for user d with a required number of return slots (required number) of 5 That is, in this determination method, the return port is determined in the order of reservations (reservation by user a → reservation by user b → reservation by user c → reservation by user d).

[0317] When the first reservation (user a) is made, as shown in the top row of FIG. 32(B), the return port with return port number "H51" is determined for the reservation of user a. That is, since the current reference determined position is the return port with return port number "H51" and the required number for user a is one, one is determined from the reference determined position (return port with return port number "H51"), that is, the return port with return port number "H51". Also, as shown in the top row of FIG. 32(B), the reference determined position is changed from the return port with return port number "H51" to the return port with return port number "H52". That is, the reference determined position is moved by the determined number (one unit) according to a predetermined order (in the example of FIG. 32(B), return port numbers are "H51" → "H52" → "H61" → "H62" → "H11" → "H12" → ...).

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

[0319] After that, when a second reservation (user b) is made, the return port with return port number "H52" is determined for user b's reservation, as shown in the second row of Fig. 32(B). In other words, since the current reference determined position is the return port with return port number "H52" and user b's required quantity is one, one is determined from the reference determined position (return port with return port number "H52"), that is, the return port with return port number "H52". Also, as shown in the second row of Fig. 32(B), the reference determined position moves by the determined number (one unit) and is changed from the return port with return port number "H52" to the return port with return port number "H61".

[0320] After that, when a third reservation (user c) is made, three return ports with return port numbers "H61", "H11", and "H12" are determined for the reservation of user c, as shown in the third row of FIG. 32(B). In other words, since the current reference determined position is the return port with return port number "H61", and the required number for user c is three, three return ports (three in a predetermined order) are determined from the reference determined position (return port with return port number "H61"), that is, three return ports with return port numbers "H62", "H61", and "H11". Also, as shown in the third row of FIG. 32(B), the reference determined position is moved by the determined number (three ports) and is changed from the return port with return port number "H61" to the return port with return port number "H12".

[0321] After that, when a fourth reservation (user d) is made, five return ports with return port numbers "H12", "H21", "H22", "H31", and "H32" are determined for the reservation of user d, as shown in the fourth row of FIG. 32(B). In other words, since the current reference determined position is the return port with return port number "H12", and the number of return ports required by user d is five, five return ports (five in a predetermined order) are determined from the reference determined position (return port with return port number "H12"), that is, five return ports with return port numbers "H12", "H21", "H22", "H31", and "H32". Also, as shown in the fourth row of FIG. 32(B), the reference determined position is moved by the determined number (five return ports) and is changed from the return port with return port number "H12" to the return port with return port number "H41".

[0322] (Method of determining the return port collectively based on the reference determination position / Fig. 32(C)) In the explanation of FIG. 32(B), it is assumed that a total of four requests for reservation of return ports are made in the following order before a predetermined time. 1st: Reservation by user A with 1 required return slot (required number) 2nd Reservation: Reservation by User B with the required number of return slots (required number) being 1 3rd Reservation: Reservation for user c with the required number of return slots (required number) of 3 4th: Reservation for user d with a required number of return slots (required number) of 5 That is, in this determination method, the return port is determined in the order of the required number (reservation of user d → reservation of user c → reservation of user a → reservation of user b).

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

[0324] Next, as shown in the top row of FIG. 32(C), five return ports, "H11", "H12", "H21", "H22", and "H31", are determined for the reservation of user d. In other words, since the number of return ports required by user d is five, five adjacent return ports (return port numbers "H11", "H12", "H21", "H22", and "H31") are determined from the return port determination range. Note that there are other combinations of five adjacent return ports besides the above combinations (return port numbers "H11", "H12", "H21", "H22", and "H31") (for example, return port numbers "H11", "H12", "H21", "H22", and "H32"), but in FIG. 32(C), the order is in accordance with a predetermined order (return port number "H11" → "H12", "H21", "H22", "H31", "H32", ...).

[0325] Next, as shown in the second row of Fig. 32(C), three return ports with return port numbers "H51", "H62", and "H61" are determined for the reservation of user c. In other words, since the number of return ports required by user c is three, three adjacent return ports (with return port numbers "H51", "H52", and "H61") are determined from among the undetermined return ports within the return port determination range (five return ports with return port numbers "H32", "H51", "H52", "H61", and "H62").

[0326] Next, as shown in the third row of Figure 32 (C), one return port with return port number "H32" is determined for user a's reservation. In other words, since user a requires only one item, the return port with return port number "H32" is determined from among the undetermined return ports within the return port determination range (the two return ports with return port numbers "H32" and "H62").

[0327] Next, as shown in the fourth row of Figure 32 (C), one return outlet with return port number "H62" is determined for user b's reservation. In other words, since the required quantity for user b is 1, an undetermined return outlet within the return outlet determination range (the one return outlet with return port number "H62") is determined.

[0328] The methods of determining the return port have been explained above using FIG. 31 and FIG. 32. Each of the methods has the following features, for example.

[0329] In the method of determining the return exit for each reservation based on the usage status (Fig. 31(B)), the return exit is determined based on the actual past usage status at the time of reservation each time a reservation is made, so adjacent return exits can be reserved as much as possible, and return exits can be reserved evenly by reflecting the usage status at the time of reservation. Furthermore, the return exit can be notified to the user immediately.

[0330] In the method of determining return ports collectively based on usage (FIG. 31(C)), the return ports are determined collectively in descending order of the number required at a given time, so adjacent return ports are more likely to be determined and return ports can be reserved evenly, reflecting the usage at the given time. Also, the processing is relatively simpler than the method of determining a return port for each reservation based on usage. In other words, in the method of determining a return port for each reservation based on usage, the return port is determined on the reservation date and past usage changes depending on the reservation date, making the processing relatively complicated, whereas in the method of determining a return port collectively based on usage, the determination date is constant regardless of the reservation date, making the processing relatively simple.

[0331] In the method of determining a return exit for each reservation based on the reference determined position (Figure 32 (B)), the return exit is determined using the reference determined position rather than past usage, so the processing is relatively simple compared to the method of determining a return exit for each individual reservation based on usage.

[0332] In the method of determining a return outlet collectively based on a reference determination position (Figure 32 (C)), the return outlet is determined using a reference determination position rather than past usage status, so the processing is relatively simpler than in the method of determining a return outlet collectively based on usage status.

[0333] The manner in which a return port is determined based on the usage status is not limited to the above-mentioned example. That is, although the example shown in FIG. 31 manages the specific use or non-use for each day, the frequency of use in a predetermined period (for example, one week, one ten days, one month, etc.) may be managed. For example, in the manner in which the frequency of use is managed on a weekly basis, the frequency of use of each return port in the previous week may be calculated, and the return port that was used less frequently in the previous week may be preferentially determined.

[0334] In addition, the manner in which the return port is determined based on the reference determined position is not limited to the above example. That is, in the example shown in Fig. 32, the reference determined position is moved by one for each reservation date, but the reference determined position may be moved by one for each predetermined period (for example, one week, one ten days, one month, etc.).

[0335] Also, a determination method based on the usage status (example of FIG. 31) and a determination method based on the reference determination position (example of FIG. 32) may be combined. As an example, the reference determination position may be determined based on the usage status. The return slot that was least frequently used in the previous specified period (e.g., the past week, the past 10 days, the past month, etc.) may be determined as the reference determination position for the current specified period.

[0336] Fig. 33 is a flowchart showing an example of the operation when reserving a locker. Specifically, the flowchart shown in Fig. 33 shows an example of the operation when a user reserves a locker return (reserving a return locker) on the user terminal 50. Note that the flowchart shown in Fig. 33 (as well as the flowchart shown in Fig. 34) shows an example of the operation in which the return port is determined for each reservation as explained in Fig. 31(B) and Fig. 32(B).

[0337] 33, step S600: The user terminal 50 requests a reservation screen (for example, the locker return scheduled date calendar screen in FIG. 25) from the management device 10. For example, when the user performs an operation on the user terminal 50 to display the reservation screen (for example, a selection to the effect that the user wishes to return the locker), the user terminal 50 requests the reservation screen from the management device 10.

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

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

[0340] Step S608: The management device 10 receives the reservation information from the user terminal 50. Step S611: The management device 10 determines the return port based on the reservation information. For example, the management device 10 determines the return port by the method described in Fig. 31(B) or Fig. 32(B). Step S612: The management device 10 updates various files based on the result of determining the return port. That is, the management device 10 reflects the result of determining the return port in S611 in the electronic slip file of the user, the deposited product information file, the locker management master file, the locker reservation status file, etc. Step S613: The management device 10 updates and generates various screens. For example, the management device 10 updates and generates a reservation confirmation screen based on the result of determining the return port 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 reflecting the reservation contents as shown in FIG. 27, and updates the locker scheduled return date calendar screen to reflect the reservation contents as shown in FIG. 25. The management device 10 may also generate a locker scheduled return list screen reflecting the reservation contents as shown in FIG. 36. That is, in step S613, screen information to be transmitted in subsequent processes (steps S615 and S625) is generated.

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

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

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

[0344] Moreover, the processing of steps S625 and S626 may be performed when a store clerk operates the device, regardless of whether the message information is transmitted or received, instead of when the return slot is determined as shown in Fig. 33. As an example of transmitting the message information, the management device 10 transmits screen information of a small screen including an OK (display) button and a Cancel (do not display) button to the POS terminal 20 together with the message, and the POS terminal 20 that receives the screen information displays the small screen by superimposing it on the currently displayed screen, and when the OK (display) button is touched (corresponding to the operation of the store clerk), a reservation confirmation screen (locker return schedule calendar screen, locker return schedule list screen, etc.) is requested and transmitted from the management device 10 to the POS terminal 20. The same applies to the flowchart of Fig. 35.

[0345] The flowchart in FIG. 33 is an example of an operation in which the management device 10 determines the return port, but in the case of the mode in which the POS terminal 20 determines the return port, it is sufficient that the determination result of the return port by the POS terminal 20 is reflected in various files stored in the management device 10. As an example, the flow may be as follows. The user terminal 50 accesses the POS terminal 20 and displays a reservation screen (locker return scheduled date calendar screen). The POS terminal 20, which is requested to display the reservation screen by the user terminal 50, may access the management device 10 to receive screen information of the latest reservation screen and transmit (transfer) it to the user terminal 50. Next, the user terminal 50, which accepts a reservation operation on the reservation screen, transmits reservation information to the POS terminal 20. The POS terminal 20, which has received the reservation information from the user terminal 50, determines the return port and transmits information indicating the determination result of the return port to the management device 10. The management device 10 updates various files based on the information indicating the determination result of the return port received from the POS terminal 20. Next, the POS terminal 20 receives screen information of a reservation confirmation screen (a slip detail screen reflecting the reservation contents as shown in FIG. 27) from the management device 10, and transmits (transfers) it to the user terminal 50. Note that the processes of S625 and S626 are similar. As a result, the result of the determination of the return port by the POS terminal 20 is reflected in various files stored in the management device 10. The same is true in FIG. 35.

[0346] Fig. 34 is a flowchart showing an example of another operation when reserving a locker. Specifically, the flowchart shown in Fig. 34 shows an example of the operation when a store clerk reserves a locker return for an item deposited at the store (reserving a return locker) on the POS terminal 20.

[0347] 34, step S630: The POS terminal 20 requests a reservation screen (for example, the locker return scheduled date calendar screen in FIG. 25) from the management device 10. For example, when a store clerk performs an operation to display the reservation screen on the POS terminal 20 in response to a request for locker return from a user in person or over the phone, the POS terminal 20 requests the reservation screen from the management device 10.

[0348] Step S631: The management device 10 receives a request for a reservation screen (locker return date calendar screen) from the POS terminal 20. Step S632: The management device 10 generates screen information for a reservation screen (the latest locker return date calendar screen based on the current reservation status) in the same manner as in step S602 of FIG. Step S633: The management device 10 transmits 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: The POS terminal 20 displays a 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 a button for a day on which a reservation is available in the calendar section (symbol H)). Step S637: The POS terminal 20 transmits the reservation information (reservation date, required quantity, etc.) to the management device 10.

[0350] Step S638: The management device 10 receives the reservation information from the POS terminal 20. Step S641: The management device 10 determines a return port based on the reservation information. For example, the management device 10 determines a return port by the method described with reference to Fig. 31(B) or Fig. 32(B). Step S642: The management device 10 updates various files based on the result of determining the return port, similarly to step S612 in FIG. Step S643: The management device 10 updates and generates various screens, similarly to step S613 in FIG.

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

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

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

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

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

[0356] FIG. 35 is a flowchart showing an example of another operation when reserving a locker. Specifically, the flowchart shown in FIG. 35 shows an example of the operation by the method of determining the return port collectively described in FIG. 31(C) and FIG. 32(C) when the user reserves the locker return at the user terminal 50 and when the store clerk reserves the locker return at the POS terminal 20. That is, as an operation in a mode in which the return port is determined for each reservation, an example of the operation when reserving the locker return at the user terminal 50 is described using the flowchart in FIG. 33, and an example of the operation when reserving the locker return at the POS terminal 20 is described using the flowchart in FIG. 34. In the following, as an operation in a mode in which the return port is determined collectively, an example of the operation when reserving the locker return at the user terminal 50 and an example of the operation when reserving the locker return at the POS terminal 20 are described together using the flowchart in FIG. 35. Note that the flowchart shown in FIG. 35 replaces a part (dashed line C) of the flowcharts shown in FIG. 33 and FIG. 34.

[0357] Step S707 in FIG. 35: When a reservation operation by the user is accepted, the user terminal 50 transmits reservation information (reservation date, required number, etc.) to the management device 10. Step S708: The management device 10 receives the reservation information from the user terminal 50 and stores the received reservation information in the storage unit. In addition, the management device 10 does not currently determine a return port, but updates (subtracts) the number of available return ports based on the reservation information. Step S709: The management device 10 transmits reservation acceptance confirmation information to the user terminal 50 to confirm that the reservation has been accepted. Step S710: The user terminal 50 receives the reservation acceptance confirmation information from the management device 10, and stores the received reservation acceptance confirmation information in the storage unit. The user terminal 50 may display the reservation acceptance confirmation information.

[0358] Step S737: When the reservation operation by the store clerk is accepted, 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 the reservation information from the POS terminal 20 and stores the received reservation information in the storage unit. In addition, the management device 10 does not currently determine a return port, but updates (subtracts) the number of available return ports based on the reservation information. Step S739: The management device 10 transmits reservation acceptance confirmation information to the POS terminal 20 to confirm that the reservation has been accepted. Step S740: The POS terminal 20 receives the reservation acceptance confirmation information from the management device 10, and stores the received reservation acceptance confirmation information in the storage unit. The POS terminal 20 may display the reservation acceptance confirmation information.

[0359] Step S751: The user terminal 50 ends the process if the predetermined time has not yet arrived, and proceeds to step S766 following execution of step S765 if the predetermined time has arrived. Step S752: The POS terminal 20 ends the process if the predetermined time has not yet arrived, and proceeds to step S776 following execution of step S775 if the predetermined time has arrived. Step S753: If the predetermined time has not yet arrived, the management device 10 ends the process, and if the predetermined time has arrived, the management device 10 proceeds to step S761.

[0360] Step S761: The management device 10 determines the return port based on the reservation information stored in step S708 or step S738. For example, the management device 10 determines the return port by the method described in Fig. 31(C) or Fig. 32(C). Step S762: The management device 10 updates various files based on the result of determining the return port, similarly to step S612 in FIG. Step S763: The management device 10 updates and generates various screens, similarly to step S613 in FIG.

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

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

[0363] 35, the management device 10 may send message information to the user terminal 50 by e-mail or the like to inform the user that a locker has been reserved. In other words, when the return ports have been determined collectively, a minimum amount of information may be sent to the user terminal 50. Similarly, instead of the processing of steps S775 and S776 in FIG. 35, the management device 10 may send message information to the POS terminal 20 to inform the user that a locker has been reserved. In other words, when the return ports have been determined collectively, a minimum amount of information may be sent to the user terminal 50.

[0364] (Notification of return opening to users) The return port determined by the device that determines the return port (e.g., the management device 10, the POS terminal 20, etc.) is notified to the user at the latest by the time the user actually picks up the product from the return port. In other words, the user may be notified of which return port is the return port from which the deposited product will be picked up at any time during the period from after the return port is determined to when the product is received.

[0365] For example, the slip details screen shown in Fig. 27 displays the reserved date (locker reservation date) as the reservation content for locker return, but the reserved return port may be displayed in addition to the reserved date. That is, each user may be notified of the result of determining the return port (the processing result of the processing of S611 in Fig. 33, S641 in Fig. 34, or S761 in Fig. 35). Note that the result of determining the return port may be notified on another screen instead of or in addition to the slip details screen. For example, the reserved return port (the return port to be used) may be displayed instead of or in addition to the number of return ports on the locker return reservation confirmation screen (Fig. 36) displayed by the user terminal 50.

[0366] The device (management device 10, POS terminal 20) that has determined a return port (a return port where the user's deposited goods are to be placed) for a certain user may transmit the determination result (the return port where the user's deposited goods are to be placed) to the POS terminal 20 of the user immediately after the determination (at the timing of determining the return port). Therefore, in a mode in which a return port is determined for each reservation (modes of Figs. 29 and 31(B)), the determined return port (information indicating the return port) is transmitted to the POS terminal 20 immediately after each reservation. Also, in a mode in which return ports are determined collectively (modes of Figs. 30 and 31(C)), the determined return port (information indicating the return port) is transmitted to the POS terminal 20 immediately after the collectively determined return port.

[0367] Furthermore, a device that has determined a return port for a certain user may transmit the determination result to the POS terminal 20 of the user at a timing different from the timing of determining the return port. For example, a device that has determined a return port (management device 10, POS terminal 20) may transmit the determination result to the POS terminal 20 of the user at a predetermined time (e.g., 8:00 a.m. on the return date).

[0368] Furthermore, the device that has determined the return port may transmit the determination result to the POS terminal 20 of the user in response to a request (a request for the determination result) from the user terminal 50. Note that the user terminal 50 may transmit a request for the determination result to the device that has determined the return port, for example, based on an operation for confirming the return port.

[0369] Furthermore, the device that has determined the return port may transmit the determination result to the POS terminal 20 of the user in response to a request from the return locker (a request for the determination result) at a timing different from the timing of determining the return port. The return locker may transmit a request for the determination result to the device that has determined the return port based on an operation by the user (insertion of a membership card into the card insertion / ejection port, input of a PIN number or the like in the input operation unit, recognition of a barcode by the code recognition unit, etc.). In other words, the reserved return port may not be notified to the user until the return locker is actually operated, and the reserved return port may be made known to the user when the return locker is actually operated.

[0370] Also, instead of or in addition to the POS terminal 20, the return locker may notify the user of the result of the determination of the return port (the return port in which the user's deposited goods are located). As an example, the common locker 200 may display information indicating the corresponding return port 210 (the return port in which the user's deposited goods are located) on the display unit 204 based on the user's operation (insertion of a membership card into the card insertion / ejection port 203, input of a PIN number or the like in the input operation unit 205, recognition of a barcode by the code recognition unit 206, etc.). Also, a light-emitting unit (not shown) may be provided for each of the return ports 210, and the common locker 200 may light up (light up, blink, etc.) the light-emitting unit corresponding to the corresponding return port based on the user's operation, etc. Although this is the simplest configuration, the common locker 200 may open the return port door of the corresponding return port 210 (widely open so that it is clear that it is the corresponding return port) based on the user's operation, etc. The timing at which the return locker obtains the result of the determination of the return port may be before or after the user performs an operation, etc. In other words, the device that determined the return port may transmit the determination result to the return locker without a request (a request for the determination result) from the return locker (for example, immediately after the return port is determined or at a specified time), or may transmit the determination result to the return locker based on a request from the return locker. In the latter case, the return locker transmits a request for the determination result to the device that determined the return port based on an operation, etc. by the user.

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

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

[0373] The locker return reservation confirmation screen shown in FIG. 36 includes a current date and time field (see symbol A), a condition setting area (see symbol B), a result display area (see symbol C), and the like.

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

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

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

[0377] The number of items "3" is displayed based on the number of corresponding items (tag numbers "TG01-1372", "TG01-1373", "TG01-1375") in the stored item information file of Fig. 26. More specifically, it is displayed based on the number (specifically, 3) of items (tag numbers "TG01-1372", "TG01-1373", "TG01-1375") with a planned delivery date of "4 / 20" among the items (tag numbers "TG01-1372" to "TG01-1375") corresponding to the above-mentioned slip number "DN01-5422" in the stored item information file of Fig. 26. It may also be displayed based on the number (specifically, 3) of items with a planned date of "4 / 20" and the same reservation number (specifically, 12345). The number of return slots used, "2", is displayed based on the number (specifically, 2) of return slots (return slot numbers "H11", "H12") used to return the relevant products (tag numbers "TG01-1372", "TG01-1373", "TG01-1375") in the deposited product information file in Figure 26. Reissue "*" is displayed based on the fact that a reissue (multiple printings) has been performed.

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

[0379] Alternatively, the POS terminal 20 may display information related to other stores. For example, a store setting field may be provided on the locker return reservation confirmation screen, and the POS terminal 20 may display information related to the store of the store code entered in the store setting field. Also, for example, an all stores button may be provided on the locker return reservation confirmation screen, and when the all stores button is operated, the POS terminal 20 may display information related to all stores without limiting the 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 the user terminal 50 of a certain user is limited to reservation information related to the user.

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

[0382] 37 and 38 are examples of media to be printed and issued. The POS terminal 20 prints and issues various slips when depositing goods. FIG. 37(A) and FIG. 37(B) are deposit slips (customer copies) issued by the POS terminal 20 of the store when depositing goods. The POS terminal 20 may print and issue, for example, a deposit slip as shown in FIG. 37(A) when the user's instruction regarding the delivery method of the deposited goods after completion is delivery by visiting the store (corresponding to delivery category "1") or is undecided (corresponding to delivery category "0"). The POS terminal 20 may print and issue, for example, a deposit slip as shown in FIG. 37(B) when the user's instruction regarding the delivery method of the deposited goods after completion is delivery by locker (corresponding to delivery category "3").

[0383] The deposit slips shown in Figures 37(A) and 37(B) are for the slip number "DN01-5422" shown in Figure 6 etc. According to Figure 6, the number of items deposited for slip number "DN01-5422" is four ("TG01-1372" to "TG01-1375"), but for the sake of explanation, the number is assumed to be three ("TG01-1372", "TG01-1374", "TG01-1375"). The same is true in Figure 38.

[0384] In the case of in-store delivery, as shown in FIG. 37(A), the date when all (3) deposited items can be delivered is printed as the finishing date, whereas in the case of delivery at a return locker, as shown in FIG. 37(B), the date when the locker return is reserved is printed as the scheduled locker return date. The locker return reservation may be made before issuing the deposit slip. For example, in the example shown in FIG. 9, the POS terminal 20 may accept the locker return reservation at any time between steps S17 to S21 and before issuing the deposit slip.

[0385] The printed and issued deposit slip is given to the user. For example, if the user is met face-to-face (for example, in the case of regular store deposit (deposit category "1")), the slip is given to the user immediately after issuance. If the user is not met face-to-face (for example, in the case of locker deposit (deposit category "4")), the slip is given to the user at the time of return (in the case of locker return, the slip is placed in the return slot together with the deposited item). Note that the POS terminal 20 may print and issue the deposit slip shown in FIG. 37(A) or FIG. 37(B) for some users who do not use the user terminal 50, and may normally (for users who use the user terminal 50) print and issue a deposit slip that is simpler than the one shown in FIG. 37(A) or FIG. 37(B).

[0386] Fig. 38 shows a factory receipt issued by the POS terminal 20 of the store when the product is deposited. When the user's instruction regarding the method of delivery of the deposited product after completion is delivery by locker (corresponding to delivery category "3"), the POS terminal 20 may print and issue, for example, a factory receipt as shown in Fig. 38.

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

[0388] A readable code (QR code, barcode, etc.) is printed on the factory copy. The QR code, etc. printed on the factory copy can be used for inspection and locker return. The type of information that is coded and printed varies depending on whether or not the item will be returned to a locker, the timing of the reservation, the timing of the return port selection, etc.

[0389] For example, when a user desires to return the product to a locker at the time of depositing the product, and reserves a return date and determines the return port before issuing a factory copy, the POS terminal 20 may print a QR code or the like that encodes the customer code, the return port number of the determined return port, etc. The POS terminal 20 may print a QR code that encodes a slip number, tag number, etc. (for example, a QR code that encodes the customer code, reservation date, tag number, and return port number) instead of or in addition to the customer code.

[0390] Furthermore, if the user wishes to return the product to a locker when depositing the product and reserves a return date but does not decide on a return port before issuing a factory copy, the POS terminal 20 may print a QR code or the like that encodes the customer code, the number of required return ports, etc. The POS terminal 20 may print a QR code that encodes a slip number, tag number, etc. (for example, a QR code that encodes the customer code, reservation date, tag number, and the number of required return ports) instead of or in addition to the customer code.

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

[0392] When depositing the goods, the POS terminal 20 may print and issue a store copy (not shown) to be kept in the store, in addition to a customer copy to be given to the user and a factory copy to be sent to the factory.

[0393] In the above description, the management device 10 or the POS terminal 20 determines the return port, but the return locker may determine the return port. The device that specifies the reservation available date (the device that determines whether or not the reservation is possible) and the device that determines the return port do not necessarily have to be the same. Therefore, various modes such as the following (a) to (f) are possible, as examples. (a) The management device 10 identifies the available reservation dates and determines the return port. (b) The POS terminal 20 identifies the available reservation dates and determines the return port. (c) The management device 10 identifies the available reservation dates, and the POS terminal 20 determines the return port. (d) The management device 10 identifies the available reservation dates, and the return locker determines the return port. (e) The POS terminal 20 identifies the available reservation dates, and the return locker determines the return port. (f) The return locker identifies the reservation dates and determines the return location.

[0394] In the above (a) to (f), the return port may be determined at the time when the reservation available date is specified, or at a different time from the time when the reservation available date is specified. In other words, the specific return port may be determined when reserving the date of return to the locker, or only the date of return to the locker may be reserved and the specific return port may be determined separately.

[0395] Figures 39 to 41 are examples of screens displayed on the display of a return locker. The screens in Figures 39 to 41 are examples of screens displayed on the display of the return-only locker 300 in Figure 18(C). Also, the return port numbers (door numbers) of the five return ports of the return-only locker 300 are assumed to be "01" to "05".

[0396] Fig. 39(A) is a standby screen (initial screen). On the standby screen of Fig. 39(A), a message is displayed to the operator (user, store clerk, etc.) encouraging the operator to touch the screen. If the operator touches the screen while the standby screen of Fig. 39(A) is displayed, the screen transitions to the screen of Fig. 39(B).

[0397] Fig. 39(B) is a card reading screen to which the standby screen of Fig. 39(A) transitions. The card reading screen of Fig. 39(B) displays a message to the user, urging the user to read the membership card or enter a password. When the card reading screen of Fig. 39(B) is displayed, if the membership card is inserted into the card insertion / ejection slot and read, or if the password button is touched and a password entry screen (not shown) is displayed after touching and a password is entered, the screen transitions to the screen of Fig. 39(C). Note that the screen of Fig. 39(C) may also be transitioned to by other methods (for example, reading the barcode G11 displayed on the membership card screen, etc.).

[0398] Furthermore, if a predetermined operation is performed by the store clerk while the card reading screen in Fig. 39(B) is being displayed, a transition to a store clerk initial screen (not shown) will occur. As an example, if a store clerk barcode printed on a medium (e.g., a store clerk barcode registered in advance to display the store clerk initial screen) is recognized by the code recognition unit and read, a transition to the store clerk initial screen will occur. Note that a transition to the store clerk initial screen may also be made by other methods (e.g., inputting a store clerk password, inserting a store clerk card into a card insertion / ejection slot, etc.). Note that Figs. 40(A) and 41(B) are screens to which the store clerk initial screen transitions.

[0399] Fig. 39(C) is a notification screen to which the screen transitions from the card reading screen of Fig. 39(B) (specifically, to which the screen transitions when the membership card is read or the password is entered). The notification screen of Fig. 39(C) notifies the user (the user identified based on the membership card or password) of the return slot number (door numbers "01", "02", "03" in the example of Fig. 39(C)) where the user's deposited goods are stored as notification information.

[0400] For example, the return locker may store the result of determining the return port (the return port number of the return port determined for each user) in a memory unit, and may notify the return port number as described above by referring to the memory unit. Note that, if another device (management device 10, POS terminal 20, etc.) determines the return port, the return locker may obtain the determination result and store it in the memory unit. Note that, the return locker may notify the return port number as described above by inquiring of the result of determining the return port (the return port number of the return port determined for the user) from the other device (management device 10, POS terminal 20, etc.).

[0401] Furthermore, the return locker may display the customer ID and the number of return slots in addition to the return slot number on the notification screen of FIG. 39(C).

[0402] The return locker displays the notification screen on the display, unlocks the return slot door of the relevant return slot (the return slot where the user's deposited items are stored), and blinks the light-emitting unit (lamp) corresponding to the unlocked return slot. When the user opens the return slot doors for all notified return slots (all unlocked return slots), removes the deposited items, and closes the return slot doors, the locker return process is completed and the screen transitions to the screen shown in Fig. 39(D). The return locker locks the closed return slot doors and turns off the light-emitting unit corresponding to the locked return slots.

[0403] The return locker may determine that the deposited product has been removed by opening and closing the return door, or may determine that the deposited product has been removed by providing an optical sensor (camera, photo sensor, etc.) inside the return locker. Also, instead of or in addition to an optical sensor, a scale may be used to determine that the deposited product has been removed. Similarly, the deposited product may be determined to have been collected when it is collected, or stored when it is stored.

[0404] Fig. 39(D) is a completion screen to which the notification screen of Fig. 39(C) transitions. When a predetermined time (e.g., 10 seconds) has elapsed since the start of displaying the completion screen of Fig. 39(D), the screen transitions (returns) to the standby screen of Fig. 39(A).

[0405] Special points may be awarded to users who have returned items to the locker, and the return locker may display the special points awarded for the current locker return on the completion screen of Fig. 39(D). Whether or not points are awarded may be determined depending on whether or not the locker return has been performed a predetermined number of times in succession (whether or not the item has been collected), and the number of points awarded may be varied. In other words, a large benefit may be given to users who always come to pick up their deposited items on the return date.

[0406] FIG. 40(A) is an initial storage screen to which the clerk initial screen (not shown) transitions. For example, the initial clerk screen has various buttons such as a return item storage button, a return item collection button, and a back button, and when the return item storage button is touched, the screen transitions to the initial storage screen. The initial storage screen of FIG. 40(A) has an empty door confirmation button and a back button. In addition, the initial storage screen of FIG. 40(A) displays a message to the clerk, encouraging the clerk to read the QR code printed on the factory copy. By touching the empty door confirmation button, the current availability of the return slots can be confirmed. For example, an image of a return locker as shown in FIG. 31(A) (specifically, an image in which each of the five return slots is color-coded according to whether it is empty or stored) may be displayed. Also, in order to efficiently determine the return slot on the initial storage screen of Fig. 40(A) (see step S518 of Fig. 30), a message recommending that the factory receipts be read in order of the number of return slots (for example, "Please read the factory receipts in order of the number of return slots") may be displayed. If the QR code printed on the factory receipt is recognized or read by the code recognition unit while the initial storage screen of Fig. 40(A) is displayed, the screen will transition to the screen of Fig. 40(B).

[0407] The return locker may also perform a date check. For example, the date in the date and time information included in the read QR code may be compared with the current date to determine whether they match. If the date check results in an error (if they do not match), the return locker may display a message indicating that they do not match (that the return date is not the original return date). The return locker may also display a message indicating that they do not match and the original return date. A date check may also be performed on the card reading screen of FIG. 39(B) described above. For example, the return date of the user identified by reading a membership card or the like may be compared with the current date to determine whether they match.

[0408] Fig. 40(B) is a storage instruction screen to which the screen transitions from the initial storage screen in Fig. 40(A). The storage instruction screen in Fig. 40(B) notifies the store clerk of the return slot number (door numbers "01" and "02" in the example of Fig. 40(B)) where the deposited items of the user (the user identified based on the QR code) will be stored. Note that a back button is provided on the storage instruction screen in Fig. 40(B).

[0409] Below, we will explain the relationship between the information that can be obtained from the QR code and the notification of the return entrance number. (If the return number can be obtained from the QR code) The return locker may notify the return port number obtained from the QR code (the return port number of the return port determined to be the return port that will receive the user's deposited products). In other words, since the return port has been determined and the determination result has been converted into a QR code, the return locker may simply notify the return port number obtained from the QR code.

[0410] (If the number of return slots can be obtained from the QR code) The return locker may determine a return port using the number of return ports obtained from the QR code (the number of return ports required to store the user's deposited products) and notify the return port number of the determined return port. In other words, since a reservation is made based on the number of return ports required but a specific return port has not been determined, a return port may be determined in the same manner as the management device 10, etc., and the return port number of the determined return port may be notified.

[0411] (If the customer ID can be obtained from the QR code) The return locker may obtain a return port number (the return port number of the return port determined as the return port that will store the deposited goods of the user) corresponding to the customer ID by transmitting the customer ID obtained from the QR code to the device that determined the return port (the management device 10, the POS terminal 20, etc.) and may notify the obtained return port number. Note that, after obtaining the customer ID from the return locker, the management device 10, etc. may determine the return port that will store the deposited goods of the user with that customer ID and transmit (notify) the determination result to the return locker.

[0412] The return locker displays the storage instruction screen on the display, unlocks the return door of the relevant return slot (the return slot that stores the user's deposited items), and blinks the light-emitting unit corresponding to the unlocked return slot. The store clerk opens the return door for all notified return slots (all unlocked return slots), stores the deposited items, and closes the return door, thereby completing the storage work for the relevant return slot. The return locker locks the closed return slot door and turns off the light-emitting unit corresponding to the locked return slot.

[0413] FIG. 41(A) is a collection initial screen to which the clerk initial screen (not shown) transitions. For example, the clerk initial screen has various buttons arranged thereon, such as a return item storage button, a return item collection button, and a back button, and transitions to the collection initial screen when the return item collection button is touched. The collection initial screen of FIG. 41(A) has an OK button for starting collection and a back button arranged thereon. The collection initial screen of FIG. 41(A) also displays a message to the clerk encouraging the user to touch the OK button. When the OK button is touched, transitions to the screen of FIG. 41(B).

[0414] Fig. 41(B) is a collection instruction screen to which the user transitions from the initial collection screen in Fig. 41(A). The collection instruction screen in Fig. 41(B) notifies the store clerk of all return slot numbers (door numbers "01" to "05" in the example of Fig. 41(B)). The collection instruction screen in Fig. 41(B) also includes a back button and the like.

[0415] The return locker displays a collection instruction screen on the display unit and unlocks the return door of all return slots. The store staff opens the return door for all notified return slots (all unlocked return slots), collects any products that have not been returned to the locker, and closes the return door, completing the collection process. The return locker locks the closed return slot door. The return locker may flash the light-emitting unit corresponding to the unlocked return slot and turn off the light-emitting unit corresponding to the locked return slot.

[0416] The return locker may use a factory receipt (or a list of factory receipts) to identify the product (user) that was not received.

[0417] Examples of screens displayed on the display unit of the return locker have been described above using Figs. 39 to 41. An operation mode when a screen (initial screen for clerk (not shown), each screen shown in Fig. 40 and Fig. 41) displayed based on a predetermined operation by a clerk is displayed may be referred to as a clerk mode (or clerk mode). In addition, an operation mode when a screen other than the screen displayed based on a predetermined operation by a clerk (the screen shown in Fig. 39) is displayed may be referred to as a user mode (or user mode). Note that, in order to transition to the initial screen for clerk (not shown) via the screens in Figs. 39(A) and 39(B) (i.e., not only the user but also the clerk operates the screens shown in Figs. 39(A) and 39(B), the mode may be limited to the screens shown in Figs. 39(C) and 39(D) being displayed, excluding the screens shown in Figs. 39(A) and 39(B).

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

[0419] 42 and 43, the factory copy is printed with a QR code that encodes information including the number of return slots, and the return locker determines the return slot based on the number of return slots, etc., as an operation when storing the item, and stores the determination result in the memory unit. Also, in the flowcharts of Fig. 42 and 43, the return locker refers to the memory unit as an operation when returning the item to the user, and recognizes the return slot number of the return slot determined for each user.

[0420] Step S800 in Fig. 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. That is, the process of step S800 is repeatedly executed until the standby screen is touched. Step S801: The user is requested to read a membership card, etc. Specifically, the card reading screen shown in Fig. 39(B) is displayed, and the user is requested to read the membership card and enter a password.

[0421] Step S802: Determine whether or not the member's card has been read, etc. If the member's card has been read, etc. (Step S802; YES), proceed to Step S804. If the member's card has not been read, etc. (Step S802; NO), proceed to Step S810.

[0422] Step S804: The relevant return slot is notified. Specifically, the notification screen shown in Fig. 39(C) is displayed, and the return slot number of the return slot where the user's deposited product is stored is notified. Step S805: The return slot door of the corresponding return slot is unlocked, and the light emitting unit is made to blink. Note that the light emitting unit may be turned off after the return slot door is opened and closed (locked), for example.

[0423] Step S806: Determine whether or not the locker return (delivery of the deposited product) is complete. If the locker return is complete (step S806; YES), proceed to step S807. If the locker return is not complete (step S806; NO), return to step S806. In other words, the process of step S806 is repeated until the locker return is complete.

[0424] Step S807: Return completion information indicating that the locker return is complete is stored in the memory unit. The return completion information stored in step S807 may include, for example, some or all of the customer ID, return slot number, tag number, date and time information, etc. The return locker may transmit the return completion information to the management device 10 in addition to storing it in the memory 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 (FIG. 27, etc.) (e.g., update the progress category to "9 (delivery completed)") and display the updated screen on the user terminal 50, etc. Step S808: Completion of the locker return is notified. Specifically, the completion screen shown in Fig. 39(D) is displayed. Then, the flow charts in Fig. 42 and Fig. 43 end.

[0425] Step S810: Determine whether or not a predetermined operation has been performed by the store clerk (for example, whether or not a store clerk barcode has been read). If a predetermined operation has been performed (Step S810; YES), proceed to Step S820. If a predetermined operation has not been performed (Step S810; NO), return to Step S802.

[0426] Step S820: An initial screen (not shown) for store clerks on which various buttons (returned item storage button, returned item collection button, back button, etc.) are arranged is displayed. That is, the process transitions to store clerk mode. After step S820, the process proceeds to step S821 in FIG. 43.

[0427] Step S821 in Fig. 43: Determine whether the back button on the initial screen for store clerk (not shown) has been touched. If the back button has been touched (step S821; YES), return to step S800. Note that if the back button has been touched (step S821; YES), the process may be configured to return to step S801 instead of returning to 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 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 clerk (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: The store clerk is requested to read the QR code printed on the factory copy. Specifically, the storage initial screen shown in Fig. 40(A) is displayed, and an instruction to read the QR code is given. Step S831: Determine whether or not the back button on the storage initial screen (FIG. 40(A)) has been touched. If the back button has been touched (step S831; YES), the process returns to step S821. Note that if the back button has been touched (step S831; YES), the process may return to step S800 (or step S801) instead of returning to step S821. If the back button has not been touched (step S831; NO), the process proceeds to step S832.

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

[0430] Step S833: Based on the read QR code (number of return ports) and the like, a return port is determined using the method shown in FIG. 29 to FIG. Step S834: The determined return port is notified. Specifically, the storage instruction screen shown in Fig. 40(B) is displayed, and the return port number of the determined return port is notified. Step S835: The return slot door of the determined return slot is unlocked, and the light emitting unit is made to blink. Note that the light emitting unit may be turned off, for example, after the return slot door is opened and closed (locked).

[0431] Step S836: Determine whether or not storage of the return item (deposited product) 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 of step S836 is repeated until storage is complete.

[0432] Step S837: The storage completion information indicating that the storage of the return item is completed 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 customer ID, return slot number, tag number, date and time information, etc. The return locker may transmit the storage completion information to the management device 10 in addition to storing the storage completion information in the storage unit, 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 (FIG. 27, etc.) (updating the progress category to "4 (delivery possible)" etc.), and display the updated screen on the user terminal 50, etc. In addition to the normal "4 (delivery possible)", a progress category "4A (storage completed)" indicating that the storage of the locker return is completed may be set, and the progress category may be updated to "4A (storage completed)".

[0433] The clerk then reads the QR codes printed on each factory copy, and executes the process (steps S832 to S837) for each factory copy in the return locker. After executing the above process for all factory copies, the clerk touches the back button (step S831; YES) and ends the process for storing.

[0434] Step S840: The store clerk is requested to perform an operation to start collection. Specifically, the collection initial screen shown in Fig. 41(A) is displayed, and the store clerk is requested to touch the OK button to start collection. Step S841: Determine whether or not the back button on the collection initial screen (FIG. 41(A)) has been touched. If the back button has been touched (step S841; YES), return to step S821. Note that if the back button has been touched (step S841; YES), the process may be configured to return to step S800 (or step S801) instead of returning to step S821. If the back button has not been touched (step S841; NO), proceed to step S842.

[0435] Step S842: Determine whether or not the OK button on the collection initial screen (FIG. 41(A)) has been touched. If the OK button has been touched (step S842; YES), proceed to step S844. If the back button has not been touched (step S842; NO), return to step S841.

[0436] Step S844: Notify all return slots. Specifically, the collection instruction screen shown in Fig. 41(B) is displayed, and the return slot numbers of all return slots are notified. Step S845: The return slot doors of all the return slots are unlocked and the light emitting units are made to flash. Note that the light emitting units may be turned off after the return slot doors are opened and closed (locked), for example. Step S847: Collection completion information indicating that collection of the return item is complete is stored in the storage unit. The collection completion information stored in step S847 may include, for example, some or all of the customer ID, return port number, tag number, date and time information, etc. Then, the process returns to step S821. Note that after the end of step S847, the process may return to step S800 (or step S801) instead of returning to step S821.

[0437] Note that the return locker may transmit the collection completion information to the management device 10 instead of storing it in the memory unit, and the management device 10 may execute updates of various files based on the collection completion information. Note that, for example, in addition to the normal "4 (available for delivery)", a progress category "4B (available for normal delivery upon collection)" may be set to indicate that the stored product has been collected without completing the return of the product via the locker, and the progress category may be updated to "4B (available for normal delivery upon collection)".

[0438] 42 and 43, the order is described as follows: return by the user to the user (processing after step S802 (YES)) → storage by the clerk (processing after step S822 (YES)) → collection by the clerk (processing after step S823 (YES)), but when focusing on a certain product B held by a certain user A, the order of processing is storage of product B by the clerk → return of product B to user A by user A → collection of product B by the clerk (however, if product B has been returned to user A, product B will not be collected). Also, when focusing on the daily movements of clerk C, etc., the order of processing is collection of the products stored last time by clerk C → storage of the products stored this time by clerk C → return of the products stored this time to the user by the user.

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

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

[0441] For example, the flowcharts shown in Figs. 33 to 35 are flowcharts showing the operation at the time of locker reservation in the case of locker return using the return locker installed in the store where the product was deposited, but the return locker in the case of locker return is not limited to the return locker installed in the store where the product was deposited. In other words, it is possible to perform locker return using a return locker other than the return locker installed in the store where the product was deposited (for example, a return locker installed in a store different from the store where the product was deposited, or a return locker not installed in any store (a return locker installed in a position away from the store. A locker shared by the stores, etc.)). When reserving locker return from the user terminal 50, for example, the user terminal 50 may display a screen on which a locker can be specified (selected), and may transmit the locker number of the locker specified (selected) by the user on the screen to the management device 10 when requesting the reservation screen (i.e., in the process of step S600 in the flowchart of Fig. 33). The same applies to the case of reserving locker return from the POS terminal 20. That is, the POS terminal 20 may display a screen on which a locker can be specified (selected), and transmit the locker number of the locker specified (selected) by the store clerk on that screen to the management device 10 when requesting the reservation screen (i.e., in the processing of step S630 of the flowchart in Figure 34).

[0442] In the above embodiment, when there is a surplus of vacant return ports in the locker return, the device for determining the return port (e.g., the management device 10, the POS terminal 20, the return locker, etc.) determines (selects) the return port. However, the user may determine the return port in the above case. For example, the user terminal 50 may display a screen on which the user can specify an empty return port together with information that allows the user to recognize an empty return port (e.g., an image that shows a schematic of the return locker as shown in FIG. 31(A) and allows the user to visually check the availability of each return port), and the user may determine which return port to use from among the empty return ports. After the return port is determined, the user terminal 50 may transmit the determination result to the management device 10, and the management device 10 may execute updates of various files, etc.

[0443] In the above embodiment, the decision of the return outlet is left entirely to each individual user, but the device for deciding the return outlet (for example, the management device 10, the POS terminal 20, the return locker, etc.) may decide the return outlet by considering the wishes of each individual user (as a condition for deciding the return outlet). As an example, the device for deciding the return outlet may decide the return outlet by considering the wishes of the user (i.e., adjacent empty spaces) for a user who wants adjacent return outlets (by the method shown in Figs. 28 to 33), and may decide the return outlet without considering adjacent empty spaces for a user who does not want adjacent return outlets (by simply deciding the return outlet based on the past usage of each return outlet). In addition, whether adjacent return outlets are desired may be confirmed with the user at the time of member registration (the confirmation result may be stored in, for example, a customer master file), or may be input by the user at the time of locker reservation (for example, a check box for requesting adjacent return outlets may be provided on the reservation screen displayed in S605 of Fig. 33).

[0444] In the above embodiment, an example was described in which the adjacent vacancies and past usage were taken into consideration when determining the return vacancy, but the height from the installation surface may be taken into consideration instead of or in addition to the adjacent vacancies and past usage. For example, the device (e.g., the management device 10, the POS terminal 20, the return locker, etc.) that determines the return vacancy may preferentially determine the return vacancy in the upper row (e.g., the return vacancy numbers "H11", "H21", ..., "H61" in FIG. 18(B)) when there are still multiple candidates based on the judgment based on the adjacent vacancies and past usage (when one is randomly determined in S503 of FIG. 29). Also, for example, the return vacancy may be determined according to the user's preference by confirming whether the user desires the upper row return vacancy or the lower row return vacancy (e.g., the return vacancy numbers "H12", "H22", ..., "H62" in FIG. 18(B)) at the time of member registration or by having the user input the desired number at the time of locker reservation, as described above.

[0445] In the above embodiment, a tag is attached to each item to be stored, but the tag to be attached to the item to be stored may be purchased by the user. That is, the user may purchase the tag to be attached to the item to be stored. More specifically, the user may purchase the tag as a part or all of the cleaning fee for the item to be stored. A plurality of types of tags (a plurality of types of tags with different selling prices) with different selling prices for each type may be sold. Specifically, the whole or part of the tag may be in a different color or pattern for each type (each selling price) so that the selling price can be easily seen. As an example, a plain light blue tag may be sold for 300 yen (tag for shirts (dry)), and a light blue tag with a red line may be sold for 500 yen (tag for shirts (dry + sweatproof, etc.)). The place where the tag is sold is not limited to a dry cleaning store, and may be a supermarket, a convenience store, a specialty store (clothing store, pharmacy, etc.), a shop in a station (or near a station), or indoors or outdoors in an apartment building, etc.

[0446] Also, a vending machine may be installed in any of the above locations and tags may be sold from the vending machine. Note that even if the vending machine is installed in a location other than the above locations, it may be installed in a location where lockers are installed or in a collection area for collection and storage. Also, the vending machine that sells tags may be provided 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. Also, the vending machine that sells tags may be made capable of recognizing a membership card so that the customer code of a member who purchases a tag is transmitted to the management device 10. Also, points may be awarded for the purchase of a tag.

[0447] In the above embodiment, the tag numbers of each deposited product in one transaction (each deposited product belonging to a certain slip) are consecutive (see FIG. 6), but as long as it is possible to specify which transaction (slip) each deposited product belongs to, the tag numbers of each deposited product in one transaction do not have to be consecutive. 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 consecutive). However, when selling different types of tags, it is difficult to sell them with consecutive numbers. In addition, when consuming (using) tags, it is not necessary to be aware of the tag numbers of the tags attached to the deposited products (for example, when depositing multiple products, it is not necessary to check whether the tag numbers of the tags attached to each product are consecutive). In the above embodiment, it is possible to use the deposited product numbers instead of the tag numbers on various screens (FIGS. 11, 12, etc.) and various files (FIG. 20, etc.). The same applies when the tags are not sold, i.e. when the tags are attached by a store clerk.

[0448] In the case of selling tags, in a case where the collection of the fee is delayed because the payment is not made at the time of depositing the goods (specifically, in the case of bagged deposit), tags may be sold to speed up the collection. For example, in the case of speed deposit (deposit category "2") or locker deposit (deposit category "4"), a request may be made to attach a tag to the goods to be deposited in a bag. The user terminal 50 may display a list screen of cleaning fees (for example, by receiving and displaying a list screen from the management device 10 or the POS terminal 20). The user terminal 50 may also display the place where tags are sold (the nearest place, etc.) (for example, the management device 10 or the POS terminal 20 may have a function for searching for a place of sale, and the user terminal 50 may use the search function to display the place of sale, etc.).

[0449] If the price of the tag attached to the product by the user does not reach the required amount (the price after inspection), the management device 10 (or the POS terminal 20) may notify the user terminal 50 of the user that the amount is insufficient and may display a screen for selecting a payment method (credit card payment, prepaid payment, coupon payment, point payment) so that the shortfall can be settled at the user terminal 50. On the other hand, if the price of the tag attached to the product by the user exceeds the required amount (the price after inspection), the management device (or the POS terminal 20) may transmit to the user terminal 50 of the user a coupon ticket with the face value of the excess amount, or an electronic exchange ticket (for example, an exchange screen displaying the amount to be received, a barcode indicating the amount to be received, etc.) that can be exchanged for cash when the user visits the store. In addition, the management device (or the POS terminal 20) may record (reflect) the excess amount as a deposit in the prepaid payment and notify the user terminal 50 of the user that the excess amount has been recorded as a deposit in the prepaid payment.

[0450] In addition, to promote sales of tags, points may be given preferentially for tag purchases. For example, in a case where 1 point is given for every 200 yen when paying in cash at a store, 2 points may be given for every 300 yen when purchasing tags. Also, instead of or in addition to points given when purchasing tags, points may be given when tags are used. Also, an expiration date may be set for purchased tags, and more points may be given if the tags are used within the expiration date.

[0451] In the above embodiment, the reception-only locker 100 is provided with a control unit, and the control unit controls the display on the display unit 104, the locking of the deposit slot door, etc., but other devices (e.g., the management device 10, the POS terminal 20) may control part (or all) of the display on the display unit 104 and the locking of the deposit slot door. The same applies to the common locker 200. For example, the common locker 200 may transmit information required for authentication (e.g., information recognized by the code recognition unit 206) to the management device 10 (or the POS terminal 20), the management device 10 (or the 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 slot door based on the authentication result received from the management device 10 (or the POS terminal 20).

[0452] In the above embodiment, a locker as shown in FIG. 18 has been 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 a door like a clothing display rack). When a shelf type storage unit is installed in a store, for example, a user can enter the store during business hours and pick up his / her own products that have been returned to the shelf by himself / herself. This is convenient for both the user and the store clerk, as in the case of the locker type, because the user does not have to wait in line to receive the products when the store is crowded, and the store clerk does not have to deal with handing over the products when the products are placed on the shelf in advance. It is also possible to prevent the products from being taken away without permission. For example, when the products for one user are placed in a box or the like and placed on a shelf, a locking mechanism may be provided on the shelf itself, or between the shelf and the box, or on the box itself, so that the products cannot be taken out of the box and taken away unless the lock is released.

[0453] Furthermore, the storage unit may have a shape other than a locker or a shelf, such as a color box type or a hanger rack type from which hangers are hung. Note that even in the above types of storage units, it is possible to prevent unauthorized removal of products. For example, in the case of a hanger rack type, a locking function may be provided on the part from which the hangers are hung, so that the hangers cannot be removed from the rack unless the lock is released.

[0454] The lock function may be released, for example, in response to an operation by a store clerk or a member. For example, a shelf-type storage cabinet (or other types of storage cabinets) may be made recognizable so that the lock of the relevant portion (the portion storing the user's product) is released when the member card is read. Furthermore, a shelf-type storage cabinet (or other types of storage cabinets) may be provided with a communication function, and the store clerk may perform an unlocking operation (which may include an operation to specify the target for unlocking) on ​​the screen of the POS terminal 20 (or the store mobile terminal 30) so that the lock of the relevant portion (the portion designated by the store clerk, the portion storing the user's product) is released.

[0455] Also, a medium (receipt) for the user to return to the locker may be printed and issued. For example, in addition to the slips shown in Figs. 37 and 38, the POS terminal 20 may print and issue a medium on which a barcode (such as a barcode printed on the factory receipt shown in Fig. 38) that can be recognized in the return locker is printed when, for example, a user who does not have a cleaning app or a membership card requests a locker return. In addition to the barcode, the medium has information on the deposited product, settlement amount information, reservation date (receiving date), etc. printed on it. The medium is a return ticket, receipt ticket, and certificate ticket (certification information) for the locker return, and the user can receive the product by storing the medium from the store clerk when reserving the locker until the reservation date, and by having the return locker recognize the barcode on the medium on the reservation date, the user can pick up the product. In other words, the return locker recognizes the barcode and unlocks the return slot in which the user's product is stored based on the information coded in the barcode. Note that instead of a barcode, a 10-digit number, for example, may be printed on the medium, and the number on the medium may be entered into the return locker on the reserved day, allowing the user to collect the product from the return locker. Note that, in consideration of cases where the medium is lost, a password determined in advance for each user may be required to be entered in addition to recognizing the barcode (entering numbers, etc.) when unlocking the locker. In other words, the return locker may be configured to unlock the return opening by recognizing the barcode printed on the medium (entering the number printed on the medium) + entering the correct password.

[0456] In addition, in the cleaning system, an estimate or the like may be obtained before depositing the product. For example, a screen (for example, referred to as an estimate screen) having input (selection) fields for inputting (selecting) the type of product to be deposited, processing (drying, stain removal, etc.), quantity, etc. may be displayed on the user terminal 50, and the information entered by the user on the estimate screen may be transmitted to the management device 10. The management device 10 may refer to the information received from the user terminal 50, the product type file (FIG. 7(A)), the processing type file (FIG. 7(C)), the service basic file, etc., calculate a fee as an estimate, and transmit (response) it to the user terminal 50. In addition to or instead of the fee, the management device 10 may calculate the number of days required as an estimate, and transmit (response) it to the user terminal 50. In addition, the estimate screen may allow the user to input (select) the deposit date (the date the product is scheduled to be deposited), and the management device 10 may calculate the expected completion date as an estimate based on the deposit date and the required number of days, and transmit (response) it to the user terminal 50.

[0457] In addition, when locker return is selected on the user terminal 50 (for example, when a button for specifying locker return is provided on the estimate screen and the button is pressed), the management device 10 (or the POS terminal 50) may calculate the date when the locker can be returned as an estimate (for example, information such as that shown in Figures 23(B), 23(C), 23(E), and 23(F)) and send it (response) to the user terminal 50.

[0458] If the user checks the response (quote content) from the management device 10 and is satisfied, the information entered at the time of the quotation may be made available for use in a subsequent process (such as processing an actual reservation). For example, a reservation button (or a proceed button) may be provided on a screen displaying the quotation content (e.g., a quotation screen, or a screen different from the quotation screen), and when the user presses the reservation button, information indicating that the user is satisfied with the quotation content is transmitted from the user terminal 50 to the management device 10, and the management device 10 may transmit screen information of a reservation screen related to product deposit to the user terminal 50. The user terminal 50 may transmit information entered by the user on the reservation screen (information related to the deposit category, etc.) to the management device 10, and the management device 10 may execute reservation processing related to product deposit (such as updating various files) using information already received at the time of the quotation (type of product, processing, quantity, deposit date, etc.) and information received this time (at the time of the actual reservation) (information related to the deposit category, etc.). The customer code may be transmitted from the user terminal 50 to the management device 10 at least one of the timings of the estimate and the actual reservation. The contents input (selected) by the user on the reservation screen are, for example, the storage category (FIG. 5, etc.), such as normal store storage or quick storage. As described above, the information input at the time of the estimate can be directly used in the subsequent process, which is convenient. The information on the storage reservation is delivered to the POS terminal 20, and the store clerk can check the reservation contents on the POS terminal 50 and use it for various preparations (including mental preparation as well as actual preparation). The reservation screen for product storage may be called up without making an estimate (for example, directly from the membership card screen, etc.).

[0459] In the above embodiment, several screens (e.g., a slip details screen, a locker return reservation confirmation screen, etc.) have been described, but other screens may be displayed based on various information stored in the cleaning system. For example, based on the progress category of the stored item information file (FIG. 6), a screen for store staff to check the progress status (e.g., a list screen of items on hold, a list screen of users who are available for delivery but have not yet made the delivery) may be displayed.

[0460] Also, for example, performance information regarding locker reservations may be displayed based on the collection completion information described in FIG. 43. As an example, information indicating whether or not the product was actually received on each past locker reservation date (or whether or not the product that was stored without being returned by the locker was collected) 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 according to the weather at the installation location of the locker in question, instead of or in addition to the above. Also, when a user reserves a locker, the user's past performance (for example, history information such as the previous reservation on XX / XX was returned and the reservation on XX / XX before last was returned incomplete (collected)) may be displayed on the locker scheduled return date calendar screen or a screen displayed by pressing a predetermined button on the locker scheduled return date calendar screen.

[0461] As another example, the ratio of items actually received on each past locker reservation date (or the transition of the ratio) may be displayed by classifying it as described above (by locker, by user, etc.). Also, users with unfavorable track records (for example, users with the ratio lower than a first reference value set in advance) may be displayed in a list. The same applies to lockers with unfavorable track records. In order to improve the situation, for example, when a user with an unfavorable track record reserves a locker, the fact that the track record is unfavorable may be notified on the locker return date calendar screen or a screen displayed by pressing a predetermined button on the locker return date calendar screen, or a message to ensure that the item is properly received on the reservation date may be displayed. Also, the above-mentioned message may be sent to users with an unfavorable track record via a cleaning app, email, etc. on the day of the reservation date or the day before.

[0462] Users with favorable track records (for example, users with the above ratio higher than a preset second reference value) may be displayed in a list. The second reference value may be a value larger than the first reference value. Points may be awarded to users with favorable track records.

[0463] In addition, high points may be given to users who actually pick up the product early (on the day of the returnable date (scheduled completion date) or within a few days of the returnable date), and the points to be given thereafter may be gradually decreased according t...

Claims

1. A cleaning system including a storage device into which a user deposits laundry items, a management device, and a mobile terminal of the user, The depository device includes: An input door for inserting cleaning items; A reading means for optically reading identification information for identifying a user; an unlocking means for unlocking the input port door based on the reading by the reading means; Equipped with The management device includes: A transmission means for transmitting information regarding the laundry items that the user has placed in the deposit device to the mobile terminal. Equipped with The mobile terminal includes: A display means for displaying the identification information in an optically readable manner by a store clerk. A cleaning system comprising:

2. The identification information is information provided by the cleaning system.

2. The cleaning system of claim 1.

3. The method further includes a return device for allowing a user to pick up the laundry by himself / herself, The display means is 3. The cleaning system according to claim 1, further comprising an operator for accepting an operation to pick up the cleaning product at the return device.

4. The display means The cleaning items are displayed side by side, and a message is displayed indicating that the cleaning items to be picked up at the return device will be picked up at the return device.

4. The cleaning system of claim 3.

5. In a cleaning system including a storage device having an input door for inserting cleaning items and into which a user inserts the cleaning items themselves, a management device, and a user's mobile terminal having a display unit, said program causing a first computer to function as the storage device, a second computer to function as the management device, and a third computer to function as the mobile terminal, The first computer, A reading means for optically reading identification information for identifying a user; An unlocking means for unlocking the input port door based on the reading by the reading means. Functioning as a The second computer, A transmission means for transmitting information regarding the laundry items that the user has placed in the deposit device to the mobile terminal. Functioning as a The third computer, A display control means for displaying the identification information on the display unit in an optically readable manner by a store clerk. A program characterized by causing the program to function as a

6. A method for managing cleaning products in a cleaning system including a storage device having an input door for inserting cleaning products and into which a user inserts the cleaning products themselves, a management device, and a user's mobile terminal having a display unit, a reading step of optically reading, by the depository device, identification information for identifying a user; an unlocking step of unlocking the deposit slot door by the deposit device based on the reading by the reading step; a transmission step of transmitting information regarding the cleaning items that the user has placed in the deposit device to the mobile terminal by the management device; a display step of displaying the identification information by the mobile terminal so that the identification information can be optically read by a store clerk; Includes A cleaning management method.

Images