Diwali 2026 Website Checklist: Get Your Online Store Ready Before 8 November

When is Diwali 2026, and how much time do you really have?

Diwali 2026 falls on Sunday 8 November, according to the panchang sources we checked. Dhanteras, which many Indian shoppers treat as the start of the buying week, is on Friday 6 November, and Choti Diwali (Naraka Chaturdashi) is on Saturday 7 November. Govardhan Puja is on Monday 9 November and Bhai Dooj is on Tuesday 10 November. The exact Lakshmi Puja timing differs between sources and cities, so if you plan a timed launch for puja hours, check a panchang for your city. One page we found still listed 20 October, which matches Diwali in 2025, so be careful with older articles.

That calendar leaves less time than it seems. If you are reading this on 22 October, you have about two weeks before Dhanteras. A realistic plan allows a week for preparation and testing, a freeze in the last week of October, and a few days of buffer for the things that always go wrong: a courier that changes its rules, a payment method that fails, a product photo that was never uploaded.

This guide is for owners and managers of small and mid-sized online stores in India, including D2C brands, Shopify and WooCommerce stores and sellers with a custom-built site. It covers the website side of festive preparation: speed, stability, checkout, stock, tracking, offers and support. It does not tell you what discount to give. Many vendor guides already cover offers and ad creative. Few cover what happens when your store has to handle three times its normal traffic and a customer is trying to pay at 11 pm on Dhanteras.

A note on honesty. We have not run a load test on your store, and we do not know your traffic. So this guide gives you a method and checks, not promises. Where a number appears, it comes from a published source. Where it does not, we say so.

What should you finish this week, before anything else?

Start with decisions, not with tools. Spend an hour with your team and write four things on one page.

First, your three or four best-selling or most-promoted products, and the pages that will receive most of your festive traffic. This is where speed and stock accuracy matter most. Everything else on the site can be slightly slower without hurting the sale.

Second, the dates of your offers. Decide when the sale starts, whether it changes on Dhanteras, Diwali and Bhai Dooj, and when it ends. Offers that change without warning cause cart abandonment and complaints.

Third, your promises. What is the last date for orders to arrive before Diwali, by pincode group? What is your return and replacement policy for festive gifts? Which payment methods do you accept, and what happens when one fails? Write the answer in plain words, because these sentences will go on the product page, the checkout and the confirmation email.

Fourth, your owners. Name one person for the website and hosting, one for stock and orders, one for customer messages and one for ads. Put their phone numbers on the page. On the evening of Dhanteras you do not want to find out who is responsible for the payment page.

• Pick the three or four pages that will get most of the traffic.
• Fix the offer dates and the order cut-off dates in writing.
• Write your delivery, return and payment-failure promises in plain words.
• Name one owner each for website, orders, support and ads.

How do you check that your store will stay fast under festive traffic?

A slow store loses sales quietly. Shoppers on a phone do not complain, they leave. Google also uses real-world page experience data, and its documentation describes Core Web Vitals as measures that align with what its systems look for. They are not a guarantee of ranking, but they are a useful standard for speed.

According to web.dev, a page has a good experience when its Largest Contentful Paint (LCP) is within 2.5 seconds, its Interaction to Next Paint (INP) is 200 milliseconds or less and its Cumulative Layout Shift (CLS) is 0.1 or less, measured at the 75th percentile of page loads across mobile and desktop. In plain words: the main content should appear within about two and a half seconds, the page should respond quickly when tapped and nothing should jump around while the page loads.

Run three checks this week. First, paste your home page, your top product page, your cart and your checkout page into PageSpeed Insights and note the mobile results. The field data section, where it appears, shows what real users experienced. The lab section helps you find causes. Second, open your top product page on a mid-range Android phone on mobile data, not on your office Wi-Fi, and time it with a stopwatch. Third, look at the heaviest items: oversized images, auto-playing banner videos, chat widgets, review widgets and tracking scripts. Each one costs time.

Typical fixes are not glamorous. Compress and resize product images, serve modern formats such as WebP, remove banners that nobody clicks, delay non-essential scripts until after the page loads and keep the number of fonts low. If you use Shopify, remove apps you no longer use, because some apps can leave code running after they are removed. If you use WooCommerce, check your caching and your hosting plan, because a cheap shared server is often the real limit. For detailed help, see our guide to Core Web Vitals for small businesses and our website speed optimization service.

