Deliveo knowledge base

The integration can be enabled on a customer-by-customer basis; therefore, only shipmentSend to An identifier that groups together packages sent from a Sender to a Recipient by a Customer at the same time. In practice, this is understood to mean the entire shipment, even if it consists of several Packing Units. data relating to designated Deliveo customers is forwarded.

Prerequisites

a subscribed Deliveo API connection;
a subscribed Deliveo webhook service;
an active Project44 account;
permission to install the add-on;
permission to configure and use the add-on.

Installation and access

The add-on can be installed on the DispatcherThe Dispatcher member of the Courier Service team. Manages customers and dispatches couriers. He/she uses the Deliveo dispatcherThe Dispatcher member of the Courier Service team. Manages customers and dispatches couriers. He/she uses the Deliveo dispatcher (admin) portal. (admin) portal. Portal under the Add-ons menu item.

Once installed, it can be accessed via the ‘Add-ons / Project44 Connect’ menu item. Only users with the appropriate authorisation may install and use the add-on.

The add-on’s own menu items:

Dashboard
ClientThe Customer (bill payer) pays the Courier Service for the delivery of parcels. You can also be the sender / recipient of the shipment. He/she uses the Deliveo customer interface.s
Settings

Linking your Project44 account

When you connect the add-on, the system creates a technical user in your Project44 account.

To complete the connection:

Open Project44 user management.
Find the user whose name appears on the Project44 Connect Settings page.
Open the user’s roles.
In the Roles section, click the Manage Roles button.
Add the ‘ShipmentSend to An identifier that groups together packages sent from a Sender to a Recipient by a Customer at the same time. In practice, this is understood to mean the entire shipmentSend to An identifier that groups together packages sent from a Sender to a Recipient by a Customer at the same time. In practice, this is understood to mean the entire shipment, even if it consists of several Packing Units., even if it consists of several Packing Units. management’ permission.
Save the changes.

A green status indicator on the Project44 Connect Settings page shows that the connection has been successfully established.

Configuring the forwarded shipmentSend to An identifier that groups together packages sent from a Sender to a Recipient by a Customer at the same time. In practice, this is understood to mean the entire shipment, even if it consists of several Packing Units. ID

On the Settings page, you can select which shipmentSend to An identifier that groups together packages sent from a Sender to a Recipient by a Customer at the same time. In practice, this is understood to mean the entire shipment, even if it consists of several Packing Units. ID Deliveo should forward to Project44. The available IDs are:

DeliveoIDUnique primary identifier for shipments in the Deliveo system.
Reference number
Tracking code

To save your selection, click the ‘Save ID setting’ button. This setting only changes the ID forwarded to Project44. Internal matching of events between Deliveo and Project44 will continue to be based on the DeliveoIDUnique primary identifier for shipments in the Deliveo system..

Configuring webhooks

Project44 Connect receives notifications about shipmentSend to An identifier that groups together packages sent from a Sender to a Recipient by a Customer at the same time. In practice, this is understood to mean the entire shipment, even if it consists of several Packing Units. events via Deliveo’s webhook feature. To configure this:

Open the Settings / Webhooks menu item in the DispatcherThe Dispatcher member of the Courier Service team. Manages customers and dispatches couriers. He/she uses the Deliveo dispatcherThe Dispatcher member of the Courier Service team. Manages customers and dispatches couriers. He/she uses the Deliveo dispatcher (admin) portal. (admin) portal. Portal.
Select the relevant event.
Open the event’s advanced settings.
Copy the webhook URL displayed for that event on the Project44 Connect Settings page.
Save the webhook settings.
Repeat this process for each required event.

There is a separate webhook URL for the following events:

Create shipmentSend to An identifier that groups together packages sent from a Sender to a Recipient by a Customer at the same time. In practice, this is understood to mean the entire shipment, even if it consists of several Packing Units.
ShipmentSend to An identifier that groups together packages sent from a Sender to a Recipient by a Customer at the same time. In practice, this is understood to mean the entire shipmentSend to An identifier that groups together packages sent from a Sender to a Recipient by a Customer at the same time. In practice, this is understood to mean the entire shipment, even if it consists of several Packing Units., even if it consists of several Packing Units. collection
Transfer
Successful delivery
Failed delivery

Webhook URLs are unique, so always use the addressesAddresses The geographical addresses where the Courier will pick up or deliver the parcel. An Address can be both a shipping address and a receiving address, the system does not distinguish between the two. shown on the Settings page of your Project44 Connect installation.

Selecting customers

On the Customers page, you can control which Deliveo customers’ data is forwarded to Project44.

To activate a customer:

Open the ClientThe Customer (bill payer) pays the Courier Service for the delivery of parcels. You can also be the sender / recipient of the shipment. He/she uses the Deliveo customer interface.s menu item.
Find the customer in the list.
Toggle the ‘Active’ switch in the customer’s row.

When this is switched on, shipmentSend to An identifier that groups together packages sent from a Sender to a Recipient by a Customer at the same time. In practice, this is understood to mean the entire shipment, even if it consists of several Packing Units. events relating to that customer will be forwarded. When this is switched off, the customer’s data will not be forwarded to Project44.

