Proxies for Wolt: One Brand Across 27 Markets, and Storefronts Built Per City

Wolt is the name DoorDash trades under across most of Europe. Founded in Helsinki in 2014 and part of DoorDash since 2022, it was the brand behind 27 of DoorDash's markets as of March 2024 (Wolt newsroom), and in February 2026 DoorDash said it would wind down the Wolt operations in Japan and Uzbekistan while keeping the rest (DoorDash investor relations). One brand, one app, but the storefronts are built per city and per address, in the local language and currency, with local fees and local venues. A restaurant group with locations in Berlin, Helsinki, Prague and Tel Aviv sees four Wolts. So does anyone trying to compare them.

That is the whole reason proxies come up. The data (venues, menus, prices, delivery fees, estimates, Wolt Market grocery prices) exists only per city, and the site serves the city it believes you are in.

What fits, in one paragraph

Residential proxies pinned to the country and city of the storefront, driving a real browser, each address in its own session. Merchant and Wolt Market logins go on a static ISP proxy, one per account. A datacenter exit can load the shell, which we confirmed, and it is the first address metered once the venue and price calls start.

Wolt as a target

Three surfaces. City storefronts: wolt.com lists venues per city, and an address narrows them to the ones that deliver there, with menu, prices, fee and estimate. Wolt Market: Wolt's own grocery stores in many cities, priced by Wolt rather than by a merchant, which makes them a quick-commerce price target in the same way Gopuff is. And the market layer: 27 markets, each with its own language, currency, fee schedule, Wolt+ membership terms and promotions.

Wolt's site is a JavaScript application. The page that loads is a shell; the venues and prices arrive through Wolt's own API calls after it, keyed to the city and the address in the session. Reading one city is a session; reading twenty cities is twenty sessions in twenty places.

Jobs a proxy is right for

• Cross-market menu and price audits. A chain checks what its own listings charge and how they rank in each city, and whether local franchisees mark up. Analysts compare delivery pricing between, say, Copenhagen and Prague in local currency.
• Delivery fee and Wolt+ research. Fees, small-order charges and membership perks differ by market and move over time.
• Coverage by address. Which venues reach an address, discovered by entering it. Chains verify every location; analysts map the footprint as it changes.
• Wolt Market price monitoring. Wolt's own grocery prices per city, compared against local supermarkets and other quick-commerce players.
• Localization testing. Two dozen languages and currencies, each read from inside its country so the storefront renders the way locals see it. The general method is in geo-testing with proxies.

Jobs a proxy is not for

Courier accounts. Identity and right-to-work checks in each country.

Multiple accounts and promotion credits. Accounts attach to phone, payment and device; farming credits runs against Wolt's terms.

Orders from another country. A local payment method and a real address in the delivery area are not network properties.

The door, measured

wolt.com gave our German datacenter server its application shell on 24 August 2026, HTTP 200 through CloudFront, no challenge page. Of 20 elite HTTP proxies from our free proxy list, once each, 15 never got a connection, 3 loaded the shell, and 2 received another response. So the front door is open. The shell is empty until the API calls run, and those calls, keyed to a city and an address, are where a scraper's pattern shows: a customer loads one city a few times, a script loads a hundred. That limit is one we have not measured. Log the first rising 403 or 429 rate per exit and treat it as the number; fixing 429 rate limits through a proxy covers the back-off.

That is a softer door than the Cloudflare challenge we measured on DoorDash's own US site the same evening (see proxies for DoorDash), and a different one from Deliveroo's, which pairs Cloudflare with PerimeterX (see proxies for Deliveroo). Same parent, three doors.

Type by job

For the tradeoffs between the two residential flavors, rotating vs static residential proxies.

Free proxies here

Three of twenty loaded the shell, and the shell is not the data. A fresh free proxy in the right country can give you one look at one city if it lives long enough for the API calls to finish, which is the honest ceiling; the country part is the hard half, because the working free pool clusters in a few hosting-heavy countries and a live free exit in Finland or Czechia is rare. Filter our free proxy list by country, verify the exit in the proxy checker, and expect to try several. For a market sweep, our residential proxies start at $0.44/GB, pay as you go, no KYC, pinned to any Wolt country.

Setup

1. Country first, city second. Pin the exit to the country of the storefront, and to the city when the pool allows. A Polish exit reading Warsaw is right; a German exit reading Warsaw is the mismatch that changes what renders and draws scrutiny.
2. Real browser, cookies kept, firm timeout. The shell is nothing without the API calls, so a bare fetch gives you an empty page and a false sense of success. The Playwright proxy guide shows the launch config.
3. Sticky session per address. Enter the address, read the venues and prices you track, record city, currency and timestamp, then rotate. Why rotating mid-session loses the address is explained in sticky vs rotating proxy sessions.
4. Store the currency with every price. Twenty-seven markets means a dozen currencies; a number without one is noise.
5. Watch the block rate per country. Pools differ in size by country, so a small market's exits get reused more often. Slow down there first. Avoiding IP bans while scraping has the wider set.

Sizing

Auditing a chain across 8 Wolt markets, weekly:
  cities per market            2-4
  addresses per city           8
  pages per address session    ~10
  sessions per exit per day    4-6
  exits per market             ~6-10 residential, city-pinned

Storefront pages with images blocked weigh little, and bandwidth is what residential meters, so the address list sets the bill. A market can be added for a week and dropped again, because nothing in our pricing is a subscription.

Where it ends

The exit supplies a local address in the market you read, and Wolt's terms, which prohibit scraping, apply through any exit; courier identity, account links and local payment methods stay exactly where they were. What a country-pinned residential exit with a real browser makes possible is the legitimate version of the job: reading public storefronts in 27 markets the way locals in each city see them, one address per session, paced like a person, with the block rate on a dashboard.

DoorDash's other European brand has a harder door and a UK center of gravity: proxies for Deliveroo. Wolt's largest direct rival in Germany is in proxies for Lieferando.

Sources

• Wolt newsroom, 25 March 2024, Wolt enters Luxembourg and Albania ("DoorDash operates in over 30 countries today, 27 of which are with the Wolt product and brand"; founded 2014; joined DoorDash in 2022): press.wolt.com
• DoorDash investor relations, 25 February 2026, wind-down of Wolt in Japan and Uzbekistan and Deliveroo in Qatar and Singapore: ir.doordash.com
• HProxy measurement, 24 August 2026: one direct request from a datacenter server (HTTP 200, application shell via CloudFront) and 20 elite HTTP proxies from our free proxy list (15 no connection, 3 shell, 2 other).