Speed and security
Cloudflare for ecommerce stores
We use Cloudflare to make headless and custom ecommerce storefronts faster and safer: edge caching, firewall and bot rules, redirects and routing by country, set up carefully around cart, checkout and account pages.
Faster pagesPages served from the edge, close to shoppers.
SaferFirewall and bot rules that stop abuse, not customers.
CarefulCart, checkout and accounts never cached.
When Cloudflare helps
Built for headless and custom storefronts
A standard Shopify theme is already served through Shopify's own global network, and putting your own Cloudflare proxy in front of it is not supported. Cloudflare earns its place when you run your own front end: a headless storefront on Next.js or BigCommerce Catalyst, a custom app, a content site or an API that sits beside your store.
We used Cloudflare edge caching on L'azurde's headless BigCommerce store, where pages are cached close to shoppers and cart and account pages are safely bypassed.
- Edge caching. Pages cached close to shoppers, with clear rules for when they refresh
- Safe bypass. Cart, checkout, account and logged-in pages never cached
- Firewall. Rules for admin paths, APIs and known bad traffic
- Routing. Redirects and country routing handled at the edge
What we set up
Six things Cloudflare does for a store
Caching
Cache rules per page type, with purges tied to product and content updates so shoppers never see stale prices.
Firewall
Rules that block attacks on admin paths, forms and APIs without blocking real customers.
Bot protection
Bot rules that slow down scrapers, card testers and fake sign-ups.
Redirects
Large redirect maps handled at the edge after a migration, so old URLs keep their rankings.
Geo routing
Shoppers sent to the right regional store or language based on where they are.
Workers
Small pieces of code at the edge for tasks like A/B tests, headers and personalisation.
How we work
Review, build, support
-
Review
We look at how the tool is set up today, what data reaches it and what is missing or wrong.
-
Plan
A short written plan: what we will connect, change or remove, and how we will test it.
-
Build
Official apps and APIs first, custom code only where they cannot do the job.
-
Test
Real test orders and journeys on a staging store before anything goes live.
-
Support
We monitor it after launch and stay on hand for changes as your store grows.
Done carefully
Caching that never shows the wrong basket
The risk with any cache on a store is showing one shopper's data to another, or an old price after a sale ends. We write rules by page type, test logged-in and logged-out journeys, and tie purges to the events that change content.
- Logged-in pages. Never cached
- Prices and stock. Purged when products change
- Testing. Real journeys checked before and after release
FAQ
Common questions
Can I put Cloudflare in front of my Shopify store?
Not on a standard Shopify theme. Shopify already serves stores through its own network and does not support proxying them through your own Cloudflare account. You can still use Cloudflare for DNS, and for any headless front end, app or site you run alongside Shopify.
Is Cloudflare useful on BigCommerce?
Yes, especially for headless BigCommerce storefronts built on Catalyst or Next.js, where you control hosting and caching yourself.
Will caching break my cart or checkout?
Not when it is set up properly. Cart, checkout and account pages are always excluded, and we test real journeys before anything goes live.
Can you fix a Cloudflare setup that is causing problems?
Yes. We review your rules, find what is caching or blocking the wrong things, and fix it without taking the site offline.
Start a project
Tell us about your store
We reply within one working day with next steps.