Patent Description:
With the advancement and proliferation of computer technology, online shopping, also known as e-commerce, has become one of the major avenues of commerce. Consumers and businesses are purchasing goods from online vendors more frequently than ever, and the number of transactions and sales revenue are projected to grow year-over-year at a staggering rate. As the scope and volume of e-commerce continue to grow, both the number of different items available online and the average number of purchases made in a given period are also growing exponentially. For example, the number of different items sold by one popular online retailer is said to have reached more than <NUM> million products, and the number of packages shipped per day by the same retailer, <NUM> million.

Each online purchase, by nature, requires a delivery of the purchased goods to its intended recipient. Each online purchase or order typically comprises of one or more goods, wherein the one or more goods can be packaged into one or more packages, each with its own promised delivery date. A typical order may be processed via steps such as: receiving, from a customer, an order for one or more goods; retrieving the one or more goods from an inventory; packaging the one or more goods into one or more packages; and delivering the one or more packages to the intended recipient before the promised delivery date. The promised delivery date may be set by the retailer itself or a shipping courier, or a specific date may be requested by the customer, which then may be assigned as the promised delivery date. An ideal system of order processing would deliver each package to the intended recipient by the promised delivery date without failure.

<CIT> discloses a method of inventory management which involves displaying a plurality of data fields related to shipping a package on a display screen in communication with a computer system; and receiving an identifier for a package from a device in communication with the computer system. In response to the receipt of the identifier, one or more data fields from the plurality of data fields is automatically populated with data for the package; and displayed on the display screen. A shipping label for the package including at least the identifier or the data from the device is then printed using a printer in communication with the computer system.

<CIT> discloses a delivery management system which includes a manifest component configured to aggregate a plurality of items into a manifest, an identifier component configured to identify respective items within the aggregated plurality of items using the manifest, a tracking component configured to calculate a delivery route and track the plurality of items during a plurality of delivery events, and an inspection component configured to require inspection of the respective items at each of the plurality of delivery events. The delivery system can be arranged to ensure quality and manage connections between distributors and manufacturers by incorporating required checks through each step of a delivery (e.g., pick up, freight aggregation, line shipping, local shipping, etc.). Inspections at delivery transitions may be required and include each time a good (e.g., an item) is moved on or off a delivery truck, and transitions between delivery areas within specific location.

Currently existing order processing systems include a varying degree of automation and complexity in implementing the steps described above. With increasing number of different goods and orders, however, aggravated by the fact that the orders need to go through a complex network of subsystems and that some orders have complicating factors such as a partial return, current systems are problematic in that they are incapable of or largely inefficient at tracking individual packages from the moment an order is placed to the moment the order is fulfilled (i.e., every package in the order is delivered to the intended recipient or returned to the inventory). This problem is aggravated by the fact that increasing number of packages and focus on expeditious processing makes the system more prone to human error, such as omitting a package, mislabeling, or mis-sorting. For example, an order comprising of multiple packages with different promised delivery dates may end up with one or more lost or damaged packages mid-way through the system, which the system may not notice until a frustrated customer follows up.

In another example, one of the packages of the order may be delayed at some point in the system and a customer may request a redelivery of the package, in which case the system will need to reorder a new package because the system cannot tell why the existing package is delayed or how long it will need in order to clear the delay. In this case, both the existing delayed package and the new package may get delivered to the customer, incurring an unnecessary expense to the system. Even in some cases where the existing delayed package is correctly routed back to a warehouse, current systems may not be able to distinguish it from a package returned by a customer, requiring the delayed package to go through a full inspection process along with other customer-returned packages when it could have been set aside and restocked with only a minimal inspection as it had not reached a customer and thus was not opened. These scenarios serve to exemplify shortcomings of current systems and many other problems may also be apparent to those of ordinary skill in the art.

Therefore, there is a need for improved methods and systems for tracking orders and packages through the order processing system and proactively identifying and taking necessary actions to reduce the number of lingering orders that have not been delivered yet, all the while minimizing its impact on operating expenses.

One aspect of the present disclosure is directed to a method for automated reshipment scheduling in accordance with claim <NUM>.

A further aspect of the present invention provides a computer-implemented system for automated reshipment scheduling in accordance with claim <NUM>.

Other systems, methods, and computer-readable media are also discussed herein.

The following detailed description refers to the accompanying drawings. Wherever possible, the same reference numbers are used in the drawings and the following description to refer to the same or similar parts. While several illustrative embodiments are described herein, modifications, adaptations and other implementations are possible. For example, substitutions, additions, or modifications may be made to the components and steps illustrated in the drawings, and the illustrative methods described herein may be modified by substituting, reordering, removing, or adding steps to the disclosed methods. Accordingly, the following detailed description is not limited to the disclosed embodiments and examples. Instead, the proper scope of the invention is defined by the appended claims.

Embodiments of the present disclosure are directed to systems and methods configured for automatic parcel tracking and processing.

Further, the disclosed delivery systems may operate in different delivery processes or paradigms. For example, the system may operate using a "waves process," a "shift process," or a combination. The waves process may arrange deliveries in waves of deliveries at different times. For example, wave deliveries may include a first wave of packages around a specific area (e.g., a route comprising sub-routes) several times a day. In contrast, a shift process may arrange deliveries to different areas, delivering first to a portion of a specific area (e.g., <NUM>%), followed by a later delivery to a remaining portion of the specific area. The disclosed systems and methods may be configurable to reconfigure routes and worker schedules based on optimization parameters for the delivery process.

In some embodiments, a delivery system operating in a "wave process" may provide for the delivery of packages to customers within a specific delivery area during one of a plurality of waves during a specific time period. For example, delivery workers may deliver packages to the intended recipients along a route or sub-route corresponding to the delivery area during a morning wave, and again during an afternoon wave. Each wave may correspond to both a cutoff time and a Promised Delivery Date (PDD). A cutoff time will generally correspond to an online order for shipment may, and may be a time associated with a certain wave or a PDD of the order at which the PDD associated with the wave become unavailable to the customer. In other words, if the customer does not order a package before the cutoff time, they will no longer be able to receive the item at the PDD associated with that cutoff time, and will only be able to receive the item at the next available PDD.

Referring to <FIG>, a schematic block diagram <NUM> illustrating an exemplary embodiment of a system comprising computerized systems for communications enabling shipping, transportation, and logistics operations is shown. As illustrated in <FIG>, system <NUM> may include a variety of systems, each of which may be connected to one another via one or more networks. The systems may also be connected to one another via a direct connection, for example, using a cable. The depicted systems include a shipment authority technology (SAT) system <NUM>, an external front end system <NUM>, an internal front end system <NUM>, a transportation system <NUM>, mobile devices 107A, 107B, and 107C, seller portal <NUM>, shipment and order tracking (SOT) system <NUM>, fulfillment optimization (FO) system <NUM>, fulfillment messaging gateway (FMG) <NUM>, supply chain management (SCM) system <NUM>, workforce management system <NUM>, mobile devices 119A, 119B, and 119C (depicted as being inside of fulfillment center (FC) <NUM>), <NUM>rd party fulfillment systems 121A, 121B, and 121C, fulfillment center authorization system (FC Auth) <NUM>, and labor management system (LMS) <NUM>.

SAT system <NUM>, in some embodiments, may be implemented as a computer system that monitors order status and delivery status. For example, SAT system <NUM> may determine whether an order is past its Promised Delivery Date (PDD) and may take appropriate action, including initiating a new order, reshipping the items in the non-delivered order, canceling the non-delivered order, initiating contact with the ordering customer, or the like. SAT system <NUM> may also monitor other data, including output (such as a number of packages shipped during a particular time period) and input (such as the number of empty cardboard boxes received for use in shipping). SAT system <NUM> may also act as a gateway between different devices in system <NUM>, enabling communication (e.g., using store-and-forward or other techniques) between devices such as external front end system <NUM> and FO system <NUM>.

External front end system <NUM>, in some embodiments, may be implemented as a computer system that enables external users to interact with one or more systems in system <NUM>. For example, in embodiments where system <NUM> enables the presentation of systems to enable users to place an order for an item, external front end system <NUM> may be implemented as a web server that receives search requests, presents item pages, and solicits payment information. For example, external front end system <NUM> may be implemented as a computer or computers running software such as the Apache HTTP Server, Microsoft Internet Information Services (IIS), NGINX, or the like. In other embodiments, external front end system <NUM> may run custom web server software designed to receive and process requests from external devices (e.g., mobile device 102A or computer 102B), acquire information from databases and other data stores based on those requests, and provide responses to the received requests based on acquired information.

