Skip to content
Adapters

Shopify to BigQuery integration tools compared on cost, refunds and duplicates

Google's own Shopify transfer is still a Preview feature that reloads all available data on every run, and BigQuery ignores the primary key you declare. The right tool loads refunds, lands money as exact decimals per currency, merges on the Shopify id and costs the same in a busy month as in a quiet one.

The live demo needs no card, and Starter is $49 a month.

Field mapping auto-plugged · tap a port to rewire

5 sample records ready

Vendor documentation read 21 November 2026

Which Shopify to BigQuery integration should you use?

If you want a first-party connector inside your own Google Cloud project and can accept Preview terms, pilot Google's Data Transfer Service Shopify connector and check whether a run merges or reloads. If you want a fixed monthly price, refunds loaded beside orders and every batch merged on the Shopify id, use a flat priced connector that backfills with a bulk export. CSV exports suit one analysis, not a model finance trusts at month end.

For Shopify on its own, with every API limit that governs an integration, see Shopify integration tools. For every other source into the same warehouse, see BigQuery ETL tools, and for what the warehouse bills, BigQuery pricing worked for a store.

What the Google and Shopify documentation say, and what a buyer assumes

We read the Data Transfer Service Shopify page and BigQuery's price list beside Shopify's rate limit documentation, and wrote down what each line costs a finance team. The last column is what we would do.

What is at stake What the docs say Why it matters What we would do
Google side The Data Transfer Service connector for Shopify is a Preview feature, read 21 November 2026. Preview features are provided as is and can have limited support. A Preview connector can change before it is generally available, and a finance close should not depend on terms that may move. Pilot it, do not close the books on it
Objects GraphQL based objects including orders, refunds, order transactions, customers, products, variants, inventory items, draft orders and metafields, each behind its own Shopify scope. You select objects and grant scopes one by one in a custom app. A missed scope gives an empty table, not a failed transfer. List the objects your report needs
Edge objects Gift cards need a Shopify Plus subscription. Discount code objects need an app created with the Shopify CLI. App subscription objects need a sales channel app. Three object families silently depend on the shape of the store or the app you built. Check each against your plan first
Refresh behavior The page says every transfer run transfers all available data from Shopify into BigQuery. It does not say whether a run merges on the Shopify id or appends. A schedule that reloads everything also grows with the store. Run twice and count rows per id
Types Decimal becomes NUMERIC, Long becomes BIGNUMERIC, Datetime becomes TIMESTAMP, Double becomes FLOAT64. Money may land as FLOAT64 if Shopify types the field as Double, and a rounding drift never raises an error. Check the amount columns on a sample
Cost and support No charge for the transfer in Preview, and support goes to a Preview support alias. Free in Preview is not a price you can budget. Storage and queries are billed as normal. Do the BigQuery sums below

The connector facts are on Google's Shopify transfer page and the limits come from Shopify's API rate limits documentation. The point arithmetic is worked through on Shopify API rate limits.

What BigQuery itself bills for Shopify tables, in dollars

Google's BigQuery pricing page lists on-demand queries at $6.25 per TiB scanned with the first TiB free each month, active logical storage at $0.000031507 per GiB hour (about $0.023 a month) with the first 10 GiB free, and batch loading free on the shared pool. Prices are the US multi-region list read on 21 November 2026 and vary by region. The table is our arithmetic on those rates.

Setup Monthly cost How we got it
10 GiB of Shopify tables $0.00 Inside the first 10 GiB free each month
50 GiB of Shopify tables $0.92 (50 - 10) x $0.023
500 GiB of Shopify tables $11.27 (500 - 10) x $0.023
Queries scanning 0.9 TiB a month $0.00 Inside the first free TiB
Queries scanning 3 TiB a month $12.50 (3 - 1) x $6.25 on demand

The point of the table is that BigQuery rarely dominates a merchant's bill. A wasteful query or a transfer that reloads everything on a tight schedule is what moves it. A full reload also multiplies the bytes your tools scan, which is why we partition the orders table by date. The same arithmetic for accounting data sits on the QuickBooks page. An Adapters plan is a fixed monthly price on pricing, whatever the order count.

Shopify to BigQuery connectors and integration tools compared

Billing units rather than price tags, because most vendors here meter or quote and any figure we printed would be stale within a quarter. Where a tool is the wrong fit, the last column says so, including for us.

