Skip to main content
Card class: Cross-Channel • Category: Ecommerce Platform
How much of total commerce revenue rides on Amazon vs the DTC store. Concentration risk if >40%, one suspension and the lights go out.

​
At a glance

The percentage of total commerce revenue that rides on Amazon vs the DTC BC storefront and other channels. Cross-connector view: BC total_inc_tax summed across Amazon channel_id values plus Amazon SP-API revenue (where connected) divided by total BC revenue. Concentration risk if >40%, one Amazon suspension and the business loses 40%+ of revenue overnight.
What it countsSUM(BC.total_inc_tax) WHERE channel_id is an Amazon Channel Manager ID + SUM(amazon_sp.amazon_revenue if connected) ÷ SUM(BC.total_inc_tax across all channels) × 100. The cross-connector blend ensures we capture Amazon orders even if they don’t fully sync into BC.
VAT / tax treatmentTax-inclusive on the BC side (total_inc_tax); Amazon SP-API may report tax-exclusive on some marketplaces. Material for international stores; the shape is internally consistent for US-only Amazon stores.
ShippingIncluded (BC total_inc_tax semantics).
DiscountsAlready deducted.
RefundsNot deducted (gross share). For net-of-refund use BC Refund Rate per channel.
Incomplete / Declined ordersExcluded. Marketplace channels (including Amazon) almost never produce these because they pre-authorise payment, but the card’s denominator excludes them store-wide for consistency with the captured-only shape.
Cancelled ordersExcluded.
CurrencyMulti-currency without FX. Amazon US, UK, EU as separate channels; per-region drift in the share is exposed as separate sub-rows.
Concentration thresholds<20% = healthy diversification, 20-40% = material channel, 40-60% = concentration risk, >60% = dangerous dependency. The single-suspension event has historically taken 3-6 months for stores to recover from at >50% Amazon-share.
Time window30D vsP
Alert triggerAmazon share >40% (channel concentration), fires when Amazon dependency reaches the warning band.
Rolesowner, finance, marketing

​
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 US homewares brand on BigCommerce Enterprise with Amazon Channel Manager (US, UK, CA). The 30-day window covers 14 Mar 26 to 12 Apr 26.
SourceRevenueSharevsP deltaRisk verdict
BC Stencil web (channel_id = 1)$352,16075.4%-3.1%Primary, healthy
Amazon US (Channel Manager)$54,46811.7%+24.2%Material, growing
Amazon UK (Channel Manager)$12,1802.6%+18.5%Small but growing
Amazon CA (Channel Manager)$1,9200.4%-2.0%Tiny, stable
Other (Facebook, POS)$14,9643.2%-5.4%Marginal
Phantom revenue (Incomplete + Declined, web only)$31,4146.7%n/a(not in share calc)
Amazon total share (this card)$68,56814.7%+22.0%Material, watch trajectory
What’s interesting:
  1. 14.7% Amazon share is in the healthy band but with strong upward velocity (+22% vsP). At current trajectory the store crosses the 20% “material channel” threshold in 6-8 weeks and the 40% concentration-risk threshold in roughly 12 months. Trajectory matters more than current level.
  2. Amazon US dominates within the Amazon split. UK and CA are early-stage growth channels; US is the load-bearing piece. A US-specific Amazon issue would take down 80% of the Amazon share simultaneously.
  3. Diversification check, the alternative channels are shrinking (Other -5.4% vsP). The store is moving from “diversified” to “Amazon plus web”, which is fine if intentional but should be a deliberate strategy. If you didn’t choose this concentration, course-correct now while the share is still recoverable.
  4. The single-Amazon-suspension scenario: a 14-day Amazon suspension for any reason would lose ~32kofrevenueimmediately.At3032k of revenue immediately. At 30%+ share, the same suspension would lose ~65k+; at 50% share, $109k+. The cost scales linearly; the recovery time scales exponentially.
How to use this card:
  1. Track quarterly trajectory, the velocity matters more than the level.
  2. Set diversification goals if Amazon share is climbing: invest in BC web SEO, paid ads to web, email program (see BC XC Klaviyo Email Revenue Share), other marketplace channels.
  3. Build a contingency plan at 20%+ Amazon share: what happens if Amazon suspends for 14 days? Document the operational response.
  4. Pair with BC Channel Revenue Mix for the full per-channel context.

​
Sibling cards merchants should reference together

CardWhy pair it with Amazon Revenue Share
BC Channel Revenue MixThe full channel breakdown. Amazon share is one pie slice; this card spotlights it.
BC Channel Revenue TrendThe over-time trajectory; complements the snapshot here.
BC XC Klaviyo Email Revenue ShareThe diversification companion. Healthy stores don’t depend on a single source (Amazon, email, paid).
BC XC Catalogue DriftAmazon-specific catalogue hygiene; high drift on Amazon erodes the channel without reducing share.
BC XC Paid Traffic WasteThe other side of acquisition diversification.
BC Alert Channel Revenue DropThe real-time guardian for any single channel disappearing, including Amazon.
amazon_sp.amazon_total_revenueThe Amazon-side revenue input; should match the Amazon channel slice within ±5%.
amazon_sp.amazon_account_healthThe leading indicator for suspension risk; pair to anticipate share loss.

