JP7344492B2 - Article management system, sales data processing device, program, and article management method - Google Patents

Description

The present invention relates to an article management system, a sales data processing device, a program, and an article management method.

For example, a cleaning product delivery system that includes a cleaning bag and a locker unit is known (see, for example, Patent Document 1).

Japanese Patent Application Publication No. 2007-296315

In the technology described in Patent Document 1, a cleaning product delivery service provider (trader) collects a cleaning bag containing clothes that has been placed in a locker unit by a customer (i.e., collects cleaning products before cleaning). ) and storing the cleaned items in the locker unit.
However, the above-mentioned collection work and storage work are manual work. For this reason, the business may forget to collect or store items such as cleaning products.

The present invention has been made in view of the above circumstances, and an object of the present invention is to enable traders to perform collection and storage operations of articles without forgetting them.

One aspect of the present invention for solving the above problems includes a storage means for storing articles to be stored or collected, and a schedule for collecting articles from the storage means or a schedule for storing articles in the storage means. A schedule storage means for storing a schedule, a determination means for determining the presence or absence of a predetermined event corresponding to collection or storage corresponding to the schedule stored by the schedule storage means, and notification based on a determination result by the determination means. This is an article management system comprising a notification control means for controlling the information.

One aspect of the present invention is to configure a computer in an article management system to include a schedule storage means for storing a schedule for collecting articles from a storage means for storing articles to be stored or collected or a schedule for storing articles in the storage means; Functions as determining means for determining the presence or absence of a predetermined event corresponding to collection or storage corresponding to the schedule stored by the schedule storage means, and notification control means for controlling so that notification is performed based on the determination result by the determining means. This is a program to do this.

One aspect of the present invention provides a schedule storage step for storing a schedule for collecting an article from a storage means for storing the article to be stored or collected or a schedule for storing the article in the storage means; An article management method comprising: a determination step of determining the presence or absence of a predetermined event corresponding to collection or storage corresponding to a scheduled schedule; and a notification control step of controlling so that notification is performed based on the determination result of the determination step. be.

According to the present invention, it is possible to obtain the effect that a trader can perform the work of collecting and storing goods without forgetting them.

FIG. 1 is a configuration diagram of a cleaning system in this embodiment. It is a figure showing an example of the appearance of a locker in this embodiment. It is a diagram showing an example of the configuration of a POS terminal in this embodiment. It is a figure showing an example of composition of a locker (locker for reception only) in this embodiment. It is a diagram showing an example of the configuration of a locker (dedicated return locker) in this embodiment. It is a diagram showing an example of the configuration of a management device in this embodiment. It is a flowchart which shows the example of a processing procedure at the time of product deposit in this embodiment. This is an example of a membership card screen in this embodiment. It is an example of a slip list screen in this embodiment. This is an example of a slip details screen (deposit slip screen, electronic deposit slip) in this embodiment. This is an example of various information stored in the cleaning system according to the present embodiment. This is an example of various information stored in the cleaning system according to the present embodiment. This is an example of various information stored in the cleaning system according to the present embodiment. This is an example of various information stored in the cleaning system according to the present embodiment. It is an example of the information which the cleaning system in this embodiment stores. It is a flowchart which shows the example of a process procedure regarding the identification method of the reservation possible date in this embodiment. This is an example of a locker return reservation screen displayed on the clerk side display section of the POS terminal in this embodiment. This is an example of a customer-side locker return reservation screen displayed on the customer-side display section of the POS terminal in this embodiment. This is an example of a locker return reservation screen displayed on the clerk side display section of the POS terminal in this embodiment. It is an example of the information which the cleaning system in this embodiment stores. This is an example of a slip details screen (deposit slip screen, electronic deposit slip). 2 is a flowchart illustrating an example of a processing procedure when reserving a locker in the present embodiment. 2 is a flowchart illustrating an example of a processing procedure when reserving a locker in the present embodiment. This is an example of a locker return schedule list screen according to the present embodiment. This is an example of a locker return schedule list slip in this embodiment. It is a flowchart showing an example of a processing procedure executed by the reception-only locker and the management device in the present embodiment. It is a flowchart showing the processing procedure performed by the return-only locker in this embodiment. It is a flowchart showing the processing procedure performed by the return-only locker in this embodiment. 12 is a flowchart illustrating an example of a processing procedure executed by the management device and the POS terminal in the present embodiment in connection with notification that a product has not been stored. It is a figure which shows the example of an aspect of a non-storage notification screen in this embodiment. 12 is a flowchart illustrating an example of a processing procedure executed by the management device according to the present embodiment in connection with notification that a product has not been stored. It is a figure which shows an example of a storage error notification screen in the modification of this embodiment. It is a figure which shows an example of a storage error list slip in the modification of this embodiment. It is a figure showing an example of a reservation form setting screen in a modification of this embodiment. It is an example of a locker return schedule list screen in a modified example of this embodiment. It is a figure which shows an example of the deposit slip in the modification of this embodiment. It is a figure showing an example of a customer information combination screen in a modification of this embodiment.

<Embodiment>
[Example of schematic configuration of cleaning system]
FIG. 1 schematically shows a configuration example of a cleaning system according to an embodiment (hereinafter referred to as embodiment) of the present invention. The cleaning system 1 of this embodiment is a system that supports cleaning operations. In cleaning services, cleaning service users (customers) entrust clothing and other items (hereinafter also referred to as products) to be cleaned, the entrusted products are cleaned at a factory, etc., and the cleaned products are used. This is done by returning the item to the person responsible. For example, the trader receives a fee from the user as compensation for cleaning the product.
In the following explanation, the terms "customer" and "user" will be used synonymously.

The cleaning system 1 includes a management device 10, a POS terminal (business terminal) 20, a store mobile terminal 30 (business terminal), a factory terminal 40, a user terminal 50, and a locker (an example of storage means).
The management device 10, POS terminal 20, factory terminal 40, user terminal 50, and lockers (100, 200, 300) are connected to a network 90.
The network 90 is not particularly limited. For example, the network 90 may utilize a wireless LAN, a mobile phone network, the Internet, or the like. The store mobile terminal 30 can communicate with the POS terminal 20, for example, via wireless LAN.

The management device 10 is, for example, a server that manages and provides various information regarding the cleaning system 1. As an example, the management device 10 may be a cloud server that provides various cleaning-related services. Note that the management device 10 may be able to perform push-type communication (notification) to other devices (for example, the user terminal 50).
Furthermore, the management device 10 may or may not have a display section or an operation section.
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), other devices (for example, a personal computer, etc.) that can communicate with (connect to) the management device 10. Maintenance and the like of the management device 10 may also be performed via a computer (not shown).

The POS terminal 20 is installed at a cleaning shop (cleaning agency) and operated by an employee of the cleaning shop. The POS terminal 20 may be installed at a private store (a cleaning shop run by an individual) or at a chain store (each store in a chain).
That is, the cleaning system 1 is applicable to both individual stores and chain stores.
The store mobile terminal 30 is, for example, a tablet terminal used in the cleaning store. Furthermore, the POS terminal 20 may be a store other than a cleaning store, such as a convenience store, that handles products to be cleaned.

For example, the POS terminal 20 is used for registering items entrusted to customers, accounting processing, etc., and the store mobile terminal 30 displays a list of items to be delivered to customers, and a store clerk moves to the backyard to pick up the items to be delivered. It can be used for different purposes, such as when taking out the item.
Note that, for example, the POS terminal 20 may be configured as a portable type. In this case, the POS terminal 20 may also have the function of the store mobile terminal 30.

The factory terminal 40 is installed in a cleaning factory and operated by a person in charge of the 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.

The user terminal 50 is a terminal operated by a user (for example, a smartphone, a tablet terminal, a personal computer, etc. owned by the user). The user terminal 50 may be configured to be able to download and install an application program from the management device 10 and a device (server (not shown)) different from the management device 10 via the network 90 .
In the present embodiment, an application program (hereinafter sometimes simply referred to as a "cleaning app") for users who use a cleaning shop (various services related to cleaning) in the cleaning system 1 is installed on the user terminal 50, and It is assumed that membership registration has been completed using the cleaning app.
The cleaning application may include data regarding various screens and various messages displayed on the display unit of the user terminal 50. Additionally, in addition to starting, running, and ending in response to user operations, cleaning apps also start, run, and end in response to requests from other programs (application programs and OS (Operating System)). There may be cases. For example, the cleaning app resides on the user terminal 50 without displaying a screen, monitors whether information transmitted from another device (for example, the management device 10, etc.) is received, and when the information is received, Alternatively, a screen corresponding to the received information may be displayed on the display unit without any operation by the user.

FIG. 2 shows an example of the appearance of the locker. The lockers used in the cleaning system 1 are divided into a locker used for depositing products (i.e., a locker used for locker reception) and a locker used for delivering products (i.e., a locker used for returning the locker). be.
FIG. 2(A) shows a dedicated locker (hereinafter sometimes referred to as a reception-only locker) 100 that is used only at locker reception.
FIG. 2(B) shows a locker (hereinafter sometimes referred to as a common locker) 200 used for both locker reception and locker return.
FIG. 2C shows a dedicated locker (hereinafter sometimes referred to as a return-only locker) 300 that is used only for returning the locker.

[Locker for reception only]
For example, as shown in FIG. 2A, the reception-only locker 100 includes an input slot 101 for inserting products, a collection section 102 for collecting the products inserted from the input slot, and a card insertion slot for inserting and ejecting cards. A discharge port 103, a display section 104 that displays various information, an input operation section 105 that accepts input operations, a code recognition section 106 that reads and recognizes barcodes, an issue port 107 that issues media such as receipts, and a storage section ( (not shown), a control unit (not shown) that controls the display on the display unit 104, the locking of the slot door (described later), etc.
Note that the reception-only locker 100 does not necessarily have to have all the configurations described above. For example, it is possible to include one of the input operation section 105 and the code recognition section 106, but not the other.

The input port 101 is provided with a curtain-shaped door (hereinafter referred to as the input port door). The input door can be locked. When the slot door is unlocked, the user can put a product (product to be deposited) into the slot 101. On the other hand, when the slot door is locked, the user cannot insert products into the slot 101. The input door is normally locked, unlocked when a predetermined condition is met, and locked again after the product is loaded.

Various conditions can be considered as the predetermined conditions for unlocking the input port door. For example, authentication is performed based on one or both of the information on the card inserted into the card insertion/ejection port 103 (e.g., membership card, etc.), and the information inputted into the input operation section 105 (e.g., a PIN number, etc.). If the authentication is OK, the slot door may be unlocked. In addition, authentication is performed based on information recognized by the code recognition unit 106 (for example, barcode G11 displayed on the membership card screen, information on the barcode printed on the membership card, etc.), and if the authentication is OK, the input is performed. You may unlock the entrance door. Alternatively, authentication may be performed based on the information recognized by the code recognition unit 106 and the information input to the input operation unit 105, and the slot door may be unlocked if the authentication is OK.

Various methods can be considered to recognize the introduction of a product. For example, a sensor that can detect whether the input slot door is in its normal state (the surface is vertical due to its own weight) (in other words, whether the input slot door is pushed toward the back) or not. By providing a sensor capable of detecting whether or not the product has been inserted, the insertion of the product may be recognized based on the detection result of the sensor. In addition, after the product is loaded, the slot door that was pushed to the back will return to its original state (normal state) due to its own weight, but after returning to its original state, it will remain in its original state for a predetermined period of time (if the same user Even if there are multiple loading operations, the time period (for example, 10 seconds) during which all input operations are considered to have been completed, the input port door may be locked (automatically locked).

A basket with casters can be accommodated in the recovery section 102. In other words, the products inserted into the input port 101 are arranged to fit inside the basket equipped with casters. Moreover, the products (basket with casters) in the collection section 102 can be taken out from either the front or the back.

The collection unit 102 is provided with a door (hereinafter referred to as a collection unit door) at a position where the products can be taken out. The collection section door can be locked. When the collection section door is unlocked, a store clerk or the like can take out a product (cart with casters) from the collection section 102. On the other hand, when the collection section door is locked, a store clerk or the like cannot take out products from the collection section 102. The input door is normally locked, unlocked with a key controlled by a store clerk, and locked again after the product is taken out.

It has been explained that the products in the collection section 102 (baskets with casters) can be retrieved from both the front and the back. If communication is established, the cart with casters can be taken out inside the store, which eliminates the need to move the cart with casters taken out outside the store into the store. In other words, if the reception locker 100 is 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. Able to work efficiently.

In addition, inside the store (back side), products put into the input slot from outside the store (front side) are automatically processed (such as preparations such as putting a cart with wheels into the collection section 102, and loading a cart with wheels loaded with products). It may also be possible to collect them without having to take them out from the collection unit 102.
For example, the bottom of the collection section 102 may be sloped so that products placed from outside the store naturally move to the inside of the store, and the inside of the store may simply be an opening without providing a collection door. As a result, products inserted from outside the store automatically slide into the opening inside the store, so there is no need to worry about the capacity (volume) of the collection section 102 (for example, users can insert products at any time). can do.
Furthermore, the store clerk no longer has to take out appropriate products from the collection section 102).
Note that a large basket with casters or the like may be placed under the opening to catch items that slip through the opening.

In addition, in order to make it easier for products to move inside the store, the sloped part (bottom) may be made of a slippery material (a material with a small coefficient of friction) (the surface may be plated, coated, etc. to make it slippery). ). Further, instead of or in addition to the material (including coating, etc.), a rotating body may be used. For example, a cylindrical object (roller) or a spherical object may be embedded in a part of the inclined part, or it may be embedded in the entire inclined part (rollers or balls may form the surface of the inclined part). ).

Note that the recovery unit door may be unlocked when a predetermined condition is met, like the input port door provided in the input port 101, instead of using a key.

Various conditions can be considered as the predetermined conditions for unlocking the collection section door. For example, any of the information on the card inserted into the card insertion/ejection slot 203 (e.g., an administrator card managed by a store clerk, etc.), or the information input into the input operation section 105 (e.g., a PIN number, etc.) Authentication may be performed based on one or both, and the collection door may be unlocked if the authentication is OK. In addition, for further security, the collection department door may be unlocked using a key managed by a store clerk or the like together with the above-mentioned authentication.

Note that the reception locker 100 may be able to communicate with other devices (for example, the POS terminal 20, the management device 10, etc.). That is, the reception-only locker 100 may include a communication section (not shown).

The management device 10 communicatively connected to the reception locker 100 periodically (for example, every day) generates information (PIN code) to be input into the input operation section 105 and sends the generated information to the user terminal 50. It may also be sent to the reception locker 100.
In other words, as a predetermined condition for unlocking the slot door, the user inputs the information confirmed on the user terminal 50 (the password generated on the management device 10) into the input operation section 105, and then enters the reception locker 100. may perform authentication by comparing the information transmitted from the management device 10 and the information input to the input operation unit 105.
As a specific example, the management device 10 periodically (for example, every day) generates information (PIN code) to be input into the input operation unit 105, and transmits the generated information to the POS terminal 20 and the reception locker 100. It's okay. In other words, as a predetermined condition for unlocking the collection department door, a store clerk or the like enters information confirmed on the POS terminal 20 (or store mobile terminal 30) (such as a password generated on the management device 10) into the operation section. 105, and the reception locker 100 may compare the information transmitted from the management device 10 with the information input to the input operation section 105 and perform authentication.

Further, when the reception locker 100 can communicate with other devices, the POS terminal 20 generates an OTP and sends a barcode obtained by converting the OTP into a barcode as a predetermined condition for unlocking the collection door. A medium with the barcode printed on it (medium for opening the collection department door) is issued, and the OTP is sent to the reception locker 100 (sent to the reception locker 100 via the management device 10, or directly) , to the reception locker 100). The reception locker 100 uses information recognized by the code recognition section 106 (specifically, OTP obtained from the barcode printed on the medium for opening the collection section door) and information received from the outside (POS terminal 20 or management Authentication may be performed based on the OTP received from the device 10.

Furthermore, if the reception-only locker 100 can communicate with another device, the reception-only locker 100 may request the other device for authentication and obtain the authentication result from the other device. Note that when requesting authentication from another device, the reception locker 100 provides information necessary for the other device to perform the authentication (for example, information about the card inserted into the card insertion/ejection port 103, input operation section 105, information recognized by the code recognition unit 106, etc.) is transmitted to the other device.

[Common locker]
For example, as shown in FIG. 2(B), the common locker 200 includes an input port 201, a collection section 202, a card insertion/ejection port 203, a display section 204, an input operation section 205, a code recognition section 206, an issuing port 207, and a memory. (not shown), a control unit (not shown) that controls the display on the display unit 204 and the locking of the return door (described later), a plurality of return ports (return units) 210, and a panel unit 210a corresponding to the return port. Be prepared. Note that the input port 201, collection section 202, card insertion/output port 203, display section 204, input operation section 205, code recognition section 206, and issuing port 207 of the common locker 200 are the same as the input port 101 and collection section of the reception-only locker 100. 102, card insertion/ejection port 103, display section 104, input operation section 105, code recognition section 106, and issuance port 107, so description thereof will be omitted. Note that the common locker 200 does not necessarily have all the configurations described above. For example, it is possible to include one of the input operation section 205 and the code recognition section 206, but not the other.

Note that the common locker 200 may be able to communicate with other devices (for example, the POS terminal 20, the management device 10, etc.). That is, the common locker 200 may include a communication section (not shown).

The common locker 200 shown in FIG. 2(B) includes a total of 11 return ports 210 out of six rows of two upper and lower rows, excluding the panel portion 210a of the first row on the left in the upper row. In FIG. 2(B), 11 return ports are represented, and the return port at the lower left end is designated by the reference numeral 210. Note that each return slot is set with a return slot number (sometimes referred to as a "door number") as a management number. For example, specifically, as shown in FIG. 2(B), the return slot numbers are "H12" at the bottom left, "H21" at the top of the second row from the left, "H22" at the bottom of the second row from the left, ..., the upper right end is "H61", and the lower right end is "H62".
The return port units in the common locker 200 in FIG. 2(B) include units including return ports with return port numbers H12, H21, H22, H31, and H32, and return port units with return port numbers H41, H42, H51, H52, H61, and H62. An example is shown in which two units including a return port for the return number are connected.
Note that the return number of each return port may be known in the common locker 200 by attaching a sticker or the like indicating the return port number to each return port.

Each of the return ports 210 is provided with a door (hereinafter referred to as a return port door). Each return door can be individually locked. When the return door is unlocked, a store clerk or the like can store the product (product to be returned to the user) in the return port 210. Furthermore, when the return door is unlocked, the user can take out the product from the return door 210. On the other hand, when the return door is locked, the user cannot take out the product from the return door 210.
Furthermore, when the return door is locked, a store clerk or the like cannot store the product in the return port 210. The return door is normally locked, and is unlocked when a predetermined condition is met. Please note that the store is locked after storing or taking out the products.

Various conditions can be considered as the predetermined conditions for unlocking the return door.
[Predetermined conditions when storing products (when unlocking by store staff, etc.)]
For example, if authentication is 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 the locker), and the authentication is OK, this applies. You may unlock the return door (the return door for storing the product to be returned to the user). Note that details of the unlocking method will be described later. In place of or in addition to the above unlocking method, for example, as in the case of unlocking the collection section door, a card inserted into the card insertion/ejection port 203 (for example, an administrator card managed by a store clerk, etc.) may be used. ), the information entered into the input operation unit 205 (for example, a PIN number, etc.), or both may be used for authentication, and if the authentication is OK, the return door may be unlocked. .

