You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When checking out on the shipping selection step, there is a Delivery Date column for the available methods that are returned and can be selected.
It looks like this date is correctly populated for real-time rate lookups from the API response for the carrier (ie. USPS Priority Mail as shown in the screen capture below), but may be worth checking to ensure it is working correctly.
For table rate methods (all other shipping methods shown in the screen capture below), this may not be accurately displaying an estimated delivery date. There isn't anywhere in the configuration for a table rate method to set an estimated delivery timing, so not sure how the date shown in the screen capture is being calculated for display.
One thing that is possible to configure for table rate methods is the Description field - which could be used for this or other purposes, but is not currently being displayed on the front end at all, although in our backend the cues state that it will be shown on the front-end if provided. Should we add this to the front-end display somewhere as well?
The text was updated successfully, but these errors were encountered:
When checking out on the shipping selection step, there is a Delivery Date column for the available methods that are returned and can be selected.
It looks like this date is correctly populated for real-time rate lookups from the API response for the carrier (ie. USPS Priority Mail as shown in the screen capture below), but may be worth checking to ensure it is working correctly.
For table rate methods (all other shipping methods shown in the screen capture below), this may not be accurately displaying an estimated delivery date. There isn't anywhere in the configuration for a table rate method to set an estimated delivery timing, so not sure how the date shown in the screen capture is being calculated for display.
One thing that is possible to configure for table rate methods is the Description field - which could be used for this or other purposes, but is not currently being displayed on the front end at all, although in our backend the cues state that it will be shown on the front-end if provided. Should we add this to the front-end display somewhere as well?
The text was updated successfully, but these errors were encountered: