Generate Shipment Weights for Manual Orders and Channel Orders #340

Closed
opened 2026-06-29 08:37:51 +00:00 by rob · 0 comments
Owner

In order to successfully implement issue #209 we need to make sure we can provide EasyPost the weight of the Shipment.

eStack stored the SKU weight in the SKU's Info tab: https://cb.estack.com/products/30127

As you can see there, the SKU is 1.61 ounces.

Now, look at this Shipment in eStack: https://cb.estack.com/retail/shipments/227209

You can see the weight of this Shipment is also 1.61 ounces.

To get the most accurate weight we can, we need to sum up the the SKU weight * quantity ordered + 1 unit of Packaging weight.

Packaging in eStack (not easypost) is the type of packaging material we will use to ship the shipment. For example, a carboard box, a polybag, or a bubble mailer. Each of these types (and sizes) will have different weights. Packaging weight must be added to the shipment weight total in order to accurately get a total package weight.

See here for the eStack Packaging Classes:

https://cb.estack.com/packaging-classes

For the moment, we can build this out with just the Default Packaging assigned to each order. However, later we will want to allow the user to toggle the Packaging type on the Shipment to best fit the shipment contents.

For example, a customer orders 5 different SKUs in one order. The shipment should calculate the total weight of the SKUs/Quanties, plus the Packaging weight from the selected Packaging Class for that order.

If the shipment selected the 'Default Packaging' but the order is too big for that packaging, then the user must be able to change the Packaging Class to a more suitable option like the 'Medium Box', for example.

The Shipment should then have the new total weight of the SKU weight * Quantity + selected Packaging Class.

SKU-level_Product_Weight

Packaging_Class_Weights

eStack_Shipment_Weight_from_SKU_+_Packaging

cc: @tim

In order to successfully implement issue #209 we need to make sure we can provide EasyPost the weight of the Shipment. eStack stored the SKU weight in the SKU's Info tab: https://cb.estack.com/products/30127 As you can see there, the SKU is 1.61 ounces. Now, look at this Shipment in eStack: https://cb.estack.com/retail/shipments/227209 You can see the weight of this Shipment is also 1.61 ounces. To get the most accurate weight we can, we need to sum up the the SKU weight * quantity ordered + 1 unit of Packaging weight. Packaging in eStack (not easypost) is the type of packaging material we will use to ship the shipment. For example, a carboard box, a polybag, or a bubble mailer. Each of these types (and sizes) will have different weights. Packaging weight must be added to the shipment weight total in order to accurately get a total package weight. See here for the eStack Packaging Classes: https://cb.estack.com/packaging-classes For the moment, we can build this out with just the Default Packaging assigned to each order. However, later we will want to allow the user to toggle the Packaging type on the Shipment to best fit the shipment contents. For example, a customer orders 5 different SKUs in one order. The shipment should calculate the total weight of the SKUs/Quanties, plus the Packaging weight from the selected Packaging Class for that order. If the shipment selected the 'Default Packaging' but the order is too big for that packaging, then the user must be able to change the Packaging Class to a more suitable option like the 'Medium Box', for example. The Shipment should then have the new total weight of the SKU weight * Quantity + selected Packaging Class. ![SKU-level_Product_Weight](/uploads/bd9fdfd5db004bc7f7a2954fe5a437e9/SKU-level_Product_Weight.png) ![Packaging_Class_Weights](/uploads/c88a49829a41181b2ae0a4e6ca8c5534/Packaging_Class_Weights.png) ![eStack_Shipment_Weight_from_SKU_+_Packaging](/uploads/9803aaf37410f834392ca453bd1ed089/eStack_Shipment_Weight_from_SKU_+_Packaging.png) cc: @tim
rob closed this issue 2026-06-29 08:37:51 +00:00
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: rob/pms3#340