This training guide will walk you through how registers and payment terminals work within CityHive POS. Understanding device pairing is crucial for efficient and accurate transaction processing in your daily operations.

We'll begin by defining what registers are, covering any device used to ring up sales. Next, we'll discuss payment terminals, the physical hardware for processing customer payments. Finally, we'll delve into the critical concept of pairing, explaining why registers and terminals must be correctly matched every time.

A register in CityHive POS is essentially the point-of-sale screen where staff process sales, apply discounts, and finalize transactions. Unlike traditional systems, CityHive registers are not tied to specific hardware; they can run on any desktop, laptop, or mobile device. Each register is uniquely named in the system, allowing staff to select the correct one upon logging in. Ultimately, the register manages the sale itself, from scanning products to totaling the cart and applying various tender types.

A payment terminal is the physical hardware customers use to complete transactions by tapping, inserting, or swiping their cards. CityHive supports both handheld and countertop terminal models. Handheld terminals offer flexibility with battery backup, allowing them to be used untethered. Countertop terminals, however, require constant power and must remain plugged in. It's important to remember that the terminal's sole function is payment processing; it does not handle product scanning or item ringing itself.

CityHive offers remarkable flexibility, freeing you from being locked into specific hardware for checkout. Any computer, laptop, or mobile device can function as a full register. While registers and their paired terminals typically remain stationary in most stores, this flexibility truly shines in scenarios like curbside pickup, in-store events, or line busting during peak times, where you can quickly set up a register anywhere. The key to this flexibility is ensuring the system accurately knows which payment terminal is assigned to which register.

Every register must be assigned to one specific payment terminal within the system's settings. For example, if "Register A" is assigned to "Payment Terminal A," when staff select Register A for a sale, the system automatically directs the payment request to its assigned terminal. This routing occurs regardless of physical proximity. Therefore, it's crucial to confirm that the terminal in front of you is the one actually paired to the register you're using before starting your day. A helpful tip is to label each register with its paired terminal for an easy visual check.

Imagine you're on Register A, but Payment Terminal B is physically on the counter. Pairing is a software assignment, not based on physical location. The system will route the payment request to Terminal A, wherever it is configured, not to Terminal B. This means Terminal B, despite being right in front of the customer, will remain inactive, appearing "frozen" or unresponsive because it never received a transaction. The solution is always to align the physical setup with the system's configuration: either move the correct terminal to the counter or update the system pairing to reflect the terminal that is actually present.

A register is your checkout screen, and a payment terminal processes cards. Each register is assigned to one specific terminal, with payments routed to that assigned device. Always confirm your physical terminal matches the system pairing before opening a register.