A restaurant dining room long after closing: chairs stacked on the tables, the floor in darkness, and a single desk lamp still lit over the service station.
Security & control

It isn't hackers you lie awake about.

Restaurant POS security and cash control means no one person can move money alone. In Zentaro Serve a void or a refund needs a reason and a second person. Staff permissions limit what each role can do, and void control and discount limits are set by you.

Many people hear "secure" and think of encryption. The question an owner often has is smaller and sharper: at eleven at night, when you are not there, who can make a sale disappear?

Money doesn't move on one person's say-so.

Three actions can quietly remove value from a restaurant: voiding a sale, refunding a payment, and writing off stock. In Zentaro Serve these can need a second person to approve. You choose who can void or refund, and the limit above which a second person is needed.

Voiding a billAbove a limit you set, a manager can be asked to approve
Second person
Refunding a paymentA refund can need a second person to approve it
Second person
Writing off stockA stock write-off needs approval. A central kitchen write-off needs a second person.
Approval

And the rule doesn't get weaker offline. A void that needs approval captures that approval on the terminal itself, even offline, and carries it to the server when the line returns. The manager needs to have signed in on that terminal while it was online. Going offline does not skip the approval.

Looking for who can see and do what? See Staff access control.

Access for every role

Everyone sees only what they need.

The same app, signed in by different people. Each one sees only the screens their role allows.

  • Waiters

    A waiter sees tables, orders and bills. Not your reports, costs or settings.

  • Managers

    A manager runs their outlet. Not your company settings.

  • Roles

    You decide what each role can do.

  • Regions

    A region manager sees only their region.

See staff access control →

Control that holds when nobody is watching.

A device is not a person

An approval to void or refund must come from a signed-in person, never from a terminal that happens to be logged in. Kitchen roles have no permission to take payment.

Least privilege, by default

Servers and bartenders handle orders, not settlements. Touching an order has never implied authority over the money on it, and nobody has to remember to switch that off.

Enforced in three places

Hiding a menu entry is not security. Access is checked on the screen, again if someone types the URL directly, and again at the API — so a hand-built client gets the same answer as the app.

A record kept apart from daily use

The audit trail is evidence, not a diary. Restaurant users, including the owner, have no screen to edit it. That is why it helps in a dispute.

Your data is your data

Each restaurant's information is kept separate from every other restaurant's. A manager given one outlet is set up to see that outlet, not a sister outlet. You choose who gets which outlet.

A guest's data, on request

Everything you hold about one person can be exported as a bundle, and erased when retention says it must be. India's DPDP Act gives your guests that right; answering it should not mean a developer writing a query.

Secrets that cannot be read back

One-time codes are stored so that reading the database cannot recover a live one, and a service refuses to start on a publicly-known secret rather than accepting attacker-signed tokens quietly.

Leaving means leaving

Sessions expire, and a revoked login stops working everywhere rather than in the one place somebody remembered. When a person leaves your team, their access leaves with them.

How we count visits

We count visits without cookies. When a page opens, the counter records which page it was and the date, and adds one to a daily total. For a few actions, such as using a calculator or printing a template, it also records the name of the action. It never records what you type. The counter gives you no ID, so it cannot link one visit to the next. The counter does not save your IP address, your browser or device details, or the page you came from. The one exception is a calculator shown on another website, described below. The counts only help us see which pages and tools are useful. To block abuse, your IP address is held in the memory of the server to limit repeat requests. It is not written to disk, and it is lost when the server restarts.

  • If your browser sends Do Not Track or Global Privacy Control, the counter does nothing.
  • The daily counts are kept in files on our own server. They can be downloaded only with a secret access key.
  • The counts hold no personal details. We have not set a deletion date for them.
  • A calculator that another website shows on its own page is counted per day by the address of that website. A template download is counted per day, with no referrer.
  • The site keeps one small cookie, zc_market. It remembers whether you chose the India site or the global site, and it lasts one year.
  • We use Cloudflare Web Analytics to count page views and measure page speed. It sets no cookies and does not track you across sites. Cloudflare processes the visit data for us.
  • Google Analytics is off. If we ever switch it on, it loads only after you say yes in the cookie choice.
  • The early-access form uses Cloudflare Turnstile to block spam. Cloudflare sees your browser details when it runs.
  • If you send the early-access form, we keep your answers to contact you, for up to 24 months after you send it, and we delete them sooner if you ask. The form has its own notice.

