Arabic menus and receipts across dialects: Jordan, Gulf, Egypt

Which words should change between Jordan, the Gulf and Egypt?

Keep the working language plain. Modern Standard Arabic suits headings such as الكمية (quantity) and الإجمالي (total). Dish names need more local judgement. A familiar spoken name can help someone order, but it should not hide what the kitchen actually serves.

These are editing cues, not rules for every speaker. Give a reader from the target city the proposed dish name without its description and ask which ingredients they expect. Compare their answer with your recipe before approving the wording.

Put personality in descriptions, not critical instructions. بدون بصل means no onion without requiring a joke or regional expression. Ingredient exclusions should remain short and explicit wherever you sell.

How should Arabic and English share a menu or receipt?

Arabic runs right to left; English runs left to right. A shared line needs explicit direction settings to keep punctuation beside its label. For an Arabic-first menu, put the Arabic item name on its own line and the English equivalent beneath it. Keep prices in a separate, aligned column.

• Keep the item and its modifiers together. Place بدون بصل directly under the relevant dish, with “No onion” beneath if the ticket is bilingual.
• Translate the meaning, not the sound alone. “Grilled chicken” tells an English reader more than a transliteration of دجاج مشوي.
• Keep quantity and price in distinct, consistently aligned positions. Do not rely on a slash between languages to separate financial information.
• Test the longest actual item name. A short burger label will not reveal how a stuffed sandwich with several modifiers wraps.

A guest receipt and a kitchen ticket serve different readers. Guests need recognisable purchases and a clear total. Cooks need the item and preparation changes where they can see them. Do not shrink all the text to make a promotional message fit.

Nexara supports Arabic and English on the same ticket, with a visual template builder for receipts and kitchen tickets. Templates can be assigned per printer. That lets you assess the actual output for each station rather than assuming a customer receipt also works in the kitchen.

Which numerals, prices and currency labels should you use?

Choose one numeral style per document and apply it consistently to quantities and money. Western digits, 0 to 9, can be used on both language lines of a bilingual layout. Arabic-Indic digits are also used across the region. Ask local readers to check the format instead of treating one choice as universal.

In this illustrative Jordanian example, a dish at JOD 6.500 with quantity 2 has a line amount of JOD 13.000 before any separate charges or discounts. Label the unit price and line amount distinctly. The guest should not have to guess whether the amount covers one dish or both.

JOD uses three decimal places in its standard minor-unit convention. SAR, AED and EGP use two. Match your price format to the currency and approved billing practice, and make rounding consistent between the menu and receipt. Check tax treatment separately with your accountant.

دينار alone is ambiguous outside Jordan, and ريال alone does not identify every Gulf currency. ISO currency codes such as JOD, SAR, AED and EGP are clearer for cross-border readers. If you use a local currency symbol, test its glyph on paper. Correct Arabic letters do not prove that a newly introduced symbol will render.

State whether menu prices include applicable tax or other charges, using wording checked for that jurisdiction. Never assume an Arabic receipt is automatically a legally valid tax invoice. Nexara does not offer JoFotara e-invoicing in Jordan or ZATCA certification in Saudi Arabia today.

How does Nexara print Arabic on thermal printers?

A printer can print English correctly and still break Arabic. Arabic letters change shape according to their position in a word. Without suitable Arabic font and encoding support, raw text sent to a printer can produce disconnected letters.

Nexara avoids depending on the printer's built-in Arabic font. Its desktop print agent reshapes Arabic text, renders it into an image and sends the raster image to the printer. English can appear on the same ticket. You still need to approve the wording before printing it.

Nexara supports standard ESC/POS thermal printers, including compatible Epson, Star and Bixolon models, connected by USB or network through the Windows print agent. It does not support every thermal printer: Bluetooth printing is not supported. Confirm your printer's protocol and connection, then test the exact model and paper width.

A successful test means more than connected letters. Inspect clipping at the paper edge and the position of English beside Arabic. Check that a modifier remains attached to its item after wrapping. Use your real menu wording, including any symbols you intend to publish.

The guide to fixing unreadable Arabic thermal receipts explains the printing problem in more detail. Nexara is the order and operations layer beside the till. Printing legible text is one part of that work, not a substitute for approving the recipe wording or invoice format.

How do you keep local wording consistent across channels?

Maintain an approved wording sheet before editing live menus. Give each product a stable reference, then record its Arabic name, English equivalent, allowed modifiers and ingredient description. Regional wording should refer back to the same recipe unless you intentionally change the dish.

Nexara provides products, categories and modifier groups in one catalogue, with per-branch availability and menu channels that control which menu a channel sees. It also supports catalogue pushes to Talabat and Careem. These Nexara menu and operations features manage catalogue content; they do not automatically translate dialects.

Check each channel after an edit. A name that fits your ordering website may wrap differently on an aggregator listing or receipt. The guide to keeping one menu across channels covers the shared-catalogue approach.

For a Gulf or Egyptian rollout, distinguish language readiness from market activation. Nexara's dashboard and storefront support Arabic and English, but live deployments today are in Jordan. Talabat and Careem activation is per market and subject to partner approval: ask about activation in your market.

What should you test before publishing?

1. Have a local reader match each dish name to its recipe. Resolve names that suggest a different ingredient or preparation.
2. Place a test order with your longest item name and a preparation exclusion. Inspect the website confirmation and printed ticket.
3. Check quantity, unit price and line total independently. Confirm that the currency label stays beside the correct amount.
4. Print both the guest receipt and kitchen ticket on the actual printers. Read them at the counter and at the preparation station.
5. Have your accountant review the tax-invoice wording and required fields for the destination country. Record any requirements your invoicing system must handle separately.

Send a bilingual menu sample through the WhatsApp contact below, including your target country and printer model. The Nexara team at nexaratech.io can review printing fit and discuss market activation before you commit.