Shopify to Data Studio: how to connect your store, what it costs and why the sales numbers never match

Can you connect Shopify to Data Studio for free?

Yes, with trade-offs. The free routes are a vendor's free plan for a single store, Google's BigQuery transfer while it is in Preview, or exporting CSVs from Shopify admin and uploading them to a Google Sheet. What you give up is refresh frequency, history, object coverage, or someone's time every week.

Data Studio's native connectors cover Google products and a set of databases: GA4, Google Ads, Search Console, Sheets, BigQuery, YouTube, Campaign Manager 360, Display and Video 360, Ad Manager, Cloud SQL, MySQL, PostgreSQL, SQL Server and Redshift. Shopify is not on that list, and the April 2026 rename from Looker Studio back to Data Studio did not add it. Every Shopify route therefore goes through a partner connector or lands the data somewhere Data Studio already reads.

The free options I checked on the vendors' own pages in October 2026: Windsor.ai keeps a forever free plan limited to 1 user, 1 data source and 1 account, after a 30-day trial with a 30-day history limit. Google's documentation for its Shopify transfer states there is no cost to transfer Shopify data into BigQuery while the feature is in Preview, though BigQuery storage and queries are billed as usual once you pass the free tier. Coupler.io offers a free trial but no permanent free plan.

What are the four ways to get Shopify data into Data Studio?

Each route trades setup speed against freshness, cost and control over how orders, refunds and line items are modelled. Pick based on order volume, how far back you report, and whether Shopify must sit beside ad spend in the same table.

A partner connector sits in the Data Studio connector gallery and queries Shopify, or the vendor's copy of it, when a chart loads. A Sheets route writes Shopify records into a Google Sheet on a schedule, and Data Studio reads the sheet through the native Sheets connector. A BigQuery route loads Shopify objects into tables, either with Google's own transfer service or an ETL vendor, and Data Studio reads views on top. A CSV route means exporting orders from Shopify admin by hand.

How much does a Shopify connector for Data Studio cost?

Entry prices run from free to about $32 a month, and costs climb with the number of stores, ad accounts and refresh frequency. The figures below come from each vendor's own pricing page, read in October 2026. Vendors change prices often, so confirm before you buy.

Several well-known vendors, including CData, Improvado and Dataslayer, do not publish a Shopify-specific price on their connector pages; Dataslayer advertises a 15-day free trial. Price the plan you will need in six months, not the entry tier. Count your stores, the ad platforms that belong in the same report, and how fresh the numbers must be. A team that reviews trading every Monday does not need a 15-minute refresh.

What is Google's Shopify transfer to BigQuery, and should you use it?

It is a Shopify connector inside BigQuery Data Transfer Service that loads your store's data into BigQuery on a schedule, and it costs nothing to transfer while it remains in Preview. For a store that already has, or is willing to open, a Google Cloud project, it is now the cheapest way to get full Shopify order history into a warehouse Data Studio reads natively.

According to Google Cloud's documentation (last updated October 19, 2026), the transfer authenticates through a custom Shopify app using its client ID and client secret, or an Admin API access token when set up from the command line. Each object needs the matching read scope, such as read_orders for orders, read_products for products and read_customers for customers. You can run it hourly, daily, weekly, monthly, on a custom interval or on demand. A few objects carry extra conditions: gift cards require Shopify Plus. Preview features fall under Google's Pre-GA Offerings Terms, with support through a preview mailbox rather than standard Cloud support.

My view: use it for new builds where you want history, cohorts and joins with ad spend, but treat it as Preview. Create the custom app from a store owner or staff account the business controls, check the transfer run history for the first few weeks, and never point a board report at raw transfer tables. Build a modelled view on top (one row per order with net sales, discounts, refunds, shipping and tax as separate columns), partition large tables by date, and connect Data Studio to the view. If Google changes the schema when the connector leaves Preview, you fix one view, not every chart.

Why don't Shopify sales in Data Studio match Shopify's own reports?

Usually because the two are measuring different things, not because the connector is broken. Shopify's sales reports follow a specific set of definitions and book returns on the day the return happens, while most connector tables are organised around orders. A Shopify Community thread about a Supermetrics Shopify connector showing "a significant difference in total sales" was never resolved in the thread, and the causes below explain most gaps like it.

Start with Shopify's own definitions, from its Help Center: gross sales are product price times quantity, before taxes, shipping, discounts and returns. Net sales are gross sales minus discounts minus returns. Total sales are net sales plus taxes and shipping. Returns show as a negative number on the date the return was created, not on the original order date.

A worked example shows the effect. Say an order is placed on September 28 for $200 of product with a $20 discount, and $50 is refunded on October 3. Shopify's sales report shows September net sales of $180 and October returns of minus $50. A connector table filtered by order date that subtracts refunds from the order shows September at $130 and nothing in October. Both are correct; they answer different questions. Pick one definition, label it on the dashboard, and reconcile against the Shopify report that uses the same definition.

Work through these causes in order before blaming the vendor.

