Nama’a Company logo

Nama’a Core · Operations and quality

Cancellations and downtime are not footnotes in a restaurant report.

Every cancellation or offline period can have a different story: unavailable items, delay, unplanned closure or a platform issue. A total count alone does not show where the response should begin.

01

Open the available detail

Review order time, branch, platform, documented reason and value when available. Do not invent a missing cause; look for a repeat pattern that deserves investigation.

02

Put downtime in context

Downtime duration needs compatible scheduled opening hours to become a meaningful rate. Offline time outside trading hours is different from downtime at peak, and missing evidence is not zero.

03

Give the problem an action owner

The response may be item-availability updates, schedule review, staff coaching or platform escalation. Review the result in the following report instead of merely recording the issue.

Common questions

Clear answers before the decision.

Is every cancellation the restaurant's fault?

No. A cancellation may come from the customer, platform or restaurant. Use the available classification and evidence rather than assigning a cause without verification.

Does no downtime record mean zero downtime?

Not always. Missing data differs from a complete source that explicitly records zero, and the report should disclose that difference.

Read next

Related guides that complete the picture.

What is restaurant operations intelligence—and why is a dashboard not enough?Why does the sales figure differ from the money received in the bank?The goal is stronger profitability—not sales alone.

Nama’a Core

Let’s turn the insight into a next step for your restaurant.

Talk to the Nama’a team
WhatsApp