Skip to main content
Card class: Non-Hero • Category: Ecommerce Platform

​
At a glance

Per-channel revenue stacked by currency_code over the trailing 30 days. The merchant’s view of “which channels are bringing in which currencies”, essential for FX exposure planning, payment-processor configuration, and tax-jurisdiction routing. BigCommerce’s multi-currency support pairs naturally with channel-native sales; this card is the cross-product visibility merchants need to manage that stack.
What it countsSUM(total_inc_tax) GROUP BY channel_id, currency_code over the trailing 30 days, displayed as a stacked bar per channel. Each channel shows its currency split as proportions and absolute values; totals are NOT FX-converted by default (each currency is shown in native amount).
API endpointGET /stores/{store_hash}/v2/orders with currency_code per order; GET /v3/channels for channel metadata. The OpenSearch index materialises per-channel-per-currency-per-day aggregates.
VAT / tax treatmentTax-inclusive in each currency. Note that VAT-inclusive USD and VAT-inclusive GBP carry different tax components; the comparison is structurally apples-to-oranges in unconverted view.
ShippingIncluded in each currency.
DiscountsDeducted.
RefundsNot deducted.
Cancelled ordersExcluded.
Incomplete ordersExcluded.
CurrencyThe decomposition variable. Shows native currency by default (USD orders in USD, GBP in GBP); converted-display option converts to a single reporting currency using daily FX rates.
Channel coverageAll BC channels. POS terminals are typically single-currency (the till’s configured currency); web channels are typically single-currency per storefront; marketplaces are channel-locked (Amazon UK = GBP, Amazon US = USD). The card surfaces the few channels that legitimately mix currencies (multi-currency web storefronts, B2B portal with international customer groups).
B2B Edition behaviourB2B portal can mix currencies if customer-group price lists are configured per-region. The card surfaces which customer groups buy in which currency, useful for cash-flow planning.
FX rate handlingWhen converted display is selected, the rate is daily_fx_rate * order_total_native. We use ECB daily rates for EU pairs and OpenExchangeRates for others. Don’t expect the converted total to match what your payment processor settled, processors apply their own FX and fees; the gap is typically 1-3%.
Time window30D rolling.
Alert triggerNone (pattern card).
Rolesowner, finance

​
Calculation

Calculated automatically from your BigCommerce data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

​
Worked example

A UK skincare brand on BigCommerce Enterprise with multi-storefront (UK, US, EU) and B2B Edition. Snapshot for 1 Apr to 30 Apr 26.
channel_idChannelGBPUSDEURAUDTotal (GBP equiv)
1UK Stencil web£180,420 (100%)$0€0A$0£180,420
2US Stencil web£0$108,500 (100%)€0A$0£86,800
3EU Stencil web£0$0€92,140 (100%)A$0£79,240
12000004B2B portal£45,000 (62%)$18,200 (20%)€11,400 (13%)A$3,200 (5%)£72,800
1019847Amazon UK£42,300 (100%)---£42,300
1019848Amazon US-$51,600 (100%)--£41,280
1020114POS UK store£8,200 (100%)---£8,200
Headline£511,040
What’s interesting:
  1. Most channels are mono-currency by design. Each storefront, each marketplace listing region, each POS terminal is currency-locked. The interesting row is the B2B portal, which carries 4 currencies because B2B Edition customer groups can be regionalised. That’s where FX exposure planning lives.
  2. B2B portal currency mix tells the wholesale-customer geography story. 62% GBP / 20% USD / 13% EUR / 5% AUD reflects the merchant’s wholesale customer book by country. If GBP suddenly drops to 40% MoM, the cause is usually a US wholesale customer placed an unusually large PO, not currency-trend movement. Always check absolute volumes alongside percentages.
  3. The headline GBP-equivalent total is FX-rate-sensitive. When USD strengthens 5% vs GBP, the total grows 5% just from FX without any volume change. For accurate revenue trend always view in either native-currency-only mode or constant-currency mode (using last-period FX rates). Configure under Settings → FX → Constant currency.
  4. Payment processor settlement gap. Merchant’s Stripe US account settled $108,500 on US storefront orders, matching this card. But the merchant’s Stripe UK account settled £179,890 on UK orders, less than the card’s £180,420. The £530 gap is Stripe’s currency conversion fees on a small sub-set of cross-border UK-storefront orders that processed through USD acquirer routing. Reconcile against payment processor before flagging as a data issue.
  5. EU storefront concentration is pure-EUR. Healthy from an FX-exposure standpoint, the merchant’s EU costs (some Lithuanian fulfilment) are EUR-denominated, so EUR revenue and EUR cost natural-hedge.
Action priority order:
  1. For finance teams, view in native-currency mode for FX exposure planning; view in converted mode for board reporting.
  2. For the B2B portal specifically, watch for currency-mix shifts month-over-month, they signal customer-book changes.
  3. Reconcile against payment processor for each currency separately; the gateway’s FX fee creates a small structural gap.
  4. Pair with BC Revenue by Currency for the cross-channel currency rollup.
  5. For multi-storefront stores, this card is essential for understanding which storefront drives which currency exposure.

​
Sibling cards merchants should reference together

CardWhy pair it with Currency Mix by Channel
BC Revenue by CurrencyThe cross-channel rollup; this card is the per-channel decomposition.
BC AOV by CountryCountry and currency are correlated but not identical; pair for the geography view.
BC Channel Revenue TrendTrend per channel with currency-aware comparison.
Total RevenueHeadline rollup; FX-converted to single currency.
BC Orders by ChannelVolume context; currency mix shifts can reflect order-count shifts.
BC Channel AOVPer-channel AOV needs currency context for cross-channel comparison.
BC Channel Top ProductsPair to identify which SKUs sell in which currency.
BC Guest vs RegisteredB2B portal currency mix correlates with the registered-customer cohort.

