> ## Knowledge Base Index > Fetch the complete knowledge base index at: https://help.pandectes.io/sitemap.xml > Use this file to discover available pages before exploring further. > Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash). # XML feed v1 vs v2: what changed ### Overview Skroutz Connect generates your product feed in two possible structures, version 1 (v1) and version 2 (v2). v1 only understood color and size. Products with other options, such as material or package, were exported with a single variant, so the rest of the catalog never reached Skroutz. v2 exports every option combination as its own entry, with its own price, stock, and weight. This article explains the differences and shows what the same product looks like in each version. ### Feature comparison | Feature | v1 | v2 | | --- | --- | --- | | Supported option types | Color and size only | All option types: color, size, material, package, and more | | Size handling | Sizes shown in a `` array | Same structure, a `` array under each product or color variation | | Color and size products | Supported, limited to color and size combinations | Fully supported, same logic with more consistent output | | Products with other options (material, package) | Only the first variant was exported | Every option combination is exported as its own variant | | Single variant products | One `` entry | Same behavior, still one clean `` entry | | Variant naming | Static titles such as `Default` or `Variant 1` | Product name plus option values, for example `Bottle Metal 20gr Large` | | Grouping behavior | Used only for sizes (`` array) | Still only for sizes, all other options become separate variants | | Data accuracy | Price, stock, and weight were sometimes shared across variants | Each variant carries its own price, stock, and weight | | Schema alignment | Partially compatible with Skroutz requirements | Aligned with the current Skroutz XML schema and validation rules | | Feed consistency | Complex products could appear incomplete | Consistent structure for every product configuration | | Migration | Legacy structure with fixed grouping | Generated automatically from your product data, one way and not reversible | || Migration to v2 is one way. Once your feed is generated in v2, it cannot be switched back to the v1 structure. ### Example 1: variant titles now include the color In v1 both color variants carried the same name, so Skroutz could not tell them apart. In v2 the color is part of the title and the `` field stays in place. v1 ```xml In Stock 10 109.99 650 In Stock 10 120 650 ``` v2 ```xml In Stock 10 109.99 650 In Stock 10 120 650 ``` ### Example 2: all option combinations are exported This product has four variants built from two options, material and length. v1 exported only the first one. v2 exports all four, each with its own variant link, SKU, and barcode. v1 ```xml Available from 4 to 6 days 10 150 ``` v2 ```xml Available from 4 to 6 days 10 150 Available from 4 to 6 days 10 150 Available from 4 to 6 days 10 150 Available from 4 to 6 days 10 150 ``` ### What to check after moving to v2 * Your product count in the feed grows, because variants that were missing are now exported. * Variant titles change, so Skroutz may need to re-match some products. * Prices, stock, and weights now follow each variant. Confirm your variant level data in Shopify is correct. ### Related articles * [How to set product availability with metafields](/en/article/skroutz-connect-set-product-availability-with-metafields-1scjkbs/) * [Skroutz Order Integration: A Complete Setup Guide](/en/article/skroutz-order-integration-a-complete-setup-guide-1v24co9/)