SCDN for commerce: separate catalog, cart and order traffic
Separate public assets from personalized transactions and verify caching with complete purchase flows.
Contents of this article
Separate traffic paths before a promotion
Versioned product images, campaign assets and scripts suit distribution; carts, eligibility, stock confirmation and orders depend on live state. Map hostnames and paths before onboarding rather than applying a long cache lifetime to the whole store.
Verify personalized responses separately
Apply appropriate cache controls to private responses and check that edge rules honor them. Test the same URL with separate accounts, regions and currencies to verify that carts and offers remain isolated.
Focus controls on expensive operations
Observe sign-in, search, coupon claims and checkout separately before tuning controls. WAF is included on SCDN Standard and higher plans; authorization, stock checks and idempotent order handling remain application responsibilities.
Validate an entire transaction
Test updates, cart changes, checkout, payment callbacks and refund lookups. Correlate edge, application and payment records by time and request ID. Cache improvements do not replace database or transaction-service capacity.