In some embodiments, external front end system <NUM> may include one or more of a web caching system, a database, a search system, or a payment system. In one aspect, external front end system <NUM> may comprise one or more of these systems, while in another aspect, external front end system <NUM> may comprise interfaces (e.g., server-to-server, database-to-database, or other network connections) connected to one or more of these systems.

An illustrative set of steps, illustrated by <FIG>, <FIG>, <FIG>, and <FIG>, will help to describe some operations of external front end system <NUM>. External front end system <NUM> may receive information from systems or devices in system <NUM> for presentation and/or display. For example, external front end system <NUM> may host or provide one or more web pages, including a Search Result Page (SRP) (e.g., <FIG>), a Single Detail Page (SDP) (e.g., <FIG>), a Cart page (e.g., <FIG>), or an Order page (e.g., <FIG>). A user device (e.g., using mobile device 102A or computer 102B) may navigate to external front end system <NUM> and request a search by entering information into a search box. External front end system <NUM> may request information from one or more systems in system <NUM>. For example, external front end system <NUM> may request information from FO System <NUM> that satisfies the search request. External front end system <NUM> may also request and receive (from FO System <NUM>) a Promised Delivery Date or "PDD" for each product included in the search results. The PDD, in some embodiments, may represent an estimate of when a package containing the product will arrive at the user's desired location or a date by which the product is promised to be delivered at the user's desired location if ordered within a particular period of time, for example, by the end of the day (<NUM>:<NUM> PM). (PDD is discussed further below with respect to FO System <NUM>.

External front end system <NUM> may prepare an SRP (e.g., <FIG>) based on the information. The SRP may include information that satisfies the search request. For example, this may include pictures of products that satisfy the search request. The SRP may also include respective prices for each product, or information relating to enhanced delivery options for each product, PDD, weight, size, offers, discounts, or the like. External front end system <NUM> may send the SRP to the requesting user device (e.g., via a network).

A user device may then select a product from the SRP, e.g., by clicking or tapping a user interface, or using another input device, to select a product represented on the SRP. The user device may formulate a request for information on the selected product and send it to external front end system <NUM>. In response, external front end system <NUM> may request information related to the selected product. For example, the information may include additional information beyond that presented for a product on the respective SRP. This could include, for example, shelf life, country of origin, weight, size, number of items in package, handling instructions, or other information about the product. The information could also include recommendations for similar products (based on, for example, big data and/or machine learning analysis of customers who bought this product and at least one other product), answers to frequently asked questions, reviews from customers, manufacturer information, pictures, or the like.

External front end system <NUM> may prepare an SDP (Single Detail Page) (e.g., <FIG>) based on the received product information. The SDP may also include other interactive elements such as a "Buy Now" button, a "Add to Cart" button, a quantity field , a picture of the item, or the like. The SDP may further include a list of sellers that offer the product. The list may be ordered based on the price each seller offers such that the seller that offers to sell the product at the lowest price may be listed at the top. The list may also be ordered based on the seller ranking such that the highest ranked seller may be listed at the top. The seller ranking may be formulated based on multiple factors, including, for example, the seller's past track record of meeting a promised PDD. External front end system <NUM> may deliver the SDP to the requesting user device (e.g., via a network).

The requesting user device may receive the SDP which lists the product information. Upon receiving the SDP, the user device may then interact with the SDP. For example, a user of the requesting user device may click or otherwise interact with a "Place in Cart" button on the SDP. This adds the product to a shopping cart associated with the user. The user device may transmit this request to add the product to the shopping cart to external front end system <NUM>.

External front end system <NUM> may generate a Cart page (e.g., <FIG>). The Cart page, in some embodiments, lists the products that the user has added to a virtual "shopping cart. " A user device may request the Cart page by clicking on or otherwise interacting with an icon on the SRP, SDP, or other pages. The Cart page may, in some embodiments, list all products that the user has added to the shopping cart, as well as information about the products in the cart such as a quantity of each product, a price for each product per item, a price for each product based on an associated quantity, information regarding PDD, a delivery method, a shipping cost, user interface elements for modifying the products in the shopping cart (e.g., deletion or modification of a quantity), options for ordering other product or setting up periodic delivery of products, options for setting up interest payments, user interface elements for proceeding to purchase, or the like. A user at a user device may click on or otherwise interact with a user interface element (e.g., a button that reads "Buy Now") to initiate the purchase of the product in the shopping cart. Upon doing so, the user device may transmit this request to initiate the purchase to external front end system <NUM>.

External front end system <NUM> may generate an Order page (e.g., <FIG>) in response to receiving the request to initiate a purchase. The Order page, in some embodiments, re-lists the items from the shopping cart and requests input of payment and shipping information. For example, the Order page may include a section requesting information about the purchaser of the items in the shopping cart (e.g., name, address, e-mail address, phone number), information about the recipient (e.g., name, address, phone number, delivery information), shipping information (e.g., speed/method of delivery and/or pickup), payment information (e.g., credit card, bank transfer, check, stored credit), user interface elements to request a cash receipt (e.g., for tax purposes), or the like. External front end system <NUM> may send the Order page to the user device.

The user device may enter information on the Order page and click or otherwise interact with a user interface element that sends the information to external front end system <NUM>. From there, external front end system <NUM> may send the information to different systems in system <NUM> to enable the creation and processing of a new order with the products in the shopping cart.

In some embodiments, external front end system <NUM> may be further configured to enable sellers to transmit and receive information relating to orders.

Internal front end system <NUM>, in some embodiments, may be implemented as a computer system that enables internal users (e.g., employees of an organization that owns, operates, or leases system <NUM>) to interact with one or more systems in system <NUM>. For example, in embodiments where network <NUM> enables the presentation of systems to enable users to place an order for an item, internal front end system <NUM> may be implemented as a web server that enables internal users to view diagnostic and statistical information about orders, modify item information, or review statistics relating to orders. For example, internal front end system <NUM> may be implemented as a computer or computers running software such as the Apache HTTP Server, Microsoft Internet Information Services (IIS), NGINX, or the like. In other embodiments, internal front end system <NUM> may run custom web server software designed to receive and process requests from systems or devices depicted in system <NUM> (as well as other devices not depicted), acquire information from databases and other data stores based on those requests, and provide responses to the received requests based on acquired information.

In some embodiments, internal front end system <NUM> may include one or more of a web caching system, a database, a search system, a payment system, an analytics system, an order monitoring system, or the like. In one aspect, internal front end system <NUM> may comprise one or more of these systems, while in another aspect, internal front end system <NUM> may comprise interfaces (e.g., server-to-server, database-to-database, or other network connections) connected to one or more of these systems.

Transportation system <NUM>, in some embodiments, may be implemented as a computer system that enables communication between systems or devices in system <NUM> and mobile devices 107A-107C. Transportation system <NUM>, in some embodiments, may receive information from one or more mobile devices 107A-107C (e.g., mobile phones, smart phones, PDAs, or the like). For example, in some embodiments, mobile devices 107A-107C may comprise devices operated by delivery workers. The delivery workers, who may be permanent, temporary, or shift employees, may utilize mobile devices 107A-107C to effect delivery of packages containing the products ordered by users. For example, to deliver a package, the delivery worker may receive a notification on a mobile device indicating which package to deliver and where to deliver it. Upon arriving at the delivery location, the delivery worker may locate the package (e.g., in the back of a truck or in a crate of packages), scan or otherwise capture data associated with an identifier on the package (e.g., a barcode, an image, a text string, an RFID tag, or the like) using the mobile device, and deliver the package (e.g., by leaving it at a front door, leaving it with a security guard, handing it to the recipient, or the like). In some embodiments, the delivery worker may capture photo(s) of the package and/or may obtain a signature using the mobile device. The mobile device may send information to transportation system <NUM> including information about the delivery, including, for example, time, date, GPS location, photo(s), an identifier associated with the delivery worker, an identifier associated with the mobile device, or the like. Transportation system <NUM> may store this information in a database (not pictured) for access by other systems in system <NUM>. Transportation system <NUM> may, in some embodiments, use this information to prepare and send tracking data to other systems indicating the location of a particular package.

In some embodiments, certain users may use one kind of mobile device (e.g., permanent workers may use a specialized PDA with custom hardware such as a barcode scanner, stylus, and other devices) while other users may use other kinds of mobile devices (e.g., temporary or shift workers may utilize off-the-shelf mobile phones and/or smartphones).

In some embodiments, transportation system <NUM> may associate a user with each device. For example, transportation system <NUM> may store an association between a user (represented by, e.g., a user identifier, an employee identifier, or a phone number) and a mobile device (represented by, e.g., an International Mobile Equipment Identity (IMEI), an International Mobile Subscription Identifier (IMSI), a phone number, a Universal Unique Identifier (UUID), or a Globally Unique Identifier (GUID)). Transportation system <NUM> may use this association in conjunction with data received on deliveries to analyze data stored in the database in order to determine, among other things, a location of the worker, an efficiency of the worker, or a speed of the worker.

Seller portal <NUM>, in some embodiments, may be implemented as a computer system that enables sellers or other external entities to electronically communicate with one or more systems in system <NUM>. For example, a seller may utilize a computer system (not pictured) to upload or provide product information, order information, contact information, or the like, for products that the seller wishes to sell through system <NUM> using seller portal <NUM>.

Shipment and order tracking system <NUM>, in some embodiments, may be implemented as a computer system that receives, stores, and forwards information regarding the location of packages containing products ordered by customers (e.g., by a user using devices 102A-102B). In some embodiments, shipment and order tracking system <NUM> may request or store information from web servers (not pictured) operated by shipping companies that deliver packages containing products ordered by customers.

In some embodiments, shipment and order tracking system <NUM> may request and store information from systems depicted in system <NUM>. For example, shipment and order tracking system <NUM> may request information from transportation system <NUM>. As discussed above, transportation system <NUM> may receive information from one or more mobile devices 107A-107C (e.g., mobile phones, smart phones, PDAs, or the like) that are associated with one or more of a user (e.g., a delivery worker) or a vehicle (e.g., a delivery truck). In some embodiments, shipment and order tracking system <NUM> may also request information from workforce management system (WMS) <NUM> to determine the location of individual products inside of a fulfillment center (e.g., fulfillment center <NUM>). Shipment and order tracking system <NUM> may request data from one or more of transportation system <NUM> or WMS <NUM>, process it, and present it to a device (e.g., user devices 102A and 102B) upon request.

Fulfillment optimization (FO) system <NUM>, in some embodiments, may be implemented as a computer system that stores information for customer orders from other systems (e.g., external front end system <NUM> and/or shipment and order tracking system <NUM>). FO system <NUM> may also store information describing where particular items are held or stored. For example, certain items may be stored only in one fulfillment center, while certain other items may be stored in multiple fulfillment centers. In still other embodiments, certain fulfilment centers may be designed to store only a particular set of items (e.g., fresh produce or frozen products). FO system <NUM> stores this information as well as associated information (e.g., quantity, size, date of receipt, expiration date, etc.).

FO system <NUM> may also calculate a corresponding PDD (promised delivery date) for each product. The PDD, in some embodiments, may be based on one or more factors. For example, FO system <NUM> may calculate a PDD for a product based on a past demand for a product (e.g., how many times that product was ordered during a period of time), an expected demand for a product (e.g., how many customers are forecast to order the product during an upcoming period of time), a network-wide past demand indicating how many products were ordered during a period of time, a network-wide expected demand indicating how many products are expected to be ordered during an upcoming period of time, one or more counts of the product stored in each fulfillment center <NUM>, which fulfillment center stores each product, expected or current orders for that product, or the like.

In some embodiments, FO system <NUM> may determine a PDD for each product on a periodic basis (e.g., hourly) and store it in a database for retrieval or sending to other systems (e.g., external front end system <NUM>, SAT system <NUM>, shipment and order tracking system <NUM>). In other embodiments, FO system <NUM> may receive electronic requests from one or more systems (e.g., external front end system <NUM>, SAT system <NUM>, shipment and order tracking system <NUM>) and calculate the PDD on demand.

Fulfilment messaging gateway (FMG) <NUM>, in some embodiments, may be implemented as a computer system that receives a request or response in one format or protocol from one or more systems in system <NUM>, such as FO system <NUM>, converts it to another format or protocol, and forward it in the converted format or protocol to other systems, such as WMS <NUM> or <NUM>rd party fulfillment systems 121A, 121B, or 121C, and vice versa.

Supply chain management (SCM) system <NUM>, in some embodiments, may be implemented as a computer system that performs forecasting functions. For example, SCM system <NUM> may forecast a level of demand for a particular product based on, for example, based on a past demand for products, an expected demand for a product, a network-wide past demand, a network-wide expected demand, a count products stored in each fulfillment center <NUM>, expected or current orders for each product, or the like. In response to this forecasted level and the amount of each product across all fulfillment centers, SCM system <NUM> may generate one or more purchase orders to purchase and stock a sufficient quantity to satisfy the forecasted demand for a particular product.

Workforce management system (WMS) <NUM>, in some embodiments, may be implemented as a computer system that monitors workflow. For example, WMS <NUM> may receive event data from individual devices (e.g., devices 107A-107C or 119A-119C) indicating discrete events. For example, WMS <NUM> may receive event data indicating the use of one of these devices to scan a package. As discussed below with respect to fulfillment center <NUM> and <FIG>, during the fulfillment process, a package identifier (e.g., a barcode or RFID tag data) may be scanned or read by machines at particular stages (e.g., automated or handheld barcode scanners, RFID readers, high-speed cameras, devices such as tablet 119A, mobile device/PDA 119B, computer 119C, or the like). WMS <NUM> may store each event indicating a scan or a read of a package identifier in a corresponding database (not pictured) along with the package identifier, a time, date, location, user identifier, or other information, and may provide this information to other systems (e.g., shipment and order tracking system <NUM>).

WMS <NUM>, in some embodiments, may store information associating one or more devices (e.g., devices 107A-107C or 119A-119C) with one or more users associated with system <NUM>. For example, in some situations, a user (such as a part- or full-time employee) may be associated with a mobile device in that the user owns the mobile device (e.g., the mobile device is a smartphone). In other situations, a user may be associated with a mobile device in that the user is temporarily in custody of the mobile device (e.g., the user checked the mobile device out at the start of the day, will use it during the day, and will return it at the end of the day).

WMS <NUM>, in some embodiments, may maintain a work log for each user associated with system <NUM>. For example, WMS <NUM> may store information associated with each employee, including any assigned processes (e.g., unloading trucks, picking items from a pick zone, rebin wall work, packing items), a user identifier, a location (e.g., a floor or zone in a fulfillment center <NUM>), a number of units moved through the system by the employee (e.g., number of items picked, number of items packed), an identifier associated with a device (e.g., devices 119A-119C), or the like. In some embodiments, WMS <NUM> may receive check-in and check-out information from a timekeeping system, such as a timekeeping system operated on a device 119A-119C.

<NUM>rd party fulfillment (3PL) systems 121A-121C, in some embodiments, represent computer systems associated with third-party providers of logistics and products. For example, while some products are stored in fulfillment center <NUM> (as discussed below with respect to <FIG>), other products may be stored off-site, may be produced on demand, or may be otherwise unavailable for storage in fulfillment center <NUM>. 3PL systems 121A-121C may be configured to receive orders from FO system <NUM> (e.g., through FMG <NUM>) and may provide products and/or services (e.g., delivery or installation) to customers directly. In some embodiments, one or more of 3PL systems 121A-121C may be part of system <NUM>, while in other embodiments, one or more of 3PL systems 121A-121C may be outside of system <NUM> (e.g., owned or operated by a third-party provider).

Fulfillment Center Auth system (FC Auth) <NUM>, in some embodiments, may be implemented as a computer system with a variety of functions. For example, in some embodiments, FC Auth <NUM> may act as a single-sign on (SSO) service for one or more other systems in system <NUM>. For example, FC Auth <NUM> may enable a user to log in via internal front end system <NUM>, determine that the user has similar privileges to access resources at shipment and order tracking system <NUM>, and enable the user to access those privileges without requiring a second log in process. FC Auth <NUM>, in other embodiments, may enable users (e.g., employees) to associate themselves with a particular task. For example, some employees may not have an electronic device (such as devices 119A-119C) and may instead move from task to task, and zone to zone, within a fulfillment center <NUM>, during the course of a day. FC Auth <NUM> may be configured to enable those employees to indicate what task they are performing and what zone they are in at different times of day.

Labor management system (LMS) <NUM>, in some embodiments, may be implemented as a computer system that stores attendance and overtime information for employees (including full-time and part-time employees). For example, LMS <NUM> may receive information from FC Auth <NUM>, WMA <NUM>, devices 119A-119C, transportation system <NUM>, and/or devices 107A-107C.

The particular configuration depicted in <FIG> is an example only. For example, while <FIG> depicts FC Auth system <NUM> connected to FO system <NUM>, not all embodiments require this particular configuration. Indeed, in some embodiments, the systems in system <NUM> may be connected to one another through one or more public or private networks, including the Internet, an Intranet, a WAN (Wide-Area Network), a MAN (Metropolitan-Area Network), a wireless network compliant with the IEEE <NUM>. 11a/b/g/n Standards, a leased line, or the like. In some embodiments, one or more of the systems in system <NUM> may be implemented as one or more virtual servers implemented at a data center, server farm, or the like.

<FIG> depicts a fulfillment center <NUM>. Fulfillment center <NUM> is an example of a physical location that stores items for shipping to customers when ordered. Fulfillment center (FC) <NUM> may be divided into multiple zones, each of which are depicted in <FIG>. These "zones," in some embodiments, may be thought of as virtual divisions between different stages of a process of receiving items, storing the items, retrieving the items, and shipping the items. So while the "zones" are depicted in <FIG>, other divisions of zones are possible, and the zones in <FIG> may be omitted, duplicated, or modified in some embodiments.

Inbound zone <NUM> represents an area of FC <NUM> where items are received from sellers who wish to sell products using system <NUM> from <FIG>. For example, a seller may deliver items 202A and 202B using truck <NUM>. Item 202A may represent a single item large enough to occupy its own shipping pallet, while item 202B may represent a set of items that are stacked together on the same pallet to save space.

A worker will receive the items in inbound zone <NUM> and may optionally check the items for damage and correctness using a computer system (not pictured). For example, the worker may use a computer system to compare the quantity of items 202A and 202B to an ordered quantity of items. If the quantity does not match, that worker may refuse one or more of items 202A or 202B. If the quantity does match, the worker may move those items (using, e.g., a dolly, a handtruck, a forklift, or manually) to buffer zone <NUM>. Buffer zone <NUM> may be a temporary storage area for items that are not currently needed in the picking zone, for example, because there is a high enough quantity of that item in the picking zone to satisfy forecasted demand. In some embodiments, forklifts <NUM> operate to move items around buffer zone <NUM> and between inbound zone <NUM> and drop zone <NUM>. If there is a need for items 202A or 202B in the picking zone (e.g., because of forecasted demand), a forklift may move items 202A or 202B to drop zone <NUM>.

Drop zone <NUM> may be an area of FC <NUM> that stores items before they are moved to picking zone <NUM>. A worker assigned to the picking task (a "picker") may approach items 202A and 202B in the picking zone, scan a barcode for the picking zone, and scan barcodes associated with items 202A and 202B using a mobile device (e.g., device 119B). The picker may then take the item to picking zone <NUM> (e.g., by placing it on a cart or carrying it).

Picking zone <NUM> may be an area of FC <NUM> where items <NUM> are stored on storage units <NUM>. In some embodiments, storage units <NUM> may comprise one or more of physical shelving, bookshelves, boxes, totes, refrigerators, freezers, cold stores, or the like. In some embodiments, picking zone <NUM> may be organized into multiple floors. In some embodiments, workers or machines may move items into picking zone <NUM> in multiple ways, including, for example, a forklift, an elevator, a conveyor belt, a cart, a handtruck, a dolly, an automated robot or device, or manually. For example, a picker may place items 202A and 202B on a handtruck or cart in drop zone <NUM> and walk items 202A and 202B to picking zone <NUM>.

A picker may receive an instruction to place (or "stow") the items in particular spots in picking zone <NUM>, such as a particular space on a storage unit <NUM>. For example, a picker may scan item 202A using a mobile device (e.g., device 119B). The device may indicate where the picker should stow item 202A, for example, using a system that indicate an aisle, shelf, and location. The device may then prompt the picker to scan a barcode at that location before stowing item 202A in that location. The device may send (e.g., via a wireless network) data to a computer system such as WMS <NUM> in <FIG> indicating that item 202A has been stowed at the location by the user using device 119B.

Once a user places an order, a picker may receive an instruction on device 119B to retrieve one or more items <NUM> from storage unit <NUM>. The picker may retrieve item <NUM>, scan a barcode on item <NUM>, and place it on transport mechanism <NUM>. While transport mechanism <NUM> is represented as a slide, in some embodiments, transport mechanism may be implemented as one or more of a conveyor belt, an elevator, a cart, a forklift, a handtruck, a dolly, a cart, or the like. Item <NUM> may then arrive at packing zone <NUM>.

Packing zone <NUM> may be an area of FC <NUM> where items are received from picking zone <NUM> and packed into boxes or bags for eventual shipping to customers. In packing zone <NUM>, a worker assigned to receiving items (a "rebin worker") will receive item <NUM> from picking zone <NUM> and determine what order it corresponds to. For example, the rebin worker may use a device, such as computer 119C, to scan a barcode on item <NUM>. Computer 119C may indicate visually which order item <NUM> is associated with. This may include, for example, a space or "cell" on a wall <NUM> that corresponds to an order. Once the order is complete (e.g., because the cell contains all items for the order), the rebin worker may indicate to a packing worker (or "packer") that the order is complete. The packer may retrieve the items from the cell and place them in a box or bag for shipping. The packer may then send the box or bag to a hub zone <NUM>, e.g., via forklift, cart, dolly, handtruck, conveyor belt, manually, or otherwise.

Hub zone <NUM> may be an area of FC <NUM> that receives all boxes or bags ("packages") from packing zone <NUM>. Workers and/or machines in hub zone <NUM> may retrieve package <NUM> and determine which portion of a delivery area each package is intended to go to, and route the package to an appropriate camp zone <NUM>. For example, if the delivery area has two smaller sub-areas, packages will go to one of two camp zones <NUM>. In some embodiments, a worker or machine may scan a package (e.g., using one of devices 119A-119C) to determine its eventual destination. Routing the package to camp zone <NUM> may comprise, for example, determining a portion of a geographical area that the package is destined for (e.g., based on a postal code) and determining a camp zone <NUM> associated with the portion of the geographical area.

Camp zone <NUM>, in some embodiments, may comprise one or more buildings, one or more physical spaces, or one or more areas, where packages are received from hub zone <NUM> for sorting into routes and/or sub-routes. In some embodiments, camp zone <NUM> is physically separate from FC <NUM> while in other embodiments camp zone <NUM> may form a part of FC <NUM>.

Workers and/or machines in camp zone <NUM> may determine which route and/or sub-route a package <NUM> should be associated with, for example, based on a comparison of the destination to an existing route and/or sub-route, a calculation of workload for each route and/or sub-route, the time of day, a shipping method, the cost to ship the package <NUM>, a PDD associated with the items in package <NUM>, or the like. In some embodiments, a worker or machine may scan a package (e.g., using one of devices 119A-119C) to determine its eventual destination. Once package <NUM> is assigned to a particular route and/or sub-route, a worker and/or machine may move package <NUM> to be shipped. In exemplary <FIG>, camp zone <NUM> includes a truck <NUM>, a car <NUM>, and delivery workers 224A and 224B. In some embodiments, truck <NUM> may be driven by delivery worker 224A, where delivery worker 224A is a full-time employee that delivers packages for FC <NUM> and truck <NUM> is owned, leased, or operated by the same company that owns, leases, or operates FC <NUM>. In some embodiments, car <NUM> may be driven by delivery worker 224B, where delivery worker 224B is a "flex" or occasional worker that is delivering on an as-needed basis (e.g., seasonally). Car <NUM> may be owned, leased, or operated by delivery worker 224B.

Referring back to <FIG>, an exemplary embodiment of a package tracking process for identifying and tracking individual packages is described. In some embodiments, SAT system <NUM> may initiate the package tracking process, electronically requesting and aggregating package information corresponding to individual packages, associated with currently pending orders and returns, from other systems such as external front end system <NUM>, shipment and order tracking (SOT) system <NUM>, FO system <NUM>, FMG <NUM>, WMS <NUM>, and 3PL systems 121A-121C. A package may refer to a physical container (e.g., a box, a parcel, an envelope, or any packaging configured to hold one or more items) holding one or more items associated with an order or a return as tracked by a network of electronic systems (e.g., SAT system <NUM>, FO system <NUM>, etc.) using a unique package identifier.

The electronic request and aggregation of information may occur once a day (e.g., at the end of a day), multiple times per day at regular intervals or as needed, or in real-time as different systems generate additional information (e.g., delivery status updates). The different systems may also electronically send and receive information with SAT system <NUM> each at different times, intervals, or frequencies. The communication and transfer of information between SAT system <NUM> and each different system is described below.

In some embodiments, SAT system <NUM> may electronically request and aggregate order information from external front end system <NUM>, internal front end system <NUM>, or a customer return system (not shown). Upon receiving an electronic request for information from SAT system <NUM>, external front end system <NUM>, internal front end system <NUM>, or a customer return system (not shown) may compile all order, return, and/or exchange data, which may include, for example, items in the order, quantity of each item, and PDD. The collected order information is then electronically sent to SAT system <NUM> for further processing. SAT system <NUM> may communicate continuously with external front end system <NUM>, internal front end system <NUM>, or a customer return system (not shown) so that the order information is continuously updated. Alternatively, the systems may communicate at a predefined interval or at predefined times, updating order information stored in SAT system <NUM> from time to time with new order information collected at external front end system <NUM>, internal front end system <NUM>, or a customer return system (not shown).

In some embodiments, SAT system <NUM> may also electronically request and aggregate delivery status information from SOT system <NUM>. SAT system <NUM> may communicate continuously with SOT system <NUM> so that the delivery status information is continuously updated as each delivery attempt is made by a delivery worker 224A or 224B or at the end of each delivery run. Alternatively, the systems may communicate at a predefined interval or at predefined times, updating delivery status information stored in SAT system <NUM> from time to time with new delivery status information collected at SOT system <NUM>. The delivery status information may include event data generated when a delivery worker 224A or 224B scans or reads package identifier on each package after a corresponding delivery attempt using a mobile device as described above.

The event data may comprise, for example, the scan/read time, date, a package identifier, delivery status, and intended recipient. If the delivery attempt was unsuccessful, the event data may also comprise a reason for the failed attempt, such as a determination of exceeded capacity at camp zone <NUM>, a determination of a lack of resources during delivery, a determination of package that was mis-sorted, unavailability of a recipient, or a damaged package. Other reasons for non-delivery would be apparent to one of ordinary skill in the art and are within the scope of the invention. A delivery worker 224A or 224B using a mobile device (e.g., devices 107A-107C in <FIG>) may add a reason for the non-delivery into the event data by selecting one or more reasons from a drop-down list displayed on a user interface. SAT system <NUM> may then add one or more corresponding reason codes to the event data and/or corresponding package information as described below. Furthermore, if a delivery worker 224A or 224B picked up a returned package from a customer during a delivery run, the event data may also comprise information for the returned package.

In some embodiments, SAT system <NUM> may also electronically request and aggregate package information from WMS <NUM> and 3PL systems 121A-121C. SAT system <NUM>, WMS <NUM>, and 3PL systems 121A-121C may communicate continuously with each other so that the package information is continuously updated as each package is scanned or read by a user using a mobile device as described above. Alternatively, the systems may communicate at a predefined interval or at predefined times, updating package information stored in SAT system <NUM> from time to time with new package information collected at the other systems. The package information may comprise event data as a user scans or reads package identifier on each package to indicate a particular event such as arriving at a camp or being loaded onto a delivery truck. The event data may further comprise a package identifier, a time, date, location, user identifier, or other information.

In order to request and collect package information from WMS <NUM> and 3PL systems 121A-121C, SAT system <NUM> may send an electronic request to FO system <NUM>, which then may forward the electronic request to FMG <NUM>. FMG <NUM> then may send an electronic request to each of WMS <NUM> and 3PL systems 121A-121C after converting the electronic request to another format or protocol appropriate for each system as described above.

Irrespective of the electronic requests from SAT system <NUM>, WMS and 3PL systems 121A-121C may continuously gather and update package information corresponding to each package based on the event data gathered from individual devices (e.g., devices 107A-107C or 119A-119C) as the packages arrive at camp zone <NUM> or are loaded onto a truck <NUM> or a car <NUM>. As described above, package information corresponding to a package may be organized based on the package identifier, and new event data may be associated with the appropriate package information based on the package identifier. In some embodiments, a package identifier may be scanned or read at least twice, first as they arrive at the camp zone <NUM>, and second as they are loaded onto a truck <NUM> or a car <NUM> for delivery. Packages may also be scanned or read if a delivery worker 224A or 224B notices that the packaging (e.g., box, envelope, or tape) of the package and/or the contents therein are damaged.

Once the event data relating to every package in each of WMS <NUM> or 3PL systems 121A-121C is aggregated or as the event data for each package is generated, the event data is sent to FMG <NUM>, which converts it to a standardized format if needed. FMG <NUM> then forwards the converted event data to FO system <NUM>, which then forwards the event data to SAT system <NUM>.

Once information from WMS <NUM> or 3PL systems 121A-121C are aggregated, SAT system <NUM> may then process the aggregated information, in real-time for example, to maintain a database of packages being processed through the system <NUM> at any given moment. This process may alternatively be performed once a day, multiple times per day at regular intervals or as needed, or in real-time as additional information is aggregated from the other systems. The processing may comprise: parsing the information to a standardized format or protocol; mapping one or more package identifiers (and thus the corresponding packages) to each order; consolidating and sorting all event data based on individual package identifiers; determining the history of individual packages based at least on the sequence of events corresponding to the corresponding package identifier; and determining the current status of individual packages based on their respective last event. The statuses a package could take may comprise, for example, arrived at camp zone <NUM>, departed for delivery <NUM>, delivery attempt unsuccessful <NUM>, and delivery successful <NUM>.

<FIG> is a flowchart of an exemplary computerized initiation process <NUM> that SAT system <NUM> follows in order to determine the status of a package and the appropriate package tracking process to follow, consistent with the disclosed embodiments. In some embodiments, SAT system <NUM> may make the status determination based on the last event data associated with a package and/or the sequence of events associated with the package. Starting from step <NUM>, SAT system <NUM> may, in some embodiments, determine the status of a package by requesting the last event data associated with the corresponding package identifier from, for example, WMS <NUM>.

Alternatively or additionally, if the last event data indicates, for example, that the package was marked lost, SAT system <NUM> may determine the last known location based on previous event data or other accompanying data such as a user identifier (e.g., determining based on a user identifier and thus the user's assigned work area) and update the status accordingly. For example, a previous event data may indicate that the package departed for delivery, in which case SAT system <NUM> sets the status as being departed for delivery <NUM>. In some embodiments where multiple event data exists for a package identifier with conflicting indications, SAT system <NUM> may choose to determine the status based on the latest one of the conflicting event data and ignore the others. In some embodiments, SAT system <NUM> may also determine that the current status of a package is incorrect and change the status.

Referring back to <FIG>, SAT system <NUM> may determine, at step <NUM>, whether the last event indicates that the package arrived at camp zone <NUM>. If positive, SAT system <NUM> may update, at step <NUM>, the package information associated with the package so its status indicates that the package has arrived at camp zone <NUM>. The process may then continue with package tracking process <NUM> in <FIG>.

If the determination from step <NUM> is negative, SAT system <NUM> may determine, at step <NUM>, whether the last event indicates that the package departed for delivery. If the result of this determination is positive, SAT system <NUM> may update, at step <NUM>, the package information associated with the package so its status indicates that the package was loaded onto a truck <NUM> or a car <NUM> and departed for delivery. The process may then continue with package tracking process <NUM> in <FIG>.

If the determination at step <NUM> is negative, SAT system <NUM> may determine, at step <NUM>, whether the last event indicates that a delivery attempt was made but failed. If the result of this determination is positive, SAT system <NUM> may update, at step <NUM>, the package information associated with the package so its status indicates that the delivery attempt was unsuccessful. The process may then continue with package tracking process <NUM> in <FIG>.

If the determination at step <NUM> is negative, SAT system <NUM> may determine that the package was successfully delivered and update, at step <NUM>, the package information associated with the package so its status indicates that the delivery was successful. The process may then continue with package tracking process <NUM> in <FIG>.

The four different statuses are only intended to serve as examples and an alternative set of statuses is also within the scope of the disclosed embodiments, and the initiation process <NUM> may be modified to add or remove other determinations to accommodate an alternative set of statuses.

Referring to <FIG>, exemplary package tracking processes <NUM>, <NUM>, <NUM>, and <NUM> are described below, consistent with the disclosed embodiments. SAT system <NUM> may, at a predetermined interval (e.g., <NUM> hours), iterate through every package in the database and perform one or more of package tracking processes <NUM>, <NUM>, <NUM>, and <NUM> based on the determinations described above in view of <FIG>. SAT system <NUM> may iterate sequentially through each package in the database, selecting and stepping through an appropriate process based on the corresponding status assigned to each package, sort the packages according to their statuses, and perform each process in batches, or otherwise.

Package tracking processes <NUM>, <NUM>, <NUM>, and <NUM> serve to verify that each package's information, which indicates that the package has not yet been delivered and therefore should have a corresponding package somewhere in FC <NUM>, can actually be mapped to a corresponding package (e.g., by verifying that the package corresponding to package information having a status "arrived at camp zone" is actually located at camp zone <NUM>). Package tracking processes <NUM>, <NUM>, <NUM>, and <NUM> may also identify and correct package information that has been assigned an incorrect status and reorder packages if needed. The four different processes are only intended to serve as examples and an alternative set of processes that match the set of statuses employed above is also within the scope of the disclosed embodiments.

In some embodiments, other systems such as SOT system <NUM>, FO system <NUM>, and WMS <NUM> may halt processing packages while SAT system <NUM> is iterating through the database of packages and resume once SAT system <NUM> is finished. Alternatively, in other embodiments, other systems such as SOT system <NUM>, FO system <NUM>, and WMS <NUM> may continue processing packages at their regular speeds, respectively, or process them at a reduced speed. Additional event data generated by the other systems while SAT system <NUM> is performing the packaging tracking processes may be electronically stored at a temporary location and reconciled with the list of packages in database after SAT system <NUM> has finished iterating through the database of packages.

A shipment cycle may refer to the period of time from the moment SAT system <NUM> has finished performing one or more of package tracking processes <NUM>, <NUM>, <NUM>, and <NUM> for every package information in the database to the moment after a predetermined interval (e.g., <NUM> hours), during which system <NUM> attempted to deliver every package, and SAT system <NUM> is about to begin performing one or more of package tracking processes <NUM>, <NUM>, <NUM>, and <NUM> on each package information again. The beginning of a shipment cycle may coincide with the end of a work day or midnight, at which point every package has been loaded and attempted to be delivered at least once. In other words, each shipment cycle is separated by a period of time during which SAT system <NUM> performs package tracking processes <NUM>, <NUM>, <NUM>, and <NUM>.

It is important to note that, during every shipment cycle, every package in the system <NUM> may be attempted to be loaded and sent out for delivery via a truck <NUM> or a car <NUM> (e.g., every package in system <NUM> is loaded and sent out at least once each day). If a package could not be loaded at least once during a shipment cycle, WMS <NUM> may add event data to the corresponding package information in SAT system <NUM> that the package was not delivered due to exceeding capacity at camp zone <NUM> (e.g., the number of packages for delivery exceeded the number that can be processed at FC <NUM>). It is also noted that each package may be at different locations (e.g., at camp zone <NUM>, on a truck <NUM> or a car <NUM>) while one or more of package tracking processes <NUM>, <NUM>, <NUM>, and <NUM> are being performed.

At the end of a shipment cycle (i.e., before any of package tracking processes <NUM>, <NUM>, <NUM>, and <NUM> begins), SAT system <NUM> may generate a list of packages currently in system <NUM>, the package identifiers of which were scanned or read by a mobile device (e.g., 107A-107C or 119A-119C). As each package is being scanned or read, a damaged package may be omitted from the list of packages in order to be flagged as meeting the condition for reorder later during package tracking processes <NUM>, <NUM>, <NUM>, or <NUM>.

<FIG> depicts computerized package tracking process <NUM> that SAT system <NUM> may follow when a package is determined to have arrived at camp zone <NUM>. The package may have arrived from hub zone <NUM> or a truck <NUM> or a car <NUM> after having been loaded for delivery.

At step <NUM>, SAT system <NUM> may verify whether a particular package exists in system <NUM> by determining whether the corresponding package identifier was scanned or read at the end of the previous shipment cycle.

A negative determination from step <NUM> may indicate, as represented at step <NUM>, that the package is lost (i.e., unaccounted for), and SAT system <NUM> may update the corresponding package information to flag the package identifier as meeting the condition for reorder at step <NUM>. Flagging, for example, may comprise modifying a parameter (e.g., a priority status and/or indicating that the package should be delivered more quickly) in a database storing the corresponding package information. (In some embodiments, upon flagging the package identifier as meeting a condition for reordering, the method may proceed to process <NUM> in <FIG>, described in further detail below.

On the other hand, a positive determination from step <NUM> may indicate that a physical package exists. In this case, the package may have never left camp zone <NUM> due to an internal delay (e.g., exceeded capacity at camp zone <NUM>) or the package may have been out for delivery during the immediately preceding shipment cycle but came back to camp zone <NUM> without being delivered for one or more reasons (e.g., delivery truck could not complete delivery within working hours). In this situation, SAT system <NUM> may determine, at block <NUM>, the reason why the package was not delivered based on the delivery status information from SOT system <NUM>.

If it is determined that the non-delivery was due to exceeded capacity as represented at step <NUM>, SAT system <NUM> may determine, at step <NUM>, whether it has been more than a first predetermined length of time (e.g., <NUM> days) since the PDD. The capacity exceeded at step <NUM> may include, for example, number of available delivery workers 224A or 224B, number of available trucks <NUM> or cars <NUM> for delivery, and amount of space on a truck <NUM> or a car <NUM>. In other embodiments, the length of time that must pass before a package is flagged as meeting the condition for reorder may be less than or greater than <NUM> days, such as half a day, <NUM> days, or the like. In yet other embodiments, the length of time may vary based on the particular resource that lacked.

If the determination from step <NUM> is positive, SAT system <NUM> may update the corresponding package information to flag the package identifier as meeting the condition for reorder at step <NUM> in a manner similar to step <NUM> described above. If not, as represented at step <NUM>, SAT system <NUM> may leave the corresponding package information unchanged, so that the package may be attempted for delivery again during the next shipment cycle, and process the next package in the database.

Referring back to block <NUM>, if the non-delivery was instead due to a customer's fault as represented at step <NUM>, SAT system <NUM> may determine whether more than a second predetermined length of time (e.g., <NUM> days) has passed since the PDD (step <NUM>) and flag the corresponding package identifier as meeting the condition for reorder at step <NUM> in a manner similar to step <NUM> described above. If not, as represented at step <NUM>, SAT system <NUM> may leave the corresponding package information unchanged. In other embodiments, the second predetermined length of time may be less than or greater than <NUM> days, such as half a day, <NUM> days, or the like. In yet other embodiments, the length of time may vary based on the particular delay caused by the customer.

Referring back to block <NUM>, if the non-delivery was instead due to a lost or damaged package as represented at <NUM>, SAT system <NUM> may determine that there is an error in the package information because the package was previously determined to exist at step <NUM> (i.e., physically present and undamaged) yet the non-delivered reason indicates that the package is lost or damaged. In this case, SAT system <NUM> may override the non-delivered reason in the package information to "exceeded capacity" as represented at step <NUM>, thus attributing the unknown reason for non-delivery to an internal delay as opposed to, for example, a customer's fault.

If the determination at step <NUM> is negative, indicating that the reason for non-delivery was something else, SAT system <NUM> may leave the corresponding package information unchanged at step <NUM>, so that the package may be attempted for delivery again during the next shipment cycle, and process the next package in the database.

<FIG> depicts computerized package tracking process <NUM> that SAT system <NUM> may follow when a package is determined to have departed for delivery, for example, if a package departed during the immediately preceding shipment cycle but a delivery attempt was not made.

At step <NUM>, SAT system <NUM> may verify, as described above with respect to step <NUM>, whether the package still exists in the system. A negative determination from step <NUM> may indicate, as represented at step <NUM> and described above with respect to step <NUM>, that the package is lost. SAT system <NUM> may then flag the corresponding package identifier as meeting the condition for reorder at step <NUM> in a manner similar to step <NUM> described above.

On the other hand, if the package is verified to exist at step <NUM>, SAT system <NUM> may then determine, at block <NUM>, why the package was not delivered based on the delivery status information from SOT system <NUM>. If it is determined that the non-delivery was due to lack of resources such as delivery time, SAT system <NUM> may determine whether more than a first predetermined length of time has passed since the PDD (step <NUM>) and flag the corresponding package information as meeting the condition for reorder if so (step <NUM>) or keep the corresponding package information unchanged (step <NUM>) as described above with respect to steps <NUM>-<NUM>.

Alternatively, if it is determined that the non-delivery was instead due to a customer's fault as represented at step <NUM>, SAT system <NUM> may determine whether more than a second predetermined length of time has passed since the PDD (step <NUM>) and flag the corresponding package information as meeting the condition for reorder if so (step <NUM>) or keep the package information unchanged (step <NUM>) as described above with respect to steps <NUM>-<NUM>.

Even still, if it is determined in block <NUM> that the non-delivery was instead due to a lost or damaged package as represented at <NUM>, SAT system <NUM> may determine that there is an error as described above with respect to step <NUM>. In this case, SAT system <NUM> may override the non-delivered reason to "mis-sort" (step <NUM>), indicating that the package was mis-sorted (e.g., loaded on to a wrong delivery truck <NUM> or car <NUM>) because the previous determinations indicate that the package had departed for delivery (step <NUM>) but is still at camp zone <NUM> for some reason (step <NUM>), suggesting that the package had not been where it was supposed to be. SAT system <NUM> may attempt to deliver these packages during the following shipment cycle.

If the determination at step <NUM> is negative, indicating that the reason for non-delivery was something else, SAT system <NUM> may keep the corresponding package information unchanged (step <NUM>) as described above with respect to step <NUM>.

<FIG> depicts computerized package tracking process <NUM> that SAT system <NUM> may follow when SAT system <NUM> determines that the package failed to deliver, for example, during the immediately preceding shipment cycle (e.g., a delivery person 224A or 224B arrived at the recipient's address but was unable to complete the delivery because the recipient was not present).

At step <NUM>, SAT system <NUM> may verify, as described above with respect to step <NUM>, whether the package still exists in the system. A negative determination from step <NUM> may indicate, as represented at step <NUM>, that the package is lost. SAT system <NUM> may then flag the corresponding package identifier as meeting the condition for reorder at step <NUM> in a manner similar to step <NUM> described above.

If the package is verified to exist at step <NUM>, SAT system <NUM> may then determine, at block <NUM>, why the package was not delivered based on the delivery status information from SOT system <NUM>. If it is determined that the non-delivery was due to a customer's fault as represented at step <NUM>, SAT system <NUM> may determine whether more than a second predetermined length of time has passed since the PDD (step <NUM>) and flag the corresponding package information as meeting the condition for reorder if so (step <NUM>) or keep the package information unchanged (step <NUM>) as described above with respect to steps <NUM>-<NUM>.

Alternatively, if it is determined in block <NUM> that the non-delivery was instead due to a lost or damaged package as represented at <NUM>, SAT system <NUM> may determine that there is an error and override the non-delivered reason to "mis-sort" (step <NUM>) as described above with respect to steps <NUM>-<NUM>. If the determination at step <NUM> is negative, indicating that the reason for non-delivery was something else, SAT system may keep the corresponding package information unchanged (step <NUM>) as previous described above with respect to step <NUM>.

In this case, SAT system <NUM> may not consider whether the non-delivery was due to lack of resources as it did in other package tracking processes <NUM> and <NUM> because a delivery attempt was indeed made, which means that, for example, the delivery person 224A or 224B had enough resources to arrive at the recipient's address and attempt the delivery.

<FIG> depicts package tracking process <NUM> that SAT system <NUM> follows when it determines that a package was successfully delivered, for example, during the immediately preceding shipment cycle.

At step <NUM>, SAT system <NUM> may verify, as described above with respect to step <NUM>, whether the package still exists in the system. A negative determination correctly indicates that the package does not exist in the system <NUM>, and the corresponding package information is left unchanged at step <NUM>, because it is true that a delivered package may not exist within system <NUM>. A positive determination, however, indicates that the information from SOT system <NUM>, and thus the current status of the package may be improper because a delivered package can no longer exist in system <NUM>. In this case, SAT system <NUM> may override, at step <NUM>, the information associated with the package to indicate that the package was not delivered due to lack of resources. SAT system <NUM> may then determine, at step <NUM>, whether more than a first predetermined length of time has passed since the PDD and take appropriate actions at steps <NUM> or <NUM> based on the determination, as described above with respect to steps <NUM>-<NUM>. In other embodiments, SAT system <NUM> may override, at step <NUM>, the corresponding package information to assign a different status and/or a reason for the unsuccessful delivery.

In some embodiments, blocks <NUM>, <NUM>, <NUM>, <NUM> may expand to comprise more reasons for non-delivery. Reasons for non-delivery <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> may also split to comprise more detailed sub-reasons. For example, reason <NUM> may be divided into sub-reasons based on the different resources that lacked, and reason <NUM> may be divided into sub-reasons based on the different types of delays caused by a customer. Furthermore, the first and second predetermined lengths of times at steps <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> may be different from one another to comprise six or more predetermined lengths of times based on the combination of status and reason for non-delivery. An alternative embodiment where one of more groups of the predetermined lengths of times have equal lengths of times is also within the scope of the present invention.

In some embodiments, once SAT system <NUM> has determined the packages to be reordered based on at least one or more of steps <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> as described above, such packages are processed through another exemplary process for reordering the packages and having them expedited through system <NUM>.

In some embodiments, having the packages expedited through the system may be based on a determined urgency code or a package identifier indicating that the package needs to be delivered more quickly. An urgency code may be a code that SAT system <NUM> assigns to a package, for example, by flagging the package, and may be based on one or more reasons for non-delivery (e.g., reasons <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM>). In some embodiments, SAT system <NUM> may have one or more urgency codes corresponding the one or more reasons for non-delivery. For example, a first urgency code may indicate a higher priority than a second urgency code (i.e., a package having a first urgency code should be delivered more quickly than a package having a second urgency code).

Additionally, in some embodiments, SAT system <NUM> may also indicate a package for reordering by updating the corresponding package information upon receipt of a request from an internal user (e.g., employee of an organization that owns, operates, or leases system <NUM>). Additionally, in some embodiments, once a package is flagged for reorder, SAT system <NUM> may determine the next available wave that another package (including, e.g., items not delivered during an earlier wave) can be delivered and automatically transmit instructions to deliver the package on the next available wave.

In some embodiments, the reordering process may comprise: identifying the items held by the package indicated for reordering in its corresponding package information (i.e., flagged package), identifying the order associated with the corresponding package identifier, canceling a portion of the identified order, creating and processing a new order with the identified items, updating the package information associated with the new order as high-priority, and delivering the corresponding package via a new delivery routes and/or sub-routes.

<FIG> depicts exemplary reordering process <NUM> that SAT system <NUM> may follow when it determines that a package has met the conditions for reorder, consistent with the disclosed embodiments.

<FIG> starts with step <NUM>. Once a package has been flagged for reorder (e.g., the package has met the conditions for reorder based on one or more of steps based on at least one or more of steps <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> as described above), the process may continue to step <NUM>.

In step <NUM>, SAT system <NUM> may cancel at least a portion of an order corresponding to the flagged package at step <NUM>. For example, an order may comprise a plurality of packages, including a first package containing a first group of items. At some point during the disclosed tracking process, the first package containing a first group of items may be flagged for reorder based on one or more reasons, as discussed above. The rest of the packages in the plurality of packages, however, may not be flagged for reorder, and it would not be necessary to cancel the said packages and delay their delivery. In this example, at step <NUM>, SAT system will only cancel the portion of the order corresponding to the flagged package (i.e., the first package containing a first group of items. Cancelling a portion of the order may include transmitting instructions to one or more devices in system <NUM> to cease delivery of the package, dispense with the package, or return the package to FC <NUM>, for example.

In step <NUM>, SAT system <NUM> may determine both the current time as well as a plurality of cutoff times associated with a plurality of upcoming delivery waves. These cutoff times may be associated with the package itself, and/or may be associated with one or more individual items contained in the package.

In step <NUM>, SAT system <NUM> may make a comparison between each cutoff time and the determined current time.

In step <NUM>, SAT system <NUM> may determine whether the cutoff time for a delivery wave has already passed. Based on the comparisons, SAT system <NUM> may determine a new scheduled delivery associated with a delivery at step <NUM>. In this example, this determination may be based on determining whether at step <NUM>. If the current time is not before the cutoff time (i.e., the cutoff time has not passed), then SAT system will not reschedule to the delivery wave associated with that cutoff time, as represented at step <NUM>, and will return to step <NUM> to make another comparison with a different cutoff time associated with a different wave.

In some embodiments, determining a new scheduled delivery in step <NUM> details may additionally or alternatively be based on determined urgency codes associated with the package, or whether the package has been flagged as needing to be shipped more quickly. For example, if a first package has been flagged for reorder, and a second package has been flagged for reorder and has a higher urgency code or has been flagged as needing to be shipped quicker, then SAT system <NUM> may prioritize the delivery of the second package. In some embodiments, process <NUM> may further include creating a new route optimized for delivering the new package when and if a new route is available.

Once a new delivery time associated with a delivery wave has been determined, SAT system <NUM> will transmit instructions to deliver the package based on the delivery time associated with the delivery wave. By automatically implementing this process upon determining that a package has been flagged for reorder, SAT system <NUM> may greatly reduce the number of lingering orders that have not been delivered yet, all the while minimizing its impact on operating expenses.

For ease of explanation without causing ambiguity, the reordering process will be described using an example, where an order comprises a first group of items, packaged together into a first package with a first package identifier and corresponding first package information, and a second group of items, packaged together into a second package with a second package identifier and corresponding second package information. For this example, SAT system <NUM> may determine that the first package was delivered to its intended recipient successfully but the second package was damaged. In this case, as described above with respect to step <NUM>, SAT system <NUM> may update the second package information to flag the second package identifier as meeting the condition for reorder along with other packages, if any, in the database that may need to be reordered as determined from one or more of package tracking processes <NUM>, <NUM>, <NUM>, and <NUM> described above.

Then, as part of the reordering process, SAT system <NUM> may proceed to identify the items in the second package (which, in this example, would be the second group of items defined above) based on the actual content of the package upon manual inspection and/or the order information and package information collected in the manner described above. Once the items and the order are identified, SAT system <NUM> may proceed to cancel the portion of the order corresponding to the items without affecting the other portions of the order that are not indicated for reorder and otherwise without issue. Then SAT system <NUM> may send a request to FO system <NUM> to create a new order comprising the second group of items. Effectively, a partial order comprising a single group of items, and thus packaged into a single package, is created and placed within system <NUM> to be processed along with the other packages.

In some embodiments, SAT system <NUM> may also indicate the corresponding new package information as "high-priority," which is communicated to other system elements (e.g., SOT system <NUM> and WMS <NUM>) and displayed as a notification to an internal user (e.g., employee of an organization that owns, operates, or leases system <NUM>) and/or a delivery worker 224A or 224B. One or more mobile devices 107A-107C of transportation system <NUM> and/or 119A-119C of a FC <NUM> may display the "high-priority" notification when scanning or reading the corresponding package identifier so that an internal user may prioritize processing the package before others.

In some embodiments, high-priority packages may be processed and delivered by a dedicated group of internal users within each system (e.g., a group of internal users in transportation system <NUM> or a group of internal users in WMS <NUM>) to ensure that the packages are packaged and delivered as quickly as possible regardless of how many other non-high-priority packages there may be. Still further, in some embodiments, SOT system <NUM> may create new delivery routes and/or sub-routes configured to optimize delivery of the high-priority packages.

In some situations, SAT system <NUM> may determine that the new packages cannot be delivered on or before the original PDD created at the time of the original order. In these cases, SAT system may send a request to FO system <NUM> for an updated PDD based on one or more factors as described above. The updated PDD may be used for internal order tracking or be disclosed to the intended recipient and/or the purchaser to apprise them of their order status.

In some embodiments, while the packages determined to be lost based on one or more of package tracking processes <NUM>, <NUM>, <NUM>, and <NUM> are processed through the reordering process as described above, a portion of internal users may be dedicated to locating the lost packages and forwarding them to a return staging zone (not pictured) located inside FC <NUM>. Alternatively or additionally, one or more previously lost packages may be discovered while internal users are performing their respective regular duties, at which point the internal user may also forward the package to the return staging zone.

It is preferable that the system <NUM> not attempt to redeliver the discovered package to the original intended recipient because the new high-priority package created through the reordering process above will then need to be cancelled and prevented from being delivered, which may slow down the system <NUM>. Additionally, in some embodiments, the packages determined to be damaged based on one or more of package tracking processes <NUM>, <NUM>, <NUM>, and <NUM> may also be forwarded to the return staging zone so that items therein may be retrieved. A subset of the items therein may still be in saleable condition.

In some embodiments, lost packages that have been located, damaged packages, and/or other packages cancelled before reaching the intended recipient due to their being flagged as meeting the condition for reorder are forwarded to the return staging zone for restocking. In such embodiments, SAT system <NUM> may update the package information corresponding to the forwarded packages as internal return, distinct from returned packages received from customers. The items inside such forwarded packages are relatively more likely to be in a sealed, saleable condition than other customer-initiated returns because no one has opened them as they were being processed through system <NUM>. As such, the items packaged therein may be forwarded and rerouted to picking zone <NUM> with minimal inspection, thereby saving the cost of performing a relatively more thorough inspection, shortening processing times, and saving the cost of duplicate orders.

While the present disclosure has been shown and described with reference to particular embodiments thereof, it will be understood that the present disclosure can be practiced, without modification, in other environments. The foregoing description has been presented for purposes of illustration. It is not exhaustive and is not limited to the precise forms or embodiments disclosed. Modifications and adaptations will be apparent to those skilled in the art from consideration of the specification and practice of the disclosed embodiments. Additionally, although aspects of the disclosed embodiments are described as being stored in memory, one skilled in the art will appreciate that these aspects can also be stored on other types of computer readable media, such as secondary storage devices, for example, hard disks or CD ROM, or other forms of RAM or ROM, USB media, DVD, Blu-ray, or other optical drive media.

Computer programs based on the written description and disclosed methods are within the skill of an experienced developer. Various programs or program modules can be created using any of the techniques known to one skilled in the art or can be designed in connection with existing software. For example, program sections or program modules can be designed in or by means of. Net Framework,. Net Compact Framework (and related languages, such as Visual Basic, C, etc.), Java, C++, Objective-C, HTML, HTML/AJAX combinations, XML, or HTML with included Java applets.

Claim 1:
A method for automated reshipment scheduling, comprising:
receiving, for a plurality of orders, electronic information comprising:
an order comprising a first group of items;
a first package identifier associated with a first package, the first package containing one or more items in the first group of items and being associated with a first recipient and a scheduled delivery time; and
a plurality of scan events associated with the first package identifier, each scan event comprising:
a scan time;
a scan location;
an event type; and
a delivery status;
wherein each scan event is received from one of a plurality of mobile devices upon scanning a package;
aggregating the received electronic information as event data;
converting the aggregated event data into a standardized format;
parsing the converted event data associated with the first package identifier by:
filtering the converted event data to isolate the event data associated with the first package identifier;
parsing the isolated event data to determine a temporal relationship;
determining a chronological sequence based on the isolated event data and the determined temporal relationship; and
determining the status of the first package based on the chronological sequence;
determining whether the first package was not delivered based on the parsed event data;
based on determining that the first package was not delivered:
flagging the first package identifier as meeting a first condition;
determining (<NUM>) a current time;
determining a plurality of cutoff times, each cutoff time in the plurality of cutoff times being associated with a delivery wave;
determining, based on a comparison between the plurality of cutoff times and the current time, a new scheduled delivery time associated with a delivery wave; and
transmitting (<NUM>) instructions to a mobile device to create a new order for a second package containing the one or more items contained in the first package;
storing the new order in a database; and
transmitting instructions to a mobile device, wherein the instructions cause the mobile device to display a notification indicating that the new order should be delivered during the delivery wave associated with the new scheduled delivery time.