Cenueksperts.lv feed for Shopify

Most comparison sites hand you a specification. Cenueksperts hands you a file: its entire merchant documentation on formats is one FAQ question, answered by a link to productfileexample.xml on the guenstiger.de CDN: the German sibling's own XML-Vorlage. That sample is the whole vocabulary: a DataFeeds root, one item_data element per offer and thirteen item_* children, from item_unique_id to item_shipping_charge, with no namespace.

Feedflock's template carries the sample's names in the sample's order and nothing else. The sample wraps no value in CDATA (it entity-escapes an ampersand inside a category path), so the export entity-escapes too. And because both the German and the Latvian template watch the same file, a change to the sample moves both.

Because Cenueksperts publishes no requirement levels, the template's required set is an openly named inference: the product name, the gross price and the product URL are the only columns the group's two published field tables (guenstiger.de's German PDF and ÁrGép's Hungarian translation of it) both mark as unconditionally required. item_unique_id is required on top, ours this time, on the same reasoning as guenstiger's Bestellnummer: a per-variant export needs a stable row id, and the German instructions warn that without one the import “can run into problems”.

Just as deliberately, the German PDF's per-field limits were not copied into the Latvian template: an id of 50 characters, URLs of 2000, a name of 500 are the German site's numbers, and nothing says they hold in Latvia. That is also why the template carries no specVerified flag: the readiness check lists missing data, it does not block your feed on limits nobody published.

Latvia is euro, so unlike ÁrGép there is no currency conversion between the group's sites: item_price is your Shopify price as is, gross, with a dot decimal and no currency symbol, exactly the sample's “999.99”. The direction is not a guess: the Latvian terms state that all published prices include the statutory value-added tax, and there is no net-price or VAT-rate element in this format.

The same terms answer two more fields. The site publishes prices of new goods only (explicitly no used, display, fair, B-grade or similar items), so item_condition defaults to the sample's “New”, with “Refurbished” existing in the sample for completeness. And item_inventory shows exactly one token across the whole sample: AVAILABLE. No second value is documented anywhere, so the template sends AVAILABLE for a sellable variant and omits the element for a sold-out one rather than inventing an OUT_OF_STOCK of its own.

Shipping in this format is one number per offer: item_shipping_charge, written as a bare amount like the sample's “5”, with no carrier element, no country, no cash-on-delivery price and no free-above threshold. Shopify has no per-product shipping price, so the template ships the element empty. A “0” would not mean “unknown”: across this group it declares free shipping on every offer, a claim you should only make deliberately. A merchant with one flat rate types it; a Liquid rule on the variant price can still express “free from 50 €” per offer.

The commercial side is stated more plainly than anywhere else in the group. The application form's last field takes your product-list URL, a human follow-up is promised before processing starts, and billing is post-paid per result, with clicks from outside the Baltics and duplicates filtered out and a monthly cap on the invoice. Once listed, your data is refreshed at least once an hour; Feedflock regenerates the file every hour on the same URL, so the two loops line up.