The Omnibus Directive requires that a price reduction be measured against the lowest price applied in the 30 days before it. That is a question about a series, not a current value — and most systems only store the value. The record below is the live record for this store: what each item costs now, what the prior-lowest reference is, how many observations support it, and when it was last seen. Nothing here is retyped for display — nothing here is even stored in this page — it is the same record an auditor exports, bound at the moment you view it.

The cards below are not stored in this page. A custom element binds at view time to the same public endpoint every other surface uses — Shopify, AEM, WordPress render the identical record, and none can drift, because none holds a copy. A 30-day low renders only where the observation record covers the full 30-day window; anywhere it does not, the surface says so instead of showing a number — an unverifiable reference is worse than none, because it is the thing a regulator would test.

Prices are observed on a schedule and each observation is written to an append-only record with its timestamp, currency, market, and the geographic context of the observation. The 30-day reference is recomputed from those observations rather than asserted; the sample count and coverage window above are what that computation had to work with. The same rows stream to the data warehouse and export as an auditor's CSV, so the page, the warehouse, and the export cannot disagree.