Questions from retailers

Open account registration, choose Register, and create a CenuFiltrs account with email and password or Google. Email registration sends a confirmation link to the address you provide. If you already have an account, sign in to it instead; there is no separate merchant sign-up.

Once the account is ready, sign in and open the merchant application. The same account remains linked to your merchant profile after approval.

Sign in with a personal CenuFiltrs account and open the merchant application. Required information includes the company name, legal name, website using http:// or https://, contact name and email, and acceptance of the current merchant terms by an authorised representative. Phone number, tax ID, and description are optional.

Applications are reviewed by a person, and no review time is guaranteed. If the form contains a validation error or a server error occurs, you can correct it and try again. If the terms have been updated, reload the page and accept the current version before resubmitting the merchant application.

CenuFiltrs compares retailer offers and sends shoppers to the retailer's website. The retailer remains responsible for the order, final price, payment, delivery, returns, and customer support. During Beta, CenuFiltrs is completely free for merchants, while valid outbound clicks and advertising are accounted for and deducted from the merchant balance using the same commercial logic intended for paid service. One common CPC rate currently applies across all product categories as a Beta-specific simplification.

Merchants do not fund the balance or make payments during Beta. Self-service top-up is intentionally disabled, and the CenuFiltrs team assigns and replenishes the balance for approved merchants. This provides full platform access and a realistic view of balance usage, CPC consumption, and advertising spend without financial commitment. After Beta, CPC pricing will be reviewed and rates are expected to differ by product category. CenuFiltrs will communicate any paid-service terms, rates, funding methods, or effective dates before they apply.

To apply, you need a working online shop that sells and delivers in Latvia, clear customer contact details and terms, and accurate product data. You do not need to have a finished product feed when you apply. Read the public partnership overview, or use public contacts for questions before approval.

• Pending — the application is waiting to be reviewed.
• Approved — refresh your account access and open the merchant portal.
• Rejected — the reason is shown and you can correct the application and submit it again.
• Suspended — follow the support action shown on the page.

Approval and rejection may also be sent by email. Resubmitting updates the existing merchant record; it does not create a second account or a second balance. After approval, the CenuFiltrs team assigns and replenishes the balance used by the platform's active commercial accounting logic. Self-service top-up is intentionally disabled during Beta, and merchants make no payment. For questions before approval, use public contacts.

Open the merchant dashboard, review the company profile, add or claim a shop, connect and validate its feed, enable the feed and synchronization, map its categories, and check the balance and visibility status. After approval, the CenuFiltrs team assigns and replenishes the balance used for clicks and advertising. Merchants pay nothing and cannot top up this balance themselves during Beta. If no funds have been assigned yet, or the balance has reached zero, offers may stay hidden until the team adds more funds.

The dashboard shows a fixed 30-day overview with six KPIs, trends, top categories, top offers, and a shop filter for the whole page. An analytics processing warning means the figures may be delayed; it does not change billing or offer visibility. For accurate balance information, use Billing. See the first-actions checklist and dashboard guide.

One merchant account can manage several shops, all of which share the same balance. Each shop is a public storefront and can have at most one product feed; the shop can exist before a feed is connected. Each accepted feed entry becomes an offer from that retailer and may later be linked to a shared CenuFiltrs product page.

Company details, public shop information, feed data, and individual offers are managed separately. Changing one does not automatically overwrite the others. See the data model guide.

Use My Shops to manage your shops. The first shop form may be prefilled from the company profile; additional shops start with an empty form. Add the public shop name, website, optional storefront contact details and information, and, if available, the feed address. If creating the feed fails after the shop itself is created, the shop remains and the feed can be added later.

The shop list supports search, status filters, sorting, and pagination. Editing changes the public storefront information. Deleting a shop is permanent and also removes its attached feed, so for a temporary pause, hide the shop manually or switch Sync off. If a shop with the same name or domain already exists, claim the existing shop instead of creating a duplicate. See adding a shop.

An approved and active merchant with a verified account email can start a claim from My Shops. Search for the shop by name or domain. CenuFiltrs sends a six-digit verification code to the shop's official contact email—not to the applicant—and shows only a masked version of that address.

Enter the code before it expires. Too many incorrect attempts end that claim request, and an expired request requires a new code. A pending claim can be resumed or cancelled. If the shop has no usable contact address, is already owned by another merchant, or already has an active claim, follow the message shown and contact merchant support if instructed.

