E-Commerce · head to head
BackToMe vs BigQuery

BackToMe
E-Commerce
Right-of-withdrawal handling for European e-commerce
- From
- €25/month
- Free plan
- No

BigQuery
Databases
Google Cloud's serverless analytical warehouse, billed either by bytes scanned per query or by reserved compute slots.
- From
- Free
- Free plan
- Yes
The short version
- BigQuery has a free plan, then $6.25/mo; BackToMe starts at €25/mo.
- Only BackToMe lists floating withdrawal button; only BigQuery lists serverless compute.
- Where BackToMe falls short: the scope is European consumer law. A merchant selling outside the EU has no use for it.
- Prices and features on this page were last checked on 17 September 2026.
Where they differ
Only the attributes on which BackToMe and BigQuery actually diverge.
Not yet recorded: founded for BackToMe.
What each one covers
Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in BackToMe
- Floating withdrawal button
- Automatic acknowledgement
- Sealed archiving
- Withdrawal dashboard
- One-click proof export
- Multi-store from one account
Only in BigQuery
- Serverless compute
- Separation of storage and compute
- Two pricing models
- Partitioning and clustering
- Materialised views
- BigQuery ML
- Storage Write API
- BI Engine
What people use each for
The jobs each tool is most often brought in to do.
BackToMe
- Meeting EU Directive 2023/2673 withdrawal obligationsnot BigQuery
- Producing dated proof of a cancellation in a customer disputenot BigQuery
- Handling withdrawal requests across several EU languagesnot BigQuery
- Running one withdrawal process across multiple storefrontsnot BigQuery
- Passing a consumer-protection audit with exportable recordsnot BigQuery
BigQuery
- A warehouse for an organisation already on Google Cloud, where identity, logging and billing are consolidated in the same placenot BackToMe
- Bursty analytical workloads with long idle periods, where paying per query beats keeping a cluster runningnot BackToMe
- Event and clickstream analytics ingested continuously through the Storage Write API and queried without a load windownot BackToMe
- Analytics teams with no infrastructure staff, where the absence of anything to tune or patch is worth more than dialect portabilitynot BackToMe
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
BackToMe
- The scope is European consumer law. A merchant selling outside the EU has no use for it
- The site and dashboard are French. The customer-facing button covers 24 EU languages, but the merchant side is not multilingual
- One price, one feature set. There is no tier for a shop that wants only the archive or only the button
- It runs as an injected script on the storefront, so a shop with a strict content security policy has an extra step before the button will render
- A young French vendor with no independent review coverage, so there is nothing outside the vendor's own material to corroborate the archive's evidentiary weight
BigQuery
- On-demand billing charges for bytes read from every column a query references, so an unqualified select or a missing partition filter turns a routine query into a large bill, and the cost is discovered after the fact rather than at review time
- There is no way to join tables that live in different regions, so a data estate split across regions for residency reasons has to be reconciled with copies and the storage and transfer that implies
- It is not built for point lookups; retrieving a single row has latency measured in hundreds of milliseconds or more, so BigQuery cannot serve an application's read path and always needs a second store in front of it
- Frequent small mutations run into DML concurrency limits and the cost of rewriting storage blocks, so a workload that updates individual rows continuously behaves badly compared with an append-only design
- The compute exists only inside Google Cloud, so while tables can be exported, the accumulated GoogleSQL, scheduled queries, authorised views, ML models and IAM structure do not move, and switching warehouses is a rewrite of the analytical layer
Pricing, plan by plan
BackToMe
€25/month- Monthly€25/mo
- Per active store, excluding VAT
- Unlimited withdrawal requests
- 24 EU languages
- Annual€250/yr
- Per store, excluding VAT
- Two months free against the monthly rate
- Everything in the monthly plan
BigQuery
Free- Free TierFree
- 1TB queries/month
- 10GB storage/month
- Standard support
- On-demand$6.25/tb
- Pay per query
- Pay per storage
- All features
Which should you pick?
Choose BackToMe if
- You need floating withdrawal button.
- You also want automatic acknowledgement.
Choose BigQuery if
- You need serverless compute.
- You want to start without paying.
- You work on Web, API.
- You also want separation of storage and compute.
Questions people ask
- Is BackToMe or BigQuery better?
- Neither clearly leads. BackToMe starts at €25/month and BigQuery at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, BackToMe or BigQuery?
- BigQuery has a free tier; the other does not. Paid plans start at €25/month for BackToMe and Free for BigQuery.
- Does BackToMe or BigQuery run on more platforms?
- BackToMe runs on Web. BigQuery runs on Web, API.
- Can I use BigQuery for free?
- Yes. BigQuery has a free tier, so you can try it without paying. BackToMe starts at €25/month.
- What is BackToMe best used for?
- BackToMe is most often used for meeting eu directive 2023/2673 withdrawal obligations, producing dated proof of a cancellation in a customer dispute, handling withdrawal requests across several eu languages, running one withdrawal process across multiple storefronts. Of those, meeting eu directive 2023/2673 withdrawal obligations and producing dated proof of a cancellation in a customer dispute are not what BigQuery is typically brought in for.
- What can BackToMe do that BigQuery cannot?
- BackToMe covers Floating withdrawal button, Automatic acknowledgement, Sealed archiving, Withdrawal dashboard. BigQuery covers Serverless compute, Separation of storage and compute, Two pricing models, Partitioning and clustering.
Answered from the vendors’ own pages
BackToMe: What does BackToMe cost?
25 euros excluding VAT per month per active store, or 250 euros excluding VAT per year, which works out at two months free. The price does not change with the number of withdrawal requests.
SourceBigQuery: How is BigQuery actually billed?
Storage is billed separately from compute. Compute is either on-demand, priced by the bytes a query reads from the referenced columns, or capacity-based, where you reserve autoscaling slots. Most cost surprises come from on-demand queries that scan more than expected.
BackToMe: Which regulation does it address?
EU Directive 2023/2673, which governs the consumer right of withdrawal on distance contracts in e-commerce.
SourceBigQuery: How do I control query cost?
Partition and cluster tables so queries prune data, select only the columns needed, use materialised views for repeated aggregations, and set maximum bytes billed on queries so a runaway scan fails instead of billing.
BackToMe: Is there a free trial?
Seven days. A card is required to start it but nothing is charged upfront, and cancelling before day seven costs nothing. There is also a 30-day money-back guarantee.
SourceBigQuery: Can I use it without being on Google Cloud?
The service only runs on Google Cloud. BigQuery Omni can query data held in S3 or Azure storage, but the compute is still Google's and the account relationship is still with Google.
BackToMe: Are staging and development stores billed?
No. Only activated stores are billed, and the withdrawal button does not display on inactive ones.
SourceBigQuery: Is it suitable for serving application queries?
No. Latency for single-row reads is far too high. BigQuery is an analytical warehouse and application read paths need a transactional database or a cache in front of it.
BackToMe: What happens to the archive if I cancel?
Cancellation is available at any time with no commitment, premium access runs to the end of the paid period, and the account stays open with archived withdrawals and proofs accessible indefinitely. Reactivation is self-service.
SourceBigQuery: When should I move from on-demand to capacity pricing?
When on-demand spend becomes both large and predictable, or when unpredictable spend is a bigger problem than query queueing. The switch trades a variable bill for a fixed one plus contention between workloads.
BackToMe: Which e-commerce platforms does it support?
Shopify, WordPress, WooCommerce, PrestaShop, Wix, Webflow, WiziShop and Squarespace, plus custom builds through a single line of script. The vendor puts installation at five minutes on any platform.
SourceRelated pages
Other head to heads
- BackToMe vs Temu
- BackToMe vs Amazon Shopping
- BackToMe vs Mailchimp
- BackToMe vs Shein
- BackToMe vs CJ Dropshipping
- BackToMe vs Memberful
- BackToMe vs Wish
- BackToMe vs Zendrop
- BackToMe vs Heartland Retail
- BackToMe vs Vinted
- BackToMe vs Mollie
- BackToMe vs TikTok Shop
- BackToMe vs SamCart
- BackToMe vs Sellfy
- BackToMe vs Shopware
- BackToMe vs Spree Commerce
- BackToMe vs Swell Commerce
- BackToMe vs Toast
- BackToMe vs Amazon Redshift
- BackToMe vs Firebolt
- BackToMe vs MotherDuck
- BackToMe vs FaunaDB
- BackToMe vs DuckDB
- BackToMe vs TiDB
- BackToMe vs Apache Druid
- BackToMe vs ClickHouse
- BackToMe vs PlanetScale
- BackToMe vs Redpanda
- BackToMe vs RisingWave
- BackToMe vs ScyllaDB
- BackToMe vs Solace PubSub+
- BackToMe vs SQLite
- BackToMe vs StarRocks
- BackToMe vs Amazon RDS
- BackToMe vs Apache Flink
- BackToMe vs DynamoDB
- BigQuery vs Temu
- BigQuery vs Amazon Shopping
- BigQuery vs Mailchimp
- BigQuery vs Shein
- BigQuery vs CJ Dropshipping
- BigQuery vs Memberful
- BigQuery vs Wish
- BigQuery vs Zendrop
- BigQuery vs Heartland Retail
- BigQuery vs Vinted
- BigQuery vs Mollie
- BigQuery vs TikTok Shop
- BigQuery vs SamCart
- BigQuery vs Sellfy
- BigQuery vs Shopware
- BigQuery vs Spree Commerce
- BigQuery vs Swell Commerce
- BigQuery vs Toast
- BigQuery vs Amazon Redshift
- BigQuery vs Firebolt
- BigQuery vs MotherDuck
- BigQuery vs FaunaDB
- BigQuery vs DuckDB
- BigQuery vs TiDB
- BigQuery vs Apache Druid
- BigQuery vs ClickHouse
- BigQuery vs PlanetScale
- BigQuery vs Redpanda
- BigQuery vs RisingWave
- BigQuery vs ScyllaDB
- BigQuery vs Solace PubSub+
- BigQuery vs SQLite
- BigQuery vs StarRocks
- BigQuery vs Amazon RDS
- BigQuery vs Apache Flink
- BigQuery vs DynamoDB
