Category: POS Systems & Setup

Adding a second or third till is one of the best ways to shorten queues — as long as every register sells from the same product list and the same stock. In a local (offline-first) POS, that is achieved by running one shared database on a host computer and connecting the other registers over the store’s network.

This guide explains how a multi-terminal POS works on a local network, how to plan the host computer and network, how to set up additional registers, and how to protect the setup with backups and a recovery plan.

How a multi-terminal POS works

In a local multi-terminal setup, one computer is the host. It stores the shared database: products, prices, stock, sales and users. Every other register is a client that reads and writes that database over the local area network (LAN). When register 2 sells the last bottle of olive oil, register 1 sees the stock at zero immediately.

Because the traffic stays inside the store, this design does not need the internet for normal selling. It does, however, make the host computer and the network the two things you must get right.

Choosing and preparing the host computer

The host should be the most reliable machine in the store, not the oldest one in the back office.

• Storage: an SSD, with plenty of free space for the database and local backups.
• Network: wired Ethernet to the switch or router — never Wi-Fi for the host.
• Power: on a UPS, with sleep and hibernation disabled during opening hours.
• Updates: schedule operating-system updates outside trading hours so the host never restarts mid-sale.
• Firewall: allow the POS application to accept connections from the local network.
• Fixed address: reserve the host’s IP address in the router so clients always find it.

Planning the local network

A multi-terminal POS is only as dependable as the network between the registers and the host.

Network separation is also good security practice: the PCI Security Standards Council and security guidance aimed at small businesses consistently recommend keeping payment and POS devices away from guest and personal devices.

Using Wi-Fi for tablets and handheld devices

Wi-Fi is ideal for devices that move — a tablet used as a pop-up till, or phones used by waiters in a restaurant. A few rules keep it reliable:

• Use a business-grade access point placed centrally, not the router hidden in a cupboard.
• Walk the floor with a device and check signal strength in every corner before opening.
• Use a separate staff network with a strong password, distinct from guest Wi-Fi.
• Keep at least one fixed register on Ethernet so a Wi-Fi problem never stops all sales.

For restaurant use, see how handheld ordering and the kitchen display connect to the same local network.

Setting up additional registers, step by step

1. Install and configure the host with your products, users and settings. Confirm it sells correctly on its own.
2. Reserve the host’s IP address in the router and note it down.
3. Connect each register to the same network, preferably by cable.
4. Install the POS software on each register and choose the option to connect to an existing host or server.
5. Point each register to the host and log in with a cashier account.
6. Configure local hardware per register: its own scanner, receipt printer and cash drawer.
7. Run a cross-check: sell an item on register 2, then confirm the stock change on register 1 and on the host.
8. Test a host restart outside trading hours and confirm the registers reconnect.

Daily operation with multiple registers

• One login per person. Staff log in on whichever register they use, so every sale is attributed correctly.
• Cash per drawer. Count each drawer separately at closing and compare it with the sales recorded on that register.
• Shared stock, shared customers. A customer’s purchase history and credit balance are the same on every register.
• Central reports. Reports read from the host database, so they include every register.

Keeping a shared database fast

Small stores rarely hit performance limits, but a few habits keep every register responsive at peak times:

• Wire the critical path. Host, switch and fixed registers on Ethernet remove most latency spikes.
• Keep the host lightly loaded. Avoid running heavy backups, antivirus scans or downloads on the host during opening hours.
• Keep the catalogue tidy. Archiving discontinued products and removing duplicates keeps search quick.
• Watch disk space. A nearly full drive slows the database and can stop backups.

Securing the store network

• Change default passwords on the router, switch and access points.
• Keep the POS network separate from guest Wi-Fi, ideally on a different network or VLAN.
• Use individual staff logins on every register and lock screens when unattended.
• Keep the operating system and POS software up to date, applying updates outside trading hours.
• Disable remote-access tools you do not use; where remote support is needed, enable it only on request.

When to add another register

A simple calculation helps. If an average sale takes about 60 seconds at the till and your busiest hour brings 90 customers, one register can serve at most 60 of them without a queue building. A second register handles the peak with spare capacity. Watch two signals in practice: customers abandoning the queue, and staff waiting for the till while there is work elsewhere. If either happens regularly, an additional register — or a tablet used as a pop-up till during peaks — is usually worth it.

For the hardware each new register needs, use the POS hardware setup checklist.

