Troubleshooting POS Systems: A Step-by-Step Guide to Common Fixes

A POS system that freezes, drops the internet, or stops taking cards can halt sales in seconds. Troubleshooting POS systems means you find the cause fast and fix it before the line backs up. Most faults trace to power, connectivity, a peripheral, or a software glitch, and you can resolve many of them yourself.

Below you will find a quick-fix checklist, a seven-step diagnostic sequence, fixes for each common symptom, how to keep selling during an outage, what downtime costs, and when to call your provider or replace hardware.

Quick Fixes For a Failing POS System

POS system troubleshooting is the process of diagnosing and fixing the power, network, hardware, software, and payment problems that stop a point of sale from working. When your POS fails, work through these fixes in order. Most problems clear within the first few.

1. Check the power and cables.
2. Confirm the internet connection.
3. Restart the terminal.
4. Test the peripherals.
5. Read and note the error message.
6. Install pending software updates.
7. Contact your provider if the problem continues.

Seven Steps to Diagnose Any POS Fault

Work these seven steps in order. Each one rules out a common cause before the next, so you fix the fault with the least effort.

1. Check power. Confirm the terminal, printer, and peripherals are plugged in and switched on, and that the outlet or surge protector works.
2. Check connectivity. Confirm the terminal can reach the internet or local network. Restart the router and modem if other devices are offline too.
3. Restart the terminal. Power it down, wait about 30 seconds, then turn it back on to clear temporary glitches and free memory.
4. Isolate the failing device. Test peripherals one at a time and swap in a known-good unit or cable to find the faulty part.
5. Read the error message. Note the exact text or code before you act, because it points to the cause and speeds up support.
6. Update the software. Install any pending updates, then restart, since outdated software causes bugs and compatibility faults.
7. Escalate to support. Contact your provider with the error text and the steps you already tried when the fault survives the first six steps.

Troubleshooting Common POS Problems by Symptom

Find your symptom below and start there. Each one lists the likely causes, the fix, and when to escalate.

POS won’t power on

A POS that will not power on almost always has a power-delivery fault rather than an internal failure.

Likely causes: dead outlet, loose or damaged power cable, tripped surge protector, drained battery on a mobile terminal, failed power adapter.

When to escalate: no response after a confirmed-good outlet and adapter points to a hardware fault. Contact your provider.

POS running slow or laggy

A slow POS is usually caused by weak connectivity or an overloaded device, not by the software itself.

Likely causes: poor internet, too many background apps, low storage, unarchived transaction data, outdated software.

When to escalate: lag that persists on a fast connection after a restart suggests a hardware or database issue.

Frozen or unresponsive screen

A frozen POS screen is resolved in most cases by a forced restart.

Likely causes: memory overload, software bug, overheating, failing touchscreen.

When to escalate: dead zones or repeat freezes after updates point to failing hardware.

No internet or dropping connection

A connection drop stops most cloud POS functions and is usually a local network fault.

Likely causes: weak Wi-Fi signal, loose ethernet, router or modem fault, ISP outage.

When to escalate: a full ISP outage means you switch to offline mode (covered below) and call your provider.

Card reader not processing, or charged but declined

Payment failures come from the reader, the connection, or the processor, and a test transaction isolates which one. If your POS is processor-agnostic, some payment faults sit with your separate processor rather than the terminal.

Likely causes: unpaired reader, loose cable, dirty chip slot, outdated payment software, processor outage.

When to escalate: failures across all cards and methods point to the payment processor, not the POS.

Receipt printer not printing or jammed

Printer faults are usually paper, connection, or driver related and rarely need a replacement.

Likely causes: empty or misloaded paper, jam, loose cable, wrong or outdated driver, wrong default printer.

When to escalate: a printer that fails after a driver reinstall and a cable swap needs service.

Barcode scanner not reading

A scanner that will not read is most often a connection or configuration problem, not a broken unit.

Likely causes: loose cable, wrong scan mode, dirty or damaged lens, unmapped barcode format.

When to escalate: a scanner that also fails on a second terminal is defective.

Cash drawer won’t open

