Blog
Blog
Black Friday is days away, and every store owner feels the same pull: change something. Swap the hero banner, install the app that promises more conversions, update the theme because a new version just came out. Most of those changes feel productive. A few of them are how stores break on the busiest weekend of the year.
The last week before a peak is not the time to improve your store. It is the time to make sure what already works keeps working under pressure. We work with Shopify and custom e-commerce stores every day, and the pattern repeats every year: the stores that struggle on the day rarely lacked features. They changed something in the last few days that nobody had time to test. Here is how we split the list into what is still worth fixing and what should wait until December.
On a normal week, a small bug costs you a few orders before someone notices. During Black Friday, traffic, ad spend and expectations all peak at once. A checkout issue that would be a minor annoyance in March becomes a very expensive afternoon. Every change you ship now carries more risk and leaves less time to roll it back.
So the rule for this week is simple: fix what is clearly broken or clearly slow, and freeze everything else. For any task on your list, ask one question: will this clearly protect or increase sales this week, and can we test it before the rush? If the answer to either half is no, it goes on the post-Black-Friday list.
1. Your slowest important page. Run your best-selling product page through PageSpeed Insights on mobile, not desktop, then open it on a mid-range phone on mobile data. If one oversized image, video or script is dragging it down, removing or compressing it is a low-risk win. Old tracking pixels and code left behind by apps you already uninstalled are another quick one. Rebuilding the page is not.
2. The checkout path, end to end. Place a real test order on a phone: add to cart, apply a discount code, pay, receive the confirmation email. Then do it again as a guest, and with each payment method you offer, including wallets and local options. You are looking for anything that stops, confuses or surprises a buyer, and for orders that don't show up where your team and fulfillment partner expect them.
3. Mobile product pages. Most Black Friday browsing happens on phones, and the product page is where interest becomes a cart. Check that the price, the discount and the add-to-cart button are visible without hunting, that variant selectors are easy to tap, and that the sale price on the page matches the price in the cart. A mismatch between the two is one of the fastest ways to lose trust.
4. Discount logic. Check that every code you plan to promote actually applies, stacks the way you expect and expires when it should. Test free-shipping thresholds and gift cards too. Broken codes create support tickets and abandoned carts in equal measure.
5. Shipping and returns information. Make cut-off dates for delivery before the holidays visible on product pages and in the cart, not only in the FAQ. Check shipping rates for your main markets. Uncertainty about delivery, or a surprise cost on the last step, is one of the most common reasons people hesitate at checkout.
6. Stock and variants. Make sure low-stock and sold-out states display correctly, and that popular variants are not hidden behind a selector nobody notices. A promoted product that sells out while still showing "in stock" does more damage than a quiet day ever would.
New apps. Every app you install can add scripts to every page and interact with your theme and checkout in ways that are hard to predict. Installing one the week before a peak means testing it under the worst possible conditions. If it wasn't installed and tested weeks ago, it doesn't go live now.
Theme updates and redesigns. A new theme version can change layout, filters or cart behaviour, or quietly reset your customizations. Even if it looks fine on your laptop, you have no time left to find the edge cases. Update after the rush, on a duplicate theme, and compare before publishing. The same goes for a new homepage or a rebuilt collection page: launch it in December, when there is time to measure and adjust.
Big navigation or catalogue changes. Renaming collections or restructuring menus now can break links in emails and ads that are already scheduled.
Experiments. A/B tests are valuable, but not when traffic is unusual and every hour counts. Run them in January, when you can read the results calmly.
Anything nobody can test or roll back. If a change touches checkout, payments, tracking or discount logic, and no one is available to verify it and undo it quickly, it waits. If something truly must change, make it small, ship one change at a time, and keep a copy of the working version.
Settle the first block with your team before the weekend, then print the page or pin it in your team channel. The point is that nobody has to improvise at 9 p.m. on Friday.
Agree on before the weekend
Before the sale goes live
During the sale
Keep notes as things happen: which pages slowed down, which questions support kept answering, where people dropped off in checkout. Reconcile orders, stock and fulfillment, then use those notes to write the January list: speed work, theme updates, the redesign ideas you parked. They are the most useful input you will get all year for planning fixes, and a much better reason to change your store than a deadline.
Want a second pair of eyes on your store before the rush, or help with the fixes that should wait until December? Talk to our team — we'll walk through your speed, mobile product pages and checkout the way a first-time shopper would, and tell you what is worth fixing now and what can wait.