[Predetermined conditions when taking out the product (when the user unlocks it)]
For example, as in the case of unlocking the slot door, either the information of the card (membership card, etc.) inserted into the card insertion/output slot 203 or the information entered into the input operation section 205 (PIN number, etc.) Authentication may be performed based on one or both, and if the authentication is OK, the corresponding return door (the return door of the return door containing the product to be returned by the user) may be unlocked. In addition, authentication is performed based on the information recognized by the code recognition unit 206 (barcode G11 displayed on the membership card screen, information on the barcode printed on the membership card, etc.), and if the authentication is OK, the slot is opened. may be unlocked. Alternatively, authentication may be performed based on the information recognized by the code recognition unit 206 and the information input to the input operation unit 205, and the slot door may be unlocked if the authentication is OK. In order to further ensure safety, authentication is performed based on information on the card inserted into the card insertion/ejection port 203, information input into the input operation section 205, and information recognized by the code recognition section 206. If the authentication is OK, the slot door may be unlocked.

Various methods can be considered to recognize the removal of the 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 open or not) is provided. In this way, removal of the product may be recognized based on the detection result of the sensor. Note that after the product is removed, the return door may be returned to its original state (normal state) by a biasing force or the like. In addition, if the original state is maintained for a predetermined period of time after returning to the original state (a time period during which all retrieval operations can be considered completed even if there are multiple retrieval operations by the same user; for example, 1 minute), The return door may be locked (automatically locked).

Note that a light emitting section corresponding to each return port 210 may be provided. For example, in the example shown in FIG. 2(B), a light emitting section 211 is provided above each return port 210. Additionally, a bar, hook, or the like may be provided in the return port 210 in order to neatly store the product.

Note that although the common locker 200 shown in FIG. 2(B) has 12 return slots, the number of return slots for the common locker 200 may be other than 12.

[Return locker]
The return locker 300 includes, for example, a card insertion/ejection port (not shown), a display section (not shown), an input operation section (not shown), a code recognition section (not shown), an issuance port (not shown), and a storage section ( (not shown), a control unit (not shown) that controls display on a display unit, locking of a return door (described later), etc., and a plurality of return ports (return units) 310. In the case of the return-only locker 300 shown in FIG. 2(C), the card insertion/ejection port, display section, input operation section, code recognition section, issuing port, etc. are arranged in the panel section 301a of the upper left 301. However, for convenience of the drawing, illustration of each is omitted.

Note that a light emitting section corresponding to each return port 310 may be provided. For example, in the example shown in FIG. 2C, a light emitting section 311 is provided above each return port 310. Further, a bar, a hook, or the like may be provided in the return port 310 in order to neatly store the product.

Note that although the number of return slots of the return-only locker 300 shown in FIG. 2(C) is five, the number of return slots of the return-only locker 300 may be other than five.

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

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

The communication unit 24 communicates via a network. Thereby, the POS terminal 20 can communicate with, for example, other POS terminals and management devices installed in stores, as well as terminal devices and servers installed in headquarters and the like. Furthermore, the communication unit 24 may be capable of short-range wireless communication, for example. Thereby, the POS terminal 20 can communicate with the store mobile terminal 30 owned by a store clerk or the like via short-range wireless communication. Furthermore, the POS terminal 20 and the user terminal 50 carried by the user at the store may be able to communicate via short-range wireless communication.

The input unit 25 is a part that receives various inputs to the POS terminal 20. The input unit 25 may include operators such as physical keys and buttons provided in the POS terminal 20. Furthermore, when the display sections (clerk side display section 26, customer side display section 27) are configured as a touch panel, the input section 25 may include a touch pad arranged on the display surface of the display section.
Furthermore, the input unit 25 may include a scanner that reads code information and the like, a card reader that reads information from various cards, and the like.

The clerk-side display section 26 is provided in the POS terminal 20 so that the clerk operating the POS terminal 20 can view the display, and displays various information under the control of the CPU 21 .

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

Note that the clerk-side display section 26 and the customer-side display section 27 may be external display devices connected to the main body of the POS terminal 20, for example, by wire or wirelessly. In this case, the external display device may have a display surface configured as a touch panel, for example, so that the display surface can be operated.

The printing unit 28 prints on the loaded paper. In this embodiment, the printing unit 28 can print a store copy slip, a factory copy slip, a customer copy slip, etc. at the time of checkout. That is, the issuance of various slips by the POS terminal 20 is realized by the printing unit 28 printing.

[Example of configuration of reception locker]
A configuration example of the reception locker 100 will be described with reference to FIG. 4. In this figure, the same parts as those in FIG. 2(A) are given the same reference numerals, and the description thereof will be omitted as appropriate.
The reception locker 100 shown in the figure includes a CPU 121, a RAM 122, a storage section 123, a communication section 124, a card reader 125, a printing section 126, and a collection section sensor 127.
The CPU 121 is a central processing unit of the reception-only locker 100, and reads the program stored in the storage unit 123, expands it to the RAM 122, and executes each step of the expanded program, thereby controlling the operation of the reception-only locker 100. control.
The RAM 122 is the main storage device of the reception locker 100, and stores information used by the CPU 121 for calculations.
The storage unit 123 is an auxiliary storage device of the reception-only locker 100 and stores various information corresponding to the reception-only locker 100.
The communication unit 124 communicates via a network. Thereby, the reception-only locker 100 can communicate with, for example, the management device 10 and the like. Furthermore, the communication unit 124 may be capable of short-range wireless communication, for example. In this case, the reception locker 100 may be able to communicate with a store mobile terminal 30 owned by a store employee or the like, a user terminal 50 owned by a user, etc. in the vicinity via short-range wireless communication.

The card reader 125 reads information on the card inserted into the card insertion/ejection port 103.
The printing unit 126 prints on the loaded paper to eject a slip such as a receipt from the issuing port 107 .
The collection unit sensor 127 detects a predetermined state of the collection unit 102 . For example, the collection unit sensor 127 may detect the state of the collection unit door (eg, open/closed, locked, unlocked, etc.). Further, the collection unit sensor 127 may detect the volume, weight, etc. of the articles stored in the collection unit 102.

[Example of configuration of return locker]
A configuration example of the return locker 300 will be described with reference to FIG. 5. In this figure, the same parts as those in FIG. 2(C) are given the same reference numerals, and the description thereof will be omitted as appropriate.
The reception locker 100 shown in the figure includes a CPU 321, a RAM 322, a storage section 323, a communication section 324, a card reader 325, a printing section 326, and a return port sensor 327.
The CPU 321 is a central processing unit of the return-only locker 300, and reads a program stored in the storage unit 323, expands it to the RAM 322, and executes each step of the expanded program, thereby controlling the operation of the return-only locker 300. control.
The RAM 322 is the main storage device of the return locker 300, and stores information used by the CPU 321 for calculations.
The storage unit 323 is an auxiliary storage device of the return locker 300 and stores various information corresponding to the return locker 300.
The communication unit 324 communicates via a network. Thereby, the return locker 300 can communicate with, for example, the management device 10 and the like. Further, the communication unit 324 may be capable of short-range wireless communication, for example. In this case, the return locker 300 may be able to communicate with a store mobile terminal 30 owned by a store employee or the like, a user terminal 50 owned by a user, etc. in the vicinity via short-range wireless communication.

The card reader 325 reads information on a card inserted into a card insertion/ejection opening provided in the panel section 301a.
The printing unit 326 prints on the loaded paper to eject a slip such as a receipt from, for example, an issuing port provided in the panel unit 301a.

The return port sensor 327 is provided corresponding to each return port 310 and detects a predetermined state of the corresponding return port 310. For example, the return port sensor 327 may detect the state of the collection door (eg, open/closed, locked, unlocked, etc.). Further, the collection unit sensor 127 may detect the weight of the article stored in the collection unit 102.

Note that the common locker 200 may have a configuration in which the configurations of FIGS. 4 and 5 are combined. When combining the configurations of FIGS. 4 and 5, parts having the same functions may be shared as appropriate.

[Example of configuration of management device]
A configuration example of the management device 10 will be described with reference to FIG. 6. The management device 10 in the figure includes a CPU 11, a RAM 12, a storage section 13, and a communication section 14.
The CPU 11 is a central processing unit of the management device 10, and controls the operation of the management device 10 by reading a program stored in the storage unit 13, loading it into the RAM 12, and executing each step of the loaded program. do.
The RAM 12 is a main storage device of the management device 10, and stores information used by the CPU 11 for calculations.
The storage unit 13 is an auxiliary storage device of the management device 10, and stores various information corresponding to the management device 10.
The communication unit 14 communicates via a network. Thereby, the management device 10 can communicate with the POS terminal 20, the factory terminal 40, the user terminal 50, the lockers (100, 200, 300), and the like.

Note that the management device 10 may also be provided with an operation section and a display section. In this case, the management device 10 may be able to perform the same operations as the store clerk can perform on the POS terminal 20. Along with this, various screens similar to those displayed on the POS terminal 20 may be displayed on the display unit of the management device 10.

Next, with reference to FIGS. 7 to 10, the basic processing performed by the cleaning system 1 when depositing goods will be described. Note that in the description of FIGS. 7 to 10, the case where the user terminal 50 is a smartphone will be taken as an example.

FIG. 7 is a flowchart illustrating an example of a processing procedure for operations during product deposit. Specifically, the flowchart of FIG. 7 shows an example of the operation when a product is left by a user (member) who visits a store (cleaning store) (that is, in the case of regular store deposit).

8 to 10 are examples of various screens displayed on the user terminal 50. Specifically, FIG. 8 shows a membership card screen, FIG. 9 shows a slip list screen, and FIG. 10 shows a slip details screen (sometimes referred to as a deposit slip screen or an electronic deposit slip). In the description of FIGS. 7 to 10, the cleaning app executed on the user terminal 50 (smartphone) displays the above screens (membership card screen, slip details screen, slip list screen).

Each step in the flowchart of FIG. 7 will be described below with reference to FIGS. 8 to 10 as appropriate.
Step S10: The user terminal 50 displays a membership card screen as shown in FIG. 8 on the display unit (touch panel). The membership card screen may be the initial screen of the cleaning app. That is, the membership card screen may be the first screen displayed on the display unit when the cleaning app is started on the user terminal 50. The user terminal 50 may display the membership card screen stored by itself on the display section, or may acquire the membership card screen from the management device 10 and display it on the display section.

Note that when acquiring the membership card screen from the management device 10 and displaying it on the display unit, the user terminal 50 may send application communication identification information (or application user identification information) to the management device 10. good. That is, the user terminal 50 may acquire the membership card screen from the management device 10 and display it on the display unit by transmitting the application communication identification information (or application user identification information) to the management device 10. . Note that the management device 10 refers to the customer master file, identifies the user (customer code) based on the application communication identification information (or application user identification information) acquired from the user terminal 50, and The user's membership card screen may be transmitted to the user terminal 50.

The membership card screen shown in FIG. 8 displays rank information, point information (number of available points), barcode G11, deposit slip icon G12, and the like. The barcode G11 is a customer code converted into a barcode. The barcode G11 displayed on the membership card screen of a certain user may be generated by the management device 10 based on the customer code of the user. For example, the management device 10 assigns (numbers) a customer code at the time of membership registration, generates a barcode based on the assigned customer code, and stores it as a barcode to be displayed on the membership card screen of the user. You can stay there.

"Membership Card," "Deposit Slip," "Notice," "Coupon," and "Survey" in a horizontal line at the bottom of the membership card screen indicate the type of screen currently being displayed. The same applies to the bottom row of the slip list screen shown in FIG. 9 and the slip details screen shown in FIG. Note that the slip list screen and slip details screen are classified as "deposit slips" when the screens are classified into five categories: "membership card," "deposit slip," "notice," "coupon," and "questionnaire." Both when the list screen is displayed (FIG. 9) and when the slip details screen is displayed (FIG. 10), it is referred to as a "deposit slip".

Step S11: The POS terminal 20 reads the barcode on the membership card screen by the operation (action) of the store clerk. Thereby, the POS terminal 20 recognizes the customer code of the user who has visited the store.
Step S12: The POS terminal 20 transmits the customer code recognized by reading the barcode to the management device 10.

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

Step S16: The POS terminal 20 receives customer information from the management device 10.
Step S17: The POS terminal 20 displays the customer information received in step S16 on the clerk side display section 26.

Note that the POS terminal 20 may display a registration screen (not shown) on the clerk side display section 26 based on receiving the customer information in step S16, and display the customer information on the registration screen in step S17. . Alternatively, the POS terminal 20 displays a customer information display screen (not shown) different from the registration screen on the clerk side display section 26 based on the reception of the customer information in step S16, and displays a customer information display screen (not shown) different from the registration screen in step S17. Customer information may be displayed on the screen.

Note that the customer information displayed by the POS terminal 20 in step S17 may be part of the information stored in a customer master file or the like. In other words, the POS terminal 20 may display part of the information stored in the customer master file or the like. Further, in step S14, the management device 10 may extract only the information displayed by the POS terminal 20 in step S17.

Note that if the POS terminal 20 stores the customer information displayed in step S17, there is no need to make an inquiry to the management device 10 (that is, the processes in steps S12 to S16 may be omitted).

Step S18: The POS terminal 20 registers the deposited product through the operation of the store clerk. Specifically, for example, on the registration screen, the POS terminal 20 receives input of information regarding each deposited product (product type, processing type), the tag number of the tag attached to each deposited product, and the like.
Note that if the customer information is displayed on the customer information display screen instead of the registration screen in step S17, information regarding each deposited product (product type, processing type) is displayed after the registration screen is displayed by the clerk's operation. It also accepts inputs such as the tag number attached to each deposited item.

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 required number of days for each deposited product, calculates the expected completion date of each deposited product based on the obtained required number of days, and calculates the expected completion date of each deposited product. The scheduled finishing date of each deposited item is displayed on the clerk side display section 26.
In addition, instead of or in addition to the scheduled finishing date of each deposited product, the POS terminal 20 displays the latest scheduled finishing date of the scheduled finishing dates of each deposited product (that is, the scheduled finishing date when all the deposited products are finished). may be displayed on the clerk side display section 26.

Note that 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 that stores the service basic file about the number of days required for each deposited product. If 20 stores the service basic file, the above inquiry is unnecessary.

Step S20: The POS terminal 20 settles the price. Specifically, the POS terminal 20 refers to the service basic file, obtains the charge for each deposited product, calculates the total charge by adding up the obtained charges for each deposited product, and calculates the total charge for each deposited product. At the same time, the total charge is displayed on the clerk side display section 26.
Subsequently, the POS terminal 20 recognizes the deposited amount through the clerk's operation (inputting a number according to the deposited amount), and calculates the amount of change from the total charge and the deposited amount. Then, the POS terminal 20 displays the deposited amount and the amount of change on the clerk side display section 26 (the payment is completed). The clerk checks the amount of change displayed on the clerk side display section 26, takes out the change, and hands it to the user.

Note that in step S20, if the POS terminal 20 does not store the service basic file, it is necessary to inquire about the fee for each deposited product from the management device 10 that stores the service basic file. If the service basic file is stored in the service basic file, the above inquiry is unnecessary.

In addition, in step S20, if the POS terminal 20 is equipped with an automatic change/bill machine (or if the automatic change/bill machine is connected to the POS terminal 20), the POS terminal 20 is configured to handle the total charge, etc. is displayed on the clerk side display section 26, the deposit amount is recognized by the clerk's operation (inserting the deposit into the coin slot of the automatic change tag machine), and the change amount is calculated from the total charge and the deposit amount. Then, the POS terminal 20 displays the deposited amount and the amount of change on the clerk side display section 26, and discharges the change into the money outlet of the automatic change and tag machine (the payment is completed).

Note that the POS terminal 20 prints and issues a receipt slip, a factory copy, etc. in step S20.

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 product, through the operation of the store clerk. For example, the POS terminal 20 displays the slip number, the date and time of deposit, the store code, the clerk code, the customer code, the deposit category (specifically, the deposit category "1 (regular store deposit)"), the tag number of each deposited product, and the product. Transaction information including the type, processing type, etc. is transmitted to the management device 10.
Note that the slip number may be assigned (numbered) by the POS terminal 20. The store code and the clerk code are stored in the storage unit (RAM 22 or storage unit 23) of the POS terminal 20. The clerk code is stored in the storage section of the POS terminal 20 by the clerk's operation (for example, inputting the clerk code, reading the clerk's card using a card reading device (not shown), etc.).

Note that although the number of deposited items is stored in the electronic slip file (see FIG. 12), the management device 10 stores the number of deposited items based on the number of items (for example, the number of tag numbers) sent from the POS terminal 20. It is possible to recognize the number of points deposited. Therefore, the POS terminal 20 does not need to transmit the number of deposited points to the management device 10. That is, the POS terminal 20 may transmit transaction information that includes the number of deposited points, or may transmit transaction information that does not include the number of deposited points. Similarly, the POS terminal 20 may transmit transaction information that includes the total fee, or may transmit transaction information that does not include the total fee.

