EP2948911A1 - Gestion commandée par le client d'expéditions - Google Patents

Gestion commandée par le client d'expéditions

Info

Publication number
EP2948911A1
EP2948911A1 EP13796181.9A EP13796181A EP2948911A1 EP 2948911 A1 EP2948911 A1 EP 2948911A1 EP 13796181 A EP13796181 A EP 13796181A EP 2948911 A1 EP2948911 A1 EP 2948911A1
Authority
EP
European Patent Office
Prior art keywords
item
customer
service level
delivery
delivery service
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
EP13796181.9A
Other languages
German (de)
English (en)
Other versions
EP2948911A4 (fr
Inventor
Robert Lee Klingenberg
Russell BOWLING
Kristin Lynne Hardesty
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
United Parcel Service of America Inc
United Parcel Service Inc
Original Assignee
United Parcel Service of America Inc
United Parcel Service Inc
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
Priority claimed from US13/746,862 external-priority patent/US20130138573A1/en
Priority claimed from US13/746,854 external-priority patent/US20130212036A1/en
Application filed by United Parcel Service of America Inc, United Parcel Service Inc filed Critical United Parcel Service of America Inc
Publication of EP2948911A1 publication Critical patent/EP2948911A1/fr
Publication of EP2948911A4 publication Critical patent/EP2948911A4/fr
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION 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/00—Administration; Management
    • G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
    • G06Q10/083—Shipping

Definitions

  • embodiments of the present invention provide systems, methods, apparatus, and computer program products for customer controlled management of shipments.
  • a method for changing the delivery service level for at least one item to be delivered by a carrier comprises (A) electronically receiving a request to automatically change a first delivery service level to a second delivery service level for items to be delivered by a carrier in accordance with the first delivery service level, wherein the request is associated with a customer profile; (B) updating the customer profile to reflect the request to automatically change the first delivery service level to the second delivery service level for items to be delivered by the carrier in accordance with the first delivery service level; (C) electronically receiving shipping data corresponding to an item, wherein the shipping data indicates that the item (1) is to be delivered by the carrier in accordance with the first delivery service level and (2) is associated with the customer profile; and (D) automatically changing the first delivery service level to the second delivery service level for the item, wherein (1) changing the first delivery service level to the second delivery service level for the item occurs prior to a first delivery attempt of the item based at least in part on the customer profile and (2) the item is subsequently delivered in accordance
  • a computer program product for changing the delivery service level for at least one item to be delivered by a carrier.
  • the computer program product may comprise at least one computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising executable portions configured to (A) receive a request to automatically change a first delivery service level to a second delivery service level for items to be delivered by a carrier in accordance with the first delivery service level, wherein the request is associated with a customer profile; (B) update the customer profile to reflect the request to automatically change the first delivery service level to the second delivery service level for items to be delivered by the carrier in accordance with the first delivery service level; (C) receive shipping data corresponding to an item, wherein the shipping data indicates that the item (1) is to be delivered by the carrier in accordance with the first delivery service level and (2) is associated with the customer profile; and (D) change the first delivery service level to the second delivery service level for the item, wherein (1) changing the first delivery service level to the second delivery service level for the item occurs
  • an apparatus comprising at least one processor and at least one memory including computer program code.
  • the at least one memory and the computer program code may be configured to, with the processor, cause the apparatus to at least (A) receive a request to automatically change a first delivery service level to a second delivery service level for items to be delivered by a carrier in accordance with the first delivery service level, wherein the request is associated with a customer profile; (B) update the customer profile to reflect the request to automatically change the first delivery service level to the second delivery service level for items to be delivered by the carrier in accordance with the first delivery service level; (C) receive shipping data corresponding to an item, wherein the shipping data indicates that the item (1) is to be delivered by the carrier in accordance with the first delivery service level and (2) is associated with the customer profile; and (D) change the first delivery service level to the second delivery service level for the item, wherein (1) changing the first delivery service level to the second delivery service level for the item occurs prior to a first delivery attempt of the item based at least in
  • a method for changing the delivery service level for at least one item to be delivered by a carrier comprises (A) receiving a request to automatically change a first delivery service level to a second delivery service level for items (1) originating from an identified consignor and (2) to be delivered by a carrier in accordance with the first delivery service level, wherein the request is associated with a customer profile; (B) updating the customer profile to reflect the request to automatically change the first delivery service level to the second delivery service level for items (1) originating from the identified consignor and (2) to be delivered by the carrier in accordance with the first delivery service level; (C) receiving shipping data corresponding to an item, wherein the shipping data indicates that the item (1) is to be delivered by the carrier in accordance with the first delivery service level, (2) is associated with the customer profile, and (3) originates from the identified consignor; and (D) automatically changing the first delivery service level to the second delivery service level for the item, wherein (1) changing the first delivery service level to the second delivery service level for the item occurs
  • a computer program product for changing the delivery service level for at least one item to be delivered by a carrier.
  • the computer program product may comprise at least one computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising executable portions configured to (A) receive a request to automatically change a first delivery service level to a second delivery service level for items (1) originating from an identified consignor and (2) to be delivered by a carrier in accordance with the first delivery service level, wherein the request is associated with a customer profile; (B) update the customer profile to reflect the request to automatically change the first delivery service level to the second delivery service level for items (1) originating from the identified consignor and (2) to be delivered by the carrier in accordance with the first delivery service level; (C) receive shipping data corresponding to an item, wherein the shipping data indicates that the item (1) is to be delivered by the carrier in accordance with the first delivery service level, (2) is associated with the customer profile, and (3) originates from the identified consignor; and (D) change the
  • an apparatus comprising at least one processor and at least one memory including computer program code.
  • the at least one memory and the computer program code may be configured to, with the processor, cause the apparatus to at least (A) receive a request to automatically change a first delivery service level to a second delivery service level for items (1) originating from an identified consignor and (2) to be delivered by a carrier in accordance with the first delivery service level, wherein the request is associated with a customer profile; (B) update the customer profile to reflect the request to automatically change the first delivery service level to the second delivery service level for items (1) originating from the identified consignor and (2) to be delivered by the carrier in accordance with the first delivery service level; (C) receive shipping data corresponding to an item, wherein the shipping data indicates that the item (1) is to be delivered by the carrier in accordance with the first delivery service level, (2) is associated with the customer profile, and (3) originates from the identified consignor; and (D) change the first delivery service level to the second delivery service level for the item, where
  • a method for receiving authorization to deliver at least one item comprises (A) receiving a request to automatically authorize items to be delivered to a customer by a carrier without an in-person signature for items that have corresponding shipping data that indicates that an in-person signature from the customer is requested for delivery, wherein the request is associated with a customer profile; (B) updating the customer profile to reflect the request to automatically authorize items to be delivered to the customer by the carrier without an in-person signature for items that have corresponding shipping data that indicates that an in-person signature from the customer is requested for delivery; (C) receiving shipping data corresponding to an item to be delivered to a customer by a carrier, wherein the shipping data indicates that an in-person signature from the customer is requested for delivery of the item; and (D) automatically updating the shipping data corresponding to the item to indicate that the item is to be delivered to the customer without an in-person signature based at least in part on the customer profile, wherein the item is subsequently delivered without an in-person signature.
  • a computer program product for receiving authorization to deliver at least one item.
  • the computer program product may comprise at least one computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising executable portions configured to (A) receive a request to automatically authorize items to be delivered to a customer by a carrier without an in-person signature for items that have corresponding shipping data that indicates that an in-person signature from the customer is requested for delivery, wherein the request is associated with a customer profile; (B) update the customer profile to reflect the request to automatically authorize items to be delivered to the customer by the carrier without an in-person signature for items that have corresponding shipping data that indicates that an in-person signature from the customer is requested for delivery; (C) receive shipping data corresponding to an item to be delivered to a customer by a carrier, wherein the shipping data indicates that an in-person signature from the customer is requested for delivery of the item; and (D) update the shipping data corresponding to the item to indicate that the item is to be delivered to the customer without an in
  • an apparatus comprising at least one processor and at least one memory including computer program code.
  • the at least one memory and the computer program code may be configured to, with the processor, cause the apparatus to at least (A) receive a request to automatically authorize items to be delivered to a customer by a carrier without an in-person signature for items that have corresponding shipping data that indicates that an in-person signature from the customer is requested for delivery, wherein the request is associated with a customer profile; (B) update the customer profile to reflect the request to automatically authorize items to be delivered to the customer by the carrier without an in-person signature for items that have corresponding shipping data that indicates that an in-person signature from the customer is requested for delivery; (C) receive shipping data corresponding to an item to be delivered to a customer by a carrier, wherein the shipping data indicates that an in-person signature from the customer is requested for delivery of the item; and (D) update the shipping data corresponding to the item to indicate that the item is to be delivered to the customer without an in-person signature based at
  • Fig. 1 is an overview of a system that can be used to practice embodiments of the present invention.
  • Fig. 2 is an exemplary schematic diagram of a carrier system according to one embodiment of the present invention.
  • Fig. 3 is an exemplary schematic diagram of a mobile station according to one embodiment of the present invention.
  • Fig. 4 is a flowchart illustrating operations and processes that can be used in accordance with various embodiments of the present invention.
  • Figs. 5-14, 15A, 15B, 16-18, 19A, 19B, 20-25, 26A, and 26B show exemplary input and output of various embodiments of the present invention.
  • various embodiments may be implemented in various ways, including as methods, apparatus, systems, or computer program products. Accordingly, various embodiments may take the form of an entirely hardware embodiment or an embodiment in which a processor is programmed to perform certain steps. Furthermore, various implementations may take the form of a computer program product on a computer-readable storage medium having computer-readable program instructions embodied in the storage medium. Any suitable computer-readable storage medium may be utilized including hard disks, CD-ROMs, optical storage devices, or magnetic storage devices.
  • These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including computer-readable instructions for implementing the functionality specified in the flowchart block or blocks.
  • the computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions that execute on the computer or other programmable apparatus provide operations for implementing the functions specified in the flowchart block or blocks.
  • blocks of the block diagrams and flowchart illustrations support various combinations for performing the specified functions, combinations of operations for performing the specified functions, and program instructions for performing the specified functions. It should also be understood that each block of the block diagrams and flowchart illustrations, and combinations of blocks in the block diagrams and flowchart illustrations, can be implemented by special purpose hardware-based computer systems that perform the specified functions or operations, or combinations of special purpose hardware and computer instructions. II. Exemplary System Architecture
  • Fig. 1 provides an illustration of a system that can be used in conjunction with various embodiments of the present invention.
  • the system may include one or more carrier systems 100, one or more mobile stations 105, one or more customer computing devices 110, and one or more networks 115.
  • Each of the components of the system may be in electronic communication with, for example, one another over the same or different wireless or wired networks including, for example, a wired or wireless Personal Area Network (PAN), Local Area Network (LAN), Metropolitan Area Network (MAN), Wide Area Network (WAN), or the like.
  • PAN Personal Area Network
  • LAN Local Area Network
  • MAN Metropolitan Area Network
  • WAN Wide Area Network
  • Fig. 1 illustrates certain communication system entities as separate, standalone entities, the various embodiments are not limited to this particular architecture.
  • Fig. 2 provides an exemplary schematic of a carrier system 100 according to one embodiment of the present invention.
  • system may refer to, for example, one or more computers, computing devices, mobile phones, desktops, notebooks or laptops, distributed systems, servers, blades, gateways, switches, processing devices, or combination of processing devices adapted to perform the functions described herein.
  • the carrier system 100 may also comprise various other systems, such as an Address Matching System (AMS), an Internet Membership System (IMS), a Customer Profile System (CPS), a Package Center Information System (PCIS), a Customized Pickup and Delivery System (CPAD), a Web Content Management System (WCMS), a Notification Email System (NES), a Fraud Prevention System (FPS), and a variety of other systems and their corresponding components.
  • AMS Address Matching System
  • IMS Internet Membership System
  • CPS Customer Profile System
  • PCIS Package Center Information System
  • CPAD Customized Pickup and Delivery System
  • WMS Web Content Management System
  • NES Notification Email System
  • FPS Fraud Prevention System
  • the carrier system 100 includes one or more processors 205 that communicate with other elements within the carrier system 100 via a system interface or bus 261.
  • the processor 205 may be embodied in a number of different ways.
  • the processor 205 may be embodied as a processing element, processing circuitry, a coprocessor, a controller or various other processing devices including integrated circuits such as, for example, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a hardware accelerator, or the like.
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the processor 205 may be configured to execute instructions stored in memory or otherwise accessible to the processor 205.
  • the processor 205 may represent an entity capable of performing operations according to embodiments of the present invention when configured accordingly.
  • a display device/input device 264 for receiving and displaying data may also be included in the carrier system 100. This display device/input device 264 may be, for example, a keyboard or pointing device that is used in combination with a monitor.
  • the carrier system 100 may further include transitory and non-transitory memory 263, which may include both random access memory (RAM) 267 and read only memory (ROM) 265.
  • the carrier system's ROM 265 may be used to store a basic input/output system (BIOS) 226 containing the basic routines that help to transfer information to the different elements within the carrier system 100.
  • BIOS basic input/output system
  • the carrier system 100 may include at least one storage device 268, such as a hard disk drive, a CD drive, and/or an optical disk drive for storing information on various computer-readable media.
  • the storage device(s) 268 and its associated computer-readable media may provide nonvolatile storage.
  • the computer- readable media described above could be replaced by any other type of computer-readable media, such as embedded or removable multimedia memory cards (MMCs), secure digital (SD) memory cards, Memory Sticks, electrically erasable programmable read-only memory (EEPROM), flash memory, hard disk, or the like.
  • MMCs embedded or removable multimedia memory cards
  • SD secure digital
  • EEPROM electrically erasable programmable read-only memory
  • flash memory hard disk, or the like.
  • each of these storage devices 268 may be connected to the system bus 261 by an appropriate interface.
  • executable instructions, applications, program modules, and/or the like may be stored by the various storage devices 268 and/or within RAM 267.
  • Such executable instructions, applications, program modules, and/or the like may include an operating system 280, a registration module 270, an alert module 260, a delivery options module 250, and identification module 245.
  • these executable instructions, applications, program modules, and/or the like may control certain aspects of the operation of the carrier system 100 with the assistance of the processor 205 and operating system 280— although their functionality need not be modularized.
  • the carrier system 100 may store or be in communication with one or more databases, such as database 240.
  • a network interface 274 for interfacing with various computing entities (e.g., with one or more mobile stations 105).
  • the carrier system 100 may be able to receive data and/or messages from and transmit data and/or messages to the mobile station 105.
  • This communication may be via the same or different wired or wireless networks (or a combination of wired and wireless networks).
  • the communication may be executed using a wired data transmission protocol, such as fiber distributed data interface (FDDI), digital subscriber line (DSL), Ethernet, asynchronous transfer mode (ATM), frame relay, data over cable service interface specification (DOCSIS), or any other wired transmission protocol.
  • FDDI fiber distributed data interface
  • DSL digital subscriber line
  • Ethernet asynchronous transfer mode
  • ATM asynchronous transfer mode
  • frame relay asynchronous transfer mode
  • DOCSIS data over cable service interface specification
  • the carrier system 100 may be configured to communicate via wireless external communication networks using any of a variety of protocols, such as 802.11, general packet radio service (GPRS), Universal Mobile Telecommunications System (UMTS), Code Division Multiple Access 2000 (CDMA2000), CDMA2000 IX (lxRTT), Wideband Code Division Multiple Access (WCDMA), Time Division-Synchronous Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), Evolved Universal Terrestrial Radio Access Network (E- UTRAN), Evolution-Data Optimized (EVDO), High Speed Packet Access (HSPA), High- Speed Downlink Packet Access (HSDPA), IEEE 802.11 (Wi-Fi), 802.16 (WiMAX), ultra wideband (UWB), infrared (IR) protocols, BluetoothTM protocols, wireless universal serial bus (USB) protocols, and/or any other wireless protocol.
  • GPRS general packet radio service
  • UMTS Universal Mobile Telecommunications System
  • CDMA2000 Code Division Multiple Access 2000
  • CDMA2000 IX Lx
  • carrier system's 100 components may be located remotely from other carrier system 100 components. Furthermore, one or more of the components may be combined and additional components performing functions described herein may be included in the carrier system 100.
  • Fig. 3 provides an illustrative schematic representative of a mobile station 105 that can be used in conjunction with the embodiments of the present invention.
  • Mobile stations 105 can be operated by various parties, including carrier personnel (e.g., delivery drivers, sorters, and/or the like).
  • the mobile station 105 can include an antenna 312, a transmitter 304 (e.g., radio), a receiver 306 (e.g., radio), and a processing device 308 (e.g., a processor, controller, and/or the like) that provides signals to and receives signals from the transmitter 304 and receiver 306, respectively.
  • the signals provided to and received from the transmitter 304 and the receiver 306, respectively may include signaling information in accordance with an air interface standard of applicable wireless systems.
  • the mobile station 105 may be capable of operating with one or more air interface standards, communication protocols, modulation types, and access types. More particularly, the mobile station 105 may operate in accordance with any of a number of wireless communication standards and protocols, such as those described above with regard to the carrier system 100. In a particular embodiment, the mobile station 105 may operate in accordance with multiple wireless communication standards and protocols (e.g., using a Gobi radio), such as GSM, UMTS, lxRTT, and EVDO, and use multiple wireless carriers. To do so, the mobile station 105 may include integrated mobile reception diversity and integrated power management. Such a configuration can provide for global connectivity to the user.
  • Gobi radio such as GSM, UMTS, lxRTT, and EVDO
  • the mobile station 105 can communicate with various other entities using concepts such as Unstructured Supplementary Service Data (USSD), Short Message Service (SMS), Multimedia Messaging Service (MMS), Dual-Tone Multi-Frequency Signaling (DTMF), and/or Subscriber Identity Module Dialer (SIM dialer).
  • USSD Unstructured Supplementary Service Data
  • SMS Short Message Service
  • MMS Multimedia Messaging Service
  • DTMF Dual-Tone Multi-Frequency Signaling
  • SIM dialer Subscriber Identity Module Dialer
  • the mobile station 105 can also download changes, add-ons, and updates, for instance, to its firmware, software (e.g., including executable instructions, applications, program modules), and operating system.
  • the mobile station 105 may include a location determining device and/or functionality.
  • the mobile station 105 may include a Global Positioning System (GPS) module adapted to acquire, for example, latitude, longitude, altitude, geocode, course, and/or speed data.
  • GPS Global Positioning System
  • the GPS module acquires data, sometimes known as ephemeris data, by identifying the number of satellites in view and the relative positions of those satellites.
  • the mobile station 105 may also comprise a user interface (that can include a display 316 coupled to a processing device 308) and/or a user input interface (coupled to the processing device 308).
  • the user input interface can comprise any of a number of devices allowing the mobile station 105 to receive data, such as a keypad 318, a touch display, voice or motion interfaces, or other input device.
  • the keypad 318 can include the conventional numeric (0-9) and related keys (#, *), and other keys used for operating the mobile station 105 and may include a full set of alphabetic keys or set of keys that may be activated to provide a full set of alphanumeric keys.
  • the user input interface can be used, for example, to activate or deactivate certain functions, such as screen savers and/or sleep modes.
  • the mobile station 105 can also include volatile memory 322 and/or non-volatile memory 324, which can be embedded and/or may be removable.
  • the non- volatile memory may be embedded or removable MMCs, secure digital SD memory cards, Memory Sticks, EEPROM, flash memory, hard disk, or the like.
  • the memory can store any of a number of pieces or amount of information and data used by the mobile station 105 to implement the functions of the mobile station 105.
  • the memory can also store content, such as computer program code for an application and/or other computer programs.
  • the customer computing devices 110 may each include one or more components that are functionally similar to those of the carrier system 100.
  • each of the customer computing devices may include: (1) a processor that communicates with other elements via a system interface or bus; (2) a display device/input device; (3) transitory and non-transitory memory; and (4) a communications interface.
  • computing device is used generically to refer to any computer, computing device, desktop, notebook or laptop, distributed system, carrier system, gateway, switch, or other processing device adapted to perform the functions described herein.
  • FIG. 4 is a flowchart illustrating operations and processes that may be performed for customer controlled management of shipments.
  • Figs. 5-14, 15A, 15B, 16- 18, 19 A, 19B, 20-25, 26 A, and 26B show exemplary input and output for customer controlled management of shipments. 1. Registration
  • the process may begin with the enrollment/registration of one or more customers for a customer delivery program.
  • a customer may be an individual, a family, a company, an organization, an entity, a department within an organization, a representative of an organization and/or person, and/or the like.
  • a customer e.g., a customer or customer representative operating a customer computing device 110
  • UPS United Parcel Service of America, Inc.
  • the carrier system 100 may transmit a webpage that provides the customer with an option of logging into a customer account or enrolling/registering for a customer delivery program.
  • the customer may be requested to provide biographic and/or geographic information by the carrier system 100 (e.g., via the registration module 270).
  • the customer may provide the customer's name, such as a first name, a last name, a company name, an entity name, and/or an organization name.
  • the customer may also provide any aliases associated with the customer. For instance, if the customer were an individual named Joseph Brown, the customer may provide Joe Brown or Joey Brown as aliases.
  • the customer may also provide one or more addresses associated with the customer (e.g., street address, city, state, postal code, and/or country).
  • Joseph Brown's address may be 105 Main Street, Atlanta, Georgia 30309, USA.
  • the customer may have multiple addresses associated with the account.
  • Joseph Brown may have a home address and a business address associated with his account.
  • an organization may have multiple locations (e.g., addresses) associated with its account.
  • addresses e.g., addresses
  • the customer may indicate which address should be used as the primary address.
  • the customer may provide other biographic and/or geographic information to adapt to various needs and circumstances.
  • the carrier system 100 may perform one or more validation operations. For example, the carrier system 100 may determine whether the primary address (and/or other addresses) in the specified country or postal code is eligible for a customer delivery program. The carrier system 100 may also determine whether the primary address (and/or other addresses) is valid, e.g., by passing the primary address through one or more address cleansing or standardization systems. The carrier system 100 may perform a variety of fraud prevention measures as well, such as determining whether the customer or one of the customer's addresses has been "blacklisted" from customer delivery programs. As will be recognized, a variety of other approaches and techniques can be used to adapt to various needs and circumstances.
  • the carrier system 100 may create a customer profile for the customer via the enrollment/registration process. Accordingly, the carrier system 100 may create and store various customer profiles (e.g., via database 240). In addition to at least the information described above, a customer profile may include one or more corresponding usernames and passwords. Additionally, the carrier system 100 may also create and store a customer identifier in association with the customer profile. In one embodiment, a customer identifier may be used to uniquely identify a customer profile. In another embodiment, a customer identifier may be used to uniquely identify a given address associated with a customer profile. In such an embodiment, if a customer profile is associated with four addresses, the carrier system 100 may create and store four customer identifiers in association with the customer profile. The customer identifier may also be stored in association with shipping data for an item to associate the item (and its shipping data) with the (a) correct customer (e.g., customer profile) and/or (b) correct address for a customer.
  • customer profile may include one or more corresponding usernames and password
  • a customer profile may correspond to one or more customer delivery programs.
  • a customer e.g., a customer or customer representative operating a customer computing device 110
  • Each customer delivery program may have different benefits, such as those shown in Fig. 7 and Table 1 below.
  • the free customer delivery program and the premium customer delivery program may have different benefits.
  • the free customer delivery program may allow customers to have access to certain features, e.g., delivery alerts, approximate delivery times, change delivery options, electronically authorize the release of an item, and/or route items to will call.
  • the premium customer delivery program (e.g., requiring a fee) may allow customers to have access to certain features in addition to those provided via the free customer delivery program, e.g., route items to other retail locations, reschedule deliveries, request that items be delivered to another address, and/or provide instructions for delivery.
  • these features are provided for illustrative purposes and are not limiting to embodiments of the present invention.
  • a variety of other approaches and techniques can be used to adapt to various needs and circumstances.
  • the customer e.g., a customer or customer representative operating a customer computing device 110
  • the customer can provide various preferences associated with the customer delivery program to the carrier system 100 via a webpage (Block 405 of Fig. 4), for example.
  • the customer e.g., a customer or customer representative operating a customer computing device 110
  • an item may be a parcel or group of parcels, a package or group of packages, scrap metal banded together, a vehicle part, a box, a crate, a drum, a box strapped to a pallet, and/or the like.
  • each item may include an item/shipment identifier, such as a barcode, a MaxiCode, electronic representation, and/or text.
  • the item/shipment identifier may be used by the carrier to identify and track the item as it moves through the carrier's transportation network.
  • Such item/shipment identifiers can be affixed to items by, for example, using a sticker (e.g., label) with the item/shipment identifier printed thereon (in human and/or machine readable form) or an RFID tag with the item/shipment identifier stored therein.
  • the carrier system 100 may store an item/shipment identifier in association with shipping data for the item.
  • the shipping data may include information about the item, such as delivery service level.
  • the delivery service level may be Next Day Air, Next Day Air Early AM, Next Day Air Saver, 2nd Day Air, 2nd Day Air Early AM, 3 Day Select, Ground, and/or SurePost.
  • the shipping data may include information about the party shipping the item (e.g., consignor), such as the party's address, the party's phone number, the party's return address, the party's name, and/or the like.
  • the shipping data may also include information about the customer to whom the item is to be delivered (e.g., consignee), such as the customer's address (e.g., delivery location), the customer's phone number, the customer's name, and/or the like.
  • the shipping data may include information about the item itself and any tracking information.
  • the tracking information may reflect the item's movement in the carrier's transportation network, including expected delivery date and time.
  • an item/shipment identifier associated with the item may be scanned or otherwise electronically read at various points as the item is transported through the carrier's transportation network.
  • the item/shipment identifier may be automatically scanned by a barcode or MaxiCode device, an RFID interrogator, by a camera controller, or by a carrier employee using a handheld device (e.g., mobile station 105).
  • an appropriate device can transmit the item/shipment identifier and other appropriate information (e.g., location and time of the scan or reading) to the carrier system 100.
  • the carrier system 100 can then receive and use the information to track the item as it is transported though the carrier's transportation network and update the shipping data accordingly.
  • customer refers to consignees throughout, the term customer may refer to consignors as well.
  • the carrier system 100 can use the shipping data to identify one or more customer profiles corresponding to the item (e.g., via the identification module 245). As described, each customer profile may include one or more addresses associated with the customer. Thus, when the carrier system 100 receives shipping data (or a portion of shipping data) for an item (Block 410 of Fig. 4), the carrier system 100 can determine whether the item corresponds to any customers enrolled/registered for a customer delivery program. In particular, the carrier system 100 can use the delivery address of the intended recipient (e.g., consignee or customer) in the shipping data for an item to identify any customer profiles with a substantially similar delivery address (Block 415 of Fig. 4).
  • the intended recipient e.g., consignee or customer
  • the carrier system 100 may identify Joseph Brown's customer profile as corresponding to the item even though the address in Joseph Brown's profile is 105 Main Street, Atlanta, Georgia 30309, USA. In other words, in making such determinations, the carrier system 100 can accommodate variations for a given address. As will be recognized, the carrier system 100 may be configured to compensate for various discrepancies.
  • the carrier system 100 can use the delivery name of the intended recipient (e.g., consignee or customer) in the shipping data to confirm that the identified customer profile is correct. To do so, the carrier system 100 may compare the delivery name of the intended recipient in the shipping data to the primary name and/or any aliases in the identified customer profile. If the names are substantially similar, the carrier system 100 can confirm that the identified customer profile is correct. By way of example, if the shipping data indicates that the delivery name of the intended recipient is Joe Brown and Joseph Brown listed Joe as a first name alias, the carrier system 100 could confirm Joseph Brown's customer profile as corresponding to the item.
  • the intended recipient e.g., consignee or customer
  • the carrier system 100 can associate the shipping data with the customer profile (Block 420 of Fig. 4). This may include appending the shipping data with the appropriate customer identifier (or other identifier corresponding to the customer profile). For instance, the shipping data for all shipments corresponding to Joseph Brown's customer profile may be appended with the customer identifier (or other identifier) created for Joseph Brown. In various embodiments, using this approach allows items (and their shipping data) to be linked to appropriate customer profiles.
  • any actions selected by the customer for an item can be passed to the shipping data for the item.
  • the carrier system 100 can be used to identify (e.g., retrieve the shipping data with the appropriate customer identifier) all shipments associated with a customer (e.g., customer profile) using the customer identifier and provide them to the customer for viewing in a customer- friendly format, such as via a dashboard/webpage/application.
  • Fig. 10 shows a dashboard/webpage/application with a list of all inbound shipments to a customer.
  • FIG. 11 shows dashboard/webpage/application with a calendar (which may have a day view, a week view, a multiple week view, and/or a month view) having a list of all inbound shipments to a customer.
  • the calendar is sorted by delivery address, indicating that the customer has more than one delivery address associated with the customer profile.
  • Fig. 12 shows another dashboard/webpage/application with a list of all inbound shipments to a customer.
  • these concepts can provide customers with ongoing visibility of all inbound packages, as well as preferences. For instance, for each item, the dashboard/webpage/application can be used to show the item/shipment identifier, a delivery indicator, last activity scan date, a non-confirmed delivery window, a confirmed delivery window a commit time, whether an in-person signature is requested for delivery, a delivery service level, and/or various other information. As will be recognized, though, a variety of other approaches and techniques can be used to provide tracking information to a customer. 4. Messages
  • the dashboard/webpage/application (or other mechanism) in communication with the carrier system 100 can be used to customize and/or provide communication preferences regarding items to be delivered to customers (shown in Fig. 13).
  • the communication preferences may provide customers with the ability to request messages for items before the carrier attempts to deliver the items (e.g., prior to the first delivery attempt by the carrier) and/or after items have been delivered.
  • a customer e.g., a customer or customer representative operating a customer computing device 110
  • the communication formats may include text messages (e.g., Short Message Service (SMS) and/or Multimedia Messaging Service (MMS), email messages, voice messages, and/or a variety of other messages in various communication formats.
  • SMS Short Message Service
  • MMS Multimedia Messaging Service
  • the customer e.g., a customer or customer representative operating a customer computing device 110
  • email messages the customer may provide one or more email addresses.
  • voice messages the customer may provide one or more cellular or landline phone numbers.
  • validation operations can be performed with respect to each input destination address— to ensure their accuracy.
  • customers may indicate the type of messages they want to receive (e.g., the content). For example, a customer may indicate that he only wants to receive messages when the shipping data for an item indicates that an in-person signature from the customer is requested for delivery of the item, when the delivery options for the item can be changed, when instructions for delivery of the item can be provided, or when the delivery service level of the item can be changed. In another example, a customer may indicate that he wants to receive messages for all items to be delivered to the customer with expected delivery dates and delivery times. As will be recognized, customers may indicate that they want to receive messages regarding items in a variety of other circumstances.
  • customers may identify/define time periods in which the messages providing information regarding items to be delivered should be transmitted to the customer.
  • the time periods may include (a) after shipment and the day before an item is delivered and (b) after shipment and the morning of the day of delivery.
  • the messages can serve as a reminder to the customer that an item is being delivered.
  • the time periods may be after delivery for confirmation of delivery.
  • the carrier system 100 can store communication preferences for providing information in association with the customer profiles.
  • the communication preferences may apply to the customer profile globally, to selected customer addresses, to groups of items, and/or an item-by-item basis.
  • the carrier system 100 may impose time constraints for placing, generating, and/or transmitting messages within the time periods identified by the customers. For example, the carrier system 100 may only transmit text messages to customers between 6:00am- 11 :00pm (based on time zones). Similarly, the carrier system 100 may place calls and transmit automated voice messages between 8:00am-9:00pm (based on time zones). And for email messages, the carrier system 100 may generate and transmit them without time constraints.
  • the carrier system 100 can automatically generate (e.g., via the message module 260) one or more messages providing information regarding an item to be delivered to the customer (Block 425 of Fig. 4) in compliance with the customer's communication preferences and the carrier's time constraints.
  • the carrier system to 100 can automatically transmit the one or messages to the electronic destination addresses in compliance with the customer's communication preferences and the carrier's time constraints.
  • the carrier system 100 may generate (including select) and transmit an email message to Joseph Brown's email address and a text message to Joseph's cellular phone the day before an item is to be delivered to Joseph's home address.
  • the messages may indicate the expected delivery date and/or delivery time, such as shown in Figs. 15A and 15B, and a variety of other information.
  • a variety of other operations and processes may be used with embodiments of the present invention. These operations and processes can be customized to adapt to various needs and circumstances. 5. Delivery Times
  • the dashboard/webpage/application (or other mechanism) can be used to view expected delivery times (estimate delivery windows and/or confirmed delivery windows).
  • estimated time windows may indicate an estimated delivery time of an item based on historical delivery times to the area. Such information may be included in messages to customers prior to the first delivery attempt.
  • the dashboard/webpage/application may also be used by the customer (e.g., operating a customer computing device 110) to request that items be delivered within a delivery window. That is, the customer may want an item delivered within a specific time window.
  • the carrier may provide such services as part of a customer delivery program or on a fee basis, as shown in Figs. 16 and 17. Table 2 below provides illustrative estimated delivery windows and confirmed delivery windows from which the customer can select to have an item delivered.
  • consignors, consignees, and/or the carrier may request that a recipient's signature be obtained at the point of delivery for certain items.
  • In-person signature requests may be for high-value and/or high-risk items, such as cellular phones, computers, narcotic medications, and/or a variety of other items.
  • in-person signature requests may be designated by the carrier for items being delivered in non-driver release areas.
  • a non-driver release area may be an area in which items have been stolen after being left at the delivery location (e.g., not delivered to a person) and/or for various other reasons. The following describes two separate approaches for delivering such packages without in-person signatures.
  • items that are shipped with a request for an in-person signature at the point of delivery may have a non-driver release status.
  • the non-driver release status may be indicated in the shipping data.
  • the shipping data for an item may indicate that an in-person signature from a recipient (e.g., customer or representative of the customer) is requested for delivery of the item.
  • such information may be displayed via the dashboard/webpage/application (shown in Fig. 13).
  • the shipping data for the item represented in Fig. 13 indicates that an in- person signature is requested for delivery of the item.
  • payment of $25.00 is also needed for delivery.
  • the customer may electronically authorize delivery of the item without an in-person signature.
  • the customer e.g., a customer or customer representative operating a customer computing device 110
  • the customer e.g., a customer or customer representative operating a customer computing device 110
  • may select a hyperlink e.g., shown in Fig.
  • the carrier system 100 can provide the appropriate information via the dashboard/webpage/application for the customer. For instance, as shown in Fig. 18, the carrier system 100 may provide a dashboard/webpage/application (e.g., displayed via a customer computing device 110) that provides a disclaimer for delivering the item without an in-person signature (e.g., delivering the item by leaving it at a front door of a house). The dashboard/webpage/application may require the customer to check a box, type in his name, and/or perform other affirmative steps. The customer computing device 110 can then transmit the input authorization to the carrier system 100.
  • a dashboard/webpage/application e.g., displayed via a customer computing device 110
  • the dashboard/webpage/application may require the customer to check a box, type in his name, and/or perform other affirmative steps.
  • the customer computing device 110 can then transmit the input authorization to the carrier system 100.
  • the carrier system 100 can then receive the input authorization to deliver the item without an in-person signature (Block 430 of Fig. 4). After (e.g., in response to) receiving the authorization, the carrier system 100 can update the shipping data to reflect that the item can now be delivered without an in-person signature at the point of delivery.
  • an electronic authorization may have the same effect as an in-person signature at the point of the delivery.
  • Such electronic signatures may apply to the customer profile globally (e.g., allowing all items for a particular address to be delivered without in-person signatures), to selected customer addresses, to groups of items, and/or an item-by-item basis.
  • Such authorizations may be provided prior to the first delivery attempt by the carrier, further streamlining carrier operations and increasing customer satisfaction.
  • the carrier system 100 can provide for payment of items so that cash-on-delivery items do not require an in-person transaction for delivery.
  • the carrier system 100 can provide for payment of items so that cash-on-delivery items do not require an in-person transaction for delivery.
  • a variety of other operations and processes may be used with embodiments of the present invention. These operations and processes can be customized to adapt to various needs and circumstances.
  • a dashboard/webpage/application in communication with the carrier system 100 can be used to automatically authorize delivery of items without in-person signatures even when the corresponding shipping data indicates that in-person signatures are requested for delivery.
  • the customer e.g., a customer or customer representative operating a customer computing device 110
  • the customer e.g., a customer or customer representative operating a customer computing device 110
  • may select a hyperlink e.g., shown in Fig.
  • the carrier system 100 can provide the appropriate information via the dashboard/webpage/application for the customer.
  • the carrier system 100 may provide a dashboard/webpage/application (e.g., displayed via a customer computing device 110) that provides a disclaimer for delivering the items without in-person signatures (e.g., delivering the item by leaving it at a front door of a house).
  • the dashboard/webpage/application may require the customer to check a box, type in his name, and/or perform other affirmative steps to properly acknowledge consent.
  • the customer computing device 110 can then transmit the input authorization to the carrier system 100.
  • the carrier system 100 can then receive the input authorization to deliver the items without in-person signatures (Block 430 of Fig. 4).
  • the carrier system 100 can update the customer profile to reflect that the items with corresponding shipping data indicating that in-person signatures are requested for delivery can be delivered without in-person signatures.
  • This feature can be configured for items that have yet to be purchased, shipped, or delivered (e.g., for future transactions).
  • the carrier system 100 can automatically change the corresponding shipping data to reflect that the item can be delivered without an in-person signature (e.g., based on the customer profile). In certain embodiments, this may require applying a new item/shipment identifier and/or label. For example, the carrier system 100 can transmit to the appropriate mobile stations 105 (and/or other computing entities) updated shipping data indicating that the item can be delivered without an in-person signature. In one embodiment, the appropriate mobile stations 105 (and/or other computing entities) can receive the updated shipping data.
  • the mobile station 105 can provide the carrier personnel with an indication that the item can be delivered without an in-person signature. This may include indicating that a new label (and/or item/shipment identifier) needs to be affixed to the item. The item can then be transported and delivered with the new label by the carrier and delivered without requiring an in-person signature.
  • this feature may also require that items satisfy certain criteria in order to automatically allow an item to be delivered without an in-person signature.
  • the customer may indicate that only items originating from identified consignors (e.g., Amazon, Lands' End, William Robinson, etc.) can be delivered without in-person signatures.
  • identified consignors e.g., Amazon, Lands' End, William Robinson, etc.
  • customer Joseph Brown can update his customer profile such that all items to be delivered to him that originate from Lands' End are to be delivered without in-person signatures.
  • all items to be delivered to Joseph Brown originating from Lands' End can be delivered without in-person signatures (if they were originally requested).
  • a variety of other approaches and techniques can be used to adapt to various needs and circumstances.
  • the carrier may include such services as part of a customer delivery program and/or require a fee on a transaction basis.
  • a variety of other operations and processes may be used with embodiments of the present invention.
  • such features can be used in conjunction with customer and item matching features, item tracking features, messaging features, delivery time features, instructions for delivery features, delivery option features, and/or the like.
  • these operations and processes can be customized to adapt to various needs and circumstances.
  • delivery persons working for a carrier may carry and operate mobile stations 105 to assist in the delivery of items.
  • shipping data (or at least a portion of shipping data) corresponding to items to be delivered can be transmitted regularly, periodically, continuously, and/or on demand to the appropriate mobile stations 105.
  • carrier personnel can scan an item/shipment identifier on an item (e.g., using a mobile station 105) to view information about the delivery of the item.
  • the mobile station 105 may also be used to provide instructions for delivery to a delivery person.
  • the instructions may include information, such as where an item should be left at a delivery location and/or access codes needed to deliver an item.
  • a dashboard/webpage/application in communication with the carrier system 100 (e.g., via the delivery options module 250) can be used to provide instructions regarding items to be delivered to customers (e.g., prior to a delivery attempt by the carrier).
  • the customer e.g., a customer or customer representative operating a customer computing device 110
  • the dashboard/webpage/application may also provide the customer with the option of providing instructions for delivering one or more items.
  • the customer e.g., a customer or customer representative operating a customer computing device 110
  • may select a button e.g., shown in Fig. 13
  • the carrier system 100 can provide the appropriate dashboard/webpage/application and information to the customer. For instance, as shown in Figs.
  • the carrier system 100 may provide a dashboard/webpage/application to the customer (e.g., displayed via a customer computing device 110) that provides the ability to input (e.g., via an input form) one or more instructions for using a code to enter an area proximate the delivery address, such as building code(s), door code(s), and/or gate code(s).
  • the carrier system 100 may also provide a dashboard/webpage/application to the customer (e.g., displayed via a customer computing device 110) that provides the ability to input (e.g., via a drop-down menu) one or more instructions that identify a location at the delivery address at which the item should be left. Table 3 below provides illustrative instructions and corresponding codes.
  • the carrier system 100 can receive the one or more instructions for delivery (e.g., before a first delivery attempt). After (e.g., in response to) receiving the one or more instructions for delivery, the carrier system 100 can update the shipping data to reflect that the item should be delivered in accordance with the one or more instructions.
  • the updated shipping data (or at least a portion of updated shipping data) can be transmitted regularly, periodically, continuously, and/or on demand by the carrier system 100 to the appropriate mobile stations 105.
  • the appropriate mobile station 105 can receive the updated shipping data (or at least a portion of updated shipping data).
  • a delivery person can scan an item/shipment identifier on an item (e.g., using a mobile station 105) to view information about the delivery of the item, and the updated shipping data (or at least a portion of updated shipping data) can be displayed, including the one or more instructions for delivery.
  • the delivery person can then delivery the item in accordance with the one or more instructions for delivery. For instance, as shown in Fig. 21.
  • the instructions may be to leave an item at a rear door at a delivery location and further provide a gate code needed to access the rear door.
  • a variety of other instructions for delivery can be provided as well.
  • the one or more instructions for delivery may apply to the customer profile globally (e.g., providing that all items be delivered in accordance with the instructions), to selected customer addresses, to groups of items, and/or an item-by-item basis. As indicated, such instructions may be provided prior to the first delivery attempt by the carrier.
  • a variety of other operations and processes may be used with embodiments of the present invention. These operations and processes can be customized to adapt to various needs and circumstances.
  • the carrier may include such services as part of a customer delivery program and/or require a fee.
  • shipping data (or at least a portion of shipping data) corresponding to items to be delivered can be transmitted regularly, periodically, continuously, and/or on demand by the carrier system 100 to the appropriate mobile stations 105.
  • carrier personnel can scan an item/shipment identifier on an item (e.g., using a mobile station 105) to view, access, provide, and/or retrieve information about the item or delivery of the item.
  • shipping data can be updated to change delivery options, such as changing the delivery location, the delivery date, the delivery time, and/or the delivery service level.
  • a dashboard/webpage/application in communication with the carrier system 100 (e.g., via the delivery options module 250) can be used to change delivery options regarding items to be delivered to customers (e.g., prior to a delivery attempt by the carrier).
  • the customer e.g., a customer or customer representative operating a customer computing device 110
  • the dashboard/webpage/application may provide the customer with the option of changing delivery options for one or more items.
  • the customer may select a button (e.g., shown in Fig. 13) that reads "Change Delivery.”
  • the carrier system 100 can provide the appropriate dashboard/webpage/application and information to the customer. For instance, as shown in Fig. 22, the carrier system 100 may provide a dashboard/webpage/application to the customer (e.g., displayed via a customer computing device 110) that provides the ability to change delivery options.
  • the delivery options may allow the customer to request to have the item held at a carrier facility for pick up (e.g., will call or same day will call).
  • the delivery options may allow the customer to request to reschedule delivery of the item for another date and/or time (e.g., a future date and time).
  • the delivery options may allow the customer to change the delivery service level of the item (e.g., change the delivery service level from Ground to 2nd Day Air or Ground to SurePost) after the item has been shipped. In one embodiment, this may allow for the item to be delivered earlier than initially indicated (e.g., both date and time).
  • the delivery options may allow the customer request to change the delivery location to a carrier facility (or other location), such as a UPS Store. And the delivery options may allow the customer to request to return the item to the consignor.
  • a carrier facility or other location
  • UPS Store such as a UPS Store
  • embodiments of the present invention may also allow a customer to change a variety of other delivery options.
  • the carrier system 100 can receive the changed delivery options as input from the customer. After (e.g., in response to) the changed delivery options, the carrier system 100 can accept the requested changes (e.g. including validating the changes). The carrier system 100 can then update the shipping data to reflect that the item should be delivered in accordance with the changed delivery options. In one embodiment, the change in delivery options may require applying a new item/shipment identifier and/or label. For example, as described, the updated shipping data (or at least a portion of updated shipping data) corresponding to items to be delivered can be transmitted regularly, periodically, continuously, and/or on demand by the carrier system 100 to the appropriate mobile stations 105 (and/or other computing entities).
  • the appropriate mobile stations 105 can receive the updated shipping data (or at least a portion of updated shipping data) corresponding to items to be delivered.
  • carrier personnel sorting items or loading delivery vehicles can scan an item/shipment identifier (e.g., using a mobile station 105) on an item to view information about the delivery of the item, and the updated shipping data (or at least a portion of updated shipping data) can be displayed.
  • the updated shipping information may indicate that a new label (and/or item/shipment identifier) needs to be affixed to the item (e.g., the new label may indicate the new delivery address).
  • the item can then be delivered in accordance with the changed delivery options.
  • the carrier may include such services as part of a customer delivery program and/or require a fee.
  • the delivery options may be changed prior to the first delivery attempt by the carrier.
  • a variety of other operations and processes may be used with embodiments of the present invention. These operations and processes can be customized to adapt to various needs and circumstances.
  • a dashboard/webpage/application in communication with the carrier system 100 (e.g., via the delivery options module 250) can be used to change delivery options regarding items to be delivered to customers while the customers are on vacation (or otherwise away from the delivery location, such as being out of town on a business trip).
  • a customer e.g., a customer or customer representative operating a customer computing device 110
  • the customer e.g., a customer or customer representative operating a customer computing device 110
  • may select a button e.g., shown in Fig.
  • the carrier system 100 can provide the appropriate dashboard/webpage/application and information to the customer. For instance, as shown in Figs. 24, 25, 26A, and 26B, the carrier system 100 may provide a dashboard/webpage/application to the customer (e.g., displayed via a customer computing device 110) that provides the ability to input vacation dates and/or delivery options (e.g., the delivery location, the delivery date, and/or the delivery time).
  • the delivery options may allow the customer to request to have items held at a carrier facility for will call or to be rescheduled for delivery on another date.
  • the delivery options may allow the customer to request to have all items delivered to a carrier facility, such as a UPS Store.
  • the carrier system 100 can receive the input vacation dates and/or delivery options. After (e.g., in response to) receiving the input vacation dates and/or delivery options, the carrier system 100 can apply the vacation delivery options to all items to be delivered to the customer (and/or one of the customer's addresses in his customer profile) during the vacation time period. For instance, as shown in Fig. 26 A, all items to be delivered to a customer between 07/01/2011 and 07/11/2011 can be rescheduled for delivery on 07/12/2011. Similarly, as shown in Fig. 26B, all items to be delivered to a customer between 07/01/2011 and 07/11/2011 can be delivered to a carrier facility (such as a UPS Store) for later pickup by the customer.
  • vacation options may require applying a new label (and/or item/shipment identifier) to items to be delivered during the vacation time period.
  • a dashboard/webpage/application in communication with the carrier system 100 can be used to change delivery service levels for items to be delivered to customers prior to respective delivery attempts by the carrier.
  • the customer e.g., a customer or customer representative operating a customer computing device 110
  • the dashboard/webpage/application may provide the customer with the option of changing the delivery service levels for one or more items (e.g., change the delivery service level from Ground to 2nd Day Air or from Ground to SurePost).
  • the customer e.g., a customer or customer representative operating a customer computing device 110
  • the carrier system 100 can provide the appropriate information via the dashboard/webpage/application to the customer.
  • the carrier system 100 may be in communication with a dashboard/webpage/application (e.g., displayed via a customer computing device 110) that provides the ability to change the delivery service level.
  • this may allow the customer to change the delivery service level from SurePost to Ground, from Ground to 2nd Day Air, from 2nd Day Air to Next Day Air, from 2nd Day Air to Ground, and/or the like.
  • the delivery service level can be changed from a first delivery service level with which it was originally shipped to a second delivery service level (after the item has been shipped but) prior to the first delivery attempt of the item.
  • this may allow for the item to be delivered earlier or later than initially indicated (e.g., both date and time).
  • the carrier system 100 can receive the request to change the delivery service level as input from the customer. After (e.g., in response to) receiving such a request, the carrier system 100 can accept the requested changes (e.g. including validating the changes). The carrier system 100 can then update the shipping data to reflect that the item should be delivered in accordance with the second (e.g., changed) delivery service level, which may automatically change the delivery date and/or cost associated with delivering the item. In one embodiment, the change in the delivery service level may require applying a new item/shipment identifier and/or label. For example, as described, the updated shipping data (or at least a portion of updated shipping data) corresponding to items to be delivered can be transmitted regularly, periodically, continuously, and/or on demand by the carrier system 100 to the appropriate mobile stations 105 (and/or other computing entities).
  • the appropriate mobile stations 105 can receive the updated shipping data (or at least a portion of updated shipping data) corresponding to items to be delivered.
  • carrier personnel sorting items or loading delivery vehicles can scan an item/shipment identifier (e.g., using a mobile station 105) on an item to view information about the delivery of the item, and the updated shipping data (or at least a portion of updated shipping data) can be displayed.
  • the updated shipping information may indicate that a new label (and/or item/shipment identifier) needs to be affixed to the item (e.g., the new label may indicate the new delivery service level).
  • the item can then be transported and delivered with the new label by the carrier in accordance with the second (e.g., changed) delivery service level.
  • the carrier may include such services as part of a customer delivery program and/or require a fee on a transaction basis.
  • the delivery options may be changed prior to the first delivery attempt by the carrier.
  • changing the delivery service level feature can be used in conjunction with other features described herein, such as customer and item matching features, item tracking features, messaging features, delivery time features, electronic authorization for item release features, instructions for delivery features, and/or delivery option features.
  • these operations and processes can be customized to adapt to various needs and circumstances.
  • a dashboard/webpage/application in communication with the carrier system 100 can be used to automatically change delivery service levels for items to be delivered to customers prior to respective delivery attempts by the carrier.
  • the customer e.g., a customer or customer representative operating a customer computing device 110
  • the dashboard/webpage/application may provide the customer with the option of automatically changing the delivery service level for all (or select) items to be delivered via a specific delivery service level (e.g., Next Day Air, Next Day Air Early AM, Next Day Air Saver, 2nd Day Air, 2nd Day Air Early AM, 3 Day Select, Ground, and/or SurePost).
  • a specific delivery service level e.g., Next Day Air, Next Day Air Early AM, Next Day Air Saver, 2nd Day Air, 2nd Day Air Early AM, 3 Day Select, Ground, and/or SurePost.
  • the customer e.g., a customer or customer representative operating a customer computing device 110
  • the carrier system 100 can provide the appropriate information via the dashboard/webpage/application to the customer.
  • the carrier system 100 may be in communication with a dashboard/webpage/application (e.g., displayed via a customer computing device 110) that provides the ability to set automatic delivery service level changes for all (or select) items to be delivered via the specific delivery service level.
  • the customer can input that all (or select) items to be delivered via a first delivery service level (e.g., SurePost) should automatically be changed to a second delivery service level (e.g., Ground).
  • a first delivery service level e.g., SurePost
  • a second delivery service level e.g., Ground
  • delivery service levels can be automatically changed from a first delivery service level (used when originally shipped) to a second delivery service level, which may automatically change the delivery dates and/or costs associated with delivering the item. As indicated, this may even occur after the items have been shipped but prior to the first delivery attempt of the items.
  • the carrier system 100 can receive the request to automatically change the delivery service level as input from the customer. After (e.g., in response to) receiving such a request, the carrier system 100 can accept the requested changes (e.g. including validating the changes). The carrier system 100 can then update the customer profile to reflect that items to be delivered in accordance with the first delivery service level (and/or from a specific consignor) should be automatically changed to a second delivery service level during transport by the carrier.
  • the carrier system 100 can automatically change the first delivery service level to the second delivery service level as reflected in the customer profile. As described, this may require applying a new item/shipment identifier and/or label.
  • the carrier system 100 can transmit regularly, periodically, continuously, and/or on demand to the appropriate mobile stations 105 (and/or other computing entities) that the first delivery service level (e.g., SurePost) should be changed to a second delivery service level (e.g., Ground) for the item.
  • the appropriate mobile stations 105 (and/or other computing entities) can receive the indication.
  • the mobile station 105 can provide the carrier personnel with an indication that the first delivery service level should be changed to the second delivery service level. This may include indicating that a new label (and/or item/shipment identifier) needs to be affixed to the item (e.g., the new label may indicate the new delivery service level).
  • the item can then be transported and delivered with the new label by the carrier in accordance with the second (e.g., changed) delivery service level.
  • this feature may also require that items satisfy other criteria in order to automatically change the delivery service level.
  • the customer may indicate that only items originating from identified consignors (e.g., Amazon, Lands' End, William Robinson, etc.) have their delivery service levels changed automatically.
  • identified consignors e.g., Amazon, Lands' End, William Robinson, etc.
  • customer Joseph Brown can update his customer profile such that all items to be delivered to him that originate from Lands' End are to be automatically changed to the Second Day Air delivery service level (if not already Second Day Air).
  • customer Joseph Brown can update his profile such that all items originating from identified consignors (e.g., Amazon, Lands' End, William Robinson, etc.) and to be delivered via a first delivery service level (e.g., SurePost) have their delivery service level automatically changed to a second delivery service level (e.g., Ground).
  • a first delivery service level e.g., SurePost
  • a second delivery service level e.g., Ground
  • all items to be delivered to Joseph Brown via SurePost and originating from Lands' End can be automatically changed from the SurePost delivery service level to the Ground delivery service level.
  • a variety of other approaches and techniques can be used to adapt to various needs and circumstances.
  • the carrier may include such services as part of a customer delivery program and/or require a fee on a transaction basis.
  • the delivery options may be changed prior to the first delivery attempt by the carrier.
  • changing the delivery service level feature can be used in conjunction with other features, such as customer and item matching features, item tracking features, messaging features, delivery time features, electronic authorization for item release features, instructions for delivery features, delivery option features, and/or the like.
  • these operations and processes can be customized to adapt to various needs and circumstances.
  • a dashboard/webpage/application in communication with the carrier system 100 can be used to block features from being used with a customer profile.
  • the features that may be blocked include customer and item matching features, item tracking features, messaging features, delivery time features, electronic authorization for item release features, instructions for delivery features, delivery option features, and/or the like.
  • the customer e.g., a customer or customer representative operating a customer computing device 110

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Economics (AREA)
  • Quality & Reliability (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Human Resources & Organizations (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Development Economics (AREA)
  • Strategic Management (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

L'invention concerne des systèmes, des procédés, un appareil et des produits programme d'ordinateur pour une gestion commandée par le client d'expéditions. Par exemple, dans différents modes de réalisation, un client peut fournir des informations avant une première tentative de livraison d'un article par un transporteur pour recevoir des messages concernant l'expédition de l'article et avoir l'article livré conformément aux informations fournies.
EP13796181.9A 2013-01-22 2013-11-04 Gestion commandée par le client d'expéditions Ceased EP2948911A4 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US13/746,862 US20130138573A1 (en) 2011-05-25 2013-01-22 Customer controlled management of shipments
US13/746,854 US20130212036A1 (en) 2011-05-25 2013-01-22 Customer controlled management of shipments
PCT/US2013/068210 WO2014116320A1 (fr) 2013-01-22 2013-11-04 Gestion commandée par le client d'expéditions

Publications (2)

Publication Number Publication Date
EP2948911A1 true EP2948911A1 (fr) 2015-12-02
EP2948911A4 EP2948911A4 (fr) 2016-06-08

Family

ID=49674370

Family Applications (1)

Application Number Title Priority Date Filing Date
EP13796181.9A Ceased EP2948911A4 (fr) 2013-01-22 2013-11-04 Gestion commandée par le client d'expéditions

Country Status (4)

Country Link
EP (1) EP2948911A4 (fr)
CN (1) CN104919479A (fr)
CA (1) CA2884747C (fr)
WO (1) WO2014116320A1 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102015119004A1 (de) * 2015-11-05 2017-05-11 Deutsche Post Ag Vereinfachte Zustellung von Sendungen mit noch unbezahlten Waren
US20180253691A1 (en) * 2017-03-06 2018-09-06 Walmart Apollo, Llc Systems and Methods for Delivering Products to a Customer
KR20230085695A (ko) * 2021-12-07 2023-06-14 현대자동차주식회사 차량 및 이를 이용한 배송품 수령 방법

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020103724A1 (en) * 2000-12-01 2002-08-01 Stephen Huxter Courier independent system and method for the delivery of goods ordered by the internet
US20020178074A1 (en) * 2001-05-24 2002-11-28 Gregg Bloom Method and apparatus for efficient package delivery and storage
CN1643534A (zh) * 2002-03-28 2005-07-20 佐川急便株式会社 配送管理服务器、配送管理方法及客户管理程序
US7765131B2 (en) * 2006-06-20 2010-07-27 United Parcel Service Of America, Inc. Systems and methods for providing personalized delivery services
CN101203873A (zh) * 2005-06-21 2008-06-18 美国联合包装服务有限公司 用于提供个性化递送服务的系统和方法
US20070156415A1 (en) * 2005-12-29 2007-07-05 Pitney Bowes Incorporated Changing delivery parameters in processing physical mail based on recipient's response to electronic notification
WO2009140669A2 (fr) * 2008-05-16 2009-11-19 Terahop Networks, Inc. Fixation, surveillance et suivi de conteneur d'expédition
US8708267B2 (en) * 2010-07-01 2014-04-29 Wayne S. Morgan Device and method for a rolling a sheet of material for packaging, storage, shipment, and dispensing
US20120303542A1 (en) * 2011-05-25 2012-11-29 United Parcel Service Of America, Inc. Customer controlled management of shipments
US20120303539A1 (en) * 2011-05-25 2012-11-29 United Parcel Service Of America, Inc. Customer controlled management of shipments
US20120303538A1 (en) * 2011-05-25 2012-11-29 United Parcel Service Of America, Inc. Customer controlled management of shipments
US20120303540A1 (en) * 2011-05-25 2012-11-29 United Parcel Service Of America, Inc. Customer controlled management of shipments

Also Published As

Publication number Publication date
CA2884747A1 (fr) 2014-07-31
CN104919479A (zh) 2015-09-16
EP2948911A4 (fr) 2016-06-08
WO2014116320A1 (fr) 2014-07-31
CA2884747C (fr) 2020-03-10

Similar Documents

Publication Publication Date Title
US20120303542A1 (en) Customer controlled management of shipments
US11769108B2 (en) Determining alternative delivery destinations
US20120303539A1 (en) Customer controlled management of shipments
US20120303541A1 (en) Customer controlled management of shipments
US11748694B2 (en) Systems and methods for delivery of an item
US11907896B2 (en) Methods, apparatuses and computer program products for facilitating label less returns
US20120303540A1 (en) Customer controlled management of shipments
US20120303538A1 (en) Customer controlled management of shipments
US10664787B2 (en) Customer controlled management of shipments
US20150081587A1 (en) Customer controlled management of shipments
US20150294262A1 (en) Determining delivery windows for item delivery based on customer and/or item location
US9916557B1 (en) Systems and methods for item delivery and pick-up using social networks
US11605049B2 (en) Systems and methods for customized shipment notifications
US11144872B2 (en) Delivery to an unattended location
US20130212036A1 (en) Customer controlled management of shipments
US20150371183A1 (en) Systems and methods for confidential shipping
US20130138573A1 (en) Customer controlled management of shipments
CA2884747C (fr) Gestion commandee par le client d'expeditions
US20130198100A1 (en) Customer controlled management of shipments
CA2881201C (fr) Gestion d'envois controlee par le client

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20150211

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAX Request for extension of the european patent (deleted)
A4 Supplementary search report drawn up and despatched

Effective date: 20160506

RIC1 Information provided on ipc code assigned before grant

Ipc: G06Q 30/00 20120101AFI20160429BHEP

Ipc: G06Q 10/08 20120101ALI20160429BHEP

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20170210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED

REG Reference to a national code

Ref country code: DE

Ref legal event code: R003

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED

18R Application refused

Effective date: 20180524