To ask what we hold about you, or to ask us to delete it, use our contact page.

Privacy and grievance contact

Privacy and grievance contact: [email protected], Zentaro LLP, Moshi, Pune 412105, Maharashtra, India.

Write to this address to see, correct or erase your details, to take back your permission, or to complain about how we handle your data. If you are not happy with our reply, you may complain to the Data Protection Board of India.

The problem you know

Why cash goes missing in restaurants

  • A void takes a sale off the books and nobody asks why.
  • One person raises a refund and approves it too.
  • A cashier gives a big discount to a friend, and you find out next week.

How does void control and approval work at the till?

  1. Each person signs in with their own login. You can add extra sign-in protection (MFA).
  2. Each role gets limits: how big a discount it can give, who can void, who can refund.
  3. A void or a refund asks for a reason. Above your limit it needs a manager PIN.
  4. A refund can need a second person to approve it. You choose who can refund.
  5. At close each cashier counts their drawer. The shift breakdown shows any gap and whose shift it was.

What restaurant POS security includes

  • Roles and staff permissions, with temporary access for a short job.
  • Audit logs and a list of sessions, so you can see who did what.
  • A lowest price (margin floor) that staff cannot sell under.
  • POS Armor, which flags patterns such as many voids or high discounts for you to review. You switch it on.
  • Lost-device recovery, so a lost till does not stay signed in.

What it is not

  • The software does not make people honest. It makes problems easy to see and hard to hide.
  • We make no certification claim on this page. Ask us about your own needs.

Who can do what in your restaurant

Who it is for

  • Owner: sees voids, refunds and discounts by person.
  • Manager: approves with a PIN and closes the shift.
  • Cashier: works inside the limits of their role.

Talk to us and we will show the controls on your own roles. Talk to us

Sign-in, records and support access

Two-step sign-in

  • Staff can turn on a code from an authenticator app as a second step at every sign-in.
  • Recovery codes cover a lost phone.
  • If a person loses both, you can reset their authenticator. They are signed out everywhere and set it up again.

Audit log

  • Changes are listed newest first: who did it, their role, what they did and to what.
  • Each row shows the reason, and the old and new value.
  • Filter by type of record and by action.

Temporary access

  • Give one person one extra permission beyond their role, from a short approved list.
  • Say where it applies, and set an end date if you want one.
  • Each grant is recorded.

Support visits you control

  • Zentaro support gets into your account only when you allow it, with a code.
  • Every support action is added to a record. Records are only ever added, never changed.
  • Only the account owner can see the log of support visits.

Lock an unattended screen

  • Set how long a screen can sit idle before it locks. Unlock with the password or a one-time code.
  • Set a longest session, after which a fresh sign-in is needed.
  • Without your settings, the screen locks after 30 minutes and a new sign-in is needed after 8 hours.

Common questions.

How do I stop staff stealing cash in a restaurant?

Set limits by role, ask for a reason on every void and refund, and ask a second person to approve refunds. Count each drawer at close, so a gap shows with the shift it came from.

Can a cashier approve their own refund?

That depends on the permissions you set. You choose who can refund, and a refund can need a second person to approve it.

What is a void in a restaurant POS?

A void cancels an item or a bill that was already entered. Because it can hide a sale, each void needs a reason, and a manager PIN above your limit.

Can I limit staff discounts in my POS?

Yes. You set a discount limit for each role. Above it, a manager decides. You can also set a lowest price that nobody sells under.

What happens if a till or tablet is lost?

Lost-device recovery lets you switch the device off, so it does not stay signed in. Every till is paired to your outlet with a code.

Ask your current vendor these four questions.

Can one person void a settled bill alone? Does that change when the internet is down? Can a kitchen screen approve anything? And can anyone in the building edit the audit log? You are entitled to specific answers, from us as much as from anyone else.

Talk to us What switching involves

Last updated:

Pricing is coming soon

We are keeping pricing simple. We will share it when Zentaro Serve launches in 2027. Join early access and we will tell you first.