Cloudflare + Shopify integration

What Cloudflare is

Cloudflare provides DNS, security, caching and edge hosting. With Shopify it usually manages the store's domain DNS, and sometimes hosts custom apps or sites beside the store.

How we would approach Cloudflare with Shopify

Shopify already runs its own CDN and security in front of your store, so the usual answer is Cloudflare for DNS only, with the proxy off for the store's records. Proxying the store causes the errors Shopify warns about. If you really need Cloudflare rules in front of Shopify, Cloudflare documents an Orange-to-Orange setup; we'd confirm it with Shopify first. Separately, Cloudflare is a good home for custom apps and webhook handlers.

What the work involves

• DNS records for the store set to DNS only
• Domain and email records checked after the change
• A decision on Orange-to-Orange, confirmed with Shopify, if rules are needed
• Custom apps or sites hosted on Cloudflare where useful

Ways to connect Cloudflare and Shopify

• Built in

  DNS only

  Cloudflare manages DNS; Shopify serves the store. The setup Shopify expects.

• Built in

  Orange-to-Orange (O2O)

  Cloudflare's documented way to proxy your zone in front of Shopify's. Workers and Snippets don't run on the /checkout path. Confirm with Shopify support before relying on it.

• Custom build

  Workers and Pages

  Cloudflare Workers or Pages for custom apps, webhook handlers or content sites beside the store.

Where these projects go wrong

• The store's records left proxied (orange cloud), triggering Shopify's proxy warning and connection problems.
• Caching rules from another site applied to the store.
• Email records changed while moving DNS, breaking mail.

Questions

Shopify says our domain has a proxy. What do we do?

In Cloudflare, switch the store's A and CNAME records from proxied to DNS only. It can take some time to clear.

Do we need Cloudflare for speed?

Not for the store. Shopify serves it through its own network. Speed problems are usually in the theme and apps.

Before we scope the work

• Which data or customer journey needs to connect, and which system owns it?
• What access, plan features or API permissions are available?
• Does an existing connector cover the requirement, including failures and updates?
• Who will maintain the connection, and how will you know it is working?

Send your current setup and one real example of the flow you need. We'll tell you whether it can be done and what it would take.