Bloub: the assistant that reads your numbers overnight
The cook needs a prep quantity, and you are still sorting yesterday's cancelled tickets. Before changing the sauce batch, you need to know whether fewer meals sold or more orders fell through.

Nexara, a restaurant order and operations platform built in Amman, Jordan, gives you Bloub to answer from your numbers with citations, check patterns overnight and create follow-up tasks. Its answers depend on recorded data, so unrecorded events leave gaps; start with one branch and date range, then check the cited source.
Figures in this post are illustrative examples, not a client's actual results.
What can you ask Bloub about your restaurant?
Bloub can compare sales periods, break orders down by channel and retrieve individual orders. Give it the branch and dates so the question has a clear scope. You can begin with yesterday's sales, then inspect cancellations before deciding whether the prep sheet needs changing.
These prompts show the kinds of questions you can ask:
- Compare this week's sales with last week's for the same branch.
- Show yesterday's orders by channel.
- Which products sold most during the period I selected?
- Show cancellations for this branch and period.
- What complaints are still open?
Bloub can also retrieve inventory alerts, printer status and a product's current menu availability. If a sandwich sold poorly yesterday, check its sales records first. Its current availability answers a different question: whether customers can order it now.
Nexara sits beside the till as the order and operations layer. Its report tabs cover orders, products, customers, channels, delivery, money and operations. The guide to restaurant reports that matter explains which reports to use for the underlying checks.
How do you check an answer through its citations?
Bloub answers questions from your company's numbers with citations. Use those citations to trace a statement to its source, then follow this checking routine.
```mermaid flowchart LR A["Your branch question"] --> B["Bloub checks records"] B --> C["Answer with citations"] C --> D["Source record review"] D --> E["Focused follow-up question"] E --> B ```
Follow the citation to the source, then narrow the next question around what the records show.
- Open the cited source and match its branch and dates to your question, including whether the period covers a full trading day.
- Compare the stated measure with the report, including the treatment of cancelled or refunded orders. For a cited financial total, check Nexara's Financial report.
- Use order-detail lookup to inspect the records behind a finding, then ask a focused follow-up.
Order count and sales value answer different questions. A branch can receive fewer orders while selling larger baskets. For the cook waiting on a prep decision, product quantities may matter more than the day's sales total. Bloub can retrieve top products as well as sales summaries.
What does Bloub read overnight?
Bloub checks patterns with six nightly detectors and provides a morning brief in the app, rather than as a scheduled email report. One check looks for customers buying fries less often with their meals after the fries price changed. Others examine demand, product and basket patterns, absent regulars and operational friction.
The numbers below are an illustrative example, not a client's actual figures. These examples show owner checks for each detector topic.
| Nightly detector | Illustrative owner review | Records to examine |
|---|---|---|
| Demand shift | Daily orders fall from 100 to 80, a 20% drop. | Order totals for equivalent trading days and the branch's opening hours. |
| Item trend | An item's units sold fall by 15% to 25% between comparable weeks. | Product sales and any recorded availability problems. |
| Basket anchor | An item appears in 30 of 100 orders. | Orders containing that item and the other products bought with it. |
| Regulars gone | A customer who ordered weekly has no recorded order for 21 days. | The customer's order history and any recorded complaint. |
| Price change attach drop | After a fries price change, fries appear in 20% of baskets instead of 30%. | Relevant baskets and the dates of price changes. |
| Ops friction | Review an operational issue identified in the morning brief. | The records cited by that finding, followed by relevant order or complaint details. |
For an absent regular, examine customer history alongside any open complaint. For a product decline, inspect the relevant orders and product sales. If fewer customers added fries after the price changed, check whether fries were available throughout both periods before deciding that price caused the drop.
Which actions can Bloub take?
Bloub can open pages, prefill forms and create workflow tasks. It also generates reports and feedback reports. Workflow functionality requires Pro. A manager can examine a finding, open the relevant screen and create a task for someone to investigate.
Bloub can list workflow templates, retrieve tasks and show workflow statistics. NexaraFlow includes a Bloub Insight Action template for follow-up work, with role-scoped tasks, stages, timing and escalation. Inspect the resulting task in the workflow screens so the morning finding has a visible follow-up.
Opening a page changes the screen you see; prefilling places information in fields. Creating a task saves work for someone to handle. The Nexara feature overview places these actions alongside the rest of the platform.
What should you know about recorded data and privacy?
Bloub uses your company's numbers and searches Nexara's documentation. “How do I change product availability?” is a documentation question. “How many sandwiches did this branch sell yesterday?” requires the branch's sales records.
Bloub processes questions through external AI providers approved by Nexara under a zero-data-retention policy. Your restaurant owns its customer data, can export orders and customers as CSV files, and can request deletion within 30 days. Nexara never markets to your customers.
Bloub can retrieve a forecast, product sales and peak hours. For the morning prep decision, compare the forecast with quantities sold on comparable trading days. Then account for what the kitchen knows, such as a planned closure or a large phone enquiry that has not become an order.
Talabat and Careem order intake brings those orders into Nexara alongside own-channel orders. Bloub's channel breakdown helps you examine the recorded sales by channel. An owner can use that breakdown to see which channel contributed to a change in sales before asking the branch team what happened during service.
How should an owner test Bloub before staff use it?
Start with a morning finding you have checked against its source. Bloub can open the relevant page, prefill a form and create a workflow task. Ask the manager who will use it during service to carry out the follow-up:
- Have the manager choose a specific branch check from the finding, such as investigating why fries sold less often with meals.
- Ask Bloub to open the relevant page and prefill a suitable form. Have the manager inspect every populated field, correct anything needed and review the form before submission.
- On Pro, request a test workflow task. Check that its branch and instructions match the intended follow-up.
- Have the intended staff member sign in and find the task in their task screen. Ask them to explain what they need to investigate and where they will record the outcome.
Record any blocked step or unexpected result, including the screen and staff role involved. Keep the prefilled values and task details available when discussing corrections. The daily reports an owner should read can help you choose a familiar finding for this exercise.
Nexara founder Issa Al-Dalu answers support in Arabic and English on Amman hours. Bring the test notes to that conversation so you can discuss the exact screen or task that needs attention.
What to remember
- Bloub answers questions from your company's numbers with citations.
- Six nightly detectors feed a morning brief.
- Bloub can prefill forms and create workflow tasks; workflows require Pro.
- Check sources, then test whether staff can review prefilled fields and find follow-up tasks.
- Use WhatsApp to arrange a Bloub demo with Nexara at nexaratech.io. Bring one branch report and a follow-up you want staff to carry out.
Questions people ask
Can I ask Bloub questions about restaurant sales?
Yes. Bloub supports sales summaries, period comparisons and channel breakdowns, with citations from your company's data. Include the branch and date range.
Does Bloub check the numbers while I am asleep?
Bloub runs six nightly detectors covering demand, product and basket patterns, regular customers, accompanying-item sales after price changes, and operational friction. You can review their findings in the morning brief.
Can Bloub explain exactly why sales dropped?
Bloub retrieves comparisons and related records with citations. Establishing the cause also requires context from the branch, such as a kitchen closure or an availability problem during the period.
Is Bloub completely read-only?
No. Bloub can prefill forms and create workflow tasks. Workflow functionality requires Pro.
Will Bloub send WhatsApp order notifications?
No. Nexara's WhatsApp feature provides a conversation inbox for call-center roles; it does not send order notifications.
Does Bloub replace my accountant or branch manager?
Bloub helps retrieve records, compare periods and create follow-up tasks. Financial interpretation and branch decisions remain with your accountant and manager.