Lieferando is where most of Germany orders delivery, and lieferando.de is where most of that data lives, behind a Cloudflare challenge. Just Eat Takeaway.com put the platform at close to 45,000 partner restaurants and retailers in Germany in July 2025, inside a group of more than 362,000 partners across 15 countries (Just Eat Takeaway.com newsroom, 17 July 2025), and the group became part of Prosus on 6 October 2025 (newsroom, 2 October 2025). The same July 2025 announcement described a 20 percent reduction of the group's own German delivery fleet, Takeaway Express, and a shift toward external fleet partners in some cities, which matters for data work because delivery fees and estimates are exactly what changes when the fleet behind a postcode changes.
Every Lieferando storefront is built per postcode: which restaurants deliver, their menus and prices, the delivery fee, the minimum order, the estimate. A city is many postcodes on a schedule, and the site challenges datacenter clients before showing any of it.
What fits
German residential proxies pinned to the city of the postcodes you read, driving a real browser, each postcode in its own session. Restaurant-partner logins belong on a static ISP proxy, one per account. A datacenter or free exit meets the challenge on the first request, and the count below says how that goes.
Lieferando as a target
Three surfaces. Restaurant storefronts per postcode, with prices set by restaurants and fees and minimums set per restaurant and market. Grocery and retail partners, where prices belong to a shop. And Austria, the second country under the same brand, on its own site and with its own fees.
Behind the challenge, lieferando.de is a JavaScript application. Once the challenge is passed, the restaurants and prices load through Lieferando's own API calls keyed to the postcode in the session.
Jobs a proxy is right for
- Menu and price monitoring across German cities. Chains audit their own listings and their franchisees' markups; independents track competitors; price-intelligence firms build the dataset. Berlin, Munich, Hamburg and Cologne are four different marketplaces in practice.
- Fee, minimum-order and estimate research. Especially now: with the group's own fleet reduced and fleet partners taking over some cities, delivery fees and estimates per postcode are the numbers people want to watch over 2026.
- Postcode coverage. Which restaurants reach a postcode, and where the gaps are, for site selection and competitor mapping.
- Cross-platform comparison. The same restaurant on Lieferando, Wolt and Uber Eats at the same postcode, which is the comparison German restaurateurs ask for most.
- Austria. The same brand across the border, read from an Austrian exit.
Jobs a proxy is not for
Rider accounts. Lieferando's own couriers are employees of its logistics arm, with normal employment checks. Nothing about an address enters that.
Promotion credits and multiple accounts. Phone, payment and device link the accounts, and farming credits runs against Lieferando's terms.
Ordering from abroad. A payment method the site accepts and a real address in the delivery area are things no network setting provides.
The door, measured
lieferando.de met our German datacenter server's single request on 24 August 2026 with HTTP 403 and Cloudflare's "Just a moment..." challenge page. The twenty elite exits from our free proxy list followed, one fetch apiece: 14 dropped before connecting, 5 connected and drew the challenge, 1 got a page back. Being in Germany did not help our server; the challenge is about the address type and the client, not the country. A datacenter address running a client that cannot execute JavaScript is what Cloudflare's managed challenge exists to stop.
That is a different door from the one on the group's UK brand, which blocks datacenter clients outright rather than challenging them (see proxies for Just Eat). A challenge is a test a real browser on a residential address passes routinely; the setup below is built around that. The mechanism is in scraping past Cloudflare.
Type by job
| Lieferando job | Proxy type | Why |
|---|---|---|
| Menu and price monitoring across cities | Rotating German residential, city-pinned, sticky per postcode | Passes the challenge; reads as a local |
| Fee, minimum and estimate research | Rotating German residential, sticky per postcode | Fees are per postcode and per session |
| Postcode coverage | Rotating German residential, sticky per postcode | Each postcode is one session |
| Cross-platform comparison | Rotating German residential, city-pinned | Same exits, three platforms |
| Austria | Austrian residential | Separate site, separate fees |
| Restaurant-partner login | German ISP (static residential) | One fixed, trusted location per account |
| Anything | Datacenter or free | Challenged at the door, 1 of 20 got a page |
The two address types are compared in datacenter vs residential proxies.
Free proxies here
One of twenty is the honest ceiling in a script. In a real browser a fresh German free proxy might clear the challenge once for one postcode, and live German exits are among the most common in the free pool, so it is a fair experiment for a single look; our free German proxy page explains what that pool looks like. Verify the exit in the proxy checker first. For the repeated version, our German residential proxies start at $0.44/GB, pay as you go, no KYC, pinned to the city.
Setup
- German residential exit, city-pinned. A Munich postcode from a Munich exit. The challenge is served less often to addresses that look like customers.
- Real browser with cookies kept. The Cloudflare clearance cookie is the session's pass; keep it for the session and never share it across exits. How to hand Playwright the proxy at launch is in the Playwright proxy guide.
- Sticky session per postcode. Enter the postcode, read the storefronts you track, record postcode and timestamp, rotate. Rotating mid-session brings the challenge back, for reasons sticky vs rotating proxy sessions explains.
- Slow down when the challenge returns. A returning challenge on a residential exit means that exit is being watched; retire it. The rest of the rules are in avoiding IP bans while scraping.
Sizing
Fee and estimate watch across 8 German cities, three times a week:
postcodes per city 12
pages per postcode session ~8
sessions per exit per day 4-6
exits in rotation ~20-25 German residential, city-pinned
Storefront pages with images blocked are light, and bandwidth is the meter, so the postcode list sets the bill. A watch can run through a season of fleet changes and stop, with nothing on our pricing page to cancel.
Where it ends
A German residential address is what turns the challenge into a page, and it is all the proxy contributes. Courier employment, account links, payment and Lieferando's terms, which prohibit scraping, are untouched by it. That leaves the honest job: a city-pinned German exit with a real browser reading public storefronts the way customers at each postcode see them, one postcode per session, paced like a person, with the challenge rate logged.
The group's UK brand with a harder door: proxies for Just Eat. The rival with an open door across 27 markets, Germany included: proxies for Wolt.
Sources
- Just Eat Takeaway.com newsroom, 17 July 2025, Lieferando expands fleet partners (close to 45,000 partners in Germany; Takeaway Express fleet reduced by 20 percent; group of more than 362,000 partners in 15 countries): newsroom.justeattakeaway.com
- Just Eat Takeaway.com newsroom, 2 October 2025, Prosus declares the offer unconditional (settlement 6 October 2025): newsroom.justeattakeaway.com
- HProxy measurement, 24 August 2026: one direct request from a German datacenter server (HTTP 403, Cloudflare challenge) and 20 elite HTTP proxies from our free proxy list (14 no connection, 5 challenge, 1 page).