Running the register
Everything a till needs between the first sale of the day and the last: a
counted cash drawer, a quick way to change who is ringing, the customer in
front of you, returns, and a proper printed receipt. All of it runs from the
register at /{site}/pos. Staff PINs are set on Products → Point of sale,
and the register's rules under the site's Admin → Plugins → Commerce.
These are part of the point of sale, so they need Pro or above, like the register itself. Only members who can use the register — anyone with the Use the point of sale permission for the site, which owners, admins and editors hold by default — can open shifts, switch in, look customers up or take returns. Each also needs its own finer permission.
Shifts and the cash drawer
A shift is one stretch of trading on one register, counted against one cash drawer.
- Open a shift from the strip above the basket and enter the starting cash (the float) you counted into the drawer.
- While it is open, every sale on that register is counted in the shift.
Use Cash in/out to record cash that moves without a sale:
- Paid in — cash added to the drawer, such as change from the bank.
- Paid out — cash taken for an expense, with a reason.
- Safe drop — cash moved from the drawer to the safe.
- X report shows the shift so far at any time and changes nothing.
- Close shift, count the drawer and enter what is in it. The Z report freezes the shift's figures, and the register is free for the next shift.
A register has one open shift at a time. If two tablets try to open the same register at once, one opens it and the other is told a shift is already open.
What the reports show
Sales (orders, gross sales, discounts, tax, tips, refunds and net sales), the same broken down by tender (cash, card, gift card and room charge), and the drawer:
| Starting cash | the float you counted when the shift opened |
| + Cash sales | what cash sales took (change handed back is not counted), plus cash tips |
| + Paid in | |
| − Paid out | |
| − Safe drops | |
| − Cash refunds | returns paid out of the drawer during the shift |
| = Expected in drawer |
The variance is what you counted minus what was expected: positive means the drawer is over, negative means it is short. Print either report on your receipt printer from its dialog.
Shift history
Commerce → Orders → Shift history lists each register's shifts, newest first, with net sales, expected and counted cash and the variance. Click a closed shift for its Z report, and use Export CSV for a spreadsheet of the shifts listed.
Day and event totals
When several people take payments on their own registers, Commerce → Orders → Day totals adds the whole day up across every register, shift and cashier. It opens on today, counted in your site's time zone. Pick From and To dates to see another day or a whole event, up to 31 days at a time, and Today to come back.
- Totals: orders, gross sales, discounts, tax, tips, refunds and net sales. Only sales rung at a register count; online orders don't.
- By tender: cash, card, gift card, room charge and store credit, each with what it took, what was refunded to it, and the net.
- By register and by cashier: each register's and each staff member's orders, gross sales, tips, refunds and net sales. Every table sorts by any of its columns.
- Cash drawers: the starting cash of the shifts that opened on those days, cash sales, paid in, paid out, safe drops and cash refunds, then what the closed drawers should have held against what was counted, and whether they came up short or over. Drawers still open show what they should hold now.
- Shifts: every shift that opened, closed or was still open on those days, with its register, times, starting cash, net sales, expected and counted cash and the variance.
Sales count on the day they were rung, and refunds on the day they were given back, whenever the sale was and wherever the refund was given: at a register, from the order's Refund button in Commerce → Orders, or in your Stripe Dashboard. A refund from the order or from Stripe counts under the register the sale was rung at, under the person who gave it (Stripe refunds show as No cashier recorded), and against the card it went back to. It moves no cash drawer, so shift reports leave it out. The day is your site's, so a refund at 11:59 PM counts that day and one at midnight counts the next. Export CSV downloads the report as a spreadsheet, and Print prints it on an 80 mm receipt printer like a Z report.
Day totals need the point of sale on your plan, and only members who can use the register can see them.
Requiring a shift
Turn on Require an open shift to sell in Admin → Plugins → Commerce to have a register refuse sales, and cash refunds, until someone opens a shift. Off by default.
Who rang it
Every sale records the cashier who rang it, the shift it was rung in and any discount's author. After a PIN switch, that is the person who switched in, not whoever is signed in on the tablet.
Check-in at the window
For a track, a campground, a lot or an event: people who bought a day pass, camping or parking online, or at the register, are looked up at the window, checked in and handed a wristband.
Choose what needs check-in. In the product editor, under Check-in, turn on Needs check-in for a ride pass, a camping spot or parking. People per item says how many people one item admits: buy 3 of a pass with 1 person per item and that is 3 check-ins; a family camping spot set to 4 admits 4. A product with options can set each variant on its own, so a spectator ticket on the same product needs no wristband. Turning it on also covers what was already sold today.
Let buyers pick the day. Under Check-in, turn on Ask the buyer which day to sell passes ahead. The product page then offers an optional Day you will use it date picker, from today (on your site's calendar) up to two years ahead, never a day that has passed. A buyer who leaves it blank gets a pass for the day they buy. Each day is its own line in the cart, the cart and the order show the day ("For Sat, Nov 1"), and checkout turns away a pass whose day passed while it sat in the cart. A variant with its own check-in setting has its own Ask which day switch. Sales at the register are for the day they are rung.
What is due on a day. Each paid order's check-in items are due on the day the buyer picked, or, when they picked none, on the day the order was placed, counted in your site's time zone, whether it was bought online or at the register. Guests whose stay covers the day are due too, one check-in for each day of the stay, or one for each guest (see Stays: one check-in or one per guest below). An item refunded on its own, or an order refunded in full or canceled, is no longer due; anyone already checked in stays on the list.
Rain checks. When weather or a closed track means a pass can't be used, give it a rain check instead of a refund: tap Rain check beside the person at the register, or in Today's check-ins, then pick one of these:
- Open: good on any later day until it is used. The pass stays on its day, marked Rain check, and no longer counts as expected there. On any later day, searching for the person finds it, and checking them in uses it that day.
- Move it to a day. Pick the new day: a day after the one the pass is on that has not passed. The pass leaves its day's list and is expected on the new day.
Each rain check records who gave it, when, and the day the pass was on. Undo rain check puts the pass back on that day. Undoing the check-in of a used rain check opens it again. Rain checks are for passes; change a stay's dates on the Reservations card. Check in all leaves open rain checks alone, so each is used on purpose.
At the register, tap Check in, then search by name, email, phone (or its last four digits) or order number. Pick the customer to see each person their passes, camping and stays cover today. Type an optional wristband number and pick a color, then tap Check in, or Check in all. Someone already checked in shows when and by whom ("Already checked in at 9:14 AM by Sam"), and Undo takes a check-in back. After a PIN switch, the check-in is recorded under the person who switched in. On a day you are checking people in, attaching a customer to a sale who has someone due today offers Check in on the customer panel too.
Stays: one check-in or one per guest. A stay can be checked in once, with one wristband, or one guest at a time, each with their own check-in and wristband. Set it for each resource with At check-in in its editor on the Reservations card (One check-in per stay, the default, or One check-in per guest). To set every stay at once, use Stays at check-in on Today's check-ins: As each resource is set, One per stay or One per guest. The change shows on the list straight away; anyone already checked in stays checked in. Checking in per guest uses the stay's guest count, which guests enter when they book with the Reservation widget and staff enter on a walk-in. A stay with no count gets one check-in.
When a stay's guests change. If a family turns up with one more or one fewer, choose Guests on the stay's row in Today's check-ins or in the register's Check in window (or on the stay in the Reservations card) and save the new count. When the stay is checked in per guest, today's list follows at once, and so does any later day already on the list: an added guest gets their own check-in, and a guest who is no longer coming is taken off only if they haven't been checked in. Someone already checked in always stays. If the new count is lower than how many are already checked in, it is refused and says how many are in; undo a check-in first if that is what you meant. Days before today stay as they were.
Commerce → Orders → Today's check-ins lists everyone due on a day with what they are checked in for, the time, who checked them in, the wristband and any rain check, with expected, checked-in and still-to-come counts, and a Rain checks count when a pass on that day has an open one. Pick a Day to see another one. Every column sorts, Export CSV downloads the list as a spreadsheet, and Print prints it on an 80 mm receipt printer.
An order placed online shows up at the window within about 30 seconds; a sale at the register shows up the moment it is paid. Check-in needs the point of sale on your plan, and only members who can use the register can check people in or see the list.
Staff PINs
A shared tablet stays signed in; each person switches in with their own PIN instead of signing out.
- Set your 4–6 digit PIN on the Staff PINs card on Products → Point of sale. A PIN that is one digit repeated or a straight run like 1234 is refused.
- At the register, tap Switch cashier, pick your name and enter your PIN. Every sale, shift and return you ring is recorded under you until someone else switches in.
- A PIN never grants more than your role: the register checks your role and your Manage POS permission each time it is used, so removing someone's access takes effect on their next tap.
- Five wrong PINs in a row lock that person out for 15 minutes. Anyone with Approve refunds over the register's limit can reset or remove anyone's PIN, which also lifts a lockout.
- Lock the register after (minutes idle) in Admin → Plugins → Commerce locks the register after that long without a tap, so the next person has to enter their PIN. Tap Lock to lock it yourself.
PINs are stored only as salted hashes and nobody can read them back, not even a workspace admin.
Customers at the register
Search the Customer field by name, email or phone to attach a customer to the sale. The register shows how many orders they have placed at your store and what they have spent. The order is saved under their email and their name, so it appears on their record, prints their name on the receipt and can have its receipt emailed.
New customer adds someone in a few taps (an email is required, a phone is optional). Adding a customer does not sign them up for marketing email.
The search reads the people your workspace keeps in the CRM. Without it you can still type an email for the receipt.
Returns and exchanges
Tap Return on the register, then type the order number, scan the barcode at the foot of the receipt, or enter the customer's email.
- Pick the items coming back, how many of each, and the reason.
- Leave Put the items back in stock on to restock them at the register's location.
- Refund. The money goes back to how the customer paid:
- Card — refunded through Stripe to the same card.
- Cash — paid out of the drawer; the register tells you how much to hand over, and the open shift counts it.
- Gift card — added back to the same gift card. A voided or frozen gift card cannot take a refund.
- Room charge — taken back off the stay's folio.
A sale paid more than one way is refunded to cards first, then gift cards and room charges, and to cash last. Turn on Split by hand to choose the amounts yourself; a payment can never take back more than it paid.
Each unit's refund is its price less its share of any discount, plus its share of the tax, so returning items one at a time refunds exactly what returning them together would.
Every register return is also listed under Returns, beside the returns customers ask for online, already marked refunded. Items a customer has already asked to return online are held for that return: the register shows them as In an online return and will not refund them a second time.
Exchanges: after the return, tap Ring up the exchange to start a new sale for the same customer.
Refund limits and manager approval
Cashier refund limit ($) in Admin → Plugins → Commerce is the largest return a cashier may refund without a manager. It is $0 by default, so every register refund needs a manager until you raise it. Above the limit the register asks someone with Approve refunds over the register's limit to enter their PIN to approve that one refund, and anyone who holds it has no limit. By default that's an admin of the whole workspace who is also the site's admin. See Order permissions.
Printed receipts
Receipts print on any 80 mm receipt printer through your browser's print dialog. Each receipt has your logo and store name, the order number and its barcode, the date, cashier and register, the customer's name, every item, discounts, tax, the total, how it was paid (card with its last four digits), the tip and change, and your receipt footer from Products → Checkout. Two more lines are set in Admin → Plugins → Commerce: Address on printed receipts, printed under your store name, and Return policy on printed receipts, printed at the foot.
- After each sale, the register shows Print receipt and Gift receipt for that sale until the next one completes.
- Gift receipt prints the items and the barcode without any prices.
- Reprint any register sale from its order on the Orders page: open the order and use Print receipt or Gift receipt.
Most network receipt printers open the cash drawer cabled to them whenever they print, so printing a cash sale's receipt also opens the drawer. That is a setting on the printer.
Selling while offline
When the register loses its connection it keeps selling cash. A banner across the top of the register says it is offline and how many sales are waiting on the device.
- What still works: the product grid, search and barcode scans (from the catalog the register saved while it was online), the basket, the cashier's discount up to your register limit, your store's own tax rate, and cash. The receipt prints through the browser's print dialog, and its barcode is the one the order answers to once it syncs.
- What is off until the connection returns: card readers, Tap to Pay, typed cards, the QR card link, gift cards, store credit and rewards, room charges, discount codes and store promotions. Card payments need the connection, a gift card or store credit balance can only be checked online, so neither is redeemed offline, and codes and promotions are counted against their limits online.
- When the connection returns, the register sends its saved sales on its own. Each one becomes a paid order, dated when it was rung, in the shift it was rung in and under the cashier who rang it. The emailed receipt goes to the customer then. Cloud receipt printers print nothing for a synced sale, and its drawer does not open again.
- A sale is never lost and never counted twice. It stays on the device until your store has recorded it, and sending it again (a connection that comes and goes) records it once.
What the sync checks
The customer has already paid, so the sync records the sale as it was rung and says what you should look at, on the order and in the register:
- Stock that went short: more was sold than the shelf held, for example because the website sold the last one meanwhile. The order lists the item and how many were short.
- A price that changed after the register saved the catalog (the sale keeps the price it was rung at), or a product deleted since.
- A shift closed before the sale synced, so its Z report does not include that cash.
- A discount above the register's limit, tax that differs from your store's rate now, or a device clock that was wrong.
- A discount given by a member whose role does not include Give discounts at the register. The register refuses that discount while online; offline the sale has already happened, so it is recorded and flagged for you to review.
Cards taken offline in the Aglyn POS app
With Take cards offline in the point of sale app turned on in your POS settings, the Aglyn POS app's own card reader saves each card while the connection is down, and Stripe charges it once the app is back online. This is for stores on a platform-managed (Express) account, set up before stores got their own Stripe account: in the iOS and Android apps, cards can't be taken offline yet for a store on its own Stripe account. Cash sales rung offline work on both. The sale syncs right after, and:
- The card is charged like a card taken online. The platform fee is deducted from that card's payout. If Stripe took less than that fee from the payout, the rest is added to your next monthly invoice and the order says so. The sale can be refunded from the order, and a chargeback on it is matched to the order, like any card sale.
- A card the bank declined, or that could not be charged, is recorded as an unpaid order, and the register says so. Collect it another way at the register: the payment you take carries the fee for its tender, as on any other sale, and the stock is not taken off the shelf a second time.
- A card set to pay a Stripe account that is not your store's (for example, one taken before you reconnected Stripe) is not charged into your store. The order is recorded unpaid, and Aglyn is alerted to check it.
- A charge that differs from the order's total: the order shows what Stripe took and asks you to check it against the receipt.
- A card that reached Stripe but whose sale never synced, for example because the app was not opened again by the member who rang it: about six hours later your site's managers get a notification. Open the app that took it, signed in as that member, so the sale syncs. A card that was approved but never charged is released about two days after it was taken.
Before you go offline
- The register needs to have been online on that device once, so it has the catalog and your store's rules. It refreshes them regularly while online.
- Your store needs a tax setting (your own rates, or no tax). A store using Stripe Tax cannot ring in-person sales, online or offline.
- If your site requires an open shift, open it before the connection drops.
- Offline sales are kept in the browser on that device, for the member who was signed in. In a private window, or where the browser blocks site data, the register says offline selling is unavailable.
- Keep the register page open. Reloading the page while offline shows the console's offline page; the saved sales are kept and send when you open the register again with a connection.
- A sale syncs only for the member who was signed in when it was rung.
- PINs are checked online, so a register that locks itself while offline stays locked until the connection returns. Set the auto-lock to suit how you trade.