Furthermore, although the deposited product number is stored in the deposited product information file (see Figure 13), the management device 10 can assign (number) the deposited product number based on the slip number and the number of deposited items. be. Therefore, it is not necessary for the POS terminal 20 to assign a deposited product number to each deposited product and send it to the management device 10. That is, the POS terminal 20 may transmit transaction information that includes the deposited product number of each deposited product, or may transmit a transaction that does not include the deposited product number of each deposited product.

In addition, information regarding delivery reservations (reservation classification, delivery classification) is stored in the deposited product information file (see FIG. 13). If there is an input of information), the POS terminal 20 transmits transaction information including input information regarding the delivery to the management device 10.

Step S22: The management device 10 receives transaction information at the time of product deposit from the POS terminal 20.
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. Note that when the management device 10 receives transaction information including input information regarding a specific product, it also updates the specific product management file.

Step S24: The management device 10 updates the document list screen based on the transaction information received in step S22 (that is, referring to the various files updated in step S23) (screen information such as adding a document). ).

Step S25: The management device 10 generates a document details screen (generates screen information of the document to be added) based on the transaction information received in step S22 (that is, referring to the various files updated in step S23). do).

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

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. The flowchart of FIG. 7 then ends.

Note that the work of attaching tags to each deposited product takes time, so if this work is postponed, the input of the tag number in step S18 is also postponed. In step S21, it is necessary to transmit transaction information including the tag number to the management device 10, so the processing in step S21 is also postponed. That is, in the processing of steps S10 to S27 described above, the processing up to step S20 is executed (in the processing of step S18, the input of the tag number is suspended, the process is temporarily ended and the process proceeds to step S19), and the process immediately proceeds to step S21. First, after executing the remaining processing of step S18 (inputting the tag number), the processing may proceed to step S21 and subsequent steps.

Here, the transition between the membership card screen in FIG. 8, the slip list screen in FIG. 9, and the slip details screen in FIG. 10 will be described.
When the deposit slip icon G12 is operated (tapped, etc.) on the membership card screen shown in FIG. 8, the user terminal 50 displays a slip list screen as shown in FIG. The slip list screen displays a list of slips for all stores.

Furthermore, when the electronic slip column G21 in the third row from the top is operated on the slip list screen shown in FIG. 9, the user terminal 50 displays a slip details screen as shown in FIG. The slip details screen corresponds to a conventional deposit slip and receipt. The detailed information of the slip operated on the slip list screen is displayed on the slip details screen.

When the product is kept, the screen information of the slip list screen updated in step S24 and the slip details generated in step S25 are displayed when the user operates without performing steps S26 and S27 in FIG. Screen information on the screen may be transmitted from the management device 10 to the user terminal 50.

On the slip details screen, "Currently in custody" corresponds to the progress classifications "1" to "5" in the deposited product information file (FIG. 13), and indicates a state before delivery. "Delivered" corresponds to the progress classification "9" in the deposited product information file (FIG. 13) and indicates that the product has been delivered.
Note that if there are multiple products, the user terminal 50 may simply arrange them in the order of expected finish date, but if there are a mixture of "Currently on hold" and "Delivered" products, the "Order" You may preferentially display products that are "on hold". In the example shown in FIG. 10, products "on hold" (products in columns G34 and G35) are displayed above products "delivered" (products in column G36). In addition, "delivered" products (products in column G36) are displayed in gray out. When the products are arranged in the order of expected finish date, the products in column G36 are located above the products in columns G34 and G35.
The return icon G31 is a button for returning to the previous screen (slip list screen (FIG. 9)).
The user can grasp the overview of the entire transaction (list of vouchers) on the voucher list screen (FIG. 9), and check the details of each transaction (each voucher) on the voucher details screen (FIG. 10).

The deposited products are delivered to a cleaning factory and cleaned. When cleaning is completed, the operator inputs information indicating that the product is finished into the factory terminal 40, and the information is transmitted to the management device 10. The management device 10, which has received the information that the product is finished, updates the progress classification of the deposited product information file (FIG. 13) (specifically, updates it to "3 (finishing complete)"). Additionally, products that have been cleaned are delivered to the store. When the product arrives at the store, the store clerk inputs information indicating that the product has arrived at the store into the POS terminal 20, and the information is transmitted to the management device 10. The management device 10 that receives the information that the product has arrived at the store updates the progress classification of the deposited product information file (specifically, updates it to "4 (deliverable)"). Further, when the delivery of the product is completed, the store clerk inputs information indicating that the delivery of the product has been completed into the POS terminal 20, and the information is transmitted to the management device 10. The management device 10, which has received the information that the delivery of the product has been completed, updates the progress classification of the deposited product information file (specifically, updates it to "9 (delivery completed)").

In addition, if the current status confirmation by the user has not been completed for a specific product, the progress classification of the deposited product information file (Figure 13) is "2 (pending)", and when the current status confirmation by the user is completed, , the management device 10 updates the progress classification (specifically, updates it to "1 (item deposit)"). In addition, when a reservation for product delivery is being accepted from a user, the progress classification is "5 (delivery reservation made)", and when the product delivery is completed, the management device 10 updates the progress classification ( Specifically, it is updated to "9 (Delivery)").

In the example shown in FIG. 10, there are two types of information indicating the progress status: "Currently in custody" and "delivered", but the information indicating the progress status does not need to be two types. As an example, there may be four types: "unfinished,""finished,""deliverable," and "delivered.""Beforefinishing" corresponds to progress classification "1" or "2" and indicates a state before finishing at the factory. "Finished" corresponds to progress classification "3" and indicates that the product has been finished in the factory. "Available for delivery" corresponds to progress classification "4" and indicates that the item is ready for delivery. “Delivered” corresponds to the progress classification “9” and indicates that the item has been delivered. As another example, "on hold" may be displayed, which corresponds to the progress classification "2" and indicates that the cleaning work is on hold. Furthermore, "Delivery reservation in progress" may be displayed, which corresponds to the progress classification "5" and indicates that the delivery reservation is being accepted.
In addition, in the case of returning the locker, for example, "Locker return reservation in progress" is displayed (FIG. 21).
When displaying the progress status of reservations such as "reserving delivery" or "reserving locker return", the reservation date may also be displayed.

An example of information stored in the cleaning system 1 of this embodiment will be described below with reference to FIGS. 11 to 15.
[Customer master file]
FIG. 11(A) shows an example of a customer master file. The customer master file may be stored in either the management device 10, the POS terminal 20, or the like. In this embodiment, a case will be exemplified in which the management device 10 stores a customer master file.
The customer master file is a file that stores various basic information regarding customers (members) who are users.
The customer master file is associated with the customer code, including name (kanji), name (furigana), address, contact address, email, phone number (1), phone number (2), identification information for app communication, and date of birth. , member registration date, registered store (store code), etc. are stored. Name (kanji), name (furigana), address, etc. are information obtained from the user at the time of membership registration.

The customer code is information for identifying each user in the cleaning system 1. For example, at the time of member registration, the management device 10 may assign (number) a unique customer code.

E-mail is the e-mail address of the e-mail sent to the user. For example, it may be the e-mail address of the user terminal 50 of the user, or the e-mail address of a terminal (not shown) of the user different from the user terminal 50.

Telephone number (1) and telephone number (2) are telephone numbers for calling the user. For example, if the user terminal 50 of the user is a smartphone, the phone number (1) is the phone number of the user terminal 50 (smartphone) of the user, and the phone number (2) is the phone number of the user terminal 50 (smartphone) of the user. It may also be the telephone number of the person's home landline telephone.

The application communication identification information is information for communicating the cleaning application executed on the user terminal 50 of the user. The identification information for application communication may be any information that can identify the user terminal 50 of the user in the communication of the cleaning application, for example, the IP address of the user terminal 50, the individual identification information of the user terminal 50, the usage It may be identification information (such as a token) that is different from the telephone number and individual identification information of the personal terminal 50.
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, it may change every time the cleaning app is started). (obtainable). If the application communication identification information is temporarily assigned, the latest application communication identification information may be stored.

Note that in addition to the application communication identification information for identifying the user terminal 50 in the cleaning application communication, application user identification information (for example, user ID, etc.) for identifying the user in the cleaning application. may be memorized.

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. Note that if you register as a member at a location other than the store (for example, if you register as a member from your home or workplace using the user terminal 50 via a cleaning app), the cleaning app will The registered store may be an automatically selected store, a store selected by the user from among the candidates presented by the cleaning app at the time of membership registration, or a store freely selected by the user at the time of membership registration. It's okay. In addition, when registering as a member, the cleaning app searches for the store closest to the user's home based on the information entered by the user (e.g. address, area code, area code, etc.) and selects it as the registered store. It may be automatically selected, or it may be presented to the user as selection candidates.

In addition, in this embodiment, an example is shown in which the store code is a 4-digit store code in which the first two digits are "TP" and the next two digits are a store-specific number (00 to 99, etc.). There is.

[Customer performance summary file]
FIG. 11(B) shows an example of a customer performance summary file. The customer performance summary file may be stored in either the management device 10, the POS terminal 20, or the like. In this embodiment, a case will be exemplified in which the management device 10 stores a customer performance summary file.
The customer performance total file is a file that stores information regarding the usage history of services (various cleaning-related services provided by the cleaning system 1) for each customer (member) who is a user.
The customer performance aggregation file shown in Figure 11(B) includes performance information for all stores combined (rank, last date of use, frequency of use, average unit price), performance information for the main store (rank , date of last use, frequency of use, average unit price). In the present embodiment, the results are compiled once a month (for example, on a specific day of each month), and the results are stored in the customer performance summary file.

The last use date is the date of last use. The frequency of use is the number of times of use in the past month. The usage amount is the total usage amount for the past month. The rank is information indicating a user's evaluation (degree of contribution), and is information calculated based on one or more of the following: the last date of use in the past month or more, frequency of use, and amount of use. As an example, a user who has used the service 12 times or more in the past June and whose usage amount in the past June is 24,000 yen or more is given the highest rank (for example, S rank), and a user who has used the service 0 times in the past December. The user may be ranked lowest (for example, 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.

[Point management file]
FIG. 11C shows an example of a point management file. The point management file may be stored in either the management device 10, the POS terminal 20, or the like. In this embodiment, a case will be exemplified in which the management device 10 stores a point management file.
The point management file contains points that are awarded according to service usage records and can be used instead of cash (for example, 1 point is awarded for every 200 yen spent, and 1 point can be used as 100 yen instead of cash). etc.) is a file that stores information regarding.
The point management file shown in FIG. 11(C) stores the number of available points and the like in association with customer codes. The expiration date may be managed (stored) in a point management file.

Note that the point management file shown in Figure 11 is used when the points to be managed are common to all stores of a chain store (when the points given at each store are added up and can be used at any store). ). However, if points are to be managed individually at each store in a chain store (points given at a certain store can only be used at that store), for example, if points are to be managed in association with the store code and customer code. (In other words, for each store code and customer code), the number of available points, etc. may be stored.

[Electronic slip file]
FIG. 12 shows an example of an electronic slip file. The electronic slip file may be stored in either the management device 10, the POS terminal 20, or the like. In this embodiment, a case will be exemplified in which the management device 10 stores an electronic slip file.
The electronic slip file is a file that stores information regarding electronic slips indicating transaction details regarding various cleaning-related services.
The electronic slip file shown in FIG. 12 includes, in association with the slip number, the deposit date and time, store code, clerk code, customer code, deposit classification, number of deposit points, total charge, scheduled completion date, delivery completion date, receipt reminder date, It remembers the update date and time. Note that the management device 10 updates the electronic slip file (adds new information) when the product is deposited, and updates the electronic slip file as appropriate according to the progress of the service.

The slip number is information for identifying the electronic slip in the cleaning system 1. For example, the POS terminal 20 may assign (number) a slip number when the product is deposited. In this embodiment, a serial number (used cyclically) for each store is assigned as the slip number. Specifically, the first two digits are "DN", the next two digits are the last two digits of the store code (store-specific number), the next one is "-", and the next four digits are the number (0000-9999). A total of 9 digits (including hyphens) is used for the slip number. Therefore, by referring to the slip number without referring to the store code, it is possible to know which store the electronic slip belongs to in the transaction.

The deposit date and time is information indicating the date and time when the product was deposited by the user at the cleaning shop. Note that the date and time when the store clerk inputs information at the POS terminal 20 at the time of product deposit may be set as the deposit date and time.

The deposit category is information indicating the method of depositing the product. In this embodiment, the product deposit methods (product reception methods) include regular store deposit (sometimes referred to as regular store reception), speed deposit (sometimes referred to as speed reception), and collection deposit (also referred to as collection reception). (In some cases, locker storage is available.) Locker storage (sometimes referred to as locker reception) is also available. The deposit category "1" indicates normal store deposit, the deposit category "2" indicates speed deposit, the deposit category "3()" indicates collection deposit, and the deposit class "4" indicates locker deposit. Note that the part in parentheses of the storage category "3()" is information (location code) indicating the collection location in the collection storage.

Normal store storage is a method in which a user brings a product to a store's reception desk, a store employee and the user meet face-to-face, the product is inspected and paid for, and the product is accepted as a deposit product. Speed deposit means that the user deposits the bagged product (bagged product) at the store's reception counter (in other words, the store staff and the user meet face-to-face for product inspection and payment). This method allows the reception to be completed without doing so. In Speed Deposit, the user must carry a membership card (with customer code, name, etc. Membership card) will also be left at the store. The same applies to the case of locker storage, which will be described later. Pick-up and storage is a method in which the cleaning shop goes to a predetermined collection location (user's home, convenience store, etc.) and accepts the received product as a deposit product. Locker storage is when a user places bagged products (products in a bagged state) into the collection section of a designated locker (i.e., the store staff and user face-to-face to inspect the product). This is a method in which the reception is completed without the need for payment or payment).

The number of items in custody is information indicating the number of items in custody. Note that information regarding individual products is stored in a deposited product information file (see FIG. 13). The total charge is information indicating the total charge for all deposited products.

The expected completion date is information indicating the date when the deposited product is finished (cleaning is completed) and can be delivered to the user (the date when the user can receive the product). When a plurality of products are deposited (the number of products deposited is 2 or more), the expected completion date indicates the date when all deposited products can be delivered.

The delivery completion date is information indicating the date on which the 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 case where a plurality of products have been deposited indicates the date on which the delivery of all the deposited products has been completed.

The receipt reminder date is information indicating the date on which the user was urged to receive the product. In addition, if there are multiple days when you are reminded to pick up the product, you can manage (memorize) only the date on which you were reminded last as the date on which you received the reminder, or you can receive and manage each date on which you were reminded as the day on which you received the reminder. Good too. Note that the method of reminding the user may be by using a cleaning app, by e-mail, or by telephone. In addition, the method of prompting may be managed (memorized) together with the receipt reminder date.

The update date and time is information indicating the date and time when any information in the electronic slip was updated. For example, if there is an update (input) of the delivery completion date, the date and time of the update becomes the update date and time.

[Deposited product information file]
FIG. 13 shows an example of a deposited product information file. The deposited product information file may be stored in either the management device 10, the POS terminal 20, or the like. In this embodiment, a case will be exemplified in which the management device 10 stores a deposited product information file.
The deposited product information file is a file that stores information regarding each deposited product.
The deposited product information file shown in FIG. 13 includes tag numbers, product types, processing types, charges, pending classifications, progress classifications, scheduled completion dates, reservation classifications, delivery classifications, scheduled delivery dates, etc. in association with deposited product numbers. It stores the delivery completion date, update date and time, storage completion flag, etc. Note that the management device 10 updates the electronic slip file (adds new information) when the product is deposited, and updates the electronic slip file as appropriate according to the progress of the service.

The deposited product number is information for identifying the deposited product in the cleaning system 1. For example, when the product is deposited, the POS terminal 20 or the management device 10 may assign (number) the deposited product number.
In this embodiment, the deposited product number is the slip number with a branch number added. Specifically, a 13-digit deposited product number (including hyphens) is used, where the first 9 digits are the slip number, the next digit is "-", and the next two digits are the branch number (01-99). Therefore, by referring to the deposited product number, it can be determined in which electronic slip the deposited product belongs. Further, as described above, since the store where the transaction was carried out can be specified from the slip number, by referring to the deposited product number, it can be determined which store the deposited product was in for the transaction.

The tag number is information for identifying the deposited product in the cleaning system 1. The tag number is, for example, when the store clerk inputs the number printed on the tag attached to each deposited product at the POS terminal 20 as the tag number of each deposited product. In this embodiment, as the tag number (number printed on the tag), the first two digits are "TG", the next two digits are the last two digits of the store code (store-specific number), and the next one is "-". , a total of 9 digits (including a hyphen) is used, with the following 4 digits being the number (0000-9999). Therefore, by referring to the tag number, it can be determined which store the item is being held in for transaction.

The product type is information indicating the type of product. The processing type is information indicating the type of processing (washing, storage, etc.). The charge is information indicating the charge for the deposited product.

The suspension classification is information indicating whether or not progress is required to be suspended. In the present embodiment, the user is asked to check the condition of the deposited product as a specific product (product with dirt, fraying, etc.). A hold class "0" indicates that hold is not required (no reason for hold), a hold class "1" indicates that hold is necessary (before user confirmation), and a hold class "2" indicates that hold is not necessary (user has been confirmed).

The progress classification is information indicating the progress status. The progress class "1" indicates that the product is in storage, the progress class "2" indicates that the product is on hold, the progress class "3" indicates that the product has been completed, the progress class "4" indicates that the product can be delivered, and the progress class "5" indicates that the product is ready for delivery. It indicates that the delivery is scheduled, and the progress classification "6" indicates that the delivery is completed.

The expected completion date is information indicating the date when the deposited product will be completed and can be delivered to the user. Note that the scheduled finishing date in the deposited product information file is the scheduled finishing date of each individual deposited product, whereas the scheduled finishing date in the electronic slip file indicates that all deposited products in the electronic slip can be delivered. It's the date. In other words, the scheduled finishing date in the electronic slip file is the latest scheduled finishing date among the scheduled finishing dates of each deposited product corresponding to the electronic slip shown in the deposited product information file. In addition, in this embodiment, the expected finishing date is basically calculated based on the product deposit date (reception date) and the required number of days, but if the user's confirmation of a specific product is delayed, the finishing date may be delayed. The scheduled date has been delayed.

The reservation category is information indicating whether or not there is a reservation for delivery of the deposited product. Reservation category ``0'' indicates no reservation, reservation category ``1'' indicates reservation made at the store, reservation category ``2'' indicates reservation made by phone, and reservation category ``3'' indicates reservation made through the app. shows. The contents of the reservation include the delivery date and time and delivery method. Furthermore, if you make a reservation for delivery when you come to the store and leave the product (in a case where the deposit category is "1" or "2"), the reservation category will be "1 (reservation made at the store)".

Reservations are subject to change. For example, a reservation made at the time of dropping off the product can be changed by phone or by using a cleaning app. For the reservation classification when the reservation is changed, information at the time of the change may be stored. For example, when a reservation made at the timing of depositing a product is changed by telephone, the reservation classification "1" before the change by telephone may be updated to [2].

The delivery classification is information indicating the delivery method of the deposited product. In this embodiment, the methods for delivering the deposited product (method for returning the deposited product) include regular store delivery (sometimes referred to as regular store return), delivery delivery (sometimes referred to as delivery return), and locker delivery (locker return). ) is available. Delivery class "0" indicates undetermined, delivery class "1()" indicates normal store delivery, delivery class "2()" indicates delivery delivery, and delivery class "3" indicates locker delivery. Note that the part in parentheses of the delivery category "1()" is information (store code) indicating the delivery store in normal store delivery. The part in parentheses of the delivery classification "2()" is information (location code) indicating the delivery location (user's home, convenience store, etc.) in the delivery delivery. The part in parentheses of the delivery classification "3()" is information (locker number) indicating the locker in the locker delivery.
Further, although not shown in the figure, in the case of delivery classification "3()", a return port number (identification information) indicating the return port in the locker indicated by the locker number may be further included.

Regular store delivery (regular store return) is a method of handing over the deposited product at the reception desk of the store. Delivery delivery (delivery return) is a method of delivering the deposited product at a predetermined delivery location. Locker delivery (locker return) is a method of delivering deposited products using a locker.

Note that if there is no delivery reservation (reservation classification "0"), the delivery method will be undetermined (delivery classification "0"). On the other hand, if there is a delivery reservation (reservation classification "1" to "3"), the delivery method will be the method specified by the user in the reservation (delivery classification "1" to "3").

The scheduled delivery date is information indicating the date on which the deposited product is scheduled to be delivered. Note that if there is no delivery reservation (reservation classification "0"), the scheduled delivery date will be undetermined (for example, blank). On the other hand, if there is a delivery reservation (reservation classifications "1" to "3"), the scheduled delivery date will be the date specified by the user in the reservation.

Note that even if there is no delivery reservation (reservation classification "0"), regular store delivery (regular store return) is possible after the scheduled completion date. In other words, the user can, of course, suddenly go to the store and pick up the product without contacting the store after the scheduled completion date.

The delivery completion date is information indicating the date on which the 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 date on which the delivery of each individual deposited product was completed, whereas the delivery completion date in the electronic slip file is the date on which delivery was completed for all deposited products in the electronic slip. It is. That is, the delivery completion date in the electronic slip file is the latest delivery completion date among the delivery completion dates of each deposited product corresponding to the electronic slip shown in the deposited product information file.

The update date and time is information indicating the date and time when any information about the deposited product was updated. For example, if there is an update (input) of the delivery completion date, the date and time of the update becomes the update date and time.

The storage completion flag is a flag indicating whether or not the store clerk has completed storing the product in the return slot of the locker when the delivery classification of the corresponding product is locker delivery.

Next, information stored by the cleaning system 1 related to locker operation will be described with reference to FIGS. 14 and 15. Each piece of information shown in FIGS. 14 and 15 may be stored in either the management device 10, the POS terminal 20, or the like, but in this embodiment, the case where the information is stored in the management device 10 is taken as an example.

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

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. Note that it is possible to install two or more return lockers in one store, or to install return lockers in a location other than the store. Locations other than stores include, for example, supermarkets, convenience stores, specialty stores (clothing stores, drug stores, etc.), shops inside (or near the station), return lockers (regarding the reception locker 100) inside and outside of apartments, etc. ) may also be installed.
The number of return lockers is the number of return lockers that the return locker has.

