Yes! We did go ahead and implement ShipperHQ and it’s been pretty good so far, I give it a solid 9/10.
We split the project into two phases - 1) implement a ShipperHQ customization in Epicor 2) implement ShipperHQ on our Adobe Commerce (Magento) website. We completed phase 1 during the summer and are working through phase 2 now.
In Epicor our customization was basically a Function Library that called ShipperHQ’s API. In Quote and Sales Order Entry we have a button to trigger the Function API request, and it sends weight and dims data about the parts on the quote/order. ShipperHQ figures out how to box it and then the API returns a dataset of different carriers / rates with different packaging options. We display all that in a grid for the user and they can select an option from the grid and click a button to add a freight Misc Charge to the quote/order and also update the ship via.
Here’s the thing though… The true challenge is NOT about anything technical. It’s about data and knowing your company’s shipping scenarios inside and out. @doug.harvey led the implementation for us and spent months architecting how all of our goofy products and shipping scenarios mapped on to how ShipperHQ thinks about packaging and carriers, etc… You need someone like Doug to mastermind how all the pieces come together, otherwise your shipping estimates aren’t going to be that good.