Welcome to the Help Centre for Notifications Webhook
Learn what this product does, how it works, and how to get set up…
The Notifications Webhook allows you to configure endpoints to receive high-level status updates for multiple carriers in a consistent and normalised fashion.
It listens for specific events for a subscribed parcel. Once an event has been received, a standardised payload is pushed to the specified endpoint(s). This means you can share status updates with your consumers using your own email, SMS, or other CRM tools.
The notifications payload will include data such as the event, event date and time, order number, email, phone number, carrier name, and the expected delivery date (defined at allocation ) and other related information.
The tracking experience is one of the most important aspects of the ecommerce journey and customers expect to receive regular tracking updates, whether this be by email, SMS, or both. Failing to provide tracking updates risks negatively impacting customer retention and brand reputation.
By sending proactive notifications to your customers, you not only reduce the number of 'where is my order?' (WISMO) queries but you also increase engagement and improve customer satisfaction by providing a better post-purchase experience.
These features are the main fields. For the most up-to-date schema please refer to our Track parcels with Notifications Webhook developer docs article.
-
Works with Metapack's shipping platform or standalone
-
Self-service configuration via our User Interface (UI)
-
Standard Payload
-
Recipient Name
-
Email Address
-
Mobile Number
-
Order Number
-
Delivery Type
-
Carrier Name
-
Has expected delivery date changed? (Y/N, Boolean)
-
Estimated Delivery Date - Delivery Window
-
Carrier Tracking ID
-
Sender Country Code
-
Recipient Country Code
-
Normalised event code + normalised event description (and date/time stamp of the event)
-
High-level parcel journey status code + high-level parcel description
-
Exception description ( in case an event is an exception)
-
-
Enriched tracking data
-
Fixed triggers
-
IN_TRANSIT
-
COLLECT_AT_LOCAL_PO
-
OUT_FOR_DELIVERY
-
CUSTOMER_CARDED
-
CUSTOMER_TO_COLLECT_FROM_CARRIER
-
DELIVERED
-
DELIVERED_TO_PO_BOX
-
DELIVERED_TO_NEIGHBOUR
-
DELIVERED_SPECIFIED_SAFE_PLACE
-
PARCEL_COLLECTED_FROM_PICKUP_POINT
-
PARCEL_DAMAGED
-
AWAITING_COLLECTION_FROM_PICKUP_POINT
-
DELIVERED_TO_LOCKER_COLLECTION_POINT
-
DELIVERED_TO_ALTERNATIVE_DELIVERY_LOCATION
-
ATTEMPTED_DELIVERY
-
ATTEMPTED_DELIVERY_2ND
-
ATTEMPTED_DELIVERY_3RD
-
NO_ACCESS_TO_RECIPIENTS_ADDRESS
-
ROUTING_ERROR
-
ADDRESS_QUERY
-
DELAYED_NOT_CARRIER
-
CARRIER_DELAYS
-
CUSTOMER_CARDED
-
PARCEL_LOST
-
CUSTOMER_MOVED
-
NOT_DELIVERED
-
-
Metapack ‘listens’ for any event that matches the trigger list of preselected events. If the event belongs to a parcel/retailer that has subscribed to the Notifications Webhook then a set of data is pushed to the endpoint(s) you've configured
You can use the Notifications Webhook with Metapack or other shipping tools. For the latter, please follow this link: Work with Notifications Webhooks through Tracking API. Then, proceed with the steps detailed below.
To get started with the Notifications Webhook, there are two key steps to follow: