As of November 9, 2026, two pricing actions out of Washington have made shelf accuracy a compliance question for U.S. retailers. The Federal Trade Commission, joined by 20 states, sued Dollar General for allegedly deceptive pricing, with a complaint that describes prices at the register running higher than the shelf tag and details an undercover investigation by the agency. Days later, the FTC sent orders to nine companies, including Walmart and Target, asking them to explain whether the price a shopper sees for a ticket, a ride or a delivery can vary from one person to the next based on data analysis. Dollar General said it aims for complete pricing accuracy but that occasional price discrepancies can occur.
Two cases, one question
The two actions point at different systems but the same outcome: the price a shopper is charged has to match the price that was shown. In the first case the mismatch is between a shelf tag and a register, which is an execution problem inside the store. In the second it is between one shopper and another, which is an analytics problem that starts in customer data. Both end up on the receipt, and the receipt is what a regulator can read.
The timing is not accidental. The agency's attention turned to pricing as consumers and retailers headed into the holiday season, a period when promotional depth and markdown cadence both rise. When a retailer runs a different offer for loyalty members, a different price for a first order and a different bundle for a delivery slot, the number of price points the shopper can be charged multiplies, and so does the number of places where a tag can go stale.
Shelf tags are the new audit trail
For years the shelf tag was a merchandising artifact, printed and replaced by store staff. It is now evidence. If a regulator can walk a store and compare tags to receipts, then a retailer's price monitoring has to be able to do the same thing at scale, on the same day, before anyone else does it. That means a tag audit that runs continuously rather than a quarterly compliance sweep.
Personalized offers under orders
The personalized pricing inquiry widens the problem. If offers are generated per shopper, the reference price is no longer a single tag but a range, and the retailer has to be able to show why a given shopper saw a given price. Documenting the inputs, the segment and the offer logic becomes as important as the price itself, because the defense is procedural, not numerical.
Deal fatigue meets price monitoring
Shoppers are also pushing back on discount theatre. Retailers heading into the holidays are already adjusting campaigns around deal fatigue, with some brands trying to reduce the number of promotions rather than add more. Fewer, deeper offers concentrate risk: a single mispriced promotion now carries more of the season's volume than it would have in a calendar full of small discounts, and a price gap that survives a week is more visible than one that lasts a weekend.
What the nine orders cover
The scope of the inquiry is easier to read as a list of questions than as a legal document. Each row below is a question a retailer should be able to answer about its own pricing before a regulator asks it.
| Area | Question asked | What good documentation looks like |
|---|---|---|
| Personalized pricing | Does the price vary by person | Segment logic and inputs recorded per offer |
| Shelf versus register | Does the tag match the charge | Daily tag audit with exception log |
| Promotional depth | Is the reference price genuine | Price history kept for the full season |
| Delivery and fees | Do fees change by user | Fee rules published and versioned |
None of this requires new technology so much as a decision about where the record lives. Retailers that already run price monitoring for competitive reasons have most of the machinery; what changes is that the output now has to be defensible rather than directional. A dashboard that shows a price gap is useful for a merchant; a log that shows what the tag said at 10 a.m. and what the register charged at 10:05 is what a compliance team needs.
Action list
Treat the holiday season as a pricing audit period. First confirm that every promotional price has a documented reference, then run a daily tag-to-register check in the highest-volume stores, and finally keep a versioned record of offer logic for any personalized discount so the reason a shopper saw a price can be reconstructed later.
- Document every reference priceKeep the pre-promotion price and the dates it applied, so a discount can be shown to be genuine rather than nominal.
- Run a daily tag checkCompare shelf tags to register prices in top stores every day during the season, and log every exception with a timestamp.
- Version the offer logicRecord the segment, inputs and rules behind each personalized offer, so a price can be explained months later.
FAQ
What is the FTC actually asking retailers to do?
Make the charged price match the shown price, and be able to explain how a personalized price was set. The first is an execution control, the second is a documentation control.
Why does personalized pricing attract scrutiny?
Because it removes the single reference price. When two shoppers see different prices for the same item, the retailer has to be able to show why, which means the inputs and the rules have to be recorded.
How does deal fatigue relate to pricing risk?
Fewer and deeper promotions concentrate volume into fewer price events, so one mispriced offer carries more of the season and a stale tag stays visible longer.
What should a price monitoring program capture?
The reference price, the promotional price, the tag price at a point in time and the price actually charged, with timestamps for each so a gap can be reconstructed.
