marql

Compare · Data Studio

Data Studio (Looker Studio) for restaurant chains: what it can and can't do

Maksim Tronin, CMO, marql · May 29, 2026 · Reading time: ~7 min

Google Data Studio (formerly Looker Studio) runs in a browser, costs nothing on its standard tier, and looks like exactly what a restaurant chain needs: a drag-and-drop reporting tool that connects to data sources and produces dashboards. When you're managing five locations and getting daily reports via WhatsApp, "free BI tool" sounds like a solution.

One correction before the rest of the page, because it changes the arithmetic for a company rather than an individual. Free applies to the standard tier. Data Studio Pro is billed per user per Google Cloud project, and Pro is where you end up if you want reports owned by the business instead of by the person who built them, or Google Cloud Customer Care when something breaks (which also needs a Google Cloud support plan). The licence rules are in Google’s Data Studio Pro subscription guide, which links to the current rate (checked on 2 November 2026). The per-project billing is what surprises people: separate projects multiply the bill even when the headcount does not.

The reality is more complicated. Data Studio is free the same way a plot of land is free: you still have to build the house. For a restaurant chain, "building the house" means connecting your POS system, structuring the data, defining your metrics, and maintaining all of it when anything changes. None of that is free, and for most operators it takes months, not days.

This is an honest breakdown of what Data Studio actually requires for a multi-location restaurant chain, what it does well, and when a purpose-built operations platform is the faster path.


What Data Studio actually is

Data Studio is a data visualization tool. Google called it Looker Studio until April 2026, when the product went back to its original name, and existing reports carried over with nothing to update. It takes data from connected sources and turns it into charts, tables, and dashboards. It does this well and at no cost for the tool itself.

What Data Studio is not: a data integration tool, a data transformation layer, or a retail operations platform. It doesn't connect to your POS, calculate gross margin from your supplier invoices, detect anomalies, or send morning briefings. Those capabilities require you to build the infrastructure that feeds it.

Google's own connectors for Data Studio cover its products (BigQuery, Sheets, Analytics, Ads), common databases such as MySQL, PostgreSQL and SQL Server, and Excel and CSV files. Other systems come in through third-party community connectors, or through an export into one of those sources. A restaurant POS like iiko, Poster, or R-Keeper is not in Google's catalogue. Neither is SmartBill, Oblio, or any accounting system used by mid-market operators in EMEA.

Data Studio is a great tool for visualizing data you already have structured somewhere. The challenge for restaurant chains is that the data isn't structured anywhere yet.


The real setup path for a restaurant chain

To get a working multi-location restaurant dashboard in Data Studio, the typical path for a 5-location chain with iiko and SmartBill looks like this:

Step 1: Get POS data out of iiko

iiko doesn't have a native Data Studio connector. Your options are a scheduled CSV export to Google Sheets (manual or via a script), a custom connector built by a developer, or an ETL pipeline into BigQuery. The Sheets route is doable in a few days but fragile: one format change in the export breaks everything. The BigQuery route is robust but requires a developer and typically 2–4 weeks.

Step 2: Get accounting data out of SmartBill

SmartBill has an API. A developer needs to write the extraction code, schedule the sync, handle authentication token refresh, and store the data somewhere Data Studio can read. Add another 1–2 weeks on top of the POS connector.

Step 3: Build the data model

Now you have POS data in one Sheets tab and accounting data in another. To calculate gross margin, you need to join them — map each POS sale to the relevant cost category, handle currency and timing differences between the invoice date and the sale date, and build the formula logic that gives you margin per location per day. This is the hardest part, and it's what most operators underestimate when they start.

Step 4: Build the Data Studio report

Once the data model is working, the actual Data Studio build is the easy part: a few hours for a competent user. The problem is getting here typically takes 6–12 weeks and €4,000–€12,000 in development work.

Step 5: Maintain it

When iiko updates its export format, the Sheets pipeline breaks. When you add a sixth location, the data model needs updating. When SmartBill changes its API authentication, the sync stops. Ongoing maintenance for a Data Studio setup of this complexity is typically €800–€3,000/year.


Direct comparison: Data Studio vs. marql for restaurant operations

Feature
Data Studio
marql
Time to first dashboard
3–16 weeks (depending on POS connector)
Connected on the first call, then no build phase
POS connection
Custom connector or Sheets export required
49 POS systems live — no development
Gross margin auto-calculation
Manual formula / SQL required
Automatic from day 1
Cross-location benchmarking
Build it yourself in the data model
Built-in
Anomaly detection
Not included
Automatic daily alerts
Requires developer / data work
Yes — for POS connector + data model
No
Licensing cost
Free tier, or Pro billed per user per Google Cloud project
€1,000/month for 5 locations, all in
Real year-one cost (5 locations)
€3,000–€15,000 (setup + maintenance)
€12,000 (no setup fee)