A stuck cash drawer is opened manually first, then diagnosed as a connection or mechanical fault.

Likely causes: obstruction inside the drawer, loose cable (many drawers open through the receipt printer), mechanical failure, POS command not firing.

When to escalate: a drawer that ignores both the manual lever and the POS command needs replacement.

Inventory not syncing or mismatched counts

Inventory mismatches come from sync failures or scan errors, not usually from the physical count.

Likely causes: dropped connection during sync, scanner misreading barcodes, manual entry errors, unsynced offline sales.

When to escalate: repeat mismatches after a clean sync suggest a database issue for your provider.

“POS unavailable” and other error messages

A “POS unavailable” error means the terminal cannot reach the service that processes transactions, usually a network or server problem.

Likely causes: lost internet, provider-side server downtime, a deallocated or logged-out device, a failed background service.

When to escalate: an error that returns after a restart with confirmed connectivity is a provider-side issue. Give support the exact error text.

Suspected data loss or breach

Missing records or a suspected breach is urgent, and the first priority is to stop further loss before you diagnose.

Likely causes: hard drive failure, malware, unsaved data after a crash, unauthorized access.

When to escalate: any confirmed unauthorized access needs immediate provider and processor notification.

POS Problems And Solutions: Quick Reference

Use this table to jump from a symptom to its first fix. It stays vendor-neutral, so it applies to any POS. Full steps for each row are listed above.

Keeping Your POS Running Without Internet

A POS with offline mode keeps taking sales during an internet outage by storing transactions locally and syncing them once the connection returns. Connectivity is the single most common cause of POS downtime, so offline mode is what decides whether an outage is invisible or costly.

During the outage:

1. Confirm the POS has switched to offline mode. Many cloud systems do this automatically.
2. Keep processing the sales offline mode supports, usually cash and, on some systems, card transactions held for later capture.
3. Record anything the system cannot process by hand, with item, price, and payment method.
4. Switch to a mobile hotspot if you need card processing back quickly.

After the connection returns:

1. Confirm the terminal is back online.
2. Force a sync so offline sales upload.
3. Enter any handwritten transactions.
4. Reconcile payments and inventory records against the day’s expected totals.

When to escalate: sales that fail to sync after the connection is stable need provider support before you trust the totals.

A POS with no offline mode stops selling the moment the internet drops, which is worth weighing against the downtime costs and the switch criteria covered below.

Information to Collect Before Calling Support

Support resolves faster when you hand over a full picture of the fault instead of “it’s broken.” Have these ready before you call:

• The exact error message or code, word for word.
• Which device or terminal is affected, and whether the others still work.
• When it started, and what changed just before it (an update, a power event, new hardware).
• The steps you already tried and what happened.
• Your account or store ID and the POS software version.

Handing this over cuts the back-and-forth and, on remote-capable systems, lets a technician connect and fix the issue without a site visit.

What POS Downtime Actually Costs

POS downtime is expensive even for a single store. A Retail TouchPoints study of 100 US retail operations managers (conducted by Censuswide) found that a single store loses roughly $855 per hour when a store system such as the POS goes down, and that returning it to service takes just over five hours on average.

Losses climb sharply during peak hours: one 2025 industry analysis put the average full-service restaurant at about $5,600 per hour of peak-time downtime, and a high-profile Square outage showed how fast a provider-side failure can stall thousands of merchants at once.

The cost is not only lost sales, because a slow or dead checkout also frustrates shoppers and chips away at the in-store experience you work to build. The takeaway for this guide is simple: the faster you work through the steps above, the smaller the bill.

Your POS Preventive Maintenance Checklist

Most POS failures are preventable with a short, regular routine.

• Install software and firmware updates on a set schedule, ideally outside business hours. The best cloud-based POS systems apply many of these automatically.
• Back up POS data daily, to both local and cloud storage.
• Put every terminal on a surge protector or an uninterruptible power supply.
• Keep hardware clean and ventilated, and clear dust from vents and scanner windows.
• Keep spare peripherals on hand: a printer, a card reader, and cables.
• Restart terminals on a regular schedule to clear memory.
• Give staff solid point of sale training so they can spot early warning signs and run the first-response steps themselves.
• Choose commercial-grade hardware and replace it within its 3 to 5-year lifecycle.

