Parcel locker bank system with automatic configuration

Abstract

It is an object of the present invention to provide a parcel locker bank system with automatic configuration.SOLUTION: Devices, systems, techniques, and computer-readable instructions are provided that enable use of a locker bank system by an ad hoc enterprise that does not require extensive configuration by a human integrator when subscribing to the locker bank system. When an ad hoc business joins the locker bank system, a business profile is selected based on the business type and other attributes of the business. The profile includes settings and other behaviors of the locker bank system that are appropriate for the business sector of the enterprise, thus enabling automatic subscription of the enterprise and automatic provisioning of locker bank resources for use by the enterprise.SELECTED DRAWING: Figure 1

Description

[Background technology]

[0001] Electronic locker bank systems are used for the delivery and storage of various types of goods. They can be used by shipping agencies to deposit shipments that can be picked up from the electronic locker bank by the recipient or, if not picked up by the recipient in time, ultimately collected by the shipping agency. In other applications, electronic locker bank systems can be used by retailers to deposit store items purchased by customers either online or in-store so that the customers can later retrieve their purchases from the electronic locker bank. A typical architecture for an electronic locker bank system generally includes a network of electronic locker banks, all in direct communication with a remote locker management system that is responsible for managing the network of electronic locker banks and also for managing data exchange with the retailer's or shipping agency's information systems.

[0002] Electronic locker banks are often operated by a user via an integrated user interface, such as a touchscreen. Some electronic locker banks may be operated by a mobile device, such as a personal digital assistant (PDA) or smartphone carried by the user, as described in EP 3306577. The mobile device may be used to scan shipments and read identification barcodes and / or shipping labels. Such operation with a mobile device is particularly suited to smart, autonomous compartments that operate without any power connection and rely only on replaceable batteries, as described in EP 3671665, EP 3671670, or EP 3671671. For example, in the case of a shipping agency using a mobile device to operate an electronic locker bank, the mobile device may provide a logistics application provided by the shipping company to manage shipment delivery and a locker bank application provided by the locker bank provider to operate the locker bank. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] European Patent Application Publication No. 3306577 [Patent Document 2] European Patent Application Publication No. 3671665 [Patent Document 3] European Patent Application Publication No. 3671670 [Patent Document 4] European Patent Application Publication No. 3671671 [Patent Document 5] U.S. Patent No. 11,386,389 [Patent Document 6] U.S. Patent No. 11,657,365 [Patent Document 7] U.S. Patent Application Serial No. 18 / 424,454 [Patent Document 8] U.S. Patent Application Serial No. 18 / 424,439 [Patent Document 9] US Patent Application Publication No. 2023 / 0316836 Summary of the Invention [Means for solving the problem]

[0004] The embodiments disclosed herein provide devices, systems, techniques, and computer-readable instructions that enable use of the LockerBank system by ad-hoc companies without requiring extensive configuration by a human integrator when joining the LockerBank system. In some embodiments, a company profile is selected for a company based on the company's industry, where the profile includes configuration settings and other behaviors of the LockerBank system that are appropriate for the company's industry. [Brief explanation of the drawings]

[0005] [Figure 1] FIG. 1 is a diagram illustrating an example of a locker bank system. [Figure 2] FIG. 1 illustrates an example of a locker bank system in communication with ad-hoc companies that have joined the system, according to embodiments disclosed herein. [Figure 3A] FIG. 1 illustrates example processes and communication flows suitable for use with embodiments disclosed herein. [Figure 3B] FIG. 1 illustrates example processes and communication flows suitable for use with embodiments disclosed herein. [Figure 3C] FIG. 1 illustrates example processes and communication flows suitable for use with embodiments disclosed herein. [Figure 3D]FIG. 1 illustrates example processes and communication flows suitable for use with embodiments disclosed herein. [Figure 3E] FIG. 1 illustrates example processes and communication flows suitable for use with embodiments disclosed herein. [Figure 4] FIG. 1 illustrates an exemplary process for creating a profile for a company within a locker bank system for onboarding an ad hoc company to the system as disclosed herein. [Figure 5] FIG. 1 illustrates an example lookup table suitable for use in determining an ad hoc company's industry sector, according to embodiments disclosed herein. [Figure 6A] FIG. 1 illustrates an exemplary user interface that may be provided on a mobile application for registering an ad hoc business into the system, according to embodiments disclosed herein. [Figure 6B] FIG. 1 illustrates an exemplary user interface that may be provided on a mobile application for registering an ad hoc business into the system, according to embodiments disclosed herein. DETAILED DESCRIPTION OF THE INVENTION

[0006] As previously described, electronic locker banks offer a variety of shipping, storage, and delivery infrastructure and options for retailers, carriers, shippers, and customers. However, conventional electronic locker bank systems generally require individual customization to be integrated into the logistics workflow of a retailer, carrier, or other enterprise. For example, developers may customize interface options on each locker bank to match delivery options, shipping label content, and other characteristics that vary among carriers. Furthermore, back-end systems used by retailers or carriers to prepare and manage shipments often need to be customized to communicate with the locker bank system to determine, for example, whether locker storage bins are available at the desired location for the desired size and time of delivery, to send confirmation data when the shipment is collected, and so on. This means that conventional locker banks are generally not available for use by enterprises, such as regional business operators or other small businesses, that do not have the resources to implement such customization.

[0007] The embodiments disclosed herein provide methods and systems that enable an electronic locker bank system to provide a non-carrier distribution channel that can be used by any business, such as to forward items to customers, receive returns from customers, provide returns to any of multiple suppliers, and / or use one or more carriers. For example, the embodiments disclosed herein may enable small and local businesses to leverage the benefits of a complete locker bank system without requiring expensive and time-consuming customization. As used herein, a "non-carrier" distribution channel refers to a distribution channel that is not tied to an individual package carrier and instead is available for use by multiple package carriers or directly by businesses and customers without any carrier intervention. A non-carrier distribution channel may be managed by a third party that coordinates the availability, use, and maintenance of one or more package lockers.

[0008] An example of a non-carrier distribution channel is an open locker system that allows multiple carriers, such as national, regional, or local postal carriers, private third-party carriers such as FedEx, DHL, UPS, etc., or a combination thereof, to utilize locker bank devices to deliver packages to recipients and pick up packages from shippers, such as retail returns. An open locker system may thus enable, for example, a retailer to ship packages to customers and / or pick up return packages from customers using multiple carriers.

