One menu across every channel: change a price once

What does one menu across every channel actually mean?

Keep each product record in Nexara's Products & Menus catalogue. Menu Lists and the visual Menu Builder organise it, while menu-channel settings control which channel sees which menu.

You can deliberately show a different selection for tables than for delivery. Set that selection through menu-channel settings so each channel shows the menu you intended, with product information maintained centrally.

Nexara's branded ordering website is generated from the menu. Customers install that same storefront as an app from their browser, keeping website and app maintenance together. Table QR ordering is another supported channel. Nexara sits beside your till as the order and operations layer.

The restaurant ordering website guide explains the storefront setup. The Nexara feature overview covers menu management alongside the order board and printing.

How should you organise categories, modifiers and sizes?

Start with what the kitchen actually sells. Nexara supports products, categories, modifiers and modifier groups. A category organises the menu; a modifier describes a choice attached to an item. Put sauce choices together in a modifier group so customers can select them under the product.

During the demonstration, select each size of an item and add the same paid extra. Compare the extra charge and final total with your menu. If the extra costs differently by size, ask the team to show how products and modifier groups handle that exact combination before agreeing on the setup.

Arabic and English deserve a kitchen check, too. Nexara supports a bilingual dashboard and storefront, and Arabic item and modifier names on kitchen tickets. Write and review both names during setup, then have the person preparing the food read them.

How does menu availability per branch work?

Sold out at one branch? Change that branch's availability. Nexara supports per-branch availability, so an item can stay on sale at other locations without deleting or recreating the product.

Channel visibility answers a different question: should this menu appear on this ordering channel? Branch availability answers whether this location can sell the product. Keep these decisions separate when you train managers. A delivery-only selection and a local sell-out need different controls.

Nexara supports branch inventory, recipes and inventory counts. When an ingredient runs out, have the branch check which dishes it can still prepare and update product availability by hand. Use the restaurant morning inventory count guide to connect the opening count with that availability check.

Nexara's live deployments are in Jordan today. For your branches in Amman or elsewhere in the country, assign responsibility for marking items unavailable and restoring them after replenishment. Before reopening an item, confirm the kitchen can prepare it with every choice still shown to customers. The multi-branch restaurant management guide covers branch assignments and shared operations.

What syncs to Talabat and Careem?

Nexara can retrieve and publish the Talabat catalogue. For Careem food orders, it can publish the catalogue, opening hours and availability, and pause the store. Receiving orders and publishing menu changes are separate tasks, so include both when planning your provider setup.

The branch connection matters when locations sell the same dishes. Matching each Nexara branch to its provider outlet directs menu publishing to the intended restaurant listing. Item matching serves the same purpose for products: the dish you edit must correspond to the dish sold by that provider.

Careem Express handles delivery dispatch for your own orders; Careem food-order catalogue publishing manages your menu on Careem. The Talabat and Careem order intake and catalogue integrations page explains these connections.

How do you update a menu without leaving old prices behind?

Edit the central product, then verify the menus your customers use before the next service. Nexara provides the shared catalogue and channel controls. Follow this procedure to cover the displayed price, paid extras and the order received by the kitchen.

1. Find the product in Products & Menus. Check its category and attached modifier groups before editing.
2. Read the Arabic and English names beside each other. Correct any mismatch in portion size or preparation.
3. Change the central price. Check whether any paid extras also need a price change.
4. Check the intended menu channels and branch availability. Keep sold-out items unavailable while changing their prices.
5. Open the website and installed storefront app, then scan a table QR where enabled. Select the item, add its extras and check the total.
6. For connected aggregators, confirm that each item and branch matches the correct Talabat listing, and that the intended Careem location is connected. Publish the catalogue changes, then open each provider's customer-facing menu and check the price and available choices.
7. Place a test order through each channel you use. Compare the customer's selection with the received order and, where printing is configured, the kitchen ticket.

Categories can also affect production: Nexara supports category-based printer routing. If you move a product between categories, check its kitchen destination as well as its position on the menu.

What should you test before using the menu?

Bring an item with sizes and paid extras to the demo. Use your own menu in the Nexara menu demonstration and compare each combination with what the kitchen sells. For aggregators, ask the team to show how your products and branches are matched to provider listings and how menu changes are published.

Then test a branch-specific sell-out. Keep the item available elsewhere and check the customer view at each location. This checks how shared product information and local availability work together when a branch runs out during service.

Choose the plan around the channels you use. The free plan supports 20 products; paid plans support unlimited products. QR dine-in starts on Growth and needs dine-in enabled at the branch. The call center is a Pro feature. If you take phone orders and want table QR ordering, include both in the setup discussion so the selected plan covers them.