POS, Provider, or Processor: Who Fixes What

Not every POS problem is a POS problem. Knowing where the fault sits tells you who fixes it.

• It’s your setup when the fix is local: power, cables, Wi-Fi, a jammed printer, or a device that needs a restart. You handle these with the steps above.
• It’s your provider when the software fails, the server is down, an error returns after a clean restart, or sync breaks. Contact support with the details listed earlier.
• It’s your processor when payments fail across every card and method while the rest of the POS works fine. Because a processor-agnostic POS keeps payments separate from the software, the outage can sit with the processor rather than the terminal.
• It’s time to switch when outages are frequent, support is slow or hard to reach, there is no offline mode, processing rates keep climbing, or the hardware is past its lifecycle and failing. Start by comparing the best POS systems for your vertical.

KORONA POS is processor-agnostic and includes 24/7 support with remote diagnostics, so a technician can often resolve software faults without a site visit.

Final Takeaways on POS Troubleshooting

Troubleshooting POS systems comes down to a clear routine: check power and connectivity, restart the terminal, isolate the faulty part, and read the error message before you escalate. You can solve most problems yourself, but the ones you cannot are exactly where your provider earns its keep.

Slow or hard-to-reach support turns a five-minute fix into hours of lost sales, so support quality matters as much as the software. KORONA POS is processor-agnostic and backs its software with 24/7 support and remote diagnostics, so a technician can often resolve an issue before it costs you a shift. Start your free trial or schedule a demo to see how fast that support responds.

Frequently Asked Questions About POS Troubleshooting

How do I fix a POS that won’t connect?

Start by confirming another device on the same network can reach the internet. If it cannot, restart the router and modem, then the terminal. If it can, reseat the ethernet cable or move closer to the access point, and switch to a wired connection where possible. A mobile hotspot works as a temporary line until the main connection is stable.

Can a POS run without internet?

Many POS systems keep selling without internet if they have an offline mode. Offline mode stores transactions on the device and syncs them once the connection returns. Coverage varies by system, so cash sales usually work while live inventory sync and some card processing may pause. A POS with no offline mode stops taking sales the moment the connection drops.

How do I reset my POS?

Most POS terminals reset from a reboot option in the settings menu. If the screen is frozen, hold the power button until the device powers off, wait about 30 seconds, then turn it back on. Save any open work first where the system allows it. A reset clears temporary glitches without deleting your data.

Why is my POS so slow?

A slow POS usually points to weak connectivity or an overloaded device rather than the software. Run a speed test, close unused apps, and restart the terminal to clear memory. Check free storage, clear the cache, and archive old transaction data if your system supports it. Lag that continues on a fast connection after a restart suggests aging hardware.

What does “POS unavailable” mean?

A “POS unavailable” error means the terminal cannot reach the service that processes transactions, usually because of a network or server problem. Note the exact error text, check the terminal’s connection, and restart it. Confirm the device is still logged in and allocated, then check your provider’s status page for an outage. An error that returns after a restart with a working connection is a provider-side issue.

How do I clear my POS cache?

Open the settings or administrative menu and look for storage or memory management, then select the option to clear the cache. Clearing the cache removes temporary files that can slow the system or cause display errors. Restart the terminal afterward so the change takes effect. Your sales and inventory data stay intact.

How much does POS downtime cost?

A single store loses roughly $855 per hour when a store system goes down, based on a Retail TouchPoints study of US retail operations managers. Losses run far higher during peak hours, reaching thousands per hour for busy or multi-store operations. Faster troubleshooting and a reliable offline mode are the two biggest levers for cutting that cost.

Should I repair or replace my POS hardware?

Repair makes sense when a single component fails and the device is still within its service life, such as a printer, a card reader, or a cable. Replace the unit when failures repeat, parts are hard to source, or the hardware is past its typical 3 to 5 year lifecycle. Keeping a spare peripheral on hand lets you swap first and decide later. Persistent faults after a clean repair point to end-of-life hardware.