Backups for a shared database

All registers depend on one database, so backing it up is non-negotiable. Apply the 3-2-1 rule — three copies, on two types of storage, one off-site — and automate it:

• Schedule an automatic backup every day after closing.
• Copy backups to a second device (external drive or NAS).
• Keep at least one copy off-site or in a cloud folder that is not permanently mounted.
• Keep several days of backups, not just the latest one.
• Test a restore every quarter on a spare computer.

Failure recovery plan

Write down what to do before you need it. Here is a simple plan for the most common failures:

Practise the host-failure scenario once. Knowing that you can restore yesterday’s data onto a spare laptop in under an hour turns a crisis into an inconvenience. For more on the trade-offs of local systems, read offline vs cloud POS.

Frequently asked questions

Related guides

• Offline vs cloud POS
• POS hardware setup checklist
• How to choose a POS system
• Multi-terminal feature

Sources and further reading

• PCI Security Standards Council — Document library (network segmentation guidance)
• Uniti — Protecting POS systems and maintaining PCI DSS compliance for small businesses
• U.S. Chamber of Commerce — The 3-2-1 backup rule
• Stripe Docs — Collect card payments while offline

Most POS problems in the first week are not software problems. They are a scanner that types into the wrong field, a cash drawer that never opens, or a printer that drops off the network every afternoon. A careful hardware setup prevents nearly all of them.

This checklist covers each device on a typical retail counter — what to buy, how it connects, how to test it — plus networking, power and a troubleshooting table you can keep behind the till.

How POS hardware fits together

Think of the counter as a hub-and-spoke layout. The POS computer is the hub; everything else connects to it directly or through the network. One detail surprises many first-time buyers: the cash drawer usually connects to the receipt printer, not the computer.

The POS computer or tablet

This device runs the POS software and, in an offline-first setup, holds the database. Choose for reliability rather than raw power:

• An operating system supported by your POS software (check the vendor’s list — for example Windows 10/11, macOS or Android tablets).
• A solid-state drive (SSD) for speed and durability.
• Enough USB ports for scanner, printer and display, or a powered USB hub.
• A wired Ethernet port if the computer will host the database for other tills.
• A touchscreen if staff will tap product buttons; a mouse works for low-volume counters.

Barcode scanners

Most retail scanners connect by USB and operate in keyboard (HID) mode: the scanner “types” the barcode digits followed by Enter, exactly as if a person had typed them. That is why they usually work without drivers — and why the cursor must be in the POS search or barcode field when you scan.

Test: open a text editor and scan a product — the digits should appear followed by a new line. Then scan in the POS and confirm the right product is added. If the suffix is wrong or characters are missing, most scanners can be reconfigured by scanning setup barcodes from their manual.

Receipt printers

Retail receipt printers are almost always thermal: no ink, just heat-sensitive paper. The two common paper widths are 80 mm (standard receipts, more columns) and 58 mm (compact counters). Most models use the ESC/POS command language, which the majority of POS software supports.

For a single till, USB is fine. For two or more tills, or a kitchen printer, Ethernet is usually the more reliable choice. Configure the printer in your POS settings, then print a test receipt and check the header, footer and paper cut.

Cash drawers

A standard cash drawer connects to the receipt printer with an RJ11/RJ12 (telephone-style) cable. When the POS completes a cash sale, it sends a “drawer kick” command to the printer, which sends an electrical pulse to open the drawer.

• Check that the drawer and printer use compatible connectors and voltage (most are 24 V).
• Enable “open drawer on cash payment” in the POS printer settings.
• Test with a cash sale. If the drawer does not open, try the drawer’s manual key and swap the cable before blaming the software.

Customer displays

A customer-facing display shows items and the total as they are scanned, which reduces disputes and speeds up payment. Options include a two-line pole display, a small second monitor, or a second screen built into an all-in-one terminal. Connect it, set it as the customer display in the POS, and check that it shows the basket during a test sale.

Some POS systems can also show promotions on the customer display between sales.

Label printers

If you sell loose, repackaged or imported goods without usable barcodes, a label printer pays for itself quickly. Direct-thermal label printers are the most common choice for shelf and product labels; thermal-transfer printers (with a ribbon) produce longer-lasting labels for items stored in heat or sunlight.

