API - multiple packages

This is a very important feature that seems to be missing.

I think we need this as well.

I agree!

This would save us thousands of hours of labor in manually entering packages and weights.

This is an absolutely critical feature for us, at our scale we cannot have people manually entering in package data.

I can't use Shipstation without it.

Definitely would be huge for us.

we need to be able to either import multiple package via CSV or use API. Most companies that have separate ERP system would create pick-and-pack packages in their system, which already generates this info. It doesn't make sense to have to re-enter this into shipstation. It should just be imported via CSV or API.

ShipStation is incredibly powerful, but this is one of the many "small" missing features that prevent it from excelling as a true B2B solution. People below have suggested API integration back to the ERP — which would obviously be welcome! But in the meantime, why not just enable "Change # Of Packages" from Apply Bulk Actions to at least automate some of the process?

Ryan, is this a solution/work around for people using API? If so, can you please provide more details? "But in the meantime, why not just enable "Change # Of Packages" from Apply Bulk Actions to at least automate some of the process?"

Hi Stephen — sorry for not being clearer. My comment was directed at ShipStation — I was hoping that they could implement the ability to "Change # of Packages" through their Apply Bulk Actions feature. If you're not familiar with Apply Bulk Actions, select more than order in your shipping queue, and then click Other Actions —> Apply Bulk Actions. This enables you to make uniform changes in bulk to multiple orders.

'+1

Any idea on how long the review process takes? this says it's been under review since September 2015...

Definitely an automated rule that allowed you to add preset multiple package configurations would be amazing!

This is a Huge need for us to use this program on a larger scale. In our scenario (with a different shipping program) we put a flag on products/items that should be shipped alone, let's call it "SOLO Ship". This could be defined in the API as well as on an item setup level (so this gives a method for both API and non API setup). So a few examples of how I envision this working. 1. Order with 5 items flagged with "solo ship" = 5 packages with weights pulled from each item. 2. Order with 2 items not flagged = 1 package with combined weight. 3. Order with 5 items flagged with "solo ship" and 2 items not flagged = 6 packages first 5 weights are pulled from first 5 items, 6'th package is last 2 items weight combined. I'm really hoping this will be a possibility in the near future!

This is something we need it badly and real fast. Because we are using a workaround method and we have separate every order based on the quantity of its order item. So 1 order =1 quantity so we create 10 different orders in Shipstation for a order with 10 quantities to handle multiple packaging scenario. It would be great if this feature is added in the order creation API. Would love to see this feature and stop using the workaround.

Any update on this?

Please add this feature. We ship large furniture items via FedEx. These items are a single sku with a single quantity on an order but it must ship in multiple packages. Currently there is no way to set automation rules to assign multiple packages or a pre-saved package set. This seems like "no-brainer" functionality. The current system forces us to individually prepare each shipment which takes on average about 4-6 different "clicks". This should definitely be added.

This feature would be very useful for our company. We have built an integration from our CRM to ShipStation via the API, and we create all of our orders in the CRM without having to log into ShipStation. With this feature we would be able to create orders with multiple packages from our CRM.

This is a failure to have parity across your API's. Your back-end services can obviously handle such a request. There seems to be little reason why an external API call cannot. If this is a compatibility issue then consider API versioning so that we can access later features without worry of breaking BC. If it is a matter of trying to push the web site as the main product I see little reason why people who would use less resources yet pay the same price as those who use more should be unfairly and unnecessarily punished with a reduced feature set. Are you familiar with the dog food principle? This very issue seems to be a very necessary use case for such a thing. Your customers are unable to use the full feature set offered to us by other SUPPORTED means and it is a real issue. Obviously, as an outsider I do not know the internal workings of your company. However, as a programmer, I know that this sort of product disparity is inefficient and requires lots of extra overhead to make functional. Please add more priority to making it a possibility.

Hello? MPS? When please?

logging out to go log in to the carriers website to save money shipping mps....

Can't move to ShipStation without it. Hope we can at least get an update on status/timeline here. Thanks

If this isn't implemented, we'll be forced to investigate alternate services. Creating multiple package shipments manually is a huge waste of time. We can easily automate this if the API simply supported "Packages".

We are new to SS. But not having the ability to automate multiple packages slows down our entire process.