Elbuz checks the products of each enabled export template against marketplace requirements and lists errors in one table before sending — along with marketplace rejections.
When you need this:
- First export to Google or Rozetka — see what the marketplace will reject before sending.
- SKUs in the barcode field — the report names each invalid code and why: length, check digit, in-store number.
- Title over the marketplace limit — the row shows the title length and the limit.
- A marketplace rejected products — the rejection text is in the same table, next to the card button.
Where to start: export template card → “Related settings” → “Feed quality”.
What the Feed quality report can do
- Opens on a template — from the card, a row or the template list menu, straight to the errors of that feed.
- Tiles by issue type — how many products have no description, no photo or an invalid barcode; a click leaves only those in the table.
- Marketplace requirements — Google, Facebook, TikTok, OpenAI, Rozetka and API marketplaces are each checked by their own rules.
- Barcode check — length, digits, check digit, in-store numbers and coupons.
- Marketplace and Google rejections — products a marketplace or Google Merchant Center rejected or held back, with the status text.
How to open the report on the right template
The shortest way is from the export template card: the “Feed quality” button is first in the “Related settings” block. The window opens on this template right away. If “Feed quality” is already open, it switches to this template by itself.
1
Feed quality- Opens the report right on this template.
Two more entry points are in the “Data export” template list:
- the “Feed quality” icon among the row actions when you hover over the row;
- the “Feed quality” item in the ☰ menu above the list — opens the report on the selected template.
A disabled button in the card explains why in its tooltip: “The template is off — Feed quality checks enabled templates only” or “This template type is not checked…”.
The report doesn't check generic XML, price lists (including idealo, billiger.de, PriceRunner and the supplier price summary), your own websites (Horoshop, Shopify, Wix, WooCommerce, Odoo, Dotykačka), 1C, Elbuz CMS and Elbuz Tunnel: they have no marketplace requirements. Elbuz CMS, Elbuz Tunnel, 1C and YouTube cards have no button at all.
How to read the report: tiles, issues, details
One report row is one product in one template. The “Issues” column shows all of that product's problems for this marketplace as chips, and “Details” explains them: which barcode and why it doesn't fit, how long the title is and what the limit is.
1
Template or channel2
Error type3
Error tile4
Issues column5
Open product- The export templates the report checks; Rozetka is selected.
- Narrows the table to one error — the same as clicking a tile.
- How many rows have this error; click to show only them.
- All the product’s issues in this template, as chips.
- Opens the product card to fix the data.
There are two lists above the table. The first is the template or marketplace: it contains only enabled templates that the report checks. The last item, “All templates and marketplaces (slower)”, combines all templates: on a large catalog it takes many times longer than one template. The second list is the issue type (“All issues” at first); it does the same as clicking a tile.
Tiles count the selected template: “Rows with issues”, “Products” and one tile per issue type. Clicking a tile leaves only that issue in the table; clicking it again clears the filter. The pencil button at the start of the row opens the product card — that's where you fix the issue.
The report checks product data in the catalog, not the finished file. So it ignores the template's feed rules, formulas and translations: a product a rule excludes from the feed stays in the report, and a title a rule truncates is still flagged “Title too long”. The template's product set is the same filtered set as in the “What will be exported” dialog before a run.
What is checked for each marketplace
The set of checks depends on the template type: what's required for Google is unnecessary for Prom.
| Template | What is checked | Title limit |
|---|---|---|
| Google Merchant, as well as Kelkoo, Pinterest and Microsoft Merchant Center | title, description, photo, price, brand, invalid barcode, stock status, “No GTIN or MPN”, link (SEO URL) | 150 characters |
| the same, except “No GTIN or MPN” | 200 characters | |
| TikTok (XML feed) | the same, except “No GTIN or MPN” | not checked |
| OpenAI (ChatGPT) | title, description, photo, price, brand, invalid barcode | 150 characters |
| Rozetka (XML) | title, description, photo, price, brand, invalid barcode | not checked |
| Other XML marketplaces (Prom, Epicentr, Hotline and others) and prom.ua (XLS) | title, photo, price, invalid barcode | not checked |
| API marketplaces, including TikTok Shop | title, photo, price, invalid barcode; for Bol.com, Cdiscount, Walmart, OTTO, Kaufland, Mirakl, Zalando, Amazon and ManoMano also “No barcode” | Allegro 75, eBay 80, Etsy 140, Amazon 200 |
What the issues mean:
- “No barcode” — all three fields are empty: EAN, GTIN and UPC. Checked where the marketplace creates a listing by barcode.
- “No GTIN or MPN” — MPN is empty too: Google can't identify such a product.
- “No link (SEO URL)” — the product's page address is empty. Checked only when the Google template takes the link from the product's SEO URL.
- “No stock status” — the product has no stock status selected.
For feeds in the Google format (Google, Facebook, TikTok and others), the report takes the title and description from the field set in the template as a simple macro, for example a custom field with a title for Google. If there's a formula or several fields, the main title and full product description are checked.
Why a barcode is invalid and how to fix it
Marketplaces check barcodes against the GS1 registry. Google and marketplaces reject a code that fails the check along with the product, so Elbuz checks each of the EAN, GTIN and UPC fields and writes the reason in “Details”:
| Reason in “Details” | What it means |
|---|---|
| not digits only | the field holds an SKU or MPN with letters or hyphens; a code of all zeros is flagged the same way |
| length is not 8, 12, 13 or 14 | a barcode has 8, 12, 13 or 14 digits; 7 or 10 digits is an internal code |
| wrong check digit | the last digit doesn't match the calculated one — the code was mistyped or made up |
| in-store or coupon number — marketplaces do not accept it | a code from the ranges for internal use and coupons: a 13-digit code starts with 020–029, 040–059, 200–299, 980–984 or 990–999, an 8-digit one with 0 or 2; a 12-digit UPC is checked like a 13-digit code with a leading zero |
Book and periodical codes 977–979 aren't treated as errors. An empty field doesn't trigger “Invalid barcode” — there's a separate “No barcode” issue for that.
1
Details- Which code and why it does not fit: check digit, length, an in-store number.
There are two ways to fix it. If the supplier or the packaging has the real barcode, enter it in the product card. If there's none at all, remove the invalid code from the field: for Google, a product without a barcode but with an MPN and brand is more acceptable than one with someone else's code. If such products shouldn't be sent at all, exclude them from the feed with the rule “invalid GTIN → Exclude” (feed rules).
Marketplace rejections
When a marketplace connected via API rejects or hides a product or keeps it in moderation, Elbuz saves this status. In the report, such a product has a separate row with the “Marketplace rejection” issue: the status text is in “Details” and the date in the “Marketplace status date” column. This way you see the template's own errors and the marketplace's response side by side.
If rejections came from a marketplace whose template the report doesn't check, it appears in the template list as a separate “Marketplace rejections” group. Marketplace statuses are refreshed by the API exchange with them, not by the report window.
Products disapproved by Google Merchant Center
Google rejections reach the report once you connect Merchant Center: the “Google Merchant Center” button above the table, the Elbuz e-mail among your Merchant Center users and the account number. After “Save and refresh statuses”, products Google disapproved or demoted appear under “Google Merchant Center” in the “Marketplace rejections” group — with Google's reasons. More: how to connect Google Merchant Center.
Next to the “Google Merchant Center” button is “Open Google Ads” — for those with access to the “Google Ads” window. It shows spend, ROAS and profit after ad spend for each product: Google Ads in Elbuz.
Scenarios
Preparing your first Google feed
Open the Google template card → “Feed quality” → the “Invalid barcode” tile.
- “Details” shows which products have an SKU in the barcode field: fix them in the card or exclude them with a feed rule.
- The “Title too long” tile shows titles longer than 150 characters — shorten them or truncate them with the “Cut to N characters” rule.
Rozetka doesn't accept some products
Select the Rozetka template in the list and look at the “No description”, “No brand” and “Invalid barcode” tiles.
- Clicking a tile leaves only these products in the table; the pencil in the row opens the card.
- After editing, click ☰ → “Refresh list”: the fixed product disappears from the report.
An API marketplace rejected products
Select the marketplace template or the marketplace in the “Marketplace rejections” group, and the “Marketplace rejection” tile.
- The marketplace's rejection text is in “Details”, with the status date next to it.
- Fix the card and send the product again with a regular export.
What to do when the report shows the wrong thing
| What you see | Why | What to do |
|---|---|---|
| The template isn't in the report list | the template is disabled or the report doesn't check its type | enable the template; the tooltip of the “Feed quality” button in the card gives the reason |
| “(template filter not applied)” next to the template | a complex template filter can't be turned into the report's filtered set | the report shows all products of the exported categories; ignore errors of products outside the filter |
| A product is in the report although a feed rule excludes or fixes it | the report checks catalog data and doesn't apply feed rules | check the rule's result with “Preview” in the “Feed rules” window |
| “No description” on almost all Google products, although the feed has a description | the template builds the description with a formula from several fields, so the report checks the full product description | put a single field macro in g:description or fill in the full description |
| The table takes long to load | “All templates and marketplaces (slower)” is selected | select one template |
FAQ
I fixed a product, but it's still in the report. Why?
The table doesn't refresh by itself. Click ☰ → “Refresh list” or select the template in the list again — the report is recalculated from current data.
Does the report take into account a test run of the template with the “Check” button?
No. The report checks product data in the catalog, not the file. The flask “Check” in the template card shows the finished XML with rules applied.
Why doesn't the report check my price list or my Horoshop website?
They have no marketplace requirements: you decide what counts as an error. The report checks only feeds for Google, Facebook, TikTok, OpenAI and marketplaces (list).
Can I get feed errors through the API?
Yes, API v2 has the feed_issues resource — read-only, with the same access as the “Feed quality” window.
How is the report different from the “AI readiness” tab?
“Feed errors” shows what a specific marketplace will reject. “AI readiness” gives the catalog a 0–100 score and shows what a card lacks for ChatGPT and other AI agents (catalog AI readiness).
Where to find it and who has access
- Menu
- Directories → Operations → Feed quality
- Other entry points
- template card → “Related settings” → “Feed quality”; the row icon and the ☰ menu of the template list
- Access right
- the “Feed quality” window; without it, the export has no such buttons
- Have ready
- an enabled export template for the marketplace
Related topics
- If you need the big picture of exports — How to set up product exports.
- If products with errors need to be removed from the feed or fixed only in it — Feed rules.
- If you need to know how many products will go into the file before a run — How to check an export before running it.
- If products will be sold through ChatGPT and AI agents — How to check whether your catalog is ready for AI.
- If you need to see Google Merchant Center rejections — How to connect Google Merchant Center.
- If a product didn't get into the file at all — How to set the product filter.
