94 pages, 20 states and tens of thousands of customer complaints describe one failure mode: a price on the shelf that is not the price at the register. The Federal Trade Commission and 20 attorneys general sued Dollar General in October 2026, alleging that thousands of stores charged more than the displayed price and that the company did not fix the problem after being told about it. The case resurfaced in November coverage of the chain expansion onto Instacart, where item prices are promised to match shelf prices. As of November 17, 2026, the allegations remain allegations, and the retailer has not responded in detail in the coverage reviewed here.
The gap is a data problem before it is a legal one
Price accuracy looks like a store operations issue until you trace where the number comes from. A single product record carries a base price, a promotional price, a regional override and a shelf-label template. Change one and forget the others, and the register and the shelf disagree until someone notices. At thousands of stores, nobody notices until a customer complains.
That is why the same failure now reaches e-commerce. When a retailer promises that delivery prices match shelf prices, the digital price inherits the accuracy of the store price file. An error that used to be visible only at a register becomes visible in an app, at scale, with a timestamp attached.
Three controls that actually catch drift
Most retailers already have a price-change process with an owner, a schedule and a system behind it. The gap is verification, which is treated as a store duty rather than a control. Three cheap additions change that, and none of them requires new hardware or a new system of record.
| Control | What it produces | Why it works |
|---|---|---|
| Weekly sample audit | Photo and timestamp per SKU | Catches drift before complaint volume does |
| Exception report | SKUs whose register price differs from file | Separates data errors from label errors |
| Complaint tagging | Reason codes for price disputes | Turns complaints into a measurable defect rate |
The second row is the one most organisations skip. A register that disagrees with the price file is a systems problem. A label that disagrees with both is a task problem. Fixing them with one process guarantees that neither is fixed.
What brands should check in their own files
Suppliers are not defendants in this case, but they are often the source of the base price. A brand that ships price updates late, or ships them with an effective date that differs from the retailer calendar, creates exactly the window where a discrepancy can live. Checking the last two quarters of price files for late or conflicting updates is a morning of work with a clear payoff.
Why this matters beyond one retailer
Price transparency is moving from a marketing promise to an enforcement issue. Regulators now treat the shelf price as a commitment, not an estimate, and the complaint volume that triggers action is generated by ordinary shoppers at ordinary checkouts. The same logic will apply to delivery and pickup, where the comparison is easier to document because the app records both prices.
What the control costs
For brands, the practical lesson is unglamorous: keep one price record, publish it everywhere from that record, and verify the last mile where a human applies it. Price monitoring at that scale is cheaper than price litigation, and it leaves a trail a regulator can read without subpoenaing a store manager. The cost of the control is small compared with the cost of explaining, years later, why the same item had three prices in the same store.
FAQ
Q: Why does a shelf-price case matter to e-commerce teams?
A: Because the same master data feeds both. If the shelf label, the shelf tag and the app disagree, the online price is part of the same failure, and the complaint record will show it.
Q: Is this a technology problem or a process problem?
A: Mostly process. Price files can be updated accurately and still fail at the shelf if the label change is treated as a store task without verification.
Q: What is the cheapest control?
A: A weekly audit of a fixed sample of SKUs per store, recorded with a photo and a timestamp. Sampling beats full-store audits on cost and catches drift early.
Q: How should a brand respond when a retailer is accused?
A: Check your own price files for the same window. If your data was part of the discrepancy, correcting it before the regulator asks is cheaper than explaining it afterwards.











