Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Response to carrier if appointment location is not using the Appointment Scheduling Tool in fetch available appointments #15

Open
E2openProductManagement opened this issue Jul 15, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@E2openProductManagement
Copy link

E2openProductManagement commented Jul 15, 2024

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.

@miller79 miller79 added the enhancement New feature or request label Jul 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants