Shoparize feed for Shopify

Shoparize's Product Feed Guide for Direct Integration is unusually concrete: to advertise your products it needs to connect automatically to a product feed on your website, and the fastest way through onboarding is to check the six required columns yourself before submitting the link. They are a subset of Google's required set, so a feed in the Google Shopping shape passes by construction.

That shape is the house format on purpose: Shoparize's own Shopify tutorial has the merchant generate RSS 2.0 with Google's g: namespace. The template Feedflock ships is exactly that document (one item per variant, g:-prefixed fields), and the checklist's named rejections (JSON, Google Sheets, anything behind a click) never apply to a hosted XML file.

Shoparize's system downloads the feed automatically from the URL you submit in the Partner Portal, and its checklist names the four walls that make the fetcher walk away: a login, a cookie-consent gate, a CAPTCHA, a click-through page. Its own first troubleshooting step is to open the link in a private window: if you see anything but the raw file, so will the fetcher.

A Feedflock feed is a plain public file on a stable URL, so there is nothing to whitelist and nothing to click through. How often Shoparize re-fetches afterwards is not published anywhere; Feedflock regenerates the file every hour, so whenever the fetch comes, it reads current prices and stock.

Shoparize sells three products off the same feed. Premium CSS is the flat-subscription Comparison Shopping Service: your Google Shopping ads run through Shoparize's CSS instead of Google Shopping Europe. Comparison Shopping is the marketplace play: listings on Shoparize.com for €33 a month plus a commission per sale, across the 21 European markets its site operates in.

Managed Ads is the hands-off option: Shoparize spends its own ad budget and bills you per sale. All three read the same product feed, so the plan is a commercial choice you can revisit; the feed work is done once.

A CSS is not a separate ad network: the ads still run in Google Shopping, the CSS is the entity they run through. That is why Shoparize's required six are a subset of Google's required set, why availability speaks Google's enum, and why the feed that serves Shoparize is the feed that serves Merchant Center: the same file can do both jobs.

The rest of Google's vocabulary rides along usefully: gtin and brand strengthen matching, g:google_product_category targets the taxonomy the pipeline works with, and a discounted product sends its compare-at price in g:price with the selling price in g:sale_price, the pair Shopping ads draw the strikethrough from. Across the 21 markets the structure never changes; only the currency and language the feed starts with do.