E-Commerce Nov 19, 2026

Peak Traffic Readiness: Test the Store Journeys That Fail First

Peak Traffic Readiness: Test the Store Journeys That Fail First

Time to read: 11 minutes

Content

  1. The peak readiness sheet
  2. Where peak failures start: dependencies, not pages
  3. Build a load model from your own order history and campaign plan
  4. Load, spike and soak tests: what each one proves
  5. Integrations under pressure: payment, ERP/OMS, search and apps with rate limits
  6. SaaS or self-hosted: what you may and may not load test
  7. Fallbacks, waiting rooms and graceful degradation
  8. Change freeze, monitoring and the go/no-go call
  9. Where Dinarys has met this problem
  10. Exceptions
  11. Check your readiness
  12. FAQ
  13. Your next step
Bookmark

Most peak-day failures start in a dependency, not on the homepage. Readiness is proven by a load model, test results per journey, and a known limit and fallback for every system those journeys call.

When a sale slows a store, the cause usually sits behind the page: a search service at its quota, a stock or price lookup waiting on the ERP, a slow payment authorization, a backed-up order export, or an app throttled by a platform API.

You know the store and the systems behind it will hold when, before the campaign starts, you have:

  1. a load model built from your own order history and campaign plan;
  2. load, spike and soak results for the journeys that call those dependencies (search and filter, add to cart, checkout, payment and order export), run on a production-like environment against agreed-upon thresholds;
  3. the limit of each dependency and what happens beyond it;
  4. a fallback for each dependency, and one owner of the go/no-go call.

On SaaS platforms, you test your own apps, APIs, headless frontend and integrations within the vendor's rules, not the vendor's platform. This guide treats ecommerce load testing as that pre-peak gate; always-on speed and uptime checks belong to ecommerce monitoring.

The peak readiness sheet

Fill in one sheet per event, as the input to the go/no-go meeting.

PartWhat to recordWho fills it in
1. Load modelPeak orders per hour, sessions, cart-to-order ratio and campaign-start spike, from your own history and campaign planEcommerce analyst with marketing
2. Journey and dependency resultsFor each journey: test type (load, spike, soak), target, observed p95 latency and error rate, limit found, ownerEngineering lead
3. Dependency limits registerRate limits of the platform API, payment provider, ERP gateway, search, tax and shipping services, and what happens when each is exceededIntegration owner, with each system owner
4. FallbacksQueued order export, cached price and stock reads with a final check at order placement, heavy recommendations switched off, a waiting roomEngineering lead and head of ecommerce
5. Event controlsChange-freeze window, on-call and rollback contacts, go/no-go ownerHead of ecommerce or COO

Worked example (fictional, for illustration only). A toy retailer on Magento 2 expects four times its normal peak hour during a December promotion.

JourneyMain dependencyTestResultLimit foundOwner
Search and filterSearch engineLoad at 4×p95 0.9 s, errors 0.1%None found at 4×Ecommerce lead
Add to cartStock check through the ERP gatewaySpike to 3×Gateway queue grewGateway capped at 20 requests per secondERP owner
CheckoutStock check per cart line; tax and shipping appsSpike to 3×p95 rose from 1.8 s to 9 s; errors above 1%Same gateway capERP owner
PaymentPayment provider, mockedLoad at 4×, latency sampled from live callsWithin thresholdsProvider's documented limits recordedPayments owner
Order exportERP order API, same gatewaySpike to 3×Order placement waited for the exportSame gateway capIntegration owner
Checkout, retestCached stock, queued exportSpike to 4×Within thresholdsNone at 4×ERP owner
Order export, soakExport queue and ERP order APISoak at 4× for 4 hours, after the fixQueue depth stable; no duplicate ERP ordersNone foundIntegration owner
Peak traffic dependency map Five customer journeys, each with an arrow to the dependency it loads. Search goes to the search engine, limited by a plan query quota, with cached top queries as fallback. Cart goes to the stock and price check, limited by an ERP gateway at 20 requests per second, with a 60-second cache and a final check as fallback; it is also called at checkout and is marked first to fail. Checkout goes to tax and shipping apps, limited by app API rate limits, with flat rates and paused apps as fallback. Payment goes to the payment provider, limited by the provider's rate limit, with a backup provider as fallback. Order export goes to the ERP or OMS order API, limited by the same 20 requests-per-second gateway, with an idempotent queue as fallback. Journey Dependency, limit, fallback Search Search engine Limit: plan query quota Fallback: cached top queries Cart Stock & price First to fail Limit: ERP gateway, 20 req/s Fallback: 60 s cache, final check Also called at checkout Checkout Tax & shipping apps Limit: app API rate limits Fallback: flat rates, apps paused Payment Payment provider Limit: provider rate limit Fallback: backup provider Order export ERP / OMS order API Limit: same 20 req/s gateway Fallback: idempotent queue
Fictional example: the five journeys tested before a December promotion, with each dependency's limit and fallback. The ERP-gated stock and price check failed first; checkout calls it too.

Where peak failures start: dependencies, not pages

Product and category pages are usually cached, so extra visitors cost little there. Filtered search, cart updates, checkout, payment and order creation are personal or stateful and mostly uncacheable, and each calls another system with its own limit.

AWS's Well-Architected guidance warns: "A shared database or downstream dependency may saturate before the component under test does." AWS also warns that "uncontrolled retries turn a small impairment into a large one."

Usual first-to-fail candidates:

Build a load model from your own order history and campaign plan

Use your own history, not industry figures. From the last comparable event, take:

Multiply by the campaign factor and agree on it with marketing in writing. Two of AWS's load-testing anti-patterns apply here: test traffic that "uses a narrow set of requests rather than a representative mix of real ones", and tests that "stop at a small margin above expected load and never find the breaking point."

