Lamoda.pl feed for Shopify

Lamoda is a pull channel with unusually good receipts: the Onet Ads FAQ states that the system regularly synchronises products from the feed the shop provides, downloading the XML and the images in it, and then publishes the crawler's fifteen source IP addresses and its User-Agent strings, asking you to allowlist them. Feedflock's hosted URL is exactly what this model expects: one address, regenerated every hour, that you paste into the panel once.

No fetch interval is published, so plan for “regularly” rather than a clock. What you control is freshness: because the file is rebuilt hourly, every pull reads current prices and stock, and Feedflock's fetch tracking shows when RASP last downloaded the file and warns you if it stops.

Lamoda's vocabulary looks like Google Shopping and is not. Google's own RSS writes title, description and link without the g: prefix; Lamoda's sample prefixes all three. Google spells availability “in stock”; Lamoda wants in_stock. A file copied from a Google Merchant template is wrong in both places, and nothing on Lamoda's side will tell you.

The spec also adds one element Google has no field for (g:omnibus_price) and drops others: no g:condition, no g:mpn, no g:item_group_id, no g:shipping. Lamoda says the structure is only an example and that it can read a differently-shaped feed, but the published sample is the one shape known to need no negotiation, and that is what the template emits.

There is no grouping element in Lamoda's vocabulary, so a shirt in five sizes is five separate items, each with its own g:id and a link that opens that variant. Feedflock renders per variant by default and keeps g:id on the variant SKU, stable across refreshes, which is what a pulling crawler matches on.

The catalogue filters by brand, colour and size, so those three attributes decide whether your items survive a filtered search; they map from your Shopify vendor and variant options. Categories are yours: g:product_type takes your own path like “Moda męska > Koszule”, because Lamoda publishes no tree. One honest caveat: g:gender and g:age_group have no published vocabulary: the sample's female and adult are the only documented values, so confirm the accepted spellings with your account manager.

A promotion is two prices in Lamoda's vocabulary: the compare-at price as g:price and the discounted one as g:sale_price, which Feedflock fills automatically and clears when the compare-at price goes away. The third price element is Poland's own: under the Omnibus rules a shop must show the lowest price of the 30 days before a promotion next to the discount. Shopify has no such field, so g:omnibus_price ships empty, since deriving it from the compare-at price would state a legal figure your shop never computed. If you track the 30-day low in a metafield, the mapping is ready.

And one expectation to set before you start: the feed can be correct today and the listings still won't appear tomorrow. Lamoda's own onboarding has you wait for a sales contact (up to two working days) and accept the terms from an activation e-mail. That is a commercial gate, not a technical one, and it is worth knowing before you mistake it for a broken feed.