Personalized price and Brazil's CDC: the line between dynamic pricing and charging each customer differently

Dynamic pricing and personalized pricing look like the same thing and are not. The rule looks small. The legal effect is not.

Dynamic pricing changes an item’s price over time, the same for everyone looking at the shelf at that moment. Personalized pricing charges different amounts to different people, based on each one’s profile. The first is common practice. The second crosses Brazil’s Consumer Defense Code and the LGPD.

What the rule says, in plain text

The Consumer Defense Code (Law 8.078/1990) forbids abusive practice and requires clear price information. Charging a customer more because the data suggests they would pay more enters the territory of price discrimination, which Senacon monitors.

Add the LGPD. Personalizing price uses personal data to set a commercial condition, and that requires a legal basis, a purpose, and transparency. Anyone who works the operation needs to know that the vendor’s “smart price” may in fact be sensitive data poorly wrapped.

The systems the rule touches

It is not only the pricing engine. The rule reaches what feeds it.

• Dynamic price by hour or stock, the same for everyone, sits on one side, the safer one.
• Personalized coupon and offer by history sit in a gray zone, depending on consent and transparency.
• Different price by geolocation or by the customer’s device sits on the risk side.

What changes for those who thought they were compliant

Being compliant with dynamic pricing does not cover personalization. The difference sits in three points to audit this quarter.

First, whether price varies by context (hour, stock) or by person (profile). Second, what legal basis supports the use of personal data, if any. Third, whether the customer can understand why they saw that price, because opacity becomes a complaint and the complaint becomes a lawsuit.

The second-order effect almost every plan ignores

The rule changes pricing vendor selection. The question stops being “does the engine raise margin” and becomes “does the engine charge differently per person, and on what basis”.

Telling legal apart from enforced is part of the work. Transparent dynamic pricing is a known path; opaque personalized pricing is a liability waiting for the trigger. It is the same discipline as elasticity measured on sales and cameras under LGPD: the data needs a declared purpose.

Think about the pricing project legal already side-eyed and operations ran anyway. That is the one the audit catches first.

Send me the list of pricing mechanisms your operation uses or plans: dynamic by stock, personalized coupon, price by region, whatever it is. In one hour I will send back a one-page gap analysis: what is a safe path, what is a gray zone, and what needs a legal basis before turning it on. If a front becomes a project, the two-week Diagnóstico is the next step. We do not give legal opinions; we map the operation against the rule.