Note that in the locker management master file, in addition to return lockers (return-only locker 300, common locker 200), reception-only locker 100 (locker number of reception-only locker 100, etc.) may be managed.

Note that the POS terminal 20 may store the locker management master file instead of or in addition to the management device 10. Note that the locker management master file stored by the POS terminal 20 may be a file related to all return lockers, similar to the file stored by the management device 10, or, as shown in FIG. It may also be a file related to a return locker related to a store where the POS terminal 20 is installed.

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

The required number of units definition file shown in Figure 14(C) determines the required number of units simply based on the number of returned products and does not take into account the type of returned products, but it is necessary to take into account the type of returned products. You may decide on the number of words. For example, instead of the required number of units definition file shown in FIG. 14(C), a required number of units definition file as shown in FIG. 14(D) and a volume number definition file as shown in FIG. 14(E) may be stored. It's okay.

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

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

For example, if there are two items you wish to deliver, one is a shirt (product type "SY01") and the other is a coat (product type "SY04"), the required quantity definition file in Figure 14(C) According to the above, since the number of returned products is 2, the required number of units is 1. On the other hand, according to the required number of units definition file in FIG. 14(D) and the volume number definition file in FIG. 14(E), the total number of volumes for one shirt and one coat is 5, so the required number of units is 2. .

Note that instead of or in addition to the management device 10, the POS terminal 20 may store a required number of units definition file as shown in FIG. 14(C). Further, instead of or in addition to the management device 10, the POS terminal 20 may store a required number of units definition file as shown in FIG. 14(D) or a volume number definition file as shown in FIG. 14(E).

[Reservation status file by locker]
FIG. 15(A) is an example of a locker-based reservation status file stored by the management device 10. The locker-specific reservation status file is a file that stores information regarding the locker return reservation status (reservation status) for each return locker. The locker-specific reservation status file shown in FIG. 15(A) shows the reservation status file for the return locker with locker number "L01", and the reservation status file, customer code, and tag are associated with the return date and return port number. Includes number, number of volumes used, reservation date, reservation number, etc.
Note that in FIG. 15A, for convenience of explanation, sheets (tables) are shown separately 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 desired to be delivered at the return port. Note that the locker-specific reservation status file shown in FIG. 15(B) will be described later.

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

In addition to future information (information on future return dates), the locker-specific reservation status file also holds past information (information on past 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 hold past information in the locker-specific reservation status file without erasing it. For example, the management device 10 may continue to hold past information for a predetermined period (at least a period referred to when determining a return port (described later)) without erasing past information.

The future information in the locker-specific reservation status file is a file that shows the future reservation status of lockers (each return slot), but since lockers are used based on reservations, the future information in the locker-specific reservation status file is My past information is also a file that shows the past usage of my locker. Therefore, by storing the reservation status file for each locker in the cleaning system 1, the cleaning system 1 can manage not only the reservation status of the return slot in the future but also the usage status of the return slot in the past.

[Locker return reservation]
A locker return reservation made in the cleaning system 1 of this embodiment will be explained. Here, "locker return reservation" means that when a user (customer) wants to return a cleaned product, the user (customer) uses the locker to return the product to the return slot of the locker, rather than handing it over to the store staff. This means making a reservation for a date when the item will be stored in a container.
A locker return reservation can be made at a store by a clerk operating the POS terminal 20 while interacting with the user (store reservation). Alternatively, the locker return reservation can be made by the user by operating a cleaning application on the user terminal 50 (application reservation). In the case of application reservation, the user does not have to go to the store and receive service from a store clerk.
The results of locker reservations made by store reservations and the results of locker reservations made by application reservations are reflected in the locker-specific reservation status file (FIG. 15).

In both cases of store reservations and application reservations, when reserving a locker, the management device 10 specifies the reservable date (returnable date) according to the completion date of the product and the reservation status of the return slot.
The flowchart in FIG. 16 shows an example of a processing procedure executed by the management device 10 in connection with specifying a reservation possible date (returnable date).
The process shown in the figure is started when specifying a reservation date for locker return (when executing processing related to locker return reservation; for example, when displaying a locker return reservation screen (described later)).
For example, in the case of a store reservation, the clerk, while accepting a customer's cleaning request face-to-face, receives a request to return the locker and performs an operation to declare the locker return reservation on the POS terminal 20. I do. Furthermore, when the clerk receives a request to return a locker from a user by telephone or the like, the clerk may perform an operation to declare a locker return reservation on the POS terminal 20.
The POS terminal 20 transmits a locker return reservation setting request to the management device 10 in response to the locker return reservation declaration operation.
Further, as an application reservation, the user performs an operation for transitioning to an operation screen corresponding to the application reservation by operating the cleaning application running on the user's POS terminal 20. In response to the operation, the POS terminal 20 requests the management device 10 to set a locker return reservation. The management device 10 may start the process shown in the figure in response to receiving the locker return reservation setting request transmitted as described above.
Note that the process shown in the figure may be executed by the POS terminal 20 when dealing with store reservations.

Step S400: The management device 10 calculates the number of return slots required for return (required number of slots) based on the number, type, etc. of products to be returned.
Step S401: The management device 10 determines whether all the products for which the locker is desired to be returned have been finished.
If it is not finished (step S401; NO), the process advances to step S402. If it has been finished (step S401; YES), the process advances to step S405. Note that when this flowchart is executed at the time of product deposit, since none of the products are finished, the process advances to step S402.

Step S402: The management device 10 identifies the latest scheduled finishing date (the latest scheduled finishing date among the scheduled finishing dates of each product for which locker return is desired).
Step S403: The management device 10 sets the latest scheduled completion date as the reference date. The process then proceeds to step S406.
Note that the reference date in steps S403, S405, and S406 is the earliest available reservation date when the usage status of the locker is not considered (ignored).
Step S405: The management device 10 sets tomorrow as the reference date. The process then proceeds to step S406.

Step S406: The management device 10 determines whether the number of vacancies on each day after the reference date is equal to or greater than the required number.
If the number of vacancies is equal to or greater than the required number, reservations can be made, so the process in step S406 is a process for determining whether it is a reservation-available date. The management device 10 can calculate the available reservation dates from the number of vacancies for each day after the reference date and the required number of units.
Step S407: The management device 10 outputs the determination result of step S406.
The content as the output of the determination result indicates whether reservation is possible or not for each day. Therefore, it can be said that the process shown in the figure determines whether or not a reservation is possible for each day (or a specific day) in specifying the reservation possible date (returnable date).
The determination result in step S406 is reflected in the locker-specific reservation status file (FIG. 22). At this time, the management device 10 may output information by display on the POS terminal 20, for example, based on the contents of the locker-specific reservation status file in which the determination result of step S406 is reflected.

[Locker return reservation screen]
In this embodiment, when a locker return reservation is made through a store reservation, for example, the determination result in step S407 in FIG. 16 may be output as a locker return reservation screen displayed on the POS terminal 20.
In this case, the management device 10 transmits the locker-specific reservation status file in which the determination result of step S407 in FIG. Display the locker return reservation screen (locker return reservation screen).

FIG. 17 shows an example of a locker return reservation screen displayed on the clerk-side display section 26 of the POS terminal 20. The locker return reservation screen is a screen on which operations related to locker return reservations are performed. The locker return reservation screen in the figure corresponds to the contents of the locker-specific reservation status file in FIG. 15(A).

The locker return reservation screen shown in the figure includes a current date and time field (see code A), a locker information field (see code B), a customer information field (see code C), a locker return product number field (see code D), A message column (see symbol E), a required return number column (see symbol F), an adjustment column (see symbol G), a calendar column (see symbol H), etc. are provided.

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 reservation screen.
The customer information column (symbol C) displays the customer code, etc. of the user (the user who makes a reservation for returning the locker).
The number of products returned to the locker column (symbol D) displays the number of products that the user wishes to deliver by returning the locker.
The required return number column (symbol F) displays the number of return lockers required for the user to return the locker.
In the adjustment field (symbol G), buttons for increasing/decreasing (adjusting) the number of required returns and an adjustable range are displayed.
The calendar column (symbol H) displays the number of return slots available (reservable) for each day (the number of vacant return slots). Each date area in the calendar column is a button.

In order to explain the figure, a customer (customer code "KB9876") selects a shirt (tag number "TG01-1372") and a sweater (tag number "TG01-1374") on the slip details screen (Figure 14). ) and a down jacket (tag number "TG01-1375") are selected as the desired products to be delivered by returning the locker. In addition, the required number of ports is calculated taking into consideration the number of volumes.

"L01 (AAA)" in the locker information column (code B) in the figure is based on, for example, the deposited product information file (Figure 13), the locker management master file (Figure 14 (A)), and information about the store. This is what is displayed. "3" in the locker returned product number column (code D) is the above-mentioned three items.

"2" in the required number of returned units column (symbol F) indicates the number of returned units based on the number of returned volumes. In the cleaning system 1, the number of volumes is defined for each product type, and for example, the management device 10 stores information defining the number of volumes for each product type. In addition, in the cleaning system 1, the number of required return slots (required number of return slots) is defined according to the number of volumes to be returned. Stores the information that defines the .
In the same figure, the volume number of a shirt (product type "SY01") is "1", the volume number of a sweater (product type "SY02") is "2", and the volume number of a down jacket (product type "SY03") is "1", and the volume number of a sweater (product type "SY02") is "2". Since the number is ``3'', the total number of volumes (number of returned volumes) is ``6''.The required number of units corresponding to the number of returned volumes ``6'' is ``2'', so in the required number of returned units column. "2" is displayed.

The adjustable range “1 to 3” in the adjustment field (symbol G) is set in advance as a fixed value in the case of the required number of return units field “2”. Note that the value may be set in advance as a fixed value when the number of returned volumes is "6".

The ``4'' displayed on the 4/20 date button in the calendar column (symbol H) corresponds to the empty number ``4'' in the locker-specific reservation status file (FIG. 15(A)). That is, the date button in the calendar field shows the number of available return slots on the corresponding date.
On the locker return reservation screen shown in Figure 17, the color (background color) of each date button is set to indicate that the date in question is a reservable day (days after tomorrow (excluding store holidays), and the number of vacancies is greater than or equal to the number of required return lockers. The dates are different depending on whether it is a certain day) or a non-reservable day (a day when reservations are not possible). In FIG. 17, date buttons corresponding to available reservation dates (4/20, 4/23, 4/24, 4/27, 4/28, etc.) are displayed on non-reservable dates (4/16 to 4/4/2019). 19, 4/21, 4/22, 4/25, 4/26, 4/29, . . . ) date buttons are grayed out, for example.

When the locker return reservation screen shown in FIG. You may display it.
FIG. 18 shows an example of an aspect of the customer-side locker return reservation screen. The customer-side locker return reservation screen in the figure corresponds to the customer-side locker return reservation screen in FIG.
In the figure, areas for each date (date area) are arranged in the calendar column. Furthermore, a cross mark or a circle mark is arranged in the date area.
A date area with a cross mark indicates that reservations cannot be made for the corresponding date because the number of available return slots is insufficient compared to the required number of slots. On the other hand, a date area with a circle mark indicates that a reservation can be made if the number of vacant return slots is greater than or equal to the required number.

Note that the manner of indicating whether reservations are possible or not possible for each date is not limited to the above-mentioned circles and crosses. For example, whether a reservation is possible or not can be indicated by an icon that resembles a locker with an empty return slot or a locker with no return slot available.
Note that such a customer-side locker return reservation screen may be displayed on the customer-side display unit 27 as an external display device connected to the main body of the POS terminal 20. The customer side display unit 27 as an external display device can easily secure a wide screen, and therefore can display the customer side locker return reservation screen in a large size. This makes it easier for customers to view the customer-side locker return reservation screen. For example, although the customer side display section 27 is provided on the main body of the POS terminal 20, if the screen size is small, an external display device may be provided as yet another customer side display section 27. A display device may be used, or the customer-side display section 27 of the main body and an external display device may be used together. When the customer side display section 27 of the main body and an external display device are used together, the display destination can be switched between the customer side display section 27 of the main body and the external display device depending on the content to be displayed to the customer. It may be possible to do so.

The user looks at the customer-side locker return reservation screen displayed in this way, decides on a reservation date from among the available dates, and informs the store clerk of the chosen reservation date. The clerk operates the date button corresponding to the notified reservation date from among the date buttons arranged in the calendar field (symbol H).
Alternatively, the date area on the customer-side locker return reservation screen may also be a button (customer-side date button) that can be operated by the user. In this case, the user can decide on a reservation date from among available dates and operate the customer-side date button corresponding to the decided reservation date.

Here, we will take as an example a case where the date button for "4/20" or the customer's date button is operated.
In response to the operation of the "4/20" date button or the customer's date button, the locker return reservation screen displayed on the clerk's display section 26 changes as shown in FIGS. 17 to 19. . That is, on the locker return reservation screen, the date button "4/20" is displayed in a manner that emphasizes it compared to other date buttons, for example by changing the background color to a predetermined color. This indicates that April 20th is currently designated as the reservation date.
Although not shown, the "4/20" date area of the date area (customer date button) may be displayed in a similar manner on the customer's locker return reservation screen. .
The clerk operates, for example, the "Register" button while the date button "4/20" is highlighted as described above. In response to the operation on the "Register" button, April 20th is confirmed as the reservation date.

In response to the confirmation of the reservation date, for example, the management device 10 updates the locker-specific reservation status file, the deposited product information file, and the deposited product information file.
FIG. 15(B) shows an example of the content of the locker-specific reservation status file that has been updated in response to the confirmation of April 20th as the reservation date.
Further, FIG. 20 shows an example of the content of the deposited product information file updated from FIG. 13 in response to the confirmation of April 20th as the reservation date.