Then test the load, if you can. A simple test sends many visitors to your pages at once and shows when response times rise or errors begin. Free open-source tools exist for this, and hosting providers often have their own. Do not run an aggressive test against a shared host without asking, because you could trigger limits or your host's security tools. Start small, increase gradually and run it on a quiet night. The aim is not a perfect score. The aim is to learn how many visitors your setup handles and what breaks first.

If the answer is that your hosting cannot cope, you have three options before Diwali: upgrade the plan, add a caching layer or content delivery network, or reduce what each page does. Ask your host in writing what traffic your plan is built for and what happens beyond it. Do not wait until the sale starts to ask.

Which checkout and payment tests should you run?

Checkout is where the money is, so it deserves the most careful testing. Place real test orders, not just a visual check.

List every way a customer can pay on your store: UPI, cards, net banking, wallets, EMI, cash on delivery. For each one, place a test order on a phone. Where your payment gateway offers a test mode, use it first to confirm the flow, then place at least one small live order per important method and refund it. Check what the customer sees, what the order record shows, whether the confirmation email and message arrive and whether stock reduces correctly.

Test the failure cases as well. What happens if a payment fails and the customer tries again? Is there a clear message, or a blank screen? Does a failed payment leave a pending order that blocks stock? Does a customer who pays twice get a refund process? These situations are rare on a normal day and common during a rush, because people tap again when a page feels slow.

If you are still choosing or changing a payment gateway, do not do it in the last fortnight unless you must. Our payment gateway guide for India explains how to compare options, but a switch needs verification steps and testing that take time. If your current gateway is stable, leave it, and ask your account manager about any limits, settlement timings or festive-season notices in writing.

Check the small things people forget. Is your GST information on invoices correct? Does the order confirmation show the delivery estimate you actually intend to meet? Is the cash-on-delivery option available only for pincodes your courier serves? Can customers apply a discount code on a phone without the page jumping? Does the coupon field accept the code with and without capital letters? Each is a small detail that costs real orders if it is wrong.

If you sell on Shopify or WooCommerce, check that every plugin or app in the checkout path is up to date, and that you do not install or update any of them after your freeze date. If you are building or rebuilding a store, our ecommerce website development team can set up and test the checkout, and our payment gateway integration service covers the connection itself.

• Place a test order for each payment method, on a phone.
• Test failed and repeated payments, not only the happy path.
• Avoid switching gateways in the last two weeks unless you must.
• Freeze plugin and app updates in the checkout path after 31 October.

How do you keep stock, orders and couriers in step?

The most expensive festive mistake is selling something you cannot ship. It costs you the order, a refund, a bad review and the customer's trust, often all at once.

Start with stock accuracy. If you sell on your own site and on marketplaces, or from more than one warehouse, check how stock is synchronized. Does a sale on one channel reduce stock on the others immediately, or in batches every few hours? If it is in batches, the gap is when overselling happens. Consider holding back a buffer of units on your own site for your best sellers, and lower the displayed quantity on items where you have only a few left.

Check bundles and combos. A gift hamper made of five items sells out when its scarcest component sells out. Make sure your system understands that, or create the bundle as its own product with its own count.

Then talk to your courier or shipping aggregator. Ask them in writing, not on the phone: what are the last dates to book pickups for delivery before Diwali, by pincode group? Are there pickup or delivery limits in the festive week? Which pincodes, if any, will be slower? Which services does the cash-on-delivery option depend on? Ask for any festive-season notices they have published. We do not quote courier cut-off dates in this guide, because they differ between providers and change, so the only safe source is your own provider's written reply.

Use that reply to set your own order cut-off dates and show them clearly: on the product page, in the cart and in the confirmation email. Where a gift must arrive by a date, say 'order by' and name the date. If you cannot promise a date for a pincode, say so before the customer pays, not after.

Finally, plan your pack and dispatch capacity. A website can accept ten times more orders than your team can pack. If orders will exceed your daily capacity, decide now what you will do: pause cash-on-delivery, extend the delivery estimate, close the sale early or add temporary help. All of these are better than silently shipping late.

