CROSS-REFERENCE TO RELATED APPLICATION(S)

[0001] This application claims the benefit of priority to U.S. Provisional Patent Application No. 62/527,584 filed on June 30, 2017, the contents of which are hereby incorporated by reference.

TECHNICAL FIELD

[0002] The following relates to systems and methods for exposing and integrating multiple supply chain and delivery networks, in particular to optimize capacity utilizations.

DESCRIPTION OF THE RELATED ART

[0003] Currently retailers establish and utilize a supply chain that allows goods to be obtained from vendors such as manufacturers and factories, wholesalers, and distributors; distributed to warehouses within certain geographical areas; and populated in bricks and mortar retail stores or outlets or made available online. Customers wishing to purchase the goods from a retailer typically makes a purchase at the store, or through an online e- commerce site. For large items, a "last mile" delivery from the store or warehouse to the customer is normally required, e.g., for mattresses, appliances, furniture, etc. When shopping online, goods of all sizes requiring shipping, and this often occurs between a retailer's warehouse or storeroom and the customer's home, office, or other designated delivery location.

[0004] As illustrated in FIG. 1 , many vendors typically supply many different retailers, each having separate warehouses, physical storerooms, and even warehouses for carriers that make the last mile delivery. Because of this, most retailers establish their own supply chain network. While a dedicated supply chain network has an upside in providing increased control and flexibility within the network, there are normally significant costs associated with having too little or too much capacity in the network. These costs can translate to higher shipping costs to be paid by the customer or be absorbed by the retailer or vendor, or lost sales because delivery times are too long, to name a few.

[0005] It is an object of the following to address at least some of these inefficiencies in retail supply chain networks.

SUMMARY

[0006] The following provides a system and related methods, software platforms, and user interfaces that expose, abstract, and integrate multiple supply chain network elements from different parties into a single supply chain and delivery network. The single supply chain network enables the density of goods handled at any given edge in the network to be increased by making excess capacity available across what would normally be separate and distinct supply chain and delivery networks.

[0007] For example, the following system enables multiple retailers to utilize common consolidation and warehousing facilities, as well as common delivery and shipping networks/routes/trucks/personnel, to increase the efficiencies of all networks. In this way, shipping costs can be minimized to the benefit of consumers enabling retailers to compete on product offerings, services, experience, and usability rather than shipping charges. Moreover, exposing and providing access to capacities in other networks reduces the reliance of any given retailer on a particular transportation or shipping company, e.g., in the event of surges in demand, labor disruptions, etc.

[0008] A system is described, for integrating a plurality of supply chain networks, the system comprising interfaces to vendors, consolidation centers, warehouses, retail facilities, and last mile delivery companies to enable multiple retailers to use at least one facility or transportation vehicle from another supply chain or delivery network to utilize excess capacities.

[0009] In one aspect, there is provided a system for integrating a plurality of supply chain networks, the system comprising: a server device logically separated from the plurality of supply chain networks to provide a layer of abstraction for supply chain network nodes associated with the plurality of distinct supply chain networks to appear to consumers as a seamless delivery flow; and an interface with each of the supply chain network nodes, wherein the network nodes comprise at least one vendor node, at least one consolidation center, at least one retail node, at least one delivery node, and at least one customer user interface; wherein the server device is operable to determine excess capacities in the network nodes via the interfaces to consolidate at least one delivery operation across multiple retailers in generating delivery routes for customers provided to the customers via the at least one customer user interface.

[0010] In another aspect, there is provided a method for integrating a plurality of supply chain networks, the method comprising: providing a server device logically separated from the plurality of supply chain networks to create a layer of abstraction for supply chain network nodes associated with the plurality of distinct supply chain networks to appear to consumers as a seamless delivery flow; interfacing the server device with each of the supply chain network nodes, wherein the network nodes comprise at least one vendor node, at least one consolidation center, at least one retail node, at least one delivery node, and at least one customer user interface; determining excess capacities in the network nodes via the interfaces to consolidate at least one delivery operation across multiple retailers; and using the determined excess capacities in generating delivery routes for customers provided to the customers via the at least one customer user interface.