Further, after the reservation date is confirmed, the status of the locker return reservation may be reflected on the cleaning app screen of the user terminal 50.
FIG. 21 shows an example of the contents of the slip details screen displayed on the user terminal 50 after the reservation date is confirmed.
In the figure, in the column for products that are subject to locker return, it is indicated that the product is to be returned to the locker, for example, "Locker return reserved", and the reservation date is also displayed. An example is shown.

Furthermore, if the number of vacant return slots is greater than the required number, the management device 10 determines the return slot (reservation return slot) in which the product should be stored from among the return slots that can be used (reservable). select. In other words, if there is enough space (room to select a return port), it is determined which return port to use.
There are several ways to determine the reservation return slot. For one thing, the management device 10 may determine the reserved return slot based on the past usage status of each return slot. As a specific example, the management device 10 may determine the reservation return slot so that a specific return slot is not used frequently (so that each return slot is used evenly). By using each return port evenly, a situation where deterioration or damage progresses at a specific return port is less likely to occur.
Note that the management device 10 grasps the past usage status of each return slot by, for example, continuing to store the reservation status file for each locker (FIG. 15) for a certain period of time without deleting it even after the return date has passed. be able to.

Further, instead of or in addition to the above method, the management device 10 may determine the reservation return port based on the positional relationship (adjacent relationship) of each return port, for example. As a specific example, when the same user makes reservations for two or more return slots (when the user's required number of return slots is two or more), the management device 10 may be configured to store products from adjacent return slots. If possible, adjacent return ports may be determined so that the items can be taken out. By determining adjacent return slots, users do not have to move to a return locker located far away.

An example of a processing procedure executed by the management device 10 in connection with locker return reservation will be described with reference to the flowchart of FIG. 22. The flowchart of FIG. 22 shows an example of a processing procedure corresponding to a case where a locker return reservation is made based on a store reservation.

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

Step S631: The management device 10 receives a request for a reservation screen (locker return reservation screen) from the POS terminal 20.
Step S632: The management device 10 generates a reservation screen (the latest locker return reservation screen based on the current reservation status). Specifically, the management device 10 generates a reservation screen by referring to the latest electronic slip file, deposited product information file, locker management master file, reservation status file for each locker, etc. of the user. . Note that the management device 10 may generate a reservation screen for a return locker installed at the store where the product (product for which locker return is requested) was kept.
Step S633: The management device 10 transmits the screen information of the reservation screen to the POS terminal 20.

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

Step S638: The management device 10 receives reservation information from the POS terminal 20.
Step S641: The management device 10 determines a return port (reservation return port) based on the reservation information according to a predetermined method.

Step S642: The management device 10 updates various files based on the return port determination result. That is, the management device 10 reflects the return port determination result in S641 in the corresponding user's electronic slip file, deposited product information file, locker management master file, locker-specific reservation status file, and the like.

Depending on step S642, in the above various files, etc., when returning the product to the customer by returning the locker, the date on which the product should be stored in the return locker 300 (scheduled delivery date, scheduled storage date) together with the return port determination result. Information about the storage schedule, including the start date) is reflected. That is, in step S642, the storage schedule of the product is stored.

Step S643: The management device 10 updates and generates various screens. For example, the management device 10 updates and generates a reservation confirmation screen based on the return port determination result in step S642. Specifically, the management device 10 updates the scheduled locker return date calendar screen to reflect the reservation details, as shown in FIG. Furthermore, the management device 10 generates a slip details screen that reflects the reservation details as shown in FIG. The management device 10 may also generate a locker return schedule list screen that reflects the reservation details, as shown in FIG. 24, which will be described later. That is, in step S643, screen information to be transmitted in subsequent processing (steps S645 and S655) is generated.

Step S645: The management device 10 transmits the screen information to the POS terminal 20. For example, the management device 10 can display screen information on a reservation screen (a locker return reservation screen that reflects the reservation details as shown in FIG. 19, a locker return schedule list screen that reflects the reservation details as shown in FIG. 24, etc.). is transmitted to the POS terminal 20.
Step S646: The POS terminal 20 receives screen information of the reservation screen (locker return reservation screen that reflects the reservation details, locker return schedule list screen that reflects the reservation details as shown in FIG. 24) from the management device 10. .
Step S647: The POS terminal 20 displays a reservation screen (locker return reservation screen reflecting the reservation details).

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

Note that instead of the processing in steps S655 and S656 in FIG. 22, the management device 10 may send message information notifying that the locker has been reserved to the user terminal 50 using e-mail or the like. That is, when determining the return port when reserving locker return at the POS terminal 20, the minimum amount of information may be transmitted to the user terminal 50.

Furthermore, the processes in steps S655 and S656 are not performed when the return slot is determined as shown in FIG. You can also do this. That is, for example, when a slip details screen is requested, it may be transmitted from the management device 10 to the user terminal 50.

The flowchart in FIG. 22 is an example of the 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 return port determination result by the POS terminal 20 is , as long as it is reflected in various files stored in the management device 10. As an example, the flow may be as follows. The POS terminal 20 that receives the reservation operation on the reservation screen (the latest reservation screen received by accessing the management device 10, as in the case of FIG. 22) determines the return port and displays the result of determining the return port. Send the information to the management device 10. The management device 10 updates various files based on information indicating the return port determination result received from the POS terminal 20. Next, the POS terminal 20 displays a reservation confirmation screen from the management device 10 (a locker return reservation screen that reflects the reservation details as shown in FIG. 19, a locker return reservation screen that reflects the reservation details as shown in FIG. 24, which will be described later). Receive screen information (e.g. schedule list screen). Note that the processes in S655 and S656 are the same. As described above, the result of determining the return port by the POS terminal 20 is reflected in various files stored in the management device 10.

Next, an example of a processing procedure executed by the management device 10 in connection with a locker return reservation as an application reservation will be described with reference to the flowchart of FIG. 23.
Step S600 in FIG. 23: The user terminal 50 on which the cleaning application operates requests the management device 10 for a reservation screen. For example, when a user performs an operation to display a reservation screen on the user terminal 50 (for example, selecting to return a locker, etc.), the user terminal 50 displays the reservation screen on the management device 10. request.

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

Step S604: The user terminal 50 receives 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 (for example, touching a button for a reservation available day in the calendar field (symbol H)) on the reservation screen.
Step S607: The user terminal 50 transmits reservation information (reservation date, required number, etc.) to the management device 10.

Step S608: The management device 10 receives reservation information from the user terminal 50.
Step S611: The management device 10 determines a return port (reservation return port) based on the reservation information according to a predetermined method.
Step S612: Similar to step S642 in FIG. 22, the management device 10 updates various files based on the return port determination result.
Step S613: The management device 10 updates and generates various screens similarly to step S643 in FIG. 22. In step S613, screen information to be transmitted in steps S615 and S625, which will be described later, is generated.

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

Step S625: The management device 10 transmits the screen information to the POS terminal 20. For example, the screen information of the reservation confirmation screen (such as the locker return reservation screen that reflects the reservation details as shown in Figure 19, the locker return schedule list screen that reflects the reservation details as shown in Figure 24 described later), etc. It is transmitted to the terminal 20.
Step S626: The POS terminal 20 receives screen information of a reservation confirmation screen (a locker return reservation screen that reflects the reservation details, a locker return schedule list screen, etc.) from the management device 10, and stores the received screen information in the storage unit. do. The flowchart of FIG. 23 then ends.

Note that the processes in steps S625 and S626 in FIG. 23 may be omitted.
Note that instead of the processing in steps S625 and S626 in FIG. 23, the management device 10 transmits message information to the POS terminal 20 informing that the locker has been reserved, and the POS terminal 20 that has received the message information, The message may be displayed on the currently displayed screen. That is, when determining the return port when making a reservation to return the locker at the user terminal 50, the minimum amount of information may be transmitted to the POS terminal 20.

Further, the processing in steps S625 and S626 is not performed when the return slot is determined as shown in FIG. 23, but is performed when the store clerk operates, regardless of whether or not the above message information is sent/received. It's okay. 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 together with the message to the POS terminal 20, and sends the screen information to the POS terminal 20. The received POS terminal 20 displays the small screen superimposed on the currently displayed screen, and when the OK (display) button is touched (equivalent to an operation by a store clerk), a reservation confirmation screen (locker return reservation screen) is displayed. , locker return schedule list screen, etc.) may be requested and transmitted from the management device 10 to the POS terminal 20.

Note that the processing procedure example in FIG. 23 corresponds to the case where the management device 10 determines the return port, but when the POS terminal 20 determines the return port, the return port determination result by the POS terminal 20 is It suffices if it is reflected in various files stored in the device 10.

If the clerk wants to check the current locker return reservation status, the clerk can display a locker return reservation confirmation screen on the clerk side display section 26 by operating the POS terminal 20.
FIG. 24 shows an example of an aspect of the locker return reservation confirmation screen. The locker return reservation confirmation screen in the figure includes a current date and time field (see reference numeral A), a condition setting area (see reference numeral B), a result display area (see reference numeral C), and the like.

The condition setting area (symbol B) is an area for setting (extracting) confirmation targets such as locker return reservation status. The condition setting area includes a scheduled return date setting field (see reference numeral B1) and a customer setting field (see reference numeral B2). The scheduled return date setting field (code B1) has selection buttons for inputting the scheduled return date (range specification button, previous day button, today button, next day button) and a range of scheduled return dates when the range specification button is selected. and a scheduled return date range input field. Note that when the previous day button, today button, or next day button is selected, a range is automatically entered in the expected return date range input field according to the type of button selected. Note that, as can be seen from the presence of the previous day button, past dates can also be set. The customer setting field (code B2) includes a scheduled return date range input field for inputting the user's customer code range, a telephone number input field for inputting the user's telephone number, and a telephone number for inputting the user's designation. It has an input field.

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 illustrated in FIG. 24 displays the scheduled return date, reception date, slip number, name, telephone number, number of products, used return slot, and reissue based on various information. .

For example, the scheduled return date "201X/4/20" in the top information (line indicated by the arrow) is the return date "201X/4/20" in the locker-specific reservation status file in Figure 15(B). Displayed based on. Alternatively, the scheduled return date "201X/4/20" may be displayed based on the scheduled delivery date "4/20" of the deposited product information file in FIG. 20.
The reception date "201X/4/19" is displayed based on the reservation date "4/19" in the locker-specific reservation status file in FIG. 15(B). Alternatively, the reception date "201X/4/19" may be displayed based on the update date and time "4/19 18:27" of the deposited product information file in FIG. 20.
The slip number "DN01-5422" is the tag number "TG01-1372" in the reservation status file by locker in Figure 15 (B), and the deposited product number "DN01-5422-01" in the deposited product information file in Figure 20. Displayed based on. Note that the top nine digits "DN01-5422" of the deposited product number "DN01-5422-01" indicate the slip number.
The customer code "KB9876" is displayed based on the customer code "KB9876" in the locker-specific reservation status file in FIG. 15(B). The name "...(omitted)" and the telephone number "...(omitted)" are displayed based on the customer master file shown in FIG. 11(A).

The number of products "3" is displayed based on the number of corresponding products (tag numbers "TG01-1372", "TG01-1373", "TG01-1375") in the deposited product information file of FIG. 20. Specifically, for example, the product number "3" corresponds to the product (tag numbers "TG01-1372" to "TG01-1375") corresponding to the above-mentioned slip number "DN01-5422" in the deposited product information file in FIG. ), the item is displayed based on the number (specifically 3) of products (tag numbers ``TG01-1372'', ``TG01-1373'', ``TG01-1375'') whose scheduled delivery date is ``4/20''. good. Alternatively, the product number "3" may be displayed based on the number (specifically, 3) of products whose scheduled date is "4/20" and the same reservation number (specifically, 12345). .

The return slots “H31, H32” are the return slot numbers (“H21 ”, “H22”).
Note that the item "use return port" is provided in response to the case where the return port in which the product is to be stored is determined when making a return reservation. If the use/return port is determined when storing the product in the return locker, an item for the number of use/return ports may be provided in place of the item for the use/return port. The item ``Number of return slots used'' indicates the number of return slots required to store the corresponding product.
Reissue "*" is displayed based on the fact that reissue (printing multiple times) has been performed.

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

Instead of the above, 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 input in the store setting field.
For example, if an all stores button is provided on the locker return reservation confirmation screen and the all stores button is operated, the POS terminal 20 may display information related to all stores without being limited to the store. good.

Further, the user terminal 50 may display a locker return reservation confirmation screen limited to information related to the user in a predetermined manner.

