Merged orders results in an inactive order that is not reachable via API

[CalebP]

When you merge 2 orders, one order ends up inactive. The surviving order has a advancedOptions.mergedIds array with order IDs that are not reachable. Asking for them gives you a 404. There should be a way to query an inactive order.

[dan_zumwalt]

Definitely a problem for us in our office. That merged order now becomes a ghost.

[dan_zumwalt]

Definitely a problem for me. The merged order becomes a ghost, even if I need to access the information after the fact. There are times when I need to determine what order is now the parent to this order.

[brett2]

Including inactive orders in API responses would be very useful when fetching recently updated - to see that an order has been made inactive is more convenient than it apparently vanishing, as far as the API is concerned.

[charlie7]

Not being able to access the 'orderNumber' of orders that have been merged is an issue for us. Unfortunately have the merged 'orderId' is not enough to clean up order data on our side.

[dbminting]

Was there every a solution for this? I still can't find anything with a merged ID.

[CaraAdmin]

Hello, @dbminting!

Thank you for your post! I understand how important this is to you. I reached out to a few folks, and they recommend contacting apisupport@shipstation.com. They’ll be able to assist you further. 

Happy Shipping!

-Cara