[0011] In yet another aspect, there is provided a computer readable medium comprising computer executable instructions for performing the method.

BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Embodiments will now be described with reference to the appended drawings wherein:

[0013] FIG. 1 is a schematic diagram illustrating the complexity of prior art retail supply chains;

[0014] FIG. 2 is a schematic diagram illustrating a simplified retail supply chain enabled by a supply chain management system as herein described;

[0015] FIG. 3 is a block diagram illustrating an implementation of a consolidated supply chain network facilitated by a supply chain management system interfaced with multiple retailer channels;

[0016] FIG. 4 is a network abstraction illustrating a centralized consolidation segment in a supply chain network having increased density at origin and destination areas;

[0017] FIG. 5 is a flow chart illustrating supply/delivery and reverse logistic channels within a consolidated supply chain network;

[0018] FIG. 6 is a flow chart illustrating operations performed in arranging a home delivery of an item purchased by a customer through a retailer interfaced with the supply chain management system;

[0019] FIG. 7 is a flow diagram illustrating the consolidation of a product catalogue;

[0020] FIG. 8 is a pictorial illustration of creation of the product catalogue shown in FIG.

7;

[0021] FIG. 9 is a flow chart illustrating a supply chain path for multiple goods delivered to a client;

[0022] FIG. 10 is a block diagram of a logical view of a mobile platform;

[0023] FIG. 1 1 is a block diagram of a logical view of a mobile web service; [0024] FIG. 12 is a block diagram of a logical view of a mobile client application;

[0025] FIG. 13 is a flow diagram illustrating a customer pick-up scenario;

[0026] FIG. 14 is a flow diagram illustrating an order cancellation workflow;

[0027] FIG. 15 is a flow diagram illustrating an order rescheduling workflow;

[0028] FIG. 16 is a flow diagram illustrating an order modification workflow for adding a new item to the order;

[0029] FIG. 17 is a flow diagram illustrating a customer pick-up process;

[0030] FIG. 18 is a flow diagram illustrating a staging and picking process;

[0031] FIG. 19 is a flow diagram illustrating a reverse logistics process;

[0032] FIG. 20 is a flow diagram illustrating a warehouse receiving process;

[0033] FIG. 21 is a flow diagram illustrating a cross-docking process;

[0034] FIG. 22 provides further detail for a cross-docking logistics example;

[0035] FIG. 23 is a flow diagram illustrating a logistics example without using cross- docking;

[0036] FIG. 24 is a screen shot of a customer user interface showing an order-in-transit scenario;

[0037] FIG. 25 is a screen shot of a customer user interface showing a missing item scenario;

[0038] FIG. 26 is a screen shot of a user interface for delivery personnel to enable selection of an album type;

[0039] FIG. 27 is a screen shot of a user interface for delivery personnel to enable an action item to be selected;

[0040] FIG. 28 is a screen shot of a user interface for enabling a comment to be added to a picture taken upon delivery of an item;

[0041] FIG. 29 is a screen shot of a user interface for enabling a delivery driver to enter mileage data;

[0042] FIG. 30 is a screen shot of a main menu user interface for a delivery driver application; [0043] FIG. 31 is a screen shot of a truck loading/unloading user interface for a delivery driver application; and

[0044] FIG. 32 is a screen shot of a delivery item inventory user interface for a delivery driver application.

DETAILED DESCRIPTION

[0045] Turning now to the figures, FIG. 2 illustrates a configuration that exposes, abstracts, and integrates multiple supply chain network elements from different parties into a single supply chain and delivery network. In this example, multiple vendors 10 ship or deliver goods to one or more consolidation centers 12 interfaced with or controlled by a centralized supply chain management (SCM) system 14. The SCM system 14 acts as a layer of abstraction for various disparate supply chain network elements (nodes) to allow for efficiencies to be built into individual retail channels. This is done by not only coordinating the movement and storage of goods within the consolidation facilities (typically referred to as the mid-mile of the network) separate from any given retail or vendor channel, but also coordinating the last-mile deliveries from the retailers (or consolidation centers) directly to the consumers 16. In this way, the SCM system 14 can increase the density of goods in any given edge of the network to enable retail stores 18 and warehouses 20 (retailers 21 generally) to provide reduced-cost deliveries to the consumers 16.

