---
title: How to keep your storefront running through Black Friday
description: Learn how to tune alerts, bot rules, and spend limits. Rehearse rollback so your team can recover quickly from checkout or order issues on Black Friday.
url: "https://vercel.com/kb/guide/black-friday-reliability"
published: 2026-11-17
last_updated: 2026-11-17
authors: Neha Julka, Anshuman Bhardwaj
install_vercel_plugin: npx plugins add vercel/vercel-plugin
search_with_vercel_cli: npx vercel@latest kb search "<query>"
read_with_vercel_cli: "npx vercel@latest kb inspect black-friday-reliability"
---

Preparing for Black Friday means more than handling a traffic spike. A firewall rule can block a shopping agent, a spend limit can pause production, and missing permissions can delay a rollback. Check critical settings and make sure your team has the access it needs to respond quickly.

This guide builds on [How to prepare your storefront for Black Friday traffic](https://vercel.com/kb/guide/black-friday-preparation) with operational checks to help prevent avoidable disruptions and keep your storefront running throughout the event.

## Start with ownership

Decide who gets paged first, who can approve changes, and who owns each critical part of the customer journey: storefront, checkout, payments, inventory, search, and fulfillment. Make sure the people on call have the [access roles](https://vercel.com/docs/rbac/access-roles) required for their actions, such as applying firewall rules, changing spend settings, and rolling back, before peak. The on-call team should know how to reach your Vercel account team and the [Support Center](https://vercel.com/docs/support-center).

## Configure monitoring and alerts

Use your [readiness criteria](https://vercel.com/kb/guide/black-friday-preparation#set-performance-and-checkout-targets) to set thresholds for errors, latency, and function duration. Define acceptable rates for checkout completion and cart abandonment. Set thresholds for checkout’s external APIs, too.

Agree which signals call for investigation, escalation, or rollback. A checkout that returns `200` but stops converting is still an incident. Run synthetic checkout checks and tune thresholds for peak traffic.

### Give alerts time to establish a baseline

[Vercel Alerts](https://vercel.com/docs/alerts) detects error and usage anomalies and sends notifications via Slack, email, incident.io, or a webhook. Turn [Observability Plus](https://vercel.com/docs/observability/observability-plus) on at least a week before peak: error anomaly alerts start after 24 hours, and usage anomaly alerts after 3 days, with a full 7-day comparison after a week.

![Usage anomaly alert showing Fast Data Transfer rising 5x, from 20 GB to 101 GB, compared with the previous 24-hour average](https://images.ctfassets.net/hjgychtc108g/2xESfSSZDZZaEAW8tohs2W/49229e44ac365c1b90619bc9b4a69dea/image.png)

Vercel Agent, in public beta, can investigate Medium and High anomaly alerts. Turn on **Investigate anomalies automatically** in **Agent** settings; 10 investigations per billing cycle are included, and more require Agent billing.

![Vercel Agent investigation of an anomaly alert, finding that api.acmepay.com was unavailable and all 893 requests to /api/checkout failed](https://images.ctfassets.net/hjgychtc108g/7b0qt5bJIfLhfJ9OAOZdsd/5b46e9e043dc58a084d5b40017c40c12/image.png)

Add [custom monitors](https://vercel.com/docs/alerts/configure-alerts#configure-custom-monitors), such as a per-route error-rate ratio that catches a failing checkout route. Excluding non-critical projects from Observability Plus saves cost but stops their alerts, and turning it off and on for the team restarts activation. Send logs and traces to on-call tools with [Drains](https://vercel.com/docs/drains) (Pro and Enterprise; Speed Insights drains need Speed Insights Plus), and test every destination in advance.

## Set policies for bots and automated traffic

Decide which automated traffic to support before you tighten protections:

| Traffic type                       | Preparation                                                   |
| ---------------------------------- | ------------------------------------------------------------- |
| Search and discovery crawlers      | Keep your catalog open to the ones you want.                  |
| Training crawlers                  | Decide separately from search and shopper visits.             |
| AI assistants acting for a shopper | Verify identity where possible and test product page access.  |
| Checkout agents and partners       | Define authentication, permissions, rate limits, and retries. |
| Scrapers and abusive automation    | Block credential stuffing, stock hoarding, and fake browsers. |

User agents can be faked, so Vercel’s [verified bot directory](https://vercel.com/docs/bot-management#verified-bots) checks IP ranges, reverse DNS, and [Web Bot Auth](https://vercel.com/changelog/vercels-bot-verification-now-supports-web-bot-auth) signatures. Bot Protection lets verified bots through unless other rules restrict them. Give agents and partners that call your APIs their own credentials, rate limits, and backoff, so their requests don’t look like anonymous browser visits.

### Test protections before enforcing them

Run new rules in log mode for a week or two before peak and check for false positives; a flash sale can look like an attack. In log mode, run the [policy tests](https://vercel.com/kb/guide/black-friday-preparation#test-capacity-and-firewall-policy-separately) without bypasses and confirm the rule doesn’t match them; then rerun them immediately after enforcement.

| **Control**                                                                                   | **Purpose**                                                                                               |
| --------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
| [Bot Protection managed ruleset](https://vercel.com/docs/bot-management)                      | Challenge clients that claim to be browsers but don’t behave like real browsers.                          |
| [AI bots managed ruleset](https://vercel.com/docs/bot-management#ai-bots-managed-ruleset)     | Log or deny known AI bots, including training crawlers, search bots, and user-directed fetches.           |
| [BotID](https://vercel.com/docs/botid)                                                        | Detect abuse on browser routes such as login, signup, and checkout.                                       |
| [WAF rate limiting](https://vercel.com/docs/vercel-firewall/vercel-waf/rate-limiting)         | Limit requests to sensitive endpoints, starting with the Log action.                                      |
| [System Bypass rules](https://vercel.com/docs/vercel-firewall/vercel-waf/system-bypass-rules) | Exempt trusted IPs from system mitigations, such as payment providers, PCI scanners, and trusted proxies. |

> **Warning:**
>
> The Bot Protection managed ruleset does not work when a [reverse proxy such as Cloudflare](https://vercel.com/kb/guide/can-i-use-a-proxy-on-top-of-my-vercel-deployment) sits in front of Vercel.

Both managed rulesets are available on all plans and off by default. Test BotID with every authorized automated purchase flow, and explicitly allow the verified agents you support. System Bypass rules need Pro or Enterprise, and [custom rule](https://vercel.com/docs/vercel-firewall/vercel-waf/custom-rules) bypasses are separate, so check both. Deny and challenge rules can block your own [Cron Jobs](https://vercel.com/docs/schedules/cron-jobs); exclude paths for jobs that handle orders, inventory, or feeds.

### Prepare for Attack Mode

[Attack Mode](https://vercel.com/docs/vercel-firewall/attack-mode) challenges traffic for 1, 6, or 24 hours, letting known bots, webhook providers, and your own functions and cron jobs through. It can block standalone APIs and unrecognized clients, including shopping agents missing from the verified directory.

Decide in advance who can turn it on, when to use it, and how you’ll confirm that shoppers, apps, and supported agents can still buy once it’s on.

## Make sure spend settings support the expected traffic

By default, [Spend Management](https://vercel.com/docs/spend-management), on Pro and on Enterprise with Flexible Commitment, pauses production for every project on the team when you reach your amount, and visitors see `503 DEPLOYMENT_PAUSED`. Raising the amount doesn’t resume projects; you have to resume each one manually.

Spend is checked every few minutes, so usage accrues before the pause. Set a budget that covers expected holiday traffic, or turn off pausing if your policies allow, and route the 50%, 75%, and 100% notifications and [spend webhooks](https://vercel.com/docs/spend-management#configuring-a-webhook) to on-call. Pausing doesn’t stop AI Gateway usage, so review [AI Gateway budgets](https://vercel.com/docs/ai-gateway/observability-and-spend/budgets) for expected holiday usage too, and see [Plan for budget limits](https://vercel.com/kb/guide/black-friday-preparation#plan-for-budget-limits).

## Test deployments and rollback

A code freeze can reduce unnecessary changes, but you still need a safe way to ship a fix during Black Friday. Before the freeze, use [Vercel Flags](https://vercel.com/docs/flags) to implement and test switches that disable non-essential dependencies and AI features. Document each feature’s fallback behavior and who can activate it without a deployment.

### Validate changes before expanding traffic

Review promotion, checkout, and inventory changes in [Preview Deployments](https://vercel.com/docs/deployments/environments#preview-environment-pre-production) with production-like configuration and data. [Vercel Agent Code Review](https://vercel.com/docs/agent/pr-review), in public beta on Pro and Enterprise, reviews pull requests and tests suggested fixes against your builds.

[Rolling Releases](https://vercel.com/docs/rolling-releases) send a new deployment to a share of traffic first so you can compare checkout and error metrics; Pro includes one project, and Enterprise limits are custom.

![Rolling release sending 25% of traffic to a canary, with error rates and Speed Insights metrics compared side by side for the current and canary deployments](https://images.ctfassets.net/hjgychtc108g/5KIxb6JeYlj7bBfBPvJD4R/7debbc69dc9f9816e0fa31c3f093a161/image.png)

[Skew Protection](https://vercel.com/docs/skew-protection) keeps client-side navigations and Server Actions on the deployment that served the page. Full-page navigations still load the latest, and Next.js and Astro need [extra setup](https://vercel.com/docs/skew-protection#pinning-requests-without-a-deployment-id) to keep a multi-step checkout on one deployment. Test your checkout across a release.

### Account for cache behavior during a release

ISR pages and Next.js 16’s `use cache: remote` entries don’t carry over to a new deployment, while Runtime Cache with `getCache` and stable keys, and Next.js `fetch` with `cache: 'force-cache'`, stay readable. Runtime-generated pages regenerate and add upstream load, so [measure a release’s effect](https://vercel.com/docs/runtime-cache#how-a-new-deployment-affects-cached-data) under test traffic.

### Rehearse the path back

Before Black Friday:

- **Choose a fallback deployment.** Identify the last known good deployment.
  
- **Verify access.** Confirm that the on-call team has permission to roll back.
  
- **Define rollback triggers.** Agree on which alerts or failures warrant a rollback.
  
- **Choose a coordination channel.** Make sure everyone knows where to communicate during an incident.
  
- **Practice the rollback.** Verify that the fallback deployment works with your current services and settings.
  

[Instant Rollback](https://vercel.com/docs/instant-rollback) points production domains to an earlier deployment, but it does not:

- Undo database, CMS, or payment changes.
  
- Apply newer environment variables to the earlier build.
  
- Move queued work. In Vercel Queues push mode, messages remain pinned to their publishing deployment.
  

After a rollback, new deployments no longer automatically receive production traffic. To resume automatic production updates, promote a deployment from the dashboard or run [`vercel promote`](https://vercel.com/docs/cli/promote).

## Troubleshoot issues during Black Friday

### Checkout failures

- **Signal:** Checkout errors exceed their threshold or the completion rate falls below its target.
  
- **Action:** Find the failing step by route and external API in Observability. If a deployment just shipped, follow [Release regressions](#release-regressions); if checkout requests are challenged, follow [Legitimate clients are blocked](#legitimate-clients-are-blocked). For a failing provider, disable non-essential features using Vercel Flags and escalate.
  
- **Verify:** Completion meets your criteria, synthetic checks pass, and orders reconcile with payments.
  

### Legitimate clients are blocked

- **Signal:** Challenges or denials rise, verified bot or partner traffic drops, or webhooks get `403` responses.
  
- **Action:** Find the matching rule on the Firewall overview, then switch it to Log, narrow it, or add a bypass. [Restore a previous configuration](https://vercel.com/docs/vercel-firewall/vercel-waf#instant-rollback) from the audit log only if no deliberate changes followed it. Changes apply globally within 300 ms. Decide whether Attack Mode is still needed.
  
- **Verify:** The client’s policy test completes, and missed webhooks are replayed.
  

### Abusive traffic or an unexpected load spike

- **Signal:** Requests far above forecast without matching purchases or Web Analytics visitors (which exclude bots), surging login attempts, or `503 FUNCTION_THROTTLED`.
  
- **Action:** Check campaign traffic, function concurrency, and downstream latency to distinguish legitimate demand from abuse. For abuse, find the dominant IPs, JA4 digests, or AS names in the Firewall overview and add targeted rate-limit or deny rules. If those don’t hold, check which checkout APIs and shopping agents can’t pass a challenge, then turn on [Attack Mode](#prepare-for-attack-mode).
  
- **Verify:** Requests fall toward forecast, checkout completion stays above your target, policy tests pass, and the traffic doesn’t return when Attack Mode expires.
  

### Release regressions

- **Signal:** Errors or latency increase after a deployment, or a rolling-release canary underperforms.
  
- **Action:** Abort the rolling release, follow [Rehearse the path back](#rehearse-the-path-back), or turn off a flag. Revert external changes in your CMS or databases separately.
  
- **Verify:** Metrics recover, database and API load stays within tested limits, and messages the rolled-back deployment published are processed or reconciled. Promote a deployment so pushes reach production again.
  

### Delayed order processing

- **Signal:** Queue backlog or message age grows, emails are delayed or fulfillment lags, or orders remain unconfirmed longer than usual.
  
- **Action:** Check downstream services and blocked webhooks or cron jobs. Restore a healthy deployment for new orders. In Vercel Queues push mode, rollback leaves pending messages on their publishing deployment; [delete that deployment](https://vercel.com/docs/queues/concepts#stopping-deliveries-to-a-deployment) if its consumers must stop. Reconcile incomplete orders with your system of record and replay unfinished work idempotently.
  
- **Verify:** Backlog and message age recover in [Queues observability](https://vercel.com/docs/queues/observability), with no duplicate or stuck orders.
  

### Spend-related interruptions

- **Signal:** `503 DEPLOYMENT_PAUSED`, spend notifications, or AI Gateway `402` responses with `quota_for_entity_exceeded`. A budget rejection may surface as an SDK exception, so inspect its quota details before retrying.
  
- **Action:** For paused projects, increase the team’s On-Demand Budget or disable production pausing, then resume each project individually. For AI Gateway quota errors, increase the budget for the relevant scope. Budget changes can take a few minutes to apply, so keep the tested fallback active until requests succeed.
  
- **Verify:** Every production domain serves requests successfully and AI features respond.
  

## Review results after the event

After the sale, do a review with the on-call team. Compare what monitoring showed with what the business saw, write down what slowed recovery, and turn each finding into a specific follow-up task. Review costs too, including ISR writes compared to reads, firewall and bot activity, and any unexpected spikes in compute or AI usage.

Save this year’s baseline, including how much traffic came from shoppers, crawlers, and agents. Schedule the follow-up work into your regular development cycle, so it ships before next year’s preparation starts.

## Get ready for Black Friday with Vercel

During BFCM 2025, Vercel served more than 115.8 billion requests, peaked at 518,027 requests per second, and handled more than 6.1 million deployments.

**Built for Black Friday scale**

Learn how retail teams use Vercel to stay fast and recover quickly during Black Friday and Cyber Monday.

[Talk to our team](https://vercel.com/contact/sales)

## Related resources

- [How to prepare your storefront for Black Friday traffic](https://vercel.com/kb/guide/black-friday-preparation)
  
- [Billions of requests: Black Friday-Cyber Monday 2025](https://vercel.com/blog/bfcm-2025)
  
- [Just another (Black) Friday](https://vercel.com/blog/just-another-black-friday)
  
- [Helly Hansen migrated to Vercel and drove 80% Black Friday growth](https://vercel.com/customers/how-helly-hansen-migrated-to-vercel-and-drove-80-black-friday-growth)
  
- [How KIKO Milano scales for Black Friday](https://vercel.com/customers/how-kiko-milano-scales-for-black-friday)
  
- [Making your catalog discoverable to AI agents](https://vercel.com/kb/guide/agentic-commerce-readiness)
  
- [Vercel Firewall](https://vercel.com/docs/vercel-firewall) and [Bot Management](https://vercel.com/docs/bot-management) documentation

## Related Documentation

- [Firewall](/docs/vercel-firewall)
- [Observability](/docs/observability)
- [Web Application Firewall](/docs/vercel-firewall/vercel-waf)

## More Firewall guides

- [How to prepare your storefront for Black Friday traffic](/kb/guide/black-friday-preparation): Set baselines and cut backend load. Make your catalog readable to agents and keep orders and AI features reliable. Then load test checkout before traffic peaks.
- [Using Cloudflare and other reverse proxies with Vercel](/kb/guide/can-i-use-a-proxy-on-top-of-my-vercel-deployment): General information about using an external proxy to serve a Vercel Deployment.
- [Protect Sensitive Routes with Vercel WAF: Challenge and Deny Rule Recipes](/kb/guide/suspicious-traffic-in-specific-countries): Use Vercel WAF custom rules to block or challenge unwanted traffic by country, ASN, IP address, user agent, path, or cookie, without redeploying.

## Reference Architecture

Choose a stack and work through the decisions behind it, with curated documentation, guides, templates, and courses to help you build.

- [Agent stack](/kb/architecture/agents): Build and operate agents with models, tools, and durable workflows.
- [Web applications](/kb/architecture/web): Choose rendering, data, authentication, and caching approaches.
- [Backends](/kb/architecture/backends): Choose a runtime, connect services, and run background work.

[Browse all stacks](/kb/architecture)

## Build with prompts

Build an app, extend an agent, or improve your project with ready-to-use prompts for your coding agent.

[Browse the prompt library](/kb/prompts) · [Read the Markdown index](/kb/prompts.md)

## Search guides from your terminal

Search the Knowledge Base and read guides as Markdown with the Vercel CLI. No login required.

```bash
# Find guides by keyword
npx vercel@latest kb search "rewrites and redirects"
npx vercel@latest kb search "AI SDK streaming"

# Show the latest guides
npx vercel@latest kb

# Print a guide as Markdown, by slug or URL
npx vercel@latest kb inspect <guide>
```
