Point of Sale is the module that you use to sell at a counter. It has three parts:
- A register is one point at your counter where you sell.
- A session is the time that one register is open, from its opening float to the final count of its drawer.
- The terminal is the full-screen page where a cashier sells, refunds and takes payment.
What happens at the register reaches the rest of your books by itself. Each sale takes the goods out of stock as soon as the ticket is complete. When a session closes, Beelocity writes the sales invoices and the treasury receipts for you, so you enter nothing again. If a close stops part-way, Sessions says what to do.
A typical day looks like this:
- The cashier opens the terminal and picks a register. They open a session with the cash that they put in the drawer, such as 5,000 DA in change.
- The cashier sells all day. They tap products or scan barcodes, take cash or a card, give change and print receipts. A customer who brings back yesterday’s purchase gets a refund against the original ticket. If the cashier makes a mistake on a ticket, they can void it during the same session.
- At the end of the day, the cashier closes the session. They count the drawer, by notes and coins if they like. Beelocity compares the count with the cash that the drawer should hold. The difference is the over / short.
- The close also settles the session. Beelocity writes one sales invoice for the walk-in sales, and one invoice for each ticket sold to a named customer. Treasury receipts pay those invoices, one for each payment method. Cash goes into the register’s own cash account. The money of each other method goes into the treasury account that the method names. The Z-report sums up the session by payment method, tax rate and product category.
Read on:
- Registers explains how to set up a register.
- Sessions covers opening, counting, closing and the Z-report.
- The terminal is the screen that a cashier works in, with the shelf, the basket, split payments and several customers at once.
- Tickets is the record of each sale, and of the refunds and voids that correct it.
Navigation
Open Point of Sale in the sidebar. The module opens on what needs doing (below), and the sidebar lists Terminal, Sessions and Tickets. Setup, at the end of the list, holds Registers as its one tab. You set up a register once, and you come back when the shop changes. Each list keeps its address, so a bookmark still opens it.
See what needs doing
When you open Point of Sale, you see the sessions that are waiting for someone, in four lists. Each row opens the session. Beelocity reads the lists again each time you open the page.
| List | What it shows | What to do |
|---|---|---|
| Closing, not finished | Sessions that were counted but whose settlement stopped. Each one holds its register until someone acts. | At the terminal, pick that register and press Finish settling. If it stops again, read the reason that it gives. As a last resort, the owner of your organization can force the session closed, unless it already has its settlement invoice. |
| Open sessions | Sessions that a cashier still has open, the oldest first. A row says so if the session has been open for over fourteen hours. | At the end of the day, close the session at the terminal and count the drawer. |
| Closed with a difference | Sessions closed in the last seven days whose count did not match the expected cash, over or short. The newest comes first. | Open the session to see the difference and the note that the cashier left. |
| Force-closed, not settled | Sessions that someone forced closed while some of their tickets had no invoice. A row shows how many tickets, their total and the reason. | Invoice those sales by hand in Sales. The session stays on this list after you do, because your invoice does not link to its tickets. |
Each list shows five rows and how many there are in all. View all opens the sessions list at the same selection. Force-closed, not settled has no View all, because Beelocity works that list out from the tickets of each session.
At the top of the page, Terminal opens the selling screen. Counter takings today, Live sessions, Average ticket today and Over / short, 7 days sit under it. Under those, Top products today draws a column for each of the day’s best sellers, by what it took. Counter takings over time sits beside it (below). You see only the lists that your role lets you open, and you see the button only if you can sell.
See what the registers took
Counter takings over time draws what your registers took each day, as sales minus refunds. It adds all your registers together, in your base currency. Voided tickets never count. The chart sits beside Top products today on the Point of Sale page, and on the Point of Sale tab of the dashboard.
- Which dates. On the dashboard, the chart follows the date range, which is the last 90 days unless you pick others. It draws a column for each day up to three months, for each week up to a year, and for each month beyond that. A week starts on Saturday. The Point of Sale page always draws the last 90 days.
- What a column says. Hover over a column to read its net takings, with its sales and refunds beside them. A refund counts on the day that it was made, not on the day of the sale that it reverses. So a day of returns can stand below zero.
- A ticket counts on the day that the register dated it, on your organization’s own clock. A ticket sold at 23:30 belongs to that evening, not to the next morning.
- Registers in another currency. If a register banks into an account in euros or dollars, Beelocity converts its takings at the exchange rate on file for each day. If a register has no rate for a day, Beelocity leaves it out of that day’s figure. It names the register under the chart, with a link to Exchange rates.
- A column opens nothing. To see the tickets of a day, open Tickets and narrow the list to that day.