Connector Versioning Policy

Modified on Wed, 13 May at 4:51 PM


How Shopify API versioning works


Shopify maintains a defined API versioning policy, and that policy directly affects the lifecycle of the Sales Layer Shopify connector.


Understanding how Shopify manages API versions helps explain why Sales Layer releases new connector versions and why migrations may be required over time.


Official documentation: Shopify API Versioning Policy


Key points of Shopify’s versioning policy


  • Shopify releases a new API version every quarter: January, April, July, and October.
  • Each version is supported for 12 months from its release date.
  • Shopify guarantees backward compatibility within a version during that 12-month period.
  • Once the support window ends, Shopify disables that version and integrations using it stop working.


Sales Layer versioning policy


Sales Layer maintains its own versioning system for the Shopify connector, aligned with the API versions supported by Shopify.


This approach is intended to maintain long-term compatibility with Shopify services, make migration easier, and improve visibility around connector changes.


Commitment to active versions


Sales Layer aims to keep at least two active and stable connector versions available, each compatible with one of the Shopify API versions supported at the same time.


This policy helps preserve service continuity and reduces the risk associated with older versions reaching end of support.


The goal is to keep a difference of at least 3 months and at most 9 months between the APIs supported by active connector versions.


The connector currently shows the compatible Shopify API version to the client.


Every migration is communicated in advance and includes documentation, step-by-step instructions, and technical support when needed.


Typical changes in a new connector version


Each new connector version may introduce changes in fields, behavior, or architecture. Common examples include:

  • Changes in field names or types, for example inventory_management replaced by tracked
  • Fields deprecated or no longer supported in newer API versions
  • New permissions required in the client’s custom Shopify app
  • Adjustments in synchronization logic, such as a GraphQL transition or changes in visibility rules


These changes may require remapping fields, updating Shopify permissions, or manually validating existing configurations. For that reason, all migrations are handled in a controlled and assisted way.


The current connector version is shown in the connector’s Activity Register tab.


For more details, see FAQs about Versioning.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article