Migrating off QuickBooks Desktop POS? See our why Intuit discontinued QuickBooks POS for the complete 2026 transition playbook.

Last Updated: May 2026

Quick Answer

The assumption that a modern point of sale system requires a dedicated hardware investment is one of the most expensive myths in small business retail. It keeps merchants locked into vendor relationships they have outgrown, delays upgrades that would pay for themselves in weeks, and generates capital expenses that sit on the balance sheet long after the software they support has been discontinued. This article makes the case against proprietary hardware with actual numbers and real operational examples.

• A browser-based POS system runs on any existing computer or tablet with no dedicated hardware purchase required
• Proprietary hardware creates vendor lock-in that costs merchants more in switching costs than the hardware itself
• The average small retailer spends between $800 and $2,400 per station on proprietary POS hardware that becomes worthless if they change platforms
• Card acceptance terminals are the only hardware a modern browser-based POS system actually requires and those are hardware-agnostic

There is a sales conversation that happens in retail technology that almost nobody talks about honestly. A merchant decides they need a better POS system. A vendor representative walks them through a demo. The software looks good. The integration claims sound right. Then the conversation turns to hardware and the merchant finds out that the system requires a specific tablet, a specific cash drawer connector, a specific receipt printer model, and a specific terminal that only works within that ecosystem. The merchant signs anyway because the software seemed worth it. Six months later the software is not working the way it was supposed to and the merchant is stuck because they just spent $3,000 on hardware that has no value outside the platform they want to leave.

That conversation happens thousands of times a year. It does not have to.

Where the Proprietary Hardware Myth Came From

The idea that a serious POS system requires dedicated hardware made sense in a specific era of retail technology. When POS software ran on Windows XP on a dedicated terminal with a proprietary database, the hardware and software were genuinely inseparable. The machine that ran the software was configured specifically for that software and nothing else. Replacing one meant replacing the other.

That era ended when browsers became capable of running complex web applications reliably. The same architectural shift that moved accounting software, project management tools, and customer databases to the cloud made it technically possible to run a fully functional point of sale system in a browser on any device with an internet connection. The software no longer needed the hardware. The hardware vendors just did not advertise that fact particularly loudly.

According to a 2024 report from Retail Dive, 64 percent of small retail businesses that purchased proprietary POS hardware in the last three years described the hardware cost as a significant barrier to switching platforms when their software relationship deteriorated. That is not a coincidence. It is a business model. Hardware lock-in is one of the most reliable retention mechanisms available to a POS software vendor that is not confident enough in its product to retain merchants on merit alone.

What a Browser-Based System Actually Runs On

A browser-based POS system runs on Chrome, Safari, Firefox, or Edge on any computer, laptop, or tablet with a stable internet connection. That means the device already sitting at the counter in most retail operations is already compatible. No configuration required beyond opening a browser and logging in.

For merchants who went through the QuickBooks POS discontinuation in 2023 and invested in proprietary hardware as part of their replacement decision, this is the part of the conversation that tends to land with some frustration. The hardware investment they made was not necessary. It was a feature of the platform they chose rather than a requirement of running a modern POS system.

The practical implication of hardware independence is significant in both directions. A merchant who already has a tablet at the counter does not need to buy anything new to get started. A merchant who wants to add a second register does not need to purchase a second dedicated terminal. A merchant who decides a year from now that they want to switch platforms does not have a hardware write-off standing between them and that decision.

The Only Hardware a Modern POS System Actually Requires

Separating the POS software from the hardware question clarifies what hardware a merchant genuinely needs versus what a vendor bundles into the relationship to create switching costs.

The actual hardware requirement for a modern retail checkout is one thing. A card acceptance device that can read chip cards, process tap payments, and handle PIN debit. That is it. Everything else, the computer, the screen, the keyboard, the receipt printer if one is needed, already exists in most retail environments and does not need to be replaced when the software changes.

The physical card readers that pair with a browser-based system are hardware-agnostic in the sense that they connect to the software through a network rather than through a proprietary software driver. The PAX terminal line covers stationary setups with ethernet and WiFi connectivity, mobile setups with 4G and battery operation for merchants who work markets or outdoor events, and configurations with built-in receipt printers for businesses that need paper records at the point of sale.

The Standard Package starts at a one-time purchase of $285 for a PAX A80 terminal covering a single location with up to two concurrent registers. The Premium Package at $575 includes the PAX A920Pro with battery operation and multi-location capability. Those are the hardware costs. The computer running the software is whatever the merchant already owns.

What Hardware Lock-In Costs Over Three Years

The financial argument against proprietary hardware becomes clearest when the total cost of ownership is spread across a realistic operating window.

