> ## 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. # Marketplace Revenue, Shopify > Marketplace Revenue for Shopify stores. Revenue from marketplace partner orders such as Mirakl, Debenhams and Rackhams. How to read it, why it matters, and how to act on it. **Card class:** [Non-Hero](/nerve-centre/overview#card-classes-explained) • **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type) > Revenue from marketplace partner orders (Mirakl / Debenhams / Rackhams). ## At a glance > Gross revenue from your marketplace-partner orders in the period, the orders fulfilled for department-store and operator-platform partners such as Mirakl, Debenhams, and Rackhams, isolated by their order tags and combined into one figure. This is your non-DTC, non-wholesale third leg: demand that comes through partner storefronts rather than your own. It is gross revenue, the same arithmetic as Total Revenue, restricted to the marketplace tags. | | | | ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **What it counts** | `SUM(totalPrice)` across orders in the window carrying any of the marketplace partner tags (default Mirakl, Debenhams, Rackhams), combined. | | **How "marketplace" is identified** | By the partner order tags. Orders routed from a marketplace partner are tagged with the partner name; this card sums the configured marketplace tags. **This is distinct from [Marketplace Revenue Share (Amazon)](/nerve-centre/kpi-cards/shopify/marketplace-revenue-share)**, which is an Amazon-specific percentage from a separate connector. This card is a currency value across non-Amazon partner marketplaces. | | **VAT / tax treatment** | Inherits each order's `taxesIncluded` mode. Partner orders typically follow the same UK VAT-inclusive convention as DTC for consumer-facing marketplaces. | | **Shipping** | **Included** (part of `totalPrice`), though many marketplace partners control fulfilment and shipping terms, so the shipping line may differ from your DTC norms. | | **Discounts** | Deducted (post-discount). Partner-run promotions you don't control are reflected here. | | **Refunds** | **NOT deducted.** Gross figure. Marketplace returns are often processed on the partner's timeline. | | **Cancelled / voided orders** | Included if Shopify indexed them. | | **Currency** | **Multi-currency arithmetic sum WITHOUT FX conversion.** Filter by currency if partners transact in different currencies. | | **Channels / sources** | Identified by tag, not by Shopify sales channel. Several partners may arrive through one integration, so the tag is the only reliable separator. | | **Time window** | `30D` (default 30D rolling) | | **Alert trigger** | Configurable. Marketplace revenue can be lumpy and partner-driven; trend alerts work better than absolute-drop alerts. | | **Roles** | owner, marketing | ## Calculation ``` SUM(totalPrice WHERE tag IN ['Mirakl','Debenhams','Rackhams', ...]) WHERE date BETWEEN [period_start, period_end] ``` ## Worked example A UK homewares brand listed on three marketplace partners alongside its own DTC store. Each partner's orders carry the partner-name tag. The 30-day window covers 14 Mar 26 to 12 Apr 26. | Partner (tag) | Orders | Revenue | Note | | ----------------------------------- | ------- | ----------- | ---------------------------------- | | Debenhams | 132 | £11,200 | Largest partner this period | | Mirakl | 78 | £10,800 | Operator-platform listings | | Rackhams | 95 | £8,200 | Regional department store | | **Marketplace Revenue (this card)** | **305** | **£30,200** | Roughly 14% of total store revenue | Three things to notice: 1. **This is one number from three partners.** The card combines the marketplace tags so the board sees the total non-DTC, non-wholesale leg at a glance. To split it back out per partner, read [Revenue by Sales Channel (Tag)](/nerve-centre/kpi-cards/shopify/revenue-by-sales-channel-tag), where each partner is its own bar. 2. **Marketplace demand is partner-driven, not yours.** A spike in the Debenhams slice may come from a Debenhams-side promotion or homepage placement you had no hand in. That makes marketplace revenue less controllable than DTC; track it for dependency and concentration, not as a lever you pull directly. 3. **Partner concentration is the risk to watch.** Debenhams alone is 37% of this card. If that partner delists you or changes terms, marketplace revenue drops a third overnight. The healthy shape is several partners of similar size, not one dominant relationship. ## Sibling cards merchants should reference together | Card | Why pair it with Marketplace Revenue | | ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- | | [Revenue by Sales Channel (Tag)](/nerve-centre/kpi-cards/shopify/revenue-by-sales-channel-tag) | The per-partner breakdown; this card combines those bars, that card splits them. | | [Marketplace Revenue Share (Amazon)](/nerve-centre/kpi-cards/shopify/marketplace-revenue-share) | The Amazon-specific share metric. Read alongside to see all marketplace exposure, Amazon and partner. | | [B2C Revenue Only](/nerve-centre/kpi-cards/shopify/b2c-revenue-only) | The DTC leg; marketplace as a share of DTC plus marketplace shows partner dependency. | | [Total Revenue](/nerve-centre/kpi-cards/shopify/total-revenue) | The aggregate; marketplace as a percentage of it sizes the partner channel. | | [Refund Rate](/nerve-centre/kpi-cards/shopify/refund-rate) | Marketplace returns can run higher than DTC; pair to watch partner-channel quality. | | [Top Products by Revenue](/nerve-centre/kpi-cards/shopify/top-products-by-revenue) | Partners often buy a different SKU mix than DTC; pair to see what sells where. | ## Reconciling against Shopify Admin **Where to look in Shopify Admin:** [Orders](https://admin.shopify.com/orders) → filter by **Tagged with** each marketplace tag in turn (Mirakl, Debenhams, Rackhams), set the same window, and sum `totalPrice` across the exports. The combined total is this card. Shopify has no native marketplace-revenue report for non-Amazon partners, so the tag-filter sum is the reconciliation path. Other Shopify Admin views and why they differ: * **Reports → Sales by sales channel**: if all partners arrive via one integration, they collapse into a single channel here, hiding the per-partner split this card relies on. * **Each marketplace operator's own seller portal**: the partner's authoritative figure, on the partner's timeline and refund treatment. **Why our number may legitimately differ from Shopify:** | Reason | Direction | Why | | -------------------- | ------------ | --------------------------------------------------------------------------------------------------------------- | | **Tag coverage** | Ours lower | A partner order that wasn't tagged is missed. New partners not yet added to the card's tag set are also missed. | | **Partner timing** | Either | Marketplace orders may sync to Shopify on a delay; the partner portal can be ahead of Shopify. | | **Refund treatment** | Ours higher | Gross here; partners net returns on their own schedule. | | **Multi-currency** | Ours blended | No FX conversion. | **Cross-connector reconciliation:** | Card | Expected relationship | What causes legitimate divergence | | --------------------------------------------------------------------- | -------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Marketplace operator dashboards (Mirakl, Debenhams, Rackhams portals) | Each partner slice should track its portal | Portals report on fulfilment and settlement timelines that differ from Shopify's order-created date; reconcile monthly, not daily. | | [`amazon_sp.amazon_revenue`](/nerve-centre/amazon_sp/amazon_revenue) | Amazon is a separate marketplace, NOT in this card | Amazon revenue sits in its own connector and in [Marketplace Revenue Share (Amazon)](/nerve-centre/kpi-cards/shopify/marketplace-revenue-share); do not expect it here. | ***
Same-metric documentation cross-reference (for agencies running multiple platforms) The same partner-marketplace concept lives on other commerce platforms. This is **not a reconciliation**, your Shopify store doesn't have a parallel store on BigCommerce or Adobe Commerce. These cross-links exist so agencies running multi-platform client books can navigate between identical metrics. * [`bigcommerce.marketplace_revenue`](/nerve-centre/kpi-cards/bigcommerce/marketplace-revenue) * [`adobe_commerce.marketplace_revenue`](/nerve-centre/kpi-cards/adobe-commerce/marketplace-revenue)
## Known limitations / merchant FAQs **Does this include Amazon?** No. This card covers partner marketplaces identified by order tag (default Mirakl, Debenhams, Rackhams). Amazon is a separate connector and is measured by [Marketplace Revenue Share (Amazon)](/nerve-centre/kpi-cards/shopify/marketplace-revenue-share). Read both for total marketplace exposure. **How do I add a new marketplace partner?** Tag the partner's orders consistently with the partner name, then add that tag to the card's marketplace tag set under the card configuration. Until the tag is added, the new partner's revenue is invisible here. **Why is the number lumpy?** Marketplace demand is partner-driven. A partner promotion, a homepage placement, or a seasonal department-store event can lift one partner's orders sharply, then fall back. Judge marketplace revenue on a rolling window rather than week to week. **My partner's portal shows a higher number, why?** Marketplace operators report on their own fulfilment and settlement timelines, and net returns differently. Their figure leads or lags Shopify's order-created view. Reconcile monthly against the portal rather than expecting a daily match. **How do I see each partner separately?** Use [Revenue by Sales Channel (Tag)](/nerve-centre/kpi-cards/shopify/revenue-by-sales-channel-tag), which charts each marketplace tag as its own bar. This card combines them into a single headline; that card splits them. **Should I worry about marketplace concentration?** Yes if one partner dominates. A single partner above a third of this card is a dependency risk, the partner controls placement, terms, and can delist you. The resilient shape is several partners of similar size. Track concentration alongside the total. *** ### Tracked live in Vortex IQ Nerve Centre *Marketplace Revenue* is one of hundreds of KPI pulses Vortex IQ tracks across Shopify 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.