BigCommerce
Cloudflare partners with BigCommerce to provide BigCommerce customers’ websites with Cloudflare’s performance and security benefits.
If you use BigCommerce and also have a Cloudflare plan, you can use your own Cloudflare zone to proxy web traffic to your zone first, then BigCommerce‘s (the SaaS Provider) zone second. This configuration option is called Orange-to-Orange (O2O).
O2O’s benefits include applying your own Cloudflare zone’s services and settings - such as WAF, Bot Management, Waiting Room, and more - on the traffic destined for your BigCommerce environment.
For more details about how O2O is different than other Cloudflare setups, refer to How O2O works.
BigCommerce customers can enable O2O on any Cloudflare zone plan.
To enable O2O on your account, create a CNAME DNS record.
| Type | Name | Target | Proxy status |
|---|---|---|---|
CNAME | <YOUR_HOSTNAME> | shops.mybigcommerce.com | Proxied |
When a hostname within your Cloudflare zone has O2O enabled, you assume additional responsibility for the traffic on that hostname because you can now configure various Cloudflare products to affect that traffic. Some of the Cloudflare products compatible with O2O are:
For a full list of compatible products and potential limitations, refer to Product compatibility.
If you are a BigCommerce customer and have set up your own Cloudflare zone with O2O enabled on specific hostnames, contact your Cloudflare Account Team or Cloudflare Support for help resolving issues in your own zone.
Cloudflare will turn to BigCommerce if there are technical issues that Cloudflare cannot resolve.