• Client to submit the package details as an Advanced Shipping Notice to ParcelPrep via an API request
  • API requests submitted for each individual package
  • API request details to include:
    • Recipient name and address
    • Shipper name and address
    • Package dimensions
    • Package weight
    • Requested service level (Initially all packages to go Parcel Select)
  • The recipient details contained in the request will be logged in the ParcelPrep database
  • A unique package serial number will be assigned to the package and meet the uniqueness requirements established by the USPS
• Client can submit packages and leverage client-based business rules in ParcelPrep to determine if packages are to be shipped via USPS, FedEx, or UPS.

• In response of the ASN package API request
  • ParcelPrep will return a Base64 formatted 4×6 package label
  • The USPS label will contain at minimum:
    • Shipper address block
    • Recipient address block
    • USPS Postal Indicia
    • USPS eVS shipping barcode
    • Destination entry code to drive downstream consolidation and sortation
  • A unique package serial number
  • UPS and FedEx labels can be generated to meet similar carrier requirements

• Client to submit the package details as an Advanced Shipping Notice to ParcelPrep via a file (SFTP)
  • Each record in the ASN file includes detail for a given package
  • API request details to include:
    • Recipient name and address
    • Shipper name and address
    • Package dimensions
    • Package weight
    • Requested service level (Initially all packages to go Parcel Select)
  • The recipient details contained in the request will be logged in the ParcelPrep database
  • A unique package serial number will be assigned to the package and meet the uniqueness requirements established by the USPS
• Client can submit packages and leverage client-based business rules in ParcelPrep to determine if packages are to be shipped via USPS, FedEx, or UPS.

• In response to the ASN file
  • Acknowledgement files or communications can take place to identify the receipt of data
  • ASN data can be matched to incoming packages and additional shipping labels can be applied at the consolidation facility
  • Many different custom options can be created to facilitate custom warehouse and consolidation environments

• The options are endless…
• A Consolidator may take packages from many end clients and prepare
• them into USPS destination entry containers
• A Consolidator may perform some pick and pack to make up the final packages
• Business rules can be applied in ParcelPrep to determine the final carrier for the package
• Sortation and Consolidation can be controlled and managed by user defined tables
• ParcelPrep has the capability to have associate packages prelabeled with only a barcode and\or the name and address to generate the final shipping label during consolidation as a “label over” or “ride along” label

• Generate and close containers via ParcelPrep with Nesting
  • ParcelPrep to create USPS Destination Entry Containers
    • Generate container label
    • Uniquely serialize containers per USPS requirements
  • Receipt of packages
  • Associate packages to Destination Entry Containers (SCF or DDU)
  • Close containers
    • Update weight of container
    • Register closed container in ParcelPrep
    • Triggers the manifesting of packages contained in each container
  • Meets the USPS “nesting” requirements
  • Provides the greatest level of tracking capabilities by tracking the container as well as the actual packages

• Generate and close containers via ParcelPrep
  • ParcelPrep to create USPS Destination Entry Containers
    • Generate container label
    • Uniquely serialize containers per USPS requirements
  • Receive which packages are going to USPS from client or DSP
  • Manifest the recorded packages in USPS eVS Manifest

*This process is a simplified version of the container and package manifesting. If there is any need for tracking of containers prior to the actual package tracking, the E1 option would be required.

• Transportation providers can be designated in user controlled and managed files within ParcelPrep
• ParcelPrep is capable of providing carrier specific transportation labels for drop shipping USPS containers. (Priority Mail Open and Distribute, FedEx, UPS, and a number of Third Party Regional Carriers)
• Transportation to either USPS delivery points or Third Party Delivery Service Provider is the responsibility of the client
• FedEx and UPS package shipments will likely be tendered to carrier directly

• At a designated time each day an automated process will generate a manifest of packages submitted to the USPS and transmit to the USPS eVS system.
• It would be recommended that a separate transmission for each consolidation facility be submitted to include the packages being physically presented by the facility.
• The transmission of the eVS manifest should take place prior to the physical presentment of the packages.
• ParcelPrep utilizes the Shipping Services File 2.0
• An email communicating the quantity, and weight by carrier and service
  level will be transmitted reflecting the data for that day.

• Throughout the life cycle of the package within the USPS, scan data will be sent to the ParcelPrep servers.
• ParcelPrep matches these transactional scans with package records and associates the USPS event data

• ParcelPrep is intended to be a self managed system
• Three layers of users to support a variety of use cases including
  administrative web access and Consolidator/DSP “operator” usage
• Self Managed Tables:
  • Destination Entry Locations “Bins” – Specify a SCF or a DDU of the USPS and can be defined by an internal code and placed on the package label
  • Zipcode to Bin mappings – a series of five digit and three digit tables that associate zipcodes to specific bins
  • Business Rules – ParcelPrep has an enormous capability to drive decision making and apply business rules to support varying operational and customer requirements
• Centralized Reporting