Background Scope Finland: Track and Trace for outbound deliveries from LC. Second phase is the visibility for the whole SC -> transit/direct/store shipments.
Definition of Done:
Ahlsell Finland and Norway flow from Astro to Addimotion is done.
Separate channels for Sweden, Norway, and Finland have been created in Addimotion.
CME App has been deployed to 30% last-mile transporters in Finland who do not have their own scanning solution.
Tracking events from Centiro have been integrated to Ahlsell/Kafka/Addimotion (CME generated and all others).
Order information has been shifted from Astro to Vivaldi for integration into Addimotion so that transit orders are included in Addimotion.
Tracking events are synchronized from Addimotion to Ahlsell Kafka topics for all orders and all countries (Sweden, Finland, and Norway).
Tracking events are consumed by web and app to show web/app users the shipping/tracking status of their orders for all countries (Sweden, Finland, and Norway).
Notifications can be sent to either email, SMS, or push notification in-app based on user preferences.
The web/app user can configure what kind of information is pushed to them as a base config but also change on individual orders.
WEB parts: Part of the reason is to meet the previously given promises to among others our customer Elinorr.
The initial objectives in this initiative is to
make the service available for NO & FI
make the service Customer oriented, meaning that we will try to lift this into “My pages” and show what the customer is having “on the way to them”
We, Team WEB & UX team are having interviews with customers to better understand their needs and how they use T&T in other places.
Miro board link for the work and discovery: Password: trackntrace
Background information - Addimotion AS IS: There are a vast number of status codes available today. RG83 & RG86 are notifying customers via SMS regarding:
Unloading according to the unloading agreement
Unsuccessful delivery. Delivery couldn't be performed
Goods are returned to the terminal
The SMS messages are sent to the phone number specified on the order, which is entered by the customer on the web (alternatively the default logged-in phone number?), from the delivery address chosen (both manual or web order) or the phone number specified on the manual order or fetched in on the EDI order.
In RG83, BDX is fully mapped in Addimotion. Schenker is in the process of starting to code for, for example, "Unloading according to the unloading agreement". Previously, files were sent from Hallsberg to Addimotion about excluded goods. This information chain was interrupted but resumes today, enabling Addimotion to signal about this.
Addimotion is working on being able to group at the shipment level, so that one can then see orders/packages and their status beneath that.
What is required from Ahlsell and our transport partners to create value in Addimotion?
Each carrier's status/scanning codes must be reviewed and mapped to what we want to notify the customer about.
All carriers must systematically work with codes and scanning at the parcel level (shipment level is not enough).
Only BDX & Schenker are onboarded today.
Is there information in Addimotion today?
Many carriers exist in Addimotion today, even though not all are connected for Ahlsell. For instance, Postnord probably is already there, even if we cannot see it today.
Information on the web
There was a prototype on the web earlier, similar to below where one could see statuses. However, it has been removed now, and it's unclear why.
Other
Can Addimotion function work Nordic today? Or if we capture status updates to Kafka and create Track n Trace info for customers based on that - are there other players in other countries who can do the same for their respective countries?
How can we capture direct Procurements in Addimotion? Do our suppliers leave any trace that clearly indicates that this should go to an Ahlsell customer, along with our purchase order number that we could then link to the customer order?
If we create a smart solution in the App & Web, we can capture info regarding orders that the currently logged-in user has registered and push deviations, etc. to them. How can we find the right customer to communicate with in the App/Web when it comes to EDI or manually registered orders? Can/Should phone numbers be mapped against web users' phone numbers and notify where we get a match and ignore the rest (obviously one should be able to see the status of each order in the App/Web regardless of who registered it)?
Carl Granlund
Martin Holmin