The scenario
The brand sells gourmet date boxes, stuffed dates and chocolate hampers direct to consumer through its own Shopify store, with KNET, Tabby and cash on delivery at checkout. Built by the founder herself on a standard theme, with the Arabic version added as a translation pass rather than a rebuild, the store had never been tested end to end by someone actually placing an occasion order under time pressure.
The traffic was never the problem. Instagram and Snapchat content built a following well before Ramadan each year, and the brand's dates and chocolate genuinely sold themselves once someone reached a product page. What the checkout had never been asked to do was tell a customer, in the customer's own language of governorates and prayer times, exactly when a box would land.
- Monthly revenue band
- pending client sign-off
- Average order value
- pending client sign-off
- Fulfilment
- In-house kitchen, made-to-order boxes, local courier
- Team
- Founder plus a small kitchen team, seasonal packers before Ramadan
The traffic showed up. The checkout never asked when it should arrive
The account looked healthy from a distance: Instagram click-through built steadily through Sha'ban, a product page that held attention on the stuffed dates and the seasonal hamper line, and a cart-add rate the founder was proud of. The number nobody had split out was how much of that cart-add rate survived the walk to a completed order once Ramadan and Eid traffic actually arrived, as opposed to the quieter months.
Split by week, the picture changed. Ordinary-month checkout completion looked close to what a small gifting store should expect. The four weeks before Ramadan and the week before Eid told a different story: abandonment climbed sharply, and session recordings on the checkout step showed the same hesitation over and over. Customers typed a note into the order-comments box asking for delivery on a specific day, deleted it, retyped it, and in many recordings left the page entirely rather than trust a generic "delivery within 2–4 business days" line that said nothing about whether that meant before or after the occasion.
None of this was a product problem, and no amount of extra ad spend would have touched it. The checkout had been built to process an order. It had never been built to promise a date, and a gift bought for a specific day is worthless on the wrong one.
What we did — the pages and offers we tested
The losers are here on purpose. A test with only winners was never a test.
A delivery-date and time-slot picker added to checkout
Winner"Choose the day and the window. We'll confirm it on WhatsApp." shown as a required checkout field
- Format:
- Checkout step, new required field, single-variable test against the control
This is the single change that mattered most. Customers were not undecided about the product; they were unwilling to commit money without knowing the box would land on the right day. Making the date a required field rather than an optional note removed the exact hesitation the recordings kept showing, and it converted best in the two weeks each side of Ramadan and Eid, which is where the old checkout had been losing the most.
A freshness and shelf-life line added to the product page
Winner"Made fresh and packed within 24 hours of your delivery date" shown next to the add-to-cart button
- Format:
- Product page trust badge, single-variable test
Freshness was the second most common hesitation, quiet but constant: shoppers buying dates and chocolate as a gift worry it was made weeks earlier and sitting in a warehouse. Stating the made-to-order timeline plainly, tied to the delivery date the customer had just chosen, removed a worry the brand had never known it needed to answer out loud.
The personalisation note moved from checkout to the product page
Winner"Add your card message here" shown as a visible field under the box selection, not buried in checkout notes
- Format:
- Product page field, moved earlier in the funnel
The personalisation option had always existed, buried in a checkout notes field most customers never scrolled to. Surfacing it on the product page, where the buying decision actually happens, lifted average order value slightly because customers who saw it were more likely to add a second, smaller item to go with the personalised one.
Pre-selecting the largest hamper as the default variant
LostThe premium 12-piece hamper shown pre-selected on load, smaller boxes requiring a manual change
- Format:
- Product page default-variant test
A reasonable idea that backfired. First-time buyers, who make up most of the pre-occasion traffic, felt steered rather than helped, and several session recordings showed customers switching the size down and abandoning anyway, unsettled by having to undo a choice they never made. It raised the price shown on load without raising the order value, and it cost more in trust than it gained in average order value.
A live countdown banner to the Ramadan order cut-off
Lost"Order in the next 4 hours to guarantee Ramadan delivery" shown as a sitewide banner
- Format:
- Sitewide countdown banner, tested against no banner
It increased pressure without increasing trust, which in a category already fighting a freshness and timing worry made things worse rather than better. Customers who had just been given a specific delivery-date field to fill in were then told to hurry regardless of the date they picked, and the contradiction between the two messages showed up as more, not fewer, abandoned carts in the final hour the banner counted down.
What we did — the optimizations, in order
Read the funnel by week, not as one blended rate
We split every funnel step by calendar week for a full year rather than reading one average conversion rate, so the four weeks before Ramadan and the week before Eid could be compared against the quieter months on their own terms.
Why: A yearly average had been hiding a healthy off-season funnel sitting on top of an occasion funnel that broke under its own pressure. Splitting by week is what turned a vague sense that Ramadan felt harder into a specific, measurable collapse worth fixing.
Sit through session recordings on the checkout step during peak weeks
We watched recorded sessions from the pre-Ramadan and pre-Eid weeks specifically, focused on the checkout notes field and the moments customers hesitated, rather than testing the site outside the season it actually breaks in.
Why: The typing-and-deleting loop in the notes field does not show up in analytics as a single number; it shows up as a pattern only a recorded session makes visible. This is where the real blocker — no way to name a date — was found rather than guessed at.
Fix the floor: a real delivery-date field and freshness copy
Added a required delivery-date and time-window field to checkout, stated the made-to-order freshness timeline on every product page, and put KNET, Tabby and cash-on-delivery badges on the product page rather than only at the final step.
Why: These touch every occasion order regardless of which later test wins, which is why they came first. A checkout that cannot name a date was suppressing every single campaign the paid team ran into Ramadan, no matter how good the targeting.
Run one page or offer test at a time, per template
The personalisation placement, the default hamper size and the countdown banner were each tested one at a time against the existing page, with the audience, the price and the offer held identical across the test.
Why: Running the default-size change and the countdown banner at once would have made it impossible to say which one was actually driving the extra abandonment. Testing them separately is the only reason we can say with confidence that the pre-selected size hurt trust and the banner made an unrelated problem worse.
Rebuild checkout around a promised date, not a promised window
Replaced the generic "delivery within 2–4 business days" line with a confirmed date and window chosen at checkout, echoed back on WhatsApp immediately after payment rather than left to a follow-up call.
Why: A gift bought for a specific day needs a specific promise, not a range that could land either side of it. Confirming the date immediately on WhatsApp, in writing, is what let a nervous first-time buyer actually finish paying instead of messaging the store to ask first.
Time the review request after the occasion, not after shipping
The review request moved from the shipping notification to a day or two after the confirmed delivery date, so it asks about the gift as it was received rather than the packaging alone.
Why: A review asked for the moment a box ships says nothing about whether it arrived on the day the occasion needed it to. Timing the ask to the actual delivery date is what produced reviews that spoke to the thing this brand had just fixed.
Keep a weekly test log through the season
Every test, its hypothesis, its result and the decision taken went into one shared log reviewed weekly through Ramadan, including the countdown banner that made things worse.
Why: Without a written log a small team reintroduces a countdown banner the following Ramadan because the memory of why it was removed has faded, and pays the same abandonment cost twice.
What changed
The table above carries the figures once the client signs them off, and the shape worth flagging now is that the biggest single move came from a field, not a redesign: giving the customer a way to name a date. Checkout completion moved because the uncertainty that had been showing up in every recording was answered before the customer had to ask.
The freshness line and the personalisation move mattered too, but in a smaller and steadier way, lifting the ordinary weeks as much as the peak ones. The two losing tests were worth running for what they ruled out: pre-selecting the biggest hamper confirmed that this audience wants to choose, not be steered, and the countdown banner confirmed that urgency and reassurance cannot be sold on the same page at the same time.
The clearest sign the fix worked was qualitative before it was numerical: the volume of WhatsApp messages asking "will this arrive before Ramadan" dropped, because the checkout was now answering that question for itself.
What we would do next
Take the confirmed-date pattern into the corporate quick-inquiry flow, since bulk buyers ask exactly the same question at a bigger scale and currently do it over WhatsApp with no structured way to lock a date.
Second, load the delivery-date picker with realistic capacity limits a month before Eid, so the kitchen never has to honour a date it physically cannot hit once the calendar fills up.