• Returns timing: Shopify reports book returns on the return date; order-based tables attach them to the order date.
• Net vs total sales: a scorecard labelled revenue may include tax and shipping in one tool and exclude them in the other.
• Time zone: Shopify reports use the store's time zone, while connector timestamps are often UTC, so orders near midnight land on different days.
• Test, cancelled and draft orders: some connectors include them unless you filter on order status and the test flag.
• Line items vs orders: summing a line-item table's order total multiplies it by the number of products in the order.
• Multi-currency: stores selling in several currencies need the shop-currency amount field, not the presentment currency.
• GA4 vs Shopify: GA4 purchase revenue depends on tracking and consent, so treat Shopify as the financial record and GA4 as behaviour.

Do Shopify API limits affect a Data Studio report?

They can, on large stores using a live connector. Shopify's GraphQL Admin API limits apps by calculated query cost rather than request count, using a leaky bucket that refills continuously. Sheets and BigQuery routes avoid the problem because Data Studio reads the copy, not Shopify.

Shopify's developer documentation lists restore rates of 100 points per second on standard plans, 200 on Advanced Shopify, 1,000 on Shopify Plus and 2,000 on Shopify for enterprise, with any single query capped at 1,000 points. Shopify's bulk operations, built for large data pulls such as order history, are not subject to those per-query limits. A live connector pulling two years of line items each time a chart loads is the pattern that hits the limit.

If charts time out or return partial data, cut live load first: raise the data freshness interval on the data source, remove duplicate charts that request the same fields, and move busy reports to a Sheet or BigQuery. If GA4 sits on the same dashboard, it has its own quota of 14,000 tokens per project per property per hour, and quota errors there are often mistaken for a Shopify problem.

What should a Shopify dashboard in Data Studio include?

Build it around the decisions you make each week: is trading on plan, which channels bring profitable customers, and which products need stock or attention. A good first version fits on three pages.

Page one is trading: net sales, orders, average order value, discounts and returns by day and week, against last year and target, with a store filter if you run more than one. Page two is acquisition: sessions, conversion rate and revenue by channel from GA4, beside Google Ads and Meta spend so cost per order and return on ad spend are visible, plus new versus returning customers. Page three is products: units and net sales by product and variant, return rate by product, and a sortable table that a buyer can export.

Use a calculated field with a CASE statement to group raw sales channels and UTM sources into the five or six labels your team uses, and a date range control that defaults to the last complete week. Blends are limited to 5 sources and equality joins only, so for cost per order across Shopify, Google Ads and Meta, build one table by date and campaign in BigQuery or a Sheet rather than stacking blends. Projects I've led at Greenwolf Tech Labs include a retail dashboard covering MoM and QoQ revenue growth, conversion rate, sell-through rate, cart abandonment against forecast, and online versus in-store sales.

How do you connect Shopify to Data Studio step by step?

The clicks take minutes. The steps that prevent trouble later are about ownership, definitions and testing, so they are included here.

Data Studio data sources run on the owner's credentials by default, so viewers see Shopify data without a Shopify staff account. That is useful, but if the connecting login belongs to a contractor or someone who leaves, every chart breaks when their access goes, and Data Studio gives no warning when a connector stops working.

• Agree the numbers: list the five or six figures leadership reviews and define each, for example net sales by order date in shop currency, excluding tax and shipping.
• Choose the route: a partner connector for one store and quick wins, BigQuery for history and ad joins, Sheets for a small store on a budget.
• Use a business-owned login or custom app, never a personal or freelancer account.
• Pull only what you need: orders, line items, refunds, products and customers, not every object and metafield.
• Model one row per order and one row per line item as separate tables, with refunds as their own columns.
• Reconcile: compare last month's net sales and order count against the Shopify sales report with the same definition, time zone and filters.
• Share the report, not the data source, and schedule an email delivery for the weekly trading meeting.

When is Shopify to Data Studio not worth it?

If Shopify is your only real source and the team already lives in Shopify admin, its built-in reports may be enough. Moving data out adds a connector, a data model and something to maintain, so do it for a reason.

Good reasons: you need Shopify beside Google Ads, Meta, GA4 or finance data in one place; people who need the numbers should not have admin access; you run several stores and want one view; or you need cohorts and history that Shopify reports cannot hold the way you want. Weak reasons: a nicer chart style, or rebuilding a Shopify report that already works.

Do it yourself if you have one store, a free or entry connector and someone comfortable in Data Studio; an afternoon is the right spend. Bring in help when totals do not match Shopify, when several stores or currencies are involved, or when the report must keep working after the person who built it moves on.

How I handle Shopify to Data Studio projects

I start with a free review of your store setup, the questions the report must answer and any dashboards you already have. I recommend the cheapest route that will hold up, often a connector you already pay for or Google's BigQuery transfer, and quote a fixed price for the build.

The work covers the data model (orders, line items, refunds, currencies and time zone), the dashboard, reconciliation against Shopify's own sales report, and a handover so your team can add fields and pages without me. Everything lives in your Google and Shopify accounts from day one, so nothing depends on my logins.