[0046] While coordinating the movement of goods between vendors 10 and retailers 21 , 20, the SCM system 14 can provide user interfaces within the delivery and shipping environment, the retail environment, and to the customer to allow the integrated supply chain and delivery flow to appear seamless to the customer. This is enabled using APIs and other interfaces between the SCM system 14 and the various entities in the supply and delivery chains to offload the coordination and integration of the process to the SCM system 14.

[0047] Turning now to FIG. 3, an implementation of the SCM system 14 is shown. The SCM system 14 is shown in this illustration as a layer, intermediary, back-end, or complementary service that is plugged into each of the stages of the supply and delivery network to blur the lines between inventory storage nodes. That is, by relying on the SCM system 14, any consolidation center, warehouse, etc. can store goods until they are ready to be placed into a last mile shipment, separate from any strict association with a particular retail channel or distribution entity. As shown in FIG. 3, the vendors 10 (typically considered the first mile), are interfaced with the SCM system 14 to have goods required by a particular retailer 21 (in this example highlighted retail store 18a) shipped to a particular consolidation center 12a. [0048] The mid mile portion of the supply chain and delivery network is therefore also plugged into the SCM system 14 such that dedicated consolidation centers 12 are not necessarily required for each retailer's 21 channel. This not only allows new retailers 21 to emerge without the costly up-front costs of establishing consolidation facilities, but also existing retailers 21 to maximize the usage of their existing facilities, which may already be a sunk cost. This is illustrated in FIG. 3 as a sub-network of consolidation facilities (12a, 12b, 12c in this example) that can be integrated from various sources, including SCM system- managed consolidation centers 12. Based on data acquired over time in a logistics database 32, the SCM system 14 can determine optimal numbers and locations for such consolidation centers 12 to allow, for example, collaborations or eliminations to emerge. The logistics database 32 can also be leveraged by 3 ^rd parties, e.g. via 3 ^rd party intelligence requests 34. This allows organizations such as retailers, investors, government planners, shipping companies, etc. to use the SCM system's datasets to optimize geographic placement of assets, fleet sizes, personnel deployment, etc.

[0049] Several retailers 21 or "retail channels" are shown operating in parallel in FIG. 3. Each retailer 21 may include its own network of bricks and mortar retail stores 18, regional warehouses 20, online e-commerce sites, etc. In addition to optimizing the flow of goods in the first and mid mile portions, it can be appreciated that the SCM system 14 can also enable retailers to eliminate redundancies in warehousing, e.g., if consolidation centers provide sufficient storage and proximity to the retail storerooms or can service direct-to- customer delivers through online purchases. In other words, the SCM system 14 can also optimize intra-channel flow of goods for any particular retailer 21 , which again may include storage and shipment of goods for multiple retailers 21 at the same time.

[0050] The SCM system 14 also integrates and coordinates the last mile portion of the supply and delivery network, by identifying a particular delivery truck 24 (24a in this example) for the goods that will flow from the particular consolidation center 12a and the retail store 18a. Further detail regarding the coordination of the last mile delivery portion can be found in co-pending U.S. Patent Application No. 15,000,899 filed on January 19, 2016 and published as U.S. 2016/0210591 , the contents of which are incorporated herein by reference.

[0051] The coordination and execution of the flow of goods can be transparent to the customer 16 by having the SCM system 14 integrated into the various retail portals provided to the customer 16 when making a purchase, arranging delivery, and tracking and completing a shipment. For example, as shown in FIG. 3, upon purchasing an item that requires or is desired to include shipping, the customer 16 is presented with an option to select a delivery data and possible one or more delivery time windows. By being integrated with the upstream portions of the supply and delivery network, the SCM system 14 can provide the retail portal with data that allows such delivery dates to be determined. It can be appreciated that various constraints on delivery dates may be imposed depending on the location of the customer, the type of goods being purchased, etc. In any event, through the integration shown in FIG. 3, the retailer 21 and/or the SCM 14 can provide the customer 16 with options that are consistent with the efficiencies built into the shipment and delivery legs of the network.

