Native Shopify Edge (Baseline)
Shopify manages a global Cloudflare-backed edge by default. Caching, DDoS mitigation, and routing are handled by the platform. Most merchants benefit from fast delivery without owning the network layer.
What O2O Adds
O2O serializes two Cloudflare zones. The merchant can enforce custom firewall rules, edge redirects, or compliance policies before Shopify receives the request. The tradeoff is that the merchant now owns edge behavior and its failure modes.
When O2O Is Justified
- Regulatory or data sovereignty requirements require geo enforcement at the edge.
- Security posture demands custom bot rules, IP allowlists, or zero-trust policies.
- Single-domain routing needs to split traffic across multiple backends.
Constraints That Matter
- Do not proxy Shopify checkout or the hosted theme through custom Workers.
- Respect Shopify cache headers; double caching creates stale content risk.
- Preserve headers required for fraud analysis, analytics, and app proxies.
- Expect longer incident resolution when ownership is split across vendors.
Failure Modes and Costs
- Support fragmentation: 403/502 errors often require joint debugging across teams.
- Double-cache drift: stale product pages can persist even when inventory changes.
- Header stripping: aggressive security rules can break fraud signals or app proxies.
- Operational overhead: more rules, more tuning, more on-call ownership.
Decision Checklist
- Is there a hard business requirement that Shopify's native edge cannot meet?
- Is the organization staffed to own Cloudflare rules and incident response?
- Can routing, compliance, or security be achieved via Shopify-native tooling?
- How will we validate cache behavior and header integrity at scale?
Key Takeaway
O2O is a specialized edge configuration. Use it when compliance or routing requirements are strict enough to justify the added operational cost.
External Documentation
These links can help further inform the decision making process and may also be more up to date: