If you are selling Christmas cake online from a Kerala bakery, the date that decides your whole season is not 25 December. It is roughly 8 December, because that is when a rum-soaked plum cake has to leave Kochi if it is going to reach a flat in Sharjah before Christmas Eve. Everything else on the Shopify build, the preorder mechanics, the batch dates, the labelling, the local delivery radius, hangs off that one cutoff and the domestic one two weeks behind it. Get the dates wrong and you will spend the last week of December refunding Gulf customers while your kitchen still has unsold stock.
Preorders for the season open around mid-November in most Kerala bakeries. So the store needs to be ready by the first week of that month, not the last.
Count backwards from 25 December before you touch the store
Write the calendar on paper first. A worked version for a bakery in Ernakulam:
- 24 December, 12 noon — last Kochi local delivery and in-store pickup slot. Drivers need the afternoon.
- 21 December — last intra-Kerala courier dispatch. Two days of transit, one day of buffer for a missed scan.
- 15 December — last dispatch to the rest of India. Delhi and the Northeast are five to seven days in the third week of December, not the three days the rate card promises.
- 8 December — last dispatch to the GCC. Air courier transit of three to six days, plus customs clearance at the destination, plus last-mile. Then subtract four more days because December is the worst month of the year to assume a clean clearance.
That gap is the thing merchants underestimate. Your Gulf cutoff lands roughly a fortnight before your domestic one, and if you advertise a single "order by 20 December" line on the homepage, every NRI who reads it will order a cake that cannot arrive. The storefront has to show different cutoffs to different buyers, which means the cutoff cannot live in a banner. It has to live in the product.
Shopify preorder setup for a bakery that bakes in batches
The temptation is to switch on "continue selling when out of stock" and call it a preorder. Do not. That setting removes your only hard cap, and a bakery's cap is physical: the oven. If you can bake 160 half-kilo cakes a day and you have 28 baking days before Christmas, your season total is 4,480 cakes. Sell 5,000 and you are buying cake from a competitor at retail to cover the gap.
The mechanic that works is to make the dispatch window a variant, and let Shopify's own inventory counter do the enforcement.
One product, Christmas Plum Cake 500g. Variants named by dispatch week: Dispatch 25–30 Nov, Dispatch 1–6 Dec, Dispatch 8–13 Dec, and so on. Each variant gets an inventory quantity equal to what that week's bake can actually produce, minus what you are holding back for walk-ins. When a week sells out, Shopify greys it out without you doing anything. When a cutoff passes, you set that variant's quantity to zero and it disappears from the picker. No app, no script, no checkout rule.
For the Gulf, run a separate product entirely. Different variants, earlier cutoff, alcohol-free recipe, different shipping profile. Trying to serve both audiences from one product forces you into conditional logic that breaks the first time someone changes their shipping country at checkout. Two products is uglier in the admin and far safer in practice.
A few things we get asked every year:
- Take prepayment. COD on a preorder is a bad trade. You have bought dry fruit, cashew and butter against that order six weeks in advance. Razorpay with UPI covers almost everything domestic, and UPI has effectively killed the COD argument for a ₹900 cake in Kerala. Keep COD for same-week local delivery if you must, not for November bookings.
- Cap the order quantity. Corporate gifting enquiries will try to buy 200 units through the retail checkout and wreck your week-by-week allocation. Set a per-order limit and point bulk buyers at an enquiry form.
- The launch email is a load test. Preorder day sends your entire list to one product page at once, a lot of it from Gulf mobile data. If that page carries a date-picker app, two review widgets and an unoptimised hero image, the slowest visitors give up. Worth running a PageSpeed check and cleanup in the first week of November rather than the first week of December.
FSSAI labelling requirements for online food sales
The licence number on the tin is not enough. For food sold through e-commerce, the mandatory label information has to appear on the listing itself, before the customer pays. On a Shopify product page that means the description, or better, a set of metafields rendered into a consistent block so every product looks the same and nothing gets forgotten.
What goes in that block: your FSSAI licence number and the name and address of the food business operator, the full ingredient list in descending order of weight, the allergen declaration (wheat, milk, egg, tree nuts, and the alcohol if there is any), net quantity, nutritional information per 100g, the veg or non-veg mark, date of manufacture or packing, and best before.
Two things catch Kerala bakeries out. First, a cake made with egg carries the brown non-vegetarian mark, not the green one, and a surprising number of storefronts show the wrong symbol on a product photo. Second, FSSAI's direction for e-commerce operators requires that food reaching the customer still has a meaningful chunk of shelf life left at delivery, measured as a proportion of total shelf life or a minimum number of days. Check the current wording with whoever handles your licence, because it directly constrains how early you are allowed to bake for a late-December dispatch.
Shelf life and batch dates in Shopify inventory
Shopify has no expiry date field. It was built for t-shirts. You have two honest options.
For most bakeries, product metafields are enough: bake_date and best_before on each dispatch-week variant, rendered on the product page and pulled into the packing slip. Because your variants are already split by dispatch window, the batch and the variant are the same thing, which is the quiet reason that structure is worth the extra admin work.
Here is why the dates have to be visible. A rum plum cake with a 60-day shelf life baked on 20 November is good until 19 January. Dispatched to Dubai on 8 December, cleared and delivered on 16 December, the customer has 34 days left. That is a defensible number and you can print it. The same cake baked on 2 November and sitting in a hot storeroom is not, and if someone photographs the tin and posts it, you will spend more on the reply than you made on the order.
The second option, proper lot tracking with an inventory app or a small WMS, is worth it above a few thousand units a season or if you supply retail counters as well as online. Below that, a spreadsheet of bake dates against variant names beats a ₹4,000-a-month app that nobody in the kitchen will update.
Shipping food from Kerala to the UAE on Shopify
Start with the recipe, not the courier. Traditional Kerala plum cake is soaked in rum or brandy, and alcohol in a food consignment entering the UAE, and far more strictly Saudi Arabia, is a reason to have the box held or destroyed. We tell every bakery with Gulf demand to bake a separate alcohol-free batch and to list it as a distinct product with the substitution stated plainly. Customers accept it. A seized consignment they do not.
Then the paperwork on the India side. For commercial export you need an IEC from DGFT. Exports are zero-rated under GST, which you can claim either by filing a Letter of Undertaking and shipping without paying IGST, or by paying and claiming the refund. For small e-commerce parcels the Courier Shipping Bill route (CSB-V) through an authorised courier is the normal path, and it is what gives you proof of export for the GST claim. Your CA will sort this in a week if you ask in October. In the second week of December they will not.
On the Shopify side, build a shipping profile that contains only the Gulf products, with the GCC zone and flat rates per weight band. Keep that profile separate from everything else so that when 8 December passes you are switching off one thing, not auditing every rate in the store.
Expect the freight to look absurd next to the product. If your courier quotes ₹2,100 for a 2 kg box to Dubai and the cake retails at ₹1,250, shipping is 168% of the item. The fix is to stop selling single cakes abroad. A Gulf-only bundle of three cakes plus a tin of achappam at ₹4,400 carries the same ₹2,100 freight, which drops shipping to 48% of order value and gets the customer to a number they will actually pay. Price the bundle, hide the single.
Packaging a perishable so it survives an Indian courier network
Assume the box will be dropped, stacked under something heavier, and left in a van in Kozhikode at 34 degrees. Dense fruit cake handles this better than almost anything else you could ship, which is lucky, because the rest of your December menu does not.
- Food-grade butter paper, then cling film, then a tin or rigid board box. The cling layer is what stops the cake drying out across a week of transit.
- An outer corrugated carton with at least 25mm of void fill on every side. Tins arrive dented without it, and a dented tin reads as a damaged cake even when the cake is fine.
- Nothing with cream, fresh fruit or ganache goes on a courier. Those are local delivery and pickup only. Say so on the product page instead of fielding the question forty times.
- Print the batch and best-before on a label, not a sticker someone writes by hand at 11pm. Handwriting is what an inspector looks at twice.
Local delivery and pickup around Kochi
Shopify's built-in Local Delivery is genuinely good and costs nothing extra. Set it on the bakery's location with a delivery radius or a pincode list, add a minimum order value so you are not sending a rider to Aluva for one ₹400 cake, and switch on Local Pickup alongside it. Buyers in Kakkanad, Edappally, Vyttila and Fort Kochi will take delivery; people driving in from Thrissur or Alappuzha will take pickup if you offer it.
Add a delivery date and slot selector. Through December the slot is the product you are really selling, and a customer who picked "24 Dec, 9am–12pm" himself does not call you on the 23rd to ask where the cake is. Cap each slot to what one rider can actually do in three hours, which in Kochi traffic in Christmas week is fewer stops than you think.
If you are building this for the first time and want it tested against a real season rather than a demo catalogue, our Kochi team does this setup most Novembers.
Multi-currency pricing when half your buyers are in the Gulf
Here is the constraint nobody mentions until checkout breaks: Shopify's true local-currency checkout runs on Shopify Payments, and Shopify Payments is not available to Indian merchants. You are settling in rupees through Razorpay, PayU or Cashfree. Which means the AED or USD price a Gulf customer sees is a display conversion, and the actual card charge arrives in INR with a cross-border fee from their issuer.
That is fine, as long as you are honest about it. Show the converted price prominently, show the INR amount next to it in smaller type, and put one line near the buy button saying the charge will appear in rupees. The alternative, a customer in Abu Dhabi seeing AED 55 and then an unexplained dirham amount on his statement, generates a chargeback every single season.
On the conversion itself, pick a rate with headroom and round up. If the spot rate is ₹23 to the dirham, a ₹1,250 cake converts to AED 54.35. Price it at AED 58. The extra covers a week of currency drift and the gateway's international transaction fee, and nobody in the Gulf has ever abandoned a cart over three dirhams. Make sure international card acceptance is actually activated on your gateway account before you launch, not discovered on preorder day. That approval is not instant.
The week it all goes wrong, and what to do about it
Something will slip. A batch underproofs, a courier's Gulf service suspends for two days, a bulk order lands on the 18th. Build two releases of slack into the calendar: hold back about 10% of each week's bake as unallocated stock, and keep one "Dispatch 20–22 Dec, Kerala only" variant unpublished until you know your position on the 17th. Publish it if you have capacity, delete it if you do not.
And put the cutoffs where people read them. On the product page above the buy button, in the cart, in the order confirmation email, and in the WhatsApp broadcast. Not in a sitewide announcement bar that says one date for everyone.
If the preorder flow is the part you are unsure about, build the variant structure first and get it reviewed before you open bookings. We run a free look at the store setup if you want a second pair of eyes on it: request an audit, or talk to the team that handles Shopify builds across Kerala about the November window.