Merged orders results in an inactive order that is not reachable via API
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.
Caleb
shared this idea
4 comments
-
Charlie Ahn MightyNest
commented
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.
-
brettlilyandfox
commented
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.
-
DZumwalt
commented
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.
-
DZumwalt
commented
Definitely a problem for us in our office. That merged order now becomes a ghost.