> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Revenue by Currency, BigCommerce > Revenue by Currency for BigCommerce stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it. **Metrics type:** [Supporting Metrics](/nerve-centre/overview#metrics-types-explained) • **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type) ## At a glance > Total revenue split by `currency_code` across all multi-currency BigCommerce orders. Critical for stores running BC's Multi-Currency feature, the FX-conversion happens at the storefront level, not the order level, so this card shows the actual settled-currency breakdown that the merchant's bank receives. | | | | ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | `SUM(total_inc_tax) GROUP BY currency_code` over the period. Each order is denominated in the customer's purchase currency; this card sums in native currency without conversion. The raw mix of currencies the merchant collected. | | **VAT / tax treatment** | **Tax-inclusive** (`total_inc_tax`). | | **Shipping** | Included (in the same currency as the order). | | **Discounts** | Already deducted. | | **Refunds** | Not deducted (gross). | | **Cancelled / voided orders** | Included. | | **Currency** | This is the by-currency view, **no FX conversion happens**. The card shows native amounts per currency code. | | **Channels / sources** | All channels contribute. Marketplace channels are typically currency-locked (Amazon UK = GBP, Amazon US = USD), so the per-currency split correlates with the per-channel split for marketplace-heavy stores. Web with multi-currency enabled spreads across many currencies. | | **BC multi-currency mechanics** | BC's [Multi-Currency feature](https://support.bigcommerce.com/s/article/Setting-Up-Multiple-Currencies) lets the storefront display prices in several currencies, but settlement happens in **one or two settlement currencies** depending on the payment gateway. Stripe Connect, Adyen, and Braintree support multi-currency settlement; PayPal often forces conversion to merchant's home currency on settlement. **The currency in this card is the customer-paid currency, not the settlement currency.** | | **Settlement vs presented** | If you take an order in EUR but Stripe settles to your USD bank, BC indexes the EUR amount; this card shows EUR revenue. To see settlement-currency totals (what your bank actually received), use the gateway's own dashboard. | | **Time window** | `30D` (rolling 30 days, vs prior 30 day comparison) | | **Alert trigger** | None on this card directly. | | **Roles** | owner | ## 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-based homewares brand on BigCommerce Pro selling worldwide via web + Amazon UK + Amazon US + Amazon DE + eBay. 30-day window 14 Apr 26 to 14 May 26. | Currency | Revenue (native) | Approx GBP equiv (FX 14 May 26) | Share by GBP equiv | vs prior 30d | Source channel mix | | --------- | ---------------- | ------------------------------- | ------------------ | ------------- | ---------------------------- | | GBP | £172,400 | £172,400 | 47.2% | +3.8% | Web (UK), Amazon UK, eBay UK | | USD | \$148,200 | £118,560 | 32.5% | +14.2% | Amazon US, Web (US shoppers) | | EUR | €78,400 | £67,224 | 18.4% | +6.1% | Amazon DE, Web (EU shoppers) | | AUD | \$9,800 AUD | £5,096 | 1.4% | +1.0% | Web (AU shoppers) | | CAD | \$2,400 CAD | £1,392 | 0.4% | -3.5% | Web (CA shoppers) | | **Total** | (mixed) | **£364,672** | **100%** | +6.7% overall | | What's interesting: 1. **47% GBP / 32% USD / 18% EUR is a typical UK exporter mix.** A pure-UK retailer would see 95%+ GBP; this merchant has built a meaningful US (Amazon US) and EU (Amazon DE + web) presence. The currency mix is a leading indicator of international expansion success. 2. **USD revenue at +14% is the standout growth signal.** Investigate: is Amazon US growing organically, did a Sponsored Products campaign work, did a US-specific SKU lift? Cross-reference with [BC Revenue by Channel](/nerve-centre/kpi-cards/bigcommerce/revenue-by-channel) filtered to Amazon US. 3. **EUR at +6% is healthy but the GBP-to-EUR FX rate matters.** If GBP weakened against EUR by 4% during the period, EUR revenue grows in GBP terms even if EUR demand was flat. Watch [Bank of England daily rates](https://www.bankofengland.co.uk/) for context. Use the FX-adjusted view for true demand signal. 4. **AUD and CAD are too small to matter strategically** but worth keeping (web traffic from these regions is essentially free; servicing them via auto-translation has near-zero marginal cost). 5. **Settlement-currency reality check.** This merchant's bank receives GBP only (PayPal converts everything). The £364k headline is the GBP-equivalent settled amount. The conversion fees (typically 2-3.5% on PayPal) are a hidden cost; switching to Stripe Connect or Adyen for multi-currency settlement saves £8-12k/year on this volume. Action priority order: 1. **Investigate USD +14% surge** this week, replicate the lever in EUR if applicable. 2. **Run an FX-cost audit**, what are you paying in conversion fees? Switch gateways if the cost exceeds the convenience. 3. **Decide on AUD / CAD strategy**: keep as small-effort tail or actively grow with localised pricing pages. 4. **Set per-currency revenue alerts** for any currency >5% of revenue dropping >15% week-over-week. 5. **Review the storefront price-display logic** quarterly, are EUR / USD prices set to absorb FX swings or pass them on? ## Sibling cards merchants should reference together | Card | Why pair it with Revenue by Currency | | ----------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [BC Channel Currency Mix](/nerve-centre/kpi-cards/bigcommerce/currency-mix-by-channel) | Channel × currency cross-tabs reveal which channels drive which currencies (Amazon-locked vs web-multi). | | [BC Revenue by Channel](/nerve-centre/kpi-cards/bigcommerce/revenue-by-channel) | The channel split, often correlates strongly with currency for marketplace-heavy stores. | | [BC AOV by Country](/nerve-centre/kpi-cards/bigcommerce/aov-by-country) | Per-country AOV; AOV in USD often higher than EUR due to product-mix differences. | | [Total Revenue](/nerve-centre/kpi-cards/bigcommerce/total-revenue) | The denominator. Note: store revenue may show a single-currency total that masks the currency mix. | | [`stripe.stripe_revenue_by_currency`](/nerve-centre/kpi-cards/stripe/revenue-by-currency) | If Stripe processes web orders, the per-currency revenue should track this card minus marketplace channels. | | [`paypal.pp_revenue_by_currency`](/nerve-centre/kpi-cards/paypal/revenue-by-currency) | PayPal-specific currency view; PayPal often forces conversion to merchant home currency on settlement, so PayPal's settled mix differs from this card's presented mix. | | [BC Customer Countries](/nerve-centre/kpi-cards/bigcommerce/orders-by-country) | The customer-country split; correlates with currency but not 1:1 (a US shopper may pay in GBP if served by the UK storefront). | | [`shopify.aov`](/nerve-centre/kpi-cards/shopify/average-order-value) | Cross-platform reference for multi-currency commerce reporting. | ## Reconciling against the vendor's own dashboard **Where to look in BigCommerce Control Panel:** [Settings → Currencies](https://login.bigcommerce.com/deep-links/manage/settings/currencies) shows the currencies your storefront supports and the FX rates BC uses to display prices. [Analytics → Sales](https://login.bigcommerce.com/deep-links/manage/analytics) on Pro / Enterprise plans includes a currency filter. **BC's analytics report converts everything to your default currency**; this card preserves native amounts. Both views are useful for different questions. For a settlement-currency view (what your bank received), use the gateway dashboard: Stripe Dashboard → Payments → Settled, PayPal Activity → Currency, or Adyen Customer Area → Settlement. **Why our number may legitimately differ from BC:** | Reason | Direction | | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------- | | **FX conversion in BC reports**. BC's analytics typically converts to merchant default currency for headline totals. Our card preserves native currency. | Different shape, not a discrepancy | | **Settlement-currency vs presentment-currency**. Some gateways (PayPal) force conversion at capture; the customer paid EUR, the merchant received GBP. We index the customer-paid amount; PayPal's dashboard shows the settled amount. | Different views by design | | **Time-zone**. BC uses store time zone; we use UTC. | Boundary-day differences | | **Manual orders / wholesale invoices**. Some merchants take wholesale orders manually and key them in BC; the order-creation currency may differ from the customer's actual payment currency. | Possible mismatches | | **Refunds in different currencies**. A USD order refunded post-FX-rate-change refunds in USD at the new rate; the GBP-equivalent differs from the original. | FX-conversion artefacts | **Cross-connector reconciliation (when payment processors are connected):** | Card | Expected relationship | What causes legitimate divergence | | ----------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- | | [`stripe.stripe_revenue_by_currency`](/nerve-centre/kpi-cards/stripe/revenue-by-currency) | Stripe-processed web orders by currency should match this card's web-channel slice within ±2%. | Stripe sees only successful captures; this card includes Incomplete and Declined. | | [`paypal.pp_revenue_by_currency`](/nerve-centre/kpi-cards/paypal/revenue-by-currency) | PayPal often forces home-currency conversion; expect significant divergence in non-home currencies. | This is by design. | | [`adyen.adyen_revenue_by_currency`](/nerve-centre/adyen/adyen_revenue_by_currency) | Adyen's multi-currency settlement matches the per-currency split here within ±1%. | Adyen is the cleanest reconciliation for multi-currency BC. | **Multi-currency reporting differs significantly between BC, Shopify, and Adobe Commerce; BC's currency display vs settlement separation is more transparent than Shopify's blended Multi-Currency feature.** ***
Same-metric documentation cross-reference (for agencies running multiple platforms) * [`shopify.revenue_by_currency`](/nerve-centre/shopify/revenue_by_currency) (planned) * [`adobe_commerce.revenue_by_currency`](/nerve-centre/adobe_commerce/revenue_by_currency) (planned)
## Known limitations / merchant FAQs **My store accepts only GBP, why does this card show USD too?** Because Amazon US orders (via Channel Manager) are denominated in USD regardless of your storefront currency. Same for eBay US, Walmart, Amazon DE (EUR), etc. The card shows the customer-paid currency; if you have any marketplace integrations active, you'll see those marketplaces' native currencies here. **Should I sum across currencies for a "total revenue" view?** No. Adding £100 + \$100 + €100 produces 300 of nothing. Use [Total Revenue](/nerve-centre/kpi-cards/bigcommerce/total-revenue) which applies a single-currency conversion, or apply an FX adjustment in this card. The native-currency view is for understanding the *mix* and the *trend per currency*, not for headline totals. **Why does the FX-equivalent column move when I haven't changed anything?** Because FX rates move daily. The native amounts are stable; the GBP / USD / EUR equivalents fluctuate with market rates. If you see GBP equivalent rising on flat USD revenue, GBP weakened (one USD now buys more GBP). Use a fixed rate (e.g. start-of-period FX) for stable historical comparisons, or accept the live-rate view for current-state assessment. **My PayPal settles to GBP only, do I see PayPal's USD orders here?** Yes. The card uses BC's order currency, which is the customer-paid currency, not the gateway-settlement currency. Your PayPal dashboard will show different numbers because PayPal converts at capture; this card shows what the customer actually paid before PayPal's conversion. **Why is my CAD share so small even though I get lots of Canadian traffic?** Canadian traffic doesn't equal Canadian payment. Many CA shoppers pay in USD if your storefront defaults to USD pricing for Canada. Check your BC currency configuration: under [Settings → Currencies](https://login.bigcommerce.com/deep-links/manage/settings/currencies), is CAD enabled and active? If only USD is offered to CA visitors, all CA orders show as USD here. **Can I set a fixed FX rate for historical comparison?** Yes. Configure the card with `fx_mode: fixed_at_period_start` (Vortex Mind setting) for stable comparison over time. Otherwise the default uses live rates which makes period-over-period comparisons noisy when FX moves materially. **A new currency appeared this period that I didn't enable, how?** Three causes: (1) Channel Manager added a new marketplace with its locked currency; (2) BC auto-detected a customer in a region and offered a new currency you previously enabled but never used; (3) a manual order was keyed in a non-default currency. Audit BC currency settings and Channel Manager listings. **My multi-currency store keeps prices fixed in each currency, do FX swings affect this card?** The native-currency revenue is unaffected by FX (you charge GBP customers GBP regardless of the GBP/USD rate). The FX-equivalent column moves with rates. If your business cares about home-currency settlement, the FX swings ARE real revenue impact (a 5% GBP strengthening means your USD revenue is worth 5% less in GBP); use the FX-equivalent column for that view. **Should I price differently per region or use auto-conversion?** **Strategically priced regions outperform auto-converted ones by 10-25% on AOV** for most BC merchants. Auto-conversion produces psychologically odd prices (£17.42 EUR equivalent vs a clean £17.99 / €19.99 dual-priced approach). For low-effort entry into a new currency use auto; for serious revenue allocate time to localised pricing. **My USD revenue is much higher than my US-customer-country revenue, how?** Because non-US customers pay in USD too (Amazon's marketplace is USD-locked regardless of buyer location). Cross-reference [BC Customer Countries](/nerve-centre/kpi-cards/bigcommerce/orders-by-country) for the buyer-country split; the currency split is a different cut of the same data. *** ### Tracked live in Vortex IQ Nerve Centre *Revenue by Currency* 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](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.