The FTC Will Let You Personalize Prices. You Just Have to Write the Sentence First.
· CX Pulse
The FTC's proposed policy says a personalized price needs a disclosure naming the basis and the data behind it. Writing that sentence is the whole test.
The Federal Trade Commission published a proposed enforcement policy statement on personalized pricing on August 19. The public comment window is open until September 25. It's eight pages, it passed on a 2-0 vote, and almost nobody in retail has read it. That's a mistake, because the standard it sets lands on a product page rather than in a legal department.
The Commission isn't proposing to ban personalized pricing, and says plainly that Congress hasn't given it the authority to. What it proposes is a disclosure test.
The standard is built on what customers expect
The operative sentence: "Where consumers reasonably expect that prices for a product or service will not vary based on their personal data, businesses that engage in personalized pricing should clearly and conspicuously disclose not just that the price is personalized, but also the basis for that personalization and the types of data on which the personalization is based."
Failing to do that, the Commission writes, "is likely to constitute an unfair or deceptive act or practice in violation of Section 5."
Read the trigger again. It's customer expectation. Whether your pricing needs a disclosure depends on what a reasonable customer loading your product page assumed was true. A regulator has taken a question that lives in customer research and made it the thing that decides legal exposure.
Chairman Andrew Ferguson put it plainly in the announcement: "When consumers see a listed price, they expect it to be same price that everyone else sees, not the retailer's estimate of how much they are willing to pay based on their personal data."
The part that should stop a pricing team
The statement names a specific phrase as inadequate. Telling a customer only that they're seeing a "specially selected" price, it says, "would likely be misleading because it omits important information."
That's the copy sitting on a great many e-commerce pages right now. Just for you. Your price. Selected for you. All of it clears the bar for marketing and none of it clears the bar the Commission has drafted.
Then the statement does something more useful than most regulatory documents manage. It gives an example of a disclosure that probably would work: one saying a personalized price is "based on a consumer's estimated willingness to pay derived from data about that consumer's previous purchases from the same retailer through the same login account."
Write that onto a product page and read it back. "This price is based on our estimate of what you personally will pay, calculated from your purchase history." It's accurate, it's compliant, and no retailer is going to put it above a buy button. The disclosure that satisfies the rule is the disclosure that kills the tactic, which tells you most of what you need to know about whether to run the tactic.
Seven scenarios, and what they aren't
The statement closes with seven examples that would raise concerns without adequate disclosure. A hotel charging more when the data suggests the guest is travelling for a funeral. A rideshare company charging more for a trip to a medical facility. A retailer charging more for a home security system because court filings show the customer was recently the victim of a crime.
These are the Commission's own illustrations, offered for discussion. The statement is explicit that they aren't findings about any company and aren't definitive positions on legality. Worth being precise about, because the list is vivid enough to get repeated as though the FTC caught somebody doing it.
Where this lands at scale
A large retailer has three problems here, and none of them belong to the pricing team alone. The disclosure has to live somewhere: clear and conspicuous means the product detail page and the checkout, owned by digital and merchandising, while naming the basis and the data types needs data governance to supply it accurately.
Consent is the second, and it has the longest tail. The statement warns that businesses basing prices on personal data "without sufficiently verifying that consumers consented to the collection of those data for that purpose may violate Section 5." Anyone buying third-party segments now has to show that data was consented to for pricing. Not for advertising, not in general.
The third problem arrives in the contact centre, and it'll arrive first. Customers compare prices with each other constantly. When one calls to ask why their price differs from their neighbour's, the agent needs an answer that's true, and somebody has to write it, approve it, and get it into the knowledge base before the call comes in. Most personalization stacks can't say which signal produced a given price, so the honest answer may not be available to the agent at all.
The smaller operation has a different version
A small retailer probably hasn't built a pricing engine. They're quite likely to have installed an app offering dynamic pricing, segment discounts or personalized offers, switched it on, and never read what it does. The default copy those tools ship with is the exact "specially selected" language the statement singles out. Nobody decided to run personalized pricing. It came switched on inside something else.
The 20-second version
Write the sentence. If your prices vary by customer, write the plain sentence that says so, names the basis, and names the data. Then decide whether you'd put it on the page.
If the answer is no, you've learned something about the pricing practice, and it arrived without a lawyer, a vendor or a project. The comment window is open until September 25 for anyone who wants the Commission to hear from the people who'd have to implement this.