WO2002021399A1 - Automated requesting system - Google Patents

Automated requesting system Download PDF

Info

Publication number
WO2002021399A1
WO2002021399A1 PCT/US2001/027696 US0127696W WO0221399A1 WO 2002021399 A1 WO2002021399 A1 WO 2002021399A1 US 0127696 W US0127696 W US 0127696W WO 0221399 A1 WO0221399 A1 WO 0221399A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
shipping
product
report
location
Prior art date
Application number
PCT/US2001/027696
Other languages
French (fr)
Inventor
Christopher Patrick Tighe
Original Assignee
United States Postal Service
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by United States Postal Service filed Critical United States Postal Service
Priority to AU2001287122A priority Critical patent/AU2001287122A1/en
Priority to US10/363,734 priority patent/US20040039652A1/en
Publication of WO2002021399A1 publication Critical patent/WO2002021399A1/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/08Logistics, e.g. warehousing, loading or distribution; Inventory or stock management

Definitions

  • This invention relates to processing shipping information, more particularly, to automating the processing of shipping information using a system.
  • a business that sells products often must transport products from a warehouse to a customer's specified address, e.g., a home or business. After a sale and before the recipient receives the product, the business must contact a warehouse that stores the product and contact a delivery service to pick-up and process the product for delivery.
  • the delivery service must determine the size of the product in the request to efficiently dispatch delivery vehicles to pick-up and transport the products.
  • Each of these stages may require a manual process to enter the pick-up and destination address of the product, and to enter relevant information concerning the product to be transported.
  • the business may also maintain and update a customer service database with the sales information in the request to serve the customer. At each manual step, time may be lost in efficiently transporting the product, and human error can lead to inefficient allocation of resources.
  • a business may have a sales team who sells products "on the road," that is, away from a sales office.
  • a sales team member calls, emails, or faxes a request back to the sales office.
  • Another employee creates shipping labels for the request and calls a warehouse regarding the request.
  • An employee at the warehouse calls the United States Postal Service ("USPS") district office to request pick-up of the request.
  • USPS United States Postal Service
  • the employee at the warehouse may also use a computer to create shipping labels used during shipping. This process involves reentering relevant shipping information at regular stages along the shipping process.
  • a customer may buy a product over the Internet using an automated requesting process. This will also require the warehouse that stores the products to contact the delivery service to pick-up the request.
  • a method for processing shipping a physical object comprising receiving a request for a product at a processing location; generating a report that includes shipping information and identifying information of the product based on the received request; and automatically transmitting the report to a shipper location for shipping of the product.
  • Figure 1 illustrates a system in which embodiments consistent with the present invention may be implemented
  • Figure 2 illustrates a more detailed view of the server shown in Figure 1 ;
  • FIG. 3 illustrates a flowchart in accordance with embodiments consistent with the present invention.
  • Figure 4 illustrates a possible embodiment of label information.
  • FIG. 1 illustrates a system 100 in which embodiments consistent with the present invention may be implemented.
  • System 100 includes a client computer 105, a shipper client computer 107, a distributor client computer 109, and a server computer 110 connected across a network 102.
  • Network 102 may be, for example the Internet, a wide area network, or local area network.
  • System 100 may also include multiple networks.
  • client 105, shipper client 107, and distributor client 109 are described as interconnected to server 110 via network 102, they may also be interconnected via separate networks.
  • Each device may be connected to network 102 in a variety of ways, including but not limited to, an Ethernet connection, a wireless technology, or a cable modem.
  • each device may be interconnected via other intermediate devices or network elements, such as a hub, router, switch, firewall, etc.
  • intermediate devices or network elements such as a hub, router, switch, firewall, etc.
  • a user may use client 105 at a requesting location to enter a request for a product to be shipped.
  • the user may be a consumer, a seller, an agent for a seller, or some other individual.
  • a requesting location may be, for example, a personal computer in an individual's home, a workstation in a retail store front operated by a store employee, a portable computer operated by a member of a sales team who conducts sales away "on the road," or any place client 105 can transmit data to server 110.
  • a product may be, for example, a bag of corn, a skirt, a book, or any physical object.
  • Client 105 transmits the request to server 110.
  • the request may include, for example: an identification — e.g., style number — of a product to be shipped; the weight and size of the product to be shipped; pick-up information — e.g., the physical address of the product from where it is to be shipped; destination information for the product to be shipped; the type of delivery service desired; and other information that enables shipping of a product.
  • the request may also be supplemented with information from a variety of sources. For example, a destination address stored in memory at server 110 may be added to the request, using the destination information.
  • Client 105 may also provide customer service information to server 110 in addition to the request.
  • the customer service information may include the name and address of the customer, the name of the recipient, the destination location, an identification of the product requested, or the type of delivery service desired.
  • Client 105 may be implemented using any suitable combination of hardware and software.
  • client 105 may be implemented as a personal computer including a processor, an I/O device, and a memory.
  • the processor may be, for example, a Pentium microprocessor or a SPARC processor.
  • the I/O device may facilitate connecting, for example, a mouse, a monitor, and a keyboard to client 105 or connecting client 105 to network 102.
  • Client 105 may use a web browser such as, Microsoft Internet Explorer or Netscape Communicator.
  • client 105 may be implemented in any device capable of transmitting or receiving data, including but not limited to a cellular telephone, an electronic pager, or a personal digital assistant.
  • Server 110 may be implemented using any suitable combination of hardware and software.
  • Server 110 may be implemented as a personal computer including a processor, an I/O device, and a memory.
  • the processor may be, for example, a Pentium microprocessor or a SPARC processor.
  • the I/O device may facilitate connecting,
  • Server 110 receives the request transmitted from client 105.
  • Server 110 may be located at a processing location, for example, at a seller's place of business, a warehouse, a storage facility, or a remote location to be accessed by another computer. Alternatively, if client 105 and server 110 are located at the same location, client 105 and server 110 may be integrated, thus allowing the user to enter the request directly into server 110.
  • server 110 compiles the received request; generates label information to enable printing of a shipping label; generates a report; updates a database; and determines the nearest shipper to the storage location, and automatically (without human intervention) transmits the report to that shipper.
  • Server 110 may transmit the label information to distributor client
  • Whether the label information is transmitted to distributor client 109 across network 102 may depend on whether server 110 is located at the same location as distributor client 109. If server 110 and distributor client 109 are at the same location, the label information may be provided to distributor client 109 directly, e.g., via a local area network, or server
  • server 110 and distributor client 105 may be integrated. If server 110 and distributor client 109 are not at the same location, the label information may be transmitted to distributor client 109 across network 102.
  • the label information generated by server 110 may include human and machine readable shipping information to enable shipping of a product.
  • the human readable shipping information identifies a particular product style to be shipped, allows a human to associate the label with a particular unit of the identified product, and may include such information as the destination location.
  • the machine readable shipping information allows a machine to recognize the particular unit as the product to be shipped and relevant shipping information, including, but not limited to, the destination location and the type of delivery service.
  • a possible embodiment of the label information is illustrated in Figure 4.
  • Server 110 may generate a report and transmit the report to shipper client 107 across network 102, thus enabling a shipping provider, such as the United States Postal Service ("USPS"), to initiate the physical shipment of one or more products referenced in the report.
  • the report generated by server 110 may include information for one or more labels, as well as additional information. That is, the report allows the shipping provider to identify at least the particular unit and pick-up location of the unit, and may identify the destination location, the type of delivery service, and resources needed — e.g., size of truck — to ship the product.
  • the report may also be verified and supplemented by the information provided in the label, which the shipping provider may scan after the product has been provided to the shipping provider.
  • Server 110 may be implemented in any suitable combination of hardware and software. One possible embodiment may be found below with reference to Figure 2.
  • Shipper client 107 receives the report transmitted from server 110. Shipper client 107 may determine resource information for delivery of the product based on information provided in the report, such as the pick-up location of a product, destination location, identifying description of the product, and the size and weight of the product to be shipped.
  • the resource information may include the size of a vehicle needed to pick-up and retrieve one or more products with an associated label, the necessary manpower to load the vehicle, and an estimated amount of time to complete the task.
  • Shipper client 107 may receive the report at a shipper location, which may be, for example, the shipping service's place of business or a remote location accessed by a computer located at the place of business.
  • Shipper client 107 may be implemented using any suitable combination of hardware and software.
  • shipper client 107 may be implemented as a personal computer or workstation including a processor, an I/O device, and a memory.
  • the processor may be, for example, a Pentium microprocessor or a SPARC processor.
  • the I/O device may facilitate connecting, for example, a mouse, a monitor, and a keyboard to shipper client 107 or connecting shipper client 107 to network 102.
  • Distributor client 109 receives the label information transmitted from server 110 and prints a label based on the received information.
  • Distributor client 109 may receive the label information at a storage location, which may be a distributor's place of business or a remote location accessed by another computer located at the place of business.
  • Distributor client 109 may be implemented using any suitable combination of hardware or software.
  • distributor client 109 may be implemented as a computer including a processor, an I/O device, and a memory.
  • the processor may be, for example, a Pentium microprocessor or a SPARC processor.
  • the I/O device may facilitate connecting, for example, a mouse, a monitor, and a keyboard to distributor client 109 or connecting distributor client 109 to a network 102.
  • FIG. 2 illustrates a more detailed view of server 110 shown in Figure 1.
  • server 110 comprises a processor 280, an I/O device 290, and a memory 270.
  • Processor 280 may be, for example, a Pentium microprocessor or a SPARC processor and may be used to process data, e.g., data received in a request from client 105.
  • I/O device 290 may facilitate connecting, for example, a mouse, a monitor, and a keyboard to a server, or for connecting server 110 to a network 102.
  • Memory 270 stores a computer program 250 and a database 260, such as a customer service database.
  • Computer program 250 may be stored on a CD-ROM, which is accessed by memory 270.
  • Computer program 250 may include program code for a web browser to display information on a web page.
  • the program code may be written in, for example, hypertext markup language or extensible markup language.
  • Computer program 250 compiles information received in the request from client 105 to generate a report to transmit to the shipper client 107 and to generate a label to transmit to distributor client 109 to be associated with a product.
  • Computer program 250 may also update database 260.
  • One skilled in the art will recognize that computer program 250 may also be implemented as multiple computer programs.
  • client 105 components stored in memories of client 105, server 110, shipper client 107, and distributor client 109 may be stored elsewhere in the device or on other devices connected to network 102.
  • FIG. 3 illustrates a flowchart of a method consistent with the present invention.
  • Client 105 transmits a request to server 110 (step 300).
  • client 105 may connect to server 110 via network 102 to provide the request.
  • a user operating client 105 may browse a web site and select a product to buy — i.e., request a product.
  • Client 105 then transmits that request to server 110 via a web page request.
  • the user operating client 105 may select a product according to any method known to those skilled in the art.
  • Server 110 may also request that client 105 provide shipping information. Although the request is described as being a sales transaction, the request may initiate any transaction that requires shipping a product, for example, a lease of a lawnmower.
  • Client 105 may transmit the request either remotely or locally (e.g., over the Internet or an intranet, respectively).
  • the request may include shipping information such as an identification of the product to be shipped; the quantity, size, and weight of the product; the destination location of the product; the shipping provider and the type of delivery service desired.
  • the shipping provider may be, for example, the USPS, although the invention is equally applicable to other shipping providers.
  • the type of delivery service may include, for example, Express, overnight, first class, registered, returned receipt requested, or air mail. Additional information may be stored on server 110.
  • server 110 Upon receiving the request from client 105, server 110 generates label information (step 305). That is, server 110 may generate label information by processing the shipping information transmitted in the request and, when appropriate, by processing additional information retrieved from database 260 to generate the label information. The additional information may be retrieved if it is not provided in the request.
  • the additional information stored in database 260 may include the pick-up location of the product to be shipped, the size of the product, the weight of the product, the destination location, and personal information of the addressee. The additional information may also retrieved from elsewhere in memory 270.
  • Label information may include a bar code that uniquely identifies the product being shipped, identifies the type of service desired, and provides error checking.
  • the bar code associated with a product allows the product to be tracked until delivery at its destination location.
  • server 110 After generating the label information, server 110 transmits the label information to distributor client 109.
  • the label information may be automatically (without human intervention) transmitted to distributor client 109.
  • distributor client 109 receives the label information, a label based on the received information may be printed.
  • the label may then be associated with the unit of the product to be shipped. For example, associating the label may include attaching the label to a package containing the product to be shipped.
  • Server 110 may then update database 260 (step 310).
  • Updating database 260 may include storing information provided in the request, such as the name and address of the customer, the name and address of the recipient, the product requested, and the type of delivery service desired. Although steps 305 and 310 are indicated to occur consecutively, they may also occur simultaneously.
  • Server 110 may compile and transmit a report to shipper client 107 (step 315).
  • the report may be compiled and transmitted instantaneously upon receipt of the request, periodically (including but not limited to, after one minute, after ten minutes, after one hour, or once daily), or upon reaching some preset value (including but not limited to, when the gross weight of a product is equal to or over a fixed weight, when the number of products reaches a particular number greater than or equal to one, when the number of products to be shipped via a specified delivery type reaches a particular number greater than or equal to one, or when a specified monetary value in a product has been reached).
  • Shipper client 107 allocates resources based on the report, which allows the shipping provider to pick-up one or more products with an associated label from the pick-up location (step 320).
  • the report may indicate the size of a vehicle needed to pick-up and retrieve one or more products with an associated label, the necessary manpower to load the vehicle, and an estimated amount of time to complete the task.
  • the shipping provider may then dispatch vehicles accordingly.
  • the shipping provider retrieves one or more products with an associated label from the pick-up location.
  • the shipping provider may return to a central shipping and distribution center with one or more products, each having an associated label to scan and to distribute further one or more products with an associated label according to type of delivery service desired and destination location. For example, packages labeled for Express service will be properly sorted for faster delivery than those packages designated for normal service.

