Why is my Ninja branch showing as closed when the restaurant is open?

Restaurant operators on Ninja get something most delivery platforms do not provide: the interface itself says which closures end on their own and which do not. The Ninja partner portal shows “Your restaurant is currently busy!” or “Your restaurant is currently closed!” at the top of a branch, offers timed options that return automatically, and marks one option as different. A branch closed for maintenance carries the instruction “To receive orders again, you have to open the restaurant manually by pressing ‘Open Restaurant’ action!” Nothing else will bring it back.

What does “Your restaurant is currently closed!” mean on Ninja?

It means the branch is not receiving orders, and it is one of two off states the portal names. The other is “Your restaurant is currently busy!” Both banners come from the Ninja partner portal at restaurant-portal.ananinja.com, whose interface dictionary is served in plain text, in English and Arabic.

The controls beneath those banners are named in the same dictionary. A branch is switched with “Mark Available”, “Mark Busy” and “Close for Maintenance”, and it is brought back with an action labelled “Open Restaurant”. A successful reopening confirms with “This branch is now open” and the explanation “The branch is now open and ready to receive orders.”

Every off state asks why. The portal has separate prompts for the two paths, “Select Busy Reason” and “Select Closing Reason”, plus “Select Maintenance End Time” for the third. That is a design decision worth noticing, because a platform that forces a reason at the moment of closing is a platform whose closure records can later be read back and argued about.

Which Ninja closures come back by themselves?

The timed ones, and the portal states the return in the option itself rather than burying it in a help article. “Change to busy 30 mins” is described as “Will receive orders after 30 minutes.” “Change to busy Until Tomorrow” is described as “The restaurant will open at the usual time in the morning to begin accepting orders.” A closing option is described as “Will close the branch based on the selected option”, and the general rule for timed closures reads “Restaurant will receive orders after selection time ends”.

That is unusually considerate wording, and it changes what an operator is deciding. On most platforms a manager choosing to pause a branch is choosing a state. On Ninja they are choosing a duration with the consequence written next to it, which is the difference between pressing a button and making a decision.

The portal also allows an early return from any timed state, telling the operator they can open it now by pressing the Open Restaurant action rather than waiting for the timer. So the timers are a floor on how long a closure lasts at most, not a lock.

Why does a Ninja maintenance closure need to be reopened by hand?

Because Ninja treats it as a different class of event, and says so in its own words: “To receive orders again, you have to open the restaurant manually by pressing ‘Open Restaurant’ action!” The exclamation mark is the platform’s, and it is doing real work. Every other off state on this portal has a return written into it. This one does not.

The reason the distinction matters operationally is that maintenance closures are the ones most likely to be set by someone who is not on the shift that ends. A branch closed on Sunday afternoon for equipment work, by a manager who then goes home, is a branch that will not reopen on Monday morning by itself no matter what the schedule says. The portal asks for a maintenance end time, but the instruction above is explicit that receiving orders again requires the manual action.

This puts Ninja in a small group. Keeta documents the same behaviour for suspended stores, stating that they stay hidden until manually reactivated. Bolt Food gives an automatic return only to busy mode and none to going offline. Most other platforms in the region attach a timer or a schedule to everything. On Ninja the rule is mixed, which is harder to remember than either extreme, and mixed rules are the ones staff get wrong.

Who is allowed to change a Ninja branch status?

Whoever holds the permission, and the portal has a specific message for everyone else: “Access Denied: Contact support to get the required permissions.” Access itself is issued rather than self service, since the sign in screen instructs the user to sign in with the restaurant account information they received from Ninja.

For a chain that produces a practical question worth answering before an incident rather than during one. If the branch manager cannot change status and the person who can is not reachable, the length of any closure is set by the availability of a permission holder. A platform that requires a manual reopen for maintenance closures and gates the reopen behind a permission has two independent human dependencies in the recovery path.

The scheduling side is simpler. The portal carries an “Open 24 Hours” switch for branches that trade around the clock, and its working hours endpoints sit alongside the branch endpoints in the same application. A branch that appears closed while its staff are working may simply be outside the hours somebody entered, which is a configuration fault rather than an operational one and repeats every day until it is corrected.

Where does Ninja operate, and does this apply to every market?

The portal’s own country list contains four entries: Saudi Arabia, Bahrain, Kuwait and Qatar. No other market appears in it, so a brand running the same interface across the Gulf is running one portal against several countries rather than several tools.

That single portal is also the only surface Ninja publishes. We found no public developer documentation and no published API for branch status, which means an integrated chain cannot read a Ninja branch’s availability the way it can on platforms that publish a status endpoint. Whatever visibility a brand has on Ninja comes from the portal, or from outside.

How do you catch a Ninja branch that stayed closed?

By checking the storefront, because the two failure modes on this platform are both invisible from the inside. A maintenance closure that nobody reopened looks, in the portal, exactly like a maintenance closure that is still in progress. A branch outside its configured hours looks like a branch that is closed for the night.

The signal to watch for is a closure that outlives its stated duration. Ninja tells you what each state was supposed to do, thirty minutes, until tomorrow morning, or until a person presses Open Restaurant, so any branch still unorderable past that point is either forgotten or blocked. Detecting it means recording when each branch could actually be ordered from and comparing that against the hours the branch published, which is what Kitchain (kitchain.co) does from the customer side rather than from the partner portal.

What Ninja is and which markets it serves is on our page at kitchain.co/aggregators/ninja/. A brand that also sells on HungerStation in the same market should note that the two platforms handle reopening in opposite ways. One writes the return into the option itself. The other publishes no auto reopen rule at all, which is set out in why a HungerStation store shows as closed.