Migration 1.10 (current version)

Introduction

Since July 2025, a new version has been released, 1.10, which is fully compatible with Shopify API 2025-07. This change marks a major architectural shift with the full adoption of GraphQL API, replacing the previous REST-based model. It offers improved performance, simplified calls, and better alignment with Shopify’s platform evolution.
.

Note: All the new connectors will be created in this version.

Summary:

Permissions in the Shopify store

Functionality	Sales Layer item types and fields involved	Shopify permission
Required for any synchronization		read_inventory read_locales read_locations read_products read_product_listings read_publications read_translations write_products write_publications write_translations
Metafields	Any category/product/variant 's metafield (defined or not) created by the user. metafields_global_title_tag and metafields_global_description_tag will no longer need these permissions.	read_metaobject_definitions
Markets	In product: markets presentment_prices In variant: presentment_prices	read_markets write_markets
Media files	Product: media_video media_video_alt media_order any file/video type metafield	read_files write_files
Inventory / inventory_quantity	Products: cost_per_item country_code_of_origin province_code_of_origin requires_shipping tracked inventory_quantity weight_unit weight Variants: cost_per_item country_code_of_origin requires_shipping tracked inventory_quantity weight_unit weight province_code_of_origin harmonized_system_code	write_inventory read_fulfillments write_fulfillments

Price field format update

The format of price fields has been updated. Prices can now be sent with 0, 1, or 2 decimal places. The connector now formats prices correctly to up to two decimal places, with no manual adjustments required.

Affected fields:

In products: price, compare_at_price
In variants: price, compare_at_price

Sales Channel

The Shopify connector supports controlling product and collection visibility across Sales Channels using the published_scopes field in Sales Layer.

Behavior introduced in v1.9.3 (last version)	New behavior (v1.10)
The connector allowed publishing products to specific Shopify Sales Channels using the published_scopes field. This was implemented using GraphQL logic.	The same logic is now extended to collections, which can now be published or unpublished in specific Sales Channels in the same way as products

Image and media ordering logic

The media_order field: allows ordering media items in Shopify such as: images, videos, 3D files, etc. Find more info about the media_order logic here.

Media synchronization and external systems

Version 1.10 introduces clearer and stricter behavior regarding how product and variant media are handled — especially when multiple systems attempt to manage media simultaneously.

Affected fields:

Collections: no action is needed
Products and variants:

Scenarios	Action needed	Expected behavior
If your image data source is ERP, DAM, Shopify apps	The following media fields from Sales Layer need to be disabled. Disable or remove fields: In products: images, media_video, media_external In variants: images	The connector does not manage any product/variant media. Existing media in Shopify is preserved. Media from an external system remains untouched.
If your image data source is Sales Layer (no ERP, DAM, Shopify apps)	Map the appropriate media fields in the connector.	Sales Layer will send all mapped product and media data to Shopify, and manage media only via mapped fields.
Only media_external is enabled	Disable or remove fields: In products: images In variants: media_video Enable: media_external	Only media from media_external is sent to Shopify. Product will display only the external media managed via this field. Any previously linked images or media_video elements will be unlinked and removed. Attention: This overrides media created by other systems unless explicitly preserved.

Note: In this version, image metafields are now supported, but it won’t link to a regular Shopify product image. They’ll exist as separate entities.

Please find info about supported metafields in this article.