CenuFiltrs supports eight registered feed structures across XML, JSON, CSV, and text: salidzini, kurpirkt, google_shopping, yandex_yml, shopify_json, csv_woocommerce, generic_xml, and generic_json. Use a stable HTTPS URL, UTF-8 encoding, and a feed that can be accessed without signing in, cookies, or bot checks. Existing Google Shopping, Meta XML, or YML exports often work without being rebuilt.

Each usable record needs a title and parseable price, and a product link should be treated as required for an outbound offer. Category, image, brand, ean/gtin, mpn, description, availability, condition, and the adult declaration can improve matching and presentation where supported. Do not translate field names. Before connecting the feed, validate the exact URL with the XML validator, JSON validator, or text/CSV validator. See feed formats and product fields.

Add the feed while creating a shop or from the shop card in My Shops. Enter a stable HTTPS URL, choose the format or use automatic detection, and specify a category delimiter only if the source actually contains multiple categories separated by that character.

Validation starts after you save. The feed cannot be activated until validation succeeds. Changing the URL or starting validation again pauses processing and switches synchronization off; after a successful check, make sure both the feed and Sync are enabled. Each shop can have only one feed, and there is no manual product-entry alternative. See connecting a feed and feed validation.

Update the source feed often enough to keep prices and availability current. CenuFiltrs downloads it according to a schedule managed by the platform administrator. Changes appear after the next successful scheduled processing run; simply enabling synchronization does not download the feed immediately.

Merchants cannot change the processing schedule or trigger a “download now” action. If the frequency needs to be reviewed, contact merchant support. The current status and time of the latest processing run are shown on the shop card and in Feed health. See feed update diagnostics.

Four separate indicators affect processing and visibility:

1. Shop visibility — visible, hidden manually, or hidden because the shared balance is zero.
2. Feed lifecycle — active, pending, error, paused, or disabled.
3. Validation — pending/validating, valid, or invalid.
4. Synchronization — whether regular feed downloads are allowed.

For a feed to be processed, it must be active, Sync must be on, and the shop must not be manually hidden. A zero balance hides offers but does not stop feed processing. Hiding a shop manually removes its offers immediately, pauses processing, and starts the delay before it can be re-enabled. After that delay, an out-of-schedule refresh may be requested if the feed is stale. A disabled feed requires support. See feed statuses, Sync, and shop visibility.

Your feed categories and the CenuFiltrs categories use separate category trees. In Category Mapping, select a shop, find source categories that are not yet mapped, assign a CenuFiltrs category, or reset an existing mapping. Saving a mapping queues the affected offers for recalculation, so the result may not appear immediately. Automatic categorisation can fill some gaps, but complete category paths and clear product titles give it better information to work with.

Category mapping determines category placement and filters. During Beta, it does not change the CPC rate because one common rate applies across all product categories. After Beta, CPC pricing will be reviewed and rates are expected to differ by product category, so accurate mapping remains important. Mapping does not guarantee a higher ranking, and category alone does not make an offer match a text search; search uses the offer title and brand. See why categories matter and how to map them.

CenuFiltrs requires three fields on every usable record: name (product title; accepted aliases: title, nosaukums, product_name, model_name, g:title), price (parseable price; aliases: cena, offer_price, product_price, g:price), and link (product URL; aliases: url, saite, product_url, href, offer_url, g:link). A record missing any of these three fields is skipped during processing. The validator classifies currency and category_full as optional, not required, even though both improve matching and presentation.

Beyond the required fields, a feed can include: currency, category_full (full category path; aliases category, category_path, cat_path, kategorija, categories, product_type, g:google_product_category), image/images, brand, ean/gtin, mpn, description, color, in_stock (availability/quantity), sale_price, and condition.

Delivery fields (prices in EUR): delivery_latvija, delivery_cost_riga, delivery_omniva, delivery_dpd_paku_bode, delivery_pasta_stacija, delivery_latvijas_pasts, delivery_venipak, delivery_circlek, delivery_statoil, delivery_pakomats, delivery_office, plus delivery-days fields delivery_days_riga, delivery_days_latvija, and delivery_days_shop (an integer from 0 to 60). For price, a value of 0 or an empty field means "not specified," not free delivery. For days, 0 is a valid value meaning same-day delivery; an empty days field means "not specified." Delivery fields are read only from XML and JSON feeds — CSV feeds ignore them.