The clientThe Customer (bill payer) pays the Courier Service for the delivery of parcels. You can also be the sender / recipient of the shipment. He/she uses the Deliveo customer interface. list:

can be filtered by name;
the filter can be cleared;
can be paginated if there are multiple pages.

Before enabling the integration, please check that only those customers whose data you wish to forward are active.

Transferred events

Project44 Connect converts Deliveo events into Project44 events.

Examples of event mappings:

Create shipmentSend to An identifier that groups together packages sent from a Sender to a Recipient by a Customer at the same time. In practice, this is understood to mean the entire shipment, even if it consists of several Packing Units. → SHIPMENT_CREATED
Collection of shipmentSend to An identifier that groups together packages sent from a Sender to a Recipient by a Customer at the same time. In practice, this is understood to mean the entire shipment, even if it consists of several Packing Units. → PICKED_UP
ShipmentSend to An identifier that groups together packages sent from a Sender to a Recipient by a Customer at the same time. In practice, this is understood to mean the entire shipmentSend to An identifier that groups together packages sent from a Sender to a Recipient by a Customer at the same time. In practice, this is understood to mean the entire shipment, even if it consists of several Packing Units., even if it consists of several Packing Units. transfer → ARRIVED_AT_STOP
Successful delivery → DELIVERED
Failed delivery → for example DELIVERY_MISSED or RETURN_TO_SENDER

The Project44 event associated with a failed delivery may depend on the failed delivery event recorded in Deliveo.

Dashboard

The Dashboard displays webhook requests from the past 30 days.

The page summarises the following by event type:

parcel creations;
parcel collections;
parcel transfers;
successful deliveries;
delivery attempts;
unsuccessful deliveries.

The detailed list of events contains the following data:

Deliveo ID
Deliveo event
P44 event
Accepted
Date

The ‘Accepted’ column indicates whether Project44 has accepted the submitted event.

The list:

can be filtered by Deliveo ID;
can be paginated;
and can be used for chronological checks and troubleshooting.

Checking the data connection

Once set up, it is worth checking that everything is working by sending a test delivery.

Make sure that the customer associated with the shipmentSend to An identifier that groups together packages sent from a Sender to a Recipient by a Customer at the same time. In practice, this is understood to mean the entire shipment, even if it consists of several Packing Units. is active on the Customers page.
Create or edit a shipmentSend to An identifier that groups together packages sent from a Sender to a Recipient by a Customer at the same time. In practice, this is understood to mean the entire shipment, even if it consists of several Packing Units. so that one of the configured webhook events is triggered.
Open the Project44 Connect Dashboard.
Search for the shipmentSend to An identifier that groups together packages sent from a Sender to a Recipient by a Customer at the same time. In practice, this is understood to mean the entire shipment, even if it consists of several Packing Units. using the Deliveo ID.
Check the Deliveo event and the corresponding P44 event.
Check that the ‘Accepted’ column indicates successful acceptance.

Disconnecting the integration

An active Project44 connection can be terminated using the ‘Delete Connection’ button on the Settings page.

Before deleting the connection, check that event forwarding to Project44 is no longer required.

After terminating the connection, it is advisable to check the webhook settings for Project44 Connect in the Deliveo Settings → Webhooks menu and remove them if necessary.

Common issues

Events are not appearing on the dashboard

Check:

that the connection is active;
that the relevant clientThe Customer (bill payer) pays the Courier Service for the delivery of parcels. You can also be the sender / recipient of the shipment. He/she uses the Deliveo customer interface. is active on the ClientThe Customer (bill payer) pays the Courier Service for the delivery of parcels. You can also be the sender / recipient of the shipment. He/she uses the Deliveo customer interface.s page;
that the required webhooks have been set up;
that the correct webhook URL has been assigned to the relevant event;
that the event occurred within the last 30 days.

Project44 will not accept the event

Please check:

that the Project44 technical user has ShipmentSend to An identifier that groups together packages sent from a Sender to a Recipient by a Customer at the same time. In practice, this is understood to mean the entire shipmentSend to An identifier that groups together packages sent from a Sender to a Recipient by a Customer at the same time. In practice, this is understood to mean the entire shipment, even if it consists of several Packing Units., even if it consists of several Packing Units. Management permissions;
whether the Project44 account connection is active;
whether the forwarded consignment ID is available in the consignment;
which Deliveo and P44 events are visible on the dashboard.

A customer’s shipmentSend to An identifier that groups together packages sent from a Sender to a Recipient by a Customer at the same time. In practice, this is understood to mean the entire shipment, even if it consists of several Packing Units.s are not being forwarded

Open the Customers page and check that the ‘Active’ toggle for the relevant customer is switched on.

An incorrect consignment ID is displayed in Project44

Check the shipmentSend to An identifier that groups together packages sent from a Sender to a Recipient by a Customer at the same time. In practice, this is understood to mean the entire shipment, even if it consists of several Packing Units. ID selected on the Settings page.

The available options are:

DeliveoIDUnique primary identifier for shipments in the Deliveo system.
Reference number
Tracking code

After making your changes, click the ‘Save ID settings’ button.

The transmission of a particular event type is not working

Check that the webhook for that specific event has been set up separately. You must use the unique URL displayed on the Project44 Connect page for each event type.

P44 Connect