Your first week on Nexara: a day-by-day checklist

What should you prepare before day one?

Start with the branch computer, ordinary ESC/POS thermal printers, the Live Orders board, the menu and staff roles. Nexara drives standard ESC/POS printers over USB or network through the Windows print agent. It does not require a proprietary terminal or hardware bundle.

• Place kitchen, bar and cashier printers where staff can collect tickets without crossing the service path.
• Check that Arabic item and modifier names are readable on a test ticket. English can appear on the same ticket.
• Give each employee the role they need. Roles include cashier, waiter, call center, branch manager, inventory manager and driver.
• Keep a phone hotspot available. Orders can remain in the cloud queue while the connection is down, but the board needs a connection.
• Write down products that must be unavailable at this branch before the first order arrives.

If a setting or screen is not covered in the product information you have, send the question to the founder's assisted setup on WhatsApp. Nexara support is available in Arabic and English during Amman hours, and the founder answers.

Day one: prove that tickets print correctly

Send a controlled test through every printer group you use. Check the branch, printer location, category routing, Arabic text, modifiers and receipt details. A ticket should reach the correct printer without anyone retyping the order.

1. Place one website or app order with an Arabic product and modifier.
2. Place one table QR order if dine-in is enabled on the branch.
3. Send a phone order through the call-center screen if your plan includes Call Center.
4. Check that each ticket appears on the Live Orders board and prints at the intended location.
5. Unplug one printer briefly and confirm the order stays on the board. Re-route its categories from the dashboard, or use the configured backup printer where available.
6. Reprint one ticket by hand only after confirming which copy the kitchen needs.

Nexara's printing engine works with standard thermal printers, including Epson, Star and Bixolon models that support ESC/POS. Tickets queue and print once, never twice, never lost. If the printer is offline, the order remains visible and waits for printing.

Day two: watch the first staff-led orders

Let the people who will actually take orders use the system. Stand beside the cashier, waiter and call-center agent for the first few orders. Check whether the work makes sense at service speed.

• Ask the cashier to find an order on the live board and locate it in order history.
• Ask the waiter to create or follow a dine-in order from the table QR flow.
• Ask the call-center agent to search a caller by phone number and confirm that saved addresses and past orders appear.
• Have the team confirm payment choice and order type before sending the order forward.
• Record every point where an employee asks, “Where do I find that?”

Nexara attaches orders to customer records. A phone lookup can show saved addresses and past orders, while complaint logging is available from the call screen. Call Center is a Pro-plan feature, so use the phone-order test only if it is included in your plan.

For a deeper staff handover, use the guide on onboarding a cashier or waiter. Keep the first session short. A cashier who can complete one real-looking order is more useful than a team that has clicked through every page.

Day three: test every order channel

Confirm that the kitchen sees one consistent order path whether the customer orders from your own storefront, a table QR code, the phone, Talabat or Careem.

Your own website, app and call-center orders carry 0% commission from Nexara. Talabat and Careem keep the commission they charge on orders they bring. Activation can depend on partner approval, so ask for assisted setup if one channel is not ready.

Nexara does not offer Jahez or DHUB integrations today. It also does not send WhatsApp order notifications. Its WhatsApp module is a conversation inbox for call-center roles.

Day four: confirm menu and branch availability

Compare the menu customers see with the menu the branch can produce. Nexara uses one catalogue across channels, with products, categories, modifiers and modifier groups. A price change can apply across connected channels, while availability can be controlled per branch.

1. Choose five frequently sold products and compare their names, prices and modifiers on the storefront and order board.
2. Mark one unavailable product at the branch and confirm the customer-facing menu reflects the intended availability.
3. Check that a modifier prints with the product on the kitchen ticket.
4. Review menu channels so the right menu is visible to the right ordering path.
5. Ask the founder's assisted setup on WhatsApp about any branch setting that is not listed in the facts you were given.

Inspect your own storefront. It can run on a Nexara subdomain or a verified custom domain, and customers can install it from their browser as an app. It is a progressive web app, not an app-store download.

See Nexara features for current product areas, and the integrations page for supported channels and delivery services.

Day five: read reports beside the till

Open the report tabs across orders, products, customers, channels, delivery, money and operations. Compare what the order board recorded with what the cashier recorded at close.

• Review orders by channel and order status.
• Check product and product-by-branch activity.
• Review failed orders and cancelled orders.
• Open customer records and website reviews.
• Use the cashier reconciliation and End of Day views alongside the till's net-sale record.
• Check delivery activity if the branch dispatches through Careem Express, TopDeliver or Nashmi.

Compare which order was accepted, prepared or cancelled with the amount the cashier recorded at close.

Day six: call for feedback and log complaints

Delivered orders can populate feedback-call tasks with item summaries. If a customer reports a problem, the complaint can become a case with routing, an SLA clock, escalation and a resolved status.

1. Open the feedback-call queue and assign the calls your team can complete.
2. Ask whether the order arrived complete and whether the food matched the order.
3. Record a complaint as a case rather than leaving it in a private notebook.
4. Attach relevant photos when the case needs evidence.
5. Review open, breached, escalated and resolved cases before the day ends.

Keep the feedback call focused on the order. Look for a broken menu item, a printing mistake, a delivery handoff problem or a repeated complaint pattern. Nexara stores customer records, reviews and complaint cases so the next call has context.

Day seven: make a short adjustment list

Review the week's notes with the branch manager. Choose the few adjustments that affect the next service: a printer route, an unavailable product, a staff permission, a menu label or a complaint process.

Keep one owner for the list and review it after the next busy service. If you are opening another branch, repeat the printer and channel tests there. Branches have their own assignments, availability and operational records, so a successful first branch does not remove the need for a second branch check.

For the launch sequence before this checklist, read how to go live in one day. For a longer trial period, use the 14-day trial checklist.