Offline mode on your handhelds is a risk limit, not a convenience toggle

Every dollar you accept offline is a dollar you're authorizing on trust until the device reconnects.

Clover's offline mode is easy to switch on and easy to forget about. That's the problem. The setting looks like a convenience toggle, but the limits underneath it are a credit decision you're making on behalf of every customer who taps a card while your Wi-Fi is down.

What Clover actually says offline payments do

Clover's help article on offline payments is short, and every line of it matters. With the Offline Payments option on, you can keep taking payments when you're not connected to the internet. "Payments are processed as soon as you're back online and logged in." When a connection comes back, the device automatically submits offline payments for authorization, and once they're authorized, you get your deposits and your customers get their receipts.

The risk sits with you, and Clover says so plainly: "When you take an offline payment, you accept the risk of a declined or partial payment when the device is back online." Its examples are a credit card that's expired or canceled, or an incorrect PIN. In each case the payment is declined after the customer has already walked out with the goods.

A few more limits worth knowing before you rely on it:

• When enabled, devices can take offline payments for up to 7 days.
• The feature isn't available with Electronic Benefit Transfer (EBT) or gift cards.
• The settings are per device. If you run more than one Clover device, you turn the options on or off for each one.

The three numbers that make it a risk limit

You'll find the controls in the Setup app under Payments, then Offline payments. For each device you can choose not to allow offline payments, in which case the device declines all offline transactions, or allow them on demand. Then come the offline payment limitations, and this is where the real decision lives:

• Limit each offline payment amount. This caps a single offline payment. Above it, Clover says the payment is declined or requires the merchant's approval.
• Limit total offline payments. This is the not-to-exceed amount for offline payments on that device. Once the total hits it, that device stops taking offline payments.
• Require merchant approval for each offline payment over a set amount. To turn this off, Clover says to set it to the same amount as the per-payment limit.

Read together, those are a per-sale cap, a per-device exposure cap, and a manager checkpoint. That's a risk policy. The question is whether you set it on purpose.

Sizing the limits by what you can afford to lose

Start with the total limit, because it's your worst case. Ask how much you could absorb if a meaningful slice of offline payments came back declined, and set the device total below that. Then set the per-payment cap around your typical ticket, so ordinary sales go through and unusually large ones get stopped or need a manager.

Example (hypothetical round numbers, not a benchmark): a counter where most tickets run $20 to $40 might set the per-payment limit at $75, ask for merchant approval over $50, and cap the device total at $500. A bad outage then exposes at most $500 on that device, and nobody can quietly ring a $300 order on trust. A shop with $400 average tickets would need very different numbers, and might decide offline mode isn't worth it at all.

There's a second-order effect here. The total limit is per device, so your real exposure is the sum across every device you've enabled. Five handhelds at $500 each is a $2,500 exposure, not $500.

Deciding which devices get offline mode

Because the setting is per device, you don't have to treat every terminal the same. Turn it on where losing a sale during an outage really costs you, and where staff can hand off a questionable payment to a manager. Leave it off, or set tight limits, on devices that tend to handle large tickets or that are used by your newest staff.

Be honest about how often you actually go offline. If your connection drops twice a year, a modest limit covers you. If a patio, a parking lot, or an event booth loses signal every weekend, offline mode is part of normal operations. In that case the limits deserve the same review as your cash drawer policy.

The one thing staff must never do

Clover's help page puts a warning at the very top: "Do not uninstall the app while offline. Doing so deletes all payments taken while offline."

Those payments haven't been submitted yet, so deleting them means the money never arrives. It's exactly the kind of thing a well-meaning employee might try when a device is acting up during an outage. Put it in training, and post it near the devices if you need to.

The other half of the habit is getting back online. Payments process once the device is back online and logged in, so a handheld left in a drawer for days is holding sales that haven't been authorized. The longer they sit, the longer you wait to find out which ones were declined, and the longer your deposits lag.

A checklist before your next outage

• Decide, device by device, whether offline payments are allowed at all.
• Set a per-payment limit near your typical ticket, and a merchant-approval amount for larger sales.
• Set each device's total limit based on what you could absorb if those payments were declined, then add up the totals across devices.
• Train staff never to uninstall the app while a device is offline.
• After any outage, get every device back online and logged in, then watch for declines and check that the deposits land.

Set those numbers deliberately, and offline mode becomes a risk you chose instead of one you discover after the Wi-Fi comes back.

If you'd like help setting sensible limits and tying offline sales back to your deposits and books, Gameplan Financials pairs bookkeeping and tax strategy with AI systems work: schedule a conversation.