Skip to main content
Card class: Non-HeroCategory: Ecommerce Platform
Mean Sales Order line total. Mid-market B2B AOVs typically run 8 to 15x DTC.

At a glance

Mean Sales Order amount in the period. The B2B-side equivalent of commerce-platform AOV, except B2B SOs typically run 8 to 15 times larger than DTC orders.
What it countsSUM(Transaction.Amount) ÷ COUNT(DISTINCT Sales Order) for Transaction.Type = 'SalesOrd' created in the period.
Tax treatmentNet of tax (revenue-only sum, divided by SO count).
ShippingIncluded if mapped to revenue.
DiscountsAlready deducted at line level.
Refunds / Credit MemosNot relevant (SO is pre-Invoice).
Cancelled SOsExcluded. Voided SOs are also excluded.
CurrencyOneWorld: reporting currency at SO-creation FX.
Subsidiary scopeRespects dashboard filter.
Time window30D vsP
Alert triggerdrop >10% vsP, sentiment aov_trend
Rolesowner, finance

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 on NetSuite. 30-day window 14 Mar 26 to 12 Apr 26.
This periodPrior periodvsP
Total SO value created$7,460,000$7,120,000+4.8%
SO count482410+17.6%
Average SO Value$15,477$17,366-10.9%
Five things to notice:
  1. AOV dropped 10.9% but revenue grew 4.8%. The card flags this as a structural shift: more SOs of smaller average size. The Controller drills in.
  2. A new distributor onboarded with smaller-basket but higher-frequency orders. They added 50+ SOs at $4-6K each, pulling the average down. This is good growth (broader customer base) even if AOV optics look bad.
  3. The 10.9% drop trips the alert threshold (>10%). The Controller validates that the AOV drop is mix-shift rather than per-customer compression. If existing customers’ AOV is steady and only the new ones are smaller, no action needed.
  4. B2B AOV at 15Kisstructurally50100xhigherthantypicalDTCecommerce(15K is structurally 50-100x higher than typical DTC ecommerce (100-500). Comparing across channels via shopify.aov is misleading; the card is meant for B2B-on-NetSuite reading.
  5. Average can mislead with concentration. A single $200K wholesale SO can lift period AOV by 5%+ on its own. The trend smooths this; for daily reads, look at SO State Breakdown for distribution.

Sibling cards merchants should reference together

CardWhy pair it with Average SO Value
Open SO ValueThe total. AOV × Count = Total.
Open Sales OrdersThe denominator (SO count).
Top B2B AccountsConcentration. Big customers drive AOV.
Top Customers RevenueCustomer-side mix.
Revenue Booked into GLLookback to validate AOV → revenue.
shopify.aov / bigcommerce.aovDTC AOV. Different number; helps gauge B2B premium ratio.

Reconciling against the vendor’s own dashboard

Where to look in NetSuite:
Reports → Sales → Sales Order Register with average aggregation Saved search: Transaction.Type = 'SalesOrd' with AVG(Amount)
Why our number may legitimately differ from NetSuite reports:
ReasonDirectionWhy
Cancelled SO inclusionEitherSome saved searches include cancelled SOs at $0; card excludes.
Multi-line SO totallingCard consistentCard sums all lines per SO before averaging. Some saved searches accidentally average lines instead of SOs.
FX rate cadenceSmallSO-creation date FX.
Cross-connector reconciliation:
CardRelationshipWhy
shopify.aovDifferent scaleDTC AOV typically 50-100x smaller than B2B. Comparison gauges premium customer mix.
bigcommerce.aovOften direct comparison if B2B storeBC B2B AOV may approach NetSuite SO AOV closely.

Known limitations / merchant FAQs

Why is my AOV dropping but revenue rising? Customer-mix shift. New customers (smaller baskets, more frequent) replacing or adding to old customers (large baskets, less frequent). This is usually healthy growth (broader base) but the optics of “AOV dropping” can spook stakeholders. Why does AOV swing so much day-to-day? B2B SO counts are low (10-50 per day for mid-market). A single $100K outlier SO can move AOV by 30% on a slow day. Look at rolling 30-day, not daily. Should B2B AOV match retail AOV? No. B2B AOV is structurally 8 to 50x larger because each SO is a multi-unit wholesale or distributor purchase. Comparing to DTC AOV is misleading. Cancelled SOs, included or excluded? Excluded by default. Cancelled SOs at $0 would skew the mean down. Voided SOs are also excluded. Recurring billing and Subscription AOV? Each subscription billing cycle creates an SO with the cycle’s billing amount, not lifetime contract value. So a 120K/yearcontractbilledmonthlyshowsas12SOsof120K/year contract billed monthly shows as 12 SOs of 10K each in successive periods. Multi-currency, what FX rate is used? SO-creation date FX. The reporting-currency average reflects the FX environment when SOs were created. ASC 606 deferral, does it impact AOV? No. SO Amount is contract value, not recognised revenue. ASC 606 affects how revenue posts; SO AOV is independent. Drop-ship SOs, included? Yes by default. Some accounts treat drop-ship as zero-margin pass-through and exclude from AOV analysis; the field map can carve them out.

Tracked live in Vortex IQ Nerve Centre

Average Sales Order Value 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.