The factory terminal 40 (the same applies to 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 of the store code input in the store setting field. Further, for example, if an all stores button is provided on the locker return reservation confirmation screen and the all stores button is operated, the factory terminal 40 displays information related to all stores without being limited to the stores. Good too.

When storing the product whose scheduled storage date is the start date (scheduled delivery date in the stored product information file (Fig. 20)) in the return slot, the clerk displays the locker return reservation confirmation screen shown in Fig. 24 on the POS terminal 20. Display. The clerk performs an operation on the locker return reservation confirmation screen to display a list of products for which the current day is the start date of the scheduled storage date in the result display area. After that, the clerk operates the print button. In response to the print button being operated, the POS terminal 20 issues a storage schedule list slip for the products whose scheduled storage date starts on the current day.

FIG. 25 shows an example of a storage schedule list slip. In the storage schedule list slip shown in the figure, information on the storage schedule corresponding to the current scheduled storage date is shown. In the storage schedule list slip, storage product unit areas AR1 corresponding to each storage product unit are sequentially arranged from top to bottom. One stored product unit corresponds to common products whose scheduled storage date starts on the same day under a common slip number.

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

In the customer information area AR11, information (customer information) regarding the corresponding customer (user) is shown. Specifically, in the figure, a customer number and name are shown as customer information.

In the storage instruction information area AR12, information indicating storage instructions for the corresponding product is displayed. As a specific example, in the storage instruction information area AR12 in the same figure, a reservation number, the start date of the scheduled storage date, the number of products to be stored, and the number of return slots (number of doors) are shown.

Note that if the return port has been determined at the stage when the locker return reservation is made, information indicating the return port may be shown instead of the number of return ports in the storage instruction information area AR12. In other words, a return slot number is assigned to each return slot as information indicating the return slot, and if a number is displayed for each return slot in the locker, the return slot number is assigned as information indicating the return slot. A number may be indicated.
Alternatively, the position of the return port may be indicated as the information indicating the return port. As an example, if the locker is the common locker 200 in FIG. 2(B), the position of the return port can be indicated as follows.
The return port side of the common locker in the figure includes a panel section 210a, one locker section on the left side having return ports H12, H21, H22, H31, and H32, and return ports H41, H42, H51, H52, H61, and H62. It is connected to one locker section on the right side. In a case where the locker including the left panel portion 210a is a parent locker and the right side is a child locker, the return port H52 is specifically indicated as "2-lower-middle" as information indicating the return port. "2" in "2-lower-middle" indicates a locker number when locker numbers are assigned with the parent locker as "1" and the child locker as "2". The "lower" in "2-lower-middle" indicates the lower tier of the two stacked return slots. The "middle" in "2-lower-middle" indicates the center position of the three positions in the side-by-side direction of the child lockers. In this case, the positions of the three columns in the horizontal direction are indicated by "left", "middle", and "right".
The manner in which the position of the return port is indicated is not limited to the above example. For example, the array of return ports may be printed and the corresponding return port may be indicated in a manner that allows it to be distinguished from other return ports.

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

The user goes to the backyard with the issued storage schedule list slip and takes out the products tagged with the tag number shown in the tag number area AR13 as products to be stored. During this work, the store clerk will check the tag number in the tag number area AR13, but since the tag number in the tag number area AR13 is emphasized more than other characters, the store clerk can check the tag number in the tag number area AR13. It becomes easier to confirm the tag number in number area AR13. This makes it easier for the store clerk to find the product corresponding to the tag number in the tag number area AR13.
Next, the store clerk continues to bring the storage schedule list slip and the items to be stored that have been taken out from the backyard, and goes to the location where the locker is installed. In the following explanation, a case will be exemplified in which a return locker 300 is installed as a locker for returning items to customers.
When the store clerk goes to the return-only locker 300, he first causes the code recognition section of the return-only locker 300 to read the code information printed in the code information area AR14 in one storage product unit area AR1 in the storage schedule list slip. Perform operations.

The return locker 300 transmits the read code information to the management device 10. The code information shows the reservation number. The management device 10 specifies the return port number associated with the reservation number indicated by the code information, and notifies the return locker 300 of the specified return port number.
The return locker 300 unlocks the return port corresponding to the notified return port number. When unlocking, for example, a display may be displayed on the display section of the return locker 300 to notify the store staff of the return slot number of the unlocked return slot.
Then, the store clerk stores the corresponding product to be stored in the unlocked return slot and locks the door. Thereafter, the store clerk uses the same procedure to have the code recognition section of the return locker 300 read the code information for each stored product unit area AR1 in the storage schedule list slip, unlock the return slot, and store the products to be stored. We will do the work of doing this.

Note that the unlocking of the return door, which is performed in response to the return locker 300 reading the code information printed in the code information area AR14, may be controlled as follows.
The return locker 300 transmits the read code information to the management device 10. The management device 10 compares the reservation number indicated by the code information with the contents of the locker-specific reservation status file, and determines whether the reservation number indicated by the code information is correct. Here, "determine whether the reservation number is correct (OK or NG)" means to determine whether the scheduled storage date indicated by the reservation number corresponds to the current date and time. be.
The management device 10 transmits reservation number correctness information indicating the determination result (OK or NG) as to whether the reservation number is correct to the return locker 300.
In the return-only locker 300, if the received reservation number correctness information indicates NG, the scheduled storage date of the corresponding product does not correspond to the current date and time, and the product should not be stored in the return slot. . In this case, the return-only locker 300 does not unlock the return port and, for example, notifies the user that the corresponding product should not be stored therein.
On the other hand, if the received reservation number correct/incorrect information indicates OK, the corresponding product may be stored because the current date and time corresponds to the scheduled storage date of the corresponding product. Therefore, in this case, the return locker 300 determines a return slot in which to store the corresponding product from among the return slots that are currently vacant, according to a predetermined rule. The return locker 300 unlocks the determined return port.
Further, the return-only locker 300 may acquire a locker-specific reservation status file from the management device 10, for example, and store it in its own device. In this case, the return-only locker 300 can refer to the read code information and the locker-specific reservation status file that it stores in order to determine the return port according to the reading of the code information. There is no need to communicate with

In addition, instead of the code information on the storage schedule list slip, it is also possible to read the code information such as a QR code printed on the factory record attached to the storage target product in the same way as above. The return slot number of the return slot to be stored may be specified, and the return slot may be unlocked.

[Example of processing procedures related to product collection]
As described above, in the cleaning system 1 of this embodiment, products that a customer has put into the collection section of a locker can be accepted as products to be cleaned. At some stage, the clerk will collect the products that have been placed in the collection section of the locker. If the store clerk forgets to collect the products that have been placed in the collection section of the locker, the collection section will become full at some point, causing problems such as customers being unable to put the products into the collection section. .
Therefore, in the cleaning system of this embodiment, as described below, a notification is sent to the store staff to collect the product so that the store staff does not forget to collect the product from the collection department. be done.
In the following explanation, a case will be exemplified in which a reception locker 100 is used as a locker for customers to put their products in.

With reference to the flowchart of FIG. 26(A), an example of a processing procedure executed by the reception-only locker 100 and the management device 10 in connection with setting a collection schedule flag as a collection schedule setting will be described.
Step S101: The reception locker 100 determines whether a collection trigger has occurred for the product to be cleaned stored in the collection unit 102. The occurrence of a collection trigger indicates that the product stored in the collection unit 102 has reached a capacity that requires collection.
The collection trigger may be generated when the number of times the customer deposits the product into the collection unit 102 exceeds a predetermined value, and the capacity of the product in the collection unit 102 has reached a level that requires collection.
Specifically, the reception-only locker 100 triggers the collection when the number of times the locker has been unlocked exceeds a predetermined threshold, based on the detection output of a sensor that detects the unlocking of the input port 101 of the collection unit 102, for example. It may be determined that this has occurred.
Further, for example, when the customer puts the product into the collection section 102, the customer performs an operation to make the code recognition section 106 or the card reader 125 read the information on the membership card in order to unlock the input slot 101. The reception-only locker 100 may determine that a collection trigger has occurred when the number of times the code recognition unit 106 or the card reader 125 has read the information on the membership card exceeds a predetermined value. In this case, for example, if the same customer's membership card information is read multiple times in a row, the reception-only locker 100 responds to the occurrence of a collection trigger for reading the membership card information from the second time onward. It may not be included in the number of times.

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

Alternatively, the reception locker 100 may determine that a collection trigger has occurred in response to a predetermined time.
The reception-only locker 100 may determine whether a predetermined time has arrived based on the time it clocks. Alternatively, the management device 10 or the POS terminal 20 may measure time, determine whether a predetermined time has arrived, and notify the reception locker 100 that the predetermined time has arrived.

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

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

Next, with reference to the flowchart of FIG. 26(B), an example of a processing procedure executed by the reception locker 100 and the management device 10 in connection with clearing the collection schedule flag as a collection schedule setting will be described.
Step S111: The reception locker 100 is waiting for the products stored in the collection section 102 to be collected.
The reception locker 100 may determine whether or not the merchandise has been collected as follows. When the store clerk collects the products, the store clerk unlocks the collection door of the collection section 102 according to a predetermined procedure, and locks the collection door after completing the collection of the products. Therefore, the reception-only locker 100 may determine that the product has been collected when it detects that the collection door is unlocked and then locked after the unlocking.
Alternatively, in the reception-only locker 100, as an event, the detection output of the sensor that detects the weight or capacity of the stored items in the collection unit 102 changes from a value corresponding to a state where the stored items are stored, to a state where the stored items are not stored. It may be determined that the product has been collected when the value changes to a value corresponding to .

Step S112: The reception-only locker 100 transmits a collection confirmation notification to the management device 10 in response to the determination that the product has been collected in step S111. The collection confirmation notification is for notifying that the product has been collected from the collection unit 102.

Step S211: The management device 10 waits for the collection confirmation notification sent from the reception locker 100 in step S112 to be received.
Step S212: When the collection confirmation notification is received, the management device 10 determines whether or not the collection schedule flag is currently set.
Step S213: If it is determined in step S212 that the collection schedule flag is set, the management device 10 resets the value of the collection schedule flag to a value indicating that there is no collection schedule.
On the other hand, if it is determined in step S212 that the collection schedule flag is not set, the process in the figure may be ended by skipping the process in step S213.

Through the processing in FIGS. 26A and 26B, the collection schedule flag is set, for example, in response to a situation in which it is necessary to collect the product from the collection unit 102. Further, the collection schedule flag that has been set is reset in response to the collection of the product from the collection unit 102.

An example of a processing procedure executed by the management device 10 and the POS terminal 20 in connection with collection notification will be described with reference to the flowchart in FIG. 26(C).
Step S221: The management device 10 determines whether a certain period of time has elapsed with the collection schedule flag remaining set. In this case, by setting the certain time to zero or a value close to zero, notification may be made immediately in response to the collection schedule flag being set.
Alternatively, in step S221, the management device 10 may determine whether a predetermined time has arrived while the collection schedule flag is set.

Step S222: If the collection schedule flag continues to be set for a certain period of time, the management device 10 transmits a product collection notification instruction to the POS terminal 20. The notification instruction is a command in which the management device 10 instructs the POS terminal 20 to execute a notification (collection instruction notification) for instructing the store clerk to collect.

Step S321: The POS terminal 20 waits to receive the product collection notification instruction transmitted from the management device 10 in step S122.
Step S322: In response to receiving the product collection notification instruction, the POS terminal 20 executes collection instruction notification. The POS terminal 20 may notify the collection instruction in a predetermined manner, for example, on the clerk side display section 26. By notifying the collection instruction in this manner, the store clerk can understand that the product should be collected from the reception locker 100. This can prevent store staff from forgetting to collect products from the reception locker 100.

Note that when the collection instruction is notified, the store clerk may not be able to immediately collect the product because, for example, he or she has to prioritize other tasks such as customer service. Therefore, collection instruction notification may be temporarily stopped, for example, in response to an operation to declare postponement of collection (collection postponement declaration operation). In this case, the POS terminal 20 may issue the collection instruction notification again, for example, after a certain period of time has elapsed since the collection postponement declaration operation was performed.

[Example of processing procedures related to product storage]
The flowcharts in FIGS. 27 and 28 show an example of the processing procedure executed by the locker in response to the return of the product. Here, we will take as an example a case where the process shown in the figure is executed by the return-only locker 300.
First, FIG. 27 will be explained.
Step S800: The return locker 300 waits for an operation to be performed on the standby screen, for example, with the standby screen displayed on the display unit 304.
Step S801: When an operation is performed on the standby screen, the return locker 300 requests the user to read a membership card or input a password, for example, by displaying a guidance screen in a predetermined manner.

Step S802: The return locker 300 determines whether or not the membership card has been read in response to the request in step S801. If the membership card has been read (step S802; YES), the process moves to step S804. If the membership card is not read or the like (step S802; NO), the process transitions to step S810.

Step S804: The return locker 300 notifies the corresponding return port. Specifically, the return locker 300 displays a notification screen in a predetermined manner on the display unit 304 to notify the user of the return port number of the return port in which the deposited product is stored.
Step S805: Further, the return locker 300 unlocks the return door of the corresponding return port and causes the light emitting unit to blink. Note that the light emitting unit may be turned off, for example, after the return door is opened and closed (after it is locked).
Step S806: The return locker 300 waits for the return of the locker (handover of the deposited product) to be completed. The return locker 300 may determine that the locker return has been completed, for example, when it is detected that the return door that was unlocked and opened in step S805 has been closed and locked. Alternatively, a sensor is installed at the return port to detect the presence or absence of stored items, and when the sensor detects that the state has transitioned from a state with stored items to a state without stored items, it is determined that the locker return has been completed. You may do so.

Step S807: When the locker return is completed, the return-only locker 300 stores return completion information in the storage unit 323 (which may be the RAM 322). The return completion information may include, for example, some or all of the customer ID, return port number, tag number, date and time information, and the like.
In addition to storing the return completion information in the storage unit, the return locker also sends the return completion information to the management device 10, and the management device 10 updates various files based on the return completion information. You may.
Furthermore, the management device 10 updates various screens such as the slip details screen (Figure 21, etc.) (updates the progress classification to "9 (delivery completed)", etc.), and displays the updated screen on the user terminal 50, etc. You may also do so.
Step S808: The return-only locker 300 notifies the user that the locker return has been completed, for example, by displaying a notification screen in a predetermined manner on the display unit 304.

Step S810: If it is determined in step S802 that the membership card, etc. has not been read, the return locker 300 checks whether there has been a predetermined operation by the clerk (for example, whether the clerk's barcode has been read or not). etc.). If it is determined that the predetermined operation has not been performed, the process returns to step S802.

Step S820: If it is determined in step S810 that the store clerk has performed the predetermined operation, the return locker 300 is equipped with various buttons (return item storage button, return item collection button, return button, etc.) for use by the store clerk. An initial screen (not shown) is displayed on the display unit 304. That is, the return locker 300 shifts to the clerk mode.

Next, FIG. 28 will be explained.
Step S821: After transitioning to the clerk mode in step S820, the return locker 300 determines whether or not the return button located on the clerk initial screen (not shown) has been operated. If the return button is operated (step S821; YES), the process returns to step S800. Note that when the return button is operated (step S821; YES), the process may return to step S801 instead of returning to step S800.

Step S822: If the return button has not been operated, the return-only locker 300 determines whether or not the return item storage button arranged on the clerk's initial screen (not shown) has been operated.
The return items storage button is a button that is operated by the store staff to transition the return locker 300 to the storage support mode from the store staff mode when storing the product to be returned in the return slot of the return locker 300. It is.
If the return item storage button is operated (step S822; YES), the process transitions to step S830. If the return item storage button is not operated (step S822; NO), the process transitions to step S823.

Step S823: The return-only locker 300 determines whether or not the return item collection button on the clerk's initial screen (not shown) has been operated. If the return item collection button is operated (step S823; YES), the process transitions to step S840. If the return item collection button is not operated (step S823; NO), the process returns to step S821.

Step S830: The return locker 300 transitions to storage mode. Then, the return locker 300 displays a predetermined storage guidance screen to request the store clerk to read the code information. The code information to be read here is the code information printed on the storage schedule list slip (FIG. 25). Further, the code information to be read may be code information printed on a factory record attached to the product.

Step S831: The return locker 300 determines whether or not the return button located on the storage guide screen has been operated. If the return button is operated (step S831; YES), the process returns to step S821. Note that if the return button is operated (step S831; YES), the process may return to step S800 (or step S801) instead of returning to step S821. If the return button has not been operated (step S831; NO), the process advances to step S832.

Step S832: The return locker 300 determines whether the code information has been read. If the code information has been read (step S832; YES), the process advances to step S833. If the code information has not been read (step S832; NO), the process returns to step S831.

Step S833: The return locker 300 specifies the return port where the product should be stored. For this reason, the return locker 300 transmits, for example, code information (or a reservation number indicated by the code information, etc.) to the management device 10. For example, the management device 10 specifies the return port number associated with the reservation number indicated by the received code information from the locker-specific reservation status file, and notifies the return locker 300 of the specified return port number.
The return locker 300 specifies the return port in which the product should be stored by receiving notification of the return port number from the management device 10.

Alternatively, the return port in which the product should be stored may not be determined, for example, when making a reservation to return the locker, but may be determined when the product is stored in the return-only locker 300. In such a case, the return locker 300 specifies the return port by determining the return port in which the product should be stored in accordance with a predetermined rule in step S833.

Step S834: The return locker 300 notifies the return port identified in step S833. Notification of the return slot is performed by a display on the display unit 304.
Step S835: Further, the return locker 300 unlocks the door of the identified return port and causes the light emitting unit to blink. Note that the light emitting unit may be turned off, for example, after the return door is opened and closed (after it is locked).

Step S836: The return locker 300 waits until storage of the product (deposited product) is completed. The return-only locker 300 completes storage of the product in response to determining that the return door of the return port 310 has been opened and closed once (unlocked and locked after the unlocking). It can be determined that Furthermore, for a return slot that has been unlocked but remains unlocked, it may be determined that storage has not been completed. This allows you to handle cases where you have unlocked the return door but forgot to put the product in and it remains unlocked, or if you have put the product in but forgot to lock it. It becomes possible to notify the store staff.
Step S837: When the storage of the product is completed, the return locker 300 stores the storage completion information in the storage unit 323 (which may be the RAM 322). The storage completion information stored in step S837 may include, for example, some or all of the customer ID, return port number, tag number, date and time information, and the like.

Step S838: The return locker 300 also sends a storage completion notification to the management device 10. The storage completion notification includes information that allows identification of the stored product. For example, the storage completion notification may include some or all of the information that can identify the stored product, such as the customer ID, return port number, tag number, date and time information, etc., similar to the storage completion information. .

The clerk reads the code information in the code information area AR14 in correspondence with each stored product unit area AR1 printed on the storage schedule list slip, and stores the products in the unlocked return slot. go. The processes of steps S830 to S838 are repeatedly executed in accordance with each such task. After the store clerk completes storing all the products to be returned in the return slot, the store clerk operates the return button. In response to an operation on the return button, the storage support mode is ended and the process transitions from step S831 to step S821.

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

Step S841: After executing the process of step S840, the return locker 300 determines whether or not the return button located on the return item collection initial screen has been operated. If the return button is operated (step S841; YES), the return item collection mode is ended and the process returns to step S821.
Note that if the return button is operated (step S841; YES), the process may return to step S800 (or step S801) instead of returning to step S821. If the return button has not been operated (step S841; NO), the process advances to step S842.

Step S842: The return locker 300 determines whether or not the OK button placed on the return item collection initial screen has been operated. If the OK button has been operated (step S842; YES), the process advances to step S844. If the return button has not been operated (step S842; NO), the process returns to step S841.

Step S844: If the OK button is operated in step S842, confirmation has been obtained that the store clerk intends to perform the work of collecting returned items. Therefore, the return locker 300 in this case notifies all return ports. For example, the return locker 300 displays a collection instruction screen in a predetermined manner, and notifies the return port numbers of all return ports on the collection instruction screen.

Step S845: The return locker 300 unlocks all the return doors and lights up the light emitting parts. Note that the light emitting unit may be turned off, for example, after the return door is opened and closed (after it is locked).
Step S847: The return locker 300 causes the storage unit 323 to store collection completion information indicating that the collection of the return item has been completed. 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, and the like. After the process in step S847, 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.

In addition to storing the collection completion information in the storage unit, the return locker also transmits the collection completion information to the management device 10, and the management device 10 updates various files based on the collection completion information. May be executed.

An example of a processing procedure executed by the management device 10 in connection with management of the storage completion flag will be described with reference to the flowchart of FIG. 29(A).
Step S231: The management device 10 waits for the storage completion notification transmitted from the return locker 300 in step S838 of FIG. 28 to be received.
Step S232: When the storage completion notification is received, the management device 10 refers to, for example, the tag number etc. indicated in the received storage completion notification, and selects the products currently received from among the products indicated in the deposited product information file. To identify a product for which storage has been completed in response to a storage completion notification. The management device 10 sets the storage completion flag corresponding to the product specified in the deposited product information file (FIGS. 13 and 20) to a value (for example, "1") indicating completion of storage.
As can be understood from the explanations in FIGS. 27, 28, and 29(A), the notification of completion of storage is based on the opening/closing (unlocking and unlocking) of the return door in accordance with the storage work performed by the clerk. This is transmitted from the return-only locker 300 in response to the subsequent locking. The storage completion flag is set in response to receiving the storage completion notification.

Next, an example of a processing procedure executed by the management device 10 and the POS terminal 20 in connection with notification of unstored products will be described with reference to the flowchart of FIG. 29(B).
Step S241: The management device 10 waits for the timing to check whether there are any unstored products.
The confirmation timing may be, for example, a predetermined time determined in advance according to the business schedule at the store. In this case, for example, when a predetermined time on a business day arrives, if there are unstored products among the products that should be stored on that day, a notification of unstored products can be made. .
Alternatively, the confirmation timing may be a timing at which a certain period of time has elapsed since the last storage completion notification was received by the management device 10. In this case, the notification can be made at a timing when a certain amount of time has passed after the store clerk finishes the storage work for the day.

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

Step S243: If it is determined in step S242 that there are unstored products, the management device 10 transmits an instruction to notify the POS terminal 20 of unstored products. The notification instruction for unstored products is the one in which the management device 10 notifies the POS terminal 20 that there are unstored products among the products that must be stored in the return slot on the day; This is a command that instructs execution of a notification (notification of unstored product) for instructing storage of the product in the return slot.

Step S341: The POS terminal 20 waits for the notification instruction of unstored products transmitted from the management device 10 in step S243 to be received.
Step S322: In response to receiving the notification instruction of unstored products, the POS terminal 20 executes notification of unstored products. The POS terminal 20 may notify unstored products in a predetermined manner, for example, on the clerk side display section 26.

FIG. 30 is a diagram showing an example of an unstored product notification screen displayed on the clerk side display section 26 as an unstored product notification. In the unstored notification screen shown in the figure, a message indicating that there are unstored products, a message instructing to store the unstored products, and a list of unstored products are displayed.

Since the unstored product notification is performed in this way, the store clerk can realize that the product should be stored if the store clerk has forgotten to store the product. Further, by being notified of unstored products, if there is a product that has been stored but has been forgotten to be stored, the clerk can know that there is a product that has been forgotten to be stored.
In addition, for example, in the case of the unstored product notification screen shown in FIG. 30, the store clerk can immediately grasp which products are unstored from the list of unstored products.

In addition, in the same way as when a collection instruction notification is performed, even when an unstored product notification is performed, the unstored product notification is temporarily stopped in response to the storage postponement declaration operation. good. In this case as well, the POS terminal 20 may perform the notification of unstored products again, for example, at a timing when a certain period of time has elapsed since the storage postponement declaration operation was performed.

[Closing prohibition process]
The clerk causes the POS terminal 20 to execute closing (closing) processing in response to the end of business. However, if the closing process is carried out without collecting the products from the storage section of the locker and storing the products in the return slot on the same day, the next day's business will be disrupted. .
Therefore, in this embodiment, if the collection and storage of products according to the day's business is not completed, the closing process by the POS terminal 20 is prohibited (an example of a restriction), as explained below. configured so that

The flowchart in FIG. 31 is a flowchart showing an example of a processing procedure executed by the POS terminal 20 in connection with the closing process.
Step S251: The POS terminal 20 is waiting for an operation to instruct execution of a closing process (a closing process instruction operation).
Step S252: When the closure process instruction operation is performed, the POS terminal 20 determines whether the collection schedule flag is set as the current status of the collection schedule flag. For example, even if a collection notice has been issued, if the collection postponement declaration operation is repeated and the store clerk performs the closure processing instruction operation without performing collection work, the collection scheduled flag may remain set. in a state.
Step S253: The POS terminal 20 also determines whether there are any unstored products by referring to the current deposited product information file.

Step S254: The POS terminal 20 determines, based on the determination results in steps S252 and S253, whether a condition (restriction condition) for validating the restriction on the closing process is satisfied. If both or one of the determination result that the collection schedule flag is set in step S252 and the determination result that there are unstored products in step S253 is obtained, the restriction condition is satisfied.

Step S255: If it is determined in step S254 that the restriction condition is satisfied, the POS terminal 20 prohibits the closing process.
Specifically, the POS terminal 20 does not execute the closing process, but instead issues an error notification indicating that the closing process cannot be executed. The error notification that the closing process cannot be executed may be displayed on the clerk side display section 26 (or the customer side display section 27).
Further, in the case of error notification, the reason why the closing process is prohibited may be notified. Specifically, if the restriction condition is satisfied because the collection schedule flag is set, the fact that the collection schedule flag is set may be notified as an error notification. Furthermore, in this case, a message instructing the store clerk to collect the product may be displayed in the error notification.
Furthermore, if the restriction condition is satisfied due to the presence of unstored products, the presence of unstored products may be notified. Furthermore, in this case, a message may be displayed instructing the store clerk to store the unstored products in the error notification.

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

In addition, in the process of the figure, the closing process is prohibited in step S255 in response to the restriction condition being satisfied in step S254. In other words, the POS terminal 20 performs control so as not to start the closing process itself in step S255. However, in step S254, the POS terminal 20 may execute a certain predetermined process item among the process items to be executed as the closing process, but may not execute other process items. That is, the POS terminal 20 may restrict the closing process so that predetermined processing items in the closing process are not executed.

<Modified example>
Modifications of this embodiment will be described below.

[First modification]
In the embodiment described above, regarding the storage of the product, notification is made when the product is not stored in the return slot of the locker, which corresponds to forgetting to store the product in the return slot.
In addition to not storing items, other mistakes made by store staff regarding product storage include, for example, storing items that already have a designated return slot in the wrong storage location. can be mentioned.
In this modification, notification regarding the storage of a product is configured such that notification is given not only when the product is not stored, but also when the product is stored in the wrong place. In this modification, a notification regarding the wrong storage location is given at the stage when the product is stored in a return slot different from the return slot in which it should originally be stored in the locker.
For this purpose, the locker uses the tag number shown in the code information that the store clerk has read by the code recognition unit in order to unlock the return slot in response to storing the product, and the return slot number of the unlocked return slot. A confirmation request including the following is sent to the management device 10 (which may also be the POS terminal 20).
The management device 10 determines whether the return slot number associated with the same tag number included in the received confirmation request matches the return slot number included in the received confirmation request in the locker-specific reservation status file. It is determined whether or not. The management device 10 transmits the determination result to the locker.
When the locker receives a determination result that the return port numbers do not match, it notifies the clerk who is handling the storage that the storage location is incorrect. Notification that the storage location is incorrect may be provided, for example, by a display on a display section included in the locker, or may be provided by voice. Further, notification may be performed using a combination of display and audio. Further, when notifying that the item is stored in the wrong location, the correct return slot number, etc. may also be notified.

[Second modification]
The POS terminal 20 may be used to notify the wrong storage location. In this modification, the POS terminal 20 is configured to be able to notify not only that the item has not been stored but also that the item has been stored in the wrong location.
Note that under this modification, notifications may be made on different occasions for items stored in the wrong place and items not stored, or notifications may be made on the same occasion for items stored in the wrong place and items not stored. good. In the following description, a case will be exemplified in which it is possible to notify of the wrong storage location and non-storage at the stage when the closing process is started.

To start the closing process, the clerk performs a closing process instruction operation on the POS terminal 20 as described above. The POS terminal 20 of this modification displays a closing process screen on the clerk side display section 26 in response to the closing process instruction operation being performed. In addition, if at least one of the items is not stored in the return slot of the locker or stored in the wrong location, a storage error notification screen will be displayed to superimpose the item on the closure processing screen. let

In this modification, for example, in response to the closure process instruction operation being performed, the management device 10 not only determines whether there are unstored products, but also determines whether there are products in the wrong storage location.
In the case of this modification, in addition to the storage completion flag, return port usage information indicating the number of the return port where the product was stored is provided in the deposited product information file shown in FIG. 13, for example.
Then, in response to the closure process instruction operation being performed, the management device 10 uses the return slot number indicated by the return slot usage information and the tag number of the corresponding product indicated in the locker-specific reservation status file (FIG. 15). It is determined whether the associated return port numbers are the same. If the management device 10 determines that the two are not the same, it transmits a storage error notification instruction to the POS terminal 20. The storage error notification instruction includes information regarding the product that has been stored in the wrong storage location, information regarding the corresponding customer, the return port number of the return port where the product is currently stored, the return port number of the correct return port, and the like.
In addition to determining the presence or absence of products in the wrong storage location as described above, the management device 10 also determines the presence or absence of unstored products using the same process as shown in FIG. 29, and determines that there are unstored products. In this case, an instruction to notify the POS terminal 20 of the mis-storage of the unstored products is sent.

When receiving the storage error notification instruction, the POS terminal 20 displays a storage error notification screen.
FIG. 32 shows an example of the storage error notification screen WD1. The storage error notification screen WD1 in the same figure is displayed in a pop-up window format, superimposed on the closing process screen. The storage error notification screen WD1 in the figure exemplifies cases where storage errors include forgetting to store and not storing items.

The storage error notification screen WD1 in the same figure notifies the store staff that a storage error has occurred, such as ``There was a storage error in the locker'' and ``Please check the receipt,'' and also confirms the storage error list slip. A message prompting the store staff is displayed.

In addition, as a message to inform the store staff that a storage error has occurred on the storage error notification screen WD1, if a storage error has occurred that has not been stored but the wrong storage location has not occurred, for example, ``I forgot to store it in my locker.'' The content may clearly indicate the occurrence of unstored items, such as "There is a problem." On the other hand, if there is no storage error that occurs but items are stored in the wrong place, the occurrence of the wrong storage should be clearly indicated and notified, for example by saying, ``There is a mistake in storing the items in the locker.'' It may be considered as the content.

A store clerk who sees the storage error notification screen WD1 can recognize that a storage error has occurred. Therefore, the store clerk operates the confirmation button BT1 arranged on the storage error notification screen WD1.
In response to the confirmation button BT1 being operated, the storage error notification screen WD1 is erased and the closing process screen is displayed in the foreground, making it possible to operate the closing process screen. Furthermore, in response to the confirmation button BT1 being operated, the POS terminal 20 issues a storage error list slip.

The storage error list slip is a slip that shows a list of products that are subject to storage errors. FIG. 33 shows an example of a storage error list slip. The storage error list slip shown in the figure shows an example in which a return port has been assigned in advance for the product to be stored, for example, due to locker reservation. Also shown in the figure is an example of a storage error list slip showing a total of three list items: two items not stored (forgot to store) and one item stored in the wrong place.

For items that have not been stored, customer information (customer number, name, phone number, etc.) about the customer corresponding to the applicable product, the slip number corresponding to the applicable product, date of receipt, score, and number of locker return slots. , the return port number, the tag number of the tag attached to the product, code information (the figure shows an example of a barcode), etc. The code information may include, for example, a slip number, etc., as at least part of the above information printed in the corresponding item.

In addition, for items that have been stored in the wrong place, as with items that have not been stored, customer information about the customer corresponding to the item, the slip number corresponding to the item, the date of receipt, the score, and the return slot of the locker are required. number, the tag number of the tag attached to the item, and code information. In addition, in the item "wrong storage location", the return slot number where the product in question is currently being stored incorrectly and the correct return slot number where the product should be stored are shown. Specifically, in the example shown in the figure, it is shown that the product in question is currently being stored in the return slot No. 6 by mistake, and should be stored in the return slot No. 1 correctly.

While checking the contents of each item printed on the storage error list slip, the store clerk searches for unstored items from the backyard using tag numbers, etc., and unlocks the corresponding return slot. Open and store. Additionally, if the store clerk has stored the product in the wrong place, the store clerk takes it out from the return slot, unlocks and opens the door of the correct return slot, and stores the product again. When performing such work, the clerk can unlock the return slot by having the code recognition section of the locker read the code information printed on the storage error list slip.
After the store clerk resolves the storage error as described above, he or she can return to the POS terminal 20, perform operations on the closing processing screen displayed on the POS terminal 20, and perform closing work.

Note that the management device 10 may also send the storage error notification instruction to the locker. For example, the return locker 300 may display a storage error notification screen on the display unit 304 in a manner similar to FIG. 32 in response to receiving the storage error notification instruction.
As a result, for example, if a clerk is doing some kind of work or business in the vicinity of the return locker 300 during closing operations, a storage error notification screen displayed on the display unit 304 of the return locker 300 will notify the employee of the storage error. You can know what happened. In this case, the return locker 300 may be configured so that the printing unit 326 can issue a slip listing the storage errors. As a result, a store clerk who notices a storage error from the display on the return locker 300 does not have to return to the POS terminal 20 to retrieve the storage error list slip.

Note that in the above example, the management device 10 makes the determination as to whether there is a storage error, but the POS terminal 20 or the locker acquires the information necessary for the determination from the management device 10, etc. It may also be possible to determine whether there is a storage error.

In addition to the above-mentioned storage errors in the wrong storage location and non-storage, storage errors may also include storage errors on the wrong storage date. Wrong storage date is a storage error in which a product with a scheduled return date different from the scheduled return date corresponding to the current date and time is mistakenly stored in the return slot.
Such a storage error can occur, for example, in the case of a locker, even if the code information for the product has a scheduled return date that is different from the scheduled return date corresponding to the current date and time, the return slot may be unlocked in response to the reading. This may occur if the specifications are such that the
In this case, the fact that the product was stored in the return slot due to the wrong storage date in the locker means that, for example, the management device 10 or the POS terminal 20 matches the return slot in the locker with the code information of the product stored in the return slot. This can be determined by comparing the stored information (storage result information) with the locker-specific reservation status file.

Further, like the locker storage error list slip shown in FIG. 33, the slip issued during the closing process may be made to be able to be registered in advance by an operation by a clerk.
As a specific example, when the clerk wants to register a form that he wants to issue in the closing process, he causes the clerk side display section 26 to display a reservation form setting screen by performing a predetermined operation on the POS terminal 20.

FIG. 34 shows an example of a reservation form setting screen. In the same figure, the forms issued (printed) during the closing process include a list of customer deposits and withdrawals by cashier, one sheet each for each "total" and "details" (total two sheets), and one sheet for each person in charge. A list of customer deposits and withdrawals is displayed in one sheet each for the contents of "total" and "details" (total of 2 sheets), and a list of customer deposits and withdrawals by customer is displayed in one sheet each for the contents of "total" and "details" (total of 2 sheets). An example is shown in which 1 sheet) is registered. Furthermore, an example is shown in which one each of a locker storage schedule list slip and a locker storage error list slip is registered as the forms issued (printed) during the closing process.

In the above description of this modification, the storage error notification screen is displayed at the timing when the closure process instruction operation is performed and the display of the closure process screen is started. In this case, the storage error notification screen is displayed at a timing before the start of the closing process.
However, the storage error notification screen may be displayed, for example, when an operation is performed on the displayed closing process screen and the closing process reaches a predetermined stage.
Further, for example, on the reservation form setting screen shown in FIG. 34, it may be possible to specify the timing of issuance of various forms including the storage error list form during closing processing.

[Third modification]
In the embodiment described above, the management device 10 is communicably connected to the POS terminal 20 and the locker, and controls for realizing notifications regarding the collection of products from the lockers and notifications regarding the storage of products in the lockers. An example is given in which the management device 10 executes the process.
However, the device in the cleaning system 1 may be configured to appropriately control the notification regarding collection and storage of products in the lockers as described above.
For example, in an environment where a POS terminal 20, a store mobile terminal 30, a locker, etc. are communicably connected, the POS terminal 20 controls its own device or the store mobile terminal 30 to issue notifications. good. Conversely, the store mobile terminal 30 may control the notification to be performed on its own device, the POS terminal 20, or the like. The notification may be performed on the factory terminal 40 by controlling the POS terminal 20, the management device 10, the store mobile terminal 30, etc.

[Fourth modification]
In the above embodiment, an example is given in which the locker is communicably connected to the management device 10 (which may also be the POS terminal 20). In this modification, products are collected and stored as follows in an environment where the locker is not connected to the management device 10 or the POS terminal 20. In the following description, a case will be exemplified in which a reception-only locker 100 and a return-only locker 300 are used.

First, regarding the collection of products from the collection section 102 of the reception-only locker 100, the POS terminal 20 issues a collection instruction that displays a message instructing collection of the products in response to a predetermined time. The screen is displayed on the clerk side display section 26. Then, when the store clerk performs an operation indicating acceptance of the product collection instruction in response to the display of the collection instruction screen, the POS terminal 20 and the management device 10 process the product as having been collected. .

Furthermore, regarding the storage of the product in the return slot 310 of the return-only locker 300, the POS terminal 20 displays the information on the clerk's side display at a predetermined time determined corresponding to the end time of the business day. 26 to display the product storage instruction screen.

FIG. 35 shows an example of the product storage instruction screen. The product storage instruction screen shown in the figure is exemplified in a manner similar to the locker return schedule list screen. For example, if the return slot is determined by having the locker read the code information, instead of the item "Used return slot" indicating the number of the return slot where the product should be stored, the return slot where the product should be stored is It is sufficient if an item indicating the number of mouths is provided.

The store clerk confirms the products to be stored in the return slot 310 based on the list of products to be stored, which is shown in the product list area with code C on the product storage instruction screen, and confirms the items for each list item in the product list area. The returned product is stored in the return port 310. When the store clerk stores the products corresponding to one list item, the store clerk performs a touch operation on the corresponding list item in the product list area. In the list item for which a touch operation has been performed, the storage confirmation area changes to a display indicating that the item has been stored. In the same figure, an example is shown in which the storage confirmation area changes from a state in which no objects are arranged to a state in which circular objects are arranged.

Note that there are no particular limitations on the modes corresponding to the unstored and stored states in the storage confirmation area. For example, each status may be represented by characters such as "not stored" or "stored".

By displaying such a product storage instruction screen, the store clerk can select the unstored products that should be stored, the return slots in which the unstored products should be placed (or the number of return slots required to store the unstored products). etc. can be understood.
In addition, while storing the products in the return slot one by one, the store clerk is required to operate the confirmation area of the list item corresponding to the product that has already been stored. You can keep track of the products that have already been stored inside and the products that should be stored in the future.

Also in this modification, when storing the product in the return slot of the locker, the store clerk issues a storage schedule list slip (Fig. 25) using the POS terminal 20, for example, and prints the storage schedule list slip on the issued storage schedule list slip. The return gate may be unlocked by having the locker read the code information.
Alternatively, when storing the product in the return slot of the locker, the store clerk can unlock the locker by having the locker read the code information printed on the factory record attached to the product to be stored.

In an environment where the locker is not connected to the management device 10 or the POS terminal 20, as in this modification, the locker communicates with the management device 10 and the POS terminal 20 to prevent misplacement of products stored in the return slot. It is not possible to determine whether
Therefore, in this modification, the code information of the product that is read by the locker includes the start date of the scheduled storage date, and the locker has a timekeeping function so that the locker can read the current date and time (or even up to the current date). ) can be obtained by the self.

