Tazz Scraper for Romanian Restaurant Menus and Fees

Romania is not one delivery market. Bucharest prices and Cluj prices diverge enough that a national average describes neither city.

Plans from €169 a month · Free project assessment · Reply within 1 business day

CSV · Excel · JSON · XML · FTP · SFTP · Amazon S3 · Google Cloud

tazz.ro
Tazz Scraper for Romanian Restaurant Menus and Fees
tazz.rowhat you get
Typical fields for food delivery apps
restaurantdishpricedelivery_feeeta_minrating
Delivery

API, JSON feed or CSV, XLSX and JSON files

Schedule

One-time, monthly, weekly, daily or 3 times a day

Managed delivery data, run end to end by us

  1. You send

    Tazz pages, filters, fields and a schedule

  2. We run the scrapers

    Built, monitored and repaired by our team

  3. You receive the data

    API, JSON feed or CSV, XLSX and JSON files

ScrapeIt runs the collection as a managed service. You name the cities and verticals; we build the pipeline with option surcharges as their own rows, city and vertical as fields, fees on the venue record, and hand back CSV, JSON, Excel or a push into your warehouse.

Cadence is set against what you are watching - menu structure moves slowly, prices and fees daily, promotions within the day - rather than one schedule that suits none of them.

We collect public catalogue data only and pace requests as part of the service. No courier data, no customer data, no account access. Everything we deliver is publicly available - what any visitor can see on Tazz - and we collect it legally.

Tazz fields in every export

Venue records carry the venue name, category, city, address, rating, delivery fee, minimum order, estimated delivery time and open state.

Menu records are keyed to the venue: section, item name, description, price in lei, and the option groups with their own surcharges. Options are separate rows rather than folded into the price, because an item with a mandatory size choice is not the price its base row shows.

City is a first class field rather than something inferred later. It is the axis the platform is built on and the axis on which Romanian delivery pricing actually varies.

Vertical is recorded per venue - restaurant, grocery, pharmacy, retail - so a client analysing restaurant pricing does not silently include a supermarket's catalogue in the average.

Every row carries the collection timestamp and the currency, since prices are in lei and a series spanning any length of time needs both.

Tazz fields in every export
City comparison, promotions and scope

City comparison, promotions and scope

City comparison is the most immediately useful output: the same chain priced across Romanian cities, with delivery fees on the row, which for a brand operating nationally is a direct read on where its franchisees or partners are pricing differently.

Promotion tracking needs a cadence matched to promotions rather than to convenience, as on any delivery platform. A discount that ran over a lunch service is invisible to a nightly crawl.

Venue coverage mapping answers which categories are thin in which cities, which is an expansion question and runs off the venue list alone without any menu collection.

What stays out of scope is people: no courier data, no customer accounts, no order histories. We never sign in, so account pages stay out of the crawl.

A city-organised delivery platform in Romania

Source
tazz.ro
Category
food delivery apps
Delivery
API, JSON feed, CSV, XLSX
Plans
From €169 a month
Get a quote

Tazz is one of Romania's largest delivery platforms, carrying restaurants, groceries, pharmacies and retail across the country's major cities. It is part of the eMAG group, which is the dominant e-commerce operator in the region.

The catalogue is organised by city, and city pages respond directly with a great deal of content. That structure matters because Romanian delivery pricing varies substantially between the capital and the regional cities, and the venue base differs even more.

Like most platforms of this kind it carries several verticals side by side, and they are different data - a restaurant menu has sections and options, a grocery listing has brands and pack sizes, a pharmacy listing has its own rules. Typing them separately is the first design decision.

Everything a visitor sees on a venue page can be collected: name, category, address, rating, delivery fee, minimum order, estimated delivery time, open state and the full menu with its option surcharges.

25Developers
500+Customers
1.5BPages extracted
15,000+Hours saved for our clients

Tazz scraping plans and pricing

Airplane

€199one-time

Setup fee included

100,000
One-time
Up to 5 days
7 days

Helicopter

€169/ mo

Setup fee €499

250,000
Monthly
Up to 5 days
14 days

Glasses

€229/ mo

Setup fee €499

1,000,000
Weekly
Up to 5 days
30 days

Microscope popular

€349/ mo

Setup fee €499

2,000,000
Daily
Same day
60 days

DNA

€549/ mo

Setup fee €799

3,000,000
3 times daily
Same day
90 days

Delivery: CSV, JSON or XLSX files, our API or a JSON feed. MCP server on request.

Full plan details

Why a smaller market needs the same discipline

Romanian delivery data gets treated as a simpler version of a Western European brief, and it is not - it has the same structural traps with less published analysis to catch mistakes.

City variation is the first. Bucharest has a venue base and a price level that the regional cities do not, and a national aggregate is dominated by the capital while describing nowhere. Collecting city as a field costs nothing and is the difference between a usable dataset and an average.

Option surcharges are the second, and they behave here as everywhere: a base price with a mandatory choice attached is not the price a customer pays. Flattening them produces a price index that is wrong by a consistent margin in whichever direction the flattening chose.

The third is vertical mixing. A platform carrying restaurants and supermarkets in one interface will, if collected naively, put a kilo of potatoes and a restaurant main course in the same price column. Typing per vertical is what keeps aggregates honest.

The fourth is that this is one platform in a market with others. It is a large slice of Romanian online delivery and it is not the Romanian food market, most of which is still offline, and we describe it that way.

Who builds and keeps your Tazz feed

ScrapeIt is a managed extraction company, not a tool you have to learn. Our team builds the pipeline, watches it as city coverage and menu templates change, and repairs it before a price series develops a gap.

You see a sample first, in your format, over the cities you actually trade in, with options expanded and fees on the row so you can judge the comparison on real venues.

FAQ

Still unsure? Write to info@scrapeit.io

Can I get a national Romanian price level?

You can, and it will be dominated by Bucharest while describing nowhere in particular. City is a field on every row precisely so you can aggregate deliberately rather than inherit the capital's weight by accident.

How are menu options handled?

As separate rows with their surcharges. An item with a mandatory size choice is not the price its base row shows, and flattening them gives a price index that is wrong by a consistent margin in whichever direction the flattening went.

Does the grocery side mix with restaurants?

Not in our output - vertical is recorded per venue. Collected naively, a kilo of potatoes and a restaurant main course end up in the same price column, which quietly ruins every aggregate built on it.

Is this the Romanian food market?

No. It is a large slice of Romanian online delivery. Most of the market is still offline with different pricing, and we describe the dataset as what it is rather than letting one platform stand in for a country.

Do you collect courier or customer data?

No. We never sign in, so account pages and anything behind them stay out of the crawl. Venue, menu, price, fee and availability data is what these projects need and it contains none of that.

How it works

  1. 1

    Make a request

    You share your needs, expectations, and desired timeframe. We'll suggest the best solution based on your request and budget.

  2. 2

    We configure the crawlers

    Our specialists configure the crawlers and extract a sample dataset for your review before proceeding with the full-scale extraction.

  3. 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.

  4. 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.

Request a quote

Tell us which sites, which fields and how often. A couple of lines is enough to start.

  • We reply within 1 business day
  • A sample dataset before the full run
  • We sign an NDA on request
  • Delivery by API, JSON feed or files
Which sites, which fields, how often. A couple of lines is enough.

This form is protected by Google reCAPTCHA, which loads when you start filling it in. If you prefer not to use it, email us at info@scrapeit.io. Privacy & Cookie Policy

We reply within 1 business day. No obligation.

Tazz data from €169/month. Free project assessment, reply within 1 business day.