Coles Cyber Incident: What to Tell Customers Before You Know
The Coles cyber incident shows how to tell customers the truth before forensics finish, keep gift cards and billing running and avoid promises you can't keep.

Photo: Pixabay
On this page 7 sections
- The Coles Cyber Incident: What Was Disclosed and What Still Works
- Why "No Evidence so Far" Is Not an All-Clear
- The First 24 Hours: Who to Call Before You Post Anything
- Cyber Incident Customer Communication: Writing the Holding Statement
- Gift Card Security After a Breach, Plus Loyalty and Subscriptions
- When Breach Notification Before Confirmation Becomes Required Notice
- A Retailer Cyberattack Response Plan That Fits on One Page
Key takeaways
- Put a date and time on any early statement and describe what you've found "to date." Don't describe it as a guarantee, because headlines will make your wording sound more certain than it is.
- If card data could be involved, call your acquirer before you post anything publicly. Visa's compromise procedures set a three-calendar-day window to notify Visa, and that report goes through your bank.
- Under state breach laws, the notice clock can start at discovery, not when forensics finish. If any customers live in a 30-day state, plan the whole response around 30 days.
- Keep gift cards, loyalty and subscription billing running while you watch them closely. Quietly pausing them suggests a problem you haven't confirmed.
If you discover a cyber incident before you know what was taken, tell customers four things: what you know, what still works, what you're doing about it, and when you'll update them. Leave out anything you can't stand behind a month from now. The Coles cyber incident, which the Australian supermarket chain disclosed on Nov. 16, 2026, is a useful template for U.S. merchants because Coles did exactly that. It also shows the gap between "no evidence so far" and "you're safe."
The Coles Cyber Incident: What Was Disclosed and What Still Works
Coles told the Australian Securities Exchange on the morning of Monday, Nov. 16, 2026, that it was investigating a cybersecurity incident. It said it was working with the Australian Cyber Security Centre and outside experts to "contain and secure the Coles IT environment." ABC News reported that the incident happened over the weekend.
The statement on the Coles Group updates page is marked "current as at 16 November 2026, 8:30am." It says that, based on the investigation so far, Coles had found no evidence that customer, team or supplier data had been compromised or removed. Stores and online shopping were running normally. Coles went through its products one by one:
- Gift cards were working as normal.
- There was "no indication" of any impact on Flybuys loyalty accounts.
- No issues had been found with its Coles Plus and Coles Plus Delivery memberships or its QuiteLike subscriptions.
It also told customers to be wary of unexpected emails and text messages claiming to come from Coles and not to click their links.
Computer Weekly pointed out what Coles left out: the kind of incident, when it was detected and which systems were involved. ABC's live coverage also reported that Coles was looking into problems a small number of customers had with Liquorland click-and-collect orders. So even on day one, "everything works" came with a caveat.
Why "No Evidence so Far" Is Not an All-Clear
Coles chose its words carefully. "We have not identified any evidence," based on "the findings of our investigation to date," is a status report with a timestamp. It stays true even if later forensics find something.
Headlines and social posts often lose that nuance. A careful "no evidence so far" turns into "customer data is safe" within a few retellings, and that is a stronger claim than the company made. Expect customers, local press and your own staff to turn your "no evidence yet" into "nothing happened."
So wording matters. Suppose you write "your data is safe" and forensics later find a skimmed payment page. Now you have to take back a promise, and the retraction becomes the story. If you write "we have found no evidence so far, and we'll update you by Thursday," a later finding is just a new update, not a reversal.
The First 24 Hours: Who to Call Before You Post Anything
The FTC's Data Breach Response: A Guide for Business tells companies to:
- pull together a response team right away
- stop any further data loss
- consider hiring an independent forensics team
- have a communications plan
For a merchant that takes cards, the call list looks like this:
- Your processor or acquiring bank. If card data could be involved at all, call your acquirer's risk or security team first. Visa's What To Do If Compromised guide applies to merchants as well as banks and processors. It sets a three-calendar-day window to notify Visa of a suspected compromise, and Visa can require an investigation by a PCI Forensic Investigator. Merchants normally report through their acquirer, so your bank needs to hear about it from you early.
- Whoever is handling containment. An earlier edition of Visa's guide says not to log on to affected systems and not to turn them off, restart or reboot them. Isolate them instead, because rebooting can destroy evidence.
- Your cyber insurer. Before you hire anyone, check your policy's notice clause and whether it limits which forensic firms and lawyers it will pay for.
- A breach-response lawyer. Whether you owe legal notice depends on what data was involved and where your customers live. That's a legal call, not a marketing one.
- Your platform vendors. Your gift card, loyalty, subscription billing and e-commerce providers can check their own logs for signs the incident reached them.
If your registers go down, keeping sales moving is a separate problem. We covered it in our piece on selling through a cyberattack when systems go dark.
Cyber Incident Customer Communication: Writing the Holding Statement
A holding statement is the short public note you post before you have answers. The Coles version works because every line is either a fact you can check or a commitment the company can keep. Build yours from the same parts:
- A date and time stamp, so readers know how current it is
- One plain sentence on what happened, with no guessing about the cause
- What still works: payments, ordering, gift cards, loyalty, subscriptions
- What you've found so far, stated as a finding and not a guarantee
- What customers should do, which almost always includes a phishing warning
- When the next update will come, and the one web page where it will appear
Here is an illustrative statement for a hypothetical grocer with three stores. The business and every detail are invented for this example.
Update, Nov. 18, 9:00 a.m. ET. On Nov. 16 we found unusual activity on part of our office computer network. We isolated those systems and hired an outside security firm to investigate. Our stores, online ordering and gift cards are working normally. So far we have found no evidence that customer information was accessed, and the investigation is continuing. We will never ask for your password, card number or a gift card code by text or email. If you get a message like that claiming to be from us, don't click the link. Our next update will be posted on this page by 5:00 p.m. Friday.
Notice what it doesn't say. "Your data is safe" and "the threat is contained" both depend on findings that aren't in yet. Only say "no card data was involved" if your systems never handle card numbers at all. That can be true if your gateway uses hosted payment fields and tokenization to keep card numbers off your servers. The statement also doesn't name a suspected attacker or offer compensation before you know what you'd be compensating for.
Give staff a three-line version to use on the phone and at the register. Cashiers who make it up as they go end up making the promises your statement was careful to avoid.
Gift Card Security After a Breach, Plus Loyalty and Subscriptions
Coles called out gift cards, loyalty and subscriptions because they hold value customers have already paid for. That makes them what people worry about first. If you run a grocery store, a retail shop or an online store that sells memberships, watch the same three products closely while an investigation is open.
Gift cards. Ask your gift card provider to watch for bursts of balance checks and for quick redemptions on cards that have sat unused for a long time. Either can mean someone is testing card numbers. Until you know more, have staff stop reading out balances or moving value between cards over the phone.
Loyalty balances. Points are stored value too. Don't force a mass password reset just to look busy. A reset email that arrives during breach news looks exactly like phishing. If you do need a reset, announce it on your website first.
Subscription billing. Keep it running. Pausing renewals without telling anyone creates support tickets and hints at a problem you haven't confirmed. If card data later turns out to be compromised, card issuers may replace customers' cards, and renewals will start to fail. Learn to read credit card decline codes, and ask your gateway whether it offers a card updater service.
Breach news also brings "I don't recognize this charge" disputes. Clear billing descriptors and renewal emails help, as our guide to preventing chargebacks before they're filed explains.
When Breach Notification Before Confirmation Becomes Required Notice
A holding statement is voluntary. Legal notice is not, and it runs on its own clock.
State law. According to the National Conference of State Legislatures, all 50 states, the District of Columbia, Guam, Puerto Rico and the U.S. Virgin Islands have laws requiring businesses to tell people when certain personal information is breached. Privacy Rights Clearinghouse's 2026 survey, which covers statutes enacted as of Jan. 1, 2026, counts 20 states with a fixed deadline for notifying consumers, ranging from 30 to 60 days. The rest use language such as "without unreasonable delay."
The survey puts California, Colorado, Florida, New York and Washington in its 30-day group. Other states can land there too, depending on how a statute is read. Maine's Bureau of Insurance, for example, says notice must go out no more than 30 days after a business is aware of the breach and has identified its scope. Surveys sort these laws differently, so check the statute in every state where you have customers instead of relying on any single list.
Many states also require notice to the attorney general or another state agency, often once the number of affected residents passes a set threshold. States also differ on when the clock starts. In some, Florida among them, it starts at discovery of the breach, not on the day the forensic report arrives.
Network rules. Visa's notification window is a card network rule, not a law. It runs through your acquirer and applies whether or not any state law is triggered. Mastercard and the other networks have their own procedures for compromises, and your acquirer will tell you which ones apply.
Here's how the deadlines stack up in an illustrative case. An online store on a self-hosted platform finds a suspected compromise of its checkout page on Day 0. Forensics later confirm that customer names and card numbers were exposed. The affected customers live in Florida, Ohio and Texas.
| Obligation | Source | Deadline (illustrative, Day 0 = discovery) |
|---|---|---|
| Tell your acquirer so Visa is notified | Visa network rule | Within 3 calendar days |
| Notify Florida residents | Florida state law | Within 30 days |
| Notify Ohio residents | Ohio state law | Within 45 days |
| Notify Texas residents | Texas state law | Within 60 days |
Because states start the clock at different points, the table assumes the earliest start. In practice you send one notice to everyone, which means Florida's 30 days sets the schedule. If forensics take three weeks, you have about one week left to draft, review and mail the notices. That's why you should have a lawyer and template letters ready before anything happens.
Whether an incident triggers any of these laws depends on how each state defines covered data and what exceptions it allows. Treat this as general information and confirm the details with a qualified attorney. Our Intermarché breach notification checklist covers what goes in the notice itself.
A Retailer Cyberattack Response Plan That Fits on One Page
Small and mid-size merchants don't need a 40-page playbook. They need one page someone can find at 7 a.m. on a Sunday:
- Who decides. One person in charge of the response and one backup, with mobile numbers.
- Who to call. Your acquirer's risk or security line (not general support), your insurer's claims line, a breach lawyer, a forensics firm, and your gift card, loyalty and gateway vendors.
- What not to touch. Isolate affected devices. Don't reboot or wipe them.
- What to say. A holding statement written in advance, with blanks for the date, the facts and the next update time, plus the three-line staff script.
- Where updates live. One page on your website, linked from your social accounts and receipts.
- How often. A set update schedule that you keep, even when the update is "no new findings."
- What needs legal sign-off. Anything that says data was or wasn't taken, and every customer notice.
The most useful thing you can do this week is call your processor and ask: if we suspect a compromise, whose number do we call, and what will you need from us in the first 72 hours? If you're reviewing your payment processing setup anyway, a MannyPay specialist answers quote requests within one business day. Then keep an eye on the Coles Group updates page. Its next statements will show whether "no evidence to date" held up.
Sources
- Updates From Coles Group (statement and customer FAQs, current as at Nov. 16, 2026, 8:30 a.m.)
- Coles Investigates Cyber Security Incident (Computer Weekly, Nov. 16, 2026)
- Supermarket Group Coles Investigates Cybersecurity Incident but Provides Little Detail (ABC News, Nov. 16, 2026)
- ASX Falls as Miners Drag, Coles Investigates Cybersecurity Incident: As It Happened (ABC News, Nov. 16, 2026)
- 'Shop as Normal': Coles Investigates Cyber Attack (InDaily, Nov. 16, 2026)
- Visa, What To Do If Compromised (Visa Public, 2016–2020 edition)
- Visa, What To Do If Compromised: Visa Supplemental Requirements, Version 5.0 (earlier edition)
- Visa, What To Do If Compromised: Fraud Control and Investigations Procedures (2008 edition)
- FTC, Data Breach Response: A Guide for Business
- NCSL, Security Breach Notification Laws
- Privacy Rights Clearinghouse, Data Breach Notification Laws: A 50-State Survey (2026 Edition)
- Maine Bureau of Insurance, Risk to Personal Data FAQs
- Fortra, State Data Breach Laws: Who to Notify and How Long You Have to Do It
- Jackson Lewis, State Data Breach Notification Laws: Overview of the Patchwork
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.