[0052] The retailer 21 after receiving the delivery date request 38 can have the SCM system 14 coordinate the flow of goods to either the store or outlet 18 for pick-up, or direct to the customer 16 using a last mile delivery. The SCM system 14 begins with the selected delivery date to back track within the system to have the vendor 10 ship the good(s) at a particular prior date which takes into account available capacities, routes and travel times, holidays, availability from manufacturers, and whether and how many consolidation and warehousing steps are required to fit within the particular retailer's channel. By having the retailer 21 expose their supply chain network to the SCM system 14, the SCM system 14 can find the most effective way to transport the goods from, for example, a vendor to a customer delivery or pick-up location. Similar logistics are planned at this time to coordinate last mile deliveries by exposing driver fleets that are able to make the delivery.

[0053] FIG. 4 illustrates a network diagram with increased density at the origin and destination nodes based on a coordinated consolidation node in between. This allows goods at various origin points to more efficiently channel towards shared consolidation locations, providing more efficient deployment into higher density delivery routes at the destination end. For example, a single transportation vehicle could be arranged to ship goods from multiple vendors to the same consolidation center 12. Then, deliveries from retailers 21 that require multiple goods from similar but different vendors 10 can utilize the same delivery trucks to bring down the overall cost of shipping to the customers 16.

[0054] FIG. 5 illustrates the abstracted flow of goods from line-haul to consolidation to storage/warehousing to last mile delivery to customers in a supply/delivery direction, as well as in the reverse direction at any one of these edges by way of reverse logistics. The SCM system 14 can be used to coordinate each of these legs or edges of the network transparently to the customer 16 and even the retailer 21 to provide a seamless supply chain without requiring dedicated facilities at all or any of the nodes. [0055] The supply and delivery network can itself also include multiple layers. For example, in business to business (B2B) interactions, the following layers are facilitated and coordinated:

[0056] 1) Vendor - Consolidation center

[0057] 2) Distribution center - Retail stores

[0058] 3) Pick-up store ^Warehouse or Consolidation center

[0059] 4) Consolidation center - Home delivery

[0060] 5) Reverse Logistics for 1) to 4)

[0061] In business to consumer (B2C) interactions, the following layers are facilitated and coordinated:

[0062] 1) Consolidation/Warehouse ^Consumer

[0063] 2) Consumer - Warehouse

[0064] 3) Retail store - Consumer

[0065] 4) Vendor - Consumer

[0066] 5) Customer pick up

[0067] 6) Reverse Logistics, in particular for 1), 2), and 4).

[0068] In one example, reverse logistics can be applied to facilitate the flow of goods from the consumer or store (e.g. returns) back to consolidation centers 12 or warehouses 20 to enable those goods to be picked up in another delivery channel or transaction. This may allow for tighter delivery dates, particularly when the lead time to obtain goods from the vendor 10 is long, but goods are able to flow in reverse within the abstracted consolidation and shipping portions of the network.

[0069] FIG. 6 is a flow diagram illustrating the coordination of shipping and delivery of an item purchased by a customer 16. At step 50, the SCM system 14 indicates to the retailer 21 or its online portal available delivery days. It can be appreciated that step 50 may be optional if the retailer 21 instead controls the delivery days and only requires the SCM system 14 to coordinate thereafter. However, if data is available to the SCM system 14, it can provide any constraints around how quickly an item can be delivered, by having access to the various legs of the network. At step 52, the retailer 21 provides an interface to the customer 16 with a delivery option. For example, when purchasing a large item such as an appliance or furniture, many customers require delivery using a last mile delivery truck. Through coordination with the SCM system 14, the retailer 21 can provide this option to allow the customer 16 to select a delivery date for the order at step 54. Based on this selection, the retailer 21 notifies the SCM system 14 at step 56 of the selected delivery date, such that the SCM 14 can work backwards to ensure that the goods are either delivered from the vendor 10 to the appropriate consolidation center 12 or warehouse 20 or moved within the mid mile portion to efficiently transfer into the last mile leg of the delivery.