• Choose label sizes that match your shelf strips and product types before buying rolls in bulk.
• Print barcodes from the POS catalogue so the barcode on the shelf always matches the product record.
• Scan a freshly printed label at the till to confirm it reads first time.

See how labels are generated from your product list on the barcode labels page, and why consistent product identification matters in our retail inventory management guide.

Card terminals

Card terminals are supplied or approved by your payment provider. From a security standpoint, the safest arrangement for a small shop is a standalone, provider-approved terminal so that card numbers never pass through the POS computer. The PCI Security Standards Council lists approved payment devices, and your provider will tell you which self-assessment questionnaire applies to your setup.

• Place the terminal where customers can reach it comfortably and where the cashier cannot see PIN entry.
• Connect it to a stable network — wired if possible — and keep it away from guest Wi-Fi.
• Learn its offline behaviour before you need it: some terminals can store payments during an outage, with limits and risk on the merchant.
• Record the payment method in the POS for every card sale so cash and card totals reconcile.

Counter layout and ergonomics

A good layout shaves seconds off every sale. Place the scanner on the cashier’s dominant-hand side, keep the receipt printer within reach without stretching, and position the cash drawer so it can open fully without hitting knees or shelving. Turn the customer display towards the queue, and route cables under the counter with cable ties so nothing gets unplugged by accident. Finally, leave space for bagging — a crowded counter slows everyone down.

Networking and power

Even a single till benefits from a tidy network. With several tills, it becomes critical.

• Use wired Ethernet for the main computer, fixed tills and network printers.
• Give the main computer and network printers fixed (reserved) IP addresses in the router.
• Keep POS devices on a separate network from guest Wi-Fi.
• Put the main computer, router and switch on a UPS so a short power cut does not interrupt sales.
• Label every cable at both ends.
• Keep a 4G/5G hotspot available for card terminals and updates during an outage.

For setups with more than one till, follow the multi-terminal POS setup guide.

Troubleshooting common hardware problems

Complete POS hardware setup checklist

• Computer meets the POS requirements; SSD; dedicated to the POS.
• POS software installed and tested with demo data.
• Scanner tested in a text editor and in the POS.
• Receipt printer configured; test receipt prints with correct header/footer.
• Cash drawer opens on a cash sale.
• Customer display shows the basket.
• Fixed IPs reserved for the main computer and network printers.
• UPS installed for computer, router and switch.
• Label printer configured if you print barcode or price labels.
• Backups scheduled and one restore tested.
• Five test sales completed, including a cancellation and a reprint.

Need help deciding what to buy in the first place? Start with what a POS system is and how to choose one. To print your own barcodes, see barcode labels.

Frequently asked questions

Related guides

• What is a POS system?
• How to choose a POS system
• Multi-terminal POS setup
• Barcode scanner feature

Sources and further reading

• L-Tron — Barcode scanner interfaces: keyboard wedge
• SuperOps — What is a keyboard wedge?
• LaunchMyStore Help — POS hardware: receipt printer, barcode scanner, cash drawer
• PCI Security Standards Council — Document library

Every shop eventually loses its internet connection — a router fails, the provider has an outage, or a contractor cuts a cable down the street. What happens next depends almost entirely on where your POS keeps its data.

This guide compares cloud-first and offline-first (local) POS architectures, explains what each can and cannot do during an outage — including the important limits on card payments — and shows how to make either setup more resilient.

Two architectures, explained

A cloud-first POS stores the master database on the vendor’s servers. The till — often a tablet or browser — is a window onto that database, so most actions require a connection. Many cloud systems add an “offline mode” that caches some data and queues transactions until the connection returns.

An offline-first (local) POS stores the master database on a computer inside the business. Tills, scanners and printers talk to that computer directly or over the store’s local network. The internet is used for optional tasks such as software updates, licence activation, remote features or integrations.

What happens during an internet outage

Example: a grocery store’s connection drops at 5 pm on a Friday. With a local POS, the two tills keep scanning and the stock count stays accurate. With a cloud POS in offline mode, both tills continue selling from their caches, but stock levels only reconcile once the connection returns — so two cashiers can sell the last unit of the same item.

The card-payment limitation nobody mentions

Here is the part that applies to both architectures: a card payment cannot be authorised by the bank without a connection. Whether your POS is cloud or local, card acceptance during an outage is decided by your payment terminal and provider, not by the POS software.

Some providers offer a “store and forward” offline mode. The terminal records the card details securely and submits them once the connection returns. Providers are clear about the trade-off:

