> ## 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. # Channel Mix (Amazon vs DTC), Amazon Seller Central > Channel Mix (Amazon vs DTC) for Amazon Seller Central accounts. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it. **Card class:** [Sensitivity](/nerve-centre/overview#card-classes-explained) • **Category:** [Revenue at Risk](/nerve-centre/connectors#connectors-by-type) ## At a glance > How your revenue splits between Amazon and your own DTC store, shown as a share. This is the platform-concentration card. A high Amazon share means strong marketplace performance but also dependence on a channel you do not own, where Amazon sets the fees, owns the customer relationship, and can change the rules. The card lets an owner or CFO see channel balance at a glance and watch for the dependency creeping past a healthy line. It is a cross-channel card by definition: Amazon revenue versus DTC revenue. | | | | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **What it counts** | The share of total revenue coming from Amazon versus your DTC store over the period, shown as a donut. Amazon revenue is the gross ordered product sales from this connector; DTC is the connected storefront's revenue. | | **Cross-channel basis** | Requires both Amazon and a DTC channel connected. With only Amazon linked, the mix reads 100% Amazon and the card carries no real signal. | | **Why it matters** | Channel concentration is platform risk. Heavy Amazon dependence means exposure to fee increases, account suspensions, policy changes, and loss of the direct customer relationship. A balanced mix is more resilient. | | **The healthy line** | There is no single correct split; it varies by category and strategy. The card alerts when Amazon dependency runs high (above roughly 70%), as a prompt to consider DTC investment, not as a verdict. | | **Comparability caveat** | Amazon revenue here is gross of fees; DTC revenue definitions vary by storefront. Read the share as a directional balance, not a precise like-for-like. | | **Chart** | Donut, Amazon share vs DTC share. | | **Unit** | Currency (underlying), shown as share. | | **Time window** | `90D`. | | **Alert trigger** | `Amazon dependency >70%`. | | **Roles** | owner, finance | ## Calculation Calculated automatically from your Amazon Seller Central 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 consumer-brand running both Amazon and a Shopify DTC store. Period: 01 Feb 26 to 30 Apr 26 (90D). | Channel | 90D revenue (illustrative) | Share | | ------------------------------ | -------------------------- | -------- | | Amazon (ordered product sales) | £312,000 | 74% | | DTC (Shopify storefront) | £110,000 | 26% | | **Total** | **£422,000** | **100%** | ```text theme={null} Amazon share = 74% → above the 70% dependency alert → card raised DTC share = 26% Trend (vs prior 90D) = Amazon share up from 69%, DTC growth flat ``` Three things to notice: 1. **74% is over the dependency line.** The card raises because Amazon now drives nearly three quarters of revenue. That is not a crisis, but it is a strategic flag: the more revenue sits on Amazon, the more a fee change, policy shift, or account issue can hurt. The alert is a prompt to weigh DTC investment, not a problem to fix today. 2. **The trend matters more than the snapshot.** Amazon share rose from 69% to 74% while DTC stayed flat, so dependency is increasing. A business that is comfortable at 74% but drifting toward 85% should act before the concentration becomes a single point of failure. Watch the direction across periods. 3. **The split is directional, not exact.** Amazon revenue here is gross of fees and DTC revenue follows the storefront's own definition, so the two sides are not perfectly like-for-like. Read the share as a balance indicator, and use [Amazon Share of Total Revenue](/nerve-centre/kpi-cards/amazon-seller/amazon-share-of-total-revenue) for the headline concentration figure. The card is raised at 74%. The strategic action is not on Amazon itself but on diversification: invest in DTC acquisition and retention so the mix rebalances over time, while keeping the Amazon channel healthy. Pair with [Amazon Share of Total Revenue](/nerve-centre/kpi-cards/amazon-seller/amazon-share-of-total-revenue) and the [Net Revenue (after fees + refunds)](/nerve-centre/kpi-cards/amazon-seller/net-revenue-after-fees-refunds) view to judge which channel actually contributes most margin. ## Sibling cards merchants should reference together Channel balance is a strategic read; these give the components and the risks: | Card | Why pair it with Channel Mix | | ---------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- | | [Amazon Share of Total Revenue](/nerve-centre/kpi-cards/amazon-seller/amazon-share-of-total-revenue) | The headline concentration figure. This donut shows the split; that card states the dependency percentage directly. | | [Total Revenue](/nerve-centre/kpi-cards/amazon-seller/total-revenue) | The Amazon side of the mix. The numerator behind the Amazon share. | | [Net Revenue (after fees + refunds)](/nerve-centre/kpi-cards/amazon-seller/net-revenue-after-fees-refunds) | Margin matters more than gross share. A channel that is a smaller share of revenue can be a bigger share of profit. | | [Catalogue Drift Revenue at Risk](/nerve-centre/kpi-cards/amazon-seller/catalogue-drift-revenue-at-risk) | The more revenue runs through Amazon, the more cross-channel drift between Amazon and DTC matters. | | [MAP Violation Risk (vs DTC)](/nerve-centre/kpi-cards/amazon-seller/map-violation-risk-vs-dtc) | Pricing discipline between the two channels protects the higher-margin DTC side. | ## Reconciling against Amazon Seller Central **Where to look in Seller Central:** Seller Central can only show you the Amazon half of this card. There is no native cross-channel mix view, because Amazon has no visibility of your DTC store. > **Amazon side:** Seller Central → Reports → Business Reports → Sales and Traffic, "Ordered product sales" for the 90D window. > **DTC side:** your storefront's own analytics (for example Shopify Analytics → Total sales) for the same window. The mix is Amazon revenue divided by the sum of Amazon plus DTC revenue. Both halves come from outside a single Amazon report, which is why this is a Vortex IQ cross-channel card rather than a Seller Central metric. **Timing and reporting-lag table:** | Topic | Detail | | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Two data sources** | Amazon and DTC revenue come from different connectors with different reporting cadences; the mix is only as fresh as the slower of the two. | | **Revenue definitions** | Amazon revenue is gross ordered product sales; DTC revenue follows the storefront definition. The share is directional, not a precise like-for-like. | | **Currency** | If the two channels report in different currencies, the share is meaningful only once both are in a common currency; read per-currency if they differ. | | **Window alignment** | Both sides use the same 90D window, but each channel's own reporting lag applies to its half. | **Why our number may legitimately differ from a manual check:** | Reason | Direction | Why | | ------------------------------- | ---------------- | -------------------------------------------------------------------------------------------------------------------------- | | **Revenue-definition mismatch** | Either direction | Amazon gross ordered product sales vs the DTC storefront's revenue definition are not identical; the share is directional. | | **Connector freshness** | Either direction | Each channel has its own sync lag; a manual same-day check of one side may differ from the card's last combined sync. | | **Refund treatment** | Either direction | Amazon revenue here is gross of refunds; the DTC side may net them, slightly shifting the share. | **Cross-connector reconciliation:** | Card | Expected relationship | What causes legitimate divergence | | --------------------------- | ----------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | | DTC / Shopify total revenue | **This card is the join.** It only exists because both channels are connected; the mix is the ratio between them. | With only Amazon connected, the mix reads 100% Amazon and carries no signal. Connect the DTC channel for the card to mean anything. | ## Known limitations / merchant FAQs **What is a healthy Amazon-vs-DTC split?** There is no single right answer; it depends on category, margin, and strategy. Some brands thrive at 80% Amazon, others deliberately keep Amazon under half to protect the direct customer relationship. The card alerts above roughly 70% Amazon dependency as a prompt to consider the risk, not as a rule that you are doing something wrong. **Why does heavy Amazon dependence count as "revenue at risk"?** Because Amazon is a channel you do not control. The more revenue runs through it, the more exposed you are to fee increases, policy changes, listing suppressions, or an account suspension, any of which can hit a large slice of revenue at once. A balanced channel mix is more resilient. **Is the split exactly like-for-like?** No. Amazon revenue here is gross of fees and the DTC side follows the storefront's own revenue definition, so the two are not perfectly comparable. Read the share as a directional balance and a trend, not a precise accounting split. For the headline figure use [Amazon Share of Total Revenue](/nerve-centre/kpi-cards/amazon-seller/amazon-share-of-total-revenue). **The card reads 100% Amazon. Is that real?** Only if no DTC channel is connected. The card needs both Amazon and a DTC storefront linked to compute a mix. With only Amazon connected it defaults to 100% and carries no useful signal; connect the DTC channel to make it meaningful. **Should I act the moment dependency crosses 70%?** Not necessarily immediately, but it is the right moment to think strategically. Watch whether the trend is rising or stable. A stable 74% may be fine for your model; a share climbing steadily toward 85% is a concentration risk worth addressing through DTC investment before it becomes a single point of failure. *** ### Tracked live in Vortex IQ Nerve Centre *Channel Mix (Amazon vs DTC)* is one of hundreds of KPI pulses Vortex IQ tracks across Amazon Seller Central 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.