[0009] Similarly, non-carrier distribution systems or channels may be used by businesses, such as local business corporations or other smaller enterprises, to provide and receive goods directly from their customers. For example, embodiments disclosed herein enable businesses, such as local business corporations, to utilize an open locker system as disclosed herein to provide goods directly to their customers, receive returned or exchange goods directly from their customers, and the like, without having to use a commercial third-party carrier, such as FedEx, UPS, or DHL. The use of such carriers can often be too technically complex, expensive, and / or inefficient for small businesses to implement in conjunction with their internal inventory and order delivery systems. The embodiments disclosed herein therefore provide a technical solution to problems small businesses may face when improving delivery of goods, receipt of returned goods, and the like, when large enterprise carrier systems are overly complex for the needs of the small business.

[0010] FIG. 1 illustrates an example of a luggage locker bank system, sometimes referred to as a “luggage locker system,” “locker network,” or the like, that includes one or more electronic locker banks 101, 102. Each locker bank 101, 102, etc., may include multiple lockers therein, i.e., individual storage boxes used to store items being transferred between a business and its customers or other senders and recipients. Each locker bank generally includes multiple lockers, which may vary in size to accommodate the transfer of various items. The operation of individual lockers within each locker bank may be the same as that disclosed herein with respect to the locker bank, unless otherwise noted or made clear by contextual requirements. For example, in some embodiments, each locker within a locker bank may be managed as disclosed herein with respect to the locker bank. Individual lockers within a locker bank may also be referred to as “storage boxes” in this disclosure. The locker bank may communicate with user devices, such as mobile phones, tablets, and the like, via short-range local communication systems known in the art. For example, the locker banks 101, 102 may provide an interface for carriers to provide package information, verify delivery, etc., and / or for recipients to retrieve packages previously delivered to the locker banks, such as via a mobile device 107. In order for a business to have access to the locker banks in the system, the business must subscribe to the system. Once subscribed, the business can use the locker banks in the system to send and / or receive goods, either directly to / from recipients or via a carrier.

[0011] The locker bank management server 110 may communicate with one or more locker banks 101, 102 via a communications network 105, such as a virtual private network (VPN), the Internet, etc. The management server 110 manages authorized access to the electronic locker banks and data regarding shipments handled by each electronic locker bank 101, 102. As used herein, a "management server" may refer to any suitable combination of one or more server-type computing devices operating alone or in parallel to provide the services disclosed herein. The management server may include one or more physical computer servers that may operate as a cluster, a collaborative network, a cloud network service, etc.

[0012] In a closed or proprietary locker system, the management server 110 may be owned and operated by a single carrier that also owns and manages the locker banks 101, 102. In this configuration, the locker banks 101, 102 are only available for use by the carrier that owns them. Alternatively, the locker banks 101, 102 may be part of an open locker network that allows use of the locker banks by multiple carriers. In this configuration, the management server 110 may be owned and operated by a third party, typically a non-carrier entity such as Quadient. One or more carriers 114 may interface with the management server 110 by communicating over a long-distance network, which may be the same communication network 105 used to communicate with the individual locker banks 101, 102, or the one or more carriers 114 may be a separate network for, for example, obtaining availability information, delivery confirmations, etc. Similarly, in embodiments disclosed herein, a business, such as a regional business company, can communicate with the management server, such as via an app on a local device, such as a smartphone or tablet, to obtain information regarding lockers and / or locker banks available for use by the business, obtain delivery confirmations, etc.

[0013] Each electronic locker bank 101, 102 includes multiple storage boxes of different sizes. Each storage box may be equipped with electronically controlled doors, package delivery sensors, etc. The electronic locker banks may be used, for example, by recipients of these shipments or by retailers to deposit items purchased by the retailer's customers and / or to receive returns from their customers. The locker banks 101, 102 may be installed in public outdoor or indoor locations, on the campuses of various businesses, in apartment complexes, private communities, universities, etc.

[0014] In an open locker network, a carrier 114 or retailer's information system may communicate with a management server 110 over a long-distance communication network, such as long-distance communication network 105, to manage the delivery and pickup of shipments and items. The management server 110 may centralize data for multiple information systems of different carriers. An electronic locker bank may operate to deposit retail items or shipments using a mobile device 107, such as a personal digital assistant or smartphone, carried by a shipping agent. An electronic locker bank may also operate to deposit or retrieve shipments using a mobile device 107, such as a smartphone, carried by a retailer's customer or shipment recipient. The carrier 114's information system communicates with the mobile device 107 over a long-distance communication network, such as long-distance communication network 105.

[0015] Further details regarding the locker banks 101, 102 and examples of the configuration and operation of locker bank systems are provided in EP 3306577, EP 3671665, EP 3671670, and EP 3671671, and U.S. Pat. Nos. 11,386,389 and 11,657,365, the disclosures of each of which are incorporated by reference in their entirety. Examples of open locker networks suitable for use with the embodiments disclosed herein are described in further detail in U.S. Patent Application No. 18 / 424,454, filed January 26, 2024, published as U.S. Patent Application Publication No. 2024 / 0257042, and U.S. Patent Application No. 18 / 424,439, filed January 26, 2024, published as U.S. Patent Application Publication No. 2024 / 0257041, the disclosures of each of which are incorporated by reference in their entirety.

[0016] 2 illustrates one embodiment disclosed herein in which different types of businesses use a locker network including multiple locker banks 101, which may include any number of locker banks managed by one or more management servers 110. As previously disclosed with respect to FIG. 1, in an open locker network, access to the locker network may be provided to any number of carriers 114. Recipients of packages delivered to lockers within the locker bank 101 may access the lockers storing the packages via local mobile devices 107; similarly, individuals, such as customers of a retailer or other business, may deposit items in the locker bank 101 to be returned via the retailer's or other business's return process, as previously described, via interaction with the local mobile devices 107; and / or carriers 114 may access the locker bank via local devices 107, such as to deposit and / or retrieve packages from lockers within the locker bank 101.

[0017] Two different types of businesses may be provided with access to the locker bank 101. In a traditional locker network, a subscribing business 201 is typically a large retailer, such as a regional, national, or international entity, that utilizes the locker network to deliver packages to customers, receive returns from customers, etc. As previously disclosed, a subscribing business 201 will generally have subscribed to the locker bank system through customized software, integration with the business's existing logistics system, etc. The operation of the locker bank 101, management server 110, and carrier 114 for a subscribing business 201 will generally be similar in the system disclosed herein to that in a traditional locker bank system.