Tool Approach Best for Billing unit Watch for
CSV exports and Shopify reports Download order and product exports and load them with a BigQuery load job by hand A one-off analysis or one closing snapshot No tool cost, paid in staff hours every month Exports are flat summaries and nobody owns the refresh
BigQuery Data Transfer Service First-party Preview connector over the Shopify GraphQL API, set up in the console or with bq Google Cloud teams comfortable with Preview software and a custom Shopify app No transfer charge in Preview, BigQuery storage and queries billed as usual Preview status, full reloads per run, scopes granted object by object
Fivetran Managed ELT with a Shopify connector writing tables into BigQuery Teams with a data engineer and many sources on the platform Metered by monthly active rows, confirm on the vendor pricing page Order edits touch old rows, so model your busiest month
Airbyte Open source or cloud ELT with a Shopify source connector Engineering teams comfortable running pipelines Self-hosted or usage-based cloud, confirm units with the vendor Self-hosting means you own retries and upgrades
Coupler.io and similar spreadsheet-first tools Scheduled export from Shopify to BigQuery with a visual setup Analysts who want a quick dataset at modest volume Tiered by plan, confirm limits with the vendor Check that refunds and transactions are included, not only orders
Workflow automation Trigger based tools inserting one BigQuery row per Shopify event A single alert or audit table, not a reporting model Billed per task, confirm on the vendor page No backfill, and order edits and refunds never update the first row
Adapters Visual mapping of Shopify objects onto typed BigQuery tables, bulk backfill, then merges on the Shopify id Merchants and finance teams that want exact money columns and a fixed monthly price Flat monthly plans from $49, no per-order or per-row fee Not a replacement for a full commerce analytics suite

Vendor billing units change, so confirm each one on the vendor's own page before you model a month. The same tools are compared more broadly on the best data integration tools.

Six facts worth knowing before you choose

Preview

Status of the BigQuery Data Transfer Service connector for Shopify on 21 November 2026.

docs.cloud.google.com

25,000

Objects a paginated Shopify query can reach, so large backfills need a bulk operation.

shopify.dev

$6.25

Per TiB scanned by on-demand BigQuery queries after the first free TiB each month.

cloud.google.com/bigquery/pricing

10 GiB

Storage that is free each month, and batch loading is free on the shared pool.

cloud.google.com/bigquery/pricing

1,000 points

Maximum cost of a single Shopify GraphQL query. Above it the query is refused.

shopify.dev

0

Duplicate rows BigQuery rejects for you. Primary keys are informational and are not enforced.

BigQuery, constraints

Six ways a Shopify to BigQuery pipeline is wrong while the log is green

Finance finds these at month end, not in monitoring. Each one exits zero.

Failure Why it is silent The check
Revenue too high after refunds A refund is a separate object. If only orders load, gross totals never move and net sales read gross. Load refunds, net them by order and tie one closed month to the Shopify sales report.
Two currencies in one column Shopify returns shop currency and presentment currency for money. Summing the wrong one mixes currencies and nothing errors. Keep the currency code next to every amount and total by currency.
Duplicate orders BigQuery accepts a primary key declaration and ignores it. A retried batch appended with a load job doubles the rows and exits zero. Count rows per Shopify id after every backfill. Any count above 1 is a failed load.
Test orders in revenue Orders placed on a test gateway carry a flag. Without a filter they count as sales. Exclude flagged test orders and compare the order count with the Shopify admin.
Days that shift at midnight Timestamps are UTC while the store reports in its own zone. Grouping by the UTC date slides evening orders into the next day. Group by the store time zone and compare the daily count on the first and last day of a month.
Money as a float A field typed Double lands as FLOAT64, and sums of floats drift by fractions of a cent with no error. Cast amounts to NUMERIC in a staging view and compare a month total to the cent.

Six steps that decide whether this project works

Step 1

List the objects you report on

Orders, refunds, transactions, line items, products, variants, customers and inventory cover most merchant models. Orders alone cannot reconcile to a payout, because fees and refunds live on other objects.

Step 2

Declare money columns first

Create amounts as NUMERIC, keep the currency code beside each amount and store created as TIMESTAMP. Keep unstructured fields in a JSON column so new Shopify fields never break a load.

Step 3

Backfill with a bulk export

One bulk operation per object type brings the full history without paging, and tie each month to the Shopify sales report before moving on. Pagination cannot reach past 25,000 objects.

Step 4

Merge on id, never append

Every load is a MERGE keyed on the Shopify id, because BigQuery will not reject a duplicate for you. That one rule makes retries safe and lets order edits update the original row.