When storing the product in the return slot of the locker, the store clerk performs an operation to cause the locker to read the code information of the product (product to be stored) to be stored in the return slot. The locker determines whether the start date of the scheduled storage date included in the read code information and the date indicated by the current date and time are the same date.
If the start date of the scheduled storage date and the date indicated by the current date and time are the same, the locker determines that the item to be stored can be stored and unlocks the return slot.
In addition, the code information may also include information on the number of return units required to store the product to be stored. In this case, if the start date of the scheduled storage date and the date indicated by the current date and time are the same, the locker can unlock the number of return slots corresponding to the number of return slots indicated by the code information.

On the other hand, if the start date of the scheduled storage date and the date indicated by the current date and time are different, this means that the date on which the product to be stored is to be stored is not that day. Therefore, in this case, the locker is configured so that the return port is not unlocked, so that storage cannot be performed. At this time, the locker may notify on the display that the storage target product cannot be stored because the scheduled start date of the storage date is different from the current date.

Further, the locker may store the storage history in response to the storage target product being stored in the unlocked return slot. The storage history includes, for example, an identifier (return port number) indicating the return port in which the product to be stored is stored, and a transaction identifier obtained from code information read when unlocking the return port. In this case, if the product to be stored is stored in a plurality of return ports, a plurality of return port numbers may be indicated in the storage history.
In this case, the customer who comes to pick up the product causes the code recognition unit of the locker to read the code information printed on the deposit slip or the code information displayed on the electronic deposit slip. The locker can search for a storage history that includes the same transaction identifier as the one included in the read code information, and unlock the return port with the return port number indicated by the searched storage history. In this case, if the searched storage history indicates a plurality of return slot numbers, the return slot for each return slot number is unlocked.
In this way, in this modification, by storing the storage history in the locker, it is possible to properly return the product (storing it in the return slot and taking it out from the return slot by the customer). I can do it.