• Stripe’s Terminal documentation explains that offline payments are only authorised after the reader reconnects, and that the merchant assumes the risk of declines.
• Square’s help centre states that offline payments must be uploaded within a time limit (24 hours in the US for many readers) or they expire, and that declined offline payments cannot be recovered by Square.
• Both providers allow limits on the value of offline transactions, which is a sensible control.

Why a local database is more resilient

An offline-first system removes the internet from the critical path. That has three practical benefits:

• No waiting: product lookups and sales do not depend on a round trip to a remote server.
• No reconciliation surprises: stock updates immediately, even with several tills, because they all share one database on the local network.
• Data on your premises: you decide where the computer sits and how it is backed up.

The trade-off is responsibility. If the main computer fails, the store is affected until it is replaced or restored — which is why backups and a recovery plan are essential. Our multi-terminal setup guide covers this in detail, and the offline POS page explains how Poskio applies this design.

Backups: the other half of reliability

Cloud vendors back up their servers; with a local POS, backups are your job — ideally automated. A widely recommended approach is the 3-2-1 rule:

• 3 copies of your data (the live database plus two backups);
• 2 different types of storage (for example an external drive and a cloud folder);
• 1 copy kept off-site.

Equally important: test a restore. A backup you have never restored is a hope, not a plan. Schedule backups daily after closing and keep at least one copy that is not permanently connected to the POS computer, so ransomware or a power surge cannot reach it.

Hybrid setups: the best of both?

The line between the two models is not absolute. Some cloud products cache enough data to sell for hours offline, and some local products offer optional internet features such as remote reporting, automated report delivery or online assistants. When you compare products, ask two precise questions rather than accepting the label “cloud” or “offline”:

1. Which functions keep working with no internet at all — sales, stock, receipts, multiple tills, reports?
2. Which functions require the internet — and what happens to them during an outage?

The answers matter more than the marketing category. A local POS whose optional online features pause during an outage is still fully usable at the counter; a cloud POS whose offline mode cannot apply discounts or look up customers may leave staff improvising.

An outage procedure your staff can follow

Print this and keep it at the counter. In a stressful moment, a written procedure prevents improvisation:

1. Confirm the outage: check the router lights and whether other devices are online.
2. Keep selling: continue ringing up sales as normal on the POS.
3. Cash: accept cash as usual and keep the drawer count accurate.
4. Cards: follow the payment provider’s offline instructions and respect the maximum offline amount set by the manager. Above that limit, ask for another payment method.
5. Record: note the time the outage started and any offline card payments.
6. Escalate: contact the internet provider and switch on the backup hotspot if available.
7. Recover: once online, upload offline card payments immediately and check that none were declined.

Questions to ask about any POS offline mode

• Can I complete a full sale, including discounts and customer selection, offline?
• Do stock levels update immediately, or only after reconnection?
• Can several tills keep selling together without the internet?
• Are reports available during an outage?
• How long can the system run offline, and is there any limit on the number of sales?
• What happens to card payments taken offline, and who bears the risk of declines?

Reliability checklist for either architecture

• Put the main computer, router and switch on a UPS (battery backup).
• Use wired Ethernet for fixed tills; reserve Wi-Fi for mobile devices.
• Keep a 4G/5G hotspot or backup line for card payments and updates.
• Know your payment provider’s offline limits and set a maximum offline amount.
• Automate daily backups and test a restore every quarter.
• Keep a printed “outage procedure” at the counter: who to call, what to accept, how to record.
• Keep a small cash float so cash sales can continue smoothly.

Offline vs cloud POS: summary comparison

Which should you choose?

Choose offline-first if internet reliability is a concern, speed at the till matters, or you prefer to keep data on site. Choose cloud-first if you manage several locations remotely and your connections are dependable. In both cases, plan for card payments during outages separately. For the full selection process, see how to choose a POS system.

Frequently asked questions

Related guides

• What is a POS system?
• Multi-terminal POS setup
• POS hardware setup checklist
• Offline POS features

Sources and further reading

• Stripe Docs — Collect card payments while offline
• Stripe Support — Terminal offline mode FAQ
• Square Help — Offline payments time limits
• Federal Reserve — Offline payments: implications for reliability and resiliency
• U.S. Chamber of Commerce — The 3-2-1 backup rule

