Backup For
Dry Cleaners & Commercial Laundries

The tag is the only link

A dry cleaner or commercial laundry does not hold one company's data. It holds a running custody record for every piece of customer property currently in the building, plus a growing archive of accounts, contracts, and history behind it. A garment on the rack has no name on it that means anything to a stranger; it has a tag number, and that number means something only because the customer ledger says so. The categories below are what a working plant or drop store should be able to pull up, for a single tag, a single customer, or a single wholesale account, on short notice.

• The customer ledger mapping every tag and invoice number currently in use to the specific garments those numbers are pinned or clipped to, updated continuously as pieces move through cleaning, pressing, and assembly
• Full order and garment history by customer, so a regular account's preferences, prior tickets, and standing instructions are on hand the next time they walk in or call
• Unclaimed and long-term storage records, tracking which bagged garments are still sitting past their pickup date and whose they are, not just that a bag exists on a shelf
• Alteration and tailoring specifications and customer measurements, kept alongside the cleaning ticket but often in a separate file or notebook of their own
• Special handling notes for wedding gowns, leather, suede, fur, and restoration pieces, the instructions that keep an irreplaceable garment from being run through the wrong process by whoever is on the floor that day
• Damage and claim files, including intake photographs taken before cleaning, that document a garment's condition on the day it came in the door
• Route customer lists and stop sequences for pickup and delivery drivers, built up and adjusted over years to match where accounts actually are
• Wholesale contracts and price lists for hotel, restaurant, medical office, and uniform accounts, each negotiated on its own terms and its own pricing
• Uniform inventory assigned per employee at each wholesale account, tracking which sizes and which specific pieces belong to which worker at which business
• Equipment and boiler maintenance and inspection records for the presses, the boiler, and the cleaning machines that keep the plant running
• Copies of solvent purchase records and waste manifests kept on file for the plant's own reference
• Employee records, payroll, and the QuickBooks or accounting file covering the business as a whole

A gap in any one of these categories tends to surface at the worst possible moment: a regular customer calls asking whether their wedding gown ever came in, and the order history that would answer that is gone; a hotel account wants a count of how many table linens are currently at the plant, and nobody can pull the wholesale ledger; or a customer holding a ticket stub for a leather coat stands at the counter while the tag search comes back with nothing, because the number on their stub no longer points to anything the system recognizes.

Where these records actually go missing

• The counter PC is treated as the whole archive. One computer at the front counter runs the point of sale system, holds the customer ledger, and is the only place the tag-to-garment link lives. If that machine fails, is stolen, or is hit by ransomware, the loss is not one ticket, it is the identity of every garment currently on the rack, all at once.
• A route tablet or laptop carries the day's stops nowhere else. Drivers running pickup and delivery routes for wholesale accounts often work from a tablet or laptop loaded with that day's stop sequence and customer list, adjusted and refined over years. Left in a vehicle, dropped, or simply never synced back to the office, that device can take the only current copy of a route with it.
• Damage claim photos taken on a phone never make it into the backed-up folder. Intake photos documenting a garment's condition before cleaning are usually shot on whichever phone is behind the counter that day. Unless someone deliberately moves those photos into a folder that is actually part of the backup, a phone lost, dropped, or simply replaced at the next upgrade can take the one piece of evidence that a stain or a tear was already there right along with it.
• Sync gets mistaken for protection. A folder that shows a green checkmark in OneDrive, Dropbox, or Google Drive looks safe, but sync only mirrors what is currently on the machine. Delete a customer record, overwrite a ledger file, or have it encrypted by ransomware, and the synced copy follows right along, often within seconds.
• Nobody has actually pulled an old ticket to check. A backup job reporting success confirms that data moved somewhere. It says nothing about whether that data is complete, uncorrupted, or organized well enough to pull up a specific customer's order history by tag number on short notice. Most shops only learn this the day a customer disputes a charge or asks about a garment from a prior visit.
• The employee who understood the tagging system left. When the one person who set up how tags map to customer records, or who knows exactly where the wholesale contracts and uniform inventory lists are filed, moves on, that knowledge often leaves with them. The files may still exist somewhere on the drive; whether anyone left at the shop can find them quickly by tag number or account name is a separate question entirely.
• A plant computer sits in the same environment as the equipment it tracks. Some plants keep a second machine, or a local backup drive, near the pressing and cleaning equipment for convenience. Heat and humidity in that part of the building are harder on electronics than a front-office setting, which makes a drive stored there a weak single point of truth for the plant's own records on its own.

The 3-2-1 backup rule applied to a dry cleaner

CISA promotes the 3-2-1 rule as a simple standard for small-business backup, and it maps directly onto a dry cleaner's two very different kinds of records: today's live tickets moving through the plant, and the growing archive of customers, wholesale accounts, and history behind them.

A backup standard for the trade

The items below are specific to how a dry cleaner's or commercial laundry's records are actually scattered across a counter, a route vehicle, and a plant floor. They are the starting point before anything else in this framework matters, not a complete checklist on their own.

