Discussions

I've posted this in a 3 year old thread which was marked as answered and I'm afraid that it will not be addressed due to seeing other questions after the ticket was marked answered left without the reply. So starting new one, in hopes to receive a reply from EasyShip Team.

In our frontend ecommerce flow, we present customers with shipping rates and allow them to choose their preferred shipping company/method. Our API requests for rates consistently include the parameter "set_as_residential = true".

However, we recently faced a puzzling situation. An order was processed with a delivery charge of $48.80. Our system initially captures the order and the customer’s payment for the chosen shipping rate. Following this, our admin team verifies the order and then forwards (using API) the order to EasyShip for label generation and to arrange pickup from our warehouse.

In this specific instance, despite having "set_as_residential = true" in both requests (front-end and back-end), an additional Residential surcharge of $2.75 was added to the shipment as displayed on the EasyShip dashboard only on the back-end request.

This occurrence is perplexing as the "set_as_residential" parameter was correctly set to true in both instances, and our customers do not have the option to alter this setting (we do not provide any UI controls for customers to switch between residential and non-residential settings).

We would greatly appreciate it if a member of the EasyShip team could provide insights into why this additional surcharge was NOT applied in rates rates_request API route, and assist us in understanding how to prevent such discrepancies in the future.

Thank you for your attention to this matter.