Ranges, not quotes — the cost figures above are ranges we assembled from vendor list prices and the integration work these stacks need. They are not quotes, not vendor offers, and not measured from customer projects. Your own stack decides where you land inside them, and marql's own price is the only figure here we can state exactly.


The "free" Data Studio cost breakdown for a 5-location chain

The application costs nothing. Here's what the infrastructure to make it useful actually costs for a 5-location restaurant chain:

  • POS connector development (iiko / Poster). €1,500–€5,000 for a developer to build a reliable export pipeline into Google Sheets or BigQuery. This varies significantly with POS API quality.
  • Accounting connector (SmartBill / Oblio). €500–€2,000 to extract supplier invoice data on a schedule and keep it aligned with POS data for margin calculation.
  • Data model and Data Studio report build. €1,000–€3,000 for the gross margin calculation logic, cross-location aggregation, and report layout.
  • Ongoing maintenance. €800–€3,000/year for API changes, new locations, and data model adjustments.

Total year-one cost: €3,800–€13,000.

The equivalent on a purpose-built platform for the same 5 locations: €1,000/month × 12 = €12,000, with zero setup fee, no developer, and nothing to maintain. That is more than the cheapest possible Data Studio build and about level with a realistic one. The difference is that nobody on your team builds it, and nobody has to keep it running when a POS changes its export.


When Data Studio does make sense for a restaurant chain

Data Studio is genuinely useful in specific scenarios:

  • You already have structured data in Google Sheets or BigQuery and just need a visualization layer on top.
  • You have an in-house developer or a contracted data engineer to build and maintain the pipeline.
  • You need custom reporting across many data sources beyond operations — marketing, HR, customer data — that a purpose-built tool doesn't cover.
  • You're operating a single location and your data is simple enough to manage with Sheets-based exports.

For chains with 3–20 locations that need daily gross margin per location this week, not in three months, Data Studio is not the right path. The setup cost and timeline exceeds the tool cost of a purpose-built platform within the first year, and the maintenance overhead compounds after that.


Getting daily restaurant reporting without the build

marql reads 49 POS systems today, from iiko and Poster to Square, Lightspeed and WizPOS — and to SmartBill, Oblio, QuickBooks, and Xero for accounting — without any custom development. See all supported integrations. The gross margin calculation, cross-location benchmarking, and anomaly detection come pre-configured.

Pricing starts at €200/month per location. No setup fee, no data engineering, no ongoing maintenance cost.

If you've already tried the Data Studio route and hit the data pipeline complexity, or you're deciding between building vs buying before starting, the full retail analytics software comparison covers all five approaches — spreadsheets, POS reports, BI tools, ERP, and purpose-built platforms — with real costs and timelines side by side. For the Power BI equivalent of this comparison, the Power BI vs marql breakdown follows the same structure.

Frequently asked questions

Data Studio for restaurant chains

Not natively. Google's own Data Studio connectors cover its products such as Sheets and BigQuery, common SQL databases, and Excel and CSV files, and no POS is among them. To connect to a POS system like iiko or Poster, you need either a custom Data Studio connector (built by a developer), a middle layer that exports POS data to Google Sheets on a schedule, or a data pipeline into BigQuery. None of these are zero-effort for a multi-location chain.

The standard tier is free to use. Data Studio Pro is not: it is billed per user per Google Cloud project, and it is the tier you land on if you want the reports owned by the company rather than by whoever built them, plus Google support. Check the current rate on Google's own pricing page. Either way the licence is not where the money goes for a restaurant chain. The cost is the infrastructure to feed it: someone builds the POS connectors, someone runs the scheduled export or ETL pipeline, and someone fixes it when a POS changes its API, which for a 5-location chain typically runs to €3,000–€10,000 up front plus ongoing maintenance. Ranges for the work, not quotes.

No. Data Studio is a visualization layer: it shows data you connect and structure. Automatic gross margin requires linking POS sales data with supplier invoice data and building the calculation yourself. This needs to be defined in your data model (Google Sheets formula, BigQuery SQL, or Data Studio calculated field) and maintained when either source changes.

A basic multi-location Data Studio dashboard (revenue by location, comparison over time) takes 3–8 weeks when you include setting up the POS data export, cleaning and structuring the data, and building the report. A dashboard that includes gross margin calculation from supplier invoices typically takes 8–16 weeks and requires BigQuery or a similar data warehouse.

Data Studio makes sense when you already have structured data somewhere (Google Sheets, BigQuery, a database), have someone who can build and maintain the reports, and need custom visualizations that a purpose-built tool doesn't offer. If you need daily gross margin per location starting this week, a purpose-built platform is faster and cheaper.