One menu across every channel: change a price once
As a restaurant owner, you change a price on the website, then find the old one on Talabat or the table QR menu. Now your staff have to explain the difference during service.
Nexara, a restaurant order and operations platform built in Amman, Jordan, keeps prices consistent across your website, installable app and table QR through one catalogue, with availability controlled per branch. Talabat and Careem publishing requires integration setup and partner approval; start by building the central menu and checking each connected channel.
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; any connection to an existing cash register needs a separate integration check.
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.
| Menu element | Practical setup rule | What to check |
|---|---|---|
| Category | Group related products under a clear heading. | The customer can find the item without guessing. |
| Product | Use a recognisable name for the item being sold. | The name means the same thing to the guest and kitchen. |
| Modifier group | Keep related choices together, such as sauce choices. | The group belongs on the intended products. |
| Size | Decide whether it should be a separate product or a choice. | Test the price for each size with its paid extras. |
| Arabic and English names | Write both names for the same product or modifier. | Both names describe the same portion and preparation. |
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 has catalogue publishing flows for Talabat and Careem. Receiving orders from a provider and publishing menu changes to it are separate flows. Once the integration is connected, publish through the supported flow and check the resulting customer-facing listing.
| Channel or provider | Supported menu capability | What to check |
|---|---|---|
| Nexara website and installable app | The storefront is generated from the shared menu. | Menu-channel settings select the intended menu. |
| Nexara table QR | QR dine-in ordering uses the platform's menu setup. | Scan the code for the intended table and check the menu. |
| Talabat | Catalogue fetch and push, with SKU mapping, outlet mapping and reconciliation. | Product identifiers and the restaurant outlet are mapped correctly. |
| Careem food orders | Catalogue, hours and availability push, plus store pause. | Check the connected location and its customer-facing menu. Careem Express is a separate dispatch service. |
SKU mapping connects product identifiers; outlet mapping connects the intended restaurant location. For Talabat, check both before publishing. Confirm the correct branch connection for Careem too. During setup, establish which provider outlets correspond to each Nexara branch.
After publishing, open the provider's customer-facing menu and check the changed item, including its extras. The Talabat and Careem order intake and catalogue integrations page explains the wider connection.
How do you update a menu without leaving old prices behind?
Edit the central product, then open the menus your customers use. Nexara provides the shared catalogue and channel controls. Check the displayed price and the total with extras before the next service, using this procedure.
- Find the product in Products & Menus. Check its category and attached modifier groups before editing.
- Read the Arabic and English names beside each other. Correct any mismatch in portion size or preparation.
- Change the central price. Check whether any paid extras also need a price change.
- Check the intended menu channels and branch availability. Keep sold-out items unavailable while changing their prices.
- Open the website and installed storefront app, then scan a table QR where enabled. Select the item, add its extras and check the total.
- For connected aggregators, use the supported catalogue publishing flow. Open the resulting Talabat or Careem listing and check the price and available choices.
- 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?
Test restaurant menu management software with an item that has sizes and paid extras. 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 the mapping and publishing steps for your connected outlets.
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.
Check plan fit as well. 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.
What to remember
- Maintain the catalogue centrally and choose which menus each channel shows.
- Use per-branch availability for local sell-outs and assign someone to restore items after replenishment.
- Check each provider's customer-facing menu after publishing catalogue changes.
- Nexara has a free plan, then paid plans per branch in Jordanian dinar, with current rates on request.
- Message Nexara founder Issa Al-Dalu on WhatsApp through nexaratech.io with an item from your menu. Ask to arrange a walkthrough of its sizes and paid extras, followed by a branch-specific sell-out check.
Questions people ask
Can I change a restaurant menu price once for the website and app?
Yes. Nexara's website and browser-installable app use the shared menu catalogue, so you edit the product centrally.
Can I hide an item at one branch without removing it everywhere?
Yes. Nexara supports per-branch availability, so you can mark the item unavailable at the affected branch and keep it on sale elsewhere.
Does Nexara update menus on Talabat and Careem?
For Talabat, Nexara supports catalogue fetch and push with SKU and outlet mapping. For Careem food orders, it supports catalogue, hours and availability pushes, plus store pause. Check the published item on each provider's customer-facing menu.
Can I manage sizes and extras in Nexara?
Nexara supports products, modifiers and modifier groups. Test each size with the same paid extra and compare the charge and final total with your menu.
What should I do when an ingredient runs out?
Use the branch inventory count to identify affected dishes, then update their per-branch availability by hand. Restore each item once the kitchen can prepare it with its listed choices.
Will Arabic item names print correctly on the kitchen ticket?
Yes. Nexara renders Arabic text as images for thermal printing, including item and modifier names, and tickets can also carry English. Check the names during setup so the kitchen receives wording it recognises.