[Fifth modification]
In the embodiment described above, the POS terminal 20 can issue a deposit slip along with a factory copy, etc. as a paper-based slip, for example, at the time of payment (step S20 in FIG. 7). Furthermore, in the case of a customer who specifies to return the locker, the deposit slip may be used for authentication when picking up the product from the locker. Therefore, as this modification, an example of the form of a deposit slip that is issued in response to a request to return a locker will be described.

FIG. 36 shows an example of a deposit slip issued in response to a request to return a locker.
In the deposit slip shown in the same figure, the product name, tag number, amount, return classification (in this case, "Return to Locker", etc.) are printed as information regarding the product to be kept. , a code information area AR31 and a pick-up guide area AR32 are arranged.In addition, the code information area AR31 and pick-up guide area AR32 are omitted in the deposit slip issued in response to the case where locker return is not specified. .

Code information area AR31 is an area where code information is printed. The code information printed in the code information area AR31 includes, for example, transaction number, customer code (customer ID), store code, number of used and returned tickets, used and returned number, PIN number, locker storage date, number of stored items, etc. Depending on the operation, etc., a predetermined number of information (authentication information) required for authentication at the locker may be included.

The pick-up guide area AR32 is an area where information related to pick-up guidance for the product (pick-up guide information) is printed. In the example shown in the figure, the pick-up guide information includes a date and time range in which items can be picked up from a locker, and the number of return slots (number of lockers used) in which items to be picked up are stored. There are no particular limitations on the contents of the collection guidance information in the collection guidance area AR32. For example, the collection guidance information may indicate the return slot number of the return slot in which the product to be collected is stored.

Further, in the deposit slip, the positions where the code information area AR31 and the collection guide area AR32 are arranged are not particularly limited, and may be changed as appropriate. For example, by arranging the pick-up guide area AR32 above the deposit slip to make it easier for customers to see, it can be expected that customers will be able to more reliably understand the date and time range in which pick-up is possible.

When the customer picks up the product stored in the return slot of the locker, the customer brings the deposit slip and causes the code recognition section of the locker to read the code information in the code information area AR31.
The locker identifies the return slot (return slot for pick-up) containing the product that is associated with the same authentication information as that included in the read code information. For example, when the authentication information is a transaction number, the locker specifies the return port containing the product associated with the same transaction number as the one included in the read code information as the return port to be picked up. The locker unlocks the return port for the specified pick-up object.
On the other hand, if the return port to be picked up is not specified, the locker will not unlock any return port.
By controlling the unlocking of the locker in this way, the customer can reliably pick up the item he or she has deposited without mistaking it for another customer's item.

[Sixth variation]
As explained in the previous embodiment, if a product remains stored in the return slot without being picked up by the customer even after the delivery deadline has passed (unclaimed product), the store staff will carry out the collection work of the product. conduct.
When the locker is communicably connected to the management device 10 and the POS terminal 20, the locker stores a storage history indicating the result of storing the product at the return slot, and a collection history indicating the result of picking up the product from the return slot by the customer. etc. can be sent to the management device 10 and POS terminal 20.
The storage history includes, for each return port number, a history regarding opening and closing of the return door when the product was stored, a history of operations performed by a store clerk in response to storage, and the like.
Further, the collection history includes, for each return slot number, a history regarding the opening and closing of the return door when the product was collected, a history of operations performed by the customer in response to the collection, and the like.
The management device 10 and POS terminal 20 check the status of unclaimed products (presence of untransacted products, presence of untransacted products, You can check the return slot where the item is stored, the elapsed time from the delivery deadline, etc.). Therefore, the management device 10 and the POS terminal 20, for example, check the status of uncollected products before the time when the store clerk is supposed to collect the uncollected products, and send the confirmed information to the store clerk. configured to output.
For example, on the locker return reservation confirmation screen displayed on the POS terminal 20 when the clerk stores the cleaned products in the locker, the current status of the unclaimed products may also be displayed. As a result, the store clerk can grasp the current uncollected products in advance and proceed with the work smoothly, such as collecting these products and storing the products in the locker.
Additionally, if a customer corresponding to the confirmed uncollected product is using the user terminal 50, the POS terminal 20 or the management device 10 notifies the cleaning app that there is an uncollected product. A notification may be provided. Further, the notification that there are uncollected products may be sent by SMS (Short Message Service) or email.

Furthermore, if the locker is not communicably connected to the management device 10 or the POS terminal 20, the handling of unclaimed products may be done as follows.
In this case, in response to the clerk performing an operation on the locker to switch to clerk mode (for example, the above-mentioned operation on the return item collection button), the locker will be displayed on the display. A list of unclaimed products will be displayed. Further, the locker may issue a slip showing a list of unclaimed products. The contents of the list of unclaimed products may be generated based on the storage history and collection history stored in the locker.
The clerk can collect the uncollected products from the locker while checking the list of uncollected products output from the locker as described above.
Then, the store clerk registers the uncollected goods by having the POS terminal 20 read the code information printed on the factory record attached to the collected uncollected goods. Registration of uncollected products (that is, storage of a list of uncollected products) may be performed at the POS terminal 20 or may be performed at the management device 10 via the POS terminal 20.
By registering unclaimed products in this way, the POS terminal 20 or the management device 10 sends a notification to the cleaning app on the user terminal 50 or sends an e-mail, SMS, etc. to notify the customer of the unclaimed products. It is possible to notify that the product is available.

[Seventh modification]
The same user (customer) who uses the store corresponding to the cleaning system 1 of this embodiment may be registered as a member twice for some reason. For example, a user who previously became a member and used the store has not used the store for a while, but when he resumed using the store, he did not remember whether he had previously registered as a member or not. You may need to register as a member again. In such a case, the current membership registration will be performed for the same user without canceling the previous membership registration. As a result, multiple membership registrations will overlap for the same user.
Customer information (customer master file (Figure 11(A)), customer performance summary file (Figure 11(B)), and point management file (Figure 11(C)) is managed for each registered member. Therefore, if multiple membership registrations are duplicated for the same user, multiple pieces of customer information will exist for the same user.

As mentioned above, the fact that multiple membership registrations have been performed may become apparent, for example, when a store clerk interacts with a user and retrieves customer information. In such a case, it is preferable to integrate the membership registrations corresponding to the users into one, and also to integrate the customer information into one.
Therefore, in this modified example, even though multiple customer information exists for the same user as described above, it is possible to integrate the customer information into one as follows. .

In this case, the store clerk specifies common information (for example, name) regarding the customer's membership registration details, and then performs an operation on the POS terminal 20 to declare the integration of customer information. In response to this operation, the POS terminal 20 displays a customer information integration screen on the clerk side display section 26. The customer information integration screen is a screen on which an operation for integrating multiple pieces of customer information having specified common information is performed.

FIG. 37 shows an example of a customer information integration screen. The customer information integration screen in the figure shows a case where two pieces of duplicate customer information about the same user are integrated. In other words, on the customer information integration screen in the same figure, two customer information areas AR21-1 and AR21-2 respectively correspond to "customer information 1" and "customer information 2" as the two duplicate customer information. It is shown. In each of the customer information areas AR21-1 and AR21-2, predetermined items included in customer information are arranged in the same order. In the following description, if there is no particular distinction between customer information areas AR21-1 and AR21-2, they will be referred to as customer information area AR21.

Further, an integrated operation area AR22 is arranged on the right side of the customer information area AR21-2. In the integrated operation area AR22, integrated buttons are arranged corresponding to each item of customer information arranged in the customer information area AR21.
For example, two integrated buttons, a "1" button and a "2" button, are arranged corresponding to the "customer number" item in the customer information area AR21. When integrating the customer information, the store clerk performs an operation to select the use of the customer number in either the customer information area AR21-1 or AR21-2. In other words, the clerk operates the "1" button when selecting the "customer number" in the customer information area AR21-1, and presses the "2" button when selecting the "customer number" in the customer information area AR21-2. Operate the button. Of the "1" button and the "2" button, the selected integrated button may be highlighted.
In this way, for customer information items where two integrated buttons, the "1" button and the "2" button, are arranged, the clerk can operate either the "1" button or the "2" button. As for the items after integration, it is possible to specify information used in either "Customer Information 1" or "Customer Information 2". Specifically, when the clerk operates the "1" button in response to "Customer Number", "0000000003", which is the "Customer Number" of "Customer Information 1", becomes the "Customer Number" after integration. used as.
In addition, for "points", "unaccounted balance", "deposit balance", etc. in customer information area AR21, three buttons, "1" button, "2" button, and "addition" button, are available in integrated operation area AR22. Placed. In this case, the clerk can set the point balance of either "Customer Information 1" or "Customer Information 2" as the post-integration point balance by operating the "1" or "2" button. . Alternatively, by operating the "Add" button, the clerk can set the number of points obtained by adding the point balances of "Customer Information 1" and "Customer Information 2" as the point balance after integration.

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

Note that, for example, the customer information of any one of the plurality of customer information areas AR21 may be set as the default content after integration. For example, if "Customer Information 1" is set as the default content among "Customer Information 1" and "Customer Information 2", the store clerk must press the "1" button when selecting the "Customer Information 1" item. There is no need to operate the ``1'' button or the ``Add'' button when you want to select an item of ``Customer Information 1'' or want to add.
Furthermore, several examples can be given as to which of the plurality of pieces of customer information is to be set as the default. For example, the customer information with the oldest date or the newest customer information can be set as the default for any of the date-related items such as the expiration date, the date of first reception, the date of last reception at the store, and the date of last use of the store. Alternatively, the customer information with the highest point balance indicated by the "Points" item can be set as the default.
Note that the number of pieces of customer information to be integrated is not limited to two, and may be a larger number of pieces of customer information.

[Eighth modification]
Note that the configuration related to collecting and storing items in lockers in this embodiment is not limited to cleaning services. As an example, the configuration of the present embodiment is applicable to a service for accepting requests for shipment of packages (an example of goods) from customers and receiving packages from customers using, for example, lockers, boxes, etc. for package management of courier companies. can also be applied.

<Summary of embodiments>
(1) As explained above, one aspect of the present embodiment includes storage means (for example, lockers 100, 200, 300) for storing articles to be stored or collected, and articles from the storage means (for example, cleaning a schedule storage means for storing a schedule for collection of a corresponding product) or a schedule for storing articles in the storage means; and presence or absence of a predetermined event corresponding to the collection or storage corresponding to the schedule stored by the schedule storage means. This is an article management system (for example, a cleaning system 1) that includes a determination means for determining the determination result, and a notification control means for controlling so that notification is performed based on the determination result by the determination means.
According to the above configuration, notification is performed when there is a product that has not been collected in the locker or a product that should be stored in the locker is not stored. As a result, in the cleaning system 1, a store clerk (an example of a trader) can perform collection work and storage work corresponding to the locker of the product to be cleaned without forgetting to do so.

(2) One aspect of the present embodiment is the above article management system, in which when the determination means determines that the predetermined operation is not performed, the article is the object of storage. The apparatus further includes a closure processing restriction means for restricting closure processing of a terminal device (for example, POS terminal 20) to which registration is performed.
According to the above configuration, it is possible to prevent the closing process of the POS terminal 20 etc. from being performed while there are products in the locker that have not been collected or products that should be stored in the locker are not stored. .

(3) One aspect of the present embodiment is the article management system described above, in which the notification control means is configured to notify when a predetermined operation related to storage is not performed when a predetermined operation related to storage is not performed. To ensure that information regarding items that are not available is reported.
According to the above configuration, in the notification in response to the fact that the product that should be stored in the locker is not stored, it becomes possible to also show information regarding the product that is not stored. As a result, when receiving the notification, the store clerk can not only realize that the product should be stored, but also be able to grasp which product should be stored.

(4) One aspect of the present embodiment is the above article management system, in which the determination means determines whether storage is performed as indicated by the contents of the stored schedule, as the presence or absence of a predetermined event corresponding to storage. The notification control means makes a notification based on the determination result as to whether or not storage has been performed as indicated by the contents of the stored schedule.
According to the above configuration, the cleaning system 1 checks whether the storage is completed as indicated by the contents of the stored schedule, for example, on the scheduled delivery date, and whether the stored products are correctly placed in the designated return slot. It becomes possible to determine whether the item is stored or not. The cleaning system 1 can then provide notification according to the determination result. In other words, if the cleaning system 1 has not completed the storage on the scheduled delivery date, it will notify the store staff that the item has not been stored, and if it has not been stored in the designated return slot, the cleaning system 1 will notify the store staff that the item has not been stored in the designated return slot. This can be reported to the store staff.

(5) One aspect of the present embodiment is a sales data processing device including the notification control means of the article management system according to any one of (1) to (4) above. Note that the sales data processing device of this embodiment may be any of the management device 10, POS terminal 20, store mobile terminal 30, and factory terminal 40.

(6) One aspect of the present embodiment is to cause a computer in the article management system to store a schedule for collecting articles from a storage means for storing articles to be stored or collected or a schedule for storing articles in the storage means. a schedule storage means, a determination means for determining the presence or absence of a predetermined event in accordance with collection or storage corresponding to the schedule stored by the schedule storage means, and notification for controlling so that notification is performed based on the determination result by the determination means. This is a program for functioning as a control means.

(7) One aspect of the present embodiment includes a schedule storage step of storing a schedule for collecting the article from a storage means for storing the article to be stored or collected or a schedule for storing the article in the storage means; A determination step for determining the presence or absence of a predetermined event corresponding to collection or storage corresponding to the schedule stored in the storage step, and a notification control step for controlling so that notification is performed based on the determination result in the determination step. This is a material management method.

Note that a computer-readable record of programs for realizing the functions of the above-mentioned management device 10, POS terminal 20, store mobile terminal 30, factory terminal 40, user terminal 50, lockers (100, 200, 300), etc. By recording the program on a medium and having the computer system read and execute the program recorded on the recording medium, the above-mentioned management device 10, POS terminal 20, store mobile terminal 30, factory terminal 40, user terminal 50, It may also be processed as a locker (100, 200, 300) or the like. Here, "reading a program recorded on a recording medium into a computer system and executing it" includes installing the program on the computer system. The "computer system" here includes hardware such as an OS and peripheral devices. Further, a "computer system" may include a plurality of computer devices connected via a network including the Internet, a WAN, a LAN, a communication line such as a dedicated line, etc. Furthermore, the term "computer-readable recording medium" refers to portable media such as flexible disks, magneto-optical disks, ROMs, and CD-ROMs, and storage devices such as hard disks built into computer systems. In this way, the recording medium storing the program may be a non-transitory recording medium such as a CD-ROM. The recording medium also includes a recording medium provided internally or externally that can be accessed from the distribution server to distribute the program. The code of the program stored in the recording medium of the distribution server may be different from the code of the program in a format executable by the terminal device. That is, as long as it can be downloaded from the distribution server and installed in an executable form on the terminal device, the format in which it is stored on the distribution server does not matter. Note that the program may be divided into a plurality of parts, downloaded at different timings, and then combined on a terminal device, or the distribution servers that deliver each of the divided programs may be different. Furthermore, a ``computer-readable recording medium'' refers to a storage medium that retains a program for a certain period of time, such as volatile memory (RAM) inside a computer system that serves as a server or client when a program is transmitted via a network. This shall also include things. Moreover, the above-mentioned program may be for realizing a part of the above-mentioned functions. Furthermore, it may be a so-called difference file (difference program) that can realize the above-mentioned functions in combination with a program already recorded in the computer system.

1 cleaning system, 10 management device, 20 POS terminal, 26 clerk side display section, 27 customer side display section, 28 printing section, 30 store mobile terminal, 40 factory terminal, 50 user terminal, 90 network, 100 reception desk locker , 101 Input port, 102 Collection section, 200 Common locker, 300 Return locker, 310 Return port

Claims (7)

a schedule storage unit that causes a storage unit to store a schedule for collecting the article from a storage means for storing the article to be stored or collected or a schedule for storing the article in the storage means;
a determination unit that determines the presence or absence of a predetermined event according to collection or storage corresponding to the schedule stored in the storage unit by the schedule storage unit;
If the determination unit determines that the predetermined event does not occur, control is performed so that the POS terminal is notified of the absence of the predetermined event during a predetermined process related to the closing process of the POS terminal. An article management system comprising a notification control section and. The article management system according to claim 1, further comprising a printing unit that prints information regarding the schedule for which the determination unit has determined that the predetermined event does not occur. The article management system according to claim 2, wherein the printing unit prints information regarding a schedule for which the determining unit has determined that there is no predetermined event as information regarding a schedule in which a clerk's work error regarding product storage has occurred. . further comprising a reception unit that receives an instruction to execute a closure process for the POS terminal,
The notification control unit controls the notification so that the notification is performed in response to the determination unit determining that the predetermined event does not occur when the reception unit receives the instruction. The article management system according to any one of 3 to 3. Computers in goods management systems,
schedule storage means for storing in a storage unit a schedule for collecting the article from a storage means for storing the article to be stored or collected or a schedule for storing the article in the storage means;
determining means for determining the presence or absence of a predetermined event corresponding to collection or storage corresponding to the schedule stored in the storage unit by the schedule storage unit;
If the determination means determines that the predetermined event does not occur, control is performed so that the POS terminal is notified of the absence of the predetermined event during a predetermined process related to the closing process of the POS terminal. A program to function as a notification control means. An article management method in an article management system, comprising:
a schedule storage step in which the schedule storage unit stores in the storage unit a schedule for collecting the article from a storage means for storing the article to be stored or collected or a schedule for storing the article in the storage means;
a determining step in which the determining unit determines whether or not a predetermined event occurs according to collection or storage corresponding to the schedule stored in the storage unit in the schedule storing step;
When the notification control unit determines in the determination step that the predetermined event does not occur, the notification control unit issues a notification regarding the absence of the predetermined event at the POS terminal during a predetermined process related to the closing process of the POS terminal. An article management method comprising: a notification control step for controlling the information so that the information is received; schedule storage means for storing in a storage unit a schedule for collecting the article from a storage means for storing the article to be stored or collected or a schedule for storing the article in the storage means;
determination means for determining the presence or absence of a predetermined event corresponding to collection or storage corresponding to the schedule stored in the storage unit by the schedule storage unit;
When the determining means determines that the predetermined event does not occur, a notification for controlling the own terminal to issue a notification regarding the absence of the predetermined event when the own terminal performs a predetermined process regarding the closing process. A POS terminal comprising a control means and.

Images