Skip to main content
Card class: Card
Revenue dimension by NetSuite Class (typically used as line-of-business, channel, or division segmentation).

At a glance

Revenue Booked into GL split by NetSuite Class. Class is the most flexible NetSuite dimension; merchants typically use it for business unit, channel, brand, or division. The most actionable cut on consolidated revenue.
What it countsSUM(Transaction.Amount) for revenue accounts grouped by Class for the period.
Tax treatmentNet of tax.
ShippingIncluded if mapped to revenue.
Refunds / Credit MemosDeducted within each class.
CurrencyOneWorld: reporting currency. Single-subsidiary: native.
Subsidiary scopeRespects dashboard filter.
Class hierarchyNetSuite supports parent-child Class records. Card displays leaf-level by default; toggleable to roll-up via dashboard control.
Unclassified transactionsTransactions without a Class assigned appear as “(Unclassified)” row. Frequent unclassified rows signal a data-entry gap.
Time window30D
Alert triggerNone at headline (informational); per-class anomaly detection on the trend
Rolesowner, finance
Only-when gateClass dimension enabled (Setup → Company → Enable Features → Classifications). Most NetSuite accounts have it on.

Calculation

Calculated automatically from your NetSuite 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 wholesale apparel distributor using Class for brand segmentation. 30-day window 14 Mar 26 to 12 Apr 26.
Class (Brand)Revenue (USD)% of totalvsP
Brand A (premium)$2,840,00043%+6%
Brand B (mid-tier)$1,920,00029%-3%
Brand C (budget)$1,180,00018%+18%
Brand D (kids)$480,0007%+2%
(Unclassified)$140,0002%+400%
Total$6,560,000100%+1.8%
Five things to notice:
  1. Brand C is the breakout (+18%). The Controller drills in: which customers, which SKUs, which channel? If it’s broad, it’s a market trend; if it’s one customer, it’s concentration risk masquerading as growth.
  2. Brand B is contracting (-3%). The mid-tier squeeze, premium and budget growing at the expense of mid-tier. Classic apparel trend; the Controller flags this for the merchandising review.
  3. Unclassified jumped from 28Kto28K to 140K (+400%). Data quality alarm. New SOs are being entered without Class set. Pings the NetSuite Admin to find the workflow that’s bypassing the Class field.
  4. The 43% Brand A concentration is the strategic risk view. If Brand A fails, the business loses 43% of revenue. Compare to Top Customers Revenue for the customer-side concentration.
  5. Class can be repurposed. Some accounts use Class for channel (Wholesale / DTC / Marketplace) instead of brand. The card adapts; whatever the Class label is, that’s what shows. The field map can rename the axis.

Sibling cards merchants should reference together

CardWhy pair it with Revenue by Class
Revenue Booked into GLThe total. Class breakdown decomposes it.
Revenue by SubsidiaryThe subsidiary cut. Use both for matrix views (Class × Sub).
Top Customers RevenueCustomer-side concentration. Class is product-side; together they map the business.
Margin by SKUProfitability of each Class. Revenue is half the picture.
Top SKUs ValueDrill-down within a class.
shopify.total_revenue (with sales-channel filter)Channel-side equivalent for Shopify-based class accounts.

Reconciling against the vendor’s own dashboard

Where to look in NetSuite:
Reports → Sales → Sales by Class Reports → Financial → Income Statement with Class group-by
Why our number may legitimately differ from NetSuite reports:
ReasonDirectionWhy
Class hierarchy roll-upEitherNetSuite’s report can roll Classes to parent; the card defaults to leaf-level. Toggle via dashboard.
Unclassified inclusionEitherSome saved searches filter out blank Class transactions. The card shows them as “(Unclassified)” by default.
FX cadenceSmallTransaction-date vs period-average FX.
Subsidiary scopeEitherCard defaults to all subs the role can read.
Cross-connector reconciliation:
CardRelationshipWhy
shopify.total_revenue (sales-channel filter)Channel-side equivalentShopify Sales Channels often map to NetSuite Class for accounts using Class for channel segmentation.

Known limitations / merchant FAQs

What does Class mean in NetSuite? A flexible, account-level dimension that can mean anything: brand, channel, business unit, division, project type. The merchant decides at setup. Most accounts use it for one consistent thing (e.g. always Brand). Some use Department for division and Class for channel. Why is Unclassified rising? Almost always a workflow change. New customers, new SKUs, or new SO entry forms that don’t enforce Class get past the validation. The Admin should fix the workflow. Class vs Department vs Location? Three separate NetSuite dimensions. Most accounts use:
  • Class for product / brand
  • Department for org structure
  • Location for inventory/warehouse
You can have all three simultaneously. The card focuses on Class because it’s the most commonly-used revenue dimension, but parallel cards for Department and Location are on the roadmap. Class hierarchy, how does roll-up work? NetSuite Class records can have parents. “Brand A > Brand A Premium” rolls into Brand A. The card shows leaf-level by default; toggle to roll-up at the bar chart. Why is one Class flat across periods even though sales are seasonal? Likely an accounting policy issue: revenue is being smoothed via Advanced Revenue Management (ARM), or Class is being assigned at journal-entry time rather than transaction time. Multi-currency Class behaviour? Each transaction’s Class carries with it; the FX translation happens at the line level. The card sums in reporting currency. No special handling. Is Class the same as Class accounting (financial classification)? No. Class accounting is a US tax concept; NetSuite Class is just a custom dimension. Different concept entirely. Can I change Class after a transaction posts? Yes, with the right permission. Edits to closed periods require re-opening. The card reflects the current Class assignment at refresh time. ASC 606 impact? None directly; Class is a tag, not a revenue rule. Each Class still respects ARM deferrals where applicable.

Tracked live in Vortex IQ Nerve Centre

Revenue by Class is one of hundreds of KPI pulses Vortex IQ tracks across NetSuite 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.