Mean Sales Order line total. Mid-market B2B AOVs typically run 8 to 15x DTC.
At a glance
Mean Sales Order value. For B2B Fortune 500 distributors typically 200K depending on industry; for B2C / DTC much lower.
| What it counts | SUM(ordered_amount) / COUNT(SO) for SOs created in the window. |
| Tax treatment | Net of tax. |
| Shipping | Included on SO line. |
| Discounts | Post-discount. |
| Cancelled | Excluded. |
| Currency | Reporting ledger. |
| Time window | 30D vsP |
| Alert trigger | drop >10% vsP |
| Sentiment key | aov_trend |
| Roles | owner, finance |
Calculation
Calculated automatically from your Oracle ERP Cloud 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 Fortune 500 distributor on Oracle ERP Cloud. 30D window 14 Mar 26 to 12 Apr 26.| This period | Prior | |
|---|---|---|
| Sales Orders | 4,820 | 4,720 |
| Total SO value | $124M | $128M |
| Average SO | $25,725 | $27,118 |
- AOV dropped 5.1% vsP. Within healthy range; if it continues 3 periods, investigate mix shift.
- Volume up but value down = customers buying smaller orders or smaller-cart customers gaining share.
- Per-channel cut reveals which channel is dragging.
- Compare to Top B2B Accounts for whether top customers are buying smaller.
- DTC vs B2B mix changes AOV dramatically.
Sibling cards merchants should reference together
| Card | Why pair |
|---|---|
| Open Sales Orders | Volume. |
| Open Sales Order Value | Total value. |
| Top Customers by Revenue | Concentration. |
Reconciling against the vendor’s own dashboard
Where to look in Oracle ERP Cloud:OTBI → Order Management Real Time with averageWhy our number may legitimately differ:
| Reason | Direction | Why |
|---|---|---|
| Date convention | Either | Card uses creation date; some reports use schedule date. |
| Card | Notes |
|---|---|
| Commerce AOV cards | Should align in commerce-only channels. |