These FAQs have been compiled from webinar participants and solutions provided by Celigo developers while migrating from deprecated Shopify Products REST APIs to the new GraphQL API endpoints. Submit your own questions in the Comments section of this article.
Q1. I no longer see an “Advanced settings” option in the import field mappings. Is it still available?
A1. No, you must replicate any mapping that used the Advanced settings with a handlebar or leverage NetSuite saved search formulas.
A.2 Do not delete any Standard (mandatory) mappings, as they are essential for the flow to function correctly. We strongly recommend checking with Celigo support first before removing any mappings. For more details, refer to Field Mappings in GraphQL-based Product Flows.
A3. Yes. We have been sending out email to all affected customers. You will continue to get notifications until the end-of-life date arrives for these API endpoints. Reminders will become more frequent if we detect that no action has been taken.
A4. In addition to Shopify communication, Celigo published an article six months in advance, announcing the plan to deprecate endpoints, which was also referenced in July 2024 release notes.
Starting at that time, Shopify exports and imports were also marked as “deprecated.”
A5. Celigo support will work with you and the Product team to resolve the issue.
A6. You can sync weight from NetSuite to Shopify using GraphQL-based product flows. For details, refer to Syncing Weight from NetSuite to Shopify using GraphQL-based product flows.
A7. Shopify introduced the ability to include inventoryItem fields in the productSet mutation (which our product flow in IA relies on) only on January 15th. Since our solution was developed before this update, there was no way to map this field, so we implemented an internal workaround. The Shopify Do Not Track Inventory logic is handled internally within the hook, so no specific mapping has been created for it.
A8. The Fulfillment Service field was used in the old REST flows but has no impact on GraphQL flows. It is not available in the productSet mutation. Instead, fulfillment details are inferred from the product’s location and managed directly by Shopify.
A9. When syncing metafields from NetSuite to Shopify, if a metafield in NetSuite has a null value, the expected behavior is for the flow to delete the corresponding metafield in Shopify. The issue can be addressed by default if the metafields are configured in the integration app via Settings > Product > Specify your Shopify variant metafield components.
In case, you are using the mappings and facing this issue, the regular format in GraphQL mapping does not resolve it, but a specific configuration is required. For details, see Map metafields at product level using the saved search.A10. We’ve identified a behavioral difference between Shopify’s GraphQL and REST APIs in how they handle variant position values:
- The REST API allows variant positions to start from any number.
- The GraphQL API, however, strictly requires variant positions to start from 1.
This is a known Shopify platform limitation, and Shopify has acknowledged the discrepancy. They are actively investigating the issue.
As of now, there is no confirmed timeline for a resolution. We will keep you updated as soon as we receive any further information from Shopify.