Compari.ro feed for Shopify

Compari pulls one file from a URL you host: XML or CSV, downloaded every day after 17:00, with changes visible the next day once your PPC balance is positive. There is no API and no upload: the URL is the whole integration.

New products take 5–8 working days: a content team places the category by hand and only then does the offer merge with identical ones. Until then it appears at the bottom of search, without an image. Feedflock regenerates the file on your schedule, as often as every hour, on a URL that does not change, and the group confirms that changing only the URL costs nothing.

The Árukereső group is one of the few comparison sites that wants two prices in every product: price, the gross consumer price including Romanian VAT and any other tax the consumer pays, and net_price, the price without VAT. Compari's own page lists net_price as recommended, the group's current page as mandatory. The template requires it, because a feed missing a mandatory field is rejected whole, not partially.

The template maps the gross price from the variant price and derives the net price from the feed's tax settings: 21 % for Romania by default, your own Shopify tax rate when it differs, with overrides for reduced-rate collections. No currency symbol anywhere; the optional currency element carries RON.

Delivery_Time is the working days from order to the customer's door, as a single maximum, never a range. Valid formats are a bare number, the number with "zile" or "zile lucratoare", and NO. The display buckets are fixed: 1 shows as In stoc, 3 as "max 3 zile", 7 as one week, 14 as two. And unlike every Heureka-family feed, in stock here is 1, not 0. The template derives it from Shopify availability so the habit cannot slip through.

Delivery_Cost is one nationwide home-delivery price including VAT, the same regardless of weight or order value, or the word FREE, gratuit, gratis or fara cost. The group's format table names 0, ranges and "from" prices invalid, and parcel-locker or pickup-point prices may not go in the field at all. Leave it empty and the client centre's delivery fee table applies instead, which is why the template's default is empty.

Pairing is human-in-the-loop: the group's content team places every category by hand, and offers merge onto a product card by category, manufacturer, name, productid and EAN. The group's modification page is blunt about stability (every change counts as a modification, even a single character), and a changed pairing value drops the offer from the merged page until it is processed again.

The identifier is stricter still: never change it, never reuse it for a different product. The template keeps it on the variant SKU with the variant ID as fallback, both stable. And the category in the feed is your shop's own path, levels separated by ">". Compari publishes no tree to download, so a descriptive, unmistakable path is the fastest thing you can hand their content team.