Hijri vs Gregorian Dates: What to Show on a GCC Store

Gulf stores run on the Gregorian calendar. Orders, invoices and delivery dates all use it, in Saudi Arabia as much as in the UAE.

The Hijri calendar still matters, though. It decides when Ramadan and Eid start, and Saudi shoppers notice when a brand gets it right.

So here's the rule: Gregorian for commerce, Hijri as a seasonal touch. This page shows where each one goes, how to code it and how to stop the moon from breaking your sale dates.

Which calendar goes where?

Gregorian is the default for every transaction. Saudi Arabia moved government salaries to the Gregorian calendar in 2016 and kept Hijri for religious use.

Hijri earns a place where the season is religious:

For example, a Ramadan banner might read "رمضان كريم · 1448 هـ" with the Gregorian dates of the offer underneath. The offer still ends on a Gregorian date, because that's what your checkout and reports understand.

Our cultural localization guide covers the wider calendar, from weekends to national days. More Arabic-store guides live in our localization hub.

Umm al-Qura vs tabular Hijri calendars

There's more than one Hijri calendar. Use Umm al-Qura, Saudi Arabia's official calculated calendar. It's what Saudi shoppers see on their phones, in government apps and on ummulqura.org.sa.

The other common option is the tabular (or "civil") calendar. It uses a fixed pattern of 29- and 30-day months, so it's easy to compute.

The catch? It can drift a day away from Umm al-Qura.

A one-day slip on a Ramadan countdown looks careless. So name the calendar in your code instead of trusting a default.

How to show Hijri dates in code

JavaScript's built-in Intl.DateTimeFormat handles Umm al-Qura with no library. Add the calendar and the digits to the locale tag:

const d = new Date("2026-10-26T12:00:00Z");
// Hijri, Umm al-Qura, Western digits
new Intl.DateTimeFormat(
  "ar-SA-u-ca-islamic-umalqura-nu-latn",
  { day: "numeric", month: "long", year: "numeric" }
).format(d);
// "15 جمادى الأولى 1448 هـ"
// Gregorian Arabic, Gulf month names
new Intl.DateTimeFormat(
  "ar-SA-u-ca-gregory-nu-latn",
  { day: "numeric", month: "long", year: "numeric" }
).format(d);
// "26 أكتوبر 2026"

Two parts of that tag do the work:

• ca-islamic-umalqura picks the Saudi calendar. Avoid plain islamic and islamic-civil, which are approximations. In Node 22, plain islamic returns 16 Jumada al-Ula for the same day.
• nu-latn forces Western digits, so dates match your prices. Our Arabic numerals guide explains why that matters.

On Shopify, Salla or Zid, look for a date format setting first. Then test an order confirmation email in Arabic, because emails often ignore the storefront setting.

Date format and month names

Gulf shoppers read dates day first. Write 26/10/2026, never 10/26/2026, in both Arabic and English.

When you spell the month out, use the Gulf names: يناير، فبراير، مارس … أكتوبر. The Levantine names, like كانون الثاني or تشرين الأول, are correct Arabic but look foreign in Riyadh and Dubai.

This bug is easy to ship by accident. Format with a Levantine locale such as ar-SY and October comes out as تشرين الأول. Stick to ar-SA or ar-AE and you'll get أكتوبر.

Want the whole Arabic layout right, not just dates? Our RTL design guide covers date pickers, forms and mirroring.

Invoices, ZATCA and delivery dates

Keep invoices on Gregorian dates. ZATCA requires a QR code on every simplified (B2C) tax invoice. That code holds the seller's name, VAT number, invoice date and time, total and VAT (ZATCA Phase One FAQ).

Your e-invoicing system fills in the timestamp, so never type a Hijri date into an invoice field.

You can print a Hijri date as a decorative line on a Ramadan receipt. Keep it outside the official invoice data. The ZATCA e-invoicing guide covers the rest of the rules.

Delivery dates need the most care, because they're a promise:

• Show the weekday. "Sunday 1 November" is easier to plan around than a bare date, and it reminds shoppers when the weekend falls.
• Give a range for longer routes. "Arrives 3–5 Nov" beats a single date you might miss.
• Plan for Eid pauses. Many couriers slow down or stop for 2–4 days over each Eid, so publish an "order by" date well before it.

Moon sighting: build a buffer into sale dates

Umm al-Qura is calculated in advance. Ramadan and Eid aren't. They start when the new moon is sighted, so the official date can move by about a day, and it can differ between countries.

That matters for anything you promise. An "Eid sale ends 9 March" banner is fine. "Delivered before Eid, guaranteed" is risky until the announcement comes.

Worked example: an Eid gift campaign

Say you sell perfume gift sets from a Riyadh warehouse, and Eid al-Fitr is expected on Tuesday 9 March 2027. Here's how the dates fall into place:

1

Set the landing page header

Write "عيد مبارك · شوال 1448 هـ" in Arabic, with the Gregorian offer dates in smaller text underneath.

2

Pick the order-by date

Couriers in Riyadh need 1–2 days, and some pause for Eid. Choose Thursday 4 March and label it in both calendars.

3

Schedule the sale end

End the sale on Wednesday 10 March, one day after the expected Eid, so a late sighting doesn't cut it short.

4

Prepare a backup banner

Draft a "we're open during Eid" message for the day the moon is announced, whichever day it is.

Nothing on that plan breaks if Eid moves by a day. Plan the full season, with prep deadlines, in our GCC ecommerce calendar.

Notes for UAE stores

The UAE follows the same pattern as Saudi Arabia: Gregorian for business, Hijri for religious seasons. A few details differ:

• Moon sighting is announced by the UAE's own committee. Eid can fall on a different day from Saudi Arabia, so check both if you sell in both.
• English pages carry more weight in the UAE. A Ramadan banner there often reads "Ramadan Kareem" with no Hijri year, and that's fine.
• The weekend is Saturday–Sunday, so "Sat 6 Mar" isn't a working day for most couriers.

Notes for developers

A few traps show up again and again in GCC builds:

• Time zones. Saudi Arabia is UTC+3 and the UAE is UTC+4. Format order dates in the shopper's zone, or a late-night order shows tomorrow's date.
• Server vs browser. Node and browsers ship different ICU data versions, so render dates in one place. Mismatched output also causes React hydration warnings.
• Store dates as ISO. Save every date as Gregorian ISO (2026-10-26) and convert to Hijri only for display.

Your date checklist

Want a team to localize your store for you? Our Shopify localization service handles dates, digits, RTL and Arabic copy in one pass.