One of our key customers faced a challenge that carriers are raising tickets after 10-15 days of shipment that they are not able to report POD or not able to create a dispute in BN4L. Support team analysis the tickets and found that messages are failing in BN4L-FC side and Carrier never got the document in the freight execution and Freight settlement tiles. On the other side, it is not a practical to regularly monitor “Manage integration logs” App in BN4L. NAV IT implemented the solution to monitor the logs in the background and notify the topic owner based on failure message. For example, we had a common error “Duplicate charge Type”, the monitoring tool identifies the topic owner and triggers an email to the topic owner with the with error detail. This smart solution simply changed the approach from “Reactive to Proactive” and improved the issue resolution efficiency by 40%.

https://nav-it.com/12-challeng....es-we-solved-for-our

12 Challenges – we solved for our BN4L customers in 2024