Deliveroo became part of DoorDash on 2 October 2025, at which point it operated in nine countries: the United Kingdom, Ireland, France, Italy, Belgium, the United Arab Emirates, Kuwait, Qatar and Singapore (DoorDash investor relations). In February 2026 DoorDash said it would wind down Qatar and Singapore (DoorDash investor relations), which leaves a marketplace centered on the UK with six other markets attached, each with its own site, currency, fee schedule and membership terms. The storefront in every one of them is built from a postcode or an address: which restaurants deliver there, their menus and prices, the fee, the estimate. A city is many postcodes on a schedule, and that is where proxies come in.
Deliveroo also has the most distinctive front door in DoorDash's family. Its own US site challenges datacenter clients with Cloudflare, Wolt's door is open, and Deliveroo's serves the page through Cloudflare and then scores you with PerimeterX. The details are below, with the jobs, the type that fits, and how to set up, size and bound the work.
What fits
Residential proxies pinned to the country and city of the storefront, driving a real browser, one postcode held per session. A restaurant-partner login sits on a static ISP proxy of its own. A datacenter or free exit can load the shell, which we confirmed, and PerimeterX is built to score exactly those addresses down on the pages after it.
Deliveroo as a target
Four surfaces. Restaurant storefronts, built per postcode, with menus and prices set by the restaurants and fees set by Deliveroo per market. Deliveroo Plus, the membership that changes the fee schedule. Deliveroo Hop and the grocery partners, where prices belong to Deliveroo or to a supermarket rather than a restaurant. And the market layer: seven remaining countries, each a separate site in its own language and currency.
Deliveroo's site is a JavaScript application. The shell loads first, and the restaurants and prices arrive through Deliveroo's own API calls keyed to the postcode in the session. The PerimeterX scripts that ride along collect the sensor data a real browser produces and a bare client does not.
Jobs a proxy is right for
- Menu and price monitoring across cities. Chains check what their own listings charge in London, Manchester and Dublin, and whether franchisees mark up; independents track the competitor down the road; price-intelligence firms build the dataset.
- Fee and Plus research. Delivery fees, service fees, small-order charges and Plus perks per market, and how they move.
- Postcode coverage. Which restaurants reach a postcode, and where the gaps are. Chains verify every site; ghost-kitchen operators pick locations by mapping reach.
- Cross-market comparison. The same brand in London, Paris and Dubai, in local currency, read from an exit in each country.
- Listing accuracy. A restaurant group checking that its hours, menu and photos are right in every city.
Jobs a proxy is not for
Rider accounts. Identity and right-to-work checks.
Promotion credits and multiple accounts. Phone, payment and device are what link accounts, and farming credits runs against Deliveroo's terms.
Ordering from abroad. The site wants a local payment method and a real address in the delivery area, and neither comes from a network.
The door: Cloudflare in front, PerimeterX behind
Our German datacenter server asked deliveroo.co.uk for its homepage once on 24 August 2026 and received the application shell, HTTP 200 through Cloudflare, no challenge page, with PerimeterX (HUMAN) script references and cookies riding along. Our twenty free proxies from the free proxy list then made one request each; 14 could not connect and 6 loaded the shell.
That combination is the pattern to plan for. Cloudflare at the edge did not challenge us, so the front door is open. PerimeterX then scores every session on the sensor data the client sends back, and a session that sends none, or sends it from an address thousands of strangers share, meets the press-and-hold challenge and then a block. A real browser on a residential exit produces the sensor data and the reputation that pass. Handling PerimeterX and HUMAN covers the mechanism; the same vendor guards Walmart, which we describe in proxies for Walmart.
Cloudflare edge
open for our test
Shell + PerimeterX sensor
scores the client
Residential exit + real browser
sensor data, clean reputation
Postcode session
menus, prices, fees
Type by job
| Deliveroo job | Proxy type | Why |
|---|---|---|
| Menu and price monitoring across cities | Rotating residential, country and city pinned, sticky per postcode | Reads as a local; passes PerimeterX with a real browser |
| Fee and Plus research | Rotating residential, sticky per postcode | Fees are per market and per session |
| Postcode coverage | Rotating residential, sticky per postcode | Each postcode is one session |
| Cross-market comparison | Residential in each country | Seven markets, seven sites |
| Restaurant-partner login | ISP (static residential) | One fixed, trusted location per account |
| One manual look at one postcode | Datacenter, or a fresh free proxy | The shell answered; the scoring will not let a sweep through |
Datacenter vs residential proxies has the general background.
Free proxies here
Six of twenty loaded the shell, which is not the data, and PerimeterX decides what happens next. A fresh UK free proxy inside a real browser might show you one postcode once; live UK exits are reasonably common in the free pool, so it is a fair experiment for a single look, and our free UK proxy page explains what to expect. Verify the exit in the proxy checker first. Once the job is a schedule, our residential proxies start at $0.44/GB, pay as you go, no KYC, pinned to the UK or any other Deliveroo country.
Setup
- Country and city pinning. A London postcode from a London exit, a Paris arrondissement from a Paris exit. Mismatches lower the score before you have read a menu.
- Real browser, cookies kept. The PerimeterX cookies are the session's standing; keep them for the session and never share them across exits. The Playwright proxy guide shows how to hand the browser the proxy at launch.
- Sticky session per postcode. Enter the postcode, read the storefronts you track, record postcode, currency and timestamp, rotate. Sticky vs rotating proxy sessions explains why rotating mid-session restarts the scoring.
- Retire an exit at the first press-and-hold. It is the scorer's verdict on that session; solving it by hand and continuing just delays the block. The remaining habits are in avoiding IP bans while scraping.
Sizing
Auditing a chain across the UK and Ireland, weekly:
cities 12
postcodes per city 8
pages per postcode session ~10
sessions per exit per day 4-6
exits in rotation ~20-25 residential, city-pinned
Adding France, Italy, Belgium, UAE, Kuwait:
exits per market ~6-10 residential each
Storefront pages with images blocked are small and bandwidth is the unit, so the postcode list sets the bill. Adding a market for a week and dropping it costs that week, since our pricing has no subscription.
Where it ends
A local address and a clean reputation to spend are what the session gets from the exit; the sensor data comes from a real browser, and Deliveroo's terms, which prohibit scraping, read the same through any address. Rider identity, account links and local payment methods stay where they are. Within them, a country-pinned residential exit lets a legitimate data job read public storefronts in seven markets the way locals at each postcode see them: one postcode per session, human pacing, and the challenge rate on a dashboard.
The UK rival with a harder door (a Cloudflare block page rather than a score) is in proxies for Just Eat; the sibling brand with an open door across 27 markets is in proxies for Wolt.
Sources
- DoorDash investor relations, 2 October 2025, completion of the Deliveroo acquisition (nine countries listed): ir.doordash.com
- DoorDash investor relations, 25 February 2026, wind-down of Deliveroo in Qatar and Singapore: ir.doordash.com
- HProxy measurement, 24 August 2026: one direct request from a datacenter server (HTTP 200 through Cloudflare, PerimeterX markers) and 20 elite HTTP proxies from our free proxy list (14 no connection, 6 shell).