[0018] Other types of businesses that may use a locker bank system as disclosed herein are referred to as “ad hoc” businesses. The embodiments disclosed herein provide ad hoc businesses with access to the locker bank system without requiring extensive onboarding processes, customization, integration with existing logistics systems, and the like. An ad hoc business 220 may be, for example, a small or local retailer or other business, a regional business, etc., that may not have extensive logistics support or may rely on a third-party system, such as a host system, to provide such support. The embodiments disclosed herein enable ad hoc businesses 220 to similarly utilize the locker bank 101 through a simplified process and user interface by automatically configuring the operation of the locker bank based on the type of business the business 220 does. For example, a shoe retailer, a regional business that delivers food to its customers, and a regional business that uses the locker bank only to receive merchandise being returned by local customers may desire to use different behaviors for the operation of the locker bank. In some embodiments, a single locker bank or a network of locker banks may be configured for normal use, specific use, or a combination of the two. In some embodiments, individual lockers may be reserved for use only by one type of business, such as when a portion of the lockers in a locker bank are reserved for specific uses and not made available for general use. In some embodiments, all lockers in an entire locker bank may be reserved for general use only or for specific uses only. In some embodiments, individual lockers may be configured for both general use and specific uses, such as when a locker is available for either use case based on first use, expected or estimated demand, known availability, etc.

[0019] 3A-3E illustrate various operations and related communications between a locker bank and other businesses according to embodiments disclosed herein. Examples of processes that may be implemented within the locker bank system include a registration process 390, a locker storage box reservation process 391, a label creation process 392, a carrier shipment preparation and delivery 393, a direct product delivery 394, a direct product return 395, and a product recovery process 396. Generally, each process may be implemented in any order, independent of other processes, unless otherwise logically required or disclosed herein. For example, while the registration process 390 will generally be required before any other process can be used, the reservation process 391 may be used before, after, or simultaneously with other processes, such as when a business uses the locker bank for more than one customer, or may be omitted entirely if the retailer does not explicitly choose to reserve lockers in advance. Similarly, some processes may be automatically initiated or implemented, in whole or in part, by the locker bank system as disclosed herein. For example, reservation process 391 may be performed by a user of the locker bank system to reserve a locker before shipping label creation process 392 or an equivalent process is performed, or reservation process 319 may be initiated automatically as part of shipment preparation process 393. Some steps may be omitted from some of the processes. For example, for some shipment preparation processes 393, a shipping label may not be required. This may be the case when a business is offering an item to a customer but does not want the item to be forwarded by a carrier, such as when the customer is local to the business and / or locker bank, or when the business is returning the item to the customer (e.g., a repaired item). In that case, the step of checking package availability 334 may be omitted, and the concurrent or preceding label creation process 392 may be omitted. In some embodiments, the locker bank will update the management server upon the successful loading of a package into a locker within the locker bank, whether the package is being forwarded to the recipient via a carrier or for direct collection by the recipient.

[0020] FIG. 3A illustrates a registration process 390. In this process, an ad hoc operating company may register with a locker bank system as disclosed herein, such as a system including the management server 110 and locker bank 101 as previously disclosed. At 303, a user associated with the operating company 220 may send a registration request 303 to the management server 110. This, and all other communication with the ad hoc operating company, may occur via an app running on a mobile device, such as a smartphone, tablet, or the like. The app may communicate with the management server 110 and / or the locker bank 101 and may provide information to the locker bank via short-range wireless communication techniques and / or by generating computer-readable codes, such as barcodes, QR codes, or the like. General registration data may include user details, such as name, email address, phone number, password, etc. The registration data may also include company-specific information about the ad hoc company, such as the operating company name and details, the operating company's address or other location, city / region, website, etc. Notably, no other registration process may be required to enable the ad hoc operating company 220 to begin using the locker bank network. 6A and 6B show exemplary user interfaces that may be provided on a mobile application for registering an ad hoc operating company into the system. At 305, the management server 110 may confirm the registration of the ad hoc company 220, such as via email confirmation, a message displayed on the mobile application, etc.

[0021] FIG. 3A also illustrates a locker storage box reservation process 391. Such a process may be used, for example, when a user desires to reserve a storage box within a locker bank for future use. At 310, the user may request locker bank storage box availability information for either a particular locker bank (e.g., a bank near the business or the intended customer recipient) or any suitable locker bank, such as if multiple locker banks are available within the business's territory. In response to that request, the management server 110 may obtain the locker bank storage box availability information, which may be stored locally within the management server's database and / or may be obtained by polling the associated locker banks 101 via individual requests 311. For example, it may be preferable for the management server 110 to maintain a continuously updated database of storage box availability, for example, by updating the database each time confirmation regarding successful delivery / use of a storage box is received from each locker, by reclaiming / emptying a storage box upon successful delivery, etc. Examples of configurations and processes for managing such a database of locker storage boxes and their status are provided in U.S. Patent Application Publication No. 2023 / 0316836, filed November 28, 2022, the disclosure of which is incorporated by reference in its entirety.

[0022] Based on the availability data 312, the management server 110 may provide 313 relevant locker storage bin data to the ad hoc user device. The data may indicate locker banks within the business company's area, or within a region near the user's device, or within a previously defined "home" region for that business company that have storage bins available for use by that business company. For example, an app on the ad hoc business company user's device may show a map of locker banks in the relevant region along with an indication of how many and what type or size of storage bins are available in each region. As another example, the user may be provided with a list of storage bins available for use.

[0023] At 314, an ad hoc user can send a request to the management server 110 to reserve a specific locker storage box, a specific type of storage box, and / or a storage box within a specific locker bank. The management server 110 can then change the status of the appropriate storage box to indicate that it has been reserved at 315. The “reserved” status of the storage box can be tracked in a database at the management server 110, by the associated locker bank 101, or a combination thereof. A reserved locker storage box can be maintained for use solely by the reserving ad hoc company 220 for a specific amount of time, for an amount of time based on the overall or company-specific types of locker storage boxes available at or within the locker bank or area, or for any other desired amount of time, until an item is delivered to the storage box. After delivery by the reserved storage box is complete, the storage box can be returned to an “available” state or an equivalent state to make it available again for use within the locker bank. In some embodiments, if a predetermined amount of time passes without a package being collected, the sender of the package can be notified that the package has not been collected by the recipient and should be collected by the sender to allow the locker storage box to be reused. The storage box may remain in a "reserved" or "in use" state until the sender collects the package. In some embodiments, such a collection may also be indistinguishable from a collection by the recipient, thus resulting in the locker storage box being returned to an "available" state, as if the package had been collected by the intended recipient.

