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
I'm sorry to have to discuss the CustomerClassification property again. After a few weeks of correspondence with UPS API support in Germany, it has now become clear that the CustomerClassification property/container is valid if ShipFrom country or territory is US. The list prices, which are also displayed here https://wwwapps.ups.com/ctc/request?loc=en_en, we receive over the API call when we omit the CustomerClassification property. However, omitting it is no longer possible because the value for CustomerClassification is taken from the public enum UPSCustomerClassification.
The following solutions would be possible:
a) The "CustomerClassification" property should be nullable and if the value is null, then this value should not be in the request string;
b) The "CustomerClassification" property only for deliveries from the USA - as it was originally;
I could imagine a combination of both points. Alexey, what do you think, how can we clean this up again?
The text was updated successfully, but these errors were encountered:
We are still receiving incorrect list prices from the UPS API. According to customer service, the request string should not include the 'CustomerClassification' property. However, we currently cannot exclude this property. Is there a possibility of implementing a solution in the near future? As suggested, the 'CustomerClassification' property should be nullable. If the value is null, then it should not be included in the request.
I'm sorry to have to discuss the CustomerClassification property again. After a few weeks of correspondence with UPS API support in Germany, it has now become clear that the CustomerClassification property/container is valid if ShipFrom country or territory is US. The list prices, which are also displayed here https://wwwapps.ups.com/ctc/request?loc=en_en, we receive over the API call when we omit the CustomerClassification property. However, omitting it is no longer possible because the value for CustomerClassification is taken from the public enum UPSCustomerClassification.
The following solutions would be possible:
a) The "CustomerClassification" property should be nullable and if the value is null, then this value should not be in the request string;
b) The "CustomerClassification" property only for deliveries from the USA - as it was originally;
I could imagine a combination of both points. Alexey, what do you think, how can we clean this up again?
The text was updated successfully, but these errors were encountered: