Google Looker Studio is free, runs in a browser, 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.
The reality is more complicated. Looker 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 Looker Studio actually requires for a multi-location restaurant chain, what it does well, and when a purpose-built operations platform is the faster and cheaper path.
What Looker Studio actually is
Looker Studio (formerly Google Data Studio) is a data visualization tool. 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 Looker 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.
The native data connectors Looker Studio ships with cover Google products (Sheets, Analytics, Ads, BigQuery) and a curated list of marketing and advertising tools. A restaurant POS like iiko, Poster, or R-Keeper is not on that list. Neither is SmartBill, Oblio, or any accounting system used by mid-market operators in EMEA.
Looker 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 Looker 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 Looker 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 Looker 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 Looker Studio report
Once the data model is working, the actual Looker 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 Looker Studio setup of this complexity is typically €800–€3,000/year.
Direct comparison: Looker Studio vs. marql for restaurant operations
The "free" Looker 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 Looker 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: €149/month × 12 = €1,788 with zero setup fee and no maintenance cost. The free tool ends up costing more than the paid one.
When Looker Studio does make sense for a restaurant chain
Looker 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, Looker 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 connects to iiko, Poster, R-Keeper, and Lightspeed for POS data — 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.
The first daily operational view across all locations is live within 72 hours of the first call. Pricing starts at €49/month for chains with up to 4 locations. No setup fee, no data engineering, no ongoing maintenance cost.
If you've already tried the Looker 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.