Cloud kitchens in Jordan: test many brands in one queue

Why start with aggregator intake rather than another till?

The cook needs the next ticket while the packer needs the right order reference. Nexara works beside your existing till. Its Live Orders board combines Talabat, Careem, phone, website, installable app and table QR orders in one live queue per branch.

Talabat intake handles incoming orders and cancellations, with status updates sent back to the marketplace. Careem intake supports auto-accept, driver information when supplied, item replacements and scheduled orders. Staff can follow preparation on the board and search order history when a question comes back after handover.

A website order can arrive while staff are preparing a Talabat order. The branch board keeps both visible; item names and modifiers tell the cook what to prepare. Readable tickets matter as much as getting the order onto the board, especially when the person packing did not prepare the food.

Talabat and Careem activation requires partner approval. Prepare your outlet details and catalogue mappings before the first service. The guide to Talabat and Careem order intake explains the connection process.

How do virtual brands fit into one kitchen?

Your packer may be handling different brands while the cook reaches for the same bread and chicken. Nexara provides menu lists and menu channels, which control which menu appears on each ordering channel. Products can have modifiers, and availability is controlled per branch.

Nexara uses a franchise, company and branch hierarchy, with one order queue per branch. Several brands sharing a physical kitchen, particularly brands owned by separate companies, need their company, branch and marketplace outlet arrangement checked with the founder. Write down which branch board should receive each outlet's orders.

Catalogue tools include Talabat item-code and outlet mapping, plus catalogue publishing to Talabat and Careem. Decide which outlet uses which menu, then match marketplace items to the kitchen catalogue, including modifiers such as extra cheese or a different bread.

Keep menu choices separate from the physical kitchen layout when planning the setup. The guide to menu control across ordering channels explains the catalogue side.

Can tickets print separately for each brand?

Nexara supports product-category routing and per-printer templates. Switch on the categories each printer should receive, then assign its kitchen-ticket or receipt template. Brand-by-brand ticket separation must be tested with your actual menus.

Routing controls include branch, printer group and location. Set the category toggles to match your preparation stations. A hot-food printer should receive the items its cooks prepare; the packing station needs the ticket used to match the finished order to its bag.

The Windows print agent works with standard ESC/POS thermal printers over USB or network. Receipt and kitchen-ticket templates support Arabic and English, including Arabic item names and modifiers. Nexara uses printed kitchen tickets; kitchen display screens are not offered today.

During an internet outage, orders keep arriving in the cloud queue, and printing catches up when the connection returns; the board itself needs a connection. Keep a tested phone hotspot beside the printer PC.

How does marketplace intake differ from delivery dispatch?

Marketplace intake receives the food order. Dispatch arranges delivery for an order from your own channels. A Careem marketplace order follows its marketplace delivery arrangement; a website order can use a courier booked through Careem Express.

Nexara supports own-order dispatch through Careem Express, TopDeliver and Nashmi, with booking, tracking and cancellation. A driver role supports restaurants using their own fleet. Delivery zones can use a radius, named areas or polygons. The own-driver and delivery dispatch guide covers this workflow.

Choose who checks the order reference against the bag and who books delivery. Test a quote with each intended provider and write down the backup booking procedure. Estimates are available per provider; staff should check the selected provider's quote for the delivery address.

```mermaid flowchart LR A["Marketplace food order"] --> C["Branch order board"] B["Own website order"] --> C C --> D["Kitchen ticket prints"] D --> E["Match order and bag"] E --> F["Marketplace courier handover"] E --> G["Own delivery booking"] G --> H["Track own delivery"] ```

Marketplace and website orders follow the same printing workflow, then take different delivery handover paths.

What costs and limits belong in the decision?

Nexara has a free plan plus paid plans per branch in JOD, with current rates on request. Growth allows one printer and one delivery provider. Pro includes unlimited printers and delivery providers, and five branches. Call-center ordering requires Pro.

Nexara charges no commission on orders from your own website, installable app or call center. Talabat and Careem keep their own commission on orders they bring. Record courier charges and card-processing fees separately when comparing the cost of direct and marketplace orders.

Count the printers you need, including any backup. Separate hot-food and packing printers means your plan must cover both devices. List the delivery providers you intend to use and say whether staff will take phone orders, so the plan covers the work your kitchen will do.

Nexara also includes ingredient records and recipes, with recipe costing, stock alerts, inventory counts and waste analytics. Include the person responsible for stock counts in the walkthrough. Have them check a recipe against the ingredients and quantities your kitchen actually uses.

How should you test your brand setup before opening?

Bring your aggregator outlet details, menu files and printer models to the demonstration. Nexara has order history with search and filters. Keep each test order reference so you can check the result again, along with your list of which board should receive each outlet's orders.

1. Check where orders appear. Submit an order from every intended outlet. Pass only when each appears on the agreed branch board; if a shared queue is required, staff must be able to see those orders together.
2. Check menu details and cancellations. Pass when ordered items and modifiers match the source order, and a cancelled marketplace order updates the board. Place a website order while marketplace orders are visible to check both channels together.
3. Check that staff can identify the right brand at packing. Pass when the packer can identify each brand from its ticket and match the order reference to the bag without guessing. Include products shared across menus. If separate brand tickets are required, inspect that separation explicitly.
4. Check printing and recovery. Pass when Arabic items are readable and only the intended categories reach each printer. Disconnect a printer and confirm that its ticket waits, then reaches the rerouted or configured backup printer.
5. Complete a delivery from your own website. Pass when staff can book the intended provider and find the tracking information. Have the packer demonstrate the different handover procedure for a marketplace order.

Have the person who will run the shift perform the test. Record any wrong menu item or unreadable ticket against its order reference, then repeat that order after the correction. Keep approved tickets beside the packing station as references.