[0024] The reservation process 391 may be performed in connection with a specific delivery of goods with a reserved storage box. For example, as described with respect to processes 393 and 394 below, a comparable reservation process may be performed when a user generates a shipment or other delivery. The reservation process 391 may also be performed by a user in anticipation of a need for a storage box before a specific shipment or delivery is prepared. In that case, the interface of the ad hoc user's device may provide an option to link the newly generated shipment or delivery with an existing reservation and use the reserved storage box for the delivery. In some embodiments, the reservation may be performed through or equivalent to advance shipment preparation. That is, the reservation and preparation of a shipment may not be performed through separate processes; rather, a single shipping process may be used, which results in the "reservation" of a storage box for the prepared shipment.

[0025] At times, the ad hoc operating company 220 may desire to use a carrier to deliver packages to customers that will be picked up from the operating company and delivered to a locker bank. In this case, the label creation process 392 may be used to generate a shipping label for use by the carrier when delivering the package. At 320, a shipment may be prepared by the ad hoc operating company 220. The shipment preparation process may follow the process described in FIGS. 3B-3C, or the shipment preparation process may follow a process prescribed by the carrier 114. Upon appropriate request or notification of shipment, at 321, the carrier 114 may generate a shipping label and provide it to the ad hoc company 220 or, for example, to the recipient 107 if a return is being initiated by the operating company 220.

[0026] For example, if an ad hoc business instructs a customer to return a purchased item through a locker bank, a process similar to label creation process 392 may be used. In this case, the business can send the customer the label generated in 321, or the business can instruct the customer to generate the label itself, for example, using payment information provided by the business. The label may be provided via the ad hoc business user's mobile device, typically through an app provided by the associated carrier that may be installed on the device simultaneously with an app capable of communicating with a management server as disclosed herein. That is, the user's device may include a separate app, or may be used separately from the ad hoc locker bank process disclosed herein, for communicating with the management server that controls the locker bank as disclosed herein and for communicating with one or more carriers to generate shipping labels that may be used in connection with the embodiments disclosed herein. More generally, whenever a carrier is used by the ad hoc business to make a delivery of goods to or from the business, locker bank, or customer, a shipping label may be created through a process similar to that described herein or using any conventional label creation process and interface available from the carrier.

[0027] FIG. 3B shows an example delivery process 393 in which the ad hoc company 220 provides a shipment to a carrier for delivery to a recipient 107 via the locker bank 101. At 330, the ad hoc company can initiate a shipment, for example, by notifying the carrier, which may then prepare the shipment and notify the locker bank system about the shipment via the management server 110. This may be done, for example, via a user interface of a mobile application in which a user at the ad hoc company 220 indicates that a new shipment is needed. The shipment preparation interface may be provided within the same mobile application as in embodiments that do not involve a carrier, or the shipment preparation interface may be provided within a separate mobile application, such as one provided by the carrier. An example of a suitable interface is shown in FIG. 6B. As part of preparing the shipment at 330, the ad hoc company 220 may have previously created a shipping label with the carrier 114, such as via process 392 shown in FIG. 3A. In that case, a tracking number, label number, etc. may be provided to the management server 110 via the mobile application. The tracking number can then be provided to the locker bank 101. When the carrier 114 later delivers the package at 333, the locker bank 101 can scan the shipping label to read the tracking number, thereby verifying that the package being delivered matches the shipment prepared at 330.

[0028] At 330, the management server 110 may reserve a storage box in a preferred locker bank. The particular locker bank to be used may be chosen by the company 220 when the shipment is prepared at 330, or the particular locker bank may be assigned by the management server 110. For example, the management server 110 may select a locker bank within the region of the ad hoc company 220, or the management server 110 may select a bank 101 from a set of banks previously selected by the ad hoc company 220 as an acceptable delivery point, and / or the management server 110 may select a preferred locker bank in coordination with the logistics system of the carrier 114. If a locker bank 101 is not selected by the ad hoc company 220, the management server 110 may inform the user of the location of the locker bank 101 to be used. At 331, the management server 110 may instruct the selected locker bank 101 to reserve a locker storage box for the goods to be delivered.

[0029] At 332, the carrier 114 may receive the item for delivery from the ad hoc company 220. For example, the item can be deposited in a shipping kiosk, picked up by the carrier 114, etc. The carrier 114 then delivers the item to the locker bank 101 at 333. To deliver the item, the carrier 114 can provide a tracking number to the locker 101, such as by scanning a barcode, QR code, etc., at which point the locker 101 can retrieve information about the item and open the appropriate storage box to receive the item, such as the storage box reserved at 331.

[0030] The locker bank 101 may confirm 334 the delivery to the management server 110 and / or the ad hoc company 220, or the management server 110 may confirm the delivery to the ad hoc company 220. For example, the ad hoc company 220 may receive a notification on the mobile application used to initiate the shipment at 330 indicating that the item has been successfully delivered to and received by the locker bank 101.

[0031] The locker bank 101 or the management server 110 may send a notification to the recipient 107 at 335, for example, via email, text message, etc. The mode of communication used to notify the recipient 107 may be selected by the ad hoc company 220, for example, during the process of preparing the shipment at 330 or via a stored customer profile maintained for the recipient 107 by the ad hoc company 220. The notification 335 may include a computer readable code, such as a barcode, QR code, and / or a collection code that the recipient 107 can enter into a user interface of the locker bank 101, etc. At 336, the recipient 107 may collect the item from the locker bank 101 by presenting the computer readable code via a scanner, user interface, etc.

[0032] Once the item is collected, the management server 110 may confirm receipt to the carrier 114, the management server 110, and / or the ad hoc company 220, as shown, at 337, 338, 339. Confirmation may be provided to the carrier via an electronic message, such as through an API, and to the ad hoc device user via email, text message, or notification within a mobile application on the user's device.

[0033] A process similar to the shipping process 393 may be used when a carrier is involved in other steps of delivery or other shipment, such as when the recipient 107 wishes to return an item to the retailer ad hoc company 220. For example, the recipient 107 may receive a shipping label from the ad hoc company 220 and use it to ship the returned item via the carrier 114, which may deliver the item to the locker bank 101 for collection by the ad hoc company 220.

[0034] FIG. 3C illustrates an example delivery process 394 in which a business company 220 delivers goods directly to a recipient 107 via a locker bank without using a carrier. At 350, 351, a user of the ad hoc company 220 may prepare a shipment as previously described with respect to 330, 331 in FIG. 3B. Because the carrier 114 is not involved in this case, the ad hoc company 220 may provide an internal reference or tracking number for the shipment, such as via the mobile application interface shown in FIG. 6B, instead of a carrier tracking number. For example, the company 220 may provide an order number, a return authorization number, etc., depending on the context in which the goods are provided to the recipient 107. As described in further detail herein, the specific operation of the locker bank 101 with respect to any shipment prepared by the ad hoc company 220 may be specified in an ad hoc company profile generated and stored by the locker bank system, such as in the admin server 110.

