SitecoreAI for retail peak seasons: Ramadan, Eid and White Friday

13 September 2026
Arcsen

Retail in the Gulf and Egypt runs to a calendar that moves. Ramadan, Eid al-Fitr and Eid al-Adha follow the lunar calendar, so they arrive earlier each Gregorian year, and national days and White Friday bring their own campaigns, often in several markets at once. Each peak needs campaign pages in Arabic and English, live from the first minute, approved by marketing, legal and the commerce team, and fast when traffic is at its highest.

Most peak problems are operational: pages built in the final week, translations finished the night before, prices typed into banners, and a site that slows at the worst moment. SitecoreAI (formerly XM Cloud) has the tools to run peaks well, when the operation is designed around them.

Build the peak calendar, then schedule the pages

Start with one calendar for every market: each peak’s start and end, the campaign phases inside it, the content freeze, and who approves what. Ramadan campaigns change through the month, and in many markets the first day of Eid is confirmed by moon sighting, so prepare a version for each phase and a way to switch at short notice.

Page builder can schedule a page version to be available, or unavailable, from a start date to an optional end date, and only one version of an item can be on Experience Edge at a time. Sitecore says you must still publish the page or the site manually to make sure the right version is live when each date starts, and that the site may take a while to update, depending on your rendering strategy.

So someone has to publish at each changeover, at midnight if that is when the offer starts. Name that person, or automate the step: the Authoring and Management GraphQL API has a publishItem operation that publishes items to Experience Edge in the languages you list, which a scheduled job can call at the minute a phase begins. For banners and images in the legacy Media Library, embargo dates, added in July 2026, make published assets become available at the scheduled date and time wherever they are used.

Stage	Content work	In SitecoreAI	Who signs off
Plan	Calendar by market and phase, offers agreed with commerce	Sites and languages for each market	Marketing and commerce
Build	Pages, banners and components, a version per phase	Page builder versions and personalized variants	Brand
Translate	Arabic and English copy, read by native speakers	AI translation guided by the brand kit, starting in Draft	A native reviewer for each language
Approve	Offers, prices shown and terms checked	Workflow states and commands, with Language Write for reviewers	Legal and marketing
Schedule	Start and end of each phase in each market	Scheduled versions, media embargoes, a publish job	The person on duty
Run	Fixes and sold-out offers on a short path	A fast workflow route, then publish and check the live page	The approver on duty
Close	Offers taken down, results recorded	Unavailable versions, and variant results beside the original	Marketing

Personalization by market and language

Retailers here usually run a site or section per market, in Arabic and English. Language is a version of each item and is absent from the personalization conditions, so use personalization for timing and place.

Page builder personalization audiences can use Date conditions (specific dates, months, and days of the week or of the month), Time conditions (times of day), Geography (country, region or state) and User interaction, such as the referrer or UTM parameters that brought a visitor. Point of sale targets visitors to any of your sites that share one site identifier. One Ramadan page can then show evening offers after iftar, an Eid message in its final days and a different hero in Saudi Arabia and the UAE, each as a variant of the same page. Check which time zone each condition uses in each market.

Each variant has its own performance dashboard, side by side with the original, which gives you evidence for next year’s plan. Sitecore states a 30/60-day data retention for Page builder, so export results after each peak. Personalization relies on cookies to recognize visitors, so align it with your consent banner in both languages.

Arabic right-to-left, and AI with approval

Right-to-left layout is the front end’s job. SitecoreAI stores the Arabic version, and the components, styles and fonts that mirror each page come from your application. Sitecore’s AI translation page does not mention Arabic or right-to-left text, so test every campaign component in Arabic before the peak: carousels, countdowns, discount badges, mixed Arabic and English product names, and numerals.

AI translation creates language versions of a page and its data sources, guided by the site’s brand kit, so put campaign names, product terms and the brand’s Arabic voice in the brand kit first. A translated item starts in the initial workflow state, typically Draft, and Sitecore recommends leaving Keep workflow state unchecked, so each translation waits for review. Translators need Write and Language Write rights, and Language Write controls who can edit each language version, so an Arabic reviewer can work on Arabic alone.

Sitecore launched Agentic Studio with SitecoreAI and 20 AI-powered agents. Since July 2026, its chat shows AI-proposed changes for review before anything is saved: users can compare current and proposed values, edit suggestions, skip changes or decline the request. Treat that as the author’s own check. Approval belongs in the workflow, so confirm in a test environment that items changed by agents enter it like any other edit.

Rehearse the changeover. Before each peak, run it in a test environment: schedule a version, run the publish job, release a banner by embargo, and time how long the live page takes to change in each market and language. Fix what is slow while there is still time.

Performance when traffic peaks

SitecoreAI keeps editing and delivery apart. Experience Edge is a GraphQL service for layout and content, distributed through a CDN and hosted by Sitecore, and your front end runs on Vercel, Netlify or another host. The limit to plan around is the Delivery GraphQL API’s rate limit of 80 requests per second, above which Experience Edge returns a 429 error. A front end that asks Edge for content on every page view will meet that limit on the busiest day.

Pre-render campaign pages, cache them at the host, and refresh each page when it is published, using SitecoreAI webhooks to tell the front end. Sitecore notes that bandwidth and storage limits may apply depending on your contract, so check them. Keep campaign video on a streaming service, since Edge caps a media item at 50 MB, and load-test the whole path, including the commerce APIs each page calls.

Where SitecoreAI sits next to the commerce platform

Experience Edge publishes a static snapshot of each item at publishing time and does not support contextual or dynamic output. That settles the split. Prices, stock, promotions, the basket and checkout stay in the commerce platform, and the front end fetches them when the page renders. SitecoreAI holds what marketing writes: campaign pages, hero banners, gift guides, FAQs and terms, in every language.

Link the two with stable references. Content points to a product, category or promotion ID, and the front end fetches the live price and stock for it. Never type a price or a discount into a banner, because it will stay there until someone republishes it. Give prices and stock a short cache and content a long one, and write an approved fallback, in both languages, for the moment a commerce API slows down.

Where to start

Draw the peak calendar for every market for the year ahead, with phases, freezes and approvers.
Agree with the commerce team which data the front end fetches live and which content SitecoreAI holds.
Build the brand kit and the Arabic and English review workflow, and test AI translation on last year’s campaign.
Automate the publish at each changeover, and rehearse it.
On XM Cloud or Sitecore XP? See what changed in SitecoreAI and what a move brings, and plan upgrades away from peak dates.

Planning your next peak on SitecoreAI? See our retail and distribution work and our retail and distribution outlook, start with the free Sitecore Health Check, or talk to our retail and distribution team. Our Sitecore practice delivers in Arabic and English.

Frequently asked questions

Can SitecoreAI publish a campaign page at a set time?

Page builder can schedule when a version is available, and Sitecore says you must still publish the page or site when each date starts. Automate that publish through the Authoring and Management GraphQL API, or name a person on duty.

Can SitecoreAI show different offers in different countries?

Yes. Page builder personalization can target visitors by country, region or state, by date and time of day, and by the referrer or UTM that brought them, and shows each variant’s results beside the original.

Does SitecoreAI support Arabic campaign sites?

Arabic can be a language version of every item, with AI translation guided by the brand kit and review in the workflow. Right-to-left layout is built in the front-end application, so test campaign components in Arabic before each peak.

Will a SitecoreAI site cope with White Friday traffic?

Yes, when the front end is built for it. Experience Edge delivers through a CDN, and its Delivery GraphQL API has a rate limit of 80 requests per second, so pre-render and cache pages at the host and refresh them on publish.