[0070] At this point, the customer 16 has completed the purchase and delivery arrangement from his/her perspective, and the retailer 21 coordinates with the SCM system 14 to facilitate the flow of the goods associated with the order. For example, at step 58 the SCM system 14 can arrange a vendor transfer to a consolidation center 12 and a subsequent transfer from the consolidation center 12 to a warehouse 20 or retail store 18 at step 60. The SCM system 14 can also arrange the last mile delivery to the customer 16 at step 62, that accounts for any of the other arrangements, including timing, availability, holidays, etc. The retailer 21 can also confirm the delivery date to the customer 16 at step 64, for example, if any of the arrangements in steps 58-62 require adjustment of the delivery date, or to simply provide a tracking number, delivery company info, driver info, etc. Since some or all of the steps taken by the SCM system 14 may occur after the customer 16 makes the purchase and selects the delivery date, step 64 may be required one or more times after the retail transaction occurs. For example, the customer 16 may perform step 54 at a retail store 21 after viewing some furniture, and have a follow-up email sent that confirms the delivery details sometime after leaving the retail store. In the interim, the SCM system 14 coordinates and facilitates the most efficient supply and delivery chain transparently or substantially transparently to the customer 16.

[0071] In order to implement a process such as that shown in FIG. 6, the SCM system 14 can have a central analysis, integration, and coordination sub-system 30 that uses APIs into the various supply chain elements (including those shown by way of example in FIG. 6). In addition to coordinating the flow of goods, the sub-system 30 can also be used to collect and analyze data to continually improve and refine the algorithms used to plan routes, determine optimal consolidation centers 12 and locations, etc.

[0072] FIG. 7 illustrates a centralized catalog wherein vendors 10, distributors, and manufacturers can provide and maintain an electronic catalog of products, with SKUs, definitions, descriptions, quantities, multimedia, etc. This content can be published to retailers 21 so that it is available in their ERP systems connected to the point of sale and e- commerce sites. This allows the retailers 21 to tap into data coordinated through the SCM system 14.

[0073] FIG. 8 illustrates how data is flowing into such a catalog, namely by EDI, API, batch files or simply via web interfaces, and pushed to the catalog so that the retailer 21 will have the information in real-time so that the goods are available for sale through the retailer 21 at that time. Once the retailer 21 makes a sale, the SCM system 14 can provide the transit time and delivery dates so that the customer can complete the transaction and schedule its delivery at the time of sale.

[0074] FIGS. 9 through 32 illustrate various scenarios and workflows that enable the SCM system 14 to interact with the retail channels, delivery channels, and the customers 16.

[0075] FIG. 9 illustrates a generic path along which goods in a customer order may follow from manufacturers to the final customer or client 16. During this path, various resources are involved, including manufacturing staff (first mile), distribution center staff (first mile), delivery hub staff (first and last mile), line-haul drivers (first mile), delivery drivers (last mile), and customer (initial order and last mile). Each of these sets of resources has preferences and constraints that are interpreted by the SCM system 14. In the line-haul segments of the network, goods are brought from the first mile hub to the last mile hub. Constraints that can affect the shipping dates include: shipping schedule at the origin hub, receiving schedule at the destination hub, holidays, transit time from origin to destination. In the first mile segment, the same constraints typically apply, but additionally it should be considered that the first mile is where the goods are assumed to physically be at the beginning of the process. The initial hub also has an extra constraint, namely cut-off time. For instance any order that is imported after the cut-off time would have an extra day added to the earliest shipping date as it is assumed that they would be unable to start the delivery process on the same day.

[0076] The last mile segment is not hub-to-hub, but from the last mile hub to the end customer 16. Some constraints include the final delivery hub schedule, specific buffer times from the hub (e.g. to provide extra time allocated to the route), delivery drivers' schedules, opened trucks for online reservation (i.e. what and how many trucks are available), offerings of the retailer/carrier inside the customer area (postal code/zip code), reachability of the customer location (e.g. remote locations).

[0077] With these constraints in mind, the SCM system 14 can determine which dates are available to the customer 14, such that where these constraints are not respected, certain corresponding dates are shown as unavailable to that customer 16 for that order. [0078] The manufacturer segment of the supply chain can also be abstracted in the same way as a distribution center or warehouse as it can be treated as a hub through which merchandise flows. APIs can be provided to the manufacturers to similarly coordinate orders, shipments, and movement through the various hubs.