Before connecting a feed, validate the exact URL you plan to use: the XML validator for XML feeds, the JSON validator for JSON feeds, or the text/CSV validator for CSV or text feeds. The validator reports the number of records checked and valid, missing required fields, duplicate IDs, and price and URL issues; it also shows a static reference list of supported fields with their aliases.

During Beta, CenuFiltrs is completely free for merchants, but its commercial accounting logic is already active. A valid outbound click from an active offer to the retailer's website is accounted for and deducted from the balance assigned by the CenuFiltrs team. One common CPC rate currently applies across all product categories; this is a Beta-specific simplification, not permanent post-Beta pricing. There is no individual shop rate. One merchant balance is shared by all of the account's shops and advertising.

Duplicate or suspicious clicks, and clicks on inactive offers, do not reduce the balance. Merchants do not fund the balance or pay real money during Beta: self-service top-up is intentionally disabled, and the CenuFiltrs team assigns and replenishes funds. Billing shows the current balance, balance changes, CPC usage for the current month, and a category breakdown for 7, 30, or 90 days. Use Billing as the authoritative record; Analytics may be delayed. After Beta, CPC pricing will be reviewed and rates are expected to differ by product category. CenuFiltrs will communicate paid-service terms before they apply.

During Beta, merchants use the platform free of charge. After approval, the CenuFiltrs team assigns an initial balance used to cover CPC, advertising, and offer-visibility services. Merchants do not make payments, and self-service balance top-up is intentionally disabled. Contact merchant support if additional balance is needed.

Funds assigned by the CenuFiltrs team appear in the transaction or funding list as a successful balance top-up even though the merchant did not make the payment. This lets merchants see how balance usage would work in paid service while giving CenuFiltrs real operating conditions for refining billing logic, analytics, and the overall experience. Rows marked Preview in a development environment are test data, not payments. Future payment and top-up methods have not yet been announced.

Beta is not a limited or artificial version of CenuFiltrs. Merchants use the full platform without cost, while valid clicks and advertising are accounted for and deducted from the shared merchant balance using the same commercial logic intended for paid service. The CenuFiltrs team funds and replenishes that balance; merchants do not pay or top it up themselves.

One common CPC rate applies across all product categories during Beta. This temporary simplification lets merchants understand CPC consumption and advertising spend without financial commitment and helps CenuFiltrs refine the service under real usage conditions. After Beta, rates will be reviewed and are expected to differ by product category. There is no guaranteed Beta duration, end date, click allowance, starting balance, future rate, or payment date. If the balance reaches zero, offers may be hidden until the team adds funds; contact merchant support.

When the balance reaches zero, all shops on the account are hidden from public search and advertising stops. The visibility switches remain on and feed processing continues, so catalogue data can still stay up to date. This is part of the active commercial accounting logic, even though merchants pay nothing during Beta. If the team-funded balance has not yet been assigned after approval, or has been fully used, offers may remain hidden until the team adds funds.

Once the CenuFiltrs team replenishes the balance and it becomes positive, shops that were hidden only because of the balance return automatically. Self-service top-up is intentionally disabled during Beta; request additional funds through merchant support. Shops that were hidden manually remain hidden and must be re-enabled separately after the lock period. Do not change visibility settings solely to fix a zero-balance state.

The low-balance threshold is set for the account's team-funded Beta balance; it is not the same fixed amount for every merchant. The low-balance preference controls the related email and portal-bell warning. The zero-balance bell notification cannot be disabled because it reports that offers have already been hidden. These notifications show actual balance consumption under the platform's accounting rules; they do not request payment. Contact support if additional balance is needed.

Email preferences and the portal bell are separate notification channels. The bell shows recent balance, feed, activity, and support events, refreshes periodically, and lets you mark the currently loaded items as read. Manage the available preferences in Settings.

Approved, active merchants can manage their own web click-tracking keys in API Keys. The full value of a new key is shown only once, so store it securely. After that, only the key prefix is visible. Keys can be deactivated or deleted, and configurable limits are available for the web channel.

Privileged service channels are not merchant-facing controls. Never place a secret in public source code, logs, screenshots, or support messages.

The dashboard provides a fixed 30-day overview with six KPIs, trends, categories, top offers, and a shop filter for the entire page. Analytics adds shared 7/30/90-day and shop filters across the Overview, Products, Price intelligence, Competitors, Demand, Feed health, Billing, and Future insights tabs.

