From feed to compliant outputs — in a few steps

Connect your product feed, build an independent price evidence log, calculate Omnibus outputs correctly, and display them via widgets or exports.

View pricing See features
•Exact capabilities depend on your plan and settings (window length, widget type, exports, frequency).
Quick overview
The system is designed for compliance and evidence. You get outputs you can show to customers and defend during a control.
Setup ~10 minutes
Data source XML feed / API
Result audit-ready outputs
1) Connect feed 2) Build evidence 3) Alerts & quality 4) Widget & display Calculation logic Exports & reports FAQ

Process in 4 steps

A simple flow that produces legally relevant outputs, not just analytics.

1
Connect
Add your feed and mapping so the system knows how to identify products and prices.
2
Monitor
Scheduler imports prices, stores only changes, and builds an evidence-grade history.
3
Calculate
Omnibus outputs are computed correctly, including availability and window rules.
4
Display / Export
Show the output in a widget (text/badge/chart) and generate PDF/CSV exports.

Step 1: Connect your feed

Start by adding your XML feed (or API, depending on plan) and defining how products are matched.

•If your feed has variations, we can track variants separately or group them — based on configuration.
What you configure
  • Feed URL and basic access
  • Product identifier (SKU / item ID / URL)
  • Price fields and availability signals
Checklist (2 minutes)
  • Feed loads reliably (HTTP 200)
  • Each product has a stable identifier
  • Price fields are present and consistent
  • Availability is provided (recommended)

Step 2: Build an evidence log

Instead of saving full snapshots, the system stores changes with validity intervals — scalable and audit-friendly.

•This is independent from your e-shop database, strengthening evidence credibility.
Example
Price stays the same for 10 days → stored as one interval. If it changes, a new interval starts.
•This is why it scales well for large catalogs.
What is stored
  • Price changes with timestamps
  • Availability changes
  • Import runs and errors (audit trail)

Step 3: Alerts & data quality

Get notified about important changes and catch feed issues before they affect compliance outputs.

•Alert channels and thresholds may depend on plan and settings.
Alerts
Notifications about price, availability, or import anomalies.
Quality checks
Detect missing fields, suspicious values, and broken runs.
Typical triggers
  • Sudden price drop/spike
  • Product becomes unavailable / returns
  • Feed import fails or missing required fields

Step 4: Display and exports

Show the correct output on product pages and generate reports when needed.

•Widget type and styling options are plan-based.
What you can publish
  • Lowest price in the configured window (Omnibus)
  • Price trend chart
  • Badge-style label (trust / compliance)
Widget types
  • Simple text (lowest price)
  • Chart (price development)
  • Badge (label)

Calculation logic (compliance focus)

The goal is a defensible “lowest price” based on real history — with availability rules respected.

Key principles
  • Calculations are based on real historical prices in the configured window
  • Availability can pause/reset the window depending on settings
  • Outputs are designed to be defensible during a control
•Exact legal window length and behavior are configurable and may depend on plan.
Why independent evidence matters

It is harder to dispute data that is stored outside the e-shop system and logged with audit context.

  • Append-only style audit trail
  • Import run history (when/what happened)
  • Exportable proof for products or lists

Exports & reports

Generate compliance-ready exports for one product or for selected product lists.

What you can export
  • PDF report (audit-ready)
  • CSV export for analysis
  • Filtered by period and product selection
  • Batch exports for larger catalogs (plan-based)
Security & storage

We store evidence independently and protect access; your e-shop database remains untouched.

  • Independent storage separate from your e-shop DB
  • Access control and audit context
  • GDPR-friendly approach (only necessary data)

FAQ

Common questions about setup, calculations, widgets and exports.

No. You connect via feed (or API). Evidence is stored independently and the widget is embedded as a simple snippet.

At least once per day. Higher frequency is available depending on your plan and system load.

Yes. Exports support single products and product lists, with period filters (plan-based features may apply).

Yes. Widget types include text, badge and chart. Availability depends on your selected plan.
Get compliant outputs without manual work
Connect your feed, let the system monitor prices, and publish or export the results when needed.
View pricing See features