[0079] The SCM system 14 can provide any suitable computing architecture to integrate and interface with the various entities in the abstracted and integrated supply chain and delivery network. FIG. 10 provides a logical view of an example of a mobile platform that can be implemented by the SCM system 14. In this logical view, a presentation layer is provided to interface with external systems, particularly client applications. A service layer provides various service interfaces and messages, a business layer provides business services, and a data layer operates data access components to interface with the data sources.

[0080] FIG. 1 1 provides a logical view of an example of a mobile web service. A service layer distributes messages to the controllers, which utilize one or more business services. The data layer in this service includes data access components and service agents. A cross-cutting component provides security, operational management, and communication elements.

[0081] FIG. 12 provides a logical view of an example of a mobile client application. The presentation layer includes various Ul components supported by the presentation logic components to provide the user experience. The business layer includes business entities to ensure that data is handled correctly. The data layer has access to local data storage and is responsible for data synchronization with the web service in this example configuration.

[0082] FIG. 13 provides an example customer pick-up flowchart that illustrates various operations between the SCM system 14 (illustrated as ClearD) and the backend of a retail channel, such as a retail store that arranges a delivery service for large items such as appliances or furniture. In this scenario, the customer 16 selects a pick-up from a particular retail store 18. The retailer 21 back-end system identifies the location and communicates with the SCM system 14 to populate a calendar with the available pick-up dates for that location. The customer 16 may then selected a desired one of the available dates and cause the retailer back-end to generate a customer pick up order for the destination of the pick-up. The SCM system 14 then coordinates the shipment of the goods to that location and provides tracking information to the retailer backend. FIG. 13 also shows coordination between the SCM system 14 and the retailer backend to handle error messages if necessary for errors in an order. It can be seen that the SCM system 14 is relied upon by the retailer 21 to both present the delivery options to the customer 16 and to coordinate the actual flow of the goods to the pick-up location.

[0083] FIGS. 14 to 16 illustrate additional scenarios carried out by customers 16 with respect to an order to further illustrate the coordination between the SCM system 14 and the backend systems of the retailer 21. In FIG. 14, an order cancellation is shown, wherein a customer 16 cancels an order on a retailer website or by phone. The customer's request is sent to the retailer's backend to cancel the actual order, which triggers a function call to send order information to the SCM system 14 in order to have the SCM system 14 cancel the order at its end. The SCM system 14 then sends a confirmation of the cancellation back to the retailer 21 to confirm that the items will not be shipped as originally planned.

[0084] FIG. 15 provides a scenario in which a customer reschedules an order, e.g. online or by phone. Here, the customer's request is sent to the retailer's backend to reschedule the order, which triggers a functional call to the SCM system 14 to provide the order information to the SCM system 14. The SCM system 14 then re-determines available dates and sends that information back to the retailer backend to allow the retailer 21 to present a new availability calendar in a user interface to the customer 16. Upon selection of a desired delivery date, the retailer backend provides new order information to the SCM system 14 to coordinate any new shipping and delivery arrangements and providing further coordination with the retailer backend as required.

[0085] FIG. 16 provides an example of a scenario wherein a customer 16 is requesting to add an item to an existing order, made via the retailer. The retailer backend system would determine first if the order has already shipped. If not, order information is provided to the SCM system 14 to determine available dates and coordinate a new delivery date if necessary as shown in FIG. 15 and described above. If the order has already shipped, the new item can be merged to the existing order or a new order can be created, depending on the preferences and constraints of the retailer backend system. In a merge, the old order can be sent to the SCM system 14 to initiate a cancellation of that order which is confirmed to the backend system of the retailer 21 and new order information created. In either branch, the new order information is passed back to the SCM system 14 to determine available dates and schedule the new order arrangements as described above.

