Hi, as a developer in non-english speaking country, we want to know the exact deadline for the migration of product/variants gql.
The by February 2025
, does it means we should finish the migration before 2025.01.31
or 2025.02.28
?
Hi, as a developer in non-english speaking country, we want to know the exact deadline for the migration of product/variants gql.
The by February 2025
, does it means we should finish the migration before 2025.01.31
or 2025.02.28
?
Hi Jaron,
You should finish the migration before 2025.01.31 - the deadline is Feb 1st 2025. Are there any specific areas that you’re blocked on currently?
Hey @Liam-Shopify
I also have something that’s blocking us from migrating, which is why I’m asking: will the Products API shut down entirely? Or will we still be able to make requests?
Unless Shopify provides a proper migration path for the REST API, migrating isn’t feasible. For example, the measurement
information cannot be provided via the ProductSet
payload. This measurement data is crucial for price calculation!
Any updates on this? (i have created a community post regarding this: Re: Unable to provide weight & weight_unit in ProductSet variations payload - Shopify Community)
Can you say more about why this is blocking you? We have added capability to add media (files) and activate quantities appropriately, and we are considering adding other Inventory related fields, but TBH cant commit to that.
measurement
informations like weight can not be provided using ProductSet (InventoryItemMeasurementInput - GraphQL Admin)
We, as developers, were told to use the ProductSet GraphQL as a migration path to replace the REST API. However, it is actually missing some very important fields, such as measurement
. Many products in Shopify are priced based on weight, and we are unable to provide this information anymore.
Using the bulk commands is far too complicated and provides no clear migration path!
Someone suggest me to this, instead of a “single” call:
That’s insane, its not possible to manage all those calls, there are also api rate limits to consider, this will never run stable when you have 100 of products. Sometimes your calls get rate limited then maybe an update call won’t run anymore, and so far.
I think that call stack is not needed as of 2024-10, highly recomment taking another look at the productSet mutation
specifically:
- productSet mutation to create or update the product
ok
- productOperation query to get the set operation and the product
It’s possible to avoid productOperation by calling productSet with synchronous set to True (itis also the default)
- productDeleteMedia to clean up old media (if it’s an update)
- productCreateMedia to append the new media
It’s possible to avoid these calls by passing in input.files object
- productVariantsBulkUpdate to set up inventory item for product variants
- inventorySetQuantities to enable fulfillment inventory
It’s possible to avoid there by passing in the info on the input.variant object
- publishablePublish to publish the product to the online store
Yes, this is still needed
Thanks for the reply @Asaf_Gitai – well, using ProductSet with the option to have measurement
in the variants would handle everything in a single call, like we did before with the REST API. So we are hopefully waiting for measurement
in this ProductSet call, which is designed to be a replacement for the REST API, and also advertised as replacment by Shopify. Is this on the roadmap? And when will the products API shut down?
We have created a headless content hub with many clients, and they are all syncing many products now (using the REST API). As mentioned, we won’t be able to upgrade, even though we have everything prepared, but we’re missing the measurement
information.
@Nadar While there is always room for further improvement, I don’t believe the measurement field should be a barrier to proceeding with the upgrade.
Thanks for the Reply @Asaf_Gitai - So will the Rest API shutdown on the Feb 1st 2025?
@Asaf_Gitai @Liam-Shopify This is so confusing. One of our app dashboards said that the deadline to migrate from Rest API to GraphQL is Jan 1 on the UPDATE DEADLINE heading. I thought Feb 1 was the deadline.
Hi Roshanbh,
I’ve connected with the relevant product team and they’ve confirmed that the Jan 1st date applies to all deprecation tasks related to 2024-01 except the REST migration items that indicate they are due by 2025-02-01
. If you fix the breaking calls for the non-REST deprecation changes, the update deadline will change to Feb 1, 2025.