For retailers

Bring your catalog to shoppers who are ready to compare

CenuFiltrs helps retailers publish structured offers, stay current through feed updates, and give shoppers a clearer path from discovery to checkout.

Read the Merchant Terms before applying

Offer-first visibility

Your offers can appear where shoppers compare real buying options, not just browse category pages.

Structured onboarding

Move from feed review to launch through a clear setup path with practical next steps.

Validation before launch

Check XML, JSON, or text feeds before they affect live offer quality.

Registration

One account for everything

There is no separate merchant sign-up. Start by creating a personal CenuFiltrs account (or signing in to your existing one), then submit the merchant application from the same account. Your merchant profile stays permanently linked to that personal account.

Supported platforms

Works with your platform

Each of these has a ready-made export that gives you a feed address to paste into the connection form. If you already publish a catalogue to Google, to Meta or as YML, that file works unchanged.

  • WooCommerce
  • PrestaShop
  • OpenCart
  • Magento (Adobe Commerce)
  • Shopify
  • Shopware 6
  • Wix Stores
  • Ecwid
  • Tilda
  • 1C-Bitrix
  • Odoo 19+
  • VirtueMart (Joomla)
  • Google Shopping
  • Meta catalogue
  • Yandex YML
Why retailers join

A more credible public presence, not just another listing

The page should explain the value quickly, then prove that onboarding is practical.

Reach shoppers with intent

CenuFiltrs is built around active comparison, so visibility starts closer to purchase intent than broad awareness campaigns.

Keep offers current

Use a feed or endpoint that can be validated, updated, and reviewed without rebuilding your catalog flow.

Support trust with cleaner data

Structured fields, predictable review steps, and validator tools help your offers look consistent before launch.

Launch flow

Three steps from feed to live visibility

The goal is not to impress with complexity. The goal is to make launch expectations clear, check data quality early, and keep the next step obvious.

How onboarding moves

  1. 1

    Share your source

    Start with the feed or endpoint you already maintain, then align it to one supported integration path.

  2. 2

    Validate before review

    Run your feed through the validator tools first so structural issues are easier to fix before launch.

  3. 3

    Review and publish

    Once the core fields are stable, the merchant flow can move into review, visibility checks, and activation.

Required fields

  • Unique product ID
  • Product title
  • Current price in EUR
  • Product URL
  • Category or taxonomy path
  • Availability status
  • Retailer or store name

Helpful extras

  • Product image URL
  • Brand or manufacturer
  • Short product description
  • Delivery or stock details
  • Attributes or specifications
  • Warranty information

Your shop may already be in the catalog

We import public product feeds, so many Latvian shops are already listed here without their owner having signed up. If you find yours, confirm ownership with a code we send to the shop's official contact address — after that you manage the listing, its feed and its visibility yourself.

Find my shop
Integration paths

Choose the feed path that fits your stack

Keep the setup grounded in what your team can maintain well, not just what looks most technical.

XML feed

Best for retailers that already export catalog feeds and want a predictable launch path.

Complexity
Easy
Typical setup
Subject to successful validation
  • Good fit for scheduled catalog updates
  • Works well with large structured assortments
  • Clear validator path before review
Open XML validator

JSON API

Best for teams that already expose product data programmatically and want tighter control over updates.

Complexity
Medium
Typical setup
Subject to successful validation
  • Flexible for custom product attributes
  • Useful when data changes frequently
  • Good fit for engineering-led integrations
Open JSON validator

CSV or text feed

Best for smaller catalogs or faster pilots where the team wants the simplest possible first step.

Complexity
Fastest
Typical setup
Subject to successful validation
  • Quickest route to a first review
  • Lower lift for leaner teams
  • Useful for early testing before automation
Open text validator
Support and launch quality

Use the tools first, then bring in sales when needed

The strongest merchant experience is clear about what can be self-checked, and what should move into a conversation.

Resources

Contact sales

Discuss onboarding, commercial fit, and next steps with the team.

Contact sales

Merchant application

Start the merchant review flow when your store is ready for activation.

Open application

Validation tools

Test XML, JSON, and text feeds before you hand over final integration details.

View validators

What strong onboarding looks like

  • Core fields are present and stable.
  • The feed format matches one supported integration path.
  • Validators pass before the first manual review.
  • The merchant team knows who owns updates after launch.

Ready to make your offers easier to compare?

Start with the merchant application if you are ready to onboard, or contact sales first if you want to talk through fit.