[0035] At 353, the ad hoc enterprise 220 may deliver the goods to the locker bank. For example, the user may enter a shipping number or scan a computer-readable code generated by the management server 110 at the locker bank 101, at which point the locker bank 101 may open the appropriate locker storage box to receive the goods.

[0036] After the goods are delivered, the management server 110 may send a notification to the recipient 107 at 355 indicating that the goods are available for pickup by the recipient 107. The notification may include a computer-readable code such as a barcode, a QR code, a collection code, or other information that the recipient can use to collect the goods at 356. For example, the recipient 107 may present the QR code from the notification 355 to a scanner in the locker bank 101, and in response, the locker bank 101 may open the locker storage box where the goods were stored to allow collection by the recipient 107. The locker bank 101 may have previously received that code from the management server 110 and may have received other identifying information from the ad hoc company 220 (such as if additional security features are indicated) that may also be presented to the locker bank 101 for verification based on the data received from the management server 110.

[0037] At 358, 359, the locker bank 101 and / or the management server 110 may confirm receipt of the item, as shown.

[0038] 3D shows an example delivery process 395 in which goods are sent from a customer to an ad hoc company, such as for a product return. At 361, the customer 107 may send an initial message to the ad hoc company 220, such as to request a return authorization or the like. The ad hoc company 220 may respond at 362 with a confirmation and further instructions, for example, to inform the customer 107 to expect further communication with a return code.

[0039] The ad hoc enterprise user may prepare the shipment at 363, 364 as previously disclosed.

[0040] At 365, the management server 110 may send a notification to the customer 107 that includes a return code or similar code that the customer 107 can use to send the item to the ad hoc company via the locker bank 101. As previously disclosed, a particular locker bank may be selected by the ad hoc company 220 when the shipment is prepared at 363 or at the ad hoc company's 220 earlier setup within the locker bank system. Alternatively, the ad hoc company 220 and / or the locker bank system, via the management server 110, may provide a set of locker banks from which the customer 107 can select.

[0041] In some embodiments, the management server 110 may send the return code to the ad hoc company 220 at 365-1, for example, by providing the return code via a mobile application. In this embodiment, the ad hoc company 220 may provide the return code to the customer 107 at 365-2, which may be sent as a single communication with the initial confirmation 362. The return code provided to the customer 107 at 365-1 or 365-2 may be, for example, a computer readable code such as a barcode, a QR code, or a code that the customer 107 may provide to the locker bank 101 via any other suitable user interface, such as a keyboard, touchscreen, etc.

[0042] At 366, the customer 107 may provide the item to the locker bank 101. For example, the customer 107 may scan a barcode, QR code, etc. at the locker bank 101 or enter the return code received at 365-1, 365-2 via another user interface. In response, the locker bank 101 may open a suitable locker storage box, such as the storage box reserved for this purpose at 364. Once the customer 107 deposits the item in the storage box and closes the door, the locker bank 101 and / or the management server 110 may notify the ad hoc company 220 at 367, 368, respectively, that the item has been received and is available for pickup by the ad hoc company 220. The item may then be retrieved at 369 via a similar process or by the process shown in FIG. 3E. For example, an ad-hoc corporate user may log into Locker Bank 101 by providing their usual credentials, such as a login / password combination, and / or by scanning a computer-readable code, such as a barcode or QR code, generated by a mobile application used to interface with the Locker Bank system.

[0043] 3E illustrates an exemplary item recovery process 396 performed by a recipient of the items. The process illustrated in FIG. 3E may be used by any entity or individual recovering items from a locker bank according to embodiments disclosed herein. For example, the recipient 107 may be a customer, partner, or affiliate of the ad hoc company 220, or the recipient 107 may be the ad hoc company 220 itself, such as when a customer is returning an item. In some cases, the sender and recipient may both be associated with the ad hoc company, such as when a business company with multiple locations uses the locker bank 101 to transfer items between different business company locations.

[0044] At 341, the recipient 107 provides a collection code to the locker bank 101. The collection code may be a return code, a shipping code, or any other human- and / or computer-readable code provided to the recipient 107 in association with items stored in the locker bank 101, as previously disclosed. The collection code may be generated in a prior process, such as by the carrier 114, the ad hoc company 220, or the locker system via the management server 110. In some embodiments, the collection code is generated within a mobile application used by the ad hoc company 220 to coordinate the shipment with the locker bank system via the management server 110.

[0045] The locker bank 101 may verify and / or confirm the authenticity of the recovery code at 349. For example, the locker bank 101 may communicate with the management server 110 or consult internal data to determine whether a recovery code has been revoked since it was provided to the recipient 107. This process allows ad hoc companies to revoke recovery codes individually or in bulk, for example, if the company 220 is concerned about theft, has issued a recovery code in error, or has otherwise issued a recovery code in error. Recovery codes may also be configured by the ad hoc company 220 to expire within a certain period of time, either as a general priority or individually at the time the recovery code is generated or the associated shipment is made. In some embodiments, the lifespan of a recovery code may be set by configuration options determined when the ad hoc company joins the locker bank system, as described in further detail herein. As previously disclosed, other configuration options may affect the delivery and recovery of items from the locker bank 101 by changing the behavior of the locker bank 101. For example, configuration options may require two-factor or multi-factor authentication of the recipient 107, the locker bank 101 may require or prohibit the use of an "automatic" code that would normally be scanned by the locker bank 101 to allow access to stored items, the locker bank 101 may require a signature of the recipient 107, such as on a touch screen or equivalent, etc.

[0046] After verifying that the collection code is valid and authentic at 349, the locker bank may deliver the items stored in the storage box to the recipient at 342. For example, the locker bank 101 may automatically open the associated locker storage box to allow access to the stored items.

[0047] The locker bank 101 and / or the control server 110 may confirm receipt of the item to the control server 110 and / or the adhoc company at 343, 345, respectively.

[0048] In this process and other processes disclosed herein, the locker bank 101 and management server 110 may confirm and update the availability of the storage box in the locker bank 101 at 344. For example, once delivery is confirmed at 343, the management server 110 and / or locker bank 101 may update their databases to indicate that the storage box is available for use.

