Navigating Shopify's New Product Model: A Developer's Guide

Shopify recently rolled out a product model and upgraded product-related elements within the GraphQL Admin API. Consequently, specific product-related components in GraphQL and REST Admin APIs, including some REST endpoints, are being phased out. These modifications aim to streamline the product development process by enabling functional teams to handle product variations and choices efficiently.

Developers creating apps on GraphQL or REST product APIs must transition to the new GraphQL product APIs before February 1, 2025. The migration deadline for custom apps developed on existing GraphQL product APIs is April 1, 2025. Custom apps relying on REST will also need to switch over if they require support for more than 100 variants. However, custom apps that do not require more than 100 variants can continue using outdated REST product APIs.

Key Takeaways

Shopify has introduced a new product model and enhanced product-related components in the GraphQL Admin API.
Specific product-related components in the GraphQL and REST Admin APIs are being deprecated.
Developers building public apps on existing GraphQL or REST product APIs must migrate to the new GraphQL product APIs by February 1, 2025, while custom apps built on existing GraphQL product APIs must migrate by April 1, 2025. Custom apps built on REST must also relocate to support more than 100 variants.

Different Mutations for Different Workflows

Shopify has created changes specifically designed for tasks frequently seen in Shopify apps and scenarios. This is necessary because there are approaches to interacting with the product model, making it essential to pinpoint the workflow that aligns best with your app or scenario and utilize the relevant categories in the GraphQL Admin API.

When the app's source of truth for merchandising data is something other than Shopify, a productSet mutation is used to push information about a product from an external source into Shopify. Examples of apps and use cases for this workflow include those that import product information from an external source into Shopify, such as Enterprise Resource Planning (ERP) systems and Worksheets.

On the other hand, when the app's source of truth for merchandising data is Shopify, and specific product data needs to be edited, sets of new and updated mutations are used to enable specific and incremental changes to products, variants, and options. Examples of apps and use cases for this workflow are those that update product model information.

The REST Admin API /products and /variants endpoints are being deprecated, so to keep working with products, it is necessary to migrate to the GraphQL Admin API. The following resources can be reviewed to start using the new product model:

Learn about the new product model and components here.
Read about the extensive product and platform transformation here.
Discover how to build a great product change management strategy here.

In conclusion, it is essential to identify the workflow that best matches your app or use case and use the corresponding types in the GraphQL Admin API. This will ensure that the new product model is used effectively and efficiently.

Q: What is product development?

A: Product development is the process of creating a new product or improving an existing one through various stages, such as concept development, design, testing, and launch.

Q: What are the stages of new product development?

A: The stages of new product development typically include idea generation, concept development and testing, business analysis, product development, test marketing, and commercialization.

Q: How important is product design in the development process?

A: Product design is crucial in the development process as it determines how the product will look, feel, and function, influencing its market success and customer satisfaction.

Q: What role does a product manager play in the product development?

A: A product manager oversees the entire product development process, from concept to launch, including collaborating with cross-functional teams, prioritizing features, and ensuring the product meets customer needs.

Q: Why is customer feedback important in product development?

A: Customer feedback is vital in product development as it helps teams understand customer preferences, gather insights for product improvement, and validate whether the product meets market demands.

Q: What are some best practices for successful product development?

A: Some best practices for successful product development include conducting thorough market research, involving stakeholders early in the process, iterating based on customer feedback, and having a clear product roadmap.

Q: How can a development team ensure their product meets market needs?

A: A development team can ensure their product meets market needs by defining a target market, conducting market research, validating product concepts with customers, and improving the product based on feedback.

Features Spotlight