​
Reconciling against the vendor’s own dashboard

Where to look in BigCommerce Control Panel: Settings → Currency shows the currencies configured on the store. Analytics → Sales shows revenue but doesn’t natively split by currency-and-channel; you need Reports → Custom to build the cross-tab. For multi-storefront: Storefronts → All storefronts shows per-storefront revenue; pair with the configured currency for each storefront. Why our currency split may differ from BC’s storefront analytics:
ReasonDirection
FX rate timing. We use ECB / OXR daily rates; BC may use different rate provider. Converted totals can differ by 0.5-2%.Either direction (rate-dependent)
B2B Edition cross-currency. B2B portal can have customer-group-specific currencies; BC’s main analytics may aggregate to the merchant’s primary.Vortex IQ surfaces granularity; BC main view less so
POS terminal currency. Each terminal has a configured currency; some BC plans surface per-terminal, others aggregate.Different granularity
Refund-currency timing. A refund processed in USD on a GBP order can muddle the figures depending on processor handling.Various
Rounding. Per-line item rounding and FX rounding compound for multi-line orders.Sub-1% gap
Cross-connector reconciliation (when payment processors are connected):
CardExpected relationshipWhat causes legitimate divergence
stripe.stripe_revenue_by_currencyShould match Stripe-paid orders per currency within 1-2%Stripe’s settlement currency may differ from order currency (acquirer routing); the gap is typically 0.5-2%.
paypal.pp_revenue_by_currencyShould match PayPal-paid orders per currencyPayPal applies its own FX which can differ from BC’s recorded rate.
adyen.adyen_settlement_currencyAdyen’s settlement currency split should match this card’s processor-routed viewAdyen offers settlement-currency-of-choice; merchants who route all to USD see only USD on Adyen, multi-currency on this card.
The per-channel currency mix view is BC-aligned with similar cards on Shopify (per presentment_currency) and Adobe Commerce (per base_currency_code); merchant-facing semantics are equivalent though Adobe’s multi-currency model is stronger and Shopify’s is weaker than BC’s.

​
Known limitations / merchant FAQs

My UK storefront only shows GBP. Why is this card useful for me? For a single-storefront single-currency BC store this card adds little. It becomes essential when (a) you have multi-storefront with different storefront currencies, (b) you have B2B Edition with international customer groups, or (c) you sell on multiple-region marketplaces (Amazon UK + Amazon US). If none apply, the card will show one row per channel with one currency per row, which is a sanity-check view but not actionable. My headline GBP-equivalent total grew 5% but my native-currency volumes are flat. Is that real growth? No, that’s FX. When USD strengthens vs GBP, your USD revenue translates to more GBP without any volume change. For comparable revenue trend, view in native-currency mode or constant-currency mode (using prior-period FX rates). True growth requires native-volume growth or basket-size growth, neither of which is moving in this scenario. Why does my B2B portal carry 4 currencies when each customer group should be locked to one? Customer groups can be locked to currencies, but the BC default allows currency override at checkout. Some B2B Edition configurations allow customers to choose between their group’s default currency and the merchant’s primary; this produces a mix. To enforce single-currency per customer group, configure under B2B Edition → Customer groups → Currency lock. My EU storefront shows EUR revenue but my Stripe account shows USD. What gives? Settlement currency vs order currency. Your customer paid in EUR, BC records the order in EUR, but Stripe (configured for USD settlement) converts to USD before depositing in your bank. Both are correct at their respective layers; the gap (and the FX fee) is Stripe’s FX. For accurate net revenue read, look at this card minus payment-processor settlement FX fees. Why doesn’t this card use my BC-configured exchange rates? We use ECB / OXR daily rates because they’re audited / consistent. BC’s configured rates can be merchant-set and may not reflect market rates. If you prefer BC-configured rates, configure under Settings → FX → Source = BigCommerce. We support both. **My Australian PRC orders show as AbutIexpectedNZD.What′swrong?∗∗Currencyissetper−orderbasedonthestorefront−and−customercombination.NewZealandcustomersbuyingthroughyourAUstorefrontgetA but I expected NZD. What's wrong?** Currency is set per-order based on the storefront-and-customer combination. New Zealand customers buying through your AU storefront get A unless your storefront is configured for NZD. Configure under Settings → Currency → Customer locale routing to route NZ-IP customers to NZD presentation. Can I see this in a single reporting currency? Yes, toggle the converted-display option at the top of the card. Each currency translates to your selected reporting currency at the daily FX rate. Be aware the converted total is for visualisation only; for finance reconciliation use native currencies and reconcile per-currency. Multi-storefront stores with shared catalogue: does inventory FX matter? Yes for cost-of-goods reporting, no for this card. This card shows revenue currency mix (what customers paid in). For COGS-currency mix (what your supplier invoices in), see BC Margin by Brand which can be filtered by purchasing-currency. Why is my POS terminal showing two currencies? Possibly the terminal supports a tourist-currency option (some POS configs allow EUR / USD payment in a UK store for visiting tourists). Check Settings → POS → Terminal currency settings. Most stores configure single-currency POS; tourist-currency is a niche use-case. The B2B portal’s USD share grew from 15% to 28% MoM. Should I be worried? Not necessarily, this often signals B2B portal expansion into US wholesale. Verify by checking customer count from US in the period; if you onboarded 2-3 new US wholesale accounts, the mix shift is structural and good. If customer count is flat but USD share grew, a single large US customer placed an outsized order, watch for repeat to confirm pattern.

​
Tracked live in Vortex IQ Nerve Centre

Currency Mix by Channel is one of hundreds of KPI pulses Vortex IQ tracks across BigCommerce and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. Start for free or book a demo to see this metric running on your own data.