Test your Shopify purchase flows before Black Friday

Thanksgiving is Thursday 26 November 2026, Black Friday is Friday 27 November and Cyber Monday is Monday 30 November. Work back from those dates:

A code freeze stops your team changing the store. It does not stop your apps. App storefront scripts are served from each vendor's own servers, so a new version goes live on your store without an approval step, including over Black Friday weekend.

In Revenue Shield's Shopify App Change Report, third-party app code on a typical monitored store changed about 5 times a week, and 74% of store-weeks had at least one change. Most of those changes are routine and harmless. The risk is the occasional one that conflicts with your theme, your discount setup or another app during the busiest days of the year.

• Ask your vendors. Check whether the apps on your product page, cart and checkout path pause releases over BFCM, and for which dates.
• Stop installing. No new apps after your freeze date, even "quick" ones.
• Watch the outcome, not the vendors. You can't review every release. You can check continuously that a customer can still add to cart and reach checkout on desktop and mobile.

Your promotion changes the paths shoppers take. You add campaign discount codes, launch bundles and gift-with-purchase offers, install or update apps for the season, and push last-minute theme edits — then drive record traffic at all of it. Each change is a chance for a conflict, and peak traffic means any latent problem gets hit far more often.

A store can return a normal page (HTTP 200) while a customer still cannot add an item to the cart or reach checkout. That is why the purchase flow itself — product to variant to cart to checkout — needs to be tested directly, not assumed to be fine because the site loads.

Work through each journey your campaign will drive traffic to, on both desktop and mobile. Record the result so anyone on the team can see what has been verified and what still needs attention. Test in advance while you can fix issues calmly, and re-run the affected rows after every change to apps, theme or promotions.

Add a row for every journey that matters to your campaign. The point is not to test everything once — it is to have a record you can re-run after each change, on both viewports.

• Product and variant selection — the specific SKUs your campaign promotes add to the cart, with the correct variant.
• Discounts — apply every campaign code on a real cart and confirm the expected total; test stacking rules (code plus automatic discount) for double-apply or conflict.
• Bundles and gift-with-purchase — the seasonal offer builds the correct cart contents and price.
• Stock — in-stock SKUs add to cart, and sold-out states are shown clearly rather than silently failing.
• Subscriptions — the first purchase of a subscription product reaches checkout. Note that this checks the initial purchase, not recurring billing.
• Viewport — repeat on mobile, where a sticky promo bar, pop-up or cart drawer can cover or block the checkout button.
• Market — check any second market or currency your campaign targets.

The checklist above is a manual pre-flight: a person works the journeys in a browser and records the result. It is the right tool for verifying the specific, seasonal combinations before the event.

Automated monitoring covers the different problem of a break that appears during the event. Revenue Shield runs the same purchase journey — product to cart to checkout — on desktop and mobile on a schedule, and alerts your team with a video recording, trace and screenshots when a run detects a failure. Checks run on a schedule (hourly on Starter and Growth, and as often as every 15 minutes on the top tier), so detection speed depends on the schedule plus run and confirmation time — not the instant a break occurs. Tests stop before payment and never place an order.

Use the manual checklist to go into the weekend on a verified flow, and use monitoring to catch anything introduced by a change made during the event. See the readiness checklist, run a free readiness audit, or read more on checkout testing.

A successful run covers the journey, product, variant, market and viewport you tested. It does not prove that every product, market, payment method or customer session works, and because the test stops before payment it does not verify that a card payment can be completed. That is why the checklist records the exact conditions for each row, and why monitoring repeats the journeys that matter most.