I'd like to be able to add multiple tracking numbers to the same line item. The reason for this is that our store has bundled products (products with multiple skus) which can be shipped in different packages. For example, suppose an order is placed for Item A, which is a bundled product containing two skus: 1 & 2. On the Shopify Order, this shows up as one line item of Item A with a quantity of 1. When sku 1 is shipped, I can write back a fulfillment to the line item with a tracking number. However, as of API version 2023-01, fulfillments can no longer have multiple tracking numbers so I am unable to add the second tracking number to the line item when sku 2 ships. Am I missing something or is this use case not supported anymore?
Hey @scolson714 - that is very odd, thanks for getting in touch.
I know that if you're using the fulfillmentTrackingInfoUpdateV2 mutation that is available in our GraphQL admin API - it should allow you to add multiple tracking numbers on one line item. I did notice that our docs do show that there is currently only a "number" field in the "tracking_info" param in the REST version of this call, but in GraphQL the field is named to imply it can take multiple strings as input. Could you share an example body for the call you were using to add multiple tracking numbers in plaintext?
Happy to take a look at this with you - hope to hear from you soon.
I am currently trying to update to the REST Admin API version 2023-01. So to confirm, if I want to add multiple tracking numbers to one line item I will need to use the GraphQL API?
Hey @scolson714 - at the moment, you are correct. You would have to use the GraphQL version of our fulfillments API to add multiple tracking numbers for one item, but I've been in touch with our product team and can confirm they intend on adding the same functionality back into our REST API. I can't guarantee a timeline, but did want to get in touch to let you know the issue has been raised to our developers and they do plan on making this possible again.
Al | Shopify Developer Support
Hello @ShopifyDevSup , My team and our app have similar requirements.
Our primary software for 3PLs/Warehouse fulfillment has a system to create Bill of Materials(BOMs). A lite kitting system. This allows the warehouses to create a BOM then when an order arrives for the Parent SKU the System understands how to split this into the components that will actually be fulfilled.
We use the Shopify REST API. In working on our Shopify Plugin updates to utilize FulfillmentOrders we started noticing issues. When fulfilling, for example, a cabinet kit that ships cheapest by shipping each part separately with the smallest items going by USPS to optimize shipping prices. We currently can only submit the final tracking number to Shopify.
I'm researching options on how to submit more tracking numbers. Our initial compromise was to find a way to stuff the info into a note. That way at minimum the data can be seen by the Merchant, though this is not ideal. If as you said the REST API is in the process of being updated that would be fantastic. Being able to send multiple Tracking Numbers for a single Shopify Fulfillment will be immensely helpful.
Are there any updates on this update?
Just adding a data point here, we would definitely appreciate the REST API being brought to parity with the GraphQL API, lack of multiple tracking number support has been an often reported problem and it is good to know there is support in the GraphQL API but it took a long time to even realize this since we assumed that the APIs were in parity so didn't look at the GraphQL API.
I sure hope this is true and comes in the future. We don't have the time to implement a shift to GraphQL for a single piece of our app just to support a lack of parity between the APIs. Because of this we are going to have to settle for single tracking numbers for the time being until Shopify gets this fixed or redesigns the Ruby API gem to leverage the GraphQL function instead.
At this time, only GraphQL supports adding multiple tracking numbers for one item. The dev changelog is the best place to be updated on any new API features.
Please be sure to post any other fulfillment questions in this FAQ thread here where we've addressed other common issues.
There should be a timeline for this feature....
That is likely a significant reason why the deadline was pushed to next quarter. As long as all of the shipments are under one master tracking number, that's great, but REST only being able to accept one tracking number per Fulfillment Order or line items of a FulfillmentOrder is a big issue.
For example, splitting an order between FedEx and USPS Media Mail.
We used the GraphQL for this one API request and kept the rest of the app using REST which took longer than it would have to use REST but it did work..
So unfortunately it's still not in their REST api. But at least they updated docs about it.
Can't imagine why they didn't integrate in REST yet.