Prisjakt is a price comparison site: a shopper opens one product page and sees what every listed shop charges for it. Getting your shop onto those pages starts with a product feed — and whether your shop is listed at all is Prisjakt's decision, not something a feed makes true.
The Prisjakt feed channel type builds that feed: a channel whose columns follow Prisjakt's offer specification, which is an extension of the Google Shopping one. The same feed and the same fields serve PriceSpy, Prisjagt, Hintaopas, leDénicheur and Pagomeno — those are this platform's names in other markets, not different products, which is why there is one channel type rather than six.
What setup does — and doesn't — get you#
Being straight about this matters more than the setup steps, because the first two decide whether the feed does anything at all:
- Creating this channel prepares a feed. It does not list your shop. Prisjakt approves each shop before it appears in the comparison, and you apply per market. The application form asks for your feed URL up front, so a published channel is the useful half of the work — but Renable can't apply for you, and "the feed published" never means "my products are on Prisjakt". Listing itself is free, though a free listed shop shows prices only: a clickable offer that sends shoppers to your store runs on a cost-per-click agreement with Prisjakt. [VERIFY: whether every market's application form asks for the same things as the Swedish one.]
- "How many of my products will show up?" is a matching question, not a feed question. Prisjakt matches your offer onto the product page other shops are already listed on. The documented accelerator is the barcode — Prisjakt says including
gtinhelps it index your products faster — withmpnas the second signal, and atitlecarrying brand and model as the structural one. So the honest answer comes from your own barcode coverage, which the channel's Fields tab already shows as a fill rate on thegtinrow. Nobody can give you a percentage in advance, and Renable won't invent one. Filling the gaps is the highest-value work you can do for this channel — see Add missing GTINs, brands, and identifiers. - How fast your prices reach Prisjakt depends on your Prisjakt package, not on Renable. Prisjakt re-reads your feed on a schedule that comes with the package you sign up for. Renable has no way to see which package you hold, so it never tells you an interval — if timing matters, and on price it usually does, that's a question for Prisjakt. [VERIFY: which refresh frequency each Prisjakt package includes, and whether the higher packages read more often — Prisjakt's package page lists intervals, but which tier each belongs to isn't confirmed.]
- A Prisjakt listing is not an ad. That's not a hedge, it's what the surface is: a comparison row is your shop name, your price and a link, drawn from your product data. Renable treats it that way: your Studio ad templates don't ride this channel, and nothing in the product describes a Prisjakt listing as an ad. (The project page's healthy-state line says your products are shipping to their destinations, so a live Prisjakt channel does appear there — that sentence is about the feed being delivered, which is exactly what's true here.) What carries here is the product photo, so the image work still pays off: a clean, well-cropped, background-removed picture reads far better in a comparison grid than a busy one.
- This channel builds Prisjakt's offer feed, and only that. Prisjakt also takes promotion, local shop and local offer feeds — separate feeds with their own fields and their own registration, not add-ons to this one. Renable doesn't build those.
Creating the channel#
From a project's Channels section, create a channel and pick the Prisjakt feed type. It seeds:
- The columns Prisjakt reads — the six it requires (
id,title,link,price,availability,condition) followed bysale_price,image_link,description,brand,gtin,mpn,item_group_id,google_product_categoryandproduct_type— bound to your product data, under Google'sg:names. Prisjakt names Google's product specification as a directly supported format and writesg:-prefixed elements in its own examples, so if you already run a Google Shopping channel this one will look familiar. - Price with the currency inside it. The
pricecolumn writes the amount, a space, and the currency code —249.00 SEK. Prisjakt reads the currency out of that value, so there's no separate currency column to map, and it takes at most two decimals. - Two starter rules — availability drops to
out_of_stockwhen a product's stock hits zero or its content is incomplete, and sale price fills only when a product is actually discounted. - No custom label columns. Custom labels exist to segment ad campaigns, and a price comparison has no campaigns to segment. You can still add them from the Fields tab if you want them for your own bookkeeping.
On the Settings tab, the Used for card shows the channel declared for Prisjakt with its always-on Price comparison listings use — that's what switches on the field checks. Prisjakt has no add-ons at all, and the reason here is plainer than for any other destination: a price comparison builds a listing row out of product data rather than a creative, so there is no ad format for an extra chip to describe. There's no Used as choice either — a Prisjakt feed is always the Main feed.
The file format stays yours. Unlike the ChatGPT and Reddit channel types, this one doesn't preset anything: XML is the platform default and one of Prisjakt's own named formats, so the File format select stays unlocked. CSV and TSV are accepted too, and Renable won't warn about any of the three.
One channel, or one per market? That question is genuinely open. The field set, the formats and the validation rules are identical in every market — what changes is the market itself: the currency inside each price, the product-page links your shop serves there, and a separate application and price list per country. Prisjakt doesn't document whether it wants one feed covering several markets or one feed each, so ask your Prisjakt contact before you build the second channel rather than guessing. [VERIFY: whether Prisjakt accepts a single feed covering several markets.]
Delivering the feed#
Prisjakt fetches your feed URL. You give Prisjakt the URL when you apply, and Renable keeps that same address up to date from then on. Managing it afterwards happens in Prisjakt's Business Center, which comes with the paid packages rather than with a free listing — so on a free listing, the application is where the URL is set. See Connecting a channel to Meta, Google, or TikTok for where to find the URL.
A few details worth knowing:
- Renable can't push to Prisjakt. Prisjakt does accept a push, but its two routes are a manual upload in Business Center or its own feed API — neither of which Renable performs. The channel's SFTP delivery section isn't the answer here; the hosted URL is, and it's the route that stays current without anyone touching it.
- The feed URL has to serve a valid TLS certificate. Prisjakt treats an invalid one as a hard error and stops reading the feed rather than warning about it. Renable's feed URLs serve a valid certificate, so this only matters if you put your own domain or proxy in front of the URL.
- Compression is the one thing Prisjakt doesn't settle. It does ask for gzip — but as an HTTP compression header, which the address Renable serves already handles on the plain file. Nothing it publishes says it reads a gzipped file, which is what the Compress feed file (.gz) switch produces. So Renable neither recommends the switch nor warns about it: leave it off unless Prisjakt tells you otherwise. [VERIFY: whether Prisjakt reads a gzipped feed file at the URL.]
- A feed Prisjakt can't read gets switched off. After repeated failed attempts — an unreachable URL, or an empty file — Prisjakt disables the feed and emails you, so an outage on your side doesn't quietly become a missing listing.
Checking the output#
- Preview tab → Source view shows the exact file content per product.
- The Fields tab marks Prisjakt's six required fields — product ID, title, link, price, availability and condition — and their fill rates from the latest render. It's a short list on purpose:
brand,descriptionand the product image are all recommended on Prisjakt, not required. A product missing one of the recommended fields is still accepted; a product missing one of the six is dropped from the feed entirely. - The product ID rule is the strictest of any destination, and it's checked here. Prisjakt allows 1–36 characters, plain ASCII only, none of
! @ # $ % ^ & * < > ; :, no space at the start or end, and a different ID for every product in the feed. (+is allowed — Prisjakt relaxed that in late 2025.) Renable checks the length, the character set and the leading/trailing spaces on the Fields tab, and raises a warning on the channel when products break one of them — worth catching before Prisjakt does, because a rejected ID takes the whole offer with it. Uniqueness is the one part Renable can't check: it's a question about the whole feed rather than about one value, so if two products can end up sharing an ID, that's on your catalog to prevent. - Availability values are written with underscores (
in_stock,out_of_stock,preorder,backorder) — Prisjakt's specification is a Google Merchant extension and prints Google's spellings. The Prisjakt channel type already writes them that way; Renable also accepts the spaced spellings here, so a channel copied from a Meta, Snapchat or Pinterest feed isn't called out for it. Condition readsnew,refurbishedorused. - Render results and warnings show on the Activity tab — see Channel events and troubleshooting.