Ecommerce & Subscription

BigCommerce sales and customer value beside your other stores

BigCommerce refunds and repeat sales are hard to compare across stores. Use shared sales, product and customer lifetime value reporting.

Access: A store-level API account with read-only permissions
MCP server: Official server, but not for your account data, checked September 2026

Book a walkthrough View docs

BigCommerce

Commerce, order, billing, and subscription systems that anchor revenue and lifecycle reporting.

Why BigCommerce?

A read-only API connection covers every channel of your BigCommerce store. Source-scoped identities keep overlapping order and customer numbers distinct when you also sell through Shopify or another platform.

Refund-aware sales

Recorded refund cash flows into the shared transaction ledger on its own event date.

Current reference data

Customer addresses, product variants and store settings use complete daily snapshots.

Before you analyze

Boundaries that change how BigCommerce numbers should be read.

Compare the same reporting basis

Align currency, timezone, date basis, order statuses and refund window before comparing native totals. Finance, payouts and settlement reports are outside this reporting scope.

Lifetime value covers captured history

Purchases outside the synced history are not included. Guest orders contribute to sales but lack a registered customer identity.

Refund breakdown limits

Product-level refund allocation and separate shipping-tax refund reporting are not certified. Known refund amounts remain in order totals without an invented allocation.

Details in the docs

What you can ask

With SourceMedium Agent, you can query BigCommerce data using natural language. Here are some examples.

How much sales revenue remains after BigCommerce refunds?

Which BigCommerce customer cohorts return to purchase again?

Investigate with your AI

Joins with other integrations

BigCommerce data is designed to join with your other data sources for unified analysis.

Shopify WooCommerce Magento

How it works

Setup depends on the source. We confirm access requirements, history, cadence, and customer responsibilities before implementation begins.

Create a read-only API account

Grant Information, Orders, Customers and Products read-only scopes.

Connect your store

Save your store hash and access token in SourceMedium.

Use shared reporting

Sales, refunds, products and customers enter the commerce models automatically.

Ready to stop debating the numbers?

In 30 minutes, we will

Map your current systems and reporting gaps.
Show one workflow relevant to your team.
Outline likely fit, implementation scope, and next steps.

Book a walkthrough

Share a little context, then choose a time immediately after submitting.