> ## 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. # Total Revenue, OnBuy > Total Revenue for OnBuy stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it. **Metrics type:** [Key Metrics](/nerve-centre/overview#metrics-types-explained) • **Category:** [Marketplace](/nerve-centre/connectors#connectors-by-type) ## At a glance > Headline gross sales through OnBuy in the period. Sum of every order's customer-paid total (`order.amount` from the `GET /orders` endpoint), gross of OnBuy commission and gross of refunds. The number a UK marketplace seller checks first thing on a Monday before opening the OnBuy console. | | | | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **What it counts** | `SUM(order.amount)` across orders with `created_at` in the selected window, pulled from OnBuy's `GET /v2/orders` endpoint. Each order's amount already contains item totals, customer-side delivery charges, and VAT. | | **API endpoint** | `GET https://api.onbuy.com/v2/orders` (paged, max 100 per call, OAuth2 client-credentials, 1h token TTL). | | **Fees / commission** | **Gross of OnBuy commission.** OnBuy charges 5% to 9% category commission plus a 9p (£0.09) transaction fee. Neither is deducted here. Pair with `onbuy_commission_pct` and `onbuy_net_revenue` for the after-fees view. | | **VAT / tax treatment** | **VAT inclusive.** OnBuy is a UK-only marketplace; `order.amount` is the gross VAT-inclusive total the buyer paid, matching what appears on the OnBuy Seller Console "Sales" report. | | **Shipping** | **Included.** Buyer-paid delivery sits inside `order.amount`; it is not separated out by the API. | | **Discounts** | **Already deducted.** Promo-priced and sale-priced listings show post-discount totals. OnBuy does not expose pre-discount RRP at order level. | | **Refunds** | **NOT deducted.** A fully refunded £40 order still contributes £40 here. For the netted view use `onbuy_net_revenue` (after commission and refunds). | | **Cancellations** | **Excluded.** Orders with `status = cancelled` before dispatch are filtered out by the engine. Buyer-cancelled-after-dispatch orders count as refunds (still included here, deducted in net revenue). | | **Currency** | **GBP only, single currency.** OnBuy operates UK-domestic for now (EU expansion is in beta but not generally available); every order is in GBP, no FX needed. | | **Channel scope** | OnBuy marketplace only. Includes "Boost" promoted listings. Direct-to-consumer (Shopify, BigCommerce) revenue is not in this card; cross-shop comparison sits in `onbuy_xc_share_of_uk_revenue`. | | **Time window** | `T/7D/30D vsP` (today, 7-day, 30-day, each compared against prior equivalent period). | | **Alert trigger** | `drop >15% vsP`. Driven by `sentiment_key: revenue_trend`. The alert fires on the 30D vsP comparison to avoid daily noise. | | **Roles** | owner, finance. | ## Calculation Calculated automatically from your OnBuy 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 small UK home-and-garden seller, week of 21 Apr 26 to 27 Apr 26.** The seller runs a 90-listing catalogue on OnBuy alongside their own Shopify store, uses Royal Mail Tracked 24 / 48 for fulfilment, and has been on OnBuy for 14 months. | Metric | This week (21 Apr 26) | Prior week (14 Apr 26) | Change | | -------------------------------------- | --------------------- | ---------------------- | ------ | | Orders | 38 | 32 | +18.8% | | Total Revenue (this card) | £1,420 | £1,210 | +17.4% | | Refund Value | £58 | £74 | n/a | | OnBuy commission (\~7% avg) | £99 | £85 | n/a | | Per-order transaction fee (£0.09 x 38) | £3.42 | £2.88 | n/a | | Net revenue after fees and refunds | £1,260 | £1,048 | +20.2% | ```text theme={null} Total Revenue (gross) £1,420 Less OnBuy commission (~7%) -£99 Less per-order fee (38 x £0.09) -£3.42 Less refunds -£58 Net revenue after fees £1,260 ``` **What it means for this seller.** A £210 lift on the gross line and a £212 lift on the net line shows OnBuy is genuinely growing for them, not just absorbing a one-off promo spike. The fee load is roughly 7.2% of gross which is normal for the home-and-garden category (8% headline rate but with a few promoted-listing rebates). On a Monday-morning glance, a +17% gross figure with consistent fee proportion and no refund-rate spike is the cleanest possible signal: they should keep investing in OnBuy listings (price visibility, image refresh, RRP completeness), not pull back. A £210 gain at 30% blended margin after fees is roughly £63 of incremental contribution this week. Modest in absolute terms, which is the reality of small-merchant marketplace traffic, but compounding week-on-week growth at this rate would double the OnBuy line over a quarter. ## Sibling cards merchants should reference together Total Revenue is the headline number, but on a fees-heavy marketplace it is rarely useful in isolation. Pair it with these: | Card | Why it matters next to Total Revenue | What the combination tells you | | ------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | | [Net Revenue (after commission and refunds)](/nerve-centre/kpi-cards/onbuy/net-revenue) | The take-home line. OnBuy fees are 5% to 9% plus 9p per order. | Gross up but net flat means commission tier just moved against you (likely a category re-classification). | | [Total Orders](/nerve-centre/kpi-cards/onbuy/orders) | The denominator behind AOV. Marketplace volume is more volatile than DTC. | Revenue up + orders flat means basket got bigger; revenue up + orders up means real demand growth. | | [OnBuy Commission % of Revenue](/nerve-centre/kpi-cards/onbuy/onbuy-commission-of-revenue) | OnBuy commission tiers are category-driven and easy to mis-classify. | If commission % drifts above your category benchmark, raise it with OnBuy seller support. | | [Suspended Listings](/nerve-centre/kpi-cards/onbuy/suspended-listings) | Suspensions silently cap revenue. | Revenue plateau with rising suspensions = ceiling that fee tweaks won't fix. | | [Dispatch SLA Compliance](/nerve-centre/kpi-cards/onbuy/dispatch-sla-compliance) | OnBuy de-prioritises sellers below 95%. | Revenue dropping while SLA is fine usually means a pricing or RRP issue, not an account-standing one. | | [Revenue Trend](/nerve-centre/kpi-cards/onbuy/revenue-over-time) | The 90-day shape of this number. | Use the trend to read whether the current week is on-pattern or a real break. | | [eBay Total Revenue](/nerve-centre/kpi-cards/ebay/total-revenue) | The peer UK marketplace number. | If both eBay and OnBuy moved in the same direction, treat the cause as channel-wide (Bank Holiday, weather, postage strike). | | [Shopify Total Revenue](/nerve-centre/kpi-cards/shopify/total-revenue) | The DTC anchor. | OnBuy revenue should be \~10 to 25% of DTC for most small UK brands; outside that band, see `onbuy_xc_share_of_uk_revenue`. | ## Reconciling against the vendor's own dashboard **Where to look in OnBuy's own dashboard:** The closest OnBuy-native view is: > **OnBuy Seller Console (`https://seller.onbuy.com`) -> Reports -> Sales Report** > Filter by date range and currency (GBP). The "Total Sales" column is the apples-to-apples comparison. For a quick sanity check, the seller homepage has a "30-day sales" tile in the top-right that should sit within a few percent of our 30D figure. **Why our number may legitimately differ from OnBuy's Seller Console:** A small gap is normal. The usual suspects: | Reason | Direction | Why | | ----------------------- | --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Time zone** | Boundary days off | OnBuy's report uses Europe/London; we use UTC. During UK summer time (BST) the cut-off is one hour earlier on our side, which can shift "today" or "yesterday" totals. | | **Cancelled orders** | Theirs higher | OnBuy's Sales Report includes orders cancelled-after-purchase as gross sales until the cancellation lands; we filter `status = cancelled` out. | | **Refunds** | Theirs lower in netted view | The Sales Report has a "Net Sales" toggle that subtracts refunds; this card is gross. Compare against the gross toggle. | | **Sync lag** | Ours lower for "today" | Our index polls OnBuy `GET /v2/orders` every 15 minutes; the most recent \~15 min of orders may not be in. Yesterday and earlier are caught up. | | **Order status filter** | Either | OnBuy's report defaults to `paid + dispatched + delivered`; if the seller toggles to "All statuses" in their console they will see pending orders we have not yet ingested. | **Cross-connector reconciliation. eBay UK:** If the merchant also runs eBay UK, [`ebay_total_revenue`](/nerve-centre/kpi-cards/ebay/total-revenue) is the natural peer. They should sit in similar bands for a comparable category mix, but a 2x to 5x gap in either direction is normal because eBay has roughly 12x the UK marketplace traffic of OnBuy. Use the pair to spot channel-wide effects (UK postal strike, Bank Holiday, weather event) versus channel-specific drops. **Cross-connector reconciliation. Shopify or BigCommerce DTC:** The merchant's DTC store is not a definitional twin (those orders never touch OnBuy), but the share is informative. The cross-platform card [`onbuy_xc_share_of_uk_revenue`](/nerve-centre/kpi-cards/onbuy/onbuy-share-of-uk-revenue) does the split. For most small UK brands OnBuy lands at 10 to 25% of DTC; if OnBuy is north of 50% the brand is marketplace-dependent and should review category exposure. ***
Documentation cross-reference (for agencies running multiple platforms) The "Total Revenue" metric exists with the same shape on other commerce connectors. This is **not** a reconciliation, the merchant's OnBuy account does not have parallel orders on Shopify or BigCommerce; the same buyer can not place the same order in two places. These references are only useful if an agency manages multiple platforms for the same brand and wants the same metric across docs. * [`shopify.total_revenue`](/nerve-centre/kpi-cards/shopify/total-revenue) * [`bigcommerce.total_revenue`](/nerve-centre/bigcommerce/bigcommerce_total_revenue) * [`ebay.ebay_total_revenue`](/nerve-centre/kpi-cards/ebay/total-revenue)
## Known limitations / merchant FAQs **Why does my OnBuy Seller Console show a higher number than this card?** Three usual suspects, in this order. First, the Console defaults to "All statuses" (including cancelled orders awaiting refund); we exclude them. Second, the Console uses Europe/London time, we use UTC, so the day boundary is offset by 0 or 1 hour. Third, our sync runs every 15 minutes, so the freshest orders may not be in yet. If after checking those the gap is still more than 5%, raise it via the support form, it usually traces to a category re-classification we have not picked up. **Does this number include OnBuy's commission?** No, this is gross of commission and gross of the per-order 9p transaction fee. Use [`onbuy_net_revenue`](/nerve-centre/kpi-cards/onbuy/net-revenue) for the take-home view. OnBuy commission tiers are 5% (basic), 7% (mid), and 9% (premium categories like beauty); plus a flat 9p per order. A typical mixed home-and-garden seller pays around 7 to 8% blended. **Why does Total Revenue look small compared to my Shopify number?** OnBuy has roughly 12x less traffic than eBay UK and about 100x less than Amazon UK. For most small brands a healthy OnBuy line is 10 to 25% of DTC revenue. If OnBuy is below 5% of DTC, you are likely under-investing (image quality, RRP completeness, Boost spend); if above 50% the brand is marketplace-dependent. Use [`onbuy_xc_share_of_uk_revenue`](/nerve-centre/kpi-cards/onbuy/onbuy-share-of-uk-revenue) to track the split. **Is OnBuy worth the effort for a small DTC brand?** For UK-only brands selling under £20k a month on DTC, OnBuy typically adds 5 to 15% of incremental revenue with low fee load (\~7% blended) and minimal extra ops once the listing pipeline is in place. The platform is much more curated than eBay (no auction-style listings, fixed-price only) which suits brand-conscious sellers. The honest answer though is: OnBuy is small. If you are looking for marketplace volume, eBay and Amazon will dwarf it. OnBuy makes sense as a low-friction supplementary channel, not a primary one. **Why is today's number volatile compared to the 30D average?** Same reason all small-volume marketplaces look noisy intra-day: with 5 to 50 orders a day, a single £200 order moves the number 4 to 40%. Use the 7D or 30D vs prior-period view for trend reading; only use "today" to spot incident-level breaks (e.g. listings disappeared, suspension applied). **My OnBuy revenue dropped 30% this week, what should I check first?** Run this playbook in order: 1. **Check [`onbuy_suspended_listings`](/nerve-centre/kpi-cards/onbuy/suspended-listings).** A single hero SKU getting suspended can wipe 30% of a small catalogue's revenue overnight. If suspensions are non-zero, this is the cause; clear the issues OnBuy flagged in the Seller Console and request reinstatement. 2. **Check [`onbuy_alert_token_expiry`](/nerve-centre/kpi-cards/onbuy/auth-token-health).** OnBuy tokens expire every 1 hour; if the refresh failed silently, our sync stops and the number looks dropped without anything actually changing on the merchant side. 3. **Check [`onbuy_sla_compliance`](/nerve-centre/kpi-cards/onbuy/dispatch-sla-compliance).** Below 95% and OnBuy de-prioritises listings in browse, this shows up as a slow-bleed revenue drop, not a sudden one. 4. **Check the eBay and Amazon UK comparison.** If both peer marketplaces moved with you, the cause is channel-wide (Bank Holiday, weather, courier strike), not OnBuy-specific. No action required. 5. **Check [`onbuy_no_rrp_set`](/nerve-centre/kpi-cards/onbuy/listings-missing-rrp) and [`onbuy_xc_dtc_price_gap`](/nerve-centre/kpi-cards/onbuy/onbuy-vs-dtc-price-gap).** Without an RRP, OnBuy can not show "Save X%" badges that drive click-through; large DTC-vs-OnBuy gaps trigger price-policing on supplier side. **Does this include EU orders?** OnBuy's EU expansion (DE, FR, NL) is in beta as of 30 Apr 26, behind a separate seller agreement. Generally available EU revenue would land under a separate `onbuy_eu_total_revenue` card when launched. Today this card is GBP-only. **How does this compare to eBay's headline revenue number?** eBay UK reports gross revenue similarly (gross of fees, not deducting refunds), so the cards are read the same way. The big difference: eBay's fee structure is 12.8% + 30p (final value fee on most categories) versus OnBuy's 5 to 9% + 9p, so eBay's "revenue minus net" gap is wider for the same gross. If a merchant runs both, treat OnBuy as the lower-fee channel and route higher-margin SKUs there preferentially. **Why don't my refunds show as a deduction?** By design. Founders want to see headline gross when checking pulse first thing; the refund deduction is a separate cognitive step (`onbuy_net_revenue`). For most categories OnBuy refund rates sit at 3 to 6%, which is lower than eBay (often 6 to 10%) because the fixed-price format avoids auction-related disputes. *** ### Tracked live in Vortex IQ Nerve Centre *Total Revenue* is one of hundreds of KPI pulses Vortex IQ tracks across OnBuy 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.