Proxies for IKEA get another clean residential-versus-datacenter split, on a catalog that is unusually tied to place. On 24 August 2026 we sent the IKEA US site a plain request from a home connection and it loaded, HTTP 200, with an ikea_geo cookie and heavy Forter and F5 Shape signals in the page. The identical request from a datacenter server got Cloudflare's "Attention Required" challenge. So the door is Cloudflare, trusting the residential IP and challenging the datacenter one, with Forter scoring orders and Shape scoring behavior behind it.
IKEA is a global home-furnishings retailer, and its data is unusually place-bound: prices differ by country, and because so much of the range is bulky and stocked locally, availability is per store. That makes the proxy job a country-and-store-matched read behind a layered Cloudflare defense, close to Wayfair but with a stronger store-stock component.
What proxies work best for IKEA?
Residential proxies exiting in the country whose store you read, behind a real browser, one exit per session. A static ISP proxy for a logged-in IKEA Family account. Datacenter proxies get challenged on contact.
Cloudflare at the door, Forter and Shape behind it
Cloudflare distrusted our datacenter address and served the challenge, while the residential address loaded; it reads IP reputation and the TLS fingerprint, so a residential IP behind a real browser is what passes (how to scrape past Cloudflare, what is JA3/JA4 fingerprinting). Behind it, F5 Shape scores the session's behavior over time (how to handle F5 Shape), which means one consistent exit per session beats rotation, and Forter scores orders, which matters at checkout rather than for reading. The combination is a residential IP for reputation, a real browser for the fingerprint and Shape, and consistency across the session.
The price is a country, the stock is a store
IKEA localizes hard. It runs a storefront per country in local currency with its own range, and it keys availability to a selected store because the catalog is heavy and stocked locally, so the same item can be a different price in another country and out of stock at the next store over. A dataset needs to pin both the country and the store, match the residential exit to that market, and record both, the way store-level retail works generally (geo-testing with proxies confirms the exit country).
Exit country
sets the storefront and currency
Cloudflare
datacenter challenged
Selected store
stock keyed locally
Price plus availability
per country, per store
Which proxy type fits which job
| IKEA job | Proxy type | Why |
|---|---|---|
| Cross-country price comparison | Residential, one pool per country | Per-country storefronts and currency |
| Store-level availability | Sticky residential per store | Bulky range stocked locally |
| Range and category collection | Rotating residential behind a browser | Cloudflare distrusts datacenter |
| Review collection | Rotating residential | Separate endpoints, own limits |
| IKEA Family account, cart | Static ISP | Session and Forter order scoring need one address |
| Parser tests against saved HTML | Residential (datacenter is challenged) | Datacenter draws the challenge |
Rotating residential IPs pass Cloudflare and land in the country you choose, and ISP proxies hold one address for an account. The two are compared in rotating vs static residential proxies.
Setup
Drive a real browser and hold one residential exit per session, because Shape scores behavior (proxies for Playwright). Pin the country and the store, match the exit to that market, and record both country and store with every price and stock reading. For accounts, use a static ISP address because Forter scores the order on consistent signals. Pace like a shopper.
Sizing
Country and store are the multipliers. Run one residential pool per market, pin the store, and find how fast one IP reads behind a browser before Cloudflare escalates, adding exits with a sticky exit per store. Budget browser-level bandwidth (headless browser proxy bandwidth cost). Our pricing is pay-as-you-go with a balance that does not expire.
Free versus paid for IKEA
A free datacenter IP draws Cloudflare's challenge, so it is not a monitoring tool; it can confirm which country a page serves from a clean residential IP, which our free proxy list and proxy checker cover. Monitoring price and stock needs residential from $0.44/GB pay-as-you-go with no KYC behind a real browser. The line is in datacenter vs residential proxies.
Staying unblocked
- Do not rotate mid-session. Against Shape, an IP swap inside a session is a bot tell.
- Do not retry the challenge from the same datacenter address. Use a residential exit and a browser.
- Pin the country and the store. A blended-store stock number is misleading, and the country sets the currency.
- Match the exit to the market. A mismatched exit reads the wrong price.
- Watch the challenge rate per country pool. A rising share means slow that pool down. The full list is in avoiding IP bans while scraping.
What a proxy does not do here
A proxy lands a browser in the right country and keeps sessions and accounts apart. It does not solve a Cloudflare challenge on its own, does not make a headless client behave for Shape, does not clear Forter on a suspicious order, and does not equalize the per-country prices. Scraping ikea.com runs against its terms of use, a risk that stays with you regardless of the IPs. What a country-correct residential exit does is read the local price and store stock a datacenter client cannot reach. Confirm the destinations with the free proxy list, then price each market and store with residential from $0.44/GB.
Sources
- Cloudflare, bot management: the layer that challenged our datacenter IP.
- F5, Shape / Distributed Cloud Bot Defense: the session-scoring layer in the page.
- Forter, order fraud prevention: the order-scoring layer present.
- HProxy test on 24 August 2026: plain GET requests to the IKEA US site from a residential IP (HTTP 200, Forter and F5 Shape present) and a datacenter IP (Cloudflare Attention Required challenge).