Magento 2 Omnibus directive: the lowest price of the last 30 days
SKU: OMNIBUSPRICETRACKER1
- Price history recorded automatically per product and customer group
- Lowest price of the last 30 days shown with price reductions
- Display on listing, product page and in the cart
- Proof export as CSV for your documentation
Einmaliger Kauf · inkl. 12 Monate Updates · zzgl. MwSt.
Magento 2 Omnibus directive: reference price automatically from the price history
Mironsoft Omnibus Price Tracker implements the Magento 2 Omnibus directive in your shop. The module records every price change and, whenever a price reduction is advertised, shows the lowest price of the last 30 days. In Germany this is set out in section 11 of the Price Indication Ordinance (PAngV), which derives from the EU directive on better enforcement of consumer protection.
For shop owners the Magento 2 Omnibus directive is above all a documentation task: whoever sets a special price in the admin today often cannot say, on the day of a warning letter, which price applied 25 days ago. The module provides that history without gaps, per product, website and customer group, including catalog price rules and scheduled campaigns.
It is built for Hyvä Themes, changes no prices and loads no additional JavaScript. The legal assessment of your campaigns remains with you or your legal adviser; the module provides data and display.
The reference price comes from your own price history
If you advertise a price reduction, you must state the lowest price of the last 30 days. For the Magento 2 Omnibus directive, the module handles recording and display.
Price history, automatic
Every price change is stored with timestamp, website and customer group.
All price sources
Base price, special price, catalog price rules and imports are captured, including scheduled campaigns.
Lowest price in 30 days
With a visible reduction, the reference price appears next to the sale price.
Progressive reductions
If a price is lowered in steps, the price before the first reduction stays the reference.
Listing, product page, cart
Display locations switchable one by one, text and format per store view.
Proof and clean-up
CSV export for your documentation; old entries are deleted after the retention period.
Magento 2 Omnibus directive: gap-free recording, even for scheduled prices
The module writes an entry to its own history table on every price change. Because catalog price rules and scheduled special prices change their value without a save action, a daily cron run additionally compares the prices that are actually valid. This leaves no gaps in the history, not even after imports.
Multi-currency shops keep the history per website and currency. A change of tax class alters the gross price, which is why the module stores the final price as actually displayed.
- Entry per product, website and customer group
- Daily comparison for rules and schedules
- First entry at start from the current price
The reference price under the Magento 2 Omnibus directive exactly when it is required
The notice appears only for a genuine price reduction, meaning the displayed price is below the previous one. It states the lowest price of the 30 days before the reduction began. Text, placeholders and location are freely adjustable per store view. Without a reduction the page stays unchanged.
Prices for reseller groups can be excluded from the notice if the campaign is not aimed at consumers. You decide this per customer group.
- Placeholders for price and period in the text
- Separate locations: listing, detail, cart
- No notice when there is no price advantage
New products, stepped campaigns, proof when asked
Products that have been in the range for fewer than 30 days are computed from their real history and are not padded with invented values. If a campaign runs in several steps, the price before the first step stays the reference. In the admin grid you see each product’s history and export it as CSV in case a competitor or an authority asks for evidence. Legal assessment of your campaigns remains with you or your legal adviser.
Notes on the legal position are provided without guarantee. For special cases such as perishable goods or market-driven price changes you should involve your legal adviser.
- Short history shown openly, nothing is padded
- Stepped reductions with a fixed reference
- CSV export and configurable retention
Inspect and export the price history in the admin
Under Catalog in the admin you find a grid with all recorded price changes. You filter by SKU, website, customer group and period and see at a glance which reference price is currently computed. For the Magento 2 Omnibus directive this is the key evidence: one click exports the history as CSV.
- Filter by SKU, website, group and period
- Computed reference price visible per product
- Permission adjustable via ACL
Where the Magento 2 Omnibus directive applies in daily shop work
Sales and seasonal campaigns
In the summer sale the price drops in steps over weeks. The Magento 2 Omnibus directive keeps the price before the first reduction as the reference.
Catalog price rules
Discounts via catalog price rules trigger no save action on the product. A daily comparison makes sure they are not missing from the history.
Price imports from the ERP
Weekly price lists from an ERP change many prices at once. Every change lands in the history with a timestamp.
Warning letters and audits
If a competitor or an authority asks for evidence, you export the price history of a product as CSV.
Manual documentation versus Magento 2 Omnibus directive
| Criterion | Without the module | With Omnibus Price Tracker |
|---|---|---|
| Price history | Spreadsheets or memory | Automatic per product and customer group |
| Catalog price rules | Not traceable | Daily comparison of valid prices |
| Reference price display | By hand in the text | Automatic with a genuine reduction |
| Stepped reductions | Error-prone | Fixed reference before the first step |
| Evidence | Laborious to piece together | CSV export per product |
| Clean-up of old data | No deletion rule | Retention period configurable |
How we set up the Magento 2 Omnibus directive in your shop
1. Capture the current state
We take the current prices as the starting value of the history.
2. Define rules
Reference period, display locations, texts and customer groups are set.
3. Installation and cron
We install the module and activate the daily comparison.
4. Verification
Joint check with sample products, then handover.
How it differs from related Mironsoft modules
Discount Percentage
Shows the discount as a percentage. The Magento 2 Omnibus directive adds the legally required reference price from the history.
Product Labels
Puts campaign badges on products. This module records prices and does not influence labels.
Daily Deals
Controls time-limited offers. The Price Tracker documents their prices and shows the reference price alongside.
No download — personal setup instead
The Magento 2 Omnibus directive solution Omnibus Price Tracker is not offered here as a download file for self-installation. The purchase is a service commission: we install the module in your shop, start the recording and agree on texts and display locations together with you. The module is not a substitute for legal advice.
Frequently asked questions
Everything about recording, display and how the purchase works.
What does the Magento 2 Omnibus directive require exactly?
Does the duty apply to B2B shops too?
From when is a history available?
Are catalog price rules considered?
Does the module change my prices?
Can I download and install the module myself?
How can I show the lowest price of the last 30 days in Magento 2?
How can I prove the price history for the Magento 2 Omnibus directive in Magento 2?
Does the module work with Hyvä Themes?
How long is price data kept?
Recently Viewed Products
Magento 2 Omnibus directive – Mironsoft Omnibus Price Tracker