Choosing a POS system is less about finding the product with the longest feature list and more about matching a system to how your store actually operates. The wrong choice shows up quickly: slow queues, stock figures nobody trusts, or a monthly bill for features you never use.

This guide walks through a practical selection process for retail stores — from writing down your requirements to testing a shortlist with your own products — and ends with a scoring checklist you can reuse.

Start with your operational requirements

Before looking at any product, describe your store in plain numbers. These answers eliminate most unsuitable systems immediately.

Example: a hardware store with 6,000 SKUs, two tills, several trade customers on monthly accounts and patchy internet has a very different shortlist from a boutique with 300 items, one till and a fibre connection.

A four-step selection process

1. List requirements using the questions above, split into must-haves and nice-to-haves.
2. Shortlist three systems that meet every must-have. More than three makes testing superficial.
3. Test with real data: load twenty of your own products, connect your scanner and printer, and run realistic sales.
4. Decide on total cost over several years, operational risk and how well the system fits the way your team works.

Essential features for a retail POS

Checkout speed

Time a full sale: scan five items, apply a discount, take payment, print the receipt. Look for barcode scanning straight into the basket, search that tolerates partial names, and the ability to park one basket while serving the next customer.

Product and price management

You should be able to organise products into categories and brands, store cost and selling prices, set taxes per product and import an existing list. Label printing from the same catalogue avoids price mismatches between shelf and till.

Customers and credit

Even small shops benefit from customer profiles and purchase history. If you let regulars or trade customers pay later, check that the system tracks outstanding balances and prints statements — this replaces the paper notebook behind the counter.

Reporting

A daily overview is the minimum. Growing stores need sales by product and period, purchase analysis, cash reconciliation and exports their accountant can use.

Check hardware compatibility early

Hardware problems are the most common reason a new POS disappoints in its first week. Confirm:

• Which operating systems the software runs on, and whether your existing computer meets the requirements.
• That your barcode scanner works in the system’s search field (most USB scanners act like a keyboard).
• That the receipt printer is supported and can trigger the cash drawer.
• Whether a second, customer-facing screen is supported if you want one.
• How the card terminal fits in: integrated, or a separate device where the cashier records the payment method.

The POS hardware setup checklist explains each connection type so you know what to ask vendors.

Inventory: ask how stock really moves

Ask vendors to demonstrate the full stock loop, not just a stock number on a screen:

1. Record a supplier delivery and show the quantity increase and saved purchase price.
2. Make a sale and show the quantity decrease.
3. Show the low-stock view and a history of stock movements for one product.

Once the system is live, the retail inventory management guide, cycle counting and shrinkage prevention articles show how to keep those stock figures accurate.

Staff management and accountability

Shared logins make it impossible to know who cancelled a sale or changed a price. Look for:

• An individual login for each employee.
• Roles that restrict sensitive actions — discounts above a limit, cancellations, price changes, settings.
• An activity log that records who did what and when.

See how this works in practice on our staff and permissions page.

Security and data protection

A POS holds sales history, customer details and sometimes payment data. Treat security as a selection criterion, not an afterthought:

• Card data: card payments should be handled by a validated payment terminal or provider so that card numbers never touch your POS computer. The PCI Security Standards Council publishes the rules merchants must follow; your payment provider will tell you which self-assessment applies to you.
• Network separation: keep POS devices off the guest Wi-Fi.
• Backups: confirm how data is backed up, where copies are kept and how a restore works. A common approach is the 3-2-1 rule: three copies, on two types of storage, one off-site.
• Access control: unique logins, strong passwords on the main computer, and automatic screen locking.

Questions to ask every POS vendor

Demos are designed to impress. These questions bring the conversation back to how the system behaves in your store:

1. What happens when the internet goes down? Ask them to show it: unplug the router during the demo and try to complete a sale.
2. Where is my data stored, and can I export it? You should be able to take your products, customers and sales history with you if you ever switch.
3. How are backups made and restored? Ask who is responsible and how long a restore takes.
4. Which hardware is supported? Get a written list of compatible scanners, printers and cash drawers.
5. How are updates delivered? Find out whether updates are included, how often they arrive and whether they can interrupt trading hours.
6. What does support look like? Ask about channels, response times and onboarding help for the first weeks.
7. Which features cost extra? Clarify which capabilities are included in the edition you are considering and which require an upgrade.
8. Which languages are supported on screen and on receipts? This matters for multilingual teams and customers.

