Terminal Management

A terminal is a named till at a branch — "Counter 1", "Window", "Kiosk". It is not the same thing as the tablet: the terminal is the record Kassly keeps, and a device gets paired to it. That distinction is the whole of this section, and it is the thing worth understanding before your first device breaks.

Terminals live at Management → Terminals. Only the Owner can add, edit or delete one. Owners and Managers can unlink a device. Cashiers can see the list, because they choose a terminal when they open a shift.

What a terminal is

Each terminal keeps its own receipt counter. Receipt numbers have to run in an unbroken sequence per till, so the counter belongs to the terminal record and never resets — not when a device is replaced, not when the app is reinstalled. It also accumulates a lifetime sales total and a Z-reading counter.

This is why the terminal record outlives the hardware. Treat a terminal as the position at the counter, and the tablet as a consumable that sits there.

Adding a terminal

Management → Terminals → Add Terminal.

Field	Required	Rule
Branch	Yes	A terminal belongs to exactly one branch and cannot be moved between branches later without editing it
Name	Yes	Up to 255 characters, unique within that branch
Status	No	Active, Inactive or Deactivated. Defaults to Active

Under those is a BIR Registration section. Leave it empty unless your store is BIR-accredited and you have been given these numbers:

Field	Limit
MIN	50 characters — the Machine Identification Number
PTU Number	50 characters — the Permit to Use number
Serial Number	100 characters — the device's serial
Registration Date	A date
Device Brand	100 characters, e.g. Sunmi
Device Model	100 characters, e.g. V2 Pro

Once your store is accredited, the MIN and serial number print on every receipt this terminal issues. Before accreditation they are stored and print nothing. See Store settings for what a receipt looks like at each stage.

Pairing a device

There is no pairing code to type. Pairing happens by itself the first time someone opens a shift.

1. You create the terminal here, on the web dashboard, and pick its branch and name.
2. On the device, someone with permission to open a shift signs in with their email and password and taps to open a shift. If the branch has only one terminal, it is chosen for them; otherwise they pick it from the Terminal dropdown.
3. The device pairs itself at that moment. Nothing to press.
4. After that, staff switch in with their four-digit PIN. They never need the owner's password again, and each person's sales are tracked separately under the same terminal.

A device does not have to pair successfully for the shift to open. If pairing fails — a flaky connection, usually — Kassly opens the shift anyway rather than blocking the sale. The device then shows as Not paired in the terminal list even though it is selling. Check the list after setting up a new device, and if it says Not paired, close and reopen the shift on a good connection.

Behind the scenes the device holds a token that lasts 72 hours and renews itself whenever the device is used, so a device in daily use never needs re-pairing. A device that has been switched off for longer re-establishes itself on the next PIN login without you doing anything.

The device also reserves a block of 500 receipt numbers at a time. That is what lets it keep selling with no internet — it already holds the numbers it needs. When the block runs low, it draws another on the next sync.

How many terminals you get

One terminal per branch, included. Not one terminal per store.

Branches	Terminals included
1	1
2	2
5	5

On the Free plan, with your one branch, that is one terminal — one device selling at a time. When you try to add a terminal beyond your allowance, Kassly refuses and tells you the limit is reached.

The refusal message says to upgrade your plan. Ignore that wording. There is nothing to upgrade to. What you actually need is either another branch or an extra terminal, below.

Inactive branches still count toward the allowance, so deactivating a branch does not cost you a terminal slot.

Buying extra terminals

When you're at your limit, the button at the top of the page changes from Add Terminal to Add another terminal, and opens a purchase dialog instead of the create form.

Price	₱100 per terminal, per month
How many at once	Between 1 and 10
Billing	Added to your subscription

Extra terminals are not tied to a branch — they raise your total allowance, and you can then create the terminal wherever you need it.

Watching your terminals

The list shows seven columns:

Column	What it tells you
Name	The terminal's name
Branch	Which branch it belongs to
Status	Active, Inactive or Deactivated
MIN	The BIR machine number, or a dash
Receipts	How many receipts this terminal has issued in its lifetime
Device	Not paired, or a green dot and the device's name
Last Seen	When the terminal last did something, or Never

Two of those are easy to misread.

The green dot means "a device is paired", not "the device is online now". There is no live connection indicator. A tablet that is switched off, or in a drawer, or lost, still shows a green dot until you unlink it.

Last Seen means the last time this terminal posted a sale or synced. It is not a heartbeat. A terminal that has been open all morning without a single sale will show a stale time, and that is normal. Read it as "last activity", not "last contact".

Kassly does not record which app version a device is running, so there is no way to tell from here whether a tablet is out of date.

For sales figures per terminal, use the terminal performance report, which needs the Business Reports add-on (₱400 per branch each month). Deactivated terminals stay in that report on purpose, so last year's numbers still add up.

Terminal status

Active, Inactive and Deactivated look like three levels of shutting a terminal down. They are not.

All three statuses do exactly one thing: anything other than Active is hidden from the terminal picker when someone opens a shift. There is no coded difference between Inactive and Deactivated — pick whichever label suits your records.

Changing the status does not cut off a paired device. It does not revoke the device's access, does not sign anyone out, and does not stop a device that is already selling. If you need to actually cut a device off, use Unlink Device.

Replacing a lost or broken device

This is the part to read before you need it.

Use Unlink Device. Do not create a second terminal.

The unlink button sits in the terminal's row, next to the edit pencil, and only appears when a device is actually paired. Confirming it:

• revokes the paired device's access immediately
• keeps the terminal record, its receipt counter, its Z counter and its lifetime total exactly as they were
• records how far the device had got through its reserved receipt numbers, so the gap is accounted for
• leaves the terminal free to pair with a new device on the next shift open

Then set up the replacement tablet the same way as the first: sign in, open a shift, pick the same terminal. It carries on the same receipt sequence.

Creating a new terminal instead is the mistake to avoid. It starts a second receipt sequence at your branch, consumes another slot from your allowance, and leaves you unable to delete the old one — because a terminal that has issued receipts can never be deleted.

Unlinking is not instant on the device itself. A tablet that is still running keeps working on the receipt numbers it already holds, and can keep selling offline until those run out. For a genuinely stolen device, unlink the terminal and change the PINs and passwords of everyone who used it. See Users and roles.

Deleting a terminal

You can only delete a terminal that has never issued a receipt — a mistake, a duplicate, a test. Once a single receipt has gone through it, Kassly refuses:

"Cannot delete terminal with existing receipts (BIR compliance)."

That is deliberate and permanent. Receipt sequences have to be accountable, and a deleted terminal would take its sequence with it. A retired terminal that has sold anything gets its status set to Deactivated and its device unlinked, and then it sits in the list as history.

You also cannot delete a branch while it still has terminals attached, so retiring a branch means dealing with its terminals first. See Branch management.