At a glance
Count of distinct customers who placed at least one Sales Order in the period. Distinct from the all-time customer count (which includes long-dormant accounts) and from new-customer count (those placing their first-ever SO). The active-customer count is the merchant’s working-account-base view: how many customers are buying right now.
| What it counts | COUNT(DISTINCT customer.internalid WHERE customer placed >=1 SO in period AND SO.status NOT IN ('Cancelled')). Each customer counts once regardless of order volume in the period. |
| VAT / tax treatment | n/a, this is a count metric. |
| Shipping | n/a. |
| Discounts | n/a. |
| Refunds | A customer whose only order in the period was refunded / cancelled is excluded. |
| Cancelled / voided orders | Customers whose only orders were cancelled are excluded. |
| Currency | n/a; customer-count is currency-agnostic. |
| Channels / sources | All sources blended: web (SuiteCommerce / SCA), B2B portal, manual SO, EDI inbound. Per-channel views available via Ask Viq. NetSuite’s customer record is unified across channels (unlike commerce platforms where the same buyer can have separate records). |
| B2B vs B2C distinction | NetSuite distinguishes Customers (companies, B2B) from Sub-Customers (individual contacts under a parent company) and uses Customer Categories (DTC, Wholesale, Distributor, etc). The default count blends all; per-category breakdowns expose the B2B vs B2C split. |
| Time window | 30D |
| Alert trigger | None on the count directly; drops surfaced via Customer Churn Signals. |
| Roles | owner, marketing, 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 distributor on NetSuite OneWorld, 30D window 02 Apr 26 to 01 May 26.| Segment | Active customers | Active customers prior 30D | Delta | Avg orders / customer | Avg revenue / customer |
|---|---|---|---|---|---|
| DTC consumer (web) | 4,820 | 4,560 | +5.7% | 1.18 | $98 |
| B2B Wholesale (parent companies) | 412 | 408 | +1.0% | 4.6 | $14,200 |
| B2B Sub-buyers (contacts within parents) | 1,840 | 1,790 | +2.8% | 1.5 | $3,180 |
| Distributor (highest tier) | 24 | 24 | 0% | 8.4 | $84,000 |
| Total | 7,096 | 6,782 | +4.6% | 2.6 | $1,980 |
- **Distributor count is flat at 24 but each averages 84k/30d hole. Cross-reference Top B2B Accounts.
- B2B parent-company count up 1%, sub-buyer count up 2.8%. Healthy: existing parent accounts are activating more sub-buyers (more individuals at the buying companies are placing orders). NetSuite’s parent-sub structure makes this visible; commerce platforms cannot see this hierarchy.
- DTC consumer +5.7% is the headline growth. 260 net new active web customers; first-time-buyer cohort accounts for 180 of these (cross-reference new-customer subset card). Acquisition + reactivation are roughly 70/30.
- The “active” baseline of 7,096 vs the all-time customer record count of 38,400. Only 18.5% of total customers transacted in the last 30 days. This is normal for B2B distribution (where many customers have purchase cadences of 60 to 180 days). For a DTC fashion brand the equivalent ratio would be 8 to 12% (longer customer-life dormancy).
- Per-subsidiary view (OneWorld): US 5,210 active, UK 1,420, AU 466. The UK active-base grew 8% (+108 customers) on the back of a Q1 marketing push; UK growth is faster than US in percentage terms.
- Action playbook: because the top 24 distributor accounts produce 28% of revenue, the highest-leverage retention is making sure none of the 24 fell out of the active list. Cross-reference Customer Churn Signals filtered to Distributor category. If any distributor’s last-order is >45 days old (their typical cadence is 21 to 28 days), an account-management call this week is the right move.
Sibling cards merchants should reference together
| Card | Why pair it with Active Customers |
|---|---|
| Top B2B Accounts | The top-N concentration view. Active count is anonymous; this drills to which accounts. |
| Customer Churn Signals | The leading indicator for active-count drops. Customers whose last-order is past their typical cadence. |
| Customer Credit Utilisation | Active customers near credit limits will stop ordering, pre-empting the churn drop. |
| B2B Payment Terms Mix | Mix shift can mask growth: 100 new Net-30 + 50 lost Net-60 = active count flat but cash cycle different. |
| Top Customers by Revenue | The dollar concentration; Pareto check on active-base health. |
| Average SO Value | Active count × Avg SO Value × Orders-per-customer = period revenue. |
shopify.unique_customers | Cross-connector: web active count should reconcile to Shopify unique customers within ±5%. |
Reconciling against the vendor’s own dashboard
Where to look in NetSuite’s own dashboard:Reports > Sales > Sales by Customer > Detail, set date range to the period, group by Customer. Distinct customer count = card value.For per-Customer-Category breakdown: Saved Search > Transaction, criteria
Type = Sales Order, Status NOT Cancelled, Date within period, group by Customer.category, count distinct.
Why our number may legitimately differ:
| Reason | Direction | Why |
|---|---|---|
| Sub-Customer hierarchy treatment | Either | Vortex IQ counts sub-customers as distinct active-customers (because each is a buyer). Some NS reports roll sub-customers up to the parent for a flat customer count. Configurable. |
| Cancelled-only customers | Vortex IQ lower | Customers whose only orders cancelled are excluded; some NS reports include them. |
| Inactive customer flag | Either | Customers marked inactive may still appear in Vortex IQ if they transacted in the period; some NS reports exclude on the inactive flag. |
| Card | Expected relationship | Notes |
|---|---|---|
shopify.unique_customers | Web subset only ≈ Shopify unique customers | Same buyer with separate Shopify and NS customer records (sync issue) inflates Shopify count. |
bigcommerce.unique_customers | Web subset only ≈ BC unique | Same logic. |
adobe_commerce.active_customers | Web subset only ≈ Adobe active | Adobe Commerce customer-group hierarchy may align with NS Sub-Customer model; check mapping. |