Common mistakes when choosing a POS

• Buying for a hypothetical future. Choose for the next two years of realistic growth, not a five-location chain you may never open.
• Comparing monthly prices only. A low entry price can hide transaction fees, add-ons or hardware lock-in; compare multi-year totals.
• Testing with demo products. Your own barcodes, long product names and real price lists reveal problems that sample data hides.
• Forgetting the people. If cashiers find the screen confusing, they will work around it. Involve your most experienced employee in testing.
• Underestimating data migration. Moving products and customer balances takes time; plan it rather than discovering it on launch day.

Switching systems: a simple migration plan

1. Export products, customers and outstanding balances from the old system.
2. Clean the data: remove duplicates, fill missing barcodes, check prices and taxes.
3. Import into the new system and spot-check twenty products and five customer balances.
4. Run both systems in parallel for a quiet afternoon if possible, or complete test sales on the new one.
5. Switch on a low-traffic day, keep the old data archived, and review the first week of reports carefully.

Total cost of ownership

Compare costs over at least three years, not just the first invoice. Include software licences or subscriptions, payment processing, hardware, setup and training time, and the cost of downtime. A system with a higher upfront licence can cost less over time than a cheaper monthly plan — and the reverse is also true. Write the numbers down for each shortlisted product.

POS evaluation checklist

Score each shortlisted system from 0 (missing) to 3 (excellent). Weight the items that matter most to your store.

• Tested a full sale with my own products and scanner.
• Printed a receipt and opened the cash drawer.
• Recorded a delivery and checked the stock change.
• Disconnected the internet and tried to sell.
• Created a cashier account and checked what it cannot do.
• Ran a backup and understood how to restore it.

Frequently asked questions

Related guides

• What is a POS system?
• Offline vs cloud POS
• POS hardware setup checklist
• Multi-terminal POS setup

Sources and further reading

• PCI Security Standards Council — Document library
• U.S. Chamber of Commerce — The 3-2-1 backup rule
• L-Tron — Barcode scanner interfaces

A point of sale (POS) system is the combination of software and hardware a business uses to record sales, take payment and keep track of what it sells. If you run a shop, café or salon, it is the tool your team touches more than any other — and the one that decides whether your stock figures, cash counts and daily reports can be trusted.

This guide explains what a POS system actually does, step by step, what equipment it needs, how inventory fits in, the difference between cloud and offline systems, and a practical checklist for setting one up.

What is a POS system?

At its simplest, “point of sale” is the moment and place where a customer pays. A POS system is everything that supports that moment: the screen where a cashier builds the order, the software that calculates totals and taxes, the devices that scan products and print receipts, and the database that remembers every transaction.

Older cash registers only added up prices and stored cash. A modern POS system goes further: it links each sale to a product record, updates the stock count, attaches the sale to a customer if needed, records which employee made it, and feeds the numbers into reports. In other words, it is both a till and a lightweight business management system.

POS system vs. payment terminal

These two are often confused. The payment terminal (card reader) is the device that reads a customer’s card and talks to the bank or payment processor. The POS system manages the order: items, prices, discounts, receipts and stock. Some products bundle both; many businesses use a POS application together with a separate card terminal from their payment provider and simply record “card” as the payment method in the POS.

How a POS transaction works, step by step

Whatever the business, almost every sale follows the same six steps. Understanding them makes it easier to judge any system you are evaluating.

1. Build the basket. The cashier scans a barcode, taps a product button or searches by name. The POS looks up the product and its price.
2. Adjust. Quantities are changed, items removed, discounts applied. If the customer has an account, the sale is linked to them.
3. Take payment. The cashier records the payment method — cash, card on an external terminal, or another method — and the POS calculates change.
4. Issue the receipt. A thermal receipt prints (or an A4 invoice for a business customer). Good systems let you reprint any past receipt.
5. Update stock. Each item sold is deducted from inventory automatically, so the stock figure reflects reality without a manual count.
6. Report. The sale flows into daily totals, payment-method breakdowns and product performance reports.

Example: a convenience store sells two bottles of water and a sandwich. The cashier scans three items, the customer pays cash, the receipt prints, and the stock count for each product drops immediately. At closing, the daily report shows the sale under “cash”, which should match the drawer.

POS hardware: what you actually need

Hardware needs vary by business, but most counters are built from the same components. Start with the essentials and add the rest only when there is a clear reason.

