Use Case: As a carrier, I can only leverage the API for Shipping Company A's appointments if they are enabled with the Appointment Scheduling Tool. In this example, it would be beneficial for the API to return a response to my TMS if a user attempted to schedule an appointment for the 4PL location that is not leveraging the Appointment Scheduling Tool for Shipping Company A.
Example: Shipping Company A manages all of their freight through the TMS and has 5 distribution centers within their network; 4 are operated by Shipping Company A and 1 is operated by a 4PL. The 4 distribution centers managed by Shipping Company A are enabled with the Appointment Scheduling Tool through their TMS, therefore carriers can schedule via the API, and the 1 4PL distribution center requires the carrier to schedule the appointments through phone call. As a carrier, I would be reliant on tribal knowledge that only 4/5 locations for Shipping Company A can be scheduled via the API.
Use Case: As a carrier, I can only leverage the API for Shipping Company A's appointments if they are enabled with the Appointment Scheduling Tool. In this example, it would be beneficial for the API to return a response to my TMS if a user attempted to schedule an appointment for the 4PL location that is not leveraging the Appointment Scheduling Tool for Shipping Company A.
Example: Shipping Company A manages all of their freight through the TMS and has 5 distribution centers within their network; 4 are operated by Shipping Company A and 1 is operated by a 4PL. The 4 distribution centers managed by Shipping Company A are enabled with the Appointment Scheduling Tool through their TMS, therefore carriers can schedule via the API, and the 1 4PL distribution center requires the carrier to schedule the appointments through phone call. As a carrier, I would be reliant on tribal knowledge that only 4/5 locations for Shipping Company A can be scheduled via the API.