Give it a thuisbezorgd.nl restaurant menu URL - or just the restaurant's slug - and get that kitchen's customer reviews back as rows: the headline, the comment, the date, the overall rating, and the three scores Thuisbezorgd asks for separately. Delivery, food and service each get their own column, so a restaurant that cooks well and delivers late shows up as exactly that.
The input is the kitchen, not the review - you name the restaurants you want feedback on and the job collects what their customers wrote.
One row per review, each tagged with the query it came from - so a run across fifty restaurants still reconciles back to your input list.
Thuisbezorgd asks customers to rate three things, and all three arrive as their own columns next to the overall rating. A cold-but-tasty meal and a hot-but-late one average to the same star; here they do not.
Thuisbezorgd sits behind Cloudflare, which is why a hand-rolled script on an office IP comes back with a "Just a moment" interstitial instead of data. Residential routing, rate limiting and IP rotation happen on our side; from yours it is a form or an API call.
Paste the full menu URL if you have it, or just the restaurant slug - mr-sushi-dedemsvaart - and the job resolves it. Whichever your list already holds is the right input; there is nothing to normalise first.
Each row carries the review as Thuisbezorgd displays it: who wrote it, the headline, the comment, the date, the overall rating, and the delivery, food and service scores the customer gave separately.
Text comes back verbatim, with no preprocessing applied, so downstream sentiment work reads the customer's own wording rather than ours. The column list below is the header row of real run exports rather than a specification - and it is worth reading the note under it, because those runs are the reason this page describes the schema and not the value formats.
Taken from the header row of real run exports, identical across them and identical to the column list the platform ships. Read the note underneath before you write a parser: these names are verified, and the value formats are not.
One thing to know before you write code against this. Thuisbezorgd is behind Cloudflare, and the free demo pool does not get past its interstitial. An export header row still names its columns, which is why the ten column names above are trustworthy. What we have not seen is the shape of the values, so this page deliberately claims no date pattern, no rating scale and no decimal places, and does not say whether the JSON export carries a rank field the workbook omits. Pull a free run and read the first rows before you assume any of them.
A per-query limit decides what a run costs and how much lands in the file. It is chosen before the job starts, alongside how you hand over the list of restaurants.
A few examples of how teams use delivery review data to answer a question they actually have.
Pull your own restaurants and read the delivery column against the food column. A kitchen scoring well on one and badly on the other tells you where to spend the week - a single averaged star rating never does.
Export every restaurant delivering to an area and compare ratings and comment volume side by side. Useful before opening a location, and useful afterwards for knowing who you are actually losing orders to.
Verbatim comments across dozens of restaurants make recurring failures visible as repeated language - late, cold, missing item - instead of as a rating that drifted a tenth of a point.
No subscription, no minimum, no recurring bill. Your first 500 rows are on us - after that, pay-as-you-go at the same flat rate as every other scraper here.
Every new account, one-time. No credit card required. Per-query limits, file upload and every export format included.
Roughly $2 per 1,000 reviews. The pre-flight estimator shows the row count and credit cost before a run starts - no surprise bills, no compute units to translate.
Volume pricing, dedicated workers and an SLA for continuous monitoring or very large historical pulls. Tell us your numbers and we will quote.
LIVESCRAPER10 at checkout.The other half of a restaurant's reputation - what people said about eating there rather than about the delivery. Same kitchens, a different room.
Reviews of the platform and the brand rather than the individual kitchen - title, full text, star rating, date and the author's reviewing history.
Short answer: yes for the public review content - and this export carries nothing about the order itself.
Reviews on Thuisbezorgd are published to be read. The rating, the headline, the comment, the date and the three component scores are shown to anyone who opens the restaurant's menu page, signed in or not. Collecting publicly visible feedback for research is long-established practice, and nothing here touches a login, a basket or a paywall.
The reviewer field carries what the site itself publishes, which is a first name rather than a full identity - there is no profile link, no address and no contact detail in this output. Nothing about what was ordered, what it cost or where it went is collected, because none of that is public. If you are processing the comment text in the EU, the usual rules still apply to what you do with it downstream.
Thuisbezorgd's own terms restrict automated access, so this is a terms question as well as a legal one - if you have a contractual relationship with the platform, check it. We run no third-party trackers on the data layer, and your exports auto-delete after 30 days.
The questions we hear most. Anything else? Talk to us - humans, not bots, write the answers.
500 one-time free rows on every new account - no expiry. After that it is $0.002 per row, pay-as-you-go - no card on file until you say so.
Livescraper's Thuisbezorgd Reviews Scraper turns a list of restaurants into review data. You submit thuisbezorgd.nl menu URLs or bare restaurant slugs - typed one per line, or uploaded as a CSV, XLSX, TXT or Parquet file - cap the rows per query if you want to, and download what customers wrote as a clean CSV, Excel or JSON file.
Each row carries the review as Thuisbezorgd displays it: the reviewer, the headline, the free-text comment, the posting date, the overall rating, and the delivery, food and service scores the customer gave separately. That last part is what makes this dataset different from most review exports - three independent component scores next to the headline number, so a kitchen that cooks well and delivers late does not hide behind an average.
Restaurant groups pull their own locations and read the delivery column against the food column to find out which half of the order is failing. Strategy teams export every restaurant delivering to a postcode and benchmark ratings and comment volume side by side before opening a location. Researchers read verbatim comments across dozens of kitchens, where recurring failures appear as repeated language instead of as a rating that drifted a tenth of a point.
One practical note up front: Thuisbezorgd sits behind Cloudflare, which is why a hand-rolled script tends to return a "Just a moment" interstitial rather than data. Residential routing, rate limiting and IP rotation are handled on our side, so from your end it is a form or an API call and there is no proxy pool to run. Start free: your first 500 rows cost nothing and need no credit card, and after that it is $0.002 per row, flat.