Hardware today
The till runs in a browser, so it works with what a browser can talk to. This page says what that covers now.
| Hardware | Works today |
|---|---|
| Tablet, laptop or phone | Yes. Any current browser. |
| Receipt printer | Yes. Any printer the browser can print to. |
| Barcode scanner | Yes. One that types like a keyboard. |
| Card reader | Yes. Stripe Terminal, Square Terminal and SumUp Solo, and simulated readers for trying the till out. |
| Cash drawer that opens by itself | Not yet. |
| Customer-facing display | Not yet. |
The screen
The till is built for a landscape tablet and works on a laptop with a mouse. On a phone in portrait it is usable for a market stall. Buttons are at least 44 pixels high and nothing needs hover. It follows the device's light and dark setting.
Open /pos on the device and add it to the home screen. It then opens full screen with its own icon.
Receipt printers
Receipts and the X and Z reports are laid out for 80 mm thermal paper, with 72 mm of printable width, no page margins and one column. The till prints them through the browser's own print dialog.
To use a receipt printer, install it on the device the way you would any printer and choose it when the print dialog opens. Any printer that can print an 80 mm page from a browser will do. The till doesn't send commands to a printer itself.
Barcode scanners
Use a scanner that types like a keyboard and presses Enter at the end of the code. Most scanners do this out of the box and are described as keyboard wedge or HID mode. Plug it in or pair it by Bluetooth and scan.
The till counts a burst of four or more characters, typed quickly and ended with Enter, as a scan. This works anywhere on the Sell screen. The search bar keeps the cursor so a scan always lands. The codes it matches are:
- A variant's barcode (GTIN)
- A variant's SKU
- An order number, for returns
Receipts carry the order number as a Code 128 barcode, so a returned item can be found with a scan.
Card readers
Card readers come from payment providers. A provider that takes cards in person offers its readers in the Card reader list on a register. Each one needs the provider's add-on, KahunaCart 1.5.7 or later, and a reader paired to the provider's account. The till sends the amount, the customer taps or inserts, and the payment lands on the order like any other. Card details never reach your store.
| Reader | Provider add-on | Notes |
|---|---|---|
| Stripe WisePOS E, Stripe Reader S700 | Stripe 1.2.10 or later | Connects over Wi-Fi or Ethernet. Bluetooth and USB readers and Tap to Pay aren't supported. Stripe's test mode has simulated readers. |
| Square Terminal | Square 1.1.7 or later | The store gives you a code and you type it into the Terminal. A Terminal that times out can still finish a payment, so the till may show a timed-out payment as checking until the Terminal has moved on. |
| SumUp Solo | SumUp 1.1.6 or later | Live SumUp accounts need an Affiliate Key. SumUp's other readers, such as the Go, aren't supported. |
| Simulated readers | Test provider 1.2.9 or later | No account and no hardware. |
Each provider's page says how to pair a reader and what it can't do yet: Stripe, Square and SumUp.
When the provider can't say how a payment ended
A reader may be offline, or the provider may not know. The till then shows the payment as checking and keeps asking. If that never settles, a staff member can look at the reader or the provider's app and, if nothing was taken, give up on the payment and take it another way. See Taking payment.
The test provider's simulated readers
The test provider has simulated readers for trying the till out:
- Simulated reader 1 and Simulated reader 2 are there from the start.
- A payment finishes after about three seconds.
- An amount ending in .05 is declined and one ending in .09 times out.
Not there yet
- A cash drawer kick. The till doesn't open a drawer for you.
- A customer display. There is no second screen showing the customer their basket.
- Other card readers. Bluetooth and USB readers, Tap to Pay on a phone and SumUp's other readers aren't supported yet. Each provider's page lists what else is missing.