apparently eshipper has different mapping in production than in development.
I was trying to play around here, (you did it by hand till now?)
my approach has two problems:
I was wondering that maybe we can just use the names they return in the API serviceName
?
{
"baseCharge": 15.3,
"carrierName": "UPS",
"currency": "CAD",
"fuelSurcharge": 2.18,
"fuelSurchargePercentage": 13.75,
"modeTransport": "GROUND",
"serviceId": 604,
"serviceName": "Standard",
"surcharges": [
{
"amount": 0.52,
"name": "Demand Surcharge"
}
],
"taxes": null,
"totalCharge": 18,
"totalChargedAmount": 18,
"transitDays": "4"
},
{
"baseCharge": 15.81,
"carrierName": "Federal Express",
"currency": "CAD",
"fuelSurcharge": 2.35,
"fuelSurchargePercentage": 13.75,
"modeTransport": "GROUND",
"serviceId": 3,
"serviceName": "Fedex Ground",
"surcharges": [
{
"amount": 1.25,
"name": "Delivery Area Surcharge"
}
],
"taxes": null,
"totalCharge": 19.4,
"totalChargedAmount": 19.4,
"transitDays": "2"
},
@danh91 please let me know what you think about this.
Thanks
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
You're funding impactful open source efforts
You want to contribute to this effort
You want to get funding like this too