How do you write offers and countdowns that stay honest?

Festive sales run on urgency, and urgency is where sellers make their riskiest mistakes. India's Central Consumer Protection Authority issued Guidelines for Prevention and Regulation of Dark Patterns on 30 November 2023. According to legal summaries, they apply to platforms offering goods and services in India, to advertisers and to sellers, and they list specific practices as dark patterns. Among them are false urgency, which means falsely stating or implying urgency or scarcity to mislead a user into an immediate purchase, and basket sneaking, which means adding items or charges at checkout without the user's consent.

In practice, this gives you a short list of things to check on your own site. A countdown timer should end when the offer really ends, and should not restart for each visitor. A message such as 'only 2 left' should reflect real stock. A 'fifty people are viewing this' message should come from real data or not exist. Charges such as gift wrapping, insurance or a donation should never be added to the basket unless the customer chooses them. Shipping and other fees should be visible before the final step, not revealed at the end. A decline button should not use wording meant to make the customer feel foolish.

We are not lawyers, and this is not legal advice. The guidelines have a full annexure with more examples than we list here, and we recommend that you read it, or ask your legal adviser, if you run complex offers. We mention the rules because honest design is also better business: customers who feel tricked during Diwali do not return in January.

A few other offer checks matter just as much. Make sure your discount is calculated correctly with GST, shipping and any coupon stacking. Make sure the 'was' price is a price you really charged. Make sure free-gift conditions are written clearly. And make sure the offer on your ad is the offer on the page, because a mismatch sends visitors back in seconds.

What tracking should you test before the sale?

Festive week produces more data than any other week of your year, and a broken tag means you lose it for good. Test your tracking before the freeze, not during the sale.

In Google Analytics 4, confirm that your purchase event fires once per order, that the value and currency are correct and that it carries the right items. Place a test order and look for it in DebugView or Realtime. Check that the same order is not counted twice when a customer refreshes the thank-you page. If you run Google Ads or Meta Ads, test that your conversion tags fire on the same event and that the values match your orders.

Our GA4 setup guide explains key events in detail, written for US businesses but with steps that apply anywhere. It explains why you should mark only the actions that matter as key events, as Google's own help page recommends.

Think also about what you want to learn afterwards. Which source brought the highest-value orders? Which product pages had the highest exit rates? What proportion of carts failed at payment? If you know the questions now, you can check that the data to answer them is being collected. Add campaign tags to every ad, message and email link so that your sources are labelled correctly. A link without tags lands in a vague 'direct' bucket and hides what worked.

Finally, decide how you will check your numbers against reality. Compare the orders in your analytics with the orders in your store admin for the same days. A small gap is normal. A large gap means something is broken, and you want to know on 2 November, not on 12 November.

What should you do about messages, emails and customer support?

Diwali shoppers send many messages, and they send them on WhatsApp, Instagram and phone more than by email. Decide in advance who answers, how fast and with what wording.

Prepare short, honest answers to the ten questions you expect: where is my order, can I change my address, why did my payment fail, can I return a gift, is cash on delivery available in my area, will it arrive before Diwali, can I get a bill, how do I use this coupon, can I cancel, and how do I reach a person. Put the answers in a shared document so that every team member says the same thing.

If you use WhatsApp Business, set an away message and a greeting that fit the festive week, and consider quick replies for the common questions. If you are weighing the WhatsApp Business app against the API, our guide to WhatsApp Business app and API for Indian businesses explains the difference. Do not set up something new in the final week. Use what you have, and make it neat.

Check your automated emails and messages. Does the order confirmation include the right order number, items and expected delivery date? Does the shipping update carry a working tracking link? Is the sender name clear, and does the reply address lead to a mailbox that someone reads? If emails go to spam, your best messages are never seen. Our guide to email marketing for small businesses explains the basics of authentication and deliverability.

Finally, plan the days after the sale. Orders keep arriving until 8 November, and complaints and return requests keep arriving for weeks. Keep support cover for 6 to 10 November, and plan a lighter rota for the week after so that your team is not exhausted. A short thank-you message with a reorder offer sent after delivery turns festive buyers into repeat customers.