Abstract

An automated requesting system that processes shipping information (Fig. 1), which comprises receiving a request for a product at a processing location (110); generating a report that includes shipping information and identifying information of the product based on the received request; and automatically transmitting the report to a shipper location (107) for shipping of the product.

Description

AUTOMATED REQUESTING SYSTEM
DESCRIPTION OF THE INVENTION
Reference to Related Applications
[001] This application claims the benefit of priority under 35 U.S.C. § 119 from co-pending prior provisional application Serial No. 60/231 ,321, filed September 8, 2000 for "AUTOMATED ORDERING SYSTEM," which is incorporated herein by reference.
Field of the Invention
[002] This invention relates to processing shipping information, more particularly, to automating the processing of shipping information using a system.
Background of the Invention
[003] A business that sells products often must transport products from a warehouse to a customer's specified address, e.g., a home or business. After a sale and before the recipient receives the product, the business must contact a warehouse that stores the product and contact a delivery service to pick-up and process the product for delivery. The delivery service must determine the size of the product in the request to efficiently dispatch delivery vehicles to pick-up and transport the products. Each of these stages may require a manual process to enter the pick-up and destination address of the product, and to enter relevant information concerning the product to be transported. The business may also maintain and update a customer service database with the sales information in the request to serve the customer. At each manual step, time may be lost in efficiently transporting the product, and human error can lead to inefficient allocation of resources.
[004] A business may have a sales team who sells products "on the road," that is, away from a sales office. A sales team member calls, emails, or faxes a request back to the sales office. Another employee creates shipping labels for the request and calls a warehouse regarding the request. An employee at the warehouse calls the United States Postal Service ("USPS") district office to request pick-up of the request. The employee at the warehouse may also use a computer to create shipping labels used during shipping. This process involves reentering relevant shipping information at regular stages along the shipping process.
[005] In another scenario, a customer may buy a product over the Internet using an automated requesting process. This will also require the warehouse that stores the products to contact the delivery service to pick-up the request.
[006] it is accordingly desirable to automate requesting and shipping procedures.
SUMMARY
[007] In accordance with the invention, a method for processing shipping a physical object is claimed, comprising receiving a request for a product at a processing location; generating a report that includes shipping information and identifying information of the product based on the received request; and automatically transmitting the report to a shipper location for shipping of the product.
[008] It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed. The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate one embodiment of the invention and together with the description, serve to explain the principles of the invention.
BRIEF DESCRIPTION OF THE DRAWINGS
[009] Figure 1 illustrates a system in which embodiments consistent with the present invention may be implemented;
[010] Figure 2 illustrates a more detailed view of the server shown in Figure 1 ;
[011] Figure 3 illustrates a flowchart in accordance with embodiments consistent with the present invention; and
[012] Figure 4 illustrates a possible embodiment of label information.
DESCRIPTION OF THE EMBODIMENTS
[013] Reference will now be made in detail to an embodiment consistent with the invention, an example of which is illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts. [014] Figure 1 illustrates a system 100 in which embodiments consistent with the present invention may be implemented. System 100 includes a client computer 105, a shipper client computer 107, a distributor client computer 109, and a server computer 110 connected across a network 102. Network 102 may be, for example the Internet, a wide area network, or local area network. System 100 may also include multiple networks. Although client 105, shipper client 107, and distributor client 109, are described as interconnected to server 110 via network 102, they may also be interconnected via separate networks. Each device may be connected to network 102 in a variety of ways, including but not limited to, an Ethernet connection, a wireless technology, or a cable modem. For example, each device may be interconnected via other intermediate devices or network elements, such as a hub, router, switch, firewall, etc. Although the invention is described with respect to a system interconnection, it is equally applicable to a connection of two or more computers.
[015] Client 105
[016] A user (not shown) may use client 105 at a requesting location to enter a request for a product to be shipped. The user may be a consumer, a seller, an agent for a seller, or some other individual. A requesting location may be, for example, a personal computer in an individual's home, a workstation in a retail store front operated by a store employee, a portable computer operated by a member of a sales team who conducts sales away "on the road," or any place client 105 can transmit data to server 110. A product may be, for example, a bag of corn, a skirt, a book, or any physical object. Client 105 transmits the request to server 110. The request may include, for example: an identification — e.g., style number — of a product to be shipped; the weight and size of the product to be shipped; pick-up information — e.g., the physical address of the product from where it is to be shipped; destination information for the product to be shipped; the type of delivery service desired; and other information that enables shipping of a product. The request may also be supplemented with information from a variety of sources. For example, a destination address stored in memory at server 110 may be added to the request, using the destination information. Client 105 may also provide customer service information to server 110 in addition to the request. For example, the customer service information may include the name and address of the customer, the name of the recipient, the destination location, an identification of the product requested, or the type of delivery service desired.
[017] Client 105 may be implemented using any suitable combination of hardware and software. For example, client 105 may be implemented as a personal computer including a processor, an I/O device, and a memory. The processor may be, for example, a Pentium microprocessor or a SPARC processor. The I/O device may facilitate connecting, for example, a mouse, a monitor, and a keyboard to client 105 or connecting client 105 to network 102. Client 105 may use a web browser such as, Microsoft Internet Explorer or Netscape Communicator. Moreover, client 105 may be implemented in any device capable of transmitting or receiving data, including but not limited to a cellular telephone, an electronic pager, or a personal digital assistant. [018] Server 110
[019] Server 110 receives the request transmitted from client 105. Server 110 may be located at a processing location, for example, at a seller's place of business, a warehouse, a storage facility, or a remote location to be accessed by another computer. Alternatively, if client 105 and server 110 are located at the same location, client 105 and server 110 may be integrated, thus allowing the user to enter the request directly into server 110. Upon receiving the request, server 110 compiles the received request; generates label information to enable printing of a shipping label; generates a report; updates a database; and determines the nearest shipper to the storage location, and automatically (without human intervention) transmits the report to that shipper.
[020] Server 110 may transmit the label information to distributor client
109 across network 102. Whether the label information is transmitted to distributor client 109 across network 102 may depend on whether server 110 is located at the same location as distributor client 109. If server 110 and distributor client 109 are at the same location, the label information may be provided to distributor client 109 directly, e.g., via a local area network, or server
110 and distributor client 105 may be integrated. If server 110 and distributor client 109 are not at the same location, the label information may be transmitted to distributor client 109 across network 102.
[021] The label information generated by server 110 may include human and machine readable shipping information to enable shipping of a product. The human readable shipping information identifies a particular product style to be shipped, allows a human to associate the label with a particular unit of the identified product, and may include such information as the destination location. The machine readable shipping information allows a machine to recognize the particular unit as the product to be shipped and relevant shipping information, including, but not limited to, the destination location and the type of delivery service. A possible embodiment of the label information is illustrated in Figure 4.
[022] Server 110 may generate a report and transmit the report to shipper client 107 across network 102, thus enabling a shipping provider, such as the United States Postal Service ("USPS"), to initiate the physical shipment of one or more products referenced in the report. The report generated by server 110 may include information for one or more labels, as well as additional information. That is, the report allows the shipping provider to identify at least the particular unit and pick-up location of the unit, and may identify the destination location, the type of delivery service, and resources needed — e.g., size of truck — to ship the product. The report may also be verified and supplemented by the information provided in the label, which the shipping provider may scan after the product has been provided to the shipping provider.
[023] Server 110 may be implemented in any suitable combination of hardware and software. One possible embodiment may be found below with reference to Figure 2.
[024] Shipper client 107
[025] Shipper client 107 receives the report transmitted from server 110. Shipper client 107 may determine resource information for delivery of the product based on information provided in the report, such as the pick-up location of a product, destination location, identifying description of the product, and the size and weight of the product to be shipped. The resource information may include the size of a vehicle needed to pick-up and retrieve one or more products with an associated label, the necessary manpower to load the vehicle, and an estimated amount of time to complete the task. Shipper client 107 may receive the report at a shipper location, which may be, for example, the shipping service's place of business or a remote location accessed by a computer located at the place of business.
[026] Shipper client 107 may be implemented using any suitable combination of hardware and software. For example, shipper client 107 may be implemented as a personal computer or workstation including a processor, an I/O device, and a memory. The processor may be, for example, a Pentium microprocessor or a SPARC processor. The I/O device may facilitate connecting, for example, a mouse, a monitor, and a keyboard to shipper client 107 or connecting shipper client 107 to network 102.
[027] Distributor client 109
[028] Distributor client 109 receives the label information transmitted from server 110 and prints a label based on the received information. Distributor client 109 may receive the label information at a storage location, which may be a distributor's place of business or a remote location accessed by another computer located at the place of business. [029] Distributor client 109 may be implemented using any suitable combination of hardware or software. For example, distributor client 109 may be implemented as a computer including a processor, an I/O device, and a memory. The processor may be, for example, a Pentium microprocessor or a SPARC processor. The I/O device may facilitate connecting, for example, a mouse, a monitor, and a keyboard to distributor client 109 or connecting distributor client 109 to a network 102.
[030] Figure 2 illustrates a more detailed view of server 110 shown in Figure 1. As shown in Figure 2, server 110 comprises a processor 280, an I/O device 290, and a memory 270. Processor 280 may be, for example, a Pentium microprocessor or a SPARC processor and may be used to process data, e.g., data received in a request from client 105. I/O device 290 may facilitate connecting, for example, a mouse, a monitor, and a keyboard to a server, or for connecting server 110 to a network 102. Memory 270 stores a computer program 250 and a database 260, such as a customer service database. Computer program 250 may be stored on a CD-ROM, which is accessed by memory 270.
[031] Computer program 250 may include program code for a web browser to display information on a web page. The program code may be written in, for example, hypertext markup language or extensible markup language. Computer program 250 compiles information received in the request from client 105 to generate a report to transmit to the shipper client 107 and to generate a label to transmit to distributor client 109 to be associated with a product. Computer program 250 may also update database 260. One skilled in the art will recognize that computer program 250 may also be implemented as multiple computer programs.
[032] One skilled in the art will also recognize that components stored in memories of client 105, server 110, shipper client 107, and distributor client 109 may be stored elsewhere in the device or on other devices connected to network 102.
[033] Figure 3 illustrates a flowchart of a method consistent with the present invention. Client 105 transmits a request to server 110 (step 300). For example, client 105 may connect to server 110 via network 102 to provide the request. A user operating client 105 may browse a web site and select a product to buy — i.e., request a product. Client 105 then transmits that request to server 110 via a web page request. The user operating client 105 may select a product according to any method known to those skilled in the art. Server 110 may also request that client 105 provide shipping information. Although the request is described as being a sales transaction, the request may initiate any transaction that requires shipping a product, for example, a lease of a lawnmower.
[034] Client 105 may transmit the request either remotely or locally (e.g., over the Internet or an intranet, respectively). The request may include shipping information such as an identification of the product to be shipped; the quantity, size, and weight of the product; the destination location of the product; the shipping provider and the type of delivery service desired. The shipping provider may be, for example, the USPS, although the invention is equally applicable to other shipping providers. The type of delivery service may include, for example, Express, overnight, first class, registered, returned receipt requested, or air mail. Additional information may be stored on server 110.
[035] Upon receiving the request from client 105, server 110 generates label information (step 305). That is, server 110 may generate label information by processing the shipping information transmitted in the request and, when appropriate, by processing additional information retrieved from database 260 to generate the label information. The additional information may be retrieved if it is not provided in the request. The additional information stored in database 260 may include the pick-up location of the product to be shipped, the size of the product, the weight of the product, the destination location, and personal information of the addressee. The additional information may also retrieved from elsewhere in memory 270.
[036] Label information may include a bar code that uniquely identifies the product being shipped, identifies the type of service desired, and provides error checking. The bar code associated with a product allows the product to be tracked until delivery at its destination location.
[037] After generating the label information, server 110 transmits the label information to distributor client 109. The label information may be automatically (without human intervention) transmitted to distributor client 109. After distributor client 109 receives the label information, a label based on the received information may be printed. The label may then be associated with the unit of the product to be shipped. For example, associating the label may include attaching the label to a package containing the product to be shipped.
[038] Server 110 may then update database 260 (step 310). Updating database 260 may include storing information provided in the request, such as the name and address of the customer, the name and address of the recipient, the product requested, and the type of delivery service desired. Although steps 305 and 310 are indicated to occur consecutively, they may also occur simultaneously.
[039] Server 110 may compile and transmit a report to shipper client 107 (step 315). The report may be compiled and transmitted instantaneously upon receipt of the request, periodically (including but not limited to, after one minute, after ten minutes, after one hour, or once daily), or upon reaching some preset value (including but not limited to, when the gross weight of a product is equal to or over a fixed weight, when the number of products reaches a particular number greater than or equal to one, when the number of products to be shipped via a specified delivery type reaches a particular number greater than or equal to one, or when a specified monetary value in a product has been reached).
[040] Shipper client 107 allocates resources based on the report, which allows the shipping provider to pick-up one or more products with an associated label from the pick-up location (step 320). The report may indicate the size of a vehicle needed to pick-up and retrieve one or more products with an associated label, the necessary manpower to load the vehicle, and an estimated amount of time to complete the task. The shipping provider may then dispatch vehicles accordingly. The shipping provider retrieves one or more products with an associated label from the pick-up location. The shipping provider may return to a central shipping and distribution center with one or more products, each having an associated label to scan and to distribute further one or more products with an associated label according to type of delivery service desired and destination location. For example, packages labeled for Express service will be properly sorted for faster delivery than those packages designated for normal service.
[041] Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.