[0049] As described in further detail herein, the specific behavior of the locker bank 101 with respect to any shipment prepared by the ad hoc company 220 may be specified in an ad hoc company profile generated and stored by the locker bank system, such as in the management server 110. This behavior may vary depending on the type of shipment, such as which of the processes in FIGS. 3A-3E are used. For example, the locker 101 and management server 110 may be configured to hold the items for a configured period of time after receiving them for delivery to the recipient 107 based on the business type identified for the ad hoc company 220. As another example, the ad hoc company 220 may indicate via a mobile application interface or other interface that a particular item is personal or sensitive, requiring enhanced security, or the ad hoc business company may generally be a business configured for secure delivery, in which case the locker bank 101 may be configured to use two-factor authentication or other security enhancements before providing the items to the recipient 107.

[0050] 4 illustrates an exemplary process for creating a profile for an ad-hoc company within the Locker Bank system to onboard the company to the system, as disclosed herein. As previously disclosed, the registration process for ad-hoc companies does not require individual specific customization of Locker Bank behavior for each operating company. Rather, the configuration may be performed automatically by the management server based on industry or other information about the operating company obtained by the management server.

[0051] At 405, the Locker Bank system may receive a request from a new ad-hoc business to gain access to the Locker Bank network. For example, the business may download and install a mobile application provided by the Locker Bank system, such as via a third-party app store or equivalent, and request that a new account be created. The registration request may be the same as request 303 described with respect to FIG. 3A and may include, for example, the information in the registration process screens shown in FIGS. 6A-6B. One item of information provided about the ad-hoc business may be the industry or business classification. The industry or business classification may be broad, such as "retail" or "food delivery," or they may be more specific, such as "pharmacy," "shoe store," or "women's clothing or accessories."

[0052] At 410, the locker bank system may determine whether the identified business type is listed in an internal database. For example, as previously disclosed, the management server may include or be in communication with a lookup table or other database structure that includes business types recognized by the system. In some embodiments, the business types in the database may be provided as a list for the user to select from. In other embodiments, the registration interface may allow the user to enter a free-form entry, after which a text match may be performed to determine whether the business type exists in the database. If the business type is found, or in embodiments where the user can only select from available business types, the process continues at 415. If the business type is not found at 435, the system may query the user to confirm or identify a “closest” business type at 440. The closest business company may be found via various text matching techniques at 450, or the closest business company may be found through a similarity lookup table, such as the example shown in FIG. 5. In some embodiments, the “closest” business company may be identified by machine learning (ML) or other artificial intelligence (AI) systems that are trained against a pre-assignment of a known correct business type. Similarly, the specific configuration options disclosed herein may be selected by an AI system that has been trained on known correct business company profiles and settings for various industries and settings.

[0053] If an updated industry vertical is found at 440, the process continues at 415. If not, the system may identify the closest "best match" industry vertical at 450. This industry vertical may be found via text matching, lookup tables, or using various forms of automated machine learning and similar techniques. For example, as ad hoc business companies are added to the system and utilize the locker network, a machine learning system may be trained to determine industry verticals that have similar usage patterns, configuration needs, etc. The system may use this training to identify or suggest the "best match" industry vertical.

[0054] At 415, the system may search for settings for the locker bank in the system based on the business type identified through the previous step. For example, if a registered ad hoc business is identified as a florist, the settings for the “florist” business type may be loaded and associated with a new ad hoc business record created in the locker bank system for the new ad hoc business. As another example, a Japanese ornaments store may prefer that its customers enter their signature on a screen when retrieving items that are assumed to be expensive from a locker bank. Therefore, a “decorations store” profile may be configured to allow consumers to enter their signature on a screen, while some other types of business, such as food delivery businesses that are assumed to be low-priced, would not require a signature. This setting may be selected and configured based on region. Continuing with the previous example, if ornaments stores in other regions do not normally require a signature, a signature requirement may be implemented in the Japanese “decorations store” profile but not in other regions. More generally, a signature requirement may be included in a business profile targeted at business companies that send and receive expensive items, highly fragile or important items, items that affect privacy, etc.

[0055] Regardless of the specific settings included in the industry profile, the locker bank will then operate using those configuration options whenever a shipment / delivery is prepared by the ad hoc operating company. Each industry defined within the locker bank system may include settings for some or all of the configuration options available to locker banks in the system. For example, each industry may be associated with a company profile that includes values ​​for some or all of the configuration options shown in Tables 1-4 below. Alternatively, each company profile may specify values ​​for only some configuration options and allow other configuration options to be unspecified or set to system-wide defaults, in which case locker banks in the system will behave according to default predefined behavior when used by the ad hoc network. Each entity profile may be stored in a database maintained by the management server. When an ad hoc company utilizes a locker bank, such as through processes such as those shown in Figures 3A-3E, the company profile may be referenced by the management server and / or locker banks involved in the process, or the profile may be used to define the behavior of the locker bank for those processes, as the case may be.

[0056] At 420, the system may present the selected configuration options for the ad hoc business company for review and confirmation by the user. The user may have the option to change individual settings at this point. Alternatively or additionally, the user may have the option to select a different business line, which may have different configuration options. In some cases, the system may not indicate the selected business line and / or settings to the user and may proceed directly to step 425. Similarly, in some embodiments, the user may not be informed that different business lines have different locker bank settings, and the system may proceed to step 425 without further user interaction.

[0057] At 425, the relevant settings, or a profile referencing all relevant settings, may be associated with the ad hoc operating company's record in the locker bank system. At 455, when a shipment is later prepared using, for example, the process described in Figures 3A-3E, the settings associated with the ad hoc operating company may be used to control the behavior and operation of the locker bank for the shipment prepared by the ad hoc company.

[0058] FIG. 5 illustrates a simplified example of a lookup table that may be used to identify appropriate settings for a particular business company. In this example, the locker bank system has broad or high-level classifications for business companies, including “apparel” and “food.” Each of these classifications is associated with various configuration options, as disclosed herein. It is anticipated that users creating new ad-hoc business accounts may not provide business types that precisely match the broad classifications; therefore, these business types are mapped to potential equivalent user responses. In this example, “clothing stores,” “shoe stores,” “men’s clothing,” and “women’s clothing” would all be mapped to the “apparel” type and use the same locker bank configuration. Similarly, “fresh fruit stores,” “fruit basket stores,” and “ice cream stores” would all be considered “food” and configured accordingly. FIG. 5 illustrates, for illustrative purposes, a simplified example of a lookup table, as disclosed herein. More generally, any number of anticipated user inputs may be mapped to any number of predefined classifications. As previously disclosed, text matching techniques, heuristic matching techniques, regular expression matching techniques, and other variable matching techniques, as well as any other suitable techniques, can be used to map the business type provided by the user to any number of predefined classifications available in the system. The predefined classifications and associated settings may be configured by an entity managing the locker bank system. In some embodiments, the predefined classifications and associated business company profiles and settings may be updated by the locker bank system from time to time, for example, to implement new settings, to adjust how particular business companies operate within the locker bank network, etc. For example, it may be discovered that some business companies want to increase the security level for picking up items from a locker bank. In that case, the profiles for those business companies may be updated to require two-factor authentication or other security features when a recipient retrieves items from a locker bank, which may not be required for other business company profiles.

