POS and payments, SMB merchants
Clover went to market through bank reps, not a sign-up flow. The owner behind each terminal is the buyer every SMB vendor wants named.
Clover is the long tail of US small-business commerce: owner-operated shops, cafes, salons, and restaurants that a bank rep sold a terminal to, not a founder who signed up online. That channel difference is what makes the file difficult to build and exactly what every SMB payments, lending, and SaaS vendor wants named. If you sell into that buyer, the Clover users dataset is your account list.
restaurants on Clover
More than 125,000 full-service and quick-service restaurants on the platform after the BentoBox acquisition rolled into Clover Hospitality. This slice is the active battleground for Toast, SpotOn, and Square at every Clover renewal.
typical bank contract term
Clover is sold on 36-month terms through Fiserv partner banks and ISOs. The renewal window is the displacement window: the moment a contract expires is when merchants seriously shop competing stacks for the first time.
per device per month, bank/ISO channel
Subscription range quoted by the bank rep at point of sale. No public rate card; the rate moves by merchant volume and hardware bundle. Hardware sits on top at $199 to $1,899 depending on the device.
Source: Orbital data team, June 2026 snapshot.
hardware cost, Mini to Station Duo
iprimary merchant verticals in the install base
imerchants who switch stacks at contract end
iTop alternatives
Where buyers shop when Clover is not the right fit.
The five tools that show up most when a Clover merchant is shopping the stack, ranked by the displacement conversations Orbital sees inside the SMB point-of-sale category. Each alternative captures a different segment of the Clover base: Square takes the self-serve crowd, Toast takes the restaurant, Lightspeed takes the multi-location retailer, SpotOn takes the independent full-service operator, and Square Appointments takes the booking-led services shop.
| # | Alternative | Positioning vs Clover |
|---|---|---|
| 1 | Square | The flat-rate self-serve default. Wins owner-operators who want hardware off the shelf, no bank contract, no ISO sales rep, and a single 2.6-percent-plus take rate from day one. |
| 2 | Toast | The restaurant-specific stack on its own Android hardware. Wins full-service and quick-service restaurants on kitchen-display, online ordering, and labor depth that a general POS like Clover does not match. |
| 3 | Lightspeed | Targets multi-location retail and hospitality with deeper inventory and supplier workflows. Wins merchants who outgrow the Clover device-count and need real SKU and stock-level reporting. |
| 4 | SpotOn | High-touch sales motion into independent full-service restaurants. Competes with Clover on a similar bundle of POS, online ordering, and loyalty, but with a named rep rather than a bank channel. |
| 5 | Square Appointments | The booking-led variant of Square. Displaces Clover at services-led operators (salons, spas, barbers) who run their book by chair or by hour rather than by ticket. |
Ranking reflects Orbital’s read of the SMB point-of-sale category as of June 2026. Source: Orbital data team.
Who buys this data
Who sells into the Clover installed base.
This page is for the vendors selling into Clover merchants, not the merchants themselves. If you ship one of the categories below, the named-owner list of Clover customers is what your AE team has been asking for.
The long version
Detail, on demand.
Clover concentrates in four verticals. The buyer on the other end of every install is almost always the owner-operator, not a corporate office, not a franchise group, not a procurement seat. That is what makes the file useful, and that is what makes it expensive to build by hand.
Full-service and quick-service restaurants. The largest single slice of the Clover file in the US, with more than 125,000 restaurants on the platform after the BentoBox acquisition rolled into Clover Hospitality. The buyer is the owner-operator who picked Clover when the bank rep walked into the back office. The displacement target is Toast at renewal.
Cafes and coffee shops. A heavy slice of the small-ticket book. The chair-or-counter operator with a Clover Mini and a card reader is the canonical record in this part of the file. The owner runs the books, signs every vendor contract personally, and answers the phone between pours.
Independent retail and convenience. Small storefronts, gift shops, vape and smoke shops, liquor, and corner-store retailers that took Clover Station as the in-store POS. The Fiserv distribution wins this slice because the bank rep already knows the merchant from the business checking account.
Personal-services and salon-style operators. Barbers, nail salons, dog groomers, and small spa operators that need a card terminal and a basic appointments hook. Lightweight on inventory, heavy on tip flow. The Clover device sits at the front desk and almost never moves.
Public references on the Clover side include The Jambalaya Shoppe, Ludwig’s German Table, and BentoBox (acquired, now operating as Clover Hospitality). These are illustrative names, not endorsements. The dataset spans the active merchant base worldwide, weighted to the US.
Orbital is a custom agent platform, not a scraped list. The Clover merchant file is built fresh every time you pull it. Here is what runs under the hood.
How the Clover customer file is built
- Tech stack agent. Crawls a merchant’s payment, ordering, and reservation surface and confirms whether it is actually running Clover, on demand. The check happens at pull-time, so the file is current at delivery, not scraped a quarter ago.
- Owner finder. Names the decision-maker at each merchant and confirms them on LinkedIn. For the single-location operator who does not maintain a polished profile, we find them by license filings and by review-site authorship.
- Email waterfall. Returns a work email and checks deliverability before it ships. The phone intel agent adds a dial-or-skip read on every number so your dialer is not chasing dead lines into the back of a kitchen.
- ICP score. Grades each Clover account A through D against your fit formula. You upload three closed-won merchants, the score calibrates, and the worklist sorts by likelihood, not by alphabet.
- Chain rollup. Separates the franchisee LLC from the franchisor when a multi-unit operator sits on top of independently-owned Clover devices. The named operator is the buyer for most vendor categories, and we keep that buyer named.
Want the cut for a specific state, metro, or vertical mix (restaurant vs cafe vs retail vs services)? Tell us when you request the sample. We do not hide the working.
This page is for the vendor selling into the merchant, not the merchant themselves. If you ship one of the categories below, the Clover users file is the account list your AE team has been asking for.
Payment processors and ISOs running displacement campaigns against the Fiserv distribution at the end of a 36-month bank contract, where the take-rate spread is the angle. The renewal window is when the merchant actually picks up the phone.
Restaurant and retail SaaS vendors in online ordering, loyalty, inventory, scheduling, and accounting, the layer that sits on top of the Clover terminal and wants a current map of merchants to upsell or displace at renewal.
SMB lenders and merchant cash advance providers sized for the single-location operator with consistent card volume across a Clover device. The bank channel does not always offer working capital; that gap is the angle.
Food and beverage distributors targeting the Clover restaurant segment for case-level reorders, with the owner-operator as the buyer who answers a cold call before lunch service.
POS hardware and peripheral suppliers selling printers, scales, scanners, and cash drawers into the same merchant base, where the bank channel does not handle accessory upsell after the initial device sale.
Competing POS platforms running structured replacement plays. Square, Toast, Lightspeed, SpotOn, and Square Appointments all have a motion into this account list whether they publish it or not.
Do not buy this if any of the following are true.
You only sell to enterprise multi-location restaurant or retail chains. Clover skews single-location and owner-operated, distributed through banks rather than corporate IT. If your motion needs a VP of operations at a 500-location chain, you want a different file, and that buyer is on Oracle Symphony or NCR Aloha anyway. Save your budget.
You sell exclusively to full-service restaurant chains above 20 locations. Clover serves the single-location restaurant and the small group. The 20-plus-location operator is almost always on a restaurant-native stack. Pull the Toast customer file instead; that is the right cut.
You sell only to multi-location retail with deep inventory and supplier workflows. Clover handles the basics, but inventory-heavy chains buy Lightspeed for the SKU and stock-level reporting. The Lightspeed customer file is the worklist for that motion.
You sell to services-led operators booking by chair or by hour. Salons, spas, and barbers running on a booking app rather than a ticket-led terminal are usually on Square Appointments, not Clover. The Square Appointments customer file is the cleaner fit.
You sell to consumers. The Clover ecosystem touches the consumer through receipts and rewards, but the merchant list is a B2B owner file. We do not ship the consumer side.
Your sales motion only fires above 100,000 dollars in annual contract value. A single-location operator with two Clover Minis rarely writes a six-figure annual check on day one. The long tail of independents will not fit your unit economics. Call us when an enterprise-only motion stalls and you need a mid-market overlay.
If you bought “Clover customers” from a generalist B2B database last quarter, you bought the Fiserv channel report from 2024 with a fresh date stamp. The active merchant base is owner-operated single-location LLCs sold through a bank rep, and bank reps rotate processors faster than the broker file refreshes. By the time the export hits your CRM, somewhere between 15 and 25 percent of the merchants on it are already on Square Terminal, Toast, or a different Fiserv-branded device sold by a different rep.
Most files sold as “companies using Clover” come from one of three sources: a scrape of the Clover App Market reviews and merchant directory, an enrichment vendor’s tech-stack guess based on a payment-page fingerprint, or a stale export pulled from somebody’s CRM the last time a Fiserv channel campaign ran. All three age out fast in this category. A restaurant owner can switch from Clover to Toast in a Tuesday afternoon at the end of a bank contract. The list looks like a list right up until your AE team works it for a week.
The harder problem is the owner. The Clover install base is heavy on single-location operators who do not file a polished LinkedIn presence and do not roll up to a corporate procurement seat. Generalist B2B databases see the merchant DBA and miss the owner, or they roll up to a parent entity that does not exist. The named operator is the buyer for almost every vendor category that sells into Clover merchants, and that name is exactly the field that goes blank in a typical export.
This is the gap Orbital sits in. We map the universe of US small and mid-market businesses, detect the payment platform live at pull-time, find the owner or operator for that account, and ship a verified contact before the conversation starts. The output is a worklist, not a directory.
Questions
Before you ask sales about the Clover dataset.
What are the best Clover alternatives in 2026?
The five most common Clover alternatives, ranked by the displacement conversations Orbital sees inside the SMB point-of-sale category, are Square, Toast, Lightspeed, SpotOn, and Square Appointments. Square is the flat-rate default for retail and quick-service. Toast is the restaurant-specific stack on its own Android hardware. Lightspeed targets multi-location retail and hospitality with deeper inventory. SpotOn wins independent full-service restaurants on a high-touch sales motion. Square Appointments displaces Clover at services-led operators booking by chair or by hour.
How many merchants use Clover?
Clover's publicly reported install base is a worldwide figure, weighted to the US market. The base spans restaurants, cafes, independent retail, and personal services, sold almost entirely through Fiserv-affiliated bank reps and ISOs rather than through a self-serve signup. The US working list Orbital builds is smaller than the global count, which matters for prospecting: when you filter for US-only merchants with a named owner and a verified email, the active file is what your AE team can actually call.
Can I get a list of companies that use Clover?
Yes. Orbital builds a vendor-grade list of Clover merchants, filterable by US state, metro, primary vertical (restaurant, quick-service, retail, services), and operator size. Each record carries a named owner, a deliverability-checked work email, and a direct dial. We send a free sample of around 100 records you can check against your own pipeline before you commit.
When is the Clover dataset the wrong fit?
Three cases. First, if you only sell to enterprise multi-location restaurant or retail chains, the Clover file skews single-location and owner-operated, and you want a different cut. Second, if you sell to consumers, you want consumer data, not the B2B merchant list. Third, if your sales motion only fires above 100,000 dollars in annual contract value, the long tail of single-location merchants will not fit your unit economics. Save your budget and call us when an enterprise-only motion stalls.
See the Clover customer dataset before you pay for it.
Tell us the states, verticals, or operator types you want. We send a free sample of around 100 verified owner-operator records you can check against your own pipeline, no commitment, no email-list back-and-forth.
Get the sample