IVO
Back to help center
Merchant Integration

Product feed format

Supported JSON, XML and CSV feed formats, field mapping, images, defaults and variants.

Supported feed URLs

IVO can read product feeds from a public URL in JSON, XML, Google Shopping RSS/XML or CSV format. The URL must return the feed content directly and must be reachable by the IVO.md crawler.

JSON structure

The feed can be an array of products or an object that contains a product list, for example {"products": [...]}, {"product": [...]}, {"offers": [...]} or another nested product array. IVO searches for the largest product list when the structure is nested.

{
  "products": [
    {
      "name": "Laptop 14",
      "price": "12999 MDL",
      "description": "Compact laptop",
      "images": ["https://example.com/1.jpg", "https://example.com/2.jpg"]
    }
  ]
}

XML structure

IVO supports common XML feeds, including Google Shopping RSS items and simple product catalogs.

<products>
  <product>
    <name>Laptop 14</name>
    <price>12999</price>
    <currency>MDL</currency>
    <image>https://example.com/1.jpg</image>
  </product>
</products>

CSV structure

CSV feeds must use the first row as headers. Comma, semicolon, tab and pipe delimiters are detected automatically.

name,price,currency,image,availability
Laptop 14,12999,MDL,https://example.com/1.jpg,5

Required fields

The minimum required fields are name and price. Currency can be included in the price, mapped as a separate currency field, or configured as a default value.

Mapping fields

In the integration preview, IVO shows every source key from the feed. Assign each source key to the IVO field it represents. Multiple source keys can be assigned to the same field. For text fields such as name or description, values are concatenated. For image, all valid image URLs are collected.

Images

Use one target field: image. You can map keys like image, images, image_1, image_2, image_link or gallery to it. Arrays of image URLs are supported.

Defaults

If the feed does not contain a value such as currency, brand, category, availability, image or description, you can set a fixed default value in the integration setup.

Variants

For variant details, map only explicit dimensions such as color, size, memory or display to variant_option. Multiple source keys may map to variant_option.

{
  "name": "Laptop 14 Ultra / 32GB / Silver",
  "price": 15999,
  "variant_option": ["memory:32GB", "color:Silver"]
}

If your feed already contains a trusted item_group_id, IVO can read it internally, but it is not inferred automatically because incorrect grouping could merge unrelated products as variants.

Crawler identification

Feed requests use this User-Agent:

IVO.md (+https://ivo.md/help/merchant-integration/ivo-md-crawler)

Was this article helpful?

Share quick feedback so we can improve it.

Related articles

Merchant Integration

Merchant API reference

Full reference for the merchant API: authentication, every endpoint, and what each input and output field means.

Merchant Integration

Extensions: how they work

A generic overview of how IVO marketplace extensions typically install, authorize, sync, and report status.

Merchant Integration

Magento 2 extension: installation

Install the IVO Marketplace Magento 2 extension and connect your store to IVO.

Merchant Integration

OpenCart 4 extension: installation

Install the IVO Marketplace OpenCart extension and connect your store to IVO.