[0059] As previously disclosed, when an ad hoc company joins the locker bank system, a profile may be created for the company that includes predefined locker bank settings appropriate for the industry type identified for that company. This profile may be selected from a predefined list of general profiles, or the profile may be created as previously disclosed. In some embodiments, the ad hoc company may be selected from a predefined set of profiles. Table 1 shows examples of setting options that may be automatically configured in this manner. Other settings may be used, and the examples provided here may be used in any logical combination for individual company profiles. Unless otherwise indicated, each option may be enabled or required by the system. For example, "login via username / password" may be selected as an enabled login method for the locker bank (such as when a user deposits or retrieves an item), or "login via username / password" may be selected as a required login method for the locker bank. Some settings may be assigned integer or other numeric values, such as a maximum number of failed login attempts allowed before preventing further access, preventing further attempts before a timeout period, etc.

[0060] [Table 1]

[0061] In some embodiments, ad hoc users may be provided with a "portal" view to enable access to existing package information, such as packages delivered to the locker bank but not yet picked up, recent shipments (delivered but not yet picked up), shipping history, payment history, etc. In some embodiments, the locker bank system may enable integration with other existing logistics systems, communication systems, etc. The ad hoc company profile may include settings that control integration options, including whether integrations are made available based on the entity's industry. Other types of settings that may be included within the ad hoc company profile stored by the locker bank system may include, for example, hardware-specific settings (such as when the locker bank system uses multiple types or versions of locker banks with different requirements or configuration options).

[0062] In some embodiments, the management server 110 disclosed herein may reserve portions of one or more locker banks for use by ad hoc companies, specific subscribing companies, or any combination thereof. For example, the management server may reserve at least a minimum number or rate of storage boxes in a given area for use by ad hoc companies to ensure that there is always a minimum number or rate of locker bank storage boxes available for use by ad hoc customers. Such "internal" reservations may be indicated to the user, or such reservations may be made "silently," i.e., without indicating to the user that the reserved storage boxes are reserved for any particular type of use.

[0063] Notably, according to the embodiments disclosed herein, no further setup of the locker bank system, the ad hoc company's logistics system or other information technology infrastructure, or any other systems of the ad hoc company needs to be updated or configured before the company can utilize the locker bank system. After the initial registration process is complete, the ad hoc company has access to the locker bank system and can begin sending and receiving deliveries through the locker bank. Such a feature is particularly desirable as locker bank systems continue to become more automated and less dependent on human intervention. The embodiments disclosed herein provide a valuable improvement over traditional locker bank systems, even relatively automatic locker bank systems, by removing technical barriers that, in some cases, would be insurmountable for smaller, less sophisticated business companies. The embodiments disclosed herein also enable more efficient use of already computerized locker banks by providing greater access to the locker bank by a larger and wider range of end consumers.

[0064] The embodiments disclosed herein demonstrate improvements and enhancements to computerized, automated package delivery and receiving systems, including automated package locker banks and open locker systems. Such systems rely on computerized communication, processing, and storage systems to achieve the package delivery efficiency and capacity required by modern shipping and receiving systems. Therefore, the processes and systems disclosed herein cannot reasonably be implemented by humans or with the human mind, due to the need to interface with existing computerized shipping systems, mobile devices and applications, post office automated routing systems and requirements, and the like. For example, the processes described herein cannot be implemented without the dedicated devices, computer processors, and software disclosed for these processes. Furthermore, the automated locker bank systems disclosed herein are designed to prevent arbitrary user access to information stored therein, including the occupancy status of each locker, recipient information stored in a local database at the locker bank, and the like. Therefore, because the associated systems do not provide human-readable information and / or human-accessible configuration elements other than those disclosed herein, the automated techniques and systems disclosed herein are necessary to accomplish package delivery to automated package lockers as disclosed.

[0065] More generally, various embodiments may be included or embodied in the form of computer-implemented processes and apparatuses for practicing those processes. The embodiments may also be embodied in the form of a computer program product having computer program code, including instructions embodied in a non-transitory and / or tangible medium, such as a floppy diskette, a CD-ROM, a hard drive, a USB (Universal Serial Bus) drive, or any other machine-readable storage medium, such that when the computer program code is loaded into and executed by a computer, the computer becomes an apparatus for practicing embodiments of the disclosed subject matter. The embodiments may also be embodied in the form of computer program code, whether stored in a storage medium, loaded into and / or executed by a computer, or transmitted over some transmission medium, such as over electrical wiring or cable, over some transmission medium, through fiber optics, or via electromagnetic radiation, such that when the computer program code is loaded into and executed by a computer, the computer becomes an apparatus for practicing embodiments of the disclosed subject matter. When implemented on a general-purpose microprocessor, the computer program code segments configure the microprocessor to create specific logic circuits.

[0066] In some settings, computer-readable instructions for implementing the techniques disclosed herein may be stored on a computer-readable storage medium and implemented by a general-purpose processor, the execution of which may transform a general-purpose processor or a device including a general-purpose processor into a special-purpose device configured to implement or perform those instructions. Embodiments may be implemented using hardware that may include a processor, such as a general-purpose microprocessor and / or an application-specific integrated circuit (ASIC), that embodies all or part of the techniques in hardware and / or firmware in accordance with embodiments of the disclosed subject matter. The processor may be coupled to memory, such as RAM, ROM, flash memory, a hard disk, or any other device capable of storing electronic information. The memory may store instructions adapted to be executed by the processor to perform the techniques in accordance with embodiments of the disclosed subject matter.

[0067] The foregoing description has been set forth with reference to specific embodiments for purposes of explanation. However, the exemplary discussion above is not intended to be exhaustive or to limit the embodiments of the disclosed subject matter to the precise forms disclosed. Many modifications and variations are possible in light of the above teachings. These embodiments were chosen and described to explain the principles of embodiments of the disclosed subject matter and their practical application, so as to enable those skilled in the art to utilize these embodiments and various modifications that may be suited to the particular use contemplated.

