How to Set Up a Prisjakt Feed for Your Shopify Store (And Keep It in Sync)

Prisjakt is one of the highest-intent traffic sources available to Nordic e-commerce stores. Shoppers who visit via Prisjakt have already compared options and are close to buying. But that traffic only reaches you if your product data is correct, complete, and current. Most stores struggle to get there — not because the concept is complicated, but because the execution requires more precision than a quick CSV export.

What format does Prisjakt require?

Prisjakt uses a feed format based on RSS 3.0 — a structured XML file that you host or publish, which Prisjakt fetches on a regular schedule. Each product is represented as an item with specific fields.

The fields Prisjakt expects include: product title, product URL, image URL, price (including VAT), stock status, EAN/GTIN, brand, category, and condition. Prisjakt will accept a feed that's missing optional fields, but it will either reject individual products or rank them poorly in search results. Incomplete data means less visibility, which defeats the purpose of listing at all.

A few things catch stores out. First, the category must map to Prisjakt's own taxonomy — not your Shopify categories. Second, condition must be declared even for new products. Third, the feed URL must remain stable and return a valid response every time Prisjakt crawls it.

The required fields in detail

Getting the required fields right is where most stores either win or lose on Prisjakt. Here's what matters and why.

EAN/GTIN is the single most important field. Without it, Prisjakt cannot match your product to its database, and the product won't appear in comparison results. If your Shopify products don't have EANs stored, that's the first thing to fix — not the feed itself.

Product title format matters more than most people realise. Prisjakt's matching algorithm parses titles, so the format Brand + Model + Key Spec performs best. "Sony WH-1000XM5 Wireless Noise Cancelling Headphones" will match and rank better than "Sony headphones (black)" — even if both have valid EANs.

Price must always include VAT. Prisjakt displays consumer prices. If you publish ex-VAT prices, your listing will appear cheaper than it is, which leads to customer complaints and poor conversion once they land on your store.

Stock status should be accurate. Listing out-of-stock products wastes your feed inclusion and frustrates shoppers. At minimum: use "yes" / "no" — but if you can pass stock quantity, do it.

Brand must match Prisjakt's brand registry. Spelling variations or abbreviations can cause products to be grouped incorrectly.

Don't stop at Prisjakt: Klarna and Prisradar too

Once you've done the work of structuring your product data correctly, extending to Klarna Comparison Shopping and Prisradar takes relatively little additional effort — and the coverage difference is significant.

Klarna's feed format shares most fields with Prisjakt but adds two requirements: delivery time (in days) and shipping cost. These are surfaced to shoppers directly on the comparison page, so leaving them empty means you'll lose to stores that provide them, even at the same price.

Prisradar uses its own XML format, somewhat similar to Google's Shopping feed. The taxonomy and required fields overlap with Prisjakt, but the category mapping is different. You'll need a separate feed endpoint rather than pointing Prisradar at your Prisjakt feed.

The practical takeaway: generate each feed from a single product data source, with format-specific transformations. Three feeds from one source is manageable. Three separate manual exports is not.

The maintenance problem: keeping feeds in sync

This is where most setups eventually break down. You create a well-structured feed, submit it, and Prisjakt starts sending traffic. Then prices change — a supplier increases their wholesale price, you run a sale, you adjust margins — and the feed doesn't update.

Stale prices cause two problems. First, if your feed shows a lower price than your store, customers click through, see the higher price, and leave. Prisjakt tracks this as a negative signal. Second, if your feed shows a higher price than your store, you're losing on comparison ranking for no reason.

Manual exports will always be out of date. The update cycle is too frequent — prices can change daily or weekly — and the process is too easy to deprioritise when other things come up. The only reliable solution is automatic synchronisation: every time a price changes in Shopify, the feed reflects it within minutes, not days.

Competitive filtering: only promote where you can win

There's one more dimension worth addressing. Listing every product on Prisjakt regardless of your competitive position is a common mistake. If you're priced 15% higher than the three cheapest options for a given product, your listing will appear at the bottom of the comparison page — getting impressions but almost no clicks. You're paying the cost of being listed (feed maintenance, Prisjakt's CPC if applicable) without any return.

The smarter approach is to filter your feed to only include products where your price is within a competitive range — say, within 5% of the category leader. Products outside that range either need a price adjustment or should be withheld from the feed entirely until the situation changes.

This requires knowing your competitive position before the feed is generated, not after. Which means your pricing data and your feed data need to be connected.

---

ATHOMIC generates Prisjakt, Klarna, Prisradar, Google Shopping, Meta, and TikTok feeds directly from your Shopify product and pricing data — with automatic updates whenever prices change and competitive filtering built in. Product Feeds