The present disclosure relates to methods and systems for commerce order fulfillment, such as methods and systems for fulfilling and shipping e-commerce orders. Specifically, the present disclosure relates to order fulfillment using a common order method and/or common order pack lists, and to systems and methods related to packaging and shipping recommendations for orders such as e-commerce orders.
Several methods and processes exist for commercial businesses performing e-commerce operations related to customer order fulfillment and shipment preparation, which can include preparing a pick and/or pack list to pick and manage the items shipped, choosing packaging, shipping carrier and rate, and printing shipping labels. Pick lists typically identify all of the items within all of the orders that need to be pulled to fulfill the orders. Pack lists typically identify all of the orders and the items included within each order. Pick or pack lists also typically include details such as order number, quantity of each item(s), and ship-to address. Customer orders are often organized by order number on a pack list, with order numbers generally sequential based on timing of the receipt of that order (e.g., Order No. 1, Order No. 2, Order No. 3, etc.).
Businesses may use computer or software applications to manually create their pick and/or pack lists and shipping labels, such as word processors or special-purpose shipping label applications. Using a word processor to prepare pick and/or pack lists and shipping labels is an error prone process, as relevant information (e.g., each destination shipping address) is entered manually. In addition, the word processor may not be configured or otherwise capable of preparing bar codes or other machine-readable indicia required or preferred by some carrier services. Manually-created pick and/or pack lists leave room for further user error, such as typographical errors in the ship-to address, item ordered, or quantity ordered.
Businesses typically pick and pack customer orders for shipping based on a pack list. Users may, in some instances, choose not to prepare the orders sequentially based on order number. Users typically have discretion on which packaging is used for each order, and then have to confirm the contents of each package individually with the order details on the pack list. The user then generates individual shipping labels based on the weight and dimensions of each order package.
Manually ensuring consistency of the data between the shipping label, pack list, and the contents of the actual package results in wrong orders or packages shipped out, additional costs to the commercial business, and unhappy customers. Manually inputting weight and dimension data during shipping label generation may result in incorrect data entry, in turn resulting in additional shipping fees, surcharges, and/or costs. Additionally, to create a shipping label, a user has to manually shop for shipping rates across different carriers and choose which rate to use based on the package, or simply proceed with a single carrier regardless of whether that carrier has the best rate available.
There is also the method of batch (mass) selection for packaging and shipping customer orders where package dimensions and weight are assumed as one standard size and one negotiated rate is used through one shipping service. Using this method, businesses will pay a special handling fee for any oversized or incorrect shipping fees. This can result in approximately 40% more in shipping costs.
Labels are generally unsorted, but they might be printed in the same order as the order numbers on the pack list. Users then have to physically match the label to the orders on the list, and then match the orders on the list to the packages before affixing the label to the corresponding packages. Then, the users need to sort the packages with shipping labels affixed by shipping carriers, which takes additional time and increases the chances of error.
The prior art manual processing and validation greatly extends fulfillment times for customer orders, introduces a multitude of opportunities for error, and increases overall costs.
The present disclosure provides various embodiments of methods and systems for a common order method of order fulfillment, and for generation of a common order pack list. The present disclosure also provides methods and systems for optimized packing and shipping recommendations for businesses fulfilling orders such as e-commerce orders.
One embodiment of a method for packing commerce orders for fulfillment according to the present disclosure includes receiving an order, grouping the order with other pending orders with the same item(s) and quantities, and assigning each group to a common order number. The method further includes creating a common order pack list organized by common order number. Additional possible steps may include gathering items for the pending orders using the pack list, and/or packing the items using the common order pack list.
One embodiment of a method for optimizing packaging and shipping for commerce orders for fulfillment according to the present disclosure includes inputting information about available packaging, inputting information about items available for ordering, receiving at least one order for at least one item, and performing at least one calculation involving the volume and/or dimensions of the at least one item. Additional possible steps may include inputting the dimensions of available packaging and the amount of packaging in stock, and/or inputting the dimensions of items available for ordering and the number of items in stock.
One embodiment of a system for fulfilling commerce orders according to the present disclosure includes at least one marketplace where customers can place orders for at least one item, and one or more hardware computing devices having a processor and memory to receive those orders from the marketplaces. The system further includes software that generates common order pack lists organized by common order number and containing optimized packaging and shipping recommendations for the common order numbers.
A better understanding of the features and advantages of the present embodiments will be obtained by reference to the following detailed description of the disclosure and accompanying drawings which set forth illustrative embodiments in which the principles of the disclosure are utilized.
Embodiments of the present disclosure provide improved methods, techniques, and processes, often computer-based, for fulfilling customer orders (e.g., e-commerce orders), such as automated generation of (1) pack lists organized by “common order” number, (2) optimized packing, packaging, and shipping carrier recommendations, and (3) shipping labels. Embodiments of the present disclosure also greatly reduce order fulfillment times and costs for businesses by providing pre-validated packaging selection and shipping rate shopping. Some embodiments of the systems and methods described herein can result in the generation of labels (e.g. pre-paid shipping labels) with common order numbers.
The present disclosure will now set forth detailed descriptions of various embodiments. Many of the methods described below may be implemented with computer software and/or hardware, such as computers, processors, smart devices (e.g. smart phones), tablets, memory, processors, computer readable medium, computer executable instructions, algorithms, and/or similar. The methods herein can be performed at least in part using software, software as a service (SAAS) technology, platform as a service (PARS) technology, infrastructure as a service (IAAS) technology, and/or other technologies as would be understood by one of skill in the art.
In the description that follows, numerous details are set forth in order to provide a thorough understanding of the disclosure. It will be appreciated by those skilled in the art that variations of these specific details are possible while still achieving the results of the disclosure. Well-known elements and processing steps are generally not described in detail in order to avoid unnecessarily obscuring the description of the disclosure.
Throughout this description, the preferred embodiments and examples illustrated should be considered as exemplars, rather than as limitations on the present disclosure. As used herein, the terms “invention,” “disclosure,” “method,” “present invention,” “present disclosure,” “present method,” or similar terms refer to any one of the embodiments of the disclosure described herein, and any equivalents. Furthermore, reference to various feature(s) of the “invention,” “disclosure,” “method,” “present invention,” “present disclosure,” “present method,” or similar terms throughout this document does not mean that all claimed embodiments or methods must include the referenced feature(s).
Although the terms first, second, etc. may be used herein to describe various elements or components, these elements or components should not be limited by these terms. These terms are only used to distinguish one element or component from another element or component. Thus, a first element or component discussed below could be termed a second element or component without departing from the teachings of the present disclosure. As used herein, the term “and/or” includes any and all combinations of one or more of the associated list items.
The steps described in the below methods may be performed in different orders than those specifically described, as would be understood by one of skill in the art. Some steps may be performed simultaneously and/or continuously, as would be understood by one of skill in the art.
The terminology used herein is for describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes,” “including,” and similar terms, when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
Embodiments of the disclosure are described herein with reference to flowcharts are schematic illustrations of embodiments of the disclosure. As such, the arrangements of components or steps can be different, and variations are expected. Additionally, components and steps shown as a singular component or step may include multiple components or substeps, while aspects shown as multiple components or steps may be a singular component or performed as a singular step. Embodiments of the disclosure should not be construed as limited to the particular arrangements, components, or steps.
The common order pack list can created manually or can be computer-generated. The automated generation of the common order pack list can be triggered manually by the user, or generated otherwise. The common order pack list, in some embodiments, may be generated automatically at certain time intervals. The common order pack list can, in some embodiments, also be under constantly and/or automatically updated, with a user able to take a “snapshots” of the current common order pack list at various times. Many different embodiments are possible.
While these steps are shown in
Referring back to
In step 404, information can be input (e.g., manually by a user, or otherwise) about each item that is available to be shipped, such as the item's dimensions and weight of the item. If the item is to be shipped in its item packaging (e.g., the item comes in the manufacturer's box, and the entire manufacturer's box is to be placed in the shipping packaging), then information regarding the item packaging can be input. In some embodiments, the item can be marked as being delicate or fragile, which can be used in determining the type of item packaging to be used and may result in a different packaging being recommended than for a non-delicate item.
When the business receives an order (e.g., e-commerce order), information from that order, which can include the item purchased and the quantity of each item purchased, can be used to generate an optimized packaging and shipping recommendation. This recommendation generation can in some embodiments be performed by hardware and/or software as previously described. In step 408, a search of a cache (which can be maintained from previous orders) can be performed to see if the exact same item or combination of items has previously been ordered; if so, then the packaging used for the previous order can be recommended for the current order. If the recommended packaging is not available (e.g., because it is out of stock), then another search of the cache can be performed for a secondary recommendation based on previously-used packaging recommendations.
If the cache search does not result in a match or no stock remains of the packaging recommendation(s) from the cache (or in embodiments not utilizing a cache search), then in step 410 a packaging test to calculate a packaging recommendation can be performed. It is understood that step 410 can be performed even if no cache test is performed, and the cache test can be completely omitted. The total volume and/or dimensions of the items in the order can be calculated, such as by using space optimization software or algorithms in order to calculate the packing organization resulting in the lowest total volume. Other parameters can also be used in this calculation; e.g., if the order needs to fit in packaging with an overall depth of 1″ or less, then this fact can be used as an input in the calculation such that the result will meet this criterion. The output optimized volume can then be compared to the types of packaging available to determine which types of packaging are suitable for the order. Then, the dimensions of the optimized volume can be compared to the available packaging to determine which packaging meets both the volume and dimension requirements. It is understood that the volume and dimension tests can be performed in any order (and/or simultaneously), or in some embodiments, only one of them might be used.
If a package fails either step, then the package can be excluded from the recommendation. These steps are run on the packaging available until a package does not fail both steps in some embodiments, and in some embodiments are run on all available packaging. If all packages available to the business fail the test, the order can be placed on hold to be manually addressed by a user (step 450).
In step 412, a virtual three-dimensional (3D) rendering tool can then be used by the algorithm to determine how the item(s) will fit into the packaging that has passed the above test. The rendering tool can be used only on the most optimal package as determined by the dimensional/volume test(s), or can be performed on all packages that passed the dimensional/volume test(s). This determination is critical for e-commerce orders with multiple items. The rendering tool can be operated manually by a user, or automatically, such as by using algorithms or artificial intelligence. If the item(s) ordered will not fit in the packaging, then that package will be excluded. The results of the fit test can be used when actually packing the ordered items, to ensure that they are packed in the manner recommended by the fit test.
Since some packaging (e.g., mailers) are commonly measured with two dimensions instead of three dimensions, in one embodiment, the method can generate and/or utilize a third dimension for the packaging, effectively making a three-dimensional object. Use of the third dimension allows the volume, dimension, and fit tests shown in steps 410 and 412 to be performed accurately.
In one embodiment, the packaging that is ultimately recommended to the user to use in fulfilling an e-commerce order (step 414) is one that (1) has passed the two-step packaging test (the dimension portion can in certain embodiments be omitted for multi-item orders, or can be included), (2) has passed the 3D rendering tool calculations (which can be omitted for single-item orders in certain embodiments, or can be included), and (3) will have the least amount of empty space in the packaging after the item(s) are placed in it. In another embodiment, the third criterion is determining the cheapest type of packaging available for the item(s). In another embodiment, these two criteria can be combined with one another (e.g., the cheapest packaging that has under a certain amount of empty space, or the packaging that has the least amount of empty space and also costs under a certain amount to ship). Many different embodiments are possible.
Optionally, in step 416, after recommended packaging has been determined, a search can be performed (manually or using an internet or other electronic search tool) to determine the cheapest carrier for the recommended packaging. Additional criteria, such as maximum shipping time and/or arrival deadline, can be used in this determination. The cheapest carrier can then be output as recommended shipping information.
In some embodiments, a user can override packaging and/or shipping recommendations, or user preference (whether manually input or algorithm-based, such as based on a user's previous usage or preferences) may be included as part of the suitability calculation. In some embodiments, secondary recommendations can be made and/or the user can manually select packaging and/or shipping. Final packaging and/or shipping information produced by any of these methods and variations thereof can be included on a common order pack list and/or can be used as an input in generating a shipping label or similar, such as the shipping label 300 shown in
In some embodiments, a forecasting tool can be used to analyze order history of a business and make recommendations on packaging that the business should use. The analysis results in several packaging options for future orders that the user should purchase. Using these recommendations, businesses can purchase packaging catered to their exact order history, preventing over-ordering of supplies or ordering of unnecessary oversized packaging, resulting in further cost-savings.
The present disclosures allows the user to pick, pack, and ship customer orders efficiently and in a manner that minimizes manual error. Users can eliminate the manual data check between shipping label, common order pack list, and actual package because all data is organized by common orders on both the common order pack list and the label, rather than individual order number. This eliminates standard data points from a common order pack list used to manually match labels to the common order pack list to customer orders in favor of a pre-matched common order management system.
While the foregoing written description of the disclosure enables one of ordinary skill to make and use what is considered presently to be the best mode thereof, those of ordinary skill will understand and appreciate the existence of variations, combinations, and equivalents of the specific embodiment, method, and examples herein. The disclosure should therefore not be limited by the above described embodiment, method, and examples, but by all embodiments and methods within the scope and spirit of the disclosure.
Furthermore, certain terminology has been used for the purposes of descriptive clarity, and not to limit the present disclosure. It is therefore intended that the following appended claims include all such alterations, modifications and permutations as fall within the true spirit and scope of the present disclosure.
It is understood that embodiments presented herein are meant to be exemplary. Embodiments of the present disclosure can comprise any combination of compatible features shown in the various figures, and these embodiments should not be limited to those expressly illustrated and discussed. Moreover, it is understood that the below appended claims could be rewritten as multiple dependent claims, and/or dependent claims could be rewritten so as to depend from a different independent claim.
Although the present disclosure has been described in detail with reference to certain preferred configurations thereof, other versions are possible. Therefore, the spirit and scope of the disclosure should not be limited to the versions described above.
This application claims the priority benefit of U.S. Provisional Application No. 63/079,227 to He et al., filed on Sep. 16, 2020 and entitled “Systems and Methods for Order Fulfillment, Common Order Pack Lists, Multi-Item Order Packing, and Shipping Rate Automation,” the entire contents of which are hereby incorporated by reference.
Number | Date | Country | |
---|---|---|---|
63079227 | Sep 2020 | US |