Transportation management- RFQ restarts up to 99 times

[singlis9]

Hello Transportation Management experts,

We use peer to peer waterfall tendering from our Road Freight orders, the tenders are sent to the carrier highest in the list based on cost, on rejection or non acceptance from the carrier it flows to the next carrier in the ranking and so on…in the case the carriers reject or don’t accept in the time lines given the system restarts the process again and again and again up to 99 times! This can be very annoying for our carriers. We use a freight order selection profile to identify what freight orders to start tendering from but I don’t see any option to omit those freight orders that have been through tendering or have been rejected. I must be missing something.

so my question, can we limit the restarting of tenders/rfqs for freight orders that have been rejected by the carrier or even not accepted?

thanks!

[yannicktuemmler]

Hi Stuart,

you might want to look into creating a condition based selection within the profile & want to use a data-crawler to check in the tendering node if (or many) tendering attempts have been happening already

[singlis9]

Hi Emanuel,

Thank you for your reply!

Based on my testing the flag controls whether the system should initiate the tendering process again or not where a carrier initially accepts the tender, then later they change their minds and rejects the tender.

Hopefully there is a solution available.

Thanks Stuart..

[GRABLERE]

Hi Stuart,

have you checked out following setting in the tendering process settings:

I also will try to check if there is maybe a bug. Based on the F4 Help the idea of the flag seem to be that tendering is restarted if the next step subcontracting is rejected by a carrier that was previously selected by tendering. However from a first glance at coding and your descritpion maybe also the RFQ rejection is retriggering it. Still you can check the flag if it will solve your issue.

Regards,

Emanuel