Your Clover register, connected once
You already run Clover. It works, your staff know it, and the last thing you want is a second system that duplicates the menu and then slowly disagrees with it.
That is the reasonable fear about bolting anything onto a register, and it is usually justified. Two menus means two prices for the same side dish, an item that is off at the counter and still selling online, and a Friday afternoon spent working out which one is right.
This connection is built the other way round. Clover stays the source of truth, the platform reads from it, and the things the register cannot do on its own get added on top: a customer record behind every sale, loyalty that works at the counter, and ordering on the channels your customers already use.
Book a Free DemoOne connect, approved once
Connecting is a one-time OAuth approval from inside your Clover account. You approve it once and it stays connected. There is no key to copy out of a settings screen, no middleware account to open, no nightly export to schedule, and nothing to reconnect every few weeks.
After that there is no ongoing setup work. The register keeps being the register, your staff keep ringing sales up the way they always have, and the platform reads what it needs.
- One-time OAuth connect from your existing Clover account
- No keys to copy, no middleware, no scheduled exports
- Stays connected: nothing to re-approve on a cycle
- Nothing changes about how your staff use the register
Clover stays the source of truth
This is the boundary that matters, so it is worth being exact about it. Your menu, your items, and your pricing stay native in Clover. The platform reads them from there.
You will not maintain a second menu. You will not have an item that is off at the counter and still selling in chat. You will not spend a Friday reconciling two systems that disagree about the price of a side. The register is where the truth lives, and everything the customer sees online is a reflection of it.
And to be equally exact about the other direction: the platform does not write menu items, prices, or promotions back into Clover. The integration is deliberately read-only apart from applying a loyalty discount to an order. If you change something, you change it at the register, which is where you would look for it anyway.
- Menu, items, and pricing stay native in Clover and are read from there
- No second menu to maintain and no risk of the two drifting apart
- The platform does not write items, prices, or promotions back into Clover
- The one exception is applying a loyalty discount to an order
Order and payment status sync on their own
Order and payment status sync automatically, which is what makes everything downstream trustworthy. A completed sale is a completed sale in both places without anyone marking anything off.
That matters because so much of the platform hangs off completion. A completed order is what triggers the review request, what earns loyalty points, and what gets counted as real revenue in attribution. If completion were a manual step, all three would quietly become approximate.
- Order and payment status synced automatically
- Completion drives review requests, points, and revenue reporting
- Nothing for you or your staff to mark off at the end of a shift
Every sale at the register earns points, with nobody signed up at the counter
A sale rung up in Clover earns loyalty points automatically. Not only orders placed online, which for most businesses are the smaller half. The revenue that walks in and pays at the counter counts too, on the same ledger.
The hard part of counter loyalty has always been identifying the customer without holding up the line, and this is where the receipt QR does the work. Somebody who paid with no account on file scans the code on their receipt and claims the visit and the points themselves, on their own phone, afterwards. No staff intervention, no sign-up pitch, and nobody waiting behind them.
Redemption works the same way round: a reward applies as a real discount on the order, tracked so it cannot be spent twice. See how the points ledger works.
- Sales rung up in Clover earn loyalty points automatically
- A receipt QR lets a walk-in claim the visit and the points themselves
- No sign-up at the counter and no staff training
- Redemption applies as a real discount on the order
What the connection is actually for
The register alone tells you what sold. It does not tell you who bought it, whether they came back, or what brought them in. Connecting it is what turns a stream of transactions into customers you can recognise.
A counter sale becomes a visit on a customer record with history and lifetime value. That record is what makes it possible to notice a regular who has gone quiet, to ask a happy customer for a review at the right moment, and to know that the campaign you sent produced twelve visits rather than a number of clicks.
- Counter transactions become named customers with a history
- Which makes win-backs and review requests possible at all
- Orders taken in chat or on WhatsApp read the same Clover menu
How it fits the rest of the platform
The connection feeds the rest of the platform. Conversational ordering reads its menu from Clover, counter sales earn on the rewards ledger, every transaction attaches to a customer record, and completed sales trigger review requests. If you run Square instead, the same shape exists with different details: see the Square integration.
Questions owners ask
How does the connection work?
A one-time OAuth connect from your existing Clover account. You approve it once and it stays connected. There are no keys to copy and no ongoing setup work.
Do I have to maintain a second menu?
No. Menu, items, and pricing stay native in Clover and the platform reads them from there. There is nothing to keep in sync by hand.
Will it change anything in my Clover account?
It does not write menu items, prices, or promotions back into Clover. The integration is deliberately read-only apart from applying a loyalty discount to an order.
Do sales rung up at the register earn loyalty points?
Yes, automatically, on the same ledger as orders placed through the platform.
How does a cash customer with no account get their points?
They scan the QR code on their receipt and claim the visit and the points themselves, on their own phone. Nothing is collected at the counter and no queue is held up.
What happens to order status?
Order and payment status sync automatically, which is what lets a completed sale trigger a review request, earn points, and be counted as real revenue in attribution.
See it working on a business like yours.
Book a free fifteen minute demo. We will show you where customers are slipping away today and what closing that gap looks like for your shop.
Book a Free Demo