Hello, We were not able to find a workaround for this, I don't recall why but when we attempted to use the GraphQL solution it did not fit our needs.We had to make a compromise with our users to only send the first tracking number if this occurs, sin...

We have hit this issue in the past and were told that there was a bug in the Orders API when using specific parameters that caused orders to not appear, we were also told that this was fixed. Potentially there is a new issue somewhere. (previously re...

I did look into the GraphQL version of the API to see if this could help us. I have a question around functionality. Is it expected behavior that the 'notify customer' only triggers sending the first tracking number to the customer? I would expect al...

Unfortunately this looks like it is only for the GraphQL API, not the REST API. I tested it in rest 2022-10 just in case. It responds with a 201 created, but only with the first tracking number. Looks like there's still this functionality gap in the ...

We are working on migrating to the new fulfillmentOrder API route due to the fulfillment deprecations. I am working with the REST API and it looks like you can only add one tracking number per fulfillment. The old create Fulfillment API supported add...

Is there anyone that can help with this?We have had even more occurrences of customers reporting this. All of them occurred between 6/7-6/8.We reported this via the partner portal but the only response we got was saying to include status=all, which g...

We work with multiple stores to pull orders in specific statuses based off of last updated date.On multiple occasions, we have noted several orders missing when they should have returned in the response. On each occasion there has only been one page ...