Black Friday 2026 falls on Friday 27 November. For online retailers, September and October are the time to test what tends to fail under pressure: inconsistent discounts, stale stock, broken payments and slow campaign pages. This checklist focuses on the customer journey from first visit to confirmed order.
1. Agree on the offer before building the campaign
Choose the eligible products, start and end times, coupon rules and the margin left after shipping, returns and tax. Put the rules in one document shared by marketing, support and operations. The product page, basket and checkout must display the same price. Schedule the promotion and test what happens both when it starts and when it ends.
Make exclusions visible near the offer. An impressive headline will not help if shoppers discover an unexpected condition at payment.
2. Reconcile catalogue, stock and delivery dates
Review the images, variants, availability, shipping costs and delivery estimates for featured products. Test the last item in stock: availability needs to update in the basket as well as on the product page. If you sell through several channels, check how inventory is shared so you do not accept orders you cannot fulfil.
Keep product prices and availability consistent across your site and Merchant Center, if you use it. Google's ecommerce structured data guidance explains how product information can help its systems understand your pages. Clear product pages also help customers make a decision before adding to basket.
3. Complete a real test order on a phone
Start on a mobile device, find a product, select a variant, apply a coupon and pay with each active payment method. Check the confirmation screen and email. Repeat with a rejected payment and an expired coupon. The error should explain the next step. Test guest checkout, autofill, mandatory fields and the final total before the customer confirms.
Record the date, device, browser and owner for every issue. Fix failures that prevent payment first, then remove unnecessary steps and confusing messages.
4. Measure speed and prepare for higher traffic
Test campaign pages, categories, products and checkout on mobile. web.dev's Core Web Vitals guide covers field and diagnostic measurements: LCP tracks when the main content appears, INP reflects responsiveness and CLS catches unexpected layout shifts. Compare results before and after adding campaign banners, tracking scripts and widgets.
Discuss expected peaks with your hosting provider or technical team. A controlled load test, alerts and an incident plan give you evidence about capacity. See our website speed guide for the underlying checks.
5. Prepare search visibility without last-minute URL changes
If the campaign returns each year, consider keeping a stable URL and updating its content. Link to it from relevant categories and products. Check page titles, descriptions, internal links, canonicals and indexing. Avoid restructuring the whole store during launch week.
Validate product offer information against Google's merchant listing documentation. Structured data can help search engines interpret price and availability; it does not guarantee rich results or sales.
6. Test measurement and assign incident owners
Before increasing ad spend, verify product views, add-to-basket events, checkout starts and purchases. Check that conversions are not counted twice and that email and ad links have useful campaign tags. Decide who will act if a payment provider fails, a featured item sells out or a discount is wrong. Prepare clear support answers about delivery and returns.
Launch-week checklist
- Prices, schedules and coupons tested on real products.
- Stock and variants aligned across sales channels.
- Full purchase tested on mobile and desktop.
- Order and payment-failure emails checked.
- Campaign URLs, metadata and product information validated.
- Alerts, technical owner and incident plan agreed.
Fix any failed item before sending more traffic to the store. If you would like an independent review of the shopping journey, tell us what you sell and where customers get stuck.
