Booking tenders can be manually generated once all attached loads have reached Planned operational status. Transportation Manager also supports a Global Setting that can automatically trigger a booking level tender once all attached loads are in Planned status. See the Auto Tender field in “Global Settings – Auto Tendering fields”.
Unlike trips where tenders can be issued at load or trip level, tenders for bookings must be issued at booking level. Therefore, there can be just one active tender applicable for a booking at any time.
If a load is added to a booking after a booking level tender has been issued, events will be generated to indicate that an additional load has been added to the existing tender.
Tenders can only be issued using a tariff service where the “Assign to Booking” flag is True.
When a booking tender is generated, a new row is created in the booking tender requests table. The “List of Booking Tender Requests (Carrier /Employee)” displays tenders generated for bookings. Carriers can respond to open tenders at booking level using this function.
The tender contacts for a booking tender may be computed using the attributes of the loads on the booking. If Tender Contacts have only been assigned for one load, or the same Tender Contact information has been assigned to multiple loads, those values will be used for the booking. Otherwise, Tender Contact information for the load level will not be considered. Tender contact information will be persisted only at load level, with the same data being assigned to all loads assigned to the booking.
When Tender Update is performed for a booking, tender request associated with the booking is updated so that the carrier receives a full description of the booking.
Loads assigned to a booking cannot be tendered and tender accepted at load level.
Booking tender requests have the follow statuses:
Tender requests in Closed, Tender Rejected and Tender Cancelled status are eligible to be purged using "Supplementary Purge (Employee)". Tender requests in Tender Rejected and Tender Cancelled status can be deleted individually from the List of Booking Tender Requests page. Data in the booking tender requests table can be purged before or after the corresponding load is purged.
Carrier sequential tendering (CST) is not supported for bookings. Bookings can be automatically tendered to the assigned carrier but will not be tendered to secondary or tertiary carriers if the tender to the first carrier is cancelled or rejected. It will be up to the logistics planner to decide if a booking should be offered to a different carrier as a booking or be re-organized onto different bookings, Since automatic cancelation of tenders is only available for loads being processed by CST, booking level tenders will not be automatically cancelled if the carrier does not respond to the tender prior to the Tender Response Required By Date/Time.
The following booking level event notifications are supported:
When a booking level tender operation is triggered, the applicable booking level events will be used, if configured. Otherwise, if the equivalent load level event has been configured, the load level event will be triggered for each affected load on the booking.
The "Load Tender Cancelled or Rejected" event notification message is used when a load in Tender Accepted operational status is tender canceled or tender rejected. When a load is in Tender Accepted status, some preparation/execution may have been taking place in the warehouse or plant. Many TM customers rely on this event to trigger certain reversal activities in their ERP. There is no booking level equivalent for this event. When applicable, it will be triggered for each load.
The audit infrastructure in TM supports booking level activity.
Spot rates cannot be assigned at booking level. Furthermore, spot rates cannot be defined for loads attached to a booking. Loads with spot rates are not eligible for optimization. When a load with a spot rate is manually assigned to a booking, the spot rate will be cleared.
When a load with is removed from a tendered booking, the load will lose its association to the booking level tender request and be returned to Planned status.