Last Mile Carrier Status Tracking
Author:
Movyn John
Changed on:
15 July 2025
Target release date: | 2025-07-16 |
---|---|
Release status: | Released |
Description
Fluent Commerce is collaborating with the Shippit team to offer an enhancement to the tracking details available within the Fluent Commerce platform for our shared user base. Currently, Shippit provides a tracking reference number for each as it is labelled via the existing . Our shared goal, is to expand the information made available to merchants in Fluent Commerce, providing them with the individual events as a fulfilment traverses on its journey from to a delivery to the customer. The consumption of these tracking events from Shippit, in real time, can be utilised to support retailer and customer visibility and analytics within the Fluent platform.
Changelog
Initial release
- Fluent Commerce Integration with Shippit
- Fluent will maintain and enhance the integration with Shippit to support ingestion of tracking event data.
- Real-Time Tracking Event Ingestion
- Tracking events from Shippit will be fed into the Fluent Commerce platform as they occur.
- Support for Existing and New Merchants
- The tracking event integration will be available to all merchants using the Fluent-Shippit connector.
The following events are excluded, as they are handled internally within the existing workflows:
`order_placed`
(Carrier Order Booking process)`despatch_in_progress`
(Label Booking process)`ready_for_pickup`
(Manifest process)`pickup_failed`
(Pickup failed is currently not used for processing or analysis)
The events consumed and their definitions are given below:
- In Transit - The order is collected and on its way to the depot or travelling between depots.
- With Driver - The package(s) are on board for delivery to the recipient.
- Delivery Attempted - The driver attempted to deliver, however no one was available to receive them. This will only occur for orders without an "Authority To Leave" assigned.
- Completed - The package(s) were delivered to the recipient.
- Returned To Sender - The package(s) were returned to the merchant. This could occur for a number of reasons such as the recipient refused, exceeded delivery attempts, incorrect address, failed to collect, damaged, etc.
- Damaged - The package(s) were damaged
- Lost - The package(s) were lost
Released capability depth: | Enhancement |
---|---|
Release bundle / Capability type: | Connector framework, Fluent OMS |