Claims

WHAT IS CLAIMED IS:
1. A method for processing information for shipping a product, comprising: transmitting a request for a product from a requesting location; receiving the request at a processing location; generating a report at the processing location, the report including shipping information and identifying information of the product based on the received request; and automatically transmitting the report to a shipper location for shipping of the product.
2. The method of claim 1 wherein the report further comprises information stored at the processing location.
3. The method of claim 1 , further comprising determining the resources needed to ship at a processing location based on the received request.
4. The method of claim 1 , wherein the generating a report step is performed once per day.
5. The method of claim 1 , further comprising updating a database at a processing location based on the received request.
6. The method of claim 1 , wherein the generating step further comprises generating the report based on additional information stored in memory at the processing location.
7. The method of claim 1 further comprising generating label information at the processing location, the label information including human readable and machine readable shipping information, and automatically transmitting the label information to a storage location for shipping of the product.
8. The method of claim 7 further comprising printing a label based on the label information received at the storage location; and associating the label with the requested product.
9. The method of claim 7, wherein the generating label information step further comprises generating label information based on additional information stored in memory at the processing location.
10. A method for processing information for shipping a product, comprising: receiving a request for a product at a processing location; generating a report that includes shipping information and identifying information of the product based on the received request; and automatically transmitting the report to a shipper location for shipping of the product.
11. A method for processing information for shipping a product, comprising; automatically receiving a report at a shipper location, the report generated at a processing location and including shipping information and identifying information of the product based on a received request for the product at a processing location; and allocating resources based on the shipping information and identifying information in the received report.
12. A method for processing information for shipping a product, comprising; automatically receiving label information at a storage location, the label information generated at a processing location and including human readable and machine readable shipping and product identifying information; accessing the product based on the identifying information; and preparing the product for shipment in accordance with the label information.
13. A method of processing shipping packages, comprising: establishing an automated entry system via the Internet; receiving a plurality of shipping requests via the automated entry system; determining the size of a resource to efficiently handle the shipping packages represented by the shipping requests; and allocating the resource to company to ship the packages.
14. A computer-readable medium containing information for controlling a data processing system to perform a method for processing shipping packages, said method comprising the steps of: automatically receiving a report at a shipper location, the report generated at a processing location and including shipping information and identifying information of the product based on a received request for the product at a processing location; allocating resources based on the shipping information and identifying information in the received report.
5. A processing shipping packages system, comprising: a memory having program information; and a processor responsive to the program information to: automatically receiving a report at a shipper location, the report generated at a processing location and including shipping information and identifying information of the product based on a received request for the product at a processing location; allocating resources based on the shipping information and identifying information in the received report.
PCT/US2001/027696 2000-09-08 2001-09-07 Automated requesting system WO2002021399A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
AU2001287122A AU2001287122A1 (en) 2000-09-08 2001-09-07 Automated requesting system
US10/363,734 US20040039652A1 (en) 2001-09-07 2001-09-07 Automated requesting system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US23132100P 2000-09-08 2000-09-08
US60/231,321 2000-09-08

