Proxies for Zalando give each account or scraper its own clean, in-country IP, so Zalando's Akamai bot layer reads ordinary shoppers instead of one machine entering every raffle or pulling every price. The right proxies for Zalando are almost always residential: a stable ISP or residential IP per account for raffles and multi-account work, and rotating residential in short sticky sessions for reading prices and catalogue across Europe. Datacenter and free public proxies look cheap, and both get blocked at Zalando's Akamai wall fast.
We build and run proxy pools, so we see what people point at Zalando and what comes back as a blocked run the next morning. This is the honest version: why people use proxies for Zalando, which type fits which job, how many IPs you actually need, sticky versus rotating, and where the proxy stops doing the work. No proxy makes Akamai disappear on its own, and we will not pretend otherwise.
What proxies are best for Zalando?
Residential, matched to the country whose Zalando site you are using. Zalando is Europe's largest fashion platform, founded in Berlin in 2008 and now operating across more than twenty European markets, each with its own site, currency, and pricing. For raffles and account work, use a static residential or ISP IP per account and keep it stable. For scraping, use rotating residential in short sticky sessions so each identity holds one IP long enough to clear the Akamai check, then rotates. Datacenter dies at the wall, and free proxies die faster.
Two jobs on Zalando, two proxy setups
Almost everything people do with proxies for Zalando falls into one of two jobs, and the two do not want the same kind of IP.
Raffles and account work. Zalando runs raffles for hyped, limited sneaker releases, which randomise who gets to buy instead of rewarding whoever clicks fastest. The natural response is to enter with many accounts to raise the odds, which means many identities, each needing its own connection. This job is identity-bound: you want one stable, trusted, in-country IP under each account, the same way a real shopper logs in from the same home connection. Rotate the IP under a logged-in account and you look like a hijacked login. Worth saying plainly: mass raffle entry through many accounts breaks Zalando's terms, and a proxy lowers the clustering risk, it does not make the tactic policy-safe.
Price and catalogue scraping. Retailers, analysts, and resellers pull Zalando's prices, stock, and product data across countries to track markets and spot gaps. This job is high-volume and account-free: you want many clean IPs rotating through, each geo-matched to the market you are reading, because Zalando shows local currency and region-specific pricing.
Get this split right and most of the rest follows. Raffles and accounts want stability (one sticky IP that stays put). Scraping wants breadth (many rotating, in-country IPs).
How Zalando spots bots
Zalando's product pages sit behind Akamai's CDN and Bot Manager, and the _abck and ak_bmsc cookies in a Zalando session are the giveaway. Understanding what Akamai checks matters, because it decides which proxies survive.
- IP reputation. The first filter is the network your IP sits on. Datacenter ASNs get distrusted immediately and served an Access Denied or a challenge. Residential IPs, registered under consumer ISPs, clear this layer because they look like real homes. This is the layer a proxy actually solves.
- A browser fingerprint. Akamai injects JavaScript that fingerprints the client (canvas, timing, headers, TLS handshake, behaviour) and binds the result into the
_abckcookie, where a mismatch voids the session. A raw HTTP client with a perfect residential IP still fails here, because it does not look like a real browser. This is the layer a proxy does not solve. - Behaviour and biometrics. Akamai reads mouse movement, timing, and navigation flow, so a session that clicks like a script gets flagged no matter how clean the IP is. This matters most on raffles, where the whole point is to catch automated entries.
- Rate and pattern per IP. Hammer the catalogue from one address and you earn blocks quickly. A cleaner IP buys more headroom, but every IP has a ceiling.
The takeaway: a residential IP is necessary but not sufficient. It gets you through the reputation gate. Clearing the fingerprint and behaviour checks is a browser problem, which is why serious Zalando work drives a real or headless browser rather than firing bare requests.
Which proxy type fits Zalando
Four proxy types show up whenever people work Zalando, and price is a bad way to choose between them.
| Proxy type | Best Zalando job | Reality on Zalando |
|---|---|---|
| Static residential / ISP | Raffles and account management | Stable, trusted, in-country IP per account; keep it consistent |
| Rotating residential | Price and catalogue scraping | Clears the IP check; short sticky sessions keep the _abck cookie coherent |
| Mobile | Accounts Akamai keeps flagging | Carrier CGNAT shares it with real users, hardest to ban; highest cost |
| Datacenter | Very light, low-volume checks | Blocked fast at the Akamai gate; fine only where you barely touch the site |
| Free / public | Testing your parser, learning | Datacenter IPs that die in minutes; blocked on sight, only a small fraction alive |
Residential is the honest default because it is what clears the reputation gate. A residential proxy routes you through a real consumer connection, so the address reads as an ordinary home rather than a server farm, and we explain the tier in what a residential proxy is. ISP proxies (static residential) are the same legitimacy on always-on hardware, which suits account work: one stable, trusted, in-country address per login. Mobile is the heavyweight tier for accounts Akamai keeps flagging, at the highest price, so most Zalando setups never reach for it. Datacenter earns its keep only on jobs so light you barely touch the site.
Sticky versus rotating on Zalando
Because the _abck cookie is bound to your IP and browser fingerprint, pure per-request rotation works against you: every new IP is a fresh stranger that has to clear Akamai again, so you burn budget re-solving the wall over and over. The pattern that holds up for scraping is short sticky sessions. Hold one in-country residential IP for a run of requests, clear the check once, reuse the cookie for that session, then drop the whole identity and pick up a fresh in-country IP for the next batch. For raffles and accounts there is no debate: sticky, one in-country IP per account, held for the life of that account.
The free versus paid reality for Zalando
Here is the part nobody selling you a proxy list will say plainly. Most free proxies are datacenter IPs that die within minutes, and only a small fraction of any public list is alive at once. On Zalando that is the worst possible combination: a datacenter range that Akamai blocks at the gate, that is also already burned by everyone else who ran through it today. You spend more time filtering dead proxies than reading prices.
Free proxies do have one honest use on Zalando: testing. While you build the scraper and debug how you parse the price and product data, a free proxy (or no proxy against a cached page) is fine, because you are testing your own code, not collecting live data. Our free proxy list re-checks and refreshes every few minutes across 100+ countries and every common protocol, so what you see is at least alive right now, and the free checker shows an IP's real exit before you trust it. The safety side is in are free proxies safe. The moment you want live data or you are entering raffles, free stops paying off.
For real Zalando work, paid residential is the honest floor. Ours starts at $0.65/GB, pay as you go, no KYC, and Zalando's pages are lightweight, so a country-by-country price sweep costs little and a small test run costs cents.
Setting it up and staying unblocked
The setup is short. The habits that keep it working are the rest.
- Pick the right IP for the job. Static residential or ISP for raffles and accounts, rotating residential for scraping. Geo-match to the Zalando market you are using.
- Match the fingerprint. For account work, use an antidetect browser so each account carries its own fingerprint, and set its timezone and language to the IP's country. A German account on a German IP with a New York clock is an easy pattern to catch.
- Test the exit first. Confirm the IP is alive and exits in the right country with the free checker before you point it at Zalando. The method is in how to check if a proxy is working.
- Pace like a shopper. Add jitter, respect per-IP rate limits, and back off on the first block instead of retrying into a hard ban.
- Keep sessions coherent. One in-country IP per browser identity for a scrape run, one sticky in-country IP per account, never mixing countries mid-session.
- Do not reuse burned public IPs. A shared free proxy is already flagged from everyone else who ran through it this morning.
Where a proxy stops and you start
A proxy solves one specific thing on Zalando: it makes your IP look like a real home in the right country instead of a data center, and it keeps your identities isolated so one flagged IP costs you one session instead of all of them. That is worth a lot, and it is not everything. The browser fingerprint Akamai reads, the behaviour on a raffle page, and the account details behind a login are all still on you. The best residential IP in the world will not save a bare HTTP client that never runs the sensor JS, or twenty raffle accounts that share one fingerprint.
So match the IP to the job, geo-match it to the market, keep sessions sticky where they need to be, and pace like a person. Mass raffle entry and multi-accounting also run against Zalando's terms, a risk you own no matter how clean the IPs are. If you are still building or testing, start on our free proxy list and the free checker, which cost nothing and refresh every few minutes. When you are entering raffles or collecting real Zalando data, move to residential: ours starts at $0.65/GB, pay as you go, no KYC, so you size up only when the work is paying for itself.
Sources
- Wikipedia, what Zalando is, its Berlin founding, and its European footprint: en.wikipedia.org
- Hyper Solutions, Zalando's Akamai CDN and anti-bot layer on sneaker drops: hypersolutions.co