A ticket is one counter transaction, which is a sale or a refund. Tickets come only from the terminal, and a ticket is final the moment that it exists. The price, discount and tax on each line stay as they were at the moment of sale. Nobody can edit or delete a ticket afterwards. You correct a mistake with a void or a refund, so the ticket list is a complete history of what your registers did.
For the screen where a cashier sells, see the terminal. This page is about the ticket as a record: what it holds, and what can still happen to it.
Finding a ticket
The Tickets list narrows on its filter button by Status, Customer, Session, Cashier, Type (Sale or Refund) or Register. It also takes a date window on Sold at, and a range on Tax amount or Total (Working with lists).
When you open a ticket, one screen shows everything that it holds. The customer, the session and the money sit down one side, and the goods sit in a table beside them. The payments that settled it are on a Payments tab of their own.
Refunds
A customer who brings goods back gets a refund ticket. At the terminal:
- Type the whole number of the original ticket into the search box, and press Enter. The ticket can come from this session or from any earlier day.
- On the refund tab that opens, tap each line that is coming back, and key its quantity.
- Press Refund, pick how to pay the money out, and press Confirm refund.
Beelocity refuses a partial number and does not guess it, so you never refund the wrong ticket.
The refund carries the original prices, so nothing is priced again. The goods go straight back into stock. If the product is tracked by batch, they return to the batch that they were sold from, at what they cost when they left. So stock reports and expiry lists stay right after a return.
The refund tab counts what is left to return, not what was first sold. So a second visit for the same ticket cannot offer units that have already come back. Pay out shows what the register will really pay, and Beelocity works it out to the centime.
You can refund a ticket in several steps until every unit is back. Beelocity refuses a request for more than is left, and it adds up all the quantities for a line before it checks. However you split the return, the total given back is exactly what was charged, to the centime. The last return of a line pays whatever is left, and not another rounded share. If the sale was rounded to a whole dinar, a return of the whole ticket gives back the rounded figure that the customer handed over.
Each line of a refund ticket names the goods exactly as the sale did. It shows the product’s name and, for a variant, its own size or colour, with a quantity below zero. That quantity and the ticket’s Type, Refund, say that the goods came back, in whichever language you use. If a session’s close writes a credit note for a return, the note names the goods in the same way. Older refund tickets may still show the word remboursement after the name, because a ticket is never rewritten.
Money goes back the way it came, in cash or by a method that the original ticket was paid with. If a sale paid in cash were refunded on a card, the drawer count would still look right. But the money would have left by another account.
A refund is never paid as a cheque or a bill of exchange, because the register never takes that paper in. Use cash, or a method that the customer paid with. If neither works, ask the owner of your organization or a Sales manager to raise a credit note for the customer in Sales.
Refunding has its own permission, apart from selling. Each Cashier holds it by default. If you want only certain people to take returns, the owner of your organization can take it off the Cashier role alone. The terminal keeps selling as before. The refund tab then tells the cashier to ask the owner of your organization to take the return, and its Refund key stays off.
Voids
A void cancels a whole ticket from the same session, while that session is still open. It is for a ticket entered by mistake, with the customer still standing there. The cashier looks the ticket up as for a refund and presses Void ticket. The goods go back into stock, and the ticket counts for nothing in the session’s takings. The ticket stays on record with the status Voided. After the session leaves Open, you cannot void its tickets, so use a refund instead.
You can never void these two kinds of ticket, and the terminal says which one you have:
- A refund ticket. A void would take back goods that the customer left with, and undo money that they were handed. If a refund was a mistake, sell the items again, because that is what really happened.
- A sale that has already been refunded, in part or in whole. Part of it is already reversed, so a void would count that reversal twice. A void is for a sale that should never have existed, and a sale that came partly back did exist. Refund what is left instead.
Voiding also has its own permission. Each Cashier holds it by default, and the owner of your organization can take it off the Cashier role alone. The terminal then hides Void ticket, and nothing else that the terminal does changes.
Receipts
Each completed sale shows a printable receipt. It holds your organization’s name, the ticket number, the register’s name and the time of sale. The lines, the tax, the total, the payments and any change follow, and then the register’s own footer. Put your return policy or a thank-you in that footer.
Press Print for a paper copy. A long basket runs onto a second page and is not cut off. The receipt prints in black on white, whatever theme the terminal uses. A refund shows a short message and no receipt.
The time on the receipt is the time recorded on the ticket, and not the clock of the machine. So a machine set to the wrong time cannot print a receipt that contradicts your records.