What does a day-by-day countdown look like?

Here is a plan you can adapt. It assumes you start on Friday 23 October. Move the days if you start later, but keep the order, because each step relies on the one before.

23 to 25 October: decide and audit. Hold the one-page planning meeting. Pick your key pages, fix your offer dates and cut-off dates, and name your owners. Run PageSpeed Insights on your top pages and note the biggest problems.

26 to 28 October: fix speed and stability. Compress images, remove unused apps and scripts, check caching and ask your host about capacity. Start a small load test on a quiet night if your host allows it.

29 to 30 October: test checkout and tracking. Place test orders for every payment method on a phone. Check the confirmation messages, stock changes and analytics events. Confirm courier cut-offs in writing.

31 October: freeze. No new plugins, no theme changes, no checkout changes. Only urgent fixes with a named approver. Take a full backup and confirm that you can restore it.

1 to 3 November: final checks. Review offer pages, countdown timers and stock numbers with a customer's eyes. Load your support answers. Schedule your ads and messages, and check that every link works.

4 to 5 November: warm up. Publish the offer. Watch speed, errors and stock hourly. Have your developer reachable.

6 to 8 November: peak. Dhanteras is Friday 6 November, Choti Diwali is Saturday 7 November and Diwali is Sunday 8 November. Watch orders, payment failures and stock several times a day. Answer messages quickly. Update delivery estimates the moment they change.

9 to 10 November: follow up. Govardhan Puja and Bhai Dooj may bring a smaller wave. Send shipping updates, answer return requests and compare analytics with your orders.

Here is an invented example, clearly for illustration only. A small home-decor brand plans a Dhanteras sale. On 24 October, its owner finds that the cart page takes seven seconds to appear on mobile because of a banner video, so the team replaces it with a still image. On 29 October a test order with UPI works, but a card payment leaves the order stuck as pending. The developer finds a plugin conflict and fixes it before the 31 October freeze. On 1 November the courier replies that pickups for some far pincodes will take longer, so the brand adds an 'order by 3 November' note for those areas. None of this is dramatic, and all of it protects the sale.

• 23 to 25 Oct: decide and audit. 26 to 28 Oct: speed and stability.
• 29 to 30 Oct: checkout, tracking and courier confirmation.
• 31 Oct: freeze and backup. 1 to 3 Nov: final checks.
• 4 to 5 Nov: warm up. 6 to 8 Nov: peak. 9 to 10 Nov: follow up.

What are the most common festive mistakes?

Changing things in the last week. New plugins, a new theme or a new checkout is the usual cause of a festive outage. Freeze early.

Testing only on a fast laptop. Your customers use phones on mobile data. Test the way they buy.

Ignoring failed payments. A payment that fails and cannot be retried easily loses the order. Test failure and repeat.

Overselling. Stock that is not synced across channels, or bundles that ignore their parts, create orders you cannot ship.

Promising dates the courier has not confirmed. Get written confirmation, then show clear order-by dates.

Fake urgency. Timers that restart, low-stock badges that are not true and charges added without choice put you at legal and reputational risk.

No plan for support. The week after Diwali is when unanswered messages become public complaints.

Losing the data. A broken analytics tag means you cannot learn from the biggest week of your year.

When should you get a developer or agency involved?

You can run most of this checklist yourself or with the people you already have. Get specialist help when something is outside your comfort zone and the cost of a mistake is high: a store that is slow on mobile, a checkout that fails for some payment methods, a hosting plan that may not cope, an inventory sync that you do not fully understand, or a custom-built site with no one who knows it well.

At Quavento Technologies, our ecommerce development team builds and maintains online stores, and our ecommerce maintenance service covers updates, monitoring and fixes. If you are a direct-to-consumer brand, see our D2C website development page. If you sell on Shopify, our Shopify development services include speed optimization. If you would like an Indian team to build or review your store, see our ecommerce website development services in India.

If you are still planning your first store, start with our guide to starting an online store in India and come back to this checklist before your first festive season. And if you can do only one thing this week, test a real order on a phone, on every payment method. It takes an hour and finds more problems than any report.