Your staff cannot log in, so everyone shares one account

Watch what happens when a new captain joins a restaurant that has "gone digital". He is asked for an email address. He may not have one, or he has one he has never opened. A password is created for him — usually something the manager can remember, because the captain will not. Within a week, everybody is using the manager's login, because it is faster than the alternative.

Nobody decided this. It is just what happens when software designed for office workers meets a restaurant floor.

Why the standard login fails here

Email addresses are not universal. A large share of restaurant floor and kitchen staff in India do not use email in daily life. Asking for one at the point of hiring creates a task nobody wants to own.

Typing a password on a touchscreen mid-service is slow. Even for someone comfortable with it, an eight-character password with a capital and a number takes several seconds and several attempts with wet or busy hands. At a rush, staff will do whatever is faster.

Reading English at speed is a real constraint. If the login screen, the error messages, and the password rules are all in English, then a staff member who reads Hindi comfortably and English slowly is being asked to do the hardest possible version of a trivial task, in front of a waiting customer.

Password resets need someone else. Every forgotten password becomes a manager's problem, which teaches everyone that logins are a hassle to be avoided.

Staff turnover makes it recurring. In an industry where people join and leave regularly, any onboarding step that takes fifteen minutes and an email address will be skipped.

What the shared account actually costs

The workaround feels harmless. It is not, and the cost shows up in places you would not immediately connect to it.

You lose all attribution. Every order, every void, every discount, and every bill is recorded against one account. When the till is short at the end of a shift, there is no way to narrow it down — which is exactly the problem described in cash going missing at the counter.

You cannot use roles. If everyone logs in as the manager, everyone has the manager's permissions. A new trainee can void a bill or change a price on day one, not through bad intent but because the system cannot tell who they are.

Your reports get less useful. Sales per captain, orders per shift, who is fast and who needs help — none of it exists. You lose the management information, not just the security.

Genuine mistakes become unfixable. When something goes wrong, you cannot go back and ask the person who did it what happened, because you do not know who it was.

There is no good paper workaround for this one

It is worth being straight about this: unlike portioning or bill sequencing, there is no process fix that makes email-and-password logins workable on a busy floor. What you can do is stop the drift:

• Never let a new staff member start on someone else's login, even for a day. That first day is where the habit forms.
• If you must stay on your current system, at minimum give managers and cashiers separate accounts, so the highest-risk actions are attributable even if the floor is not.
• Write down who worked which shift, so you can at least correlate a discrepancy with a group of people.

These reduce the damage. They do not fix the cause.

What a PIN actually changes

The fix is to stop asking for credentials the job does not require. In Orderix, each staff member gets a 4-digit PIN and a role — Owner, Manager, Captain, Kitchen, or Cashier. There is no email address, no password, and no reset process.

The practical differences:

• Onboarding takes under a minute. The owner adds the person, picks a role, sets a PIN. A captain hired at 5pm is working at 5:05pm.
• Logging in takes about two seconds, on a number pad with large touch targets, which works with wet hands and without reading anything.
• Every action carries a name automatically. Attribution stops being something staff have to cooperate with and becomes a property of the system.
• Roles actually apply. The kitchen screen shows the kitchen what it needs; a captain cannot reach owner reports. Not because of policy, but because of who is logged in.
• Someone leaving is one click. Deactivate the account, and the PIN stops working. Compare that to changing a shared password everybody knew.

Pair it with a Hindi interface and the literacy barrier largely disappears, because now nothing about signing in requires reading English at all.

The test to apply

If you are evaluating any restaurant software, ask the vendor to demo adding a new staff member and having that person take an order — with you playing the part of someone who does not use email and reads English slowly.

How long that takes, and how much help the person needs, tells you more about whether the system will survive in your restaurant than any feature list will.