If you're planning an Onam sale for a Shopify store in Kerala, the single most useful thing to fix in your head is this: it isn't one discount day. Atham to Thiruvonam is ten days, and the order pattern across those ten days changes three times. Gulf orders land first, gifting and hamper orders peak in the middle, and the last 48 hours before Thiruvonam belong entirely to local, same-state, we-need-it-tomorrow buyers. Merchandise for one curve and you'll misprice, mis-stock and miss cut-offs on the other two.
Onam sits in Chingam, so depending on the year you're looking at late August or early September. The build and merchandising work needs to be finished three weeks before Atham, which is why this is a July conversation, not an August one. Every year we get requests in the third week of August to "add a hamper section quickly" and every year the honest answer is that the theme work will land after the money has already moved.
The ten-day curve, and why it breaks a single-campaign plan
Roughly how it plays out on a Kerala D2C store selling food, handloom or ayurveda:
- Before Atham — NRI buyers in the UAE, Saudi and Qatar start ordering, either shipping to family in Kerala or bringing product to themselves. These orders come early because the buyer knows international transit is slow. Average order value is the highest you'll see all season.
- Atham to day four — corporate and bulk gifting. Someone in Infopark or Technopark buying forty hampers on one PO, and asking for GST invoices with their company GSTIN before they'll confirm.
- Days five to eight — the real retail volume. Individual gifting, sadya ingredients, new clothes, jewellery.
- Last two days — panic buying, Kerala pincodes only, and a very high share of COD.
A single site-wide 20% banner running for ten days serves none of those groups well. It gives away margin to the early NRI buyer who was going to pay full price anyway, and it does nothing for the day-nine buyer whose only question is whether the parcel reaches Thrissur by Thiruvonam morning.
What to build before Atham (and where to stop)
Three weeks out, freeze the theme. From that point, only content and stock changes. The build list is usually shorter than founders expect:
- An Onam landing collection with its own metafield-driven hero, so you can change the headline and the delivery promise without touching Liquid during the sale.
- Bundle or hamper products set up as real products with their own SKUs, not as cart-level discounts. Cart-level bundling breaks in weird ways when a customer removes one component, and your packers can't pick against a rule.
- A visible delivery-cut-off block on product and cart pages. One line, updated daily.
- COD eligibility logic (see below).
- A tested checkout on a real phone on a real 4G connection, not on office Wi-Fi.
What not to build: a new theme, an ERP integration, or a loyalty programme. We've watched a mid-August theme migration eat the entire festive window. If your store needs replatforming or a rebuild, do it in October.
Collections, bundles and the Malayalam layer
Kerala buyers search in a mix of English, Malayalam script and Manglish transliteration. "Kasavu saree", "onam sadya kit", "banana chips gift box", "ഓണം ഹാമ്പർ" — all of it shows up in site search. If your on-site search only matches your English product titles, you're losing carts you already paid to acquire. Add Malayalam terms as product tags or into a search-synonym setting, and check your search logs on day three of the sale to find the terms returning nothing.
For campaign copy, translation is worth it in exactly two places: WhatsApp broadcasts and Meta ad creative. Malayalam ad copy consistently outperforms English on Kerala-geo audiences for food and traditional wear, and WhatsApp is where the order-confirmation-to-repeat-purchase loop actually happens. Your checkout, on the other hand, should stay in English. Half-translated checkouts confuse buyers more than English-only ones. If you want the storefront properly bilingual, it's a content project with its own keyword and copy workflow, not a Google Translate pass in week one of August.
COD limits: the number that decides your festive P&L
COD share on Kerala food and apparel orders climbs during the last three days of the run, and so does the return-to-origin rate, because a chunk of those buyers order the same hamper from two stores and accept whichever arrives first. Set a COD cap by cart value and by pincode before Atham. Our default starting point: COD off above a threshold you pick from your own RTO data, COD off entirely on perishable hampers, and COD off on any pincode where you've eaten two or more RTOs in the last six months.
Then do the arithmetic before you run a prepaid discount, because it doesn't always pay. Say you expect 1,000 orders across the ten days: 600 COD, 400 prepaid. At a 20% RTO rate on COD, that's 120 failed orders. Forward plus return freight at ₹85 each way is ₹170 per failure, so ₹20,400 gone. Now offer ₹75 off for prepaid and assume it converts 150 COD orders to prepaid. Cost: 150 × ₹75 = ₹11,250. RTOs avoided: 150 × 20% = 30. Freight saved: 30 × ₹170 = ₹5,100. On freight alone the discount loses money.
It only turns positive when you add write-offs. If half of those 30 avoided RTOs would have come back unsellable at ₹400 COGS, that's another ₹6,000, taking the saving to ₹11,100 against a cost of ₹11,250. Effectively breakeven. The real reason to run it is capacity: 30 fewer parcels to repack during the week your packing table is the bottleneck. Decide on that basis, not on a vague belief that prepaid is always better.
Razorpay or your gateway of choice should have UPI intent as the first option on mobile, with the collect flow available as fallback. Test a ₹1 live transaction on the actual phone models your traffic uses. Test it again two days before Atham.
Gulf orders need their own cut-off, and their own rules
Cross-border isn't an afterthought for Kerala brands. Spices, cashew, coir, snacks, ayurveda and handloom all move to the Gulf, and a share of your Onam revenue will come from a buyer in Sharjah or Dammam. Practical things that go wrong:
- Cut-offs: an international parcel needs a cut-off roughly two weeks earlier than a Kochi-to-Kozhikode parcel. Publish both dates. Separately.
- Restricted goods: food, honey, ghee and ayurveda preparations get held at customs far more often than dry goods. Check your courier's prohibited and restricted list per destination before you list the hamper, not after a customer complains.
- Licensing: your FSSAI number belongs on the label and the invoice for food, and Ayush licensing details for ayurveda products. Importers ask. Buyers ask too, increasingly.
- Currency: Shopify Markets with AED and USD pricing removes a real friction point. A Dubai buyer seeing ₹4,180 hesitates in a way they don't at AED 182.
If you sell gold, the ten days are a pricing problem
Onam is a gold-buying occasion in Kerala, and a ten-day sale window is long enough for the spot rate to move against you. Manually updating a jewellery catalogue every morning is how stores end up selling a 22k chain below cost on day seven, or losing an order because the site shows yesterday's higher rate. The fix is to price off the live rate and show the buyer the breakup — metal weight, making charge, wastage, the 3% GST line — which is what our Gold & Silver Live Rate app was built to handle. Showing the breakup matters as much as the automation; Kerala jewellery buyers compare making charges, and a store that hides them looks like it has something to hide.
Courier cut-offs, stated as promises you can keep
Pick your cut-off dates with your courier account manager, in writing, and then subtract a day. Festive-week pickups slip. Publish per-zone dates: intra-Kerala, rest of India, Gulf. Kochi, Thrissur, Kozhikode and Thiruvananthapuram addresses will generally take a same-day or next-day promise; a Wayanad or Idukki pincode will not, and promising it anyway buys you an angry WhatsApp message on Thiruvonam morning.
One more thing that trips people up: if you're running more than one location — a Kochi warehouse and a Kozhikode outlet, say — check your Shopify shipping profiles and location priority before the sale. Multi-location fulfilment logic that has never been tested under load routes orders to the wrong shelf, and you find out when your packer says the stock isn't there.
Speed, because almost all of this traffic is a phone on mobile data
Kerala traffic is overwhelmingly mobile, often on a mid-range Android over 4G. Every festive campaign app you install between now and Atham adds script weight to the same pages your ad spend lands on. Audit before you add: a countdown timer, a popup, a bundle app, a reviews widget and a WhatsApp chat button together can add well over a second to LCP on a mid-range device, and that second gets paid for in bounce on the most expensive traffic of your year. Measure the collection page and the product page, not just the homepage. If you need the fixes done properly rather than guessed at, start there in July, not the week before.
The run sheet
- Atham (day 1) — Onam collection live. Send the first email and WhatsApp broadcast to your existing list only. No discount site-wide; hamper bundles priced as bundles. Publish all three cut-off dates.
- Day 2 — Turn on Meta and Google spend. Malayalam creative to Kerala geo, English to Gulf geo. Check site-search logs for zero-result queries and fix tags.
- Day 3 — Corporate gifting push. A simple bulk-order enquiry form with GSTIN capture converts better than trying to force forty units through a retail checkout.
- Day 4 — Restock check on hamper components. Anything with under three days of cover gets pulled from the bundle or marked as backorder-off.
- Day 5 — First real discount, on slow movers only. Not on the hero hamper.
- Day 6 — Gulf cut-off. Change the international shipping message the same hour it passes; stale promises generate refunds.
- Day 7 — Abandoned-checkout flow frequency up. Add the delivery date to the recovery email subject line.
- Day 8 — Rest-of-India cut-off. Tighten COD: cap it lower, kill it on perishables.
- Day 9 — Kerala-only messaging. "Delivered before Thiruvonam" on the homepage, and pull the Onam collection from your ad sets outside Kerala so you stop paying for traffic you can't serve.
- Thiruvonam (day 10) — Sell nothing new that needs shipping. Digital gift cards and store-pickup only. Send a Thiruvonam greeting with no offer in it. It's the highest open rate of the year and the one message people don't resent.
The day after Thiruvonam is worth more than day nine
Most Kerala stores go quiet for a week after the festival and lose the easiest repeat purchase they'll get. Two flows to build before Atham so they fire automatically:
First, a review and photo request going out four days after delivery, not on day one. Food gets eaten late; kasavu gets worn once. Ask when they have something to say.
Second, a second-purchase flow segmented by what they bought. Someone who bought a snack hamper as a gift is a different buyer from someone who bought two kilos of chips for themselves; the gifter converts on "order for yourself this time", the self-buyer on replenishment timing. Then hold that list. Vishu in April is your next real peak, and a list built in September that has heard from you four times by March converts at a rate a cold audience never will.
If you'd rather have someone look at your store's festive readiness with fresh eyes before the build freeze, a free audit takes about a week to turn around, which still leaves room to fix what it finds.