[0086] Turning now to FIG. 17, another example of a customer pick-up workflow is shown to illustrate the coordination between the retail channel and the SCM system 14. The customer 16 in this example selects one or more items to be picked up at a store and the pick-up location. This information is fed to the SCM system 14 via an API. The customer 16 then selects a day/time for the pickup which is based on information provided to the customer via the SCM system 14. The customer also makes the purchase which is communicated to the SCM system 14 via an API. The SCM system 14 meanwhile checks the delivery information and determines the possible delivery date to deliver the order at the selected pickup location, which dictates the available days/times for the customer 16 to select. The SCM system 14 also updates its database with the new order. The order generates a barcode for each item in the order at the warehouse 20 and the items are cross- docked and shipped from the warehouse 20. The barcode information and shipping status are communicated to the SCM system 14 via API, PDA, portal, etc. This allows the SCM system 14 to update its information during the supply chain progress.

[0087] The warehouse 20 will either ship to the location or ship to another warehouse 20 in this example. If shipment to another warehouse 20 occurs, the items are received and inspected, cross-docked, and sent out to the next warehouse 20 if applicable, or the pick-up location. The final destination receives the order and inspects the item(s). As illustrated in FIG. 17, these various steps are communicated to the SCM system 14 to allow the SCM system 14 to update its information, and enables further coordination, e.g., if the SCM 14 is involved in arranging delivery trucks between warehouses 20, the use of other retailers' consolidation centers 12 or warehouses 20, etc. The SCM system 14 is also able to update tracking information, e.g., to notify the customer 16 that the order has arrived and is ready for pick-up.

[0088] FIG. 18 shows a staging and picking workflow in which the SCM 14 generates a picking list for a truck at a warehouse 20 and sends the list to the warehouse 20. The warehouse 20 receives the list of items and goes to the location of the first item to scan that item. If the item is not in a convenient place, an inventory control system is notified. The scanned item is also communicated back to the SCM system 14 to enable it to display item details. The warehouse 20, if the item is placed correctly, moves the item to the appropriate truck door and scans the item and truck to confirm the new location, which is sent to the SCM system 14 for updating. This repeats until all of the items in the order from that warehouse 20 are placed near the shipping truck. The items are then loaded and scanned again to confirm loading, which is communicated back to the SCM system 14. As shown in FIG. 18, load planning software can be used by the SCM system 14 to optimize the planning for a particular warehouse 20, e.g., by having floorplans, inventory lists, etc. When the items are loaded in the truck, controls can be implemented to ensure that the items are loads first in/last out, consistent with the planning and picking list to optimize the picking and staging. [0089] FIG. 19 illustrates a reverse logistics procedure generally, wherein a truck arrives at a warehouse 20 returning items along a reverse logistics path. The item is received and moved to a specific location and scanned. The warehouse 20 and location within the warehouse 20 are communicated to the SCM system 14 to enable coordination of that item with respect to a customer return, inventory reshuffling, recall or warranty, etc. FIG. 20 illustrates an item being received at a warehouse 20, inspected, and moved. This process involves communicating the steps back to the SCM system 14 and may be applied when, for example, items are transported between different warehouses 20. Similar operations can be applied at any hub that is utilized in the supply chain and delivery network.

[0090] FIG. 21 provides further details in respect of an example cross-docking scenario. Cross-docking is a practice in logistics of unloading materials from an incoming semi-trailer truck or railroad car and loading these materials directly into outbound trucks, trailers, or rail cars, with little or no storage in between. In this example, routes are created for the shipping of various items, with a database updated with routes sequencing and picking time information. In a second step, the cross-docking occurs at a facility such as a warehouse 20 or consolidation center 12. At reception, multiple trucks are unloaded at the facility and the unloaded items are checked against inventory or order lists to confirm reception of the expected goods. The expected items are either found or not found. A mobile application for cross-docking can be used as illustrated to determine the next operation(s), such as movement to particular lanes in the warehouse 20 and to update the locations where they are placed. With this information fed back to the SCM system 14, the coordination of last mile trucks 24 is enabled and optimized based on the routes, number of drivers, etc. The SCM system 14 can provide a mobile application to drivers as shown in FIG. 21 to enable coordination between the shipment hubs and last mile deliveries.

