FAQ for technical details

This article answers frequently asked questions about the Shopify Connector.

Which Microsoft products work with the Shopify Connector?

The connector is available only for Business Central online. The connector is preinstalled for new environments. Organizations with existing environments can download and install the connector from Marketplace. The organization must have both a Business Central license and a Shopify license to use the connector. To learn more about supported countries/regions, languages, and editions of Business Central, go to Shopify Connector on the Marketplace.

It isn't available for on-premises deployments.

The Shopify connector doesn't work for Embed App, where the client URL has the https://[application name].bc.dynamics.com format.

The Shopify connector doesn't work with other Dynamics 365 applications, like Dynamics 365 Sales or Dynamics 365 Supply Chain Management.

What support is offered for the Shopify Connector?

To learn more, go to Support for the Shopify Connector.

What Shopify API is used

The Shopify Connector primarily uses the Shopify GraphQL Admin API for all integration calls, with the exception of operations related to sold gift cards. For consistency, all interactions with Shopify use the same API version.

Shopify releases a new API version every three months at the beginning of each quarter, and supports each version for 12 months. These updates often include important changes, such as enhanced stability, improved security, and new features. To reduce impact on your environment, adoption of the latest released Shopify API version happens in major releases of Business Central. For example, the Shopify Connector released in April 2025 uses the Admin API version from January 2025, while the October release uses the API version released in July.

Impact on integration

If you're using Business Central with the Shopify Connector released in 2025 release wave 2 (October 2025), your integration relies on API version 2025-07, which is supported until July 1, 2026. To ensure uninterrupted synchronization and data exchange with Shopify, you must upgrade to the latest major version of Business Central (2026 release wave 1) before this end-of-support date. If you don't upgrade, API calls might be blocked, which means you can't synchronize data between Business Central and Shopify.

Why does the connector have so many internal (non-public) codeunits?

The Shopify Connector is built on the Shopify GraphQL Admin API, which Shopify versions every three months and aggressively deprecates fields between versions. The connector pins a specific API version (adopted at each Business Central major release) and must uptake to the next version before support ends. Fall behind, and the integration stops working.

If internal helpers, staging tables, and communication codeunits were all part of a public surface, every upstream API change would land as a breaking change in your extensions on a quarterly cadence. The design trade-off is deliberate: keep internals private so the connector can keep pace with Shopify without breaking the partners building on top.

For the operations partners need most often, we publish stable, public façade codeunits. To learn more, go to Extend the Shopify Connector.

Is the Shopify Connector extensible?

Yes. The connector exposes a substantial extensibility surface while keeping internal communication and staging logic private to absorb Shopify's quarterly API changes without breaking partner extensions. The current surface includes:

• Integration events across dedicated event codeunits covering orders, products, customers, inventory, shipping, and return/refund processing.
• Public façade codeunits for common operations without subscribing to events:
  • Shpfy Orders (codeunit 30409) — MarkAsPaid, CancelOrder
  • Shpfy Metafields (codeunit 30418) — GetMetafieldDefinitions, SyncMetafieldToShopify, SyncMetafieldsToShopify
  • Shpfy Product (codeunit 30234) — AddItemToShopify, GetProductUrl, GetProductsOverview
• Extensible enums with interface implementations for stock calculation, customer mapping, company mapping, return/refund processing, and more.

These façade codeunits are stable and intended to grow. If you need a specific method exposed, you can open a pull request to add it to the relevant façade — that's a small, low-risk change.

The connector is open source and welcomes contributions from partners, including new events, façade methods, bug fixes, and feature work. You can find the source code in the BCApps repository.

To learn more and explore extensibility examples, go to Extend the Shopify Connector.

Building your version of the Shopify Connector

According to Shopify, if you want to build and publish a connector app on Shopify marketplace that has the primary purpose of transferring or sharing merchant data to a third party (Business Central), you must have written consent from Shopify. As part of this process, you must get consent from Microsoft in the "End Recipient Data Acknowledgement Form". We need to ask you to handle the matter with Shopify because Microsoft can't sign third-party agreements.

What to do

Check the Shopify requirements because you still might be able to have an unlisted app.

Alternatively, the Shopify Connector for Business Central constantly gets new features and new customers. If you discover a specific gap, consider submitting a product suggestion or a code contribution to Business Central. For requirements that might not be relevant for a majority of customers, and can't be easily addressed by the current extensibility model, please reach out to the Business Central development team to discuss the use case. We should be able to find a feasible solution.

Related information

Shopify Connector overview
FAQ for the Shopify connector
Troubleshoot the Shopify Connector
Walkthrough: Setting Up and Using Shopify Connector

Start a free trial!

Find free e-learning modules for Business Central here