Combine/Split order using ShipStation's API

Provide more details about orders that are combined in the API. When an order has combined the data that you provide in the API is minimal. You provide no data if the order is combined at the marketplace.

If an order is combined in your application all you provide in the API is the old order Ids under advanced options. We use the API to sync orders into our ERP/CRM. When an order is combined in Shipstation the surviving order only has the other Order Ids. However, the combined order changes the order line items and the API response does not tell you what the old Order Line Items where. A change would be at least provide the old order ID and the Old order line items that were on that order so that line items can be moved. Secondly, if an order is combined in eBay inside the marketplace all you do is mark the order canceled in Shipstation. the order wasn't canceled it was combined with another order just not in shipstation.

I also have the same issue when building some integration with ShipStation. We have a bunch of Shopify stores connected to ShipStation and we are interested getting data about combined orders via ShipStation API. However, the API currently only show ShipStation ID of the orders that are merged, not the original Shopify ID. As non-surviving orders will no longer be visible through the API, there is not consistent way to get the mapping between the Shopify ID and the ShipStation ID. We tried to use webhook to get information about an order as soon as it's imported into ShipStation but it's not consistent

We are in the final stages of building a system that will automatically weigh, dimension, select the correct service, ship, and invoice the order. ShipStation's API is the backend for rates and shipping. It works VERY well, but multi-box shipments are problematic because to my knowledge ShipStation will not let you split an order using the API. This would be a GREAT feature!

If I can create an order, and add items to it via the API - I should be able to do a partial shipment.

'@Admin any update on this. We may have to change to something else because of this. The lack of information that is given when an order is combined is causing hours of extra work each month.

We need to be able to see which order IDs were combined and to have a way to search by these IDs to find which order they were combined with.

Absolutely. For repeat orders that happen before shipping takes place. Need this NOW.

I am also interested. We've been using API but badly need this feature (split / combine)

definitely would like to see info about combined and split orders in the api as it becomes a monthly reconciliation exercise today

I agree - the ability to split orders via the API would be very valuable to us.

I need this as a possibility along with automated dropshipping

'+1 for this feature.

Any update on this?

More Interest from another user.

I am also interested. This is kind of deal braker for my porject now.

'+1 We have many weekly recurring orders that need to be combined or split. We'd love to automate this task.

We could really use this feature. How many responses would it take to get this implemented?

I would like to see this occur - this is especially useful when doing something for preorder, and needing to split a portion of the order from the pre order portion. Very useful from a store owner's perspective and would give more control of orders without added admin

I would love this! But It looks like I will need to write my own method :-(

'+1 !!

We use the Novamodule/Shipstation integration with Netsuite which does not support combined orders. This would be an amazing feature to have the tracking map back from Shipstation to both orders that were combined in Netsuite.

I am really surprised this is not available in the API, is there an alternative?

It would be nice to be able to get the OrderNumber/OrderKey of the merged ids since we can't seem to get the old orders via the api.

This is a big requirement now that we are automating many of our processes and without this feature, we'll be looking for another solution.