If you're opening a hardware store and wondering whether Square or Clover can run it, the answer is yes, for a while, and plenty of the stores we serve started exactly there. Both will ring up a hammer without complaint. The real question isn't whether a generic POS works on day one. It's how long until your store stops acting like a checkout line and starts acting like a supply store, because that's the moment the aisle runs out.
Built for a different kind of business
Square got a generation of small businesses off paper tickets, Clover was designed for restaurants and simple retail, and Lightspeed, the third name that usually comes up in this conversation, is a general retail platform sold across many industries. All three were built for businesses where every transaction ends the same way: customer orders, customer pays, customer leaves. A hardware store doesn't work like that. A contractor picks up materials on Monday, comes back for fence posts on Wednesday, drops off a partial payment on Friday, and returns four of the posts the next week because he measured wrong. Generic POS handles the first kind of business as designed and the second kind with workarounds, and the gap between the two shows up in four predictable places.
Wall one: the SKU count
A coffee shop menu fits on a chalkboard, while a hardware store carries a deep catalog where the same item might be bought by the box and sold by the piece, the pound, or the gallon. Stores that come to us from Clover consistently describe inventory management that doesn't scale once the count climbs into the thousands of SKUs (the individual items on your shelves), and Square stores tell us the reason they switched was wanting real clarity on their inventory, who owes them money, and where their margins are going. When your buyer is working from a day-old export while the counter sells in real time, the SKU count has officially outgrown the system.
Wall two: the day someone says "put it on my account"
This is the wall most hardware stores hit first, because charge accounts are the backbone of the pro side of the business. On Square, running a charge account means keeping one long open ticket per customer that grows endlessly, entering partial payments as notes attached to zero-dollar charges, and printing the entire receipt just to figure out what someone owes. Clover doesn't natively support the way supply stores bill their customers either, which is how balances end up living in a spreadsheet next to the register. Lightspeed stores describe charge accounts as a consistent pain point too, with payments bouncing between separate systems.
None of that is a design flaw in those products; house accounts with statements, aging, tiered contractor pricing, and month-end billing simply weren't the job they were hired for. It is, however, the job a hardware store needs done every single day, and you can only stock so many workarounds before they need their own bin tag.
Wall three: the catalogs you buy through
Independent hardware stores order through buying groups like True Value, Do it Best, and Orgill, and the store runs smoother when those catalogs live in the same system the counter sells from, so the buyer and the cashier are looking at the same product record. A generalist POS serves restaurants, boutiques, golf courses, and everything in between, which means supply-store needs like EDI ordering (orders sent electronically, nothing re-keyed), buying group integrations, and contractor pricing tiers are never going to be at the top of their product team's list. That's a rational choice for them and a daily tax on you.
Wall four: purchasing that keeps up with the truck
The last wall is the loop between selling and buying. In a system built for supply stores, stock, costs, and purchase orders update the moment you ring a sale or receive a truck, reorder suggestions come from live numbers, and multi-location stores keep inventory, pricing, and customer data in sync across every branch. Multi-store Clover operators have described keeping locations aligned on pricing and inventory transfers in words we can't print on a family-friendly hardware blog, and Lightspeed stores tell us multi-location invoicing was a major headache. Once you're moving product between two buildings, the generic tools start costing you more than they save.
What the workarounds look like in practice
Rusty Gate Nursery & Building Supply in Forks, Washington ran on Square for five years after a fire pushed them off paper, and owner Andrea Perkins kept the charge-account side of the business alive through exactly the routine described above: endless open tickets, zero-dollar payment notes, and arithmetic with a pencil while the customer waited. Then Square removed the ability to convert running tickets into invoices and leaned into email-based electronic payment, which makes sense for plenty of businesses but not for a clientele that settles up by check at the end of the month.
"It's not our clientele. We take checks."
Andrea's story isn't an indictment of Square, and she'd be the first to say it got them off paper when they needed it most. It's a story about fit, and about what happens when a business built on accounts, statements, and returns runs on software built for transactions.
If you're reading this a few years too late
Maybe you're not choosing a first POS, you're realizing you outgrew the one you have. The good news is that the data you've built up comes with you: point our Square and Clover parsers at your export and they carry your products, customers, sales history, vendors, inventories, pricing tiers, and product categories across on their own, so the years you spent on a generic system aren't sunk cost, they're a head start.
Start on Square or Clover if you're small and simple, and run them while they fit. But when the charge accounts, the catalogs, and the SKU count start stacking up, it's worth looking at a system that was built for hardware stores from the first line of code, because a hardware store deserves software that knows the difference between a transaction and a relationship.
