Suspicious - given the last time W were hacked and did not publicly acknowledge it.....
Makes me wonder if another attempt has been underway for the last couple of days.
Running multiple self-checkout system that each interface with multiple databases (WRewards, inventory, GC, eftpos to name a few) creates great opportunity to test for unforeseen issues.
As each area generally has its own IT staff (previously known as programmers or contract programmers) who mostly work in their own silos - stupid and preventable mistakes abound. Nothing like one variable name being used by different teams in the interlinked programs.
Couldn't happen?
One of the largest Finance Groups in Australia had to delay the sending out of all tax year info to over 300,000 customers for nearly 7 months (and got an ATO extension for all customers) for just this reason. Where a variable was defined and used by 2 different s within the programming teams. So all tax data was corrupted.
Oh those enhancements!