Step 5

Partition by order date

Partition the orders table by created date and query only the months you need. On-demand pricing is per byte scanned, so a dashboard that reads one month scans a fraction of the table.

Step 6

Reconcile after every close

Count and sum by month and currency in both systems. A mismatch is a failed sync even if the log is green.

With Adapters the type decisions in step 2 happen when you map the field, so an order total lands as NUMERIC beside its currency and created keeps its zone from the first run, and every batch is merged on id. The mapping for this pair is on the Shopify to BigQuery connector page.

Five jobs where you should not pick us

A comparison that never says the competition wins is an advert. These are the cases where something else on this page is the right answer.

  • You are a Google Cloud team that wants a first-party connector inside your own project and can accept Preview terms. The Data Transfer Service connector is the least moving parts.
  • You already run Fivetran or Airbyte across thirty sources into BigQuery and Shopify is one more. A second tool for one source rarely pays back.
  • You only need storefront reports. Shopify's own analytics answers that without a warehouse.
  • You need every Shopify object, including ones no preset covers. A connector with an object override or a full-schema loader will cover more.
  • You need a push on every order the second it is placed. Every scheduled route here, ours included, runs on an interval.

Four questions to ask any vendor on this list

Question 01

Do you MERGE or INSERT?

Ask how the tool writes each batch into BigQuery. BigQuery will not stop a duplicate, so a tool that appends and deduplicates later leaves a window where your totals are wrong.

Question 02

What do I pay at twice my order volume?

Ask for the bill at your busiest month and at double it. Per row pricing moves with your sales, and a full reload per run moves with the size of the store. A flat plan does neither.

Question 03

How do refunds, edits and deletes arrive?

Ask for the behavior by object and the column that shows the change. A vendor that cannot answer has not handled it.

Question 04

How are amounts and currencies stored?

Ask whether money lands as exact decimals with a currency code, or as floats or strings you must convert. That is where mixed currency totals and cent drift come from.

Questions buyers ask about Shopify to BigQuery integration

How do I connect Shopify to BigQuery?
There are three routes. Google's BigQuery Data Transfer Service has a Shopify connector, which is a Preview feature and needs a custom Shopify app. A third-party or Adapters connector does the same on its own schedule. Or you run Shopify bulk operations yourself and load the files through Cloud Storage.
Does BigQuery have a native Shopify connector?
Yes, in Preview. The Data Transfer Service connector reads GraphQL based Shopify objects such as orders, refunds, order transactions, customers and products into a dataset you choose. Google says Preview features are provided as is and can have limited support, so it is native but not yet a service you can sign a finance close on.
How much does the BigQuery Shopify transfer cost?
Google lists no charge for the transfer while the feature is in Preview. You still pay BigQuery storage and queries. On-demand queries cost $6.25 per TiB scanned after the first free TiB each month, and storage is about $0.023 per GiB a month after the first 10 GiB. Expect pricing to be set when the connector reaches general availability.
Why do my Shopify order totals not match BigQuery?
Usually refunds, currency or test orders. A refund is its own object, so gross order totals stay unchanged unless refunds are loaded and netted. Money comes as shop currency and presentment currency pairs, and test orders carry a flag. Reconcile one closed month against the Shopify sales report.
Can Shopify data be backfilled into BigQuery?
Yes, through bulk operations, which export a whole object type as one file instead of paging. Paging stops at 25,000 objects per query, so a store with years of orders cannot be backfilled by pagination alone. Run the bulk export once, then switch to changes since the last updated timestamp.
Does BigQuery enforce a primary key on Shopify orders?
No. BigQuery accepts primary key declarations as information for the optimizer but does not reject duplicates. A retried load that appends instead of merging doubles the rows and exits zero. Count rows per Shopify id after every backfill and merge on that id, whichever tool does the loading.
What is the best Shopify to BigQuery integration for a small merchant team?
The one whose cost does not grow with orders, that loads refunds and money in the right currency, merges on the Shopify id so reruns never duplicate rows and tells you how deletes arrive. Run any trial on one closed month tied to the Shopify sales report.

For pushing warehouse results back into your storefront or CRM, see reverse ETL tools.

Land Shopify in BigQuery at a price that ignores your order count

Map each object once, declare NUMERIC money per currency, backfill in bulk, then merge only what changed on the schedule you pick. Flat plans from $49 a month, no overage fees.

The live demo needs no card, and Starter is $49 a month.

Get started