idealo, PriceRunner and Kelkoo: Price Rank Before Bid

On a comparison engine you buy position with price, not with bid. An offer sitting outside the three cheapest on an idealo product page converts at a fraction of the top offer's rate, and no CPC fixes that, so if your leading thirty products sit more than about four percent above the median offer, raising bids buys visits that leave. The first deliverable is that price-rank table. On roughly half the merchants who ask for this work it ends the conversation before money reaches a channel, and I would rather that happen in week one. Matching before bidding: idealo and PriceRunner attach an offer to a catalogue product through EAN and MPN. A match rate below about ninety percent means a real share of the catalogue sits as an unattached offer that shoppers never see when they compare. Fixing it is data work: correct GTINs, variant-level identifiers rather than parent codes, brand strings spelled the way the engine holds them, and manual mapping submissions where the engine's own catalogue is wrong. PriceRunner matches more strictly than idealo and rejects more. That is a feature, and it is also why a feed that satisfies idealo is not ready for PriceRunner. Fields that move ranking: Delivery cost and delivery time form part of the compared price and part of the sort, so a free-shipping threshold expressed correctly moves rank further than a bid change. Stock accuracy decides whether clicks are wasted, which sets sync interval: hourly for fast-moving lines, daily for the rest, and deciding which is which is the judgement being paid for. Where idealo Direktkauf is on the table, I will tell you whether its checkout and returns obligations are worth the volume at your margin, and for some merchants the answer is no. Kelkoo: Kelkoo Group is both a comparison engine and a Google CSS partner, and those are two separate decisions. Moving Shopping campaigns to a CSS partner changes who fronts your bids and what you pay for them; it is worth doing for some merchants and immaterial for others. I run that arithmetic against your own Shopping spend before recommending either way, rather than presenting the migration as free money. Bidding: Category-level CPC where the engine allows it, product exclusion where it does not, and a standing rule that a product falling out of the top three offers is paused rather than bid up. Budget follows price competitiveness. When merchandising changes a price on Thursday, the campaign reflects it on Thursday. Not included: Building or migrating a PIM. Feed tool licences: I work inside Channable, Productsup or DataFeedWatch if you have one, and I will not sell you a new one. Setting your prices — I show the rank consequence and you decide. Amazon and Google Shopping account management. Returns policy and service terms, which the engines display and which affect you whether or not anyone advertises. Who this is not for: Brands bound by minimum advertised price rules that cannot compete on displayed price. Merchants whose leading products are exclusive to them, because with no competing offers a comparison engine has nothing to compare and the same traffic is cheaper elsewhere. Anyone who wants one feed pushed to every engine: one feed per engine is the entire point of the exercise. Reporting: Monthly, product level, price rank next to cost and revenue, with the exclusion list first and the products worth a price decision named individually.