Why a cloud system goes offline
A cloud dealership system runs on the vendor’s servers. Your team reaches it through the internet. So it becomes unreachable when your internet connection drops, when the vendor has an outage, or when something between the two fails, such as a sign-in service.
What usually stops
Anything that needs the system’s records waits until it comes back.
- Signing in, if sign-in also runs in the cloud
- Looking up a customer, vehicle, or open deal
- Structuring and printing a deal
- Posting a payment and printing a receipt
- Checking a balance, payoff, or title status
How dealers cope today
Most dealerships fall back to paper: handwritten receipts, notes about which vehicle went where, and a list of things to type in later. That works for an hour. Over a busy day it creates double entry, missed payments, and mismatched balances that someone has to reconcile.
Plan for it, whatever system you use
- Write down what your team does when the system is unavailable, and who decides
- Keep a paper receipt book and a simple log for payments taken during an outage
- Know how you will enter that log afterwards, and who checks it
- Ask your vendor how outages are reported and how long they have lasted
- Keep your own copy of key records, so you are never fully locked out
How a local system changes this
A system that runs on hardware inside the dealership keeps working when the internet is down, because staff reach it over the dealership’s own network. ClozBox works this way: daily work such as customers, inventory, deals, payments, titles, and reports does not need an internet connection.
A local system brings its own responsibilities. The hardware is in your building, so power, physical security, and backups are yours to plan for. Neither approach removes the need for a plan; they move where the risk sits.
This guide is general information, not legal, tax, or accounting advice. Your contracts, state rules, and qualified advisers decide what applies to your dealership.