Omnibus Directive

When you advertise a price reduction in the EU, you have to show what the product actually cost before. This extension keeps that number for you — the lowest price of the preceding 30 days — and prints it beside the reduced price on product pages, category listings and search results, so a promotion can go live without anyone compiling price history by hand.

Latest version: 2.0.0 — changelog

Why it matters

• Price promotions stop being a legal risk. Article 6a of Directive 2019/2161 requires the prior lowest price alongside any announced reduction. The figure is produced automatically, so a campaign does not wait on someone exporting price history.
• The number is computed, not typed. A per-product, per-website, per-customer-group index tracks the running 30-day minimum, so nobody maintains a spreadsheet and nobody forgets to update one.
• Reductions driven by integrations are covered too. Price changes arriving by REST, by bin/magento import or from an ERP record history exactly as admin-panel edits do.
• It renders where customers actually see prices — product page, category grid, search results, and CMS-driven landing categories that use a Catalog Products List widget.
• Storefront cost stays flat. Listings read the whole page's prices in one batched query, and stores on Smile ElasticSuite can serve them straight from the search index instead.

Features

Feature	Benefit
Dynamic pricing from a pre-built minimum-price index	The displayed figure is derived from real price history rather than a value someone has to keep current
Static pricing from a product attribute	Lets you carry a figure you already hold, when history lives in another system
Show on Product Listing Pages	The prior price appears in category grids and search results, not only on the product page
Show on Product Detail Pages	The prior price sits with the price block customers are actually reading
Always Show Historical Price	Choose between showing the figure only after a genuine reduction, or at all times
Store-view and website scoping	Different countries on one installation can be configured independently, which is what a per-country requirement needs
Hyvä companion module	The same figure on a Hyvä storefront, with Tailwind-safe markup
ElasticSuite companion module	Listing prices come from the search index, with an automatic fallback to the database

What sets it apart

• Hyvä-native. qoliber/omnibus-directive-hyva ships real Hyvä layouts and templates, registered with Hyvä's Tailwind scanner — not a Luma template forced into a Hyvä page.
• No third-party service. Price history is computed and stored inside your Magento database and, optionally, your own search index. Nothing about your pricing leaves the store.

Also available in: Polish.

Supported versions

PHP 8.1 – 8.5. magento/framework >= 103.0.0 < 104 and magento/module-catalog >= 104.0.0 < 106 — Magento Open Source 2.4.7–2.4.8 and the equivalent Mage-OS releases. The Hyvä and ElasticSuite companions are optional and installed separately.

Next steps

• Install it
• Configure it