Build the load model from your own historyLoad model inputs from the last comparable event: peak orders per hour, sessions and journey mix, cart-to-order ratio and the campaign-start spike, then multiplied by the campaign factor agreed with marketing.Build the load modelfrom your own historyFrom the last comparable eventPeak orders per hourFrom the order database rather thananalytics aloneSessions and journey mixThe share that search, add to cartand reach checkoutCart-to-order ratioCarts load stock and price serviceseven when they never convertCampaign-start spikeTraffic after an 08:00 email doesnot spread evenly across the hour

The test environment also needs production-like data volume, since catalog size and price rules change query cost. On Adobe Commerce and Magento Open Source, Adobe's data generator (bin/magento setup:perf:generate-fixtures) builds test catalogs from small to extra-large profiles.

Load, spike and soak tests: what each one proves

Grafana's k6 documentation defines the test types:

Testk6 definitionWhat it proves before a peak
Average load"assess how your system performs under expected normal conditions"Your baseline p95 and error rate
Spike"validate the behavior and survival of your system in cases of sudden, short, and massive increases in activity"Whether the campaign-start surge breaks a dependency
Soak"assess the reliability and performance of your system over extended periods"Whether queues or connection pools grow over a long sale day
Breakpoint"gradually increase load to identify the capacity limits of the system"The first limit, and the metric that warned of it

Start with a smoke test, keep load shapes simple and run more than one type: in k6's words, "no single test can uncover all issues."

Integrations under pressure: payment, ERP/OMS, search and apps with rate limits

Take each limit from its owner's documentation or configuration, not from memory.

SaaS or self-hosted: what you may and may not load test

For Adobe Commerce on cloud infrastructure, Adobe asks you to "enter a ticket with support advising the environments you are testing, what tools you are using, and the time frame" before testing Staging or Production.

On Shopify, the platform scales the storefront. Its Terms of Service say merchants agree not to access the Services "using any robot, spider, scraper, or other automated means." Its bot glossary describes authorized load tests as those "conducted with prior permission", and its go-live guide for Oxygen-hosted Hydrogen storefronts (now marked legacy, versions 2026-04 and earlier) warns that its "anti-bot System might recognize your load test system as bot traffic and throttle it", asking you to coordinate a scheduled test with your Merchant Success Manager or Shopify Support "three to five weeks in advance of your go live date."

So on SaaS, test what you own: custom apps, middleware, the headless frontend and ERP connectors, within the vendor's rate limits.

Fallbacks, waiting rooms and graceful degradation

AWS describes the goal: "Graceful degradation converts hard dependencies into soft dependencies, so a component continues to deliver its core function even when a dependency is unhealthy." For a store, that means:

Cap retries, with backoff and jitter, at one layer. Exercise each fallback during the test run: as Google's SRE book warns, "the code path you never use is the code path that (often) doesn't work."

Graceful degradation for a storeGraceful degradation for a store: cached stock and price reads with a final check at order placement, a queued order export with idempotent retries, heavy features behind a switch, and a waiting room.Graceful degradationfor a storeExercise each one during the test runStock and price readsA short cache, with a final check orreservation at order placementOrder exportA queue with idempotent retries, soplacement does not wait for the ERPHeavy features behind aswitchRecommendations, personalization andlive widgetsWaiting roomAdmits shoppers at a rate theslowest dependency can take

Change freeze, monitoring and the go/no-go call

After the final passing test, freeze code and configuration until the event ends, except approved fixes: the build you tested is the build that runs. Agree on the release strategy and rollback for those fixes in advance.

During the event, watch the signals the tests used: checkout p95, error rate per journey, gateway request rate and order-queue depth. Check that alerts reach each on-call owner. If on-call and rollback cover is thin, plan it into your DevOps support and maintenance arrangement well before the freeze.

The go/no-go meeting reads the sheet and records one decision: go; go with named fallbacks on; change the campaign, for example by staggering email sends; or no-go. If the limit found is your own infrastructure, see our guide to cloud scalability.

Where Dinarys has met this problem

Two Dinarys case pages start from peak load:

Neither is a load-test result; both projects included integration with the client's existing systems.

Exceptions

Check your readiness

Before your next event:

  1. Fill in part 1 of the sheet from your own order history and campaign plan.
  2. Name each dependency's limit, its source and its fallback.
  3. Run one spike test at the campaign multiple on a production-like environment.
  4. Record the go/no-go decision, its owner and the evidence behind it.

If any dependency has no known limit, or any fallback has never run, the sheet is unfinished.

A passing test shows that the tested build handled the tested load on the tested environment. It is not a promise about the event day; that is why fallbacks and a go/no-go owner are on the sheet.

FAQ

How far ahead of a peak should we load test?

Early enough to fix what fails and retest before the change freeze, plus any vendor's lead time. Shopify's legacy go-live guide for Oxygen-hosted Hydrogen storefronts asks for three to five weeks; confirm the current lead time with Shopify Support or your Merchant Success Manager.

Can we load test in production?

Yes, as a planned game day: AWS describes running it "during a period of low customer usage" with "the responsible people present to interpret results". Do it only with every dependency owner's agreement and with synthetic orders isolated.

What p95 and error thresholds should we use?

There is no universal figure: take your baseline from an average-load test and agree on the tolerance with the head of ecommerce, in writing, before testing.

Your next step

Fill in the load model and the dependency limits register for your next event; the gaps show where to start testing. If the results point to work your team cannot finish before the freeze, talk to Dinarys about ecommerce performance optimization.

Let professionals meet your challenge

Our certified specialists will find the most optimal solution for your business.

Please enter valid name
Please enter valid company
Please enter a valid phone
Please enter valid E-mail
Message is too short

    Your message has been successfully sent. We will be in touch shortly! Success icon