Demand hides groups below the privacy threshold. Feed health shows processing and data-quality information; manual Sync is not available because processing is controlled by the administrator. The Billing tab inside Analytics is an estimate and does not replace the main Billing record. See the Analytics guide.

Revenue, conversion, add-to-cart, bounce, and post-CPC results require attribution data from the merchant side. Without that data, Analytics shows that setup is required, the metric is unavailable, or there is not enough data; it does not invent values. Price alerts, time-at-best-price information, and predictive demand are currently unavailable.

Repricing information is advisory only. CenuFiltrs never changes a retailer's prices automatically. Evaluate any recommendation against your own costs and commercial rules. No future repricing integration is guaranteed. See the Analytics guide.

In Analytics, choose CSV or JSON and export the data from the active tab. The file reflects the selected dataset, 7/30/90-day period, and shop filter. Each tab exports its own set of data.

This business-data export is separate from the personal-data export in Settings. If the selected view is empty or some data is hidden for privacy reasons, the exported file may also be empty or limited; sample figures are not inserted.

Advertising is currently enabled. A promoted-offer campaign selects eligible active offers and sets the CPM bid, daily budget, total budget, and campaign dates. The campaign is created as active, so eligible impressions can begin at the scheduled start without another launch step. Whether a campaign can be paused, resumed, edited, or deleted depends on its current status. If the total budget is exhausted, increase the budget rather than simply trying to resume the campaign.

During Beta, valid advertising spend is accounted for and deducted from the same team-funded balance as CPC. Merchants pay nothing, and self-service top-up is disabled; the CenuFiltrs team replenishes the balance when needed. Advertising does not bypass the rules for shop visibility, feeds, offer status, balance, or 18+ inventory. Placements are labelled. A higher bid can improve position in placements ranked by bid, but it does not guarantee an impression; the homepage_featured placement shuffles eligible offers and ignores the bid.

Create a banner in Advertising, choose the placement, and upload a JPEG, PNG, or WebP file. The uploaded image must exactly match the required placement dimensions; both browser and server checks validate the format, dimensions, and file size. Add alternative text, a headline, button text, an HTTPS destination, CPM, budgets, and the schedule.

A new banner starts as a draft and is not displayed. Submit it for human moderation. While it is pending, editing is locked; approval activates the banner, while rejection shows a note and allows you to correct and resubmit it. When the banner is active, paused, pending, or completed, the creative fields are locked and only the allowed budget or schedule changes remain available. No review time or outcome is guaranteed. See the advertising guide.

In Settings, you can manage the company name, legal and contact details, website, tax ID, description, logo, and account password. CenuFiltrs uses the company information to manage the merchant relationship. The public shop name, shop contacts, delivery information, and payment information belong to each individual shop and are edited in My Shops.

Required fields and email format are validated. Reset restores the last successfully loaded values; it does not delete data stored on the server.

Settings includes email preferences for low-balance alerts, a daily digest, a weekly summary, and feed errors. Each preference controls only the corresponding documented email or portal notification. Turning an email preference off does not remove events from the portal, and the operational zero-balance notification in the bell remains enabled.

The portal bell shows recent activity, balance, feed, and support events. It can refresh the list, show unread counts, and mark the currently loaded items as read. No SMS, push, or guaranteed immediate delivery channel is promised.

Activity combines a seven-day traffic overview with the ten most recent audit events relating to account and feed changes. The traffic and activity sections load separately, so either can independently be empty or show an error.

This is a limited record of recent activity, not full analytics, financial history, or a complete audit archive. Use Analytics for performance and Billing for financial information.

The Export Data action in Settings downloads personal user data such as profile details, preferences, wishlist items, searches, tasks, recent outbound offers, support requests, and reviews. It does not include the merchant product catalogue, shop analytics, advertising, or billing history.

Export business analytics separately from the relevant Analytics tab. The two exports serve different purposes and are not expected to contain the same data.

Merchant account closure is handled through support because the CenuFiltrs team needs to deal with the shops, feeds, balance, advertising, and any business records that must be retained. Deleting the ordinary shopper profile does not close the merchant record or delete the merchant's business data.

Open merchant support and specify the company, the relevant shops, and the outcome you want. If you only need a temporary stop, reversible alternatives include hiding shops manually, switching Sync off for eligible feeds, or pausing advertising.

Yes. Merchant approval adds access to the merchant portal without removing the shopper profile. The account menu sends approved merchants to Merchant Portal; signed-in users who are not yet approved follow the merchant-application flow. Shopper profile pages remain available.

