Delivery to the Consolidation Center

Overview

All parcels shipping with the PB Cross-Border Delivery Service (CBDS) are first brought to CBDS Consolidation Centers for customs processing and labeling before being sent to their international destinations. Each merchant who ships with CBDS through the Shipping APIs uses one of the following solutions for delivering parcels to the Consolidation Center. The solutions available to a merchant depend on the outbound country:

Within each solution, the merchant chooses a First-Mile Option, as described in the tables below. Merchants can test the options in Sandbox using the Sandbox Client IDs listed in the tables.

PB End-to-End Solution

The PB End-to-End Solution is available for U.S. Outbound only. In this solution, Pitney Bowes is responsible for the end-to-end journey of the parcel. Depending on the size of merchant, Pitney Bowes offers either Bulk Pickup or Piece-Level Shipment as the option for first-mile delivery from the client facility to the CBDS Consolidation Center. In both cases, the Create Shipment API prints the first-mile label.

PB End-to-End Solution for U.S. Outbound

First-Mile
Option


Description


  API Behavior


Sandbox
Client ID


Bulk Pickup

Pitney Bowes picks up the parcel. This solution is available for merchants who ship more than 200 parcels a day.

  • API Request: The merchant provides parcel details.
     

  • API Response: The API returns a PB Standard pickup label and an end-to-end tracking number.

NGST

Piece-Level Shipment

The merchant either drops off the parcel to a USPS facility or has USPS pick up the parcel.

  • API Request: The merchant provides parcel details.
     

  • API Response: The API returns a USPS label and an end-to-end tracking number.

USPSFM_1

Client Drop-Off Solution

In this solution, the merchant is responsible to deliver the parcel to a Pitney Bowes facility. The Client Drop-Off Solution is available for both U.S. Outbound and UK Outbound:

Client Drop-Off Solution for U.S. Outbound

The merchant is responsible to deliver the parcel to a Pitney Bowes facility—either to a PB Standard Facility or to the CBDS Consolidation Center.

First-Mile
Option


Description


API Behavior


Sandbox
Client ID


Drop-Off to PB Standard

The merchant delivers the parcel to a PB Standard Facility. The label for delivery to the facility should include the following on Address Line 1:

“Attn: PB Cross-Border”

The Create Shipment API prints a label for delivery from the PB Standard Facility to the CBDS Consolidation Center.

  • API Request: The merchant provides parcel details.
     

  • API Response: The API returns the label for delivery from the PB Standard Facility to the CBDS Consolidation Center. The API returns the end-to-end tracking number for the entire journey, including the drop-off to PB Standard.

NGST

Drop-Off to CBDS

The merchant delivers the parcel to a CBDS Consolidation Center. The Create Shipment API does not print a label. Instead, the merchant prints the first-mile label prior to invoking the API. The merchant enters the label’s tracking number when calling the API.

Important

If the merchant fails to enter a tracking number when invoking the Create Shipment API, the parcel will not be recognizable at the CBDS Consolidation Center.

  • API Request: The merchant provides parcel details, the tracking number for the first-mile label, and the name of the first-mile carrier.
     

  • API Response: The API returns an end-to-end tracking number.

COFM_1

Merchants can optionally use SFTP instead of the Shipping APIs to provide parcel data to Pitney Bowes. For more information, contact your Pitney Bowes representative.

Client Drop-Off Solution for UK Outbound

The merchant is responsible to deliver the parcel to the UK Consolidation Center (UK Hub).

First-Mile
Option


Description


API Behavior


Sandbox
Client ID


Drop-Off to UK Hub

The merchant delivers the parcel to the UK Hub. The Create Shipment API does not print a label. Instead, the merchant prints the first-mile label prior to invoking the API. The merchant enters the label’s tracking number when calling the API.

Important

If the merchant fails to enter a tracking number when invoking the Create Shipment API, the parcel will not be recognizable at the UK Hub.

  • Request: The merchant provides:

    • Parcel details

    • The tracking number for the first-mile label

    • The name of the first-mile carrier

  • Response: The API returns an end-to-end tracking number.

COFM_1

Merchants can optionally use SFTP instead of the Shipping APIs to provide parcel data to Pitney Bowes. For more information, contact your Pitney Bowes representative.