Publications (1)

Publication Number Publication Date
WO2002021399A1 true WO2002021399A1 (en) 2002-03-14

Family

ID=22868729

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2001/027696 WO2002021399A1 (en) 2000-09-08 2001-09-07 Automated requesting system

Country Status (2)

Country Link
AU (1) AU2001287122A1 (en)
WO (1) WO2002021399A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100450009C (en) * 2003-06-17 2009-01-07 华为技术有限公司 Method for distributing universal label of network node
WO2019100979A1 (en) * 2017-11-23 2019-05-31 菜鸟智能物流控股有限公司 Method for processing item sorting scheduling request, and related device

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5694551A (en) * 1993-05-20 1997-12-02 Moore Business Forms, Inc. Computer integration network for channeling customer orders through a centralized computer to various suppliers
US5758329A (en) * 1993-08-24 1998-05-26 Lykes Bros., Inc. System for managing customer orders and method of implementation
US5870717A (en) * 1995-11-13 1999-02-09 International Business Machines Corporation System for ordering items over computer network using an electronic catalog
US5893076A (en) * 1996-01-16 1999-04-06 Sterling Commerce, Inc. Supplier driven commerce transaction processing system and methodology
US5968110A (en) * 1995-05-12 1999-10-19 Hardware Street, Inc. Method and apparatus for an interactive on line catalog system for facilitating international, cross-border transactions

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5694551A (en) * 1993-05-20 1997-12-02 Moore Business Forms, Inc. Computer integration network for channeling customer orders through a centralized computer to various suppliers
US5758329A (en) * 1993-08-24 1998-05-26 Lykes Bros., Inc. System for managing customer orders and method of implementation
US5968110A (en) * 1995-05-12 1999-10-19 Hardware Street, Inc. Method and apparatus for an interactive on line catalog system for facilitating international, cross-border transactions
US5870717A (en) * 1995-11-13 1999-02-09 International Business Machines Corporation System for ordering items over computer network using an electronic catalog
US5893076A (en) * 1996-01-16 1999-04-06 Sterling Commerce, Inc. Supplier driven commerce transaction processing system and methodology

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100450009C (en) * 2003-06-17 2009-01-07 华为技术有限公司 Method for distributing universal label of network node
WO2019100979A1 (en) * 2017-11-23 2019-05-31 菜鸟智能物流控股有限公司 Method for processing item sorting scheduling request, and related device
US11537967B2 (en) 2017-11-23 2022-12-27 Cainiao Smart Logistics Holding Limited Method for processing item sorting scheduling request, and related device

