A Just Eat catalogue is keyed to a postcode district rather than a city: move three kilometres across London and most of the partner list, the fees and the delivery estimates move with it.
You give us the storefronts, the postcodes or the partner slugs, the fields you need and a cadence. We design the schema, build and run the Just Eat scraper, watch it and repair it when the site moves, and you receive files rather than code: CSV, JSON, XLSX, a Google Sheet, a direct database load, or a hosted Just Eat API endpoint we run and you call, delivered over email, S3, SFTP or webhook.
Anti-bot handling, proxy rotation and CAPTCHA solving are part of the service and never become your problem - the storefronts are closed to automatic clients, and getting through that is our work, not yours. Coverage is planned as a list of postcodes rather than one call per town, because the catalogue and the fees answer to the point. We stay on public pages, keep away from basket, checkout, payment and account areas, respect the paths the robots file closes, and leave reviewer and courier names out by default as personal data.
A Just Eat partner card is a dense record where every field earns its place. It holds a numeric restaurant id and a slug, the trading name, a street address with city, first line, postcode and coordinates, a rating object with a star value and a review count, a new-partner flag, the drive distance in metres, the next opening time for shop and for delivery, a delivery estimate as an approximate figure with lower and upper bounds, booleans for delivery and collection plus three more for open-now on delivery, collection and pre-order, a temporarily-offline flag, a delivery cost, a minimum delivery value, a display rank, a temporary-boost flag, a logo url, a test-restaurant flag, and arrays of deals, tags and cuisines.
Two money encodings sit side by side, and mixing them ruins a Just Eat price feed. The card prints the delivery cost as a plain decimal, while the separate fee table for the same partner is currently in minor units: a minimum order value of 1499, with bands such as 0 giving 500, 2000 giving 400 and 7000 giving 0, so the fee drops as the basket grows. Deals arrive as a description plus an offer type from a fixed vocabulary: ItemLevelDiscount, Percent, TotalOrder, FreeItem, Bogof, BogofMixMatch, StampCard and Notification.
Open a partner and the menu names itself. Beside a menu version string sits a store record with the trading and legal name, a colophon with legal representative, registered address, chamber of commerce number and VAT number, an allergen phone number, an alcohol licence id, halal and certified-pharmacy flags, a storefront type of Restaurant or Grocery, an energy-units setting, cuisine types with numeric ids and slugs, and opening times per service type and weekday as local from and to strings. The menu proper is categories carrying item ids, items carrying variations, and modifiers hanging off them. A variation has its own id, a size name such as (25cm) Medium or (35cm) Large, a base price, a deal-only flag and an energy line in kilojoules and kilocalories. Modifier groups declare minimum and maximum choices, which separates a required crust choice from an optional topping list, and each option has an addition price and a removal price. To extract Just Eat data cleanly, keep the variation id, the modifier group id and the option id: one dish name repeats across sizes and branches.
The Food Hygiene Rating is a field of its own on Just Eat, and it is not the star rating. Stars and review counts come from customers; the hygiene score comes from the regulator, and a dedicated badge service is wired for Britain alone. The filter is labelled Hygiene Rating 3+ / Pass, and that wording is exact: England, Wales and Northern Ireland publish a number from 0 to 5, while Scotland publishes a pass or improvement-required verdict, so one column has to hold both shapes. It sits on every British listing, from the City of London to a one-partner postcode on Skye.
Groceries are a second storefront type, not a cuisine in disguise. The store record declares itself Grocery rather than Restaurant, the layout switches to a grid showing one aisle at a time, and the payload is deliberately truncated: an Amsterdam SPAR carried about 3,856 item ids across fifty aisles with five hundred preloaded and the rest in a sibling items file, plus manifests for Dutch, German and English. A Just Eat data pull that stops at the first payload quietly misses most of a supermarket.
The British cuisine vocabulary is wider than food. Next to pizza, kebabs, peri-peri and roast-dinners sit groceries, convenience, alcohol, allnightalcohol, pharmacy, shops, flowers, gifts, electronics and health-and-beauty, which is how Boots, Superdrug, Co-op, Asda Express and CeX end up in the same listing as a kebab shop. Merchandising rides in the same arrays: deals, freebies and stampcard-restaurants are stored as cuisines, and the filter map mixes about 136 cuisine slugs with more than a thousand campaign keys such as 10-off-indies-jan.
Just Eat is the British face of Just Eat Takeaway.com, and just-eat.co.uk is one window onto a shared platform. The group's markets page currently names fifteen trading countries: United Kingdom, Germany, Canada, the Netherlands, Austria, Belgium, Bulgaria, Ireland, Israel, Italy, Luxembourg, Poland, Slovakia, Spain and Switzerland. One brand per country is stated policy, so the same engine answers as Just Eat in Britain, Ireland, Italy, Spain and Switzerland, as Lieferando in Germany and Austria, Thuisbezorgd.nl in the Netherlands, Pyszne.pl in Poland, Bistro.sk in Slovakia, Takeaway.com in Belgium, Luxembourg and Bulgaria, 10bis in Israel and SkipTheDishes in Canada.
Domains and brands do not line up. just-eat.fr serves a Takeaway.com-branded French shop, the footer switcher still offers a Danish Just Eat whose domain returns no catalogue, and the group has said it will stop delivering in Bulgaria on 15 September 2026, so the map currently moves. A target list copied from an old country table burns budget on storefronts that have closed, so we rebuild it from the live switcher before every Just Eat scraping run.
One consumer application renders all of them, so a Just Eat scraper written against Lieferando reads Pyszne.pl and Thuisbezorgd.nl with no new parsing rules: same field names, same page shapes, different currency and language. Only the wiring differs: a Food Standards Agency badge service is configured for Britain alone. Language follows the visitor rather than the domain, so Thuisbezorgd.nl replies in German to a German browser and in Dutch to a Dutch one, and even the listing path is translated - delivery, lieferservice, bestellen, na-dowoz, livraison, a-domicilio, entrega - always followed by postcode and town.
Get a Quote
Developers
Customers worldwide
Pages extracted
Hours saved for our clients
€199 / one-time
setup fee - included
€169 / mo
setup fee €499
€229 / mo
setup fee €499
€349 / mo
setup fee €499
€549 / mo
setup fee €799
The Just Eat catalogue answers to a postcode, and the outward code is the key. The listing response echoes that district back and calls it the delivery area, so EC1V, SW1A, M1, BT1 and CF10 are five separate catalogues rather than five views of one. About 2,125 partners answered for a Finsbury postcode and about 1,313 for Westminster three kilometres away, yet only 314 ids appeared in both lists. Of that overlap, 221 partners quoted a different delivery cost from the two points and 102 quoted a different delivery estimate: one Krispy Kreme read 4.09 and sixty minutes from the first point, 1.39 and fifty-five from the second.
Scale runs the other way too. Manchester M1 returned about 1,098 partners, Belfast 546 and Cardiff 517, while a Portree postcode on Skye returned exactly one. Covering Britain city by city is the wrong unit of work; a Just Eat price monitoring programme is planned as a list of postcodes, and a row means nothing without the postcode and capture time stamped on it.
Time matters as much as place. At one moment in the City of London about 606 of 2,125 partners were flagged temporarily offline and 842 were shut for delivery, which is trading hours rather than a broken crawl. The merchandising rails shift as well: a London postcode was served a delivery-under-one-pound rail, Manchester a different low-fee rail and Belfast a healthy-choices rail. The platform also makes a claim worth auditing: its price guarantee promises the same price whether you eat in the restaurant or order at home, and only item-level collection can test it.
Learn how to use web scraping to solve data problems for your organization
Leveraging advances in technology, the AI-powered web scraper has skyrocketed in demand and is helping to expand capabilities by automating tedious daily tasks and speeding up data collection from thousands of websites several times over.
Web scraping is a method of obtaining web data by extracting it from pages of web resources with the help of a program, that is, in automatic mode. It is used to syntactically convert web pages into more usable forms.
If you specialize in machine learning, you need to feed large amounts of data to the algorithms. Web scraping is the easiest and the most efficient method of collecting the data from all over the Internet.
ScrapeIt is a managed web scraping agency. We are not a library and not a self-serve tool: we build the crawler, run it on your schedule, monitor it and repair it when a page changes, so what you keep is a feed rather than a codebase. A sample lands before sign-off, which lets you check base prices, modifier trees and hygiene ratings against live Just Eat pages yourself. Every row carries the postcode and the capture time behind it, so successive deliveries stack into one series. We have no affiliation with Just Eat or with Just Eat Takeaway.com.
No. Just Eat publishes no data API for outside buyers. The developer side of the group faces merchants and till vendors instead: a partner centre for restaurants and integration documentation for point-of-sale middleware, which push that partner's own menu, stock, prices and orders into the platform and pull its own orders back. None of it returns another partner's catalogue, and the storefront's own menu routes refuse an unauthenticated caller outright. A buyer who wants Just Eat menu data for a whole city has nothing to call, which is why the feed has to be built from public pages.
The live ones. Just Eat itself in the United Kingdom, Ireland, Italy, Spain and Switzerland; Lieferando in Germany and Austria; Thuisbezorgd.nl in the Netherlands; Pyszne.pl in Poland; Bistro.sk in Slovakia; Takeaway.com in Belgium and Luxembourg; 10bis in Israel; SkipTheDishes in Canada. Because one application serves all of them, the schema is identical everywhere and only currency, language and local rules change. Bulgaria is being wound down and a Danish domain still listed in the footer switcher no longer serves a catalogue, so we check the list before each run rather than trusting it.
Yes, and it is the single most important thing to plan for. The listing is built for a postcode district and the response names that district as the delivery area. Two central London postcodes about three kilometres apart shared only 314 partners out of roughly two thousand each, and most of those shared partners quoted different delivery fees and different delivery estimates from the two points. Availability moves through the day as well, so we stamp the postcode and the capture time on every row and treat a partner as a set of postcode-specific records rather than one record.
Cadence follows the question. Store attributes, menu structure and hygiene ratings are steady enough for a daily or weekly pass; item prices, fee bands and offers deserve a daily run; availability, open-now state and delivery estimates change through the day, so those are collected hourly or on a schedule tied to trading hours. Output comes as CSV, JSON, XLSX, a Google Sheet, a direct database load or an endpoint we host, pushed over email, S3, SFTP or webhook. Full snapshots and change-only deltas are both available, keyed on restaurant id, item id and variation id.
We work on public pages only: no login, no basket, no checkout, no payment. The paths the group's robots file closes - account, order history, checkout and internal service routes - are left alone, along with the filter query strings it asks crawlers to skip, and request rates stay polite. Reviewer names, courier names and any other personal data are left out by default; what we take is menu, price, fee, availability, cuisine, hygiene rating and store attributes, which are facts about the trade. Legal advice for your own use case remains yours to take.
Step 1 - Make a Request
You share your needs, expectations, and desired timeframe. We’ll suggest the best solution based on your request and budget.
Step 2 - Configuring Custom Web Crawlers
Our specialists configure the crawlers and extract a sample dataset for your review before proceeding with the full-scale extraction.
Step 3 - Collect and Deliver
Once you approve the sample, we launch the project and start full data collection. We gather, filter, and structure the data for easy use, delivering it on time in your preferred format.
Step 4 - Maintain and Support
Our team manages ongoing processes, monitors website changes, and supports all data extraction cycles. We can also help integrate data into your systems or create dashboards to simplify analysis.
Scrapeit Sp. z o.o.
10/208 Legionowa str., 15-099, Bialystok, Poland
NIP: 5423457175
REGON: 523384582
