Skip to content
ENS.EG

Restaurant Cashier Software: The Shift, the Drawer, the Receipt

31 Oct 2026

Cashier software in this article is narrower than a full restaurant management program. It is shift close, drawer movement, the receipt, and who may void or discount. Kitchen, stock, and online ordering live in a wider guide this page points to.

The cashier corner in an Egyptian restaurant is usually a drawer with cash, a person who changes with the shift, and a guest who pays before sitting or after eating. Software that helps this corner is not a board of every management idea. It is a record that can open a shift, sell, and explain at the end of the day why the drawer is heavy or light. Without that record, a kitchen screen or a guest app is built on sand.

This article stays on the box. It does not tour the kitchen, stock, branches, or the digital channel. That wider picture has its own guide, linked at the end, for the day the pain is larger than the drawer. The questions here are the ones an accountant asks on an evening visit: who opened the shift, what was sold, what was voided, what was discounted, and how much cash should still be there.

Opening a shift and closing it

Opening a shift names the staff member and records the amount the drawer started with. That amount is a float, not revenue. A sale after open belongs to this shift, not to a vague "day". Closing the shift asks for a cash count and records the gap between what the program expects from drawer movement and what was counted by hand. The gap is not an automatic accusation. It is a line that needs a reason: a remainder from the previous shift, an expense that left with no entry, or a counting mistake. Without the line, the argument returns to memory.

  • Each shift has an opening person and a starting amount.
  • A sale during the shift belongs to it, not to an unbounded day.
  • Close records the count, the expected cash, and the gap.
  • An unclosed shift blocks or warns before the next one opens.
  • A sale after close is refused, or it opens a new shift.

Pick one reading of the last line and write it down for staff. If the program sells on a shift that is already closed, the report lies. If it blocks every sale while a supervisor is away, the queue stops. A practical middle is an emergency shift in a supervisor name, not a bill with nobody on it.

The drawer is a set of movements, not a black box

Cash comes in with cash sales and goes out with a cash refund or an approved expense, such as buying ice in the middle of a shift. Every out needs a type and the name of the person who paid it. Cards and wallets never enter the drawer, so they appear on the sales report and not in the paper count. Mixing them is the common reason a gap is blamed on staff. A program that dumps "everything that was paid" into one cash column creates that mix even when the cashier is careful.

Nothing here sets an acceptable gap or a ratio. That is a decision for the owner and whoever reviews the books. The fields that make a review possible are: opening float, cash in, cash out, expected, counted, and a reason when the last two differ. A missing field sends the review back to chat.

The receipt, and what this article will not invent on it

A receipt that helps the guest and the shift carries the item name, the quantity, the price, the total, the order number, the branch, and the time. Anything further that your accountant or a reviewing body requires is something you write into the request. This article does not invent legal lines. A copy for the guest and a copy that stays on the record are enough for a dispute about what was paid. A receipt printed with no order number cannot be tied to a complaint later.

Void and discount are not buttons sitting open on the main screen. A discount needs a limit or a permission: the cashier up to an amount you agree, and a supervisor above that. A void after payment needs a recorded reason and the name of the person who pressed it. Without that, the sales report is a net with holes that only the person counting the drawer at night can feel.

How the box meets the rest of the restaurant

The till reads items from a list. If the list price changes and never reaches the box, the receipt disagrees with the board on the wall. That is a meeting point with menu management, not the subject here. A guest order from a phone does not close a drawer unless you agree that the channel hands a bill to the shift. Write that handoff if you need it. Do not assume a ready till program already knows your current app.

What to send so the quote is actually about the till

  • How many shifts run in a day, and who opens them.
  • Which payment methods enter the drawer and which do not.
  • Who may discount, and who may void after payment.
  • Whether the receipt is paper or shown on a screen for the guest.
  • The name of the current program, if any, and what fails in it.

Questions from the accountant and the branch

Is this a restaurant management program?

No. This is the till corner. Kitchen, stock, ordering in the restaurant name, and branches sit in the wider guide. Buy the box when the pain is a shift, a drawer, and a receipt, and move to that guide when the pain grows.

Does the program force staff to be careful?

It makes movement visible and puts a name on a void. It does not replace a hand count or a camera in the room. A recorded gap starts a conversation. It is not a verdict.

What about more than one box in the branch?

Each box is its own shift, or a shift tied to a device, so cash from two devices is not counted as one pile. Mention the device count in the first message so a branch is not priced as a single box.

The wider picture is in the restaurant management guide. A build or a link shaped around your shift starts from custom software.

Describe the shifts and the drawer through start your project. The WhatsApp button under the page opens the conversation with this till article as the source.

Have an idea or a system that needs building?

Tell us about your project in three short steps. We will review it and contact you to agree on the next step.

Start a project