Your promotion is ready. Are its prices, stock signals and product variants telling the same story? We help your team find the differences, prepare fixes and verify what changed.
This invented example shows the kind of discrepancy we investigate. It is a demonstration, not a live scan or a client result.
The feed and matched structured offer disagree. Confirm the visible price, selected variant and intended sale timing before changing the source.
One market, a current catalog export, your promotion timing and permission to check the agreed pages. No shopper data or passwords.
We review feed format, planned sale dates and changed products. Current page checks use current prices; future prices are verified after activation.
Your team gets a ranked report and proposed fixes. You authorize changes. We recheck the fresh export and document what resolved.
€99 once
One store and market. A focused report within three business days after complete inputs.
€249 / month
A focused monitoring and repair allowance for one store and market.
Join within 14 days and the €99 pilot is credited toward your first month. Only €150 additionally payable.
Prices exclude applicable VAT. Business customers only. Cancel before the next renewal.Automated checks compare feed data and machine readable product offers. They do not certify visible checkout prices, delivery rules, images, account policy compliance or Google approval.
Ambiguous variants and JavaScript pages need human review. Support runs Monday to Friday in Portugal business hours, with an initial response within two business days. Monitoring is scheduled, with coverage shown in every report.
Already well served by your feed app? Keep it. This service is for teams that need help diagnosing and verifying a specific issue.
Submit your store details, track approval, pay securely and read the report in your browser. The checks run on the server; your browser can be closed.
Open your workspace →Try the full fictional customer journey →Manage payment methods and cancel renewal through Stripe’s customer portal. The dashboard shows the effective end date.
This private preview cannot take live payments until the business and payment account setup is complete.
The registry includes parsers for Amazon, Shopify, Mirakl/PcComponentes, osCommerce, Magento and PrestaShop. Supported formats and limits differ. We detect the platform and require a readable exact sample before approval or payment. Amazon challenges, custom themes and unresolved variants can prevent a check. See supported platform parsers and limits.
Before we accept your request, you provide one product ID and exact page link from the same CSV row. We detect the store and run its parser to identify an offer with a usable price, expected currency and stock signal. Marketplaces also require the expected seller. If it fails, the form explains the problem and how to correct it before resubmitting. A successful sample is not a full catalog check; visible checkout prices and country selectors are not tested.
A variant is one sellable product version, commonly with its own SKU. A T-shirt in 3 sizes and 2 colours counts as 6 variants when all combinations are sold. A product without options counts as 1. Count one feed row per version, not the quantity in stock. The starting scope supports up to 1,000 rows.
The customer portal currently requires a direct CSV product feed URL in the supported format. We read its product links and compare submitted values with the matched product pages. A homepage only identifies the store; it does not trigger catalog discovery or a store crawl. Download a fictional CSV format example and replace the example rows with your own export.
No. We work with the source data and tools you already own. Agencies can request a report under their brand with their merchant's permission.
Those results cannot be promised. The service investigates agreed technical discrepancies and verifies changes. Google makes its own eligibility decisions.
Begin with a supported CSV feed URL, its intended storefront and currency, promotion timing and permission to inspect agreed public pages. Any account access or store changes need a separate authorized scope.
The starting scope is up to 1,000 sellable versions in one CSV feed, one store and one expected currency. Complex bundles, checkout testing, additional feeds or regional versions and extra development need a separate scope or referral.