Our POS hardware setup checklist covers each device, connection types and common troubleshooting in detail.

POS software: core features to expect

The software is where systems differ most. Beyond adding up a sale, these are the capabilities that matter in daily use:

• Fast checkout: product grid by category, search, barcode scanning, discounts, several open baskets at once.
• Product catalogue: categories, brands, cost and selling prices, taxes and barcodes.
• Customers: profiles, purchase history and — for many shops — customer credit and account statements.
• Staff management: separate logins, roles and permissions, and an activity log of sensitive actions.
• Receipts and documents: customisable receipts, A4 invoices, and for some businesses quotations, delivery notes and credit notes.
• Reporting: a daily overview at minimum, and ideally sales, stock and cash analysis plus exports for your accountant.
• Backups: a reliable way to copy and restore your data.

For a structured way to compare products on these points, see how to choose a POS system.

How inventory integrates with the POS

Inventory integration is what separates a POS system from a simple calculator. When the product catalogue and the sales screen share the same database, three things happen automatically:

• Sales reduce stock. No end-of-day data entry and no spreadsheet to reconcile.
• Purchases increase stock. Recording a supplier delivery adds quantities and saves the purchase price, which makes margins visible.
• Low stock becomes visible. You can see which items need reordering before shelves run empty.

The quality of the data depends on discipline: every product sold must be scanned or selected as itself, and deliveries must be recorded when they arrive. A weekly spot-check of a few fast-moving products is a simple way to catch drift early.

Read more about inventory management in a POS and recording supplier purchases. For the full method, see our retail inventory management guide and how to set a reorder point.

Cloud vs. offline (local) POS systems

POS systems store their data in one of two broad ways:

Neither model is automatically better. A shop with unreliable internet often values a local database; a chain that needs head-office dashboards may prefer the cloud. We compare both in depth, including what happens to card payments during an outage, in offline vs cloud POS.

Who needs a POS system?

Any business that sells in person benefits once it has more than a handful of products or more than one person at the counter. Needs differ by sector:

• Retail and grocery: barcode scanning, stock control and labels — see POS for supermarkets and grocery stores.
• Restaurants and cafés: table plans, kitchen screens and waiter ordering — see restaurant POS.
• Trade counters: large catalogues, customer accounts and quotations — see hardware stores and auto parts.

The POS in daily store routines

Once installed, the POS becomes part of every routine: opening the till with a float, recording deliveries, closing with a cash count, and reviewing the daily report. Our retail store operations guide covers these routines, and retail KPIs explains which numbers to watch.

Common mistakes when starting with a POS

Most problems with a new POS come from setup decisions rather than the software itself. Avoid these and the system will pay for itself quickly:

• Skipping product data cleanup. Duplicate items, missing barcodes and inconsistent names make search slow and reports unreliable. Clean the list before importing it.
• Sharing one login. Without individual accounts you cannot see who cancelled a sale or gave a discount.
• Not recording deliveries. If purchases are not entered, stock figures drift and low-stock alerts become useless.
• No backup plan. Whether your data is in the cloud or on a local computer, know how it is backed up and how to restore it.
• Ignoring training. Ten minutes per employee on the most common tasks prevents most day-one errors.

POS setup checklist

Use this checklist when installing a new system. Most small shops can complete it in a day if the product list is ready.

• Choose the computer that will hold the main database and keep it on a UPS.
• Install the POS software and, if available, explore it with demo data first.
• Enter business details, taxes, payment methods and receipt header/footer.
• Create categories, then add or import products with prices and barcodes.
• Connect and test the scanner, receipt printer, cash drawer and customer display.
• Create user accounts for each employee with appropriate permissions.
• Set up automatic backups and test a restore once.
• Run five test sales, including a discount, a refund or cancellation, and a reprint.
• Check the daily report against the test sales, then delete or void test data if needed.
• Train staff on the five things they do most: sell, discount, cancel, reprint and close the day.

Frequently asked questions

Related guides

• How to choose a POS system
• Offline vs cloud POS
• POS hardware setup checklist
• Multi-terminal POS setup

Sources and further reading

• PCI Security Standards Council — Document library (PCI DSS, SAQ B-IP)
• Stripe — Collect card payments while offline (Terminal)
• Square — Process offline payments
• L-Tron — Barcode scanner interfaces and keyboard wedge