Bigshopper is a European price comparison platform that has run as a shopping search engine since 2007, listing products from connected webshops so consumers can compare prices before they buy. Today it operates in 21 European countries, including Belgium and the Netherlands, and works with more than 3,000 connected online stores.
Bigshopper's other, increasingly central role is as a Premium Google Comparison Shopping Service (CSS) partner, a status it has held since August 2018 that lets it meet Google's stricter Premium Partner requirements and bid into the Google Shopping auction on a merchant's behalf. For most advertisers evaluating Bigshopper today, it functions less like a classic Akakçe-style comparison listing and more like an alternative, lower-cost route into Google Shopping ads.
Two distinct benefits are documented for advertisers connecting a feed to Bigshopper:
The trade-off is that Bigshopper's CSS service is a paid, flat-fee subscription rather than a free listing (details in the next section), so the calculation is whether the auction advantage outweighs the monthly cost for your catalog size and country count.
Unlike Google's own CSS, which effectively takes a share of ad performance, Bigshopper prices its CSS service as a flat monthly fee per country, independent of ad spend or how many products you list. Published plans are:
| 租赁计划 | 价格筛选 |
|---|---|
| Product Listings Only | €29 per country / month |
| Self-service CSS Professional | €29 / month + €19 / month per extra country |
| Self-service CSS Premium | €49 / month + €19 / month per extra country |
Bigshopper advertises a 30-day free trial and monthly (calendar-month) cancellation with no long-term contract, plus a discount for paying annually. Because pricing is per country rather than per click or per product, the economics change depending on how many markets you plan to run Shopping ads in.
Bigshopper accepts three connection methods: a CSV 文件,一个 XML product feed, or a direct read of your existing Google Merchant Center feed through a Bigshopper-provided API address that you authorize in Merchant Center. Bigshopper's own guidance is that the feed should be structured to match the Google Shopping feed specification as closely as possible, since it reuses the same underlying product data model that Google Merchant Center uses.
If your Merchant Center account holds more than 100,000 products, Bigshopper specifically recommends submitting a separate XML feed rather than relying on the API connection. Submitted feed data is documented as being uploaded and then refreshed on a daily basis.
Bigshopper has not published its own distinct, itemized attribute specification the way some comparison engines do — what's documented instead is that it consumes the same core fields as a standard Google Shopping / Merchant Center feed: identifier, title, description, landing page link, image, price, availability, brand and category. Since Bigshopper's matching relies on Google-standard data, keeping your feed aligned to that spec is the safest way to stay compatible, rather than building a Bigshopper-specific variant.
One piece of Bigshopper-specific guidance did surface: including a GTIN/EAN value for each product is reported as recommended by Bigshopper to help its product-grouping logic match identical items across different sellers more reliably. Treat this as directional advice rather than a confirmed mandatory field, since Bigshopper's own help documentation was not directly accessible to verify the exact wording.
Feedance sits between your store's product data and the feed Bigshopper needs, so you don't have to hand-build or hand-maintain a separate export.
Because Bigshopper's onboarding also depends on account-level steps outside of feed data — a signed order confirmation and an email confirming who administers your Google Merchant Center — Feedance handles the data side while you complete those account steps directly with Bigshopper.
Bigshopper documents daily refreshes for feeds submitted as XML files. For price-comparison traffic specifically, stale prices or stock status are a direct trust problem for shoppers landing from a comparison listing, so a daily sync is best treated as a minimum rather than a target. Some feed-management integrations built for Bigshopper advertise closer to real-time inventory synchronization, so that products going out of stock are removed from listings promptly rather than waiting for the next daily cycle. If your prices or stock levels change intraday, more frequent updates than the documented daily minimum will reduce the risk of listing prices that no longer match your site at the moment of the click.
Bigshopper does not publish its own list of feed error codes or rejection messages, so nothing specific to Bigshopper can be cited here. What can be said with confidence is that because Bigshopper's CSS listings are built on the same product data as Google Merchant Center, the failure modes that break a Google Shopping feed — missing or mismatched identifiers, out-of-stock items still marked available, category mismatches, broken image links, and landing-page prices that don't match the feed price — are the same categories worth auditing before and after connecting to Bigshopper. Treat this as general feed hygiene rather than a documented Bigshopper error list.
These are general product-feed best practices, not Bigshopper-specific requirements:
Is listing on Bigshopper free?
Basic comparison-site listing has no connection cost and no click fees on traffic from Bigshopper to your store. Running Google Shopping ads through Bigshopper as a CSS partner is a separate, paid subscription starting at €29 per country per month.
Does Bigshopper charge per click?
No. Bigshopper's CSS plans use a flat monthly fee per country rather than a cost-per-click or percentage-of-spend model.
Which countries does Bigshopper cover?
Bigshopper operates in 21 European countries, including Belgium and the Netherlands.
入职需要多长时间?
Bigshopper describes the CSS connection itself as a 5-10 minute setup, arranged within 24 hours, once you've submitted a signed order confirmation, connected a feed or API access, and sent an email confirming your Google Merchant Center administrator.
What feed format do I need?
CSV, XML, or a direct connection to your existing Google Merchant Center feed via an API address Bigshopper provides. If your Merchant Center catalog exceeds 100,000 products, Bigshopper recommends the XML route.