One Glovo city page opens six tiles and only the first is food. We scrape Glovo menus, prices, fee lines and darkstore shelves across three continents and hand you the feed.
ScrapeIt runs Glovo scraping as a managed service. You name the countries, cities and categories; we build the crawl, keep it alive when the markup shifts, and deliver CSV, JSON, Parquet or a hosted Glovo API endpoint on whatever cadence the question needs - hourly for a promotion watch, daily for price monitoring, weekly for coverage mapping.
Menus render in the browser and stores gate themselves by delivery zone, so getting a clean read is part of the job rather than an extra line on the invoice: anti-bot handling, proxy rotation and CAPTCHA solving are included, with exits in the right country so a Kazakh store answers with Kazakh prices and a Polish store with zloty. We work public pages only - no accounts, no logins, no baskets, no checkout. Personal data stays out of the export: we do not take reviewer names, courier names or anything that identifies a person.
A Glovo store page is a header stacked on a long menu, and we extract Glovo store data field by field:
Two things about a Glovo price deserve saying plainly. The crossed-out figure is not the everyday price: the platform labels it as the lowest price in the 30 days before the reduction, which is the European reference-price rule, so a diff against it measures a legal baseline rather than the counter price. And the header fee is only the first line of the bill - a small-order fee lands when the basket sits under the merchant's minimum, and night orders can carry a service charge applied to each item instead of to the basket, set by city and by store.
Food is one tile of six. A Barcelona city page also opens Groceries, Shops, Pharmacy and Beauty, Package Delivery, and El Super de Glovo - and each of those is a catalogue in its own right.
The company also runs its own warehouses, and whose warehouse it is can be read from the outside: they trade as El Super de Glovo in Spain and as Glovo Market in Italy and Portugal, one per city and sometimes several - a night store in Milan, an express store beside it, a Nairobi branch under the same name. Their aisle tree runs three levels deep, from fresh produce down to a single yogurt type, and pack size is written into the product title rather than held in a field of its own, so grams and millilitres have to be parsed out. Package Delivery, the send-me-anything courier errand, has no web catalogue at all - it lives inside the app, and we say so rather than promise a feed that cannot exist.
Glovo began in Barcelona as a courier app for anything you could point at, and it still behaves that way: one order screen where a restaurant, a supermarket, a pharmacy, a florist and a phone shop sit next to each other. That breadth is what separates Glovo data from a purely restaurant marketplace - a city page opens on six tiles, and only the first of them is food.
The country picker lists 21 markets: Spain, Italy, Portugal, Poland, Romania, Ukraine, Moldova, Bulgaria, Croatia, Serbia, Montenegro, Georgia, Armenia, Kazakhstan, Kyrgyzstan, Morocco, Tunisia, Ivory Coast, Kenya, Nigeria and Uganda. Three continents on one codebase, with prices in the local money of each - euro in Spain, Italy and Portugal, zloty in Poland, hryvnia in Ukraine, tenge in Kazakhstan, dirham in Morocco, shilling in Kenya and Uganda. The interface ships in 18 languages, Basque, Catalan, Georgian, Kazakh, Kyrgyz and Armenian among them, and the same store answers on 18 addresses because of it.
Addresses follow one grammar everywhere: language, country, city, then either a store or a category. A Glovo scraper written for Madrid runs in Tbilisi once the city slug is swapped. The engine is shared; the identifiers are not. Category numbers are handed out per market, so restaurants are category 1 in Spain and Italy and category 394 in Nairobi, and the cuisine filters are rewritten country by country - Jollof and Suya in Lagos, Laghman and Khachapuri in Almaty. Older country-first links survive in the sitemap and pass through a legacy handler, and a few of them still point at cities the company has left - so a coverage plan starts from the live country list, never from the sitemap alone.
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
Buyers come to Glovo data for four jobs, and each wants a different cut of the same crawl.
The subscription tier is the trap. A single tile can carry -50% some items for everyone and -55% with Prime at the same moment, and a store that charges walk-up users a delivery fee charges subscribers nothing. Any Glovo price series that folds those into one number will drift within weeks, so the member price and the public price stay in separate columns and you decide which one your model should follow.
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, not a tool vendor. We do not hand you a crawler and wish you luck against a defended marketplace - we run the job, watch it, and answer when a field changes shape. A named engineer owns your feed, a free sample from your own cities arrives before you pay for volume, and the schema is agreed in writing so nothing shifts quietly underneath your pipeline.
Tell us the markets and the fields you need, and a sample export comes back from the cities you actually sell in.
No. The only documented interface is the Glovo Partners API, and it points the other way: it serves merchants and point-of-sale vendors, credentials are issued on request by the integrations team, and it lets a partner receive its own orders, upload its own menu, edit its own items and close its own store temporarily. There is no read endpoint that returns another merchant's catalogue and no customer-facing feed of stores, dishes or fees. A buyer who wants Glovo menu data across a city gets it by collecting the public pages, which is exactly what we do.
All 21 markets on the country picker, from Spain and Italy through Poland, Romania, Ukraine and Georgia to Morocco, Tunisia, Ivory Coast, Kenya, Nigeria, Uganda, Kazakhstan and Kyrgyzstan. Coverage is quoted per city, because the catalogue is city-shaped: a chain is one store per city and one address per branch. Category listings hand out a slice of stores at a time, so a full city is assembled from category and sub-category cuts rather than from one endless list. Name the cities and we size the job against the store counts there.
As often as the question deserves. Promotion and availability work runs hourly or several times a day, because member deals and Closed until tomorrow states turn over quickly. Menu and price monitoring usually runs daily; store coverage and assortment mapping runs weekly. Delivery is CSV, JSON, JSONL or Parquet, dropped to S3, GCS, SFTP or straight into your warehouse, or served from an endpoint we host. Field names are fixed before the first run and versioned whenever they change.
Yes, and more sharply than on a national retailer. Every store draws a delivery zone, and a store page opened from outside that zone says so instead of showing the menu. Fees, promotions and the visible store list all follow the point the request is standing at, and the night surcharge is set per city and per store. So each crawl is pinned to a real address inside the zone and every row records which address produced it - without that, two runs of the same city are not comparable.
The robots file lets crawlers into the public catalogue and closes only embedded views, order-tracking share links and password recovery, and we respect those boundaries. The terms of use carry no explicit ban on automated collection, but they do reserve the platform's content against commercial reuse without written permission, so the legal read on what you publish from the data is a decision for you and your counsel. Our own rules are short: public pages only, no login, no orders, no checkout, and no personal data - reviewer names and courier names never reach the export.
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
