Yes. You authorize the connection once, the Clover merchant is backfilled and then kept current, and settled sales appear in your reporting alongside your own store sales. The connection reads only, so refunds and cash still happen on the Clover, and day close shows Clover sales in their own panel.
Plenty of parks already run a Clover register somewhere: the snack bar, the marina fuel dock, the store itself. The staff know it, the printer works, the kitchen has muscle memory for the button layout. Then a new platform arrives and the first thing it wants is for you to throw that away.
Keep it. Connect it instead, and let its sales show up where you read your numbers.
What does connecting a Clover do?
You authorize the connection once from your integrations settings. CampGuide backfills what's already in that Clover merchant, then keeps pulling as new activity happens: orders, payments, refunds, inventory, employees, and cash events. Settled sales come through into your reporting alongside your own store sales, so the snack bar's Saturday shows up in the same revenue picture as the campsites and the firewood.
That's the whole promise, and it's worth being precise about the shape of it.
Does the connection write back to the Clover?
The connection is one way. CampGuide reads from Clover and never pushes anything back, never charges a card through it, and never voids or refunds a Clover sale. If a guest wants a refund on a snack bar order, that happens on the Clover, the way it does today, and the refund flows back into the reporting on the next pull.
Clover money is marked as Clover money the whole way through, which is the part that protects you. It can't be mistaken for a CampGuide sale, refunded through CampGuide's register math, or swept into your CampGuide payout. The two sets of money stay legible as two sets of money.
Where each thing lives after you connect
Why does day close keep Clover sales in their own panel?
Your CampGuide drawer count is built from cash the CampGuide register took. Clover's drawer has its own cash log that CampGuide can't see into, so folding those two totals together would produce a number that ties to nothing.
Instead, day close shows Clover sales as their own panel. You see the day's snack bar volume next to your own tender breakdown, you know what the property took in total, and each side reconciles against the system that actually holds its cash. Two honest numbers beat one blended one.
What can't the Clover integration do yet?
Being straight about this is more useful than a feature list.
Today, Clover items don't link to your CampGuide products, so a hot dog on the Clover and a hot dog in your camp store catalog are two separate items with two separate stock counts. Clover sales don't post to a guest folio either, which means a guest can't charge a snack bar order to their site the way they can at your own register. And Clover sales don't post into the accounting sync.
Item linking and folio posting are the planned next phase. A charge to campsite tender on the Clover device itself is the phase after that. Until they ship, the honest description of this integration is: Clover keeps running exactly as it does now, and its sales stop being invisible in your reporting.
A revenue center nobody reports on is a revenue center nobody manages.
Which parks should connect a Clover?
Parks with a real second counter. If the snack bar does forty thousand dollars a summer, the reason to connect it is that you currently have to open two systems and do arithmetic to answer a simple question about your own Saturday. Connect it once and the question has one answer.
If you're running one register and it happens to be a Clover, you have a different decision to make: keep it as the outside register, or move the store onto CampGuide's own register and get charge to site, guest ordering, and folio settlement with it. Both are reasonable. The one nobody should have to make is throwing out working hardware to get a report.