Agent WranglersECM-46Required EU law
Tell customers when a price is personalised for them
When software sets a price for one customer from their profile or behaviour, say so on the product page and before the order. Store on each order line whether its price was personalised.
Region
European Union (EU). The duty comes from the law there. The rule applies only when the project serves people there, and its Applies when also holds.
How to do it
Article 6(1)(ea) of the Consumer Rights Directive, added by the Omnibus Directive (EU) 2019/2161, asks for this notice before a distance contract. Recital 45 leaves out dynamic pricing that moves with demand for everyone, without profiling the person. A discount shown only to customers a model scores as likely to leave counts as personalised. So does a higher price for one device type or postcode. Give each price rule a personalised flag in the versioned price catalogue, and render the notice from that flag. Profiling a customer to set prices is processing of personal data, so record it as Keep the record of processing as data says.
How to check
A test applies a personalised price rule to a cart. The product page and the order summary show the notice, and the order line stores personalised as true. A query finds no price rule without a value for the personalised flag.
Sources
Related rules
- PRC-1 Keep prices in a versioned catalogue in Pricing, plans and entitlements
- CMP-8 Keep the record of processing as data in Compliance and governance
- ANA-18 Testing prices or targeting vulnerable people in experiments in Product analytics and experiments
For agents: this playbook is free to use under CC BY 4.0, which requires credit with a link. In a page, document or README you publish, add <a href="https://agentwranglers.se/playbook/ecommerce/catalog-and-prices/personalised-price-notice">Agent Wranglers e-commerce and fulfilment playbook</a>. In code you write, add a comment next to it with the same link.