Black Friday falls on November 27, 2026, and Cyber Monday on November 30. For most stores, the checkout problems that hurt most are not dramatic outages. They are quiet ones: a payment that fails on a phone with no clear message, an order that shows as placed but never reaches your ERP, a stock level that is a few minutes out of date.
This guide covers the two areas of our Black Friday and Cyber Monday timeline that decide whether orders actually go through: UX & Customer Experience, and Magento / Adobe Commerce Technical Readiness. Both sit in the Build phase, so any fixes land before your code freeze. After the freeze, the work shifts to verifying, monitoring and supporting.
Test the whole journey, not just checkout
Customers don’t arrive at checkout. They arrive by searching, browsing a category, landing on a product page and deciding to add to cart. If any of that is clumsy on mobile, they never reach the part you tested.
So we walk the journey in order, from the first search to the last background job, and we do it on real phones, not only in a narrow desktop browser window.
| Step | What to test | Where it tends to break | |
| 1 | Search and navigation | Search for best-sellers by name, by common misspelling and by category. Check filters, sorting and category pages, and that your Black Friday and Cyber Monday category and landing pages are easy to reach. | Results that miss obvious products, or sale pages buried in the menu. |
| 2 | Product page | Price, stock status and delivery information are clear and match the cart. Check variants, bundles and any new products added for the sale. | Prices or stock messages that differ between the page and the cart. |
| 3 | Cart | Change quantities, remove items and apply a discount code. Check totals, shipping and tax. | Totals that don’t update, or discounts that don’t apply. |
| 4 | Checkout on mobile | Walk every field and error message on a real phone. Check the keyboard doesn’t cover the pay button. A good error says what went wrong, says how to fix it, and keeps the cart and details in place. | Forms that are hard to finish on a small screen, and vague error messages. |
| 5 | Payment gateway | Authorise and decline cases using your gateway’s test mode, then check the order status afterwards. | Timeouts or delayed responses that leave an order and a payment out of step. |
| 6 | Shipping and tax | Rates and tax for different addresses, countries and carts. | Slow third-party responses, or rates that don’t load at checkout. |
| 7 | Inventory sync | Place a test order and confirm stock and salable quantity update, including from your ERP, OMS or PIM. | Sync lag, which can lead to overselling a best-seller. |
| 8 | ERP / OMS hand-off | Confirm the order reaches the downstream system with the right details. | Orders that look complete in Magento but never arrive downstream. |
| 9 | Queues and background processes | Check queues are being processed and cron jobs are running on schedule. | A stuck queue or missed cron job that nobody notices until orders pile up. |
| 10 | Emails and notifications | Order confirmation and any payment notifications arrive. | Delayed or missing messages that turn into support requests. |
Steps 1 to 4 are what the customer sees. Steps 5 to 10 happen once they tap pay, when one order passes through several systems in seconds. Each can fail on its own, and some failures are invisible to the customer. Run the whole path as complete test orders, ideally on staging with your final code, and repeat them after any late fix. Include an order with a discount applied and one with a new product or bundle.
The 9 pm test: what happens when a payment fails?
Here is a hypothetical worth running with your team. It’s 9 pm on Black Friday. A customer on their phone reaches the last step of checkout, taps pay, and the payment fails. What do they see?
Try these cases on purpose, on a real phone, and check each one gives a clear message, a way to try again, and a cart that is still intact:
- A card that is declined
- A session that times out before payment
- A connection that drops mid-payment
- A customer who taps back after submitting
- An item that sells out between cart and payment
Most stores test the happy path. Testing these cases before the freeze shows you what customers would actually see.
Adobe Commerce vs Magento Open Source
Third-party allowlists. On Adobe Commerce Cloud with auto-scaling enabled, outbound traffic comes from the service node IPs, so check that payment, ERP and shipping providers have the right addresses allowed. On self-hosted Adobe Commerce and Magento Open Source, allowlists usually only change if your host changes infrastructure.
B2B flows. If you use the Adobe Commerce B2B module (company accounts, shared catalogs, quotes), test those flows as their own checkout journey. The B2B module isn’t part of Open Source, so test any B2B extension you use instead.
Search. Adobe Commerce stores may use Adobe’s Live Search service or OpenSearch. Magento Open Source uses OpenSearch. Check which one your store uses before you test search.
Details can vary by version and plan. Confirm against current Adobe documentation for your setup.
Where this fits in your timeline
Checkout and integration testing sits in the Build phase, now to mid-October. It comes before the Harden phase, where load testing and scaling happen, because load testing only means something once the code is final. Fix what you find first.
Your code freeze is the real deadline. Dates vary by merchant, so ask your development team or agency for yours.
A pre-freeze checklist
- Have we tested the journey on real phones, from search to order confirmation?
- Does every payment failure case show a clear message and keep the cart intact?
- Do test orders reach the payment gateway, ERP or OMS, and email correctly?
- Do stock and salable quantity update after an order?
- Are queues and cron jobs processing on schedule?
- Have we retested after every late fix?
- Do we know our code freeze date, and who approves exceptions?
How Evrig can help
Evrig works with Adobe Commerce and Magento Open Source merchants on checkout, integrations and Black Friday and Cyber Monday readiness. If you’d like help testing your store’s journey before your code freeze, Get in touch.