[0068] While the flowcharts in the figures show a particular order of operations performed by some implementations, such order is exemplary and not limiting. Other implementations and various embodiments may perform these operations in a different order, combine some operations, perform some operations in parallel, overlap the performance of some operations so that some operations are partially parallel, etc.

[0069] The above description includes some exemplary implementations. However, those skilled in the art will recognize that the invention disclosed herein is not limited to the described implementations, but can be practiced with modification and alteration within the spirit and scope of the appended claims. The description is therefore illustrative rather than limiting. [Explanation of symbols]

[0070] 101 Electronic Locker Bank, Locker Bank 102 Electronic Locker Bank, Locker Bank 105 Telecommunications networks, long-distance communication networks 107 Mobile Device, Local Mobile Device, Local Device, Recipient, Customer 110 Locker bank management server, management server 114 Shipping companies 201 Member companies 220 ad hoc companies, companies, business companies, ad hoc business companies 303 Registration Request, Request 311 request 312 Availability Data 334 Baggage Availability 355 Notifications 362 Initial Confirmation 390 Registration Process 391 Locker Storage Box Reservation Process, Reservation Process 392 label creation process, shipping label creation process, process 393 Carrier Shipment Preparation and Delivery, Shipment Preparation Process, Process, Delivery Process 394 Direct delivery of goods, process, delivery process 395 Direct product returns and delivery process 396 Product Recovery Process, Product Recovery Process

Claims

1. 1. A method of operating a computerized locker bank system including a plurality of locker banks, the plurality of locker banks including a plurality of locker storage boxes, the method comprising: receiving a request to join from a device associated with a business that is not subscribed to the locker bank system; receiving identification information from the device regarding the business, the identification information including an indication of the business type; automatically selecting, by the computerized locker bank system, a setting profile from among a plurality of setting profiles in response to receiving the subscription request and the identification information and based on the business type indicated by the identification information, each setting profile defining a plurality of behaviors of the locker bank; creating and storing a record assigning said configuration profile to said business; following the step of creating and storing the record, and in response to one or more delivery requests initiated by the business, operating one or more of the plurality of locker banks in accordance with the plurality of behaviors in the configuration profile assigned to the business; A method comprising:

2. the step of automatically selecting the configuration profile further comprising: determining that the business type in the identification information does not exist in a business type database; responsive to the determination that the business type is not present in the business type database, selecting a business type from the business type database based on the business type in the identification information; The method of claim 1 further comprising:

3. The method of claim 2 , wherein the business types selected from the business type database are selected based on a textual or heuristic match of the business types in the identification information to the business types selected from the business type database.

4. 3. The method of claim 2, wherein the industries selected from the industry database are selected based on the output of a machine learning system trained on a plurality of ad hoc companies that previously joined the locker bank system.

5. receiving, from a user associated with the business, instructions for goods to be delivered via a locker bank of the plurality of locker banks in the locker bank network; The method of claim 1 further comprising:

6. The goods to be delivered are received from a customer of the business, and the method comprises: generating a shipping code; sending the shipping code to the customer of the business; In response to receiving the delivery code from the customer's mobile device, sending a notification to the business that the item has been received in a storage bin of the locker bank.

6. The method of claim 5, further comprising:

7. The method of claim 6, wherein the notification is also sent to the business upon receipt of the item in the storage box of the locker bank.

8. the goods are delivered from the business to a customer of the business, and the method comprises: receiving identification information from the business at a locker bank of the plurality of locker banks; opening a storage box of the locker bank; sending a notification to the customer that the item has been delivered to the locker bank in response to the storage box being closed, in response to confirmation by the business that the item has been placed in the storage box, or both; 6. The method of claim 5, further comprising:

9. 2. The method of claim 1, wherein the plurality of behaviors of the locker bank in the configuration profile are selected based on previous behaviors of companies subscribing to the locker bank system that have the same or similar business type as the business type listed in the identification information for the company.

10. 1. A luggage locker bank system, comprising: a management server system including one or more management servers; Multiple locker banks and each locker bank including a plurality of locker storage boxes available for receiving and storing goods; The management server system receiving a request to join from a device associated with a business that is not a subscriber to the luggage locker bank system; receiving identification information from the device regarding the business, the identification information including an indication of a type of business of the business; automatically selecting, by a computerized locker bank system in response to receiving the subscription request and the identification information and based on the business type indicated by the identification information, a configuration profile from among a plurality of configuration profiles, each configuration profile defining a plurality of behaviors of the locker bank; creating and storing a record that assigns said configuration profile to said business; subsequent to creating and storing said record, and in response to one or more delivery requests initiated by said business, operating one or more of said plurality of locker banks in accordance with said plurality of behaviors in said configuration profile assigned to said business. and configured to operate the locker bank in association with ad hoc companies subscribing to the locker bank system by Luggage locker bank system.

11. automatically selecting the configuration profile; determining that the business type in the identification information does not exist in a business type database; responsive to said determining that said business type is not present in said business type database, selecting a business type from said business type database based on said business type in said identification information; 11. The locker bank system of claim 10, further comprising:

12. 12. The locker bank system of claim 11, wherein the business type selected from the business type database is selected based on a text match or a heuristic match of the business type in the identification information to the business type selected from the business type database.

13. 12. The locker bank system of claim 11, wherein the business types selected from the business type database are selected based on the output of a machine learning system trained on a plurality of ad hoc companies that previously joined the locker bank system.

14. The management server receiving, from a user associated with the business, instructions for merchandise to be delivered via a locker bank of the plurality of locker banks in the locker bank network; 11. The locker bank system of claim 10, further configured as follows:

15. The product to be delivered is received from a customer of the company, and the management server Generate a shipping code, sending the shipping code to the customer of the business; In response to receiving the shipping code from the customer's mobile device, sending a notification to the business that the item has been received in a storage box at the locker bank.

15. The locker bank system of claim 14, further configured as follows:

16. 16. The locker bank system of claim 15, wherein the notification is also sent to the business upon receipt of the item in the storage box of the locker bank.

17. The product is delivered from the company to a customer of the company, and a management server receiving identification information from the business at a locker bank of the plurality of locker banks; opening a storage box of the locker bank; sending a notification to the customer that the item has been delivered to the locker bank upon the closing of the storage box, upon confirmation by the business that the item has been placed in the storage box, or both; 15. The locker bank system of claim 14, further configured to operate in conjunction with said locker bank of said plurality of locker banks to:

18. 11. The locker bank system of claim 10, wherein the plurality of behaviors of the locker bank in the setting profile are selected based on previous behaviors of companies that have joined the locker bank system and have the same or similar business type as the business type listed in the identification information for the company.

Images