I have a product in Shopify with the weight set to 1 lb.
I’m using a solution based on the Carrier Service API, where the product weight is critical.
In the Carrier Service API, the weight is returned in grams. For this product, I’m getting 454 g.
The issue is that 1 lb = 453.59237 g, so there’s a rounding discrepancy.
When I convert this value back from grams to pounds, I get:
454 g = 1.00089867 lb
Our app uses weight-based calculation rules, where the merchant sets them according to the unit used in their store. Because of this inaccuracy in CSA, discrepancies occur.
Could you make the Carrier Service API return more precise weight data (e.g. with higher precision instead of rounding to whole grams)?
Hey @sebastian.pisula, thanks for flagging this, I’ll reach out to some folks internally to investigate this further and loop back with you once I have next steps to share. Speak with you as soon as I can on my end here!
Hey @sebastian.pisula - just following up here, our calculations for weight round up to the nearest whole number, which is why we’re seeing 454 g in this case. That said, I definitely realize it’s not the most ideal, so I’m happy to log a feature request for you so we can consider making adjustments to the method in the future.
Would you be open to sharing more about your use case if possible, including if you’re seeing any large scaling issues so I can properly advocate on my end since I do realize this could potentially cause headaches when it comes to managing parcel weights, etc? Hope to hear from you soon, happy to advocate for the feature on my end here for sure.
Thanks for getting back to me. From our perspective, this is a significant issue. Since our app relies on the Carrier Service API for weight-based shipping cost calculations, the rounding leads to inaccurate shipping rates being displayed to customers.
We’ve seen cases where this causes shoppers to abandon their carts because the cost does not properly reflect the actual weight of the order. Ultimately, this impacts merchants’ revenue.
We are the developers of a shipping app that integrates with the Carrier Service API, and we’ve observed this problem across multiple clients. That’s why we believe it’s important to address.Please let me know if this gives you enough context to move the request forward. Thanks again for your help in advocating for this.
Thanks @sebastian.pisula for following up here, really appreciate your perspective on this and as I mentioned, I can see how it’s not the most ideal limitation. I can’t guarantee anything on my end here, but I will reach back out to our product team to see if I can log a feature request for you at the very least as I mentioned/to see if there is a way to expedite this.
I’ll be in touch again here in the thread with more info as soon as I have that for you.