Patent Grant
11282025
The invention relates generally to generation of shipping documentation and, more particularly, to shipping documentation processing operation that spawns intelligent generation subprocesses, such as may be used to facilitate autonomous functionality and/or independent operation.
The use of various forms of computing equipment to automate or otherwise perform a number of tasks has become widespread. With the proliferation of processor-based platforms, such as personal computers (PCs), tablet devices, smart phones, personal digital assistants (PDAs), and servers, capable of executing instruction sets for providing specialized or generalized functionality, such as word processing, accounting, document generation and management, printing, data communication, and image capture, generation, and management, the use of such computing equipment has become nearly ubiquitous in both business as well as personal settings. One example of functionality that is provided through the use of such computing equipment is the automation of tasks associated with the shipment of items, including the management of item orders, managing the picking and packing of items for order fulfilment, generation of invoices, packing slips, manifests, shipping labels, and postage or other prepaid shipping indicia, and tracking of shipment of items through a shipping service provider. Such automation of item shipment management is provided, for example, by the SHIPSTATION shipping management system provided by Auctane LLC of Austin Tex.
With the advent of the Internet and the advent of innumerable e-commerce merchants, not only have the number of items shipped increased appreciably in recent years, but so too have the number of shippers and recipients of such items. It is commonplace for such merchants, whether they be “brick and mortar” merchants, online merchants, or sellers through an electronic marketplace (e.g., eBay, Amazon Marketplace, etc.), to utilize computing equipment to facilitate their shipping goods using a number of forms of shipping services and media, such as letters, flats, and parcels, via various shipping service providers, such as the United States Postal Service (USPS), United Parcel Service (UPS), Federal Express (FedEx), Dalsey, Hillblom and Lynn (DHL), and local and regional couriers. Accordingly, more and more shippers, including not only large scale business traditionally involved with high volume shipping but also less sophisticated smaller entities tasked with an appreciable number of shipments, are processing relatively large numbers of items for shipment.
Although various shipping management systems have automated many shipping functions, shipping management systems have generally provided for generation of shipping labels in a user interactive process, whereby the user interacts with the user interface throughout completion of generation of each shipping label. For example, a user of a shipping management system may select an order for generation of a shipping label and thereafter be required to step through functions such as verifying the order, selecting and/or confirming shipping parameters (e.g., shipment method, shipping service provider, shipment date, rating information, additional services, etc.), requesting generation of a shipping label, waiting for rate details to be presented, confirming rate details, selecting a shipping label creation option, waiting for a shipping label to be generated, reviewing and/or approving the generated shipping label, and printing or downloading the shipping label for use in shipping the item. In addition to inputting and/or selecting information at a number of these steps in the shipping label generation process, the user may be presented with various warnings and/or queries and be required to address one or more issues with respect to the generation of the shipping label, such as to purchase additional postage value where the shipping label is to include prepaid indicia and sufficient postage value is not otherwise present. The foregoing shipping label generation process is typically essentially captive-atomic, in that it must complete or be aborted before the user is free to perform other functions in the shipping management system, such as to initiate a process for generating a shipping label for another order or to otherwise perform shipping management functions independent of the then current shipping label generation process.
Such captive-atomic processing of shipping label generation functionality, although well suited for shipping management operation with respect to individual orders, can be very tedious and slow when a user is attempting to process a relatively large number of orders and their attendant shipments. For example, where the shipping label is to be generated to include prepaid postage indicia (e.g., postage indicia accepted by the USPS for shipping services), in addition to being presented with postage rate information for verification and acceptance in response to a shipping label generation request (a task which can be somewhat time consuming and quite repetitive in many shipping situations), the user must wait for operation at the postage indicia server to complete the processing required to generate the secure value bearing indium (a process that may require appreciable time in light of the secure vault protocols and cryptographic operations performed). Thus, the duration of the processing to generate a shipping label can be appreciable, and can aggregate in a situation where the user is processing shipping labels for a relatively large number of orders to comprise a substantial amount of time dedicated to shipping label generation. Even where a shipping label does not include value bearing indicium (e.g., shipping labels typically used by such shipping service providers as UPS, FedEx, and DHL), the generation of a number of shipping labels using the captive-atomic processing typically provided may nevertheless require an appreciable amount of time, including appreciable idol user time spent waiting for various operations to complete, dedicated to shipping label generation.
The present invention is directed to systems and methods which provide shipping management system shipping documentation generation operation which spawns intelligent generation subprocesses. The intelligent generation subprocesses of embodiments facilitate autonomous shipping documentation generation functionality of a concatenated shipping documentation generation process. The shipping documentation generated according to embodiments of the invention may, for example, comprise shipping labels used in shipping items for one or more orders placed to a shipper. Such shipping labels may comprise various features, such value bearing postage indicia, machine readable information (e.g., in the form of barcodes, graphic tags, etc.), cryptographic aspects (e.g., digitally signed information), etc., in addition to or in the alternative to more traditional shipping label information, such as origination address, destination address, shipper account information, shipping service information, tracking information, and the like. The shipping documentation generated according to embodiments herein may comprise documentation in addition to or in the alternative to the aforementioned shipping labels, such as manifests, bills of lading, way bills, transmittals, etc. For example, shipping documentation generated by embodiments of the invention comprises shipping labels and supporting documentation, such as packing slips, invoices, product picking instructions, customs forms, etc., for one or more orders.
A user may initiate a shipping documentation generation process, whereby an intelligent generation subprocess is spawned in accordance with the concepts herein, and thereafter the user may be freed to perform one or more independent operation and/or interaction with the shipping management system. For example, embodiments of the invention may perform operations for generating shipping documentation with respect to shipment processing of an order precipitating shipment of an item, while one or more other processes of the shipping management system (e.g., shipping documentation generation processing for another order) are performed in parallel in response to independent user interaction with the shipping management system.
In operation of an intelligent generation subprocess of embodiments, one or more verifications, checks, warnings, and/or the like (collectively referred to as advices) typically implemented in shipping documentation generation processing by the shipping management system are suspended. Further, one or more parameter, input, selection, and/or the like (collectively referred to as configuration factors) typically solicited in shipping documentation generation processing by the shipping management system are defaulted. The intelligent generation subprocess of embodiments operates without presenting the aforementioned advices and using one or more defaulted configuration factors to intelligently and autonomously generate appropriate shipping documentation in the background. The intelligent operation provided by an intelligent generation subprocess of embodiments herein may fail the generation processing where one or more critical issues (e.g., insufficient postage funds, insufficient inventory, incomplete order processing, incompatible defaulted configuration factors, etc.) are detected with respect to shipping documentation generation. Accordingly, intelligent generation subprocesses operable in accordance with concepts herein adroitly control one or more aspect of documentation generation.
In adapting a shipping management system for use of intelligent generation subprocesses, embodiments of the invention implement a documentation queue. The documentation queue of embodiments provides historical information with respect to intelligent generation subprocess operation. For example, a documentation queue may operate to provide a running history of the operation of each active intelligent generation subprocess. Additionally or alternatively, a documentation queue may present the results of intelligent generation subprocess operation for the use of a user. For example, a documentation queue of embodiments may provide information regarding and/or access to successfully generated shipping documentation (e.g., shipping labels, manifests, bills of lading, way bills, transmittals, packing slips, invoices, product picking instructions, customs forms, etc.). Likewise, a documentation queue of embodiments may provide information regarding a failed documentation generation, perhaps providing access to one or more functions for correcting critical issues causing the generation processing to fail. Entries in the documentation queue of embodiments may be removed or otherwise omitted from presentation by the documentation queue, such as by archiving queue entries (e.g., manually and/or automatically), changing a state with respect to the queue entry, etc.
The foregoing has outlined rather broadly the features and technical advantages of the present invention in order that the detailed description of the invention that follows may be better understood. Additional features and advantages of the invention will be described hereinafter which form the subject of the claims of the invention. It should be appreciated by those skilled in the art that the conception and specific embodiment disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present invention. It should also be realized by those skilled in the art that such equivalent constructions do not depart from the spirit and scope of the invention as set forth in the appended claims. The novel features which are believed to be characteristic of the invention, both as to its organization and method of operation, together with further objects and advantages will be better understood from the following description when considered in connection with the accompanying figures. It is to be expressly understood, however, that each of the figures is provided for the purpose of illustration and description only and is not intended as a definition of the limits of the present invention.
For a more complete understanding of the present invention, reference is now made to the following descriptions taken in conjunction with the accompanying drawing, in which:
The illustrated embodiment shows a cloud-based implementation of shipping management system 111. For example, shipping management system 111 may comprise a cloud-based deployment of a multiuser application which is stored and executed by computing equipment disposed in the “cloud” of network 110. Accordingly, system 100 of the illustrated embodiment includes network 110 in which shipping management system 111 is present. Shipping management system 111 may, for example, comprise a system providing various desired functionality such as in the form of software as a service (SaaS), infrastructure as a service (IaaS), platform as a service (PaaS), unified communications as a service (UCaaS), etc.
It should be appreciated that although a cloud-based application environment is shown in the embodiment of
Shipping management system 111 may comprise computer executable code executing on one or more processor-based systems (e.g., web servers) deployed in network 110. Network 110 of the illustrated embodiment provides communication links facilitating the communication between various systems and components of system 100, such as user devices 120A-120D and shipping management system 111. Accordingly, network 110 may comprise any number of network configurations, such as the Internet, an intranet, the public switched telephone network (PSTN), a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a cellular network, a wireless network, a cable transmission network, and/or the like. The communication links between the user devices and the other nodes of system 100 (e.g., shipping management system 111, postage system 112, shipping service provider system 113, commerce system 114, computing resources 130A-130D, and other ones of user devices 120A-120D) may comprise wired links (e.g., as illustrated for user devices 120A and 120B) or wireless links (e.g., as illustrated for user devices 120C and 120D), as well as combinations thereof. One or more interfaces, such as may comprise appropriate application programming interfaces (APIs), may be included in or otherwise provided with respect to shipping management system 111 to provide data exchange and/or other functionality described herein between shipping management system 111 and other applications, systems, devices, etc. of system 100 (e.g., postage system 112, shipping service provider system 113, commerce system 114, and/or user devices 120A-120D).
Postage system 112 may comprise one or more processor-based systems (e.g., web servers) operable to provide prepaid postage account and postage indicia generation services (e.g., to generate postage indicia, shipping labels, etc. acceptable by the USPS and/or other shipping service providers). For example, postage system 112 may comprise one or more server of the online postage service offered by Stamps.com Inc. Various individuals (shippers, purchasers, etc.) and/or other entities (e.g., business entities, merchants, etc.) may maintain an account with respect to postage system 112 facilitating the generation of postage indicia, whether individually, in batch, in combination with other documentation (e.g., shipping labels, bills of lading, manifests, customs documents, etc.), and whether directly by the account holder or indirectly, such by operation of shipping management system 111. Prepaid value associated with such accounts may be stored by, or in association with, postage system 112, such as within a postage security device (PSD). Additional or alternative information may be stored by, or in association with, postage system 112, such as user credentials utilized in validating users for account access, usage logs for accounting and/or fraud prevention/detection, rating information for use in shipping service rate determinations, etc.
Shipping service provider system 113 may comprise one or more processor-based systems (e.g., web servers) operable to provide functionality with respect to shipping services provided by a shipping service provider. For example, shipping service provider system 113 may comprise one or more server associated with the USPS providing an interface for accessing various functions and data (e.g., rating tables, shipment tracking functionality and/or data, etc.) with respect to shipments made via USPS provided shipping services. Various individuals (shippers, intended recipients, etc.) and/or other entities (e.g., businesses, merchants, etc.) may utilize such functionality and/or data in association with shipment of items as managed by shipping management system 111.
Commerce system 114 may comprise one or more processor-based systems (e.g., web servers) operable to provide functionality with respect to the sale and purchase of items for which shipping services are ultimately to be provided by a shipping service provider and managed by operation of shipping management system 111. For example, commerce system 114 may comprise one or more server operable to provide online electronic commerce sites (e.g., online merchant stores), electronic marketplaces (e.g., eBay and Amazon Marketplace), etc. Multiple such commerce sites may be in communication with a shipping management system configuration of embodiments, thereby providing a multi-channel shipping management platform. In operation, commerce system 114 of embodiments provides order information (e.g., item purchase information, buyer information, shipping destination information, shipping service information, payment information of one or more marketplaces, such as Amazon.com, eBay, etc., for facilitating shipping management functionality (e.g., shipping management control, reporting, and other operations) of the shipping management system.
Functionality in addition to or in the alternative to the aforementioned postage generation services provided by postage system 112, the aforementioned functionality and/or data provided by shipping service provider system 113, and the aforementioned commerce functionality and/or data provided by commerce system 114 may be provided by these and/or one or more other systems of system 100 (not shown), according to embodiments. For example, functionality may be provided by one or more servers (e.g., manufacturers' systems, distributors' systems, product database systems, etc.) to provide information relevant to shipping various items (e.g., weight information used to determine shipping service rates, item content information used to determine shipping services available for use with respect to particular items, such as in the case of hazardous materials, package size information used to determine shipping service rates and/or compatibility with respect to particular items, etc.). It should be appreciated that the functionality provided by various servers and/or other systems of the cloud environment of system 100 of embodiments is not limited functionality directly related to the management of the shipment of items.
Storage 115 shown in the illustrated embodiment disposed in the cloud environment of network 110 may, for example, comprise various forms of tangible, non-transitory computer readable media. For example, storage 115 of embodiments may comprise random access memory (RAM), read only memory (ROM), flash memory, disk memory, magnetic memory, optical memory, etc. Storage 115 may comprise a storage array or other storage system, such as a redundant array of independent disks (RAID) array, a storage area network (SAN), a network attached storage (NAS) array, and/or the like. Such computer readable storage may be utilized to store various information, including program code of shipping management system 111, program code of client applications utilized with respect to shipping management system 111, postage system 112, shipping service provider system 113, and/or commerce system 114, data utilized by and/or with any or all of shipping management system 111, postage system 112, shipping service provider 113, commerce system 114, and their client applications, etc. Portions of storage 115 may comprise a part of one or more systems of the cloud (e.g., shipping management system 111, postage system 112, shipping service provider system 113, and/or commerce system 114) and/or may be separate from such systems (e.g., provided as an independent database system).
User devices 120A-120D of embodiments comprise processor-based systems operable under control of one or more instruction set (e.g., software, firmware, applet, etc.) adapted to cooperate with shipping management system 111 to provide desired functionality, such as the aforementioned exemplary shipping management functionality. For example, user devices 120A-120D may comprise servers and/or terminals in the form of one or more computer, workstation, kiosk terminal, portable processor-based device, personal digital assistant (PDA), smartphone, etc. Such processor-based systems may comprise a central processing unit (CPU) (e.g., a processor from the PENTIUM or CORE line of processors available from Intel Corporation), memory (e.g., RAM, ROM, flash memory, disk memory, optical memory, etc.) storing the aforementioned one or more instruction set and/or other data used herein, and appropriate input/output circuitry and devices (e.g., network interface card (NIC), keyboard, digital pointer, display screen, peripheral interface, microphone, speaker, wireless interface, etc.). It should be appreciated that, although the illustrated embodiment shows a representative example of the number and configuration of user devices as may be utilized with respect to system 100, the concepts of the present invention are not limited to application to the particular number or configuration of user devices shown.
User devices 120A and 120B of the illustrated embodiment comprise computer systems having a processor, memory, and input/output to enable interaction with shipping management system 111 for providing at least some portion of functionality available through operation of system 100. User device 120A may, for example, be configured for use by a merchant or other shipper to operate with commerce system 114 to offer items for sale and/or with shipping management system 111 for managing orders of such items, outbound shipments of the items of such orders, and return of items by purchasers or other recipients thereof, possibly also operating with postage system 112 and/or shipping service provider system 113 for certain functionality provided thereby. Accordingly, the illustrated embodiment of user device 120A includes a number of computing resources 130A, 130C, and 130D, as may be utilized in facilitating such functionality. Correspondingly, user device 120B may, for example, be configured for use by a purchaser or other acquirer/recipient of an item to operate with commerce system 114 to purchase items and/or with shipping management system 111 for requesting and processing return shipment of various purchased or otherwise acquired items. Accordingly, the illustrated embodiment of user device 120B includes computing resource 130B, as may be utilized in facilitating such functionality.
User device 120C of the illustrated embodiment comprises a tablet device having a processor, memory, and input/output to enable interaction with shipping management system 111 and/or commerce system 114 for providing at least some portion of functionality available through operation of system 100, possibly also operating with postage system 112 and/or shipping service provider system 113 for certain functionality provided thereby. User device 120D of the illustrated embodiment comprises a smartphone having a processor, memory, and input/output to enable interaction with shipping management system 111 and/or commerce system 114 for providing at least some portion of functionality available through operation of system 100, possibly also operating with postage system 112 and/or shipping service provider system 113 for certain functionality provided thereby. Such user device configurations may be particularly well suited for use by purchasers or other recipients of items herein. Of course, such user devices may be utilized by a merchant or other shipper to provide some functionality as described herein.
Irrespective of the particular configuration of the user device, user devices 120 (e.g., user devices 120A-120D) of system 100 of embodiments comprise one or more client applications, such as for interacting with shipping management system 111 to provide operation as described herein. For example, user devices 120 may comprise a user interface client application operable to facilitate user interaction with shipping management system 111. Such user interface client applications may comprise a web browser (e.g., INTERNET EXPLORER, GOOGLE CHROME, or FIREFOX) hosting a client applet associated with shipping management system 111 and operable within the web browser. Thus, a user may interact with shipping management system 111 via a client applet executing within a user interface client application. Additionally or alternatively, user devices 120 may comprise one or more other applications for facilitating operation as described herein. For example, user devices 120 may comprise a mail client (e.g., OUTLOOK, POSTBOX, etc.), a short message service (SMS) client, a social media client (e.g., FACEBOOK, TWITTER, etc.), and/or the like for receiving messages relevant to operations herein. For example, messages delivered using such client applications may comprise notifications regarding shipping documentation generation, notifications regarding resource status (e.g., prepaid postage balance, insufficient postage balance, etc.), shipment notifications, return authorizations, tracking status reports, etc. The messages may include active components operable to cause the user device to interact with functionality of other systems, such as shipping management system 111, postage system 112, shipping service provider system 113, etc., such as to request information, initiate a prepaid balance transaction, etc.
As illustrated with respect to user devices 120A and 120B, various peripherals and other computing resources useful in providing functionality available through operation of system 100 may be coupled to or otherwise in communication with user devices, or other nodes of system 100, of embodiments. For example, computing resources, such as one or more printer (e.g., thermal printer, ink printer, laser printer, etc.), imaging device (e.g., optical scanner, barcode scanner, handheld scanner, camera, biometric sample scanner, etc.), scale (e.g., electronic scale, digital scale), memory device (e.g., optical disk drive, hard disk drive, solid state disk drive, etc.), and/or the like, may be provided for use with any or all of the foregoing processor-based systems according to embodiments herein. Computing resources 130A and 130B, shown in the illustrated embodiment as printers (e.g., printer for printing proof of payment indicia, bills of lading, manifests, receipts, shipping labels, etc.) are shown as being coupled to user devices 120A and 120B, respectively. Similarly, computing resource 130C, shown as a scale (e.g., an electronic scale for weighing items for shipping), and computing resource 130D, shown as an imaging device (e.g., a scanner for obtaining images of shipping items, for scanning barcodes, for scanning addresses or other shipping item information, etc.), are shown as being coupled to user device 120A of the illustrated embodiment. Of course, configurations and deployments of computing resources different than that shown may be utilized according to embodiments of the invention.
Operation according to embodiments of shipping management system 111 to provide shipping documentation processing spawning intelligent generation subprocesses according to embodiments of the invention is shown the flow diagram of
At block 201 of the illustrated embodiment of flow 200, a user's selection to employ the intelligent generation shipping document processing is received. For example, a user may manipulate a control input, such as “QUICKSHIP™” control 301 of
Having elected to initiate the shipping documentation processing mode operable to spawn intelligent generation subprocesses, the user may be provided with notifications regarding advices and/or defaulted configuration factors at block 202 of the illustrated embodiment. In operation of an intelligent generation subprocess of embodiments, presenting one or more verifications, checks, warnings, and/or the like (collectively referred to as advices) typically implemented in shipping documentation generation processing by the shipping management system are suspended. For example, when operating in a standard shipping documentation generation mode, a user may be provided with various warnings, such as a warning that shipping documentation for a selected order has already been generated, that data required or preferred in generating shipping documentation is not present with respect to a selected order, that a prepaid balance for a shipping service provider selected with respect to a selected order is below a threshold, etc. Additionally or alternatively, when operating in the standard shipping documentation mode, the user may be provided with various verifications, such as to present rate details to the user for confirmation prior to generating the shipping documentation, to present a shipping documentation preview to the user for confirmation prior to printing the shipping documentation, etc. Further, one or more parameter, input, selection, and/or the like (collectively referred to as configuration factors) typically solicited in shipping documentation generation processing by the shipping management system are defaulted. For example, when operating in a standard shipping documentation mode, the user may be provided with the opportunity to input various parameters, such as shipping documentation size and/or format parameters, shipping date information, etc. Additionally or alternatively, when operating in the standard shipping documentation mode, the user may be provided with the opportunity to make one or more selections, such as to select a particular printer or other peripheral device to be used with respect to the shipping documentation, to select a particular shipping account for payment for shipping services and/or the shipping documentation itself, etc. However, the intelligent generation subprocess of embodiments operates without one or more of the aforementioned advices and using one or more defaulted configuration factors to intelligently and autonomously generate appropriate shipping documentation in the background. That is, some or all such advices may be suspended and/or some or all such configuration factors may be defaulted in intelligent generation subprocess operation according to embodiments. Thus, appropriate notifications regarding the suspension of advices and the inability to provide configuration factors with respect to the shipping documentation processing operable to spawn intelligent generation subprocesses may be provided at block 202.
Embodiments of the invention may additionally or alternatively enable the user to select settings or otherwise input parameters utilized with respect to the shipping documentation processing operable to spawn intelligent generation subprocesses. A user may be provided with the ability to select operations to be performed by the subprocesses, to be performed at spawning and/or conclusion of the subprocesses, etc. according to embodiments herein. For example, as illustrated in
At block 203 of the illustrated embodiment a determination is made as to whether the user has accepted the notification regarding defaulted configuration factors and/or adequately inputted any information (e.g., defaulted configuration factor selections or other parameters) for enabling intelligent generation subprocess operation according to embodiments herein. For example, a user may not be aware of, or desirous of, the suspension of advices and may thus decline acceptance of operation of shipping documentation processing spawning intelligent generation subprocesses (e.g., the user may wish to review rate details or be warned regarding certain conditions prior to generation of shipping documentation). Similarly, the user not wish to use a defaulted configuration factor with respect to one or more shipping document to be generated and may thus decline acceptance of operation of shipping documentation processing spawning intelligent generation subprocesses. In operation according to the illustrated embodiment, if the user declines acceptance of operation of shipping documentation processing spawning intelligent generation subprocesses, processing proceeds to block 204 wherein standard shipping documentation generation mode operation is provided. However, if the user accepts operation of shipping documentation processing spawning intelligent generation subprocesses, processing according to the illustrated embodiment proceeds to block 205.
At block 205 of the illustrated embodiment, selections of one or more orders for shipping documentation processing are received. For example, as shown in
Initiation of shipping documentation processing according to embodiments operates to spawn one or more intelligent generation subprocesses in accordance with the concepts herein at block 206. Thereafter, the one or more intelligent generation subprocesses perform operations for generating shipping documentation with respect to shipment processing of the selected one or more selected order at block 207.
Because operation of the one or more intelligent generation subprocesses are autonomous according to embodiments herein, the user may be freed to perform one or more independent operation and/or interaction with the shipping management system during the shipping document processing, at block 208. For example, one or more other processes of the shipping management system (e.g., shipping documentation generation processing for another order) may be performed in response to independent user interaction with the shipping management system in parallel to shipping documentation generation processing performed by the one or more intelligent generation subprocesses.
In adapting a shipping management system for use of intelligent generation subprocesses, embodiments of the invention implement a documentation queue, such as through storing relevant data in storage 115 and presenting some or all such queue data in a documentation queue user interface of shipping management system 111. Documentation queues of embodiments of the invention provide a history with respect to shipping documentation generation using intelligent generation subprocesses. Additionally or alternatively, documentation queues provide a visual aid for organizing the generated shipping documentation and/or information associated therewith. In operation of embodiments, a documentation queue is accessible throughout the shipping management system user interface to facilitate the user's ability to perform other operations within the shipping management system and nevertheless remain apprised of the shipping documentation generation and/or to facilitate the user's access to generated shipping documentation.
An exemplary documentation queue user interface of shipping management system 111 for a documentation queue implemented according to embodiments herein is shown as documentation queue 304 in
Using a documentation queue of embodiments, despite the user being free to perform one or more independent operation and/or interaction with the shipping management system during the shipping documentation processing, the user may nevertheless be apprised of the documentation generation processing operations initiated by the user. Accordingly, embodiments operate to display the documentation queue user interface (e.g., documentation queue 304) persistently in the shipping management system user interface. For example, a documentation queue user interface may remain displayed in the shipping management system user interface so long as an intelligent generation subprocess is executing (e.g., until all spawned instances of intelligent generation subprocesses have terminated), until all intelligent generation subprocess instances represented in the documentation queue have been archived, until all shipping documentation generated by intelligent generation subprocesses has been printed or otherwise consumed, until all instances of intelligent generation subprocesses have been archived or otherwise removed from the documentation queue, until an intelligent generation shipping processing mode of the shipping management system is exited, until a user selects closing of the documentation queue user interface, and/or the like. Thus, the documentation queue may remain displayed in the shipping management system user interface throughout the user interacting with the shipping management system during the shipping documentation processing to facilitate the user being apprised of the documentation generation processing operations.
As discussed above, a user may select more than one order for initiating shipping documentation generation using intelligent generation subprocesses of embodiments herein. In operation, an intelligent generation subprocess may be spawned for each such selected order to thereby provide separate autonomous shipping documentation generation in association with each of the selected orders. Embodiments of the invention, however, operate to spawn an intelligent generation subprocess that generates shipping documentation for a plurality of selected orders. For example, such intelligent generation subprocesses may operate to “stich” together multiple generated shipping documents (e.g., to form one large PDF file containing multiple shipping labels) for easy organization, for use in keeping shipping documentation having a common attribute (e.g., same shipping origin, same shipping destination, same shipping service provider, orders including the same items, etc.) together, etc. An exemplary documentation queue showing entries associated with operation of intelligent generation subprocesses that generate shipping documents for a plurality of selected orders according to embodiments herein is shown in
Processing of shipping documentation with respect to a plurality of orders by an intelligent generation subprocess may be adapted to facilitate efficient or expedited processing. Such embodiments may, for example, leverage functionality of external systems (e.g., one or more of aforementioned postage system 112, shipping service provider system 113, and commerce system 114) to perform shipping documentation generation processing for multiple orders while minimizing certain interactions and/or communications, such as handshaking protocols, serial requests and acknowledgments, etc. As a specific example, an intelligent generation subprocess may include an API or other control interface adapted to interact with a postage indicia generation platform (e.g., postage system 112), such as those shown and described in the above referenced application entitled “SINGLE SECURE ENVIRONMENT SESSION GENERATING MULTIPLE INDICIA,” providing for generation of multiple value bearing indicia in a single secure vault session. In such an embodiment not only are the serial communications between the shipping management system and the postal system for multiple shipping documents consolidated into a single request, but further expediting of the shipping documentation generation processing is provided through loading of a secure vault configuration for generating multiple value bearing indicia (as opposed to the traditional loading/unloading of a secure vault configuration for each postage indicia generated).
Detail with respect to operation of an intelligent generation subprocess of embodiments to intelligently and autonomously generate appropriate shipping documentation at block 207 of
Embodiments of shipping management system 111 may provide integration with inventory management functionality. For example, shipping management system 111 may operate to automatically track and adjust stock in inventory records, such as where a “ship from” field in an order being processed is linked to an inventory source (e.g., warehouse). In operation, the current stock level may be made available with respect to order processing functionality. In addition to tracking the number of items remaining in inventory, such inventory management functionality may provide reservation of inventory items for specific orders (e.g., manually or automatically) by allocating inventory prior to the inventory actually having been depleted. For example, inventory may be allocated to orders to ensure availability of inventory for certain orders, such as orders placed by particularly important customers (e.g., repeat customers, customers having purchased a “membership”, etc.), orders placed through certain channels (e.g., reseller marketplaces imposing strict order fulfillment requirements), orders meeting certain criteria (e.g., large orders that cannot be completed without some piece of inventory), and/or the like. Such allocation may be performed based on customizable prioritization rules, for example. The analyzing of advices, configuration factors, and/or critical issues with respect to selected orders at block 211 of embodiments may operate to analyze such inventory data for determining critical issues. For example, if insufficient inventory is available, whether out of stock or allocated for fulfilling another order, logic of an intelligent generation subprocess may determine that a critical issue is present with respect to the generation of the shipping documentation (e.g., shipping documentation is not to be generated for an order that cannot be fulfilled).
The intelligent operation provided by an intelligent generation subprocess of embodiments herein may fail the shipping documentation generation processing where one or more critical issues (e.g., insufficient postage funds, insufficient inventory, incomplete order processing, incompatible defaulted configuration factors, etc.) are detected. Accordingly, at block 212 of the illustrated embodiment a determination is made as to whether a failure state is detected (e.g., a critical issue is present). For example, various advices, configuration factors, and/or other parameters associated with the selected one or more orders and the shipping documentation to be generated therefor may be compared to a database of failure conditions to determine if a failure state is detected. Such comparisons may use single parameters (e.g., insufficient postage funds) meeting corresponding entries within the database as well as multiple parameters meeting corresponding entries in the database (e.g., insufficient postage funds and no alternative prepaid account designated and a postage fund auto-refill function being inactive or inoperable), for example.
If a failure state is detected at block 212 of the illustrated embodiment, processing proceeds to block 213 wherein available failure state processing is performed in order to attempt to mitigate the failure state and facilitate shipping documentation generation. For example, where insufficient postage funds are present for generating the shipping documentation, failure state mitigation processing may operate to initiate a postage fund refill operation, such as through interaction with one or more external platforms providing or facilitating such operation (e.g., postage system 112, shipping service provider system 113, and/or commerce system 114). As another example, where a missing or otherwise incompatible configuration factor is detected, failure state mitigation processing at block 213 of embodiments may operate to analyze historical shipping processing data to select a configuration factor from a prior shipping documentation generation session determined to be a similar scenario, indicative of the user's preference, etc. Additionally or alternatively, failure state mitigation processing may operate to mitigate a failure state through interaction with one or more external systems (e.g., postage system 112, shipping service provider system 113, and/or commerce system 114), such as to obtain data, mitigation processing, etc. therefrom. Thereafter, processing according to the illustrated embodiment proceeds to block 214 where a determination is made as to whether failure state mitigation has been performed (or successfully performed).
If it is determined at block 214 that failure state mitigation processing was not successfully performed, processing according to the illustrated embodiment proceeds to block 215 wherein the state of the intelligent generation subprocess is updated to a failed state and further processing by the intelligent generation subprocess is ended or suspended. It should be appreciated that a documentation queue entry for the intelligent subprocess will be provided in the documentation queue to alert the user of the failure of the intelligent generation subprocess to generate the one or more shipping documents. In operation according to embodiments of the invention, the user may select the documentation queue entry for the intelligent generation subprocess (e.g., at any time convenient to the user, such as after completion of another task being performed within shipping management system 111 by the user) to determine the details of a cause of the failure state and/or to take action to perform failure state mitigation processing. For example, where insufficient postage funds are present for generating the shipping documentation, the user may initiate a postage fund refill operation (e.g., using postage system 112, shipping service provider system 113, and/or commerce system 114). As another example, where a missing or otherwise incompatible configuration factor is detected, the user may input or select one or more configuration factor. Thereafter, processing according to embodiments may operate to re-initiate the intelligent generation subprocess (e.g., returning to block 211) for providing shipping documentation generation processing according to the concepts herein.
If, however, it is determined at block 214 that failure state mitigation processing was successfully performed, processing according to the illustrated embodiment returns to block 211 to analyze advices, configuration factors, and/or critical issues with respect to the one or more selected orders and the respective shipping documentation to be generated in light of the mitigation processing (e.g., to determine if advices of a nature indicating that autonomous shipping documentation processing should not be or cannot be performed are present, to determine if parameters for the generation of the shipping documentation are missing or are otherwise incompatible with generation of shipping documentation indicating that autonomous shipping documentation processing should not be or cannot be performed, to determine if critical issues with respect to the generation of the shipping documentation are present, etc.). Although not expressly shown in the illustrated embodiment, processing to return to block 211 may comprise operation to re-spawn at least one intelligent generation subprocess (e.g., in accordance with block 206 of
If no failure state was detected at block 212 of the illustrated embodiment, processing proceeds to block 216 wherein logic of the intelligent generation subprocess interacts with shipping documentation functionality to generate the shipping documentation. For example, the intelligent generation subprocess may interact with one or more systems (e.g., postage system 112, shipping service provider system 113, and commerce system 114, whether through an API or other interface adapted to facilitate operation of intelligent generation subprocesses herein, by providing interaction spoofing or mimicking that of user interaction, and/or the like), preferably providing acknowledgements, inputs, etc., receiving outputs, results, etc., to provide shipping documentation generation processing, or some portion thereof. For example, logic of the intelligent generation subprocess may interact with postage system 112 to generate value bearing postage indicia, postal shipping labels, manifests, etc. to thereby generate the shipping documentation requested by the user or to otherwise facilitate the generation of shipping documentation. Additionally or alternatively, logic of the intelligent generation subprocess may interact with shipping service provider system 113 to generate shipping labels, manifests, item shipment forms, customs forms, etc. to thereby generate the shipping documentation requested by the user or to otherwise facilitate the generation of shipping documentation. Likewise, logic of the intelligent generation subprocess may interact with commerce system 114 to conduct one or more transaction (e.g., payment and purchase for shipping services, value bearing indicia, etc.) for facilitating the generation of shipping documentation.
It should be appreciated that the interaction with shipping documentation functionality to generate the shipping documentation provided by an intelligent generation subprocess need not be with an external system (e.g., postage system 112, shipping service provider system 113, and/or commerce system 114), but may additionally or alternatively be with logic of shipping management system 111 itself. For example, where the shipping documentation comprises a shipping label which does not require value bearing indicia generated by such systems as postage system 112, and where shipping management system 111 comprises sufficient data (e.g., shipping label format information, shipper address, recipient address, etc.) and/or functionality (e.g., barcode generator, facing indication mark generator, etc.) to generate such a shipping label, the intelligent generation subprocess may interact with logic of shipping management system 111 to generate one or more shipping documents according to embodiments of the invention. As another example, an intelligent generation subprocess may interact with an external system (e.g., postage system 112, shipping service provider system 113, and/or commerce system 114) to obtain the benefit of some shipping documentation generation functionality (e.g., generation of postage indicia data, digital value token, shipping service rating, etc.) and utilize functionality internal to shipping management system 111 to generate the shipping documentation (e.g., generate shipping labels having postage indicia thereon rendered from secure data provided by an external system, generate shipping documents having rates determined by an external system, etc.).
Although not expressly shown in the illustrated embodiment, it should be appreciated operation at block 216 of embodiments may include updating the state of the intelligent generation subprocess at one or more milestone in a corresponding instance in the documentation queue of embodiments. For example, the state of the intelligent generation subprocess may be updated to reflect interaction with an external system, initiation of a particular process, completion of a particular process, waiting completion of a process, etc.
At block 217 of the illustrated embodiment, a determination is made as to whether the appropriate shipping documentation was obtained from the interaction with shipping documentation functionality. If the appropriate shipping documentation was not obtained, such as due to a failure to complete the shipping documentation functionality (e.g., resulting from a failure at a remote system or the communication therewith, an undetected critical issue, etc.), processing according to the illustrated embodiment proceeds to block 215 for processing as described above. However, if the appropriate shipping documentation was obtained, processing according to the illustrated embodiment proceeds to block 218.
The state of the intelligent generation subprocess is updated in a corresponding instance in the documentation queue to reflect successful shipping documentation generation at block 218 of embodiments. Thereafter, at block 219, manual and/or automatic processing may be performed with respect to the generated shipping documentation. For example, a user may interact with the instance of the intelligent generation subprocess in the documentation queue at any time convenient to the user (e.g., after completion of another task being performed within shipping management system 111 by the user) to view data regarding the generated shipping documentation, such as to view the shipping documentation, to obtain information regarding shipping rates associated with the shipping documentation, to view/select a printer for printing the generated shipping documentation, etc. Additionally or alternatively, the user may interact with the instance of the intelligent generation subprocess in the documentation queue to take action, such as to print the generated shipping documentation, to archive documentation queue entries for which processing has been completed and the user has no further need for the historical shipping documentation generation information, etc.
It should be appreciated that various actions may be performed automatically by an intelligent generation subprocess and/or by other functionality of the shipping management system, at block 219, after obtaining the generated shipping documentation. For example, where a user has selected to do so, the shipping management system may cause the shipping documentation to be printed to a selected printer. Likewise, where a user has selected to do so, the shipping management system may cause the instance of the intelligent generation subprocess in the documentation queue to automatically be archived (i.e., removed from the documentation queue) after printing of the generated shipping documentation.
Although some embodiments have been described herein with respect to printing generated shipping documentation, it should be appreciated that the concepts of the present invention are not limited to use in scenarios where shipping documentation is printed. For example, embodiments of the present invention may be implemented with respect to third-party fulfillment or drop-shipper scenarios, such as wherein a user transmits shipping instructions (e.g., some or all of the generated shipping documentation) to another party for fulfillment of orders. Accordingly, embodiments facilitate fulfillment of orders whether by self-fulfilling an order (e.g., by generating a shipping label) or by sending a request to a third-party to fulfill the order.
Although the present invention and its advantages have been described in detail, it should be understood that various changes, substitutions and alterations can be made herein without departing from the spirit and scope of the invention as defined by the appended claims. Moreover, the scope of the present application is not intended to be limited to the particular embodiments of the process, machine, manufacture, composition of matter, means, methods and steps described in the specification. As one of ordinary skill in the art will readily appreciate from the disclosure of the present invention, processes, machines, manufacture, compositions of matter, means, methods, or steps, presently existing or later to be developed that perform substantially the same function or achieve substantially the same result as the corresponding embodiments described herein may be utilized according to the present invention. Accordingly, the appended claims are intended to include within their scope such processes, machines, manufacture, compositions of matter, means, methods, or steps.
The present application is a continuation of U.S. patent application Ser. No. 15/064,218 filed Mar. 8, 2016 and entitled “CONCATENATED SHIPPING DOCUMENTATION PROCESSING SPAWNING INTELLIGENT GENERATION SUBPROCESSES,” which is related to co-pending U.S. patent application Ser. No. 14/255,713 filed Apr. 17, 2014 and entitled “SINGLE SECURE ENVIRONMENT SESSION GENERATING MULTIPLE INDICIA,” which issued Sep. 17, 2019 as U.S. Pat. No. 10,417,728, and Ser. No. 14/753,918 filed Jun. 29, 2015 and entitled “SYSTEMS AND METHODS FOR CLOUD-BASED APPLICATION ACCESS TO RESOURCE,” which issued Nov. 13, 2018 as U.S. Pat. No. 10,129,172, the disclosures of which are incorporated herein by reference in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3584696 | Eblowitz | Jun 1971 | A |
| 3594727 | Braun | Jul 1971 | A |
| 3691726 | Stephens et al. | Sep 1972 | A |
| 4119194 | Freeman et al. | Oct 1978 | A |
| 4253158 | McFiggans | Feb 1981 | A |
| 4376299 | Rivest | Mar 1983 | A |
| 4511793 | Racanelli | Apr 1985 | A |
| 4641347 | Clark et al. | Feb 1987 | A |
| 4725718 | Sansone et al. | May 1988 | A |
| 4743747 | Fougere et al. | May 1988 | A |
| 4744554 | Kulpa et al. | May 1988 | A |
| 4757537 | Edelmann et al. | Jul 1988 | A |
| 4763271 | Field | Aug 1988 | A |
| 4775246 | Edelmann et al. | Oct 1988 | A |
| 4800508 | Axelrod et al. | Jan 1989 | A |
| 4802218 | Wright et al. | Jan 1989 | A |
| 4807139 | Liechti | Feb 1989 | A |
| 4812994 | Taylor et al. | Mar 1989 | A |
| 4831554 | Storace et al. | May 1989 | A |
| 4831555 | Sansone et al. | May 1989 | A |
| 4837701 | Sansone et al. | Jun 1989 | A |
| 4858138 | Talmadge | Aug 1989 | A |
| 4864618 | Wright et al. | Sep 1989 | A |
| 4868757 | Gil | Sep 1989 | A |
| 4873645 | Hunter et al. | Oct 1989 | A |
| 4893249 | Silverberg | Jan 1990 | A |
| 4900903 | Wright et al. | Feb 1990 | A |
| 4900904 | Wright et al. | Feb 1990 | A |
| 4900941 | Barton et al. | Feb 1990 | A |
| 4901241 | Schneck | Feb 1990 | A |
| 4908770 | Breault et al. | Mar 1990 | A |
| 4941091 | Breault et al. | Jul 1990 | A |
| 5010485 | Bigari | Apr 1991 | A |
| 5058008 | Schumacher | Oct 1991 | A |
| 5065000 | Pusic et al. | Nov 1991 | A |
| 5067088 | Schneiderhan | Nov 1991 | A |
| 5075862 | Doeberl et al. | Dec 1991 | A |
| 5077792 | Herring | Dec 1991 | A |
| 5085470 | Peach et al. | Feb 1992 | A |
| 5111030 | Brasington et al. | May 1992 | A |
| 5150407 | Chan | Sep 1992 | A |
| 5202834 | Gilham | Apr 1993 | A |
| 5222018 | Sharpe et al. | Jun 1993 | A |
| 5233657 | Gunther | Aug 1993 | A |
| 5237506 | Horbal et al. | Aug 1993 | A |
| 5239168 | Durst, Jr. et al. | Aug 1993 | A |
| 5289540 | Jones | Feb 1994 | A |
| 5319562 | Whitehouse | Jun 1994 | A |
| 5323323 | Gilham | Jun 1994 | A |
| 5323465 | Avarne | Jun 1994 | A |
| 5341505 | Whitehouse | Aug 1994 | A |
| 5423573 | de Passille | Jun 1995 | A |
| 5454038 | Cordery et al. | Sep 1995 | A |
| 5483445 | Pickering | Jan 1996 | A |
| 5485369 | Nicholls et al. | Jan 1996 | A |
| 5490077 | Freytag | Feb 1996 | A |
| 5510992 | Kara | Apr 1996 | A |
| 5583779 | Naclerio et al. | Dec 1996 | A |
| 5602743 | Freytag | Feb 1997 | A |
| 5606507 | Kara | Feb 1997 | A |
| 5606613 | Lee et al. | Feb 1997 | A |
| 5612541 | Hoffmann et al. | Mar 1997 | A |
| 5612889 | Pintsov et al. | Mar 1997 | A |
| 5619571 | Sandstrom et al. | Apr 1997 | A |
| 5623546 | Hardy et al. | Apr 1997 | A |
| 5649118 | Carlisle et al. | Jul 1997 | A |
| 5655023 | Cordery et al. | Aug 1997 | A |
| 5663547 | Ziarno | Sep 1997 | A |
| 5696829 | Cordery et al. | Dec 1997 | A |
| 5706502 | Foley et al. | Jan 1998 | A |
| 5708422 | Blonder et al. | Jan 1998 | A |
| 5715314 | Payne et al. | Feb 1998 | A |
| 5717596 | Bernard et al. | Feb 1998 | A |
| 5717597 | Kara | Feb 1998 | A |
| 5729459 | Brandien et al. | Mar 1998 | A |
| 5729460 | Plett et al. | Mar 1998 | A |
| 5729674 | Rosewarne et al. | Mar 1998 | A |
| 5742683 | Lee et al. | Apr 1998 | A |
| 5768132 | Cordery et al. | Jun 1998 | A |
| 5774886 | Kara | Jun 1998 | A |
| 5778076 | Kara et al. | Jul 1998 | A |
| 5796834 | Whitney et al. | Aug 1998 | A |
| 5801364 | Kara et al. | Sep 1998 | A |
| 5801944 | Kara | Sep 1998 | A |
| 5812991 | Kara | Sep 1998 | A |
| 5819240 | Kara | Oct 1998 | A |
| 5822739 | Kara | Oct 1998 | A |
| 5825893 | Kara | Oct 1998 | A |
| 5860068 | Cook | Jan 1999 | A |
| 5923885 | Johnson et al. | Jul 1999 | A |
| 5936885 | Morita et al. | Aug 1999 | A |
| 5946671 | Herring | Aug 1999 | A |
| 5960418 | Kelly et al. | Sep 1999 | A |
| 5983209 | Kara | Nov 1999 | A |
| 6005945 | Whitehouse | Dec 1999 | A |
| 6010069 | Debois | Jan 2000 | A |
| 6047273 | Vaghi | Apr 2000 | A |
| 6061670 | Brand | May 2000 | A |
| 6061671 | Baker et al. | May 2000 | A |
| 6175825 | Fruechtel | Jan 2001 | B1 |
| 6199055 | Kara et al. | Mar 2001 | B1 |
| 6208980 | Kara | Mar 2001 | B1 |
| 6233565 | Lewis et al. | May 2001 | B1 |
| 6233568 | Kara | May 2001 | B1 |
| 6249777 | Kara et al. | Jun 2001 | B1 |
| 6381590 | Debois | Apr 2002 | B1 |
| 6385504 | Pintsov et al. | May 2002 | B1 |
| 6385731 | Ananda | May 2002 | B2 |
| 6424954 | Leon | Jul 2002 | B1 |
| 6430543 | Lee et al. | Aug 2002 | B1 |
| 6470327 | Carroll et al. | Oct 2002 | B1 |
| 6526393 | Fredman | Feb 2003 | B1 |
| 6532452 | Pintsov et al. | Mar 2003 | B1 |
| 6834273 | Sansone et al. | Dec 2004 | B1 |
| 6853990 | Thiel | Feb 2005 | B1 |
| 6865557 | Cordery et al. | Mar 2005 | B1 |
| 6889214 | Pagel et al. | May 2005 | B1 |
| 7149726 | Lingle et al. | Dec 2006 | B1 |
| 7177825 | Borders et al. | Feb 2007 | B1 |
| 7182259 | Lubow et al. | Feb 2007 | B2 |
| 7225170 | Ryan, Jr. | May 2007 | B1 |
| 7233929 | Lingle et al. | Jun 2007 | B1 |
| 7243842 | Leon et al. | Jul 2007 | B1 |
| 7266531 | Pintsov et al. | Sep 2007 | B2 |
| 7337152 | Gawler | Feb 2008 | B1 |
| 7343357 | Kara | Mar 2008 | B1 |
| 7383194 | Heiden et al. | Jun 2008 | B2 |
| 7409353 | Uslontsev et al. | Aug 2008 | B1 |
| 7430424 | Kraft et al. | Sep 2008 | B2 |
| 7444290 | Woods et al. | Oct 2008 | B2 |
| 7458612 | Bennett | Dec 2008 | B1 |
| 7509291 | McBride et al. | Mar 2009 | B2 |
| 7548612 | Weissman et al. | Jun 2009 | B2 |
| 7660721 | Williams et al. | Feb 2010 | B2 |
| 7711650 | Kara | May 2010 | B1 |
| 7756796 | Bodie et al. | Jul 2010 | B2 |
| 7778924 | Ananda | Aug 2010 | B1 |
| 7784090 | Lord et al. | Aug 2010 | B2 |
| 7827118 | Smith, III et al. | Nov 2010 | B1 |
| 7831518 | Montgomery et al. | Nov 2010 | B2 |
| 7831824 | Abdulhayoglu | Nov 2010 | B2 |
| 7840492 | Leung et al. | Nov 2010 | B2 |
| 7882042 | Meyer et al. | Feb 2011 | B2 |
| 7954709 | Leon et al. | Jun 2011 | B1 |
| 7963437 | McBride et al. | Jun 2011 | B1 |
| 8005762 | Ogg et al. | Aug 2011 | B2 |
| 8027927 | Ogg et al. | Sep 2011 | B2 |
| 8027935 | Begen | Sep 2011 | B1 |
| 8041644 | Ogg et al. | Oct 2011 | B2 |
| 8046823 | Begen et al. | Oct 2011 | B1 |
| 8100324 | Leon | Jan 2012 | B1 |
| 8204835 | Ogg | Jun 2012 | B1 |
| 8240579 | Bennett | Aug 2012 | B1 |
| 8255337 | Bennett et al. | Aug 2012 | B1 |
| 8600910 | Kara et al. | Dec 2013 | B2 |
| 8600913 | Williams et al. | Dec 2013 | B2 |
| 8612361 | Bussell et al. | Dec 2013 | B1 |
| 8626673 | Bennett | Jan 2014 | B1 |
| 8775331 | Tsuie et al. | Jul 2014 | B1 |
| 8868472 | Lin et al. | Oct 2014 | B1 |
| 9082234 | Clem | Jul 2015 | B1 |
| 9208620 | Bortnak et al. | Dec 2015 | B1 |
| 9230233 | Sundaresan et al. | Jan 2016 | B1 |
| 9761061 | Bussell et al. | Sep 2017 | B1 |
| 9824380 | Chowdhary et al. | Nov 2017 | B1 |
| 9842308 | Biswas et al. | Dec 2017 | B1 |
| 9922302 | Gventer et al. | Mar 2018 | B2 |
| 20010007086 | Rogers et al. | Jul 2001 | A1 |
| 20010020234 | Shah et al. | Sep 2001 | A1 |
| 20010022060 | Robertson et al. | Sep 2001 | A1 |
| 20010042052 | Leon | Nov 2001 | A1 |
| 20020032573 | Williams et al. | Mar 2002 | A1 |
| 20020032668 | Kohler et al. | Mar 2002 | A1 |
| 20020032784 | Darago et al. | Mar 2002 | A1 |
| 20020052841 | Guthrie et al. | May 2002 | A1 |
| 20020065577 | Teraura et al. | May 2002 | A1 |
| 20020073050 | Gusler et al. | Jun 2002 | A1 |
| 20020082935 | Moore et al. | Jun 2002 | A1 |
| 20020095347 | Cummiskey | Jul 2002 | A1 |
| 20020099652 | Herzen et al. | Jul 2002 | A1 |
| 20020116318 | Thomas et al. | Aug 2002 | A1 |
| 20020143431 | Sansone | Oct 2002 | A1 |
| 20030009425 | Stonedahl et al. | Jan 2003 | A1 |
| 20030029914 | Hortman et al. | Feb 2003 | A1 |
| 20030037008 | Raju et al. | Feb 2003 | A1 |
| 20030050819 | Koenigbauer et al. | Mar 2003 | A1 |
| 20030065739 | Shnier | Apr 2003 | A1 |
| 20030080182 | Gunther | May 2003 | A1 |
| 20030088473 | Fisher et al. | May 2003 | A1 |
| 20030089765 | Kovlakas | May 2003 | A1 |
| 20030101143 | Montgomery et al. | May 2003 | A1 |
| 20030101147 | Montgomery et al. | May 2003 | A1 |
| 20030101148 | Montgomery et al. | May 2003 | A1 |
| 20030130963 | Stickler et al. | Jul 2003 | A1 |
| 20030138345 | Schwabe | Jul 2003 | A1 |
| 20030167241 | Gilham | Sep 2003 | A1 |
| 20030182155 | Nitzan et al. | Sep 2003 | A1 |
| 20030187666 | Leon | Oct 2003 | A1 |
| 20030204477 | McNett | Oct 2003 | A1 |
| 20030217018 | Groff et al. | Nov 2003 | A1 |
| 20030233276 | Pearlman et al. | Dec 2003 | A1 |
| 20030236709 | Hendra et al. | Dec 2003 | A1 |
| 20040002926 | Coffy et al. | Jan 2004 | A1 |
| 20040044586 | Gullo et al. | Mar 2004 | A1 |
| 20040048503 | Mills et al. | Mar 2004 | A1 |
| 20040064422 | Leon | Apr 2004 | A1 |
| 20040083179 | Sesek et al. | Apr 2004 | A1 |
| 20040083189 | Leon | Apr 2004 | A1 |
| 20040089482 | Ramsden et al. | May 2004 | A1 |
| 20040122776 | Sansone | Jun 2004 | A1 |
| 20040122779 | Stickler et al. | Jun 2004 | A1 |
| 20040128264 | Leung et al. | Jul 2004 | A1 |
| 20040185827 | Parks | Sep 2004 | A1 |
| 20040185882 | Gecht et al. | Sep 2004 | A1 |
| 20040186811 | Gullo et al. | Sep 2004 | A1 |
| 20040212833 | Taskett et al. | Oct 2004 | A1 |
| 20040215581 | Lord et al. | Oct 2004 | A1 |
| 20040215583 | Elliott | Oct 2004 | A1 |
| 20040230544 | Herbert | Nov 2004 | A1 |
| 20040254808 | Bennett et al. | Dec 2004 | A1 |
| 20050060165 | Knight et al. | Mar 2005 | A1 |
| 20050065892 | Ryan et al. | Mar 2005 | A1 |
| 20050065896 | Kummer et al. | Mar 2005 | A1 |
| 20050065897 | Ryan et al. | Mar 2005 | A1 |
| 20050071244 | Phillips et al. | Mar 2005 | A1 |
| 20050080751 | Burningham | Apr 2005 | A1 |
| 20050114222 | Mundy | May 2005 | A1 |
| 20050116047 | Lu et al. | Jun 2005 | A1 |
| 20050119786 | Kadaba | Jun 2005 | A1 |
| 20050171791 | Chimenti et al. | Aug 2005 | A1 |
| 20050171869 | Minnocci | Aug 2005 | A1 |
| 20050192899 | Reardon | Sep 2005 | A1 |
| 20050237203 | Burman et al. | Oct 2005 | A1 |
| 20050256811 | Pagel et al. | Nov 2005 | A1 |
| 20050278266 | Ogg et al. | Dec 2005 | A1 |
| 20060000648 | Galtier | Jan 2006 | A1 |
| 20060020505 | Whitehouse | Jan 2006 | A1 |
| 20060122947 | Poulin | Jun 2006 | A1 |
| 20060173700 | Fenelon | Aug 2006 | A1 |
| 20060173796 | Kara | Aug 2006 | A1 |
| 20060173799 | Minnocci | Aug 2006 | A1 |
| 20060213979 | Geller et al. | Sep 2006 | A1 |
| 20060213980 | Geller et al. | Sep 2006 | A1 |
| 20060220298 | Fairweather et al. | Oct 2006 | A1 |
| 20060224462 | Brezenoff | Oct 2006 | A1 |
| 20060229895 | Kodger | Oct 2006 | A1 |
| 20060259390 | Rosenberger | Nov 2006 | A1 |
| 20060282271 | Ananda et al. | Dec 2006 | A1 |
| 20060283943 | Ostrowski et al. | Dec 2006 | A1 |
| 20070011187 | Chitgupakar et al. | Jan 2007 | A1 |
| 20070033110 | Philipp et al. | Feb 2007 | A1 |
| 20070073551 | Williams et al. | Mar 2007 | A1 |
| 20070073587 | Walker et al. | Mar 2007 | A1 |
| 20070078795 | Chatte | Apr 2007 | A1 |
| 20070080228 | Knowles et al. | Apr 2007 | A1 |
| 20070174213 | Whitehouse et al. | Jul 2007 | A1 |
| 20070174215 | Morel | Jul 2007 | A1 |
| 20070198977 | Abernethy et al. | Aug 2007 | A1 |
| 20070255664 | Blumberg et al. | Nov 2007 | A1 |
| 20080103968 | Bies et al. | May 2008 | A1 |
| 20080133659 | Aldrey et al. | Jun 2008 | A1 |
| 20080154781 | Kumar | Jun 2008 | A1 |
| 20080169343 | Skaaksrud et al. | Jul 2008 | A1 |
| 20080281719 | Hall et al. | Nov 2008 | A1 |
| 20090146410 | Uslontsev et al. | Jun 2009 | A1 |
| 20090164392 | Raju et al. | Jun 2009 | A1 |
| 20090172084 | Lavanya et al. | Jul 2009 | A1 |
| 20090172126 | Brennan et al. | Jul 2009 | A1 |
| 20090259513 | Tung | Oct 2009 | A1 |
| 20090265585 | Ikegami | Oct 2009 | A1 |
| 20100076903 | Klingenberg et al. | Mar 2010 | A1 |
| 20100169241 | Schoonmaker et al. | Jul 2010 | A1 |
| 20100179892 | O'Brien et al. | Jul 2010 | A1 |
| 20100235267 | Brookner et al. | Sep 2010 | A1 |
| 20100298662 | Yu et al. | Nov 2010 | A1 |
| 20100312627 | Khechef et al. | Dec 2010 | A1 |
| 20100323722 | Hatami | Dec 2010 | A1 |
| 20110015935 | Montgomery et al. | Jan 2011 | A1 |
| 20110022544 | Kim et al. | Jan 2011 | A1 |
| 20110029429 | Whitehouse | Feb 2011 | A1 |
| 20110071944 | Heiden et al. | Mar 2011 | A1 |
| 20110145107 | Greco | Jun 2011 | A1 |
| 20110173144 | Shan et al. | Jul 2011 | A1 |
| 20110225180 | Liao et al. | Sep 2011 | A1 |
| 20110231334 | Jindel | Sep 2011 | A1 |
| 20110242554 | Farry et al. | Oct 2011 | A1 |
| 20110295646 | Barros | Dec 2011 | A1 |
| 20110317158 | Lyng et al. | Dec 2011 | A1 |
| 20120008766 | Robertson et al. | Jan 2012 | A1 |
| 20120054754 | Teichmann et al. | Mar 2012 | A1 |
| 20120084090 | Woodard et al. | Apr 2012 | A1 |
| 20120109777 | Lipsitz et al. | May 2012 | A1 |
| 20120159603 | Queck | Jun 2012 | A1 |
| 20120216133 | Barker et al. | Aug 2012 | A1 |
| 20120233252 | Vats et al. | Sep 2012 | A1 |
| 20120240204 | Bhatnagar et al. | Sep 2012 | A1 |
| 20120265676 | Gould et al. | Oct 2012 | A1 |
| 20130056533 | Zimberoff et al. | Mar 2013 | A1 |
| 20130061337 | Zimberoff et al. | Mar 2013 | A1 |
| 20130066794 | Hill et al. | Mar 2013 | A1 |
| 20130144763 | Skyberg et al. | Jun 2013 | A1 |
| 20130179361 | Williams et al. | Jul 2013 | A1 |
| 20130254132 | Srinath et al. | Sep 2013 | A1 |
| 20130346249 | Li | Dec 2013 | A1 |
| 20140019517 | Fawcett | Jan 2014 | A1 |
| 20140067665 | Paletz et al. | Mar 2014 | A1 |
| 20140149308 | Ming | May 2014 | A1 |
| 20140208325 | Chen et al. | Jul 2014 | A1 |
| 20140265300 | Jena | Sep 2014 | A1 |
| 20140278099 | Schenken | Sep 2014 | A1 |
| 20140324633 | Pollak et al. | Oct 2014 | A1 |
| 20150046361 | Williams et al. | Feb 2015 | A1 |
| 20160196527 | Bose et al. | Jul 2016 | A1 |
| 20210081890 | Atwood | Mar 2021 | A1 |
| Number | Date | Country |
|---|---|---|
| 2470371 | May 2003 | CA |
| 0137737 | Apr 1985 | EP |
| 0571259 | Nov 1993 | EP |
| 0927958 | Jul 1999 | EP |
| 0927963 | Jul 1999 | EP |
| 1785856 | May 2007 | EP |
| 2580844 | Oct 1986 | FR |
| 2251210 | Jul 1992 | GB |
| 04284558 | Oct 1992 | JP |
| 2000-105845 | Apr 2000 | JP |
| WO-8801818 | Mar 1988 | WO |
| WO-9740472 | Oct 1997 | WO |
| WO-9814907 | Apr 1998 | WO |
| WO-9814909 | Apr 1998 | WO |
| WO-9857302 | Dec 1998 | WO |
| WO-9857460 | Dec 1998 | WO |
| WO-02063517 | Aug 2002 | WO |
| WO-02093498 | Nov 2002 | WO |
| WO-03039051 | May 2003 | WO |
| WO-03083784 | Oct 2003 | WO |
| Entry |
|---|
| Weigand, Hans, Willem-Jan van den Heuvel, and Marcel Hiel. “Rule-based service composition and service-oriented business rule management.” Proceedings of the International Workshop on Regulations Modelling and Deployment (ReMoD'08). Jun. 2008. (Year: 2008). |
| International Search Report and Written Opinion issued for PCT Application No. PCT/US2017/020662, dated May 19, 2017, 14 pages. |
| Ford, C., “Frequent Flyer Programs,” Australian Accountant, 63,1, Feb. 1993, pp. 52-58, 7 pages. |
| Alexander, K.L., “U.S. Stamps Pay Tribute to Starry-Eyed Jurors,” Final Edition, Calgary Herald, Calgary, Alberta, Canada, Sep. 14, 2007, 2 pages. |
| Non-Final Office Action dated Aug. 3, 2009 for U.S. Appl. No. 11/353,690 to Kara, filed Feb. 14, 2006, and entitled “System and Method for Validating Postage,” 19 pages. |
| “Domestic Mail Manual Section 604,” United States Postal Service, Aug. 31, 2005, 45 pages. |
| “Mobile Postage stamps via text message announced”, http://telecoms.cytalk.com/2011/03/mobile-postage-stamps-via-text-messages-announced/, CY.TALK Telecoms News Blog, Mar. 14, 2011 in Telecoms, Texting, pp. 1-9. |
| Mobile Postage Stamps via Text Messages Announced, Phone Reviews, Mobile Phones, News, Mar. 11, 2011, pp. 1-3. |
| Anonymous, “Automated Indicia Detection System From Parascript Protects Postage Revenue for Postal Operators, Cracks Down on Fraud:—Parascript StampVerify Simplifies Complex Task of Automatically Locating and Verifying Different Types of Indicia on Envelope Images—,” PR Newswire, New York, Sep. 18, 2007, 2 pages. |
| Davies, Brad L. “Printing System for Preventing Injustice by Delivering Print Data from Postal Charge Meter to Printer,” Jan. 2001, 1 page. |
| Unpublished U.S. Appl. No. 12/103,496 to Bortnak et al., filed Apr. 15, 2008 and entitled “Systems and Methods for Activation of Postage Indicia at Point of Sale,” 40 pages. |
| Unpublished U.S. Appl. No. 11/509,309 to Leon, filed Aug. 24, 2006 and entitled “Invisible Fluorescent Ink Mark,” 15 pages. |
| Unpublished U.S. Appl. No. 12/030,739 to McBride et al., filed Feb. 13, 2008 and entitled “Systems and Methods for Distributed Activation of Postage,” 35 pages. |
| Unpublished U.S. Appl. No. 11/323,463 to Leon et al., filed Dec. 30, 2005 and entitled “Systems and Methods for Single Pass Printing Postage Indicia,” 23 pages. |
| Unpublished U.S. Appl. No. 10/606,579 to Ogg, filed Jun. 26, 2003 and entitled “System and Method for Automatically Processing Mail,” 15 pages. |
| “Endicia Releases Unique Return Shipping Solution,” retrieved from http://www.endicia.com/about-us/press-room/20140610, last accessed May 13, 2015, Jun. 10, 2014, 2 pages. |
| “Return Shipping Labels—Simplify Product Returns Without the Extra Cost of Accounts & Permits,” retrieved from http://www.endicia.com/Features/ReturnShippingLabels/, last accessed May 13, 2015, undated, 2 pages. |
| “Newgistics: Offering Reverse Logistics to Easily Manage Returns,” retrieved from http://www.newgistics.com/corp_returns/#newgisticssmartlabelandshipmentmanager, last accessed May 13, 2015, undated, 5 pages. |
| “E-Commerce Technology—The Most Modular and Scalable E-Commerce Platform that Grows With Your Business,” http://www.newgistics.com/corp_ecommerce/index.aspx, last accessed May 13, 2015, undated, 6 pages. |
| “Returns Made Easy,” retrieved from <https://www.usps.com/returns/>, last accessed May 13, 2015, undated, 5 pages. |
| “Return Services & Options for Parcels,” retrieved from https://www.usps.com/business/return-services.htm, last accessed May 13, 2015, undated, 6 pages. |
| Unpublished U.S. Appl. No. 13/647,001 to Yoggi, filed Oct. 8, 2012 and entitled “Systems and Methods for Providing Shipping Service Guarantees,” 44 pages. |
| Unpublished U.S. Appl. No. 12/316,542 to Leon, filed Dec. 9, 2008 and entitled “Mail Piece Processing,” 74 pages. |
| Unpublished U.S. Appl. No. 13/705,935 to McBride, filed Dec. 5, 2012 and entitled “Visual Graphic Tracking of Item Shipment and Delivery,” 62 pages. |
| Unpublished U.S. Appl. No. 13/828,800 to Atkinson, filed Mar. 14, 2013 and entitled “Systems and Methods for Mail Piece Interception, Rescue Tracking, and Confiscation Alerts and Related Services,” 63 pages. |
| International Search Report issued for PCT/US95/00237, dated May 29, 1995, 4 pages. |
| Examination Report No. 1 issued for Australian Patent Application No. 2017228918, dated Jun. 28, 2019, 4 pages. |
| Grabara, J. et al. “The Role of Information Systems in Transport Logistics” International Journal of Education and Research, vol. 2, No. 2, Feb. 2014, 8 pages. |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15064218 | Mar 2016 | US |
| Child | 16691143 | US |
