I'm working with the fulfillment orders API endpoints and I have the following use case:
1. FULFILLMENT_ORDER1 on LOCATION1 has the following items:
2. FULFILLMENT_ORDER2 on LOCATION2 has the following items:
The use case is the following:
I do a first fulfillment fulfilling only FO1Item1 and everything goes ok.
Then I want to do a second fulfillment with the same tracking nb and the following items taken from LOCATION2
But to do this I will first need to move FO1Item2 and FO1Item3 to LOCATION2 with the move.json endpoint in fulfillment orders. When I do that according to the API this will happen:
Second scenario: Re-assign a subset of the line items belonging to a fulfillment order to a new location. You can specify a subset of line items using the fulfillment_order_line_items field under the FulfillmentOrder parameter (available as of the2023-04 API version), or specify that the original fulfillment order contains line items which have already been fulfilled.
If the new location is already assigned to another active fulfillment order, on the same order, then the line items are moved to the existing fulfillment order. Otherwise, a new fulfillment order is created
So according to the API doc the expected result should be:
But what is happening in fact is that a new Fulfillment order is created containing the items I wanted PLUS the one remaining in FULFILLMENT_ORDER2, and that FULFILLMENT_ORDER2 is closed:
That is different from what the API doc is saying. I wanted to confirm what is the expected behavior