A merchant who purchases a two-station proprietary POS setup with dedicated tablets, cash drawer connectors, and receipt printers at $1,200 per station has spent $2,400 on hardware before the first transaction is processed. If the software relationship lasts three years before the merchant decides to switch, that $2,400 was a three-year lease on a vendor relationship with a $0 residual value at the end of it.

The same merchant using a browser-based system on existing hardware and a $285 card terminal has spent $285. If the software relationship lasts three years and the merchant decides to switch, the $285 terminal either works with the new platform or is replaced for another $285. The switching cost is measured in hundreds rather than thousands.

This is not an abstract exercise. It is the actual financial difference between a hardware-dependent POS relationship and a hardware-independent one, and it repeats every time a merchant considers making a change. The multi-vendor fragmentation problem that traps small retailers in underperforming setups is partly a software problem and partly a hardware problem. Removing the hardware component removes one of the stickiest parts of the trap.

The Robustness Argument That Hardware Vendors Do Not Want You to Think About

Proprietary hardware vendors often make the argument that a dedicated system is more reliable than a browser-based one because it is not dependent on internet connectivity and does not share resources with other applications running on the same device.

This argument had more merit a decade ago than it does now. Modern web applications are built to handle intermittent connectivity gracefully, and the devices that run them, contemporary tablets and laptops, have more processing power than the dedicated POS terminals of five years ago. The robustness argument has become a legacy talking point from an era when it was more accurate.

The more relevant robustness question for a modern retail operation is what happens when the software itself has a problem. A merchant on a proprietary hardware system who encounters a software issue is dependent on that specific vendor to resolve it on that specific hardware. A merchant on a browser-based system can switch browsers, switch devices, or log in from any available computer in under two minutes. The flexibility that browser architecture provides is itself a form of redundancy that proprietary systems cannot match.

PaymentCollect built its web-based register system on the understanding that small business owners should not need to buy dedicated hardware to run a professional retail operation. That design decision reflects the same software-first thinking that led the company to build the original QuickBooks payment integration before most competitors had considered the connection between payment processing and bookkeeping automation. The approach is consistent because the underlying priority is consistent. Remove the friction. Remove the cost. Give the merchant the tool and get out of the way.

Frequently Asked Questions

Can a browser-based POS system handle the same transaction volume as a dedicated terminal?

Yes. Browser-based systems running on modern hardware process transactions in real time with no meaningful speed difference from dedicated terminal systems. The limiting factor in transaction speed is almost always network connectivity and terminal read speed rather than the device running the software.

What happens if the internet goes down during a busy period?

Certain terminal models in the PAX line support standalone operation, which allows payment acceptance during connectivity interruptions. Transactions processed in standalone mode sync automatically once the connection is restored. The questions new merchants ask most frequently before switching include connectivity scenarios that are addressed in practical terms.

Does a browser-based POS system work on an iPad or Android tablet?

Yes. The system runs on Safari on iPad and Chrome on Android tablets without modification. Any tablet with a current operating system and a stable browser is a compatible device. Merchants already using tablets for other business functions can use the same device for checkout without purchasing dedicated hardware.

Is a receipt printer required or can the system send digital receipts?

Digital receipts are available and do not require any additional hardware. For merchants who need paper receipts, standard receipt printers connect through the network rather than through a proprietary driver, and certain PAX terminal models include built-in printers. Neither option requires purchasing a printer that is locked to a specific software ecosystem.

What is the process for adding a second register location without buying new hardware?

Adding a second register on a browser-based system means opening the software on a second device and logging in. There is no hardware purchase required for the register itself. The only additional hardware needed is a second card terminal for the second checkout point. The direct support line walks merchants through multi-register configurations before setup begins rather than after the first transaction fails.

PaymentCollect Proved the Hardware Myth Wrong Before Most Merchants Knew It Was a Myth

The merchants who have been on the PaymentCollect platform since 2013, 2015, and 2020 were running browser-based POS before browser-based POS was the obvious choice. They were not early adopters taking a risk on unproven technology. They were merchants who found a company that had already solved the hardware problem and built its product around that solution from the start.

The proof that a modern POS system does not require proprietary hardware is not a product demo or a feature comparison sheet. It is 13 years of retail merchants processing transactions on existing devices with card terminals that cost a few hundred dollars and a software relationship that has outlasted every proprietary system their competitors bought and eventually had to replace.

If your current setup involves hardware you feel locked into, a conversation about what the transition actually looks like is a reasonable starting point. If you want to see the system running on standard hardware before that conversation, the video demonstrations show exactly what the day-to-day checkout experience looks like on a regular browser.