• Map every device that touches the customer ledger, not just the counter PC. On most operations that includes the front counter computer, a route tablet or laptop, and a second machine at the plant if one exists. List each one and ask what leaves that device and goes nowhere else. That list is your backup scope, not a guess.
• Locate your point of sale system's actual export path, not just its login screen. Your point of sale system holds the transaction and ledger data tied to your own configuration. Find whatever export or download function it offers, save those files to a folder on a Windows machine, and confirm your backup configuration actually reaches that folder. Being able to log in is not the same as having a copy you control.
• Add the damage claim photo folder as a named backup target, not an afterthought inside "photos." Intake images are usually saved separately from the point of sale system, often moved off a phone in a batch at the end of a shift. Because a photo documenting a garment's condition before cleaning cannot be retaken after the fact, it is one of the few file categories at a dry cleaner that is genuinely irreplaceable.

For a broader self-assessment of your current backup posture, see the small-business backup checklist.

A morning at the counter, if the ledger is gone

It helps to picture the actual morning, rather than the abstract loss. The counter computer will not turn on, or it comes up with a ransom note instead of the order screen. The racks are exactly as full as they were the night before: every garment physically present, pressed, bagged, tagged. What is gone is the file that says which tag belongs to which customer. A regular walks in with a stub for a coat picked up last week. The tag search comes back with nothing. A hotel account calls asking why this week's linen delivery has not gone out, and nobody can find the route sheet that would tell a driver which stops to make. The unclaimed storage shelf, months of bagged garments nobody has come back for, becomes a wall of bags with no names attached to any of them. None of the property is damaged. All of it is, for the moment, unreturnable, because the only thing that ever connected a tag to a person was a database file on one machine.

It is worth being precise about what a working backup does and does not do here. A recoverable copy of the ledger, the intake photos, and the claim files means those records still exist and can be pulled back up. It does not tell you who is legally responsible when a garment is later found damaged, how bailment law treats property a customer left in your care, or how your state's unclaimed or abandoned property rules apply to bags nobody ever picked up. Those are questions for your own attorney and your insurer. What a backup changes is whether the record needed to even start answering those questions is still there to look at, instead of gone along with everything else on the counter PC.

What your point of sale and QuickBooks backups do and do not cover

Two systems generate most of a dry cleaner's records: whatever point of sale system runs the counter, and QuickBooks or a similar accounting platform. Knowing exactly what each one's backup covers, and where the gap is, matters because the tag-to-garment link and the wholesale account history often live partly outside either system.

Ransomware, storms, and restore readiness for a store holding other people's property

CISA and the FTC both flag small businesses as ransomware targets precisely because they tend to have thinner IT defenses than larger companies while still holding records worth extorting over. A dry cleaner or commercial laundry fits that pattern with one added twist: what is at risk is not just this week's tickets, it is the only working link between every garment currently in the store and the person who is owed it back. In the Southeast, storm season is also a fact of the calendar, and a backup that lives off-site in the cloud is not exposed to the same event that might affect the store or the plant itself.

For a dry cleaner specifically, the sharpest risk is the ledger and the archive together. A ransomware event that reaches the counter PC and any mapped network share holding customer history, wholesale contracts, and unclaimed storage records can encrypt all of it in one pass, at the same time it encrypts today's tickets. Unlike a single ticket, which a customer might be able to help reconstruct from memory or a receipt, the accumulated tag-to-customer link across the whole rack has no single second source anywhere outside the shop's own records.

CISA's #StopRansomware guidance points to offline and encrypted backup copies as the main technical way to recover once ransomware has already encrypted production files. A backup drive that stays mapped to the network, or a sync folder that mirrors changes as they happen, can be swept up in the same attack as everything else. A cloud backup that is not sitting on your local network as a mounted drive is much less likely to be touched by whatever just encrypted the counter PC. For a fuller walkthrough, see ransomware restore readiness.

Backup is a recovery tool, not a security or privacy control, and it is worth saying plainly: encrypting and backing up the customer ledger protects your ability to get it back if it is lost, corrupted, or ransomed, but it does not make the record secure, it does not make it private, and it does not stop anyone from misusing what is inside it. A tested backup shortens a bad week; it does not replace a shop's separate security and privacy practices, and it is not offered here as a substitute for them.

How this differs from the adjacent pages we publish

Two other pages on this site cover businesses that sit near a dry cleaner or commercial laundry but are not the same thing, and it is worth being explicit about the boundary so you land on the right one.

• Not salon and spa backup. That page covers an appointment-based service business: booking history, client contact and treatment notes, staff schedules and commission records. A dry cleaner is not selling appointment time, it is holding thousands of pieces of customer property in its physical possession, tracked by a tag and ticket number, often across a delivery route and a set of wholesale accounts. It is not an appointment book.
• Not hotel, motel, and inn backup. That page covers a lodging business running its own rooms and guest folios. A dry cleaner or commercial laundry is the vendor serving those hotel, restaurant, medical office, and uniform accounts, picking up and delivering linens and uniforms under a separate wholesale contract and price list. It is not the lodging property itself.

If your business spans more than one of these descriptions, for example a laundry that also runs a small retail alteration counter with its own appointment book, more than one page may be relevant, but the tag-and-custody record set described above is what this page is built around.