Implement 'Shipping Class' to Shipments and SKU-level Info tab #339

New Issue

2026-06-29T08:37:51Z

rob commented

2026-06-29 08:37:51 +00:00

To successfully implement issue #209 and #210 we need to add a couple of functions first.

Add a drop-down field called 'Shipping Class' and 'Packaging Class' under the 'Weight' field (see mockup screenshot below).

Previously, we had something called 'Postage Classes' located here: https://cb.estack.com/postage-classes but the link seems to be broken at the moment. Postage Classes currently holds basic info about which shipping services the user creates in the system.

Let's change the name/label 'Postage Class' to 'Shipping Class' as some shipments will may out by UPS or FedEx (not the post office).

Let's try and fix the broken postage-classes page and see if we want to use what's there. I believe we can use what's there to build out the EasyPost service mapping. If we don't want to use what's there, we can make a new page.

Since we are starting with EasyPost, we want to first allow the user to add EasyPost as a Shipping Class. This means they need to have some kind of setup process for the user to connect their EasyPost API keys.

Please create a 'EasyPost' button on the page that sends the user to a form in which they can add their Easypost API keys (both test and production keys). They also should have the option to be in Test or Production mode, and eStack should use the correct API key depending on their choice.

Once they connect their EasyPost account, the page should populate which EasyPost services we support. For the first iteration, let's just offer USPS services. Let's call the EasyPost Shipping Class for USPS services 'EasyPost - USPS'.

Any service options such as USPS First Class Mail or USPS Priority Mail should be labeled 'EasyPost - [service name]' or similar so it is clear for the user.

Once this is done, we can add the drop-down menu at the SKU-level to allow the user to set the default Shipping Class for that SKU, and also one drop-down menu on the Shipment-level to allow users to change the shipping service on a Shipment before they process and print the Shipments.

I will create a seprate issue for Packaging Classes

To successfully implement issue #209 and #210 we need to add a couple of functions first. Add a drop-down field called 'Shipping Class' and 'Packaging Class' under the 'Weight' field (see mockup screenshot below). Previously, we had something called 'Postage Classes' located here: https://cb.estack.com/postage-classes but the link seems to be broken at the moment. Postage Classes currently holds basic info about which shipping services the user creates in the system. Let's change the name/label 'Postage Class' to 'Shipping Class' as some shipments will may out by UPS or FedEx (not the post office). Let's try and fix the broken postage-classes page and see if we want to use what's there. I believe we can use what's there to build out the EasyPost service mapping. If we don't want to use what's there, we can make a new page. Since we are starting with EasyPost, we want to first allow the user to add EasyPost as a Shipping Class. This means they need to have some kind of setup process for the user to connect their EasyPost API keys. Please create a 'EasyPost' button on the page that sends the user to a form in which they can add their Easypost API keys (both test and production keys). They also should have the option to be in Test or Production mode, and eStack should use the correct API key depending on their choice. Once they connect their EasyPost account, the page should populate which EasyPost services we support. For the first iteration, let's just offer USPS services. Let's call the EasyPost Shipping Class for USPS services 'EasyPost - USPS'. Any service options such as USPS First Class Mail or USPS Priority Mail should be labeled 'EasyPost - [service name]' or similar so it is clear for the user. Once this is done, we can add the drop-down menu at the SKU-level to allow the user to set the default Shipping Class for that SKU, and also one drop-down menu on the Shipment-level to allow users to change the shipping service on a Shipment before they process and print the Shipments. I will create a seprate issue for Packaging Classes ![Screen_Shot_2020-02-19_at_10.15.09_AM](/uploads/24bbee451db2c20004ae4952d2bbbee5/Screen_Shot_2020-02-19_at_10.15.09_AM.png) ![Screen_Shot_2020-02-19_at_10.50.52_AM](/uploads/c7e3c31e01b16d01f9e97dd8eb685b85/Screen_Shot_2020-02-19_at_10.50.52_AM.png)

rob added the QA label 2026-06-29 08:37:51 +00:00

rob closed this issue

2026-06-29 08:37:51 +00:00

Sign in to join this conversation.

No Label QA

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: rob/pms3#339