​
Reconciling against the vendor’s own dashboard

Where to look in BigCommerce Control Panel: Channel Manager → Amazon shows the Amazon integration health and recent sync activity. Analytics → Sales on Plus / Enterprise has a Sales by channel view with the Amazon slice. For a complete Amazon picture, Amazon Seller Central → Reports → Business Reports is authoritative. Why our number may legitimately differ from Amazon Seller Central:
ReasonDirection
Channel Manager sync gaps. Some Amazon orders take 2-24 hours to flow into BC; the card shows BC-indexed revenue, not real-time Amazon revenue.Vortex IQ LAGS Amazon by hours
Currency. Amazon Seller Central reports in marketplace currency; we sum without FX.Material for international Amazon stores
Refunds and adjustments. Amazon’s reports include various adjustments (FBA fee credits, A-to-Z refunds) that don’t flow through BC at the order layer.Vortex IQ HIGHER (gross only)
Multi-channel fulfillment. Amazon orders fulfilled via FBA show up in BC; orders fulfilled via Vendor Central don’t.Vortex IQ LOWER for vendor-central stores
Cross-connector reconciliation:
CardExpected relationshipNotes
amazon_sp.amazon_total_revenueThe Amazon-side total.Should align with the Amazon channel slice within ±5%.
Total RevenueThe denominator base.Direct dependency.
BC Channel Revenue MixThe full pie chart.Amazon is one slice.

​
Known limitations / merchant FAQs

My share is 8%, can I scale Amazon harder? Yes, with caveats. Amazon scaling typically delivers fast revenue growth (90-180 days from listing to material velocity) but at the cost of brand control and unit economics (8-15% Amazon commission, FBA fees, advertising costs). Decide deliberately whether you want a 30%-Amazon-share business or a 10%-Amazon-share business; both are viable, but they call for different operating models. My share is 55%, what should I do? Diversify, urgently. A 55%-Amazon-share business has fragile economics: a single suspension event historically costs 30-60% of trailing-12-month revenue and takes 6-12 months to recover. Invest in BC web SEO, paid social, email program, other marketplaces (eBay, Walmart) for 6-12 months until share normalises to 30% or below. Diversification is the single highest-priority strategic move at >50% Amazon dependency. Why doesn’t my Amazon share match Seller Central? Most commonly because we use BC-indexed revenue (which lags Amazon by 2-24 hours for new orders) plus tax/refund handling differs. The directional view is reliable; the absolute dollar match is ±5%. For exact Amazon revenue, use Seller Central directly; for cross-channel share context, use this card. Should I include Amazon Vendor Central revenue here? Vendor Central orders don’t typically flow through Channel Manager (the relationship is wholesale, not retail), so by default they’re excluded. Some merchants want to include Vendor revenue for the full Amazon-exposure view; configure this in Vortex Mind if applicable. The bigger question, a Vendor + Seller-Central merchant is functionally Amazon-dependent regardless of how it’s bucketed. My Amazon share dropped 8 points this month, what changed? Three usual causes: (1) Web revenue grew, the share dropped because the denominator grew, not because Amazon shrunk. Check Amazon absolute revenue separately. (2) An Amazon listing got suppressed (BSR drop, image rejection, policy flag), check Amazon Seller Central → Account Health. (3) A competitor seller is winning the buy box, check the buy-box-share metric in your Amazon SP-API connector. Should I worry about Amazon UK if I’m primarily a US store? Only at scale. UK Amazon stores carry different operational requirements (VAT registration, EU representation post-Brexit, packaging rules) that aren’t trivial to set up. If your UK Amazon revenue is <5k/month,theoperationaloverheadmayexceedtherevenuebenefit.Above5k/month, the operational overhead may exceed the revenue benefit. Above 20k/month, dedicated UK ops is justified. What does “channel concentration” mean in practical terms? It means: if this single source of revenue disappears, what fraction of your business goes with it? At 40% Amazon share, four out of every ten dollars depend on Amazon’s continued goodwill. Amazon can suspend you with hours of notice; recovery takes months. Concentration is a continuous business risk measured in months-of-runway. Multi-currency Amazon stores: how does the share work? We compute share per-currency where possible (Amazon US + Amazon UK reported separately), then aggregate. The headline percentage is mixed-currency without FX, prefer the per-region breakdown for international stores. My DTC strategy explicitly de-prioritises Amazon, why does the card flag me? The alert is set at 40% by default to fire on dependency risk. If you’re explicitly running a high-Amazon strategy with eyes open (e.g. Amazon-first brands deliberately keeping web at 5-10%), the alert is informational, not actionable. Configure the alert threshold higher (60-70%) for stores with this strategy. Should I close my Amazon channel to reduce concentration risk? No, except in extreme cases. Closing the channel forfeits the revenue without the diversification work elsewhere paying off. The right move is “grow other channels until Amazon’s share naturally drops”. Cutting Amazon is a 6-month revenue hit; growing other channels is a slow-build win.

​
Tracked live in Vortex IQ Nerve Centre

Amazon Revenue Share vs DTC 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.