Also Published As

Publication number Publication date
AU2001287122A1 (en) 2002-03-22

Similar Documents

Publication Publication Date Title
US7069236B1 (en) System and methods to effect return of a consumer product
JP3968243B2 (en) Return method and return system for generating and sending electronic shipping return labels
US8635113B2 (en) Integrated online store
US8756113B2 (en) Methods for automated access to shipping services
US20030195784A1 (en) Intelligent authorized return systems and methods
US20070055586A1 (en) Computer program product, system and methods for tracking supply chain items
US20050114221A1 (en) Systems and methods for using a web portal to integrate into a carrier return system
US20030105704A1 (en) Method and apparatus for facilitating shipment of packages
US20090094082A1 (en) Systems and methods for application programming interfaces for shipping services
US20030233293A1 (en) Warehouse management system and method
KR20020092978A (en) Inventory control system and methods
WO2002073369A2 (en) Systems and methods for initiating returns over a network
US20030195778A1 (en) Intelligent authorized return systems and methods
JP2002109002A (en) Strategic cooperation information management system, operation method therefor, managing program recording medium therefor or slip issuance system, freight management system, physical distribution management system and merchandise management method
US20030135428A1 (en) Internet-based method and system for managing order updates for delivery of goods
US20040039652A1 (en) Automated requesting system
WO2002021399A1 (en) Automated requesting system
JP2003150869A (en) Transportation service with using network and transportation system with using network
JP7123183B2 (en) Systems and methods for interfacing networks using a unified communication scheme
JP2002205821A (en) Customer corresponding type multi-shipment support system using internet and invoice preparation program using internet
CA2422182A1 (en) Methods for automated access to shipping services
WO2003017163A1 (en) System for facilitating transactions between freight customers and service providers
MXPA02000636A (en) Method and system for generating and transmitting electronic shipping return labels.
JP2003076752A (en) Processing method and system for information on palette recovery
AU2007205715A1 (en) Inventory control system and methods

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PH PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

WWE Wipo information: entry into national phase

Ref document number: 10363734

Country of ref document: US

ENP Entry into the national phase

Ref document number: 2003107050

Country of ref document: RU

Kind code of ref document: A

Format of ref document f/p: F

121 Ep: the epo has been informed by wipo that ep was designated in this application
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP