Validate XML Feed

Check feed URLs, uploaded XML files, or pasted XML before moving to integration review.

XML validator

Using Cloudflare or a firewall? Allow access from our IP.

Validate an HTTP(S) feed URL through the current backend validation flow.

XML Example

A compact product feed example using the fields shown in the validator checklist.

<?xml version="1.0" encoding="UTF-8"?>
<products>
  <product>
    <name>Gaming Laptop Pro 16 512GB</name>
    <link>https://store.example.com/laptop001</link>
    <price>1299.99</price>
    <currency>EUR</currency>
    <category_full>Computers > Laptops > Gaming</category_full>
    <image>https://store.example.com/images/laptop001.jpg</image>
    <brand>TechBrand</brand>
    <model>Pro 16</model>
    <ean>4718017889766</ean>
    <mpn>TB-PRO16-512</mpn>
    <description>High-performance gaming laptop</description>
    <color>Black</color>
    <in_stock>8</in_stock>
    <condition>new</condition>
  </product>
</products>

Validation errors

These are the same codes a merchant sees in the feed validation report in the shop panel. The code is machine-readable and never translated — search the report for it literally.

Fetching the feed

  • FETCH_ERROR - The feed could not be downloaded: unreachable address, no answer within 30 seconds, an HTTP error, or bot protection served instead of the file.

Reading the file

  • PARSE_ERROR - The file could not be read: broken markup, a truncated file, the wrong encoding. Commonly an HTML page returned instead of the feed.
  • UNSUPPORTED_FORMAT - The file format is not supported.
  • VALIDATION_ERROR - The validation itself failed — contact support and include the feed URL.

Individual products

  • MISSING_REQUIRED_FIELD - The record has no title, price or link. The product is skipped entirely.
  • INVALID_PRICE - A price is present but unreadable: a placeholder such as %regular_price%, free text, a range, or a value above 1,000,000. The product is skipped.
  • INVALID_URL - The link is not an absolute http(s) address — a relative path or an address without a protocol.
  • ITEM_PARSE_ERROR - One record failed; the rest of the feed was read normally.
  • SKIPPED_PRODUCT - The record was skipped and no more precise reason could be determined.

When no product got through

  • NO_ITEMS - No product elements were found in the file.
  • NOT_A_PRODUCT_FEED - Elements exist but none carries a usable price — this may not be a product feed (a news feed, say), or the price sits under an unrecognised tag.
  • INVALID_PRICES - Every element carries a price but none of them is readable — the problem is the format of the price values.
  • ITEMS_ALL_SKIPPED - Elements were found but every one of them was skipped: no title or no price.

Warnings

  • category - The product has no category. It still imports, but it is harder to find.
  • brand - The product has no brand. It still imports, but it matches the shared product page less reliably.
  • INVALID_CONDITION - The supplied condition is not supported. Import is not blocked, but the value is ignored; use new, used or refurbished (jauns, lietots and atjaunots are also accepted).
  • INVALID_ADULT - The supplied adult flag is not recognized. Import is not blocked, but the product is treated as not declared; use yes/no (or true/false, 1/0).