The merchant menu contains Dashboard, My Shops, Analytics, Activity, Category Mapping, Billing, Ads, API Keys, Settings, Support, and Help. Logging out ends the shared session. Guests must sign in first, while signed-in users without merchant approval return to the application flow. See the first-actions guide.

In merchant support, choose a topic and send a message between 10 and 5000 characters. Include the shop, feed address, time of the issue, exact error, a specific example, and the checks you have already performed. New requests appear in a paginated list and keep their message thread.

You can reply to an open request. Replying to a resolved request reopens it. A closed request cannot receive new replies, so create a new one if necessary. No response time is guaranteed. For partnership questions before approval, use public contacts. See contacting support.

If an offer is hidden because of a moderation decision, the merchant receives the reasons by email. The message identifies the decision, the relevant facts and legal basis, whether automation was used, and the available appeal route. The current merchant portal does not provide a separate view of the restriction or the appeal.

A moderation restriction is different from a zero balance, a shop hidden manually, an inactive feed, or outdated feed data. Check the reason in the email before changing feed or visibility settings. Use merchant support for further help, and do not send confidential evidence through a public contact channel.

The current merchant portal does not have a screen for submitting or tracking an appeal. Follow the appeal route provided with the moderation decision or contact merchant support. The underlying process allows one reasoned appeal for each restriction within the stated six-month period, and the appeal is reviewed by a person.

If the appeal is accepted, a new reinstatement decision can return the offer to a publishable moderation status. This does not guarantee immediate visibility: the account still needs a positive balance, the shop must be visible, the offer must be active, and the feed data must be current. No review time, acceptance, reinstatement, or particular notification channel is guaranteed.

Check the following in order:

1. Balance — a zero balance hides every shop; ask support for team-assigned funds.
2. Shop visibility — remove manual hiding after the re-enable lock period.
3. Sync — an active feed can still have synchronization paused.
4. Feed lifecycle — resolve pending, error, paused, or disabled states.
5. Validation — correct invalid records, validate again, and then check Sync.
6. Source feed — confirm the product, title, price, and link are still present.

If the offer exists but a search query does not find it, improve the title and brand. Category alone is not enough to match a text query. See the full search-visibility diagnosis.

An “Active” status alone is not enough. For the feed to be processed, the feed must be active, Sync must be on, and the shop must not be manually hidden. Check the time of the most recent processing run. If it ran recently, confirm that the source URL now contains the new values rather than old cached data or an HTML access page.

Processing follows a schedule controlled by the administrator, and merchants cannot start it manually. If all conditions are met and the source is current, send support the shop, feed URL, one example product, the value in the source, the value shown by CenuFiltrs, and the latest processing time. See feed update diagnostics.

A feed can be enabled only after it passes validation successfully. Pending or validating means the check is still in progress. If the result is invalid, open or download the report, correct every error, and validate again. Common causes include an unreachable URL, an HTML sign-in or bot-check page instead of the feed, or records without both a title and parseable price.

After validation succeeds, enable the feed and separately check that Sync is on. A manually hidden shop blocks Sync, and a Disabled feed can be restored only by the CenuFiltrs team. See feed enablement diagnosis.

Start with Billing, not the estimate in Analytics. During Beta, “spend” records actual consumption of the team-funded balance under the platform's commercial accounting rules, not a payment by the merchant. Compare the same time periods and shop scope. One common CPC rate currently applies across all product categories, advertising uses the same balance, the monthly CPC figure covers the calendar month, and advertising cards cover the last seven days. After Beta, CPC rates will be reviewed and are expected to differ by product category.

Count valid clicks rather than every interaction. Duplicate or suspicious clicks, clicks when the balance is zero, and clicks on inactive offers do not reduce the balance. If the Billing records still appear incorrect, send support the relevant period, shop, offers, and balance entries.

Check the selected shop and the 7/30/90-day period, then confirm that the offers are visible and receiving impressions. An analytics processing warning means the analytics data may be delayed; it does not mean Billing is delayed. Demand may hide small groups for privacy reasons, and Future insights may remain empty until merchant-side attribution data is available.

Dashboard, Analytics, and Billing use different time windows and data sources. Use Billing for accurate financial information and Analytics for behaviour and performance. If data is genuinely unavailable, incomplete, or in an error state, CenuFiltrs does not replace it with estimated or invented figures. See why figures differ.