[0091] FIG. 22 provides a logistics mapping for a cross-docking example that uses multiple warehouses 20. In this example, two vendors 10 (Vendor 1 and Vendor 2) ship goods to either a final last mile shipment phase or to a distribution warehouse 20 based on a postal code (i.e. proximity, remoteness, etc.). Here a main warehouse 20 receives inbound deliveries from both vendors 10 and based on the associated postal codes for the deliveries redirects goods to a satellite warehouse 20, a last mile warehouse 20, or the final shipment to the customer 16. It can be seen that within each warehouse 20, including the last mile warehouse 20, the goods can be redirected to different delivery routes (or other warehouses 20) based on location. This allows the last mile portion of the supply chain to be optimized. It can be appreciated that the SCM system 14 can also optimize the shipments and other movements prior to the last mile segments as discussed above (e.g. to have the same warehouse 20 service multiple retailers 21).

[0092] FIG. 23 provides an example of the various logistics that need to be coordinated without cross-docking. Here it can be seen that for each vendor 10, shipments may be required within multiple retailer channels, but can use the same distribution center 12 and retailer and carrier warehouses 20. Whereas the complicated paths could lead to inefficiencies when each retailer has its own separate supply chain and delivery network, the SCM system 14 allows efficiencies to be built in by abstracting across the mid mile locations.

[0093] As indicated above, the SCM system 14 can provide or integrate with user interfaces that are used by the customers 16 and/or the shippers/drivers. In FIG. 24, a customer user interface is shown in which an order is in transit. The SCM system 14 can provide such information through a retailer's online portal using APIs, and allows the customer 16 to benefit from the integration of the entire supply and delivery chain.

[0094] FIG. 25 provides an example of the same user interface during a missing item scenario wherein the customer 16 is provided with a rescheduling calendar to provide seamless reorganization of an order to account for missing portions of an order. Similar user interfaces can also indicate when the order has been shipped, provide pictures, damage reports, etc. as well as other status points within the process.

[0095] FIGS. 26-32 provide screen shots of example user interfaces that can be provided by the mobile application service to delivery or shipping. In FIG. 26 a tasks menu is shown that allows the driver to select whether there is property damage, item damage, whether or not anyone is home, or other events associated with the delivery or shipment. A delivery action menu is shown in FIG. 27 wherein the driver can select whether the task is completed or should be canceled. FIG. 28 illustrates a user interface in which comments can be added to a picture taken in relation to the delivery or shipment. FIG. 29 provides a user interface to enable a driver to log the date, starting and ending mileage. FIG. 30 provides a menu interface for KM management, items management and execute route. FIG.

31 provides a user interface for recording and capturing loading/unloading tasks, and FIG.

32 a user interface for loading items onto a truck from a warehouse 20 including scanning barcodes therefor.

[0096] For simplicity and clarity of illustration, where considered appropriate, reference numerals may be repeated among the figures to indicate corresponding or analogous elements. In addition, numerous specific details are set forth in order to provide a thorough understanding of the examples described herein. However, it will be understood by those of ordinary skill in the art that the examples described herein may be practiced without these specific details. In other instances, well-known methods, procedures and components have not been described in detail so as not to obscure the examples described herein. Also, the description is not to be considered as limiting the scope of the examples described herein.

[0097] It will be appreciated that the examples and corresponding diagrams used herein are for illustrative purposes only. Different configurations and terminology can be used without departing from the principles expressed herein. For instance, components and modules can be added, deleted, modified, or arranged with differing connections without departing from these principles.

[0098] It will also be appreciated that any module or component exemplified herein that executes instructions may include or otherwise have access to computer readable media such as storage media, computer storage media, or data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, or tape. Computer storage media may include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data. Examples of computer storage media include RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by an application, module, or both. Any such computer storage media may be part of the SCM system 14, any component of or related thereto, etc., or accessible or connectable thereto. Any application or module herein described may be implemented using computer readable/executable instructions that may be stored or otherwise held by such computer readable media.

[0099] The steps or operations in the flow charts and diagrams described herein are just for example. There may be many variations to these steps or operations without departing from the principles discussed above. For instance, the steps may be performed in a differing order, or steps may be added, deleted, or modified.

[00100] Although the above principles have been described with reference to certain specific examples, various modifications thereof will be apparent to those skilled in the art as outlined in the appended claims.