Frequently asked questions

This is not generic CDN tuning—it keeps CS-Cart as the protagonist in architecture. Initial Cloudflare work for CS-Cart — standard CDN + Cache Rules. We design, implement, and document the changes (not a DIY tool handoff). Secure adds basic WAF. Rollback / Secure are rollback-ready within agreed scope using SafeCache Pro (SafeCache subscription fees are separate, billed in USD via Freemius — product page).

We perform the work. On your Cloudflare account, with agreed access, our team implements the configuration. The goal is an initial architecture owned by specialists within scope—not handing you a DIY product. You may change rules after delivery; responsibility boundaries apply (see below).

• Cloudflare Workers
• Custom development (theme, add-ons, server code)
• Complex infrastructure (multi-origin, unusual topologies)
• Real-time / chat support

No — SafeCache is not mandatory. Safe Setup can deliver the initial Cloudflare configuration on its own. AP SafeCache is a separate product for ongoing change history, monitoring, rollback support, and similar operations. If you want rollback-assisted operations in scope, pick Rollback or Secure (SafeCache Pro assumed within the agreed engagement). Visibility maps to SafeCache Free and does not include rollback-assisted recovery.

Typically we need:

• Domain(s) and whether DNS is on Cloudflare
• CS-Cart storefront URL patterns and admin URL (if non-default)
• Appropriate Cloudflare access (member invite or shared procedure)
• Staging URL if you use one — we prefer validating changes safely

About 2–5 business days after we have complete access and answers, depending on complexity and your approval windows. Because cache-related behavior can be hard to reproduce, staging validation is appreciated when you have it.

We aim for no planned storefront downtime. DNS or SSL changes can sometimes cause brief propagation effects. Steps with unclear blast radius are coordinated with you when possible.

Yes — it is your account. Manual changes after delivery can invalidate the assumptions we documented. We are not responsible for issues caused by those changes (this is a common class where display and checkout can diverge after cache rule edits).

Start with the inquiry form (within plan scope). Rollback / Secure engagements include rollback-oriented recovery assumptions using SafeCache Pro where agreed. Visibility does not include rollback-assisted recovery. No plan includes unlimited post-delivery operations.

For storefront behavior we prefer Cache Rules (modern, easier to reason about). Page Rules are legacy and limited; we only use them when there is a clear technical reason.

Within standard CS-Cart + Cloudflare scope — yes, when they are part of the agreed hostname list. Wildcard or unusual subdomain farms may need a custom quote.

Yes in principle. Contact us with your current plan and what you need; we will quote the difference or a follow-on engagement.

Use the form below for questions and consultation (opens in a new window). Plan purchases use the per-plan buttons in the pricing section.

Open consultation form

Typical response after we receive your inquiry: 1–2 business days. Scope is limited to what the plan covers. This is not an on-call or always-on chat service.

We are not responsible for issues caused by manual changes after delivery in Cloudflare, CS-Cart, or third-party systems — unless you have a separate support agreement. If you want ongoing guardrails beyond the initial build, consider AP SafeCache or a separate maintenance engagement.