Installing a POS system is usually described as a list of steps that end with the word connect. What actually decides whether the installation holds for a year is a set of nine configuration items, none of which appears in a quick start guide and each of which produces a specific fault when it is left at the default.
The nine items, and what each one breaks
All nine are set once, at installation, and then forgotten. That is exactly why they cause trouble: when the symptom appears three months later, nobody connects it to a checkbox that was left alone on the first afternoon.
| Item | Default behaviour | What to set | If left alone |
|---|---|---|---|
| Terminal address | DHCP | Fixed IP, or a DHCP reservation on the router | After a power cut the kitchen display cannot find the printer |
| Printer interface | Auto | The actual interface and speed in use | Receipts print as garbage characters, or not at all |
| Firewall | On, blocking inbound | An explicit rule for the POS and the printer port | The terminal works alone but the KDS or the back office never connects |
| Time zone and clock | Factory default, often UTC | Local zone, automatic time sync on | End-of-day falls on the wrong date; HTTPS calls fail on certificate checks |
| Tax rules | Single flat rate | Every rate, plus inclusive or exclusive pricing | Totals differ from the previous system on mixed-rate baskets |
| Language and codepage | English, Western | The character set the receipts need | Accented or non-Latin characters print as symbols |
| Display resolution | Native | Native, and recalibrate touch afterwards | Taps land a centimetre from where the finger is |
| Automatic updates | On | Off, applied manually on a quiet morning | The terminal restarts at 12:30 on a Saturday |
| Backup | None | A scheduled export of the catalogue, prices and tax table | A re-image means re-entering the whole menu by hand |
Addressing: why fixed addresses are not optional
A POS system is not a set of independent devices, it is a set of devices that have to find each other. When the terminal, the printer and the kitchen display all get their addresses from a lease, any one of them can come back with a different address after a power cut, and the others keep trying the old one. The result is a fault that appears only after an outage and disappears after a reboot, which is the hardest kind to explain to staff.
Two ways to fix it, and either is fine. A static address on each device, which requires somebody to keep a list and to remember not to reuse an address. Or a DHCP reservation, where the router hands out the same address to the same MAC address every time, which keeps everything in one place and avoids the list. The second is easier to maintain and is what most small sites should do.
The one address that must be static
The printer or the print server. Everything else can move; if the printer address changes, every terminal that sends a receipt to it stops printing at once, and the symptom is a terminal that looks connected and produces nothing.
The printer: interface, speed and the garbage character problem
Thermal receipt printers can be reached over USB, serial, Ethernet or Bluetooth, and each path has its own configuration. The failure mode that confuses people most is the one where a receipt of sorts comes out: characters that are recognisable as letters but in the wrong order, or a single line of symbols. That is a speed or protocol mismatch rather than a broken printer.
| Connection | What must match | If it does not match |
|---|---|---|
| Serial (RS232) | Baud rate, data bits, parity, flow control | Garbage characters, or nothing at all |
| USB | The virtual COM port number, which can change between devices | The software prints to a port that no longer exists |
| Ethernet | IP address and TCP port, commonly 9100 | The job waits in the queue and never prints |
| Bluetooth | Pairing, and the printer must be awake when the job is sent | Intermittent missing receipts, worse with several devices paired |
The common speeds are 9600, 19200, 38400, 57600 and 115200 bits per second. They must match exactly on both ends; there is no negotiation, unlike Ethernet. If a printer came from another installation, its stored speed travels with it, which is why a printer that worked yesterday can produce garbage today after being moved.
Firewall and ports: the reason the KDS never connects
A terminal that can reach the internet but not the kitchen display is almost always a firewall question. The operating system blocks inbound connections by default, and a POS installation that works one-way will look half-working: sales go through, the kitchen never sees the order.
| Purpose | Port | Direction | Notes |
|---|---|---|---|
| Raw printing | 9100 TCP | Terminal to printer | The most common direct print path on Ethernet printers |
| LPR printing | 515 TCP | Terminal to printer | Older path, still common on Windows |
| IPP printing | 631 TCP | Terminal to printer | Usually with a driver rather than raw data |
| Kitchen display | Vendor-specific, often 8080 or 3000 | Terminal to KDS | Check the vendor documentation rather than assuming |
| Back office sync | 443 TCP | Terminal to server | Outbound only, usually already allowed |
The practical approach is to add explicit rules for the local subnet rather than to switch the firewall off. Turning it off does make the problem disappear, and it also means the terminal is unprotected on a network that staff phones also use.
Time, tax and language: three settings that produce accounting errors
These three share a property: when they are wrong, the system still works, and the error shows up in the books rather than on the screen.
Time zone first, because it corrupts everything downstream. A terminal left on a factory default zone puts the end-of-day cut at the wrong moment, so a Saturday night’s sales split across two reporting days. It also breaks HTTPS calls, because a clock that is wrong by hours fails certificate validation, and the error usually reads as a connection failure rather than a time problem.
Tax second. The settings that matter are not just the rates but whether prices are entered tax-inclusive or tax-exclusive, and how a basket that mixes rates is rounded. Two systems that agree on every rate can still disagree by a cent on a mixed basket, and a cent per transaction is a real number by the end of a month.
Language and codepage third. Thermal printers take a character set, and a receipt that needs accented characters or a non-Latin script will print as symbols if the codepage is wrong. The width available also matters: an 80 mm roll gives about 72 mm of printable width and roughly 48 characters per line at the usual font, and a 58 mm roll gives about 48 mm and 32 characters. A long product name will wrap, and where it wraps is decided by the printer, not by the software.
Resolution, touch and the calibration nobody does
Changing the display resolution after setup is a common cause of a touch screen that is off by a centimetre. The touch layer maps physical positions to screen coordinates, and that mapping is calibrated for the resolution that was active when it was set. Change the resolution and the mapping is stale: the pointer appears offset, usually further from centre as you move towards the edges.
Two rules follow. Do not change the resolution after installation unless you can recalibrate, and if you do change it, recalibrate immediately and test all four corners rather than the middle. A screen that responds correctly in the centre and badly at the edges passes a casual test and fails at the payment button.
Updates, backup and permissions
Three settings that are about the future rather than the present. Automatic updates should be off on a terminal that takes payments, not because updates are bad but because the timing is uncontrolled. Apply them yourself, on a morning when the shop is closed, and keep a note of which unit is on which version.
Backup should cover the four things that are expensive to recreate: the product catalogue, the price list, the tax table and the staff list. Everything else can be rebuilt. A scheduled export once a week to a file that lives somewhere other than the terminal is enough, and it is the difference between a two-hour recovery and a week of re-entering a menu.
Permissions should have three levels at minimum: cashier, supervisor and administrator. The point is not distrust. It is that a void, a discount and a price change each need to be attributable to somebody, and a system with one shared login cannot attribute anything.
The receipt that proves the installation works
One test transaction, printed, containing seven elements. If all seven are present and correct, the installation is done. If any is missing, the corresponding setting was skipped.
| On the receipt | Proves |
|---|---|
| Correct local date and time to the minute | Time zone and clock sync |
| Two tax lines on a mixed basket, each with the right rate | Tax configuration |
| Correct rounding on the total | Rounding rule and inclusive or exclusive pricing |
| A product name with its full characters intact | Language and codepage |
| The shop name and address, wrapped sensibly | Paper width and line length |
| A line that says which terminal and which cashier | Permissions and device naming |
| A barcode or QR printed at the right size and readable | Print density and alignment |
Keep that receipt. When something goes wrong in month four, the first question is always whether it ever worked, and a printed receipt with a date answers it.
FAQ
How long does a POS installation take?
The hardware takes an afternoon. The nine configuration items take another half day, and the tax and catalogue work takes as long as the menu is complicated. Installations that finish in two hours usually skipped items five to nine.
Do I need a fixed IP address for every device?
Every device that another device has to find. That is at minimum the printer and the kitchen display. A terminal that only talks outbound can stay on DHCP, though a reservation costs nothing and removes a class of future problem.
Why do receipts print accented characters as symbols?
The printer is using a different codepage from the software. Thermal printers do not detect this; the setting has to be sent explicitly. Change it on both sides, then reprint the test receipt before assuming it is fixed.
Where to go next
Nine settings, one test receipt with seven elements on it. That receipt is the acceptance document for the whole installation.
The four startup stages and what each failure means Wiring a cash drawer to the right kick-out voltage Thermal receipt printers by paper width and interface · what happens between the button press and the drawer · how a thermal printer prints without ink · what each part adds to the bill
Specifying the hardware? The hardware side is covered in Cafe POS, station by station — how 48 characters on a ticket change the printer you need.