At a glance
Revenue decomposed by customer country (billing or shipping). Reveals geographic concentration, expansion opportunities, and tax-jurisdiction mix. Most ecommerce stores have a power-law distribution: 80% of revenue from 1-3 countries, 15% from a handful of secondary markets, 5% scattered across the long tail. The card is essential for tax compliance (knowing where to register for VAT/GST), localisation prioritisation (which translations and currencies to invest in), and shipping-cost optimisation (where to place fulfilment centres or pricing).
| What it counts | Total order revenue grouped by billing country (default) or shipping country (configurable). Computed across the current 30-day period. Includes successful payment status only. |
| Sample type | Backend API data from BigCommerce orders, refreshed on the standard data refresh. |
| Why country breakdown matters | (1) Tax registration: VAT/GST registration is required when revenue in a jurisdiction crosses a threshold (e.g., £85K in UK, €10K for EU OSS). The card surfaces approaching thresholds before non-compliance. (2) Localisation ROI: countries with growing revenue but no local content/currency are the highest-leverage localisation targets. (3) Shipping economics: revenue concentration in a country justifies a fulfilment centre or carrier partnership in that country. (4) FX exposure: multi-currency revenue creates FX risk that this card surfaces for finance. |
| Reading the value | (1) Identify top-3 countries (typically 70-90% of revenue). (2) Identify growth markets (countries rising vs prior period). (3) Cross-reference bc_aov_by_country to see whether high-AOV countries are well-served. (4) Flag countries approaching tax-registration thresholds. (5) Use as the input for localisation, currency, and shipping investment decisions. |
| Currency | currency (consolidated to merchant’s primary currency, with FX conversion shown for transparency). |
| Time window | 30D vsP. |
| Alert trigger | n/a (decomposition card; alerts live on per-country sub-thresholds). |
| Sentiment key | n/a (composition view). |
| Roles | owner, finance, marketing |
Calculation
Worked example
A UK-based BigCommerce home-and-garden store, revenue by country reading on Wednesday 15 May 26.| Country | Revenue (30D) | % of total | vs prior period | AOV | Notes |
|---|---|---|---|---|---|
| United Kingdom | £441,512 | 80.4% | -8.1% | £261 | Home market |
| Ireland | £38,950 | 7.1% | +12.4% | £288 | Growing, VAT-OSS implications |
| Germany | £24,180 | 4.4% | +5.6% | £302 | Growth market, DE localisation? |
| France | £15,500 | 2.8% | +1.2% | £258 | Stable |
| Netherlands | £11,200 | 2.0% | +18.7% | £315 | Fastest grower |
| United States | £9,800 | 1.8% | -3.4% | £210 | Long tail |
| Spain | £4,200 | 0.8% | +6.2% | £240 | Long tail |
| Other (15 countries) | £3,800 | 0.7% | mixed | £196 | Long tail |
| Total | £549,142 | 100.0% | -6.3% | £261 | - |
- UK dominates at 80%; Ireland + Germany + France + Netherlands together represent 16%. The store is structurally UK-anchored with meaningful EU traction. EU growth (+12.4% Ireland, +18.7% Netherlands, +5.6% Germany) is outpacing UK contraction (-8.1%), indicating the brand is finding product-market fit in the EU even as the home market softens.
-
VAT thresholds and OSS implications.
- UK: above the £85K VAT registration threshold (UK-resident store).
- EU OSS (one-stop shop): once cumulative EU revenue exceeds €10,000/year, the merchant must register for OSS to remit VAT to each EU jurisdiction. At the current pace (£90K+/year EU revenue), the store is well above the threshold and should already be OSS-registered. Confirm registration status; non-compliance is a meaningful tax exposure.
-
Localisation ROI prioritisation.
- Germany: £24K/month with +5.6% growth, AOV £302 (highest in the EU mix). German-language site + EUR pricing would likely lift conversion 20-40% on this audience.
- Netherlands: smaller absolute revenue but fastest growth. Watch for 60-90 days; if growth sustains, prioritise Dutch localisation or accept English-fluent NL audience.
- France: stable but not growing. French localisation is a meaningful investment (~30K-100K depending on scope) and may not pay back on current trajectory.
-
Shipping economics.
- UK: domestic shipping; no optimisation needed.
- Ireland: cross-border but English-speaking; current carrier likely fine.
- Germany / France / Netherlands: EU shipping. Consider a Netherlands or Belgium fulfilment centre once combined EU revenue exceeds £100K/month (currently £93K/month, close to threshold).
-
FX exposure.
- 80% UK (GBP, no FX risk for a UK merchant).
- 14% EU (EUR, exposed to GBP/EUR fluctuations). On £77K/month of EUR revenue, a 5% FX swing is £3,850/month volatility.
- 2% US (USD, smaller exposure).
- Hedge consideration: above £50K/month of EUR revenue, a forward contract or hedging arrangement becomes worth the operational cost. Discuss with finance.
-
Recommended actions:
- Confirm EU OSS registration is in place (if not, register immediately; the £90K+ exposure is real).
- Prioritise German localisation for the next quarter, highest leverage in the current geography mix.
- Watch Netherlands for 60-90 days; if growth sustains, add Dutch language and shipping options.
- Review FX hedging for EUR exposure above £50K/month threshold.
- Monitor UK contraction, cross-reference
revenue_trendfor the home-market trajectory; this is the biggest single absolute revenue lever.
- Read the country distribution. Identify top-3 (usually 70-90% of revenue).
- Flag any country approaching tax-registration thresholds.
- Identify growth markets (high vs P delta, growing share).
- Decide localisation, shipping, FX investments based on revenue concentration.
- Re-audit quarterly; geography mix shifts slowly but materially over 12-24 months.
| Time horizon | Action |
|---|---|
| First 1 hour | Read distribution. Flag tax-registration thresholds. |
| First week | Confirm tax compliance for top 3 markets. |
| First quarter | Prioritise localisation for top growth market. |
| Annual | Review FX hedging for material non-home revenue. |
Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
bc_aov_by_country | AOV by country; complements revenue. |
bc_orders_by_state | Order count by state/region. |
bc_revenue_by_currency | Currency mix; complements country mix. |
bc_channel_currency_mix | Per-channel currency mix. |
bc_revenue_by_channel | Channel decomposition. |
total_revenue | Total revenue companion. |
Reconciling against the vendor’s own dashboard
Where to look in BC: Analytics → Insights → Customers (with country filter); Reports → Orders by Country (Plus / Pro plans). Why our number may differ:| Reason | Direction | What to do |
|---|---|---|
| Country source. BC may use shipping country; Vortex IQ uses billing by default. | Variable | Confirm setting. |
| FX timing. Multi-currency: FX rate at order time vs at report time may differ. | Marginal | Use consistent FX timing. |
| B2B order treatment. B2B orders may have different country fields. | Variable | Confirm B2B handling. |
| Period boundary. BC defaults to calendar; Vortex IQ uses 30-day rolling. | Variable | Match periods. |
klaviyo.klv_segments_overview (audience geography) for the marketing dimension, and tax-platform integrations (Avalara, TaxJar) for the compliance dimension.
Quick rule: confirm billing-vs-shipping country source first; FX timing second.
Known limitations / merchant FAQs
Q: Should we use billing country or shipping country? Billing for tax purposes (which jurisdiction taxes the sale); shipping for fulfilment purposes. The card defaults to billing because tax compliance is usually the higher-stakes use case. Configurable per profile. Q: We sell to “Unknown” country a lot, what is that? Orders without a billing country populated (rare for credit-card orders, more common for digital wallets like Apple Pay/Google Pay where address may not be captured by default). Audit the checkout: ensure country is required at checkout. Even small “Unknown” populations create tax-compliance gaps. Q: We’re approaching the EU OSS threshold. What do we do? Register for OSS via your home-country tax authority before crossing the threshold. Most merchants register pre-emptively even at modest EU revenue because the operational overhead is small and the compliance benefit is large. UK merchants register via HMRC if non-EU; EU-resident merchants via their home country. Q: Our German revenue is rising but no local site. How much would a German site lift conversion? Typically 20-40% on the German audience. The investment scope: translation (£3-10K), local payment methods (SEPA, GiroPay added, £2-5K integration), local shipping rates (free if Vortex IQ shipping connectors), local customer-service email/phone (£5-15K/year). At £24K/month of German revenue, a 25% lift is £6K/month, which pays back localisation in 4-12 months. Q: Should we list every country or just the top 10? Card defaults to top 10 + “Other” bucket. Long-tail countries (less than 0.5% of revenue) rarely justify individual focus. The “Other” bucket is the input to localisation prioritisation as it grows. Q: How does FX affect this card? For multi-currency stores, all values are converted to the merchant’s primary currency at the order’s FX rate (BC’s recorded rate at order time). Period-over-period changes can include FX-driven movement; for FX-stripped comparisons, use constant-currency methodology. Vortex Mind reports support constant-currency views. Q: B2B orders, do they show in this card? Configurable. By default yes, since B2B revenue is real revenue and tax-compliance includes B2B. For stores where B2B is dominant and the card is mainly used for D2C marketing decisions, filter B2B out at profile level. Q: How does this card differ frombc_aov_by_country?
This card is total revenue per country (volume × AOV). bc_aov_by_country is the per-order average per country. Together they decompose the geography story: revenue tells you where to invest; AOV tells you how to position.