At a glance
Order count split by customer’s billing-country code (or shipping-country, configurable). The international-expansion view, where in the world your customers are coming from, where you have ad-targeting opportunity, and where shipping logistics need investment.
| What it counts | COUNT(orders) GROUP BY billing_address.country over 30 days. Each order attributed to the country code on the billing address by default; toggle to shipping country. |
| VAT / tax treatment | n/a (count metric). |
| Shipping | n/a (the country is geographic, not shipping-cost). |
| Discounts | n/a. |
| Refunds | Refunded orders included (the country is still geographic fact). |
| Cancelled / voided orders | Cancelled orders excluded by default. |
| Currency | n/a (this is country, not currency; though strongly correlated). |
| Channels / sources | All channels contribute. Marketplace orders provide country via the marketplace’s billing-address pass-through; some marketplaces strip the address and only provide a region (Amazon US sees “United States” without zip / state precision via Channel Manager in some configurations). |
| Billing vs shipping | Default is billing country. Toggle to shipping for the “where are goods physically going” view; useful for logistics decisions. The two diverge for gift orders (billing US, shipping UK), expat orders (billing home, shipping current location), and corporate orders (billing HQ, shipping branches). |
| Country-code normalisation | We normalise to ISO-3166 alpha-2 codes (US, GB, DE, FR, etc.). BC stores country codes consistently; minor variations (e.g. “GB” vs “UK”) are normalised. |
| B2B Edition note | B2B accounts often have one HQ billing country with shipping spread across branches in many countries. The split between billing and shipping country views can be very different for B2B-heavy stores; review both. |
| Time window | 30D (rolling 30 days, vs prior 30 day comparison) |
| Alert trigger | None on this card directly. |
| Roles | owner, marketing |
Calculation
Worked example
A UK-based homewares brand on BigCommerce Pro selling internationally, 30-day window 14 Apr 26 to 14 May 26.| Country | Code | Orders | Share | AOV | Total revenue | Verdict |
|---|---|---|---|---|---|---|
| United Kingdom | GB | 4,820 | 64% | £88 | £424,160 | Home market, dominant |
| United States | US | 1,180 | 15.7% | $112 | $132,160 | Strong export market |
| Germany | DE | 480 | 6.4% | €92 | €44,160 | Solid EU presence |
| France | FR | 280 | 3.7% | €88 | €24,640 | Growing EU |
| Ireland | IE | 220 | 2.9% | €82 | €18,040 | Cross-border IE |
| Netherlands | NL | 180 | 2.4% | €94 | €16,920 | Steady |
| Spain | ES | 140 | 1.9% | €86 | €12,040 | Modest |
| Australia | AU | 120 | 1.6% | $138 AUD | $16,560 AUD | Long-distance |
| Canada | CA | 80 | 1.1% | $108 CAD | $8,640 CAD | Long-distance |
| Other (10 countries) | mixed | 90 | 1.2% | mixed | small | Tail |
| Total | 7,590 | 100% | (mixed) | (mixed) |
- 64% UK / 36% international is healthy global mix. Pure-domestic UK stores would be 95%+ GB; this merchant has clearly invested in international expansion. The next 5 markets (US, DE, FR, IE, NL) account for 31% of orders combined.
- **US at 15.7% with 112 vs £88 ~ $108) suggests US customers are buying higher-tier items. Investigate which SKUs drive US orders, are they specific premium items? Does Amazon US cannibalise the direct US channel (cross-reference BC Revenue by Channel)?
- EU markets (DE + FR + IE + NL + ES) = 17% combined. Post-Brexit shipping complexity has hurt many UK→EU exporters; if these markets are growing, your EU logistics setup is working. If declining, customs / VAT / shipping-cost friction is killing demand.
- **Australia at 120 orders / 138 vs $108 for closer markets) reflects either premium-product mix or shipping-included pricing.
- The 10-country tail at 90 orders combined rarely justifies dedicated investment. Maintain access (don’t block these countries) but don’t allocate marketing spend until any single tail country crosses 1% of orders.
- Double down on US allocate ad spend, consider US-warehouse fulfilment to reduce shipping time / cost.
- EU customs / VAT review ensure your post-Brexit IOSS / OSS registrations are current; broken registration = customs holds = customer experience disaster.
- Australia logistics review is the high AUD AOV genuine premium demand or shipping-cost-baked-in? Worth optimising.
- Tail-country audit quarterly any tail country crossing 1% of orders deserves localised pricing / shipping consideration.
- Cross-reference with BC Revenue by Currency country and currency are correlated but not identical; both views together inform expansion strategy.
Sibling cards merchants should reference together
| Card | Why pair it with Customer Countries |
|---|---|
| BC AOV by Country | Per-country AOV; the dollar lens of this card. |
| BC Revenue by Currency | Currency split; correlates with country but not identical. |
| Top Cities | Within-country city-level view; useful for top markets. |
| BC Orders by State | US-state-level granularity (or equivalent in other countries). |
| BC Channel Currency Mix | Channel × currency cross-tab. |
| Customer Count | Total customer base; this card is country-split. |
| Total Revenue | Total revenue context. |
google_analytics.ga_revenue_by_country | GA4 country attribution; should track within ±10%. |
Reconciling against the vendor’s own dashboard
Where to look in BigCommerce Control Panel: Analytics → Customer Reports on Plus / Pro / Enterprise plans includes a per-country breakdown. Orders → All orders can be filtered by billing country for spot checks. Customers → View shows registered customer countries (different from order country, since registered customers may not have ordered in this period). Why our number may legitimately differ from BC:| Reason | Direction |
|---|---|
| Billing vs shipping. We default to billing; BC may default to shipping in some reports. | Different totals on gift / corporate orders |
| Cancelled orders. We exclude; BC may include. | BC HIGHER counts |
| Time-zone. UTC default vs BC store time. | Boundary differences |
| Channel coverage. We include all channels; BC reports may default to web. | Different totals |
| Marketplace orders. Some marketplaces strip address granularity; we attribute to country at the resolution available. | Possible attribution differences |
| Country-code normalisation. We use ISO-3166 alpha-2; BC stores may have legacy codes. | Cosmetic differences only |
| Card | Expected relationship | What causes legitimate divergence |
|---|---|---|
google_analytics.ga_revenue_by_country | GA4’s country attribution should match within ±10%. | GA4 misses 10-25% to ad blockers; uses IP geolocation rather than billing address (different mechanism). |
google_ads.ga_geo_targeting_performance | Ad-spend by country should align with order-share by country if targeting is right. | Targeting is leading; orders are trailing. |