The present disclosure relates to systems and methods that facilitate delivery of products to users.
Customers who purchase products at online merchants need to select a method of delivery for the products. Typically, the products are shipped to the customer using a parcel delivery service or a mail service. Some parcel delivery services and mail services provide an estimated delivery date to inform the customer of when they can expect to receive the shipped products. However, the delivery dates are generally estimates and do not provide a specific delivery time (or delivery time window). Thus, customers are not provided with a definite date and time (or time window) for delivery of their products. Although some parcel delivery services and mail services offer “morning delivery,” they charge an increased fee for this service.
Many customers do not want packages left at their door if they are not home. For example, residents of apartments or condominiums may not want packages left at their door or at the outside door of the apartment complex. Since these customers do not have a specific delivery time for their products, they have difficulty receiving shipments of products purchased from online merchants.
Non-limiting and non-exhaustive embodiments of the present disclosure are described with reference to the following figures, wherein like reference numerals refer to like parts throughout the various figures unless otherwise specified.
In the following description, reference is made to the accompanying drawings that form a part thereof, and in which is shown by way of illustration specific exemplary embodiments in which the disclosure may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the concepts disclosed herein, and it is to be understood that modifications to the various disclosed embodiments may be made, and other embodiments may be utilized, without departing from the scope of the present disclosure. The following detailed description is, therefore, not to be taken in a limiting sense.
Reference throughout this specification to “one embodiment,” “an embodiment,” “one example,” or “an example” means that a particular feature, structure, or characteristic described in connection with the embodiment or example is included in at least one embodiment of the present disclosure. Thus, appearances of the phrases “in one embodiment,” “in an embodiment,” “one example,” or “an example” in various places throughout this specification are not necessarily all referring to the same embodiment or example. Furthermore, the particular features, structures, databases, or characteristics may be combined in any suitable combinations and/or sub-combinations in one or more embodiments or examples. In addition, it should be appreciated that the figures provided herewith are for explanation purposes to persons ordinarily skilled in the art and that the drawings are not necessarily drawn to scale.
Embodiments in accordance with the present disclosure may be embodied as an apparatus, method, or computer program product. Accordingly, the present disclosure may take the form of an entirely hardware-comprised embodiment, an entirely software-comprised embodiment (including firmware, resident software, micro-code, etc.), or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module,” or “system.” Furthermore, embodiments of the present disclosure may take the form of a computer program product embodied in any tangible medium of expression having computer-usable program code embodied in the medium.
Any combination of one or more computer-usable or computer-readable media may be utilized. For example, a computer-readable medium may include one or more of a portable computer diskette, a hard disk, a random access memory (RAM) device, a read-only memory (ROM) device, an erasable programmable read-only memory (EPROM or Flash memory) device, a portable compact disc read-only memory (CDROM), an optical storage device, and a magnetic storage device. Computer program code for carrying out operations of the present disclosure may be written in any combination of one or more programming languages. Such code may be compiled from source code to computer-readable assembly language or machine code suitable for the device or computer on which the code will be executed.
Embodiments may also be implemented in cloud computing environments. In this description and the following claims, “cloud computing” may be defined as a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned via virtualization and released with minimal management effort or service provider interaction and then scaled accordingly. A cloud model can be composed of various characteristics (e.g., on-demand self-service, broad network access, resource pooling, rapid elasticity, and measured service), service models (e.g., Software as a Service (“SaaS”), Platform as a Service (“PaaS”), and Infrastructure as a Service (“IaaS”)), and deployment models (e.g., private cloud, community cloud, public cloud, and hybrid cloud).
The flow diagrams and block diagrams in the attached figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flow diagrams or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It will also be noted that each block of the block diagrams and/or flow diagrams, and combinations of blocks in the block diagrams and/or flow diagrams, may be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions. These computer program instructions may also be stored in a computer-readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instruction means which implement the function/act specified in the flow diagram and/or block diagram block or blocks.
The systems and methods described herein manage the delivery of products purchased from an online merchant to a local merchant location. Additionally, the described systems and methods manage scheduling of the delivery of the products from the local merchant location to a customer (also referred to herein as a “user”). In some embodiments, the products received by the local merchant are delivered to the user along with a grocery order from the local merchant. Although particular embodiments discussed herein refer to delivery of received products with a grocery order, the described systems and methods are useful in delivering received products with any type of order containing any type of item(s).
An online merchant 106 and a parcel delivery service 108 are also coupled to data communication network 104. In some embodiments, online merchant 106 and a parcel delivery service 108 implement one or more computer systems, such as servers, to perform various operations and interact with other devices and systems via data communication network 104. A local merchant 110 is also coupled to data communication network 104. Local merchant 110 uses one or more computer systems, such as servers, to implement a delivery management system 112. Delivery management system 112 manages the receiving of product shipments from online merchant 108 and the delivery of those product shipments to appropriate users. A database 114, coupled to delivery management system 112, stores data used by delivery management system 112, such as user data, product data, delivery data, order data, and the like. Additional details regarding delivery management system 112 are provided herein.
Although one online merchant 106, one parcel delivery service 108, and one local merchant 110 are shown in
Delivery management system 112 also includes a customer management module 208 that manages customer information, customer orders, customer deliveries, and the like. A grocery order manager 210 manages various aspects of a grocery order, such as receiving grocery order contents, determining order volume, determining order weight, and scheduling delivery of a grocery order to a customer. Delivery management system 112 also includes a product tracking module 212, which tracks the location of received product shipments within the local merchant location. For example, when a product shipment is received for a customer from an online merchant, product tracking module 212 associates the product shipment with the customer identity, assigns a temporary storage location for the product shipment, and records that temporary storage location. By recording the temporary storage location, a delivery employee or system can easily locate the product shipment when preparing to deliver the product shipment to the customer.
Delivery management system 112 further includes a delivery time manager 214 that handles the scheduling of deliveries from the local merchant to the customer. These deliveries may include a grocery order as well as a product shipment for the customer that was received from an online merchant. As discussed herein, the scheduling of deliveries considers the volume of the order (both groceries and products from an online merchant), the weight of the order, the time required to deliver the order, available space on delivery vehicles, and the like. A customer communication module 216 interacts with one or more customers regarding grocery orders, products received from online merchants, delivery of orders and products, delivery reminders, and the like.
Method 300 continues as the online merchant instructs a parcel delivery service (or mail delivery service) to deliver the product to the local merchant location at 306. The parcel delivery service then delivers the product to the local merchant location at 308. The local merchant receives the product at 310 and identifies a user associated with the product based on the recipient's name or customer number on the shipping label. Additionally, information about the user can be identified from a customer management system, customer database or other system that manages customers of the local merchant. For example, a customer management system may identify the user's email address, phone number, delivery address, and the like. The local merchant then notifies the user at 312 that the product has been received at the local merchant location. Finally, the user schedules a delivery time for the local merchant to deliver the product to the user at 314. As discussed herein, delivery of the product may be combined with a delivery of groceries or other items from the local merchant.
The local merchant determines a volume, weight, and estimated delivery time for the groceries and the product at 506. For example, the total volume and weight associated with the groceries and the product are calculated based on the known volume and weight of the individual grocery items and the product. The estimated delivery time is determined based on the volume and weight of the items and the delivery location (e.g., stairs or a long walk). For example, if a large product is being delivered up several flights of stairs, the estimated delivery time is extended to accommodate the size of the product and delivery situation. In some embodiments, the volume and weight of the product are determined upon receipt of the product and stored by the delivery management system 112 (
Method 500 continues as the local merchant communicates the available delivery time slots to the user at 512. The user then selects a delivery time slot that is convenient for the user. The local merchant receives the selected delivery time slot from the user at 514. Finally, the local merchant assigns the selected delivery time slot to the user at 516 and schedules the appropriate delivery vehicle to deliver the groceries and the product to the user.
In some embodiments, the local merchant receives an online grocery order from a customer. Upon receipt of the grocery order, the delivery management system 112 determines whether any parcels are awaiting delivery to the customer. If a parcel is identified, the local merchant offers to deliver the parcel to the customer along with the grocery order. If the user accepts the offer, the delivery management system 112 schedules a delivery of both the grocery order and the parcel. If the user declines the offer, the package remains at the local merchant for a future delivery to the customer.
Computing device 600 includes one or more processor(s) 602, one or more memory device(s) 604, one or more interface(s) 606, one or more mass storage device(s) 608, and one or more Input/Output (I/O) device(s) 610, all of which are coupled to a bus 612. Processor(s) 602 include one or more processors or controllers that execute instructions stored in memory device(s) 604 and/or mass storage device(s) 608. Processor(s) 602 may also include various types of computer-readable media, such as cache memory.
Memory device(s) 604 include various computer-readable media, such as volatile memory (e.g., random access memory (RAM)) and/or nonvolatile memory (e.g., read-only memory (ROM)). Memory device(s) 604 may also include rewritable ROM, such as Flash memory.
Mass storage device(s) 608 include various computer readable media, such as magnetic tapes, magnetic disks, optical disks, solid state memory (e.g., Flash memory), and so forth. Various drives may also be included in mass storage device(s) 608 to enable reading from and/or writing to the various computer readable media. Mass storage device(s) 608 include removable media and/or non-removable media.
I/O device(s) 610 include various devices that allow data and/or other information to be input to or retrieved from computing device 600. Example I/O device(s) 610 include cursor control devices, keyboards, keypads, microphones, monitors or other display devices, speakers, printers, network interface cards, modems, lenses, CCDs or other image capture devices, and the like.
Interface(s) 606 include various interfaces that allow computing device 600 to interact with other systems, devices, or computing environments. Example interface(s) 606 include any number of different network interfaces, such as interfaces to local area networks (LANs), wide area networks (WANs), wireless networks, and the Internet.
Bus 612 allows processor(s) 602, memory device(s) 604, interface(s) 606, mass storage device(s) 608, and I/O device(s) 610 to communicate with one another, as well as other devices or components coupled to bus 612. Bus 612 represents one or more of several types of bus structures, such as a system bus, PCI bus, IEEE 1394 bus, USB bus, and so forth.
For purposes of illustration, programs and other executable program components are shown herein as discrete blocks, although it is understood that such programs and components may reside at various times in different storage components of computing device 600, and are executed by processor(s) 602. Alternatively, the systems and procedures described herein can be implemented in hardware, or a combination of hardware, software, and/or firmware. For example, one or more application specific integrated circuits (ASICs) can be programmed to carry out one or more of the systems and procedures described herein.
Although the present disclosure is described in terms of certain preferred embodiments, other embodiments will be apparent to those of ordinary skill in the art, given the benefit of this disclosure, including embodiments that do not provide all of the benefits and features set forth herein, which are also within the scope of this disclosure. It is to be understood that other embodiments may be utilized, without departing from the scope of the present disclosure.