White Friday lands on November 27 this year. In Saudi Arabia and across the Gulf it's one of the biggest shopping moments of the year, coming right after 11.11. Salla's season calendar suggests merchants start preparing about six weeks out, which means most teams are finalising their sale screens right now.
Most of the advice merchants get is about discounts, stock and ad budgets. That's important, but sale season is also the moment when an Arabic interface is under the most pressure: more traffic, more urgency, more last-minute banners, and more ways for small RTL mistakes to cost real money. Here's the checklist I go through with e-commerce clients before the season starts.
Key takeaways
- Sale season is a UX stress test. Treat it as a product release, not just a campaign.
- Price displays break first in RTL: old and new price order, percent signs, currency and digit styles all need fixed rules.
- Urgency works when it's honest. Shoppers are sceptical of fake deals, so countdowns and stock labels must be true.
- Build bilingual banner templates in advance so campaigns can change in minutes without breaking layouts.
- Design checkout for heavy load: fast pages, clear payment options and helpful failure states.
Why sale season is a UX stress test
For most of the year, a store's interface handles a steady flow of normal shoppers. During White Friday, everything gets more extreme at once. Traffic spikes, people arrive from ads straight onto product pages, they compare prices across several apps, and they're more willing to abandon a cart the moment something feels off.
At the same time, the content changes constantly. Marketing teams push new banners, new discount labels and new countdowns, often translated in a hurry. As Khaleej Times' explainer shows, there are now several competing "Friday" sale names in the region, so even the campaign naming varies between stores. That's a lot of moving parts for a layout that was designed for calm weeks.
Prices and discounts in RTL
Prices are where I see the most mistakes. Decide these rules once, put them in the design system, and stop deciding them per banner:
- Old and new price order. In Arabic layouts, the new price should come first in reading order, which means it sits on the right, with the struck-through old price after it. Make the new price clearly larger or bolder.
- Strikethrough on mixed content. A strikethrough must cover the whole old price, including the currency. Test it with the currency symbol or abbreviation you actually use, because some glyphs sit higher or lower than digits.
- Percent badges. "خصم 30%" and "30% off" need fixed patterns. Decide where the percent sign goes and whether you use Western or Arabic-Indic digits, and keep it consistent with the rest of the app.
- Currency. Symbol, ISO code or Arabic abbreviation? I covered this in detail in my post on the new GCC currency symbols. Pick one per context and don't switch mid-campaign.
- Digit consistency. Don't mix digit styles on the same card. A price in Western digits next to a discount in Arabic-Indic digits looks like a mistake, and shoppers read mistakes as risk.
Urgency without dark patterns
Countdowns and "only 3 left" labels work, which is exactly why they get abused. Gulf shoppers have seen enough inflated "original" prices and fake timers to be sceptical. In my experience, trust is the main thing a sale page has to protect.
A few rules I recommend:
- Countdowns must be real. If the timer resets on refresh, someone will notice and share a screenshot.
- Stock indicators should reflect real stock and update when it changes.
- Show where the old price came from when possible, for example "price before the sale" rather than an unexplained crossed-out number.
- Label deal types clearly: a percentage discount, a bundle and a free-shipping offer are different things. Don't make shoppers work it out at checkout.
- Countdown direction and format in RTL. Hours, minutes and seconds should read correctly in Arabic, and the units should be labelled if the timer is small.
Dates deserve a mention too. If your audience uses both Hijri and Gregorian calendars, decide which one the campaign end date uses and show it consistently.
Bilingual banners and campaign templates
The fastest way to break a store during sale season is a hand-made banner in two languages. The Arabic headline is longer, the English one gets cut off, the image subject ends up under the text, or the "Shop now" button points the wrong way.
Before the season starts, build a small set of banner templates with:
- Text areas sized for the longer of the two languages
- Image safe zones that work in both mirrored and non-mirrored layouts
- Fixed slots for discount badges, dates and calls to action
- Arabic type styles from the design system, not whatever font is on the marketer's laptop. See Arabic typography for UI for what to pick.
Then the marketing team can change a campaign in minutes, in both languages, without asking a designer to fix it at midnight.
[Waleed: add an example of a bilingual sale banner template from a client project, with branding removed.]
Checkout under load
All of this is wasted if checkout fails. Pattern's write-up on peak season in the UAE makes the business case for preparing early. From a design point of view, I focus on:
- Speed. Heavy hero images and autoplay video on sale pages slow everything down. Keep sale pages lighter than usual, not heavier.
- Payment options up front. Show supported methods (cards, wallets, instalments, cash on delivery where offered) before the last step, so nobody fills in a form only to find their method isn't supported.
- Clear failure states. If a payment fails or an item sells out during checkout, tell the shopper what happened in plain Arabic and what to do next. Keep their cart.
- Address and phone fields that accept local formats, including Arabic input, without throwing errors.
A one-page pre-White Friday checklist
- Price, discount and currency rules are documented and used everywhere.
- Strikethrough prices tested with real currency glyphs in both languages.
- Digit style is consistent on every card and banner.
- Countdowns, stock labels and "original" prices are real and verifiable.
- Campaign dates use one calendar consistently.
- Bilingual banner templates are built and tested with the longest copy.
- Sale pages are lighter than normal pages, not heavier.
- Payment methods are visible before checkout.
- Sold-out and payment-failure states are designed and tested.
- Someone owns RTL QA for every new banner during the campaign.
Closing thoughts
White Friday rewards stores that feel trustworthy and easy, not just cheap. Most of the work happens weeks before the sale: fixed rules for prices, honest urgency, templates that survive two languages, and a checkout that holds up under pressure. Do it now and the campaign team can focus on deals instead of fixing broken banners on the night.
Sources: White Friday 2026 season calendar (Salla), Black, White, Yellow, Green Friday sales explained (Khaleej Times), Peak season power: Singles' Day and White Friday in the UAE (Pattern).
FAQs
How should sale prices be shown in an Arabic app?
Put the new price first in reading order (on the right) and make it more prominent, with the old price struck through after it. Keep currency and digit styles consistent.
Are countdown timers a dark pattern?
Not if they're real. A timer that reflects a genuine deadline is useful information. A timer that resets or invents urgency damages trust.
When should a store start preparing its White Friday UX?
About six weeks before the sale, which leaves time to fix price rules, build banner templates and test checkout under load.