← All company lists

ERP and business systems · October 2026 research

Oracle NetSuite company list

Review 133 operators with recorded NetSuite statements or SuiteCommerce configuration. Separate ERP research from storefront work before choosing which records to inspect.

Research dated 2026-10-23. Original source dates and website scope stay with the records.

Oracle NetSuite research summary

133 reviewed company operators

Research dated

Contact-free research examples · CSV

133 reviewed operators: 37 have statements naming ERP, 29 have unspecified NetSuite modules, one names WMS, one MRP and one inventory, and 64 have SuiteCommerce storefront configuration only. Commerce configuration does not establish ERP or CRM use.

Download the 4-row CSV preview

Separate ERP statements from commerce configuration

37

ERP named in company or issuer statements

The statement names ERP at its recorded reporting-entity, period and module scope.

32

Other module scopes

29 records leave NetSuite modules unspecified; one names WMS, one MRP and one inventory. These do not establish whole-ERP coverage.

64

SuiteCommerce configuration only

Referenced static storefront configuration; ERP, CRM, paid status and executed runtime are unverified.

37 + 32 + 64 = 133 operators, counted once each. The 32 other module scopes comprise 29 unspecified, one WMS, one MRP and one inventory record.

Preview the list

Source mix, findings and four contact-free examples from the 133-operator Oracle NetSuite research cohort. The full account file is not offered; commercial reuse and delivery rights remain unresolved.

CSV columns: name · domain · sourceClass · checkedOn · scope

Four companies in the preview

These approved examples illustrate the 2026-10-23 research. They are not a representative sample of all customers.

Lovesac

lovesac.com

historical issuer erp disclosure · 2026-10-22

ERP with POS, financial reporting, order management and CRM functionality as described in the May2019 issuer filing. Source publication: 2019-05-20. Historical record. Paid status unknown; current runtime unverified.

GitLab

gitlab.com

historical company handbook erp · 2026-10-22

GitLab finance ERP/general ledger in retained February2024 handbook revision; current deployment unverified. Historical record. Paid status unknown; current runtime unverified.

PagerDuty

pagerduty.com

company internal system job disclosure · 2026-10-22

PagerDuty order-to-revenue ecosystem explicitly names NetSuite ERP; no additional modules inferred. Paid status unknown; current runtime unverified.

Datadog

datadoghq.com

company internal system job disclosure · 2026-10-22

Datadog financial-system enhancements and billing automation; exact NetSuite modules unspecified. Paid status unknown; current runtime unverified.

Workflows and source dates in this list

WhosBuilt analysis of the saved October 2026 research. Findings describe this selected cohort, not market share.

64 / 133 · 48.1%

Separate commerce from ERP

64 of 133 operators have commerce configuration only, while 37 have a statement naming ERP. These groups answer different research questions.

Discovery oversampled accessible storefronts. Counts describe this package and cannot estimate market share or paid use.

Research 2026-10-23 · reviewed company operators · WhosBuilt saved-record analysis

37 / 133 · 27.8%

Keep the older disclosures dated

37 of 133 operator records are historical. A new website or contact check does not make those technology statements current.

The historical flag and original source dates are preserved. A false historical flag also does not verify current execution or a paid contract.

Research 2026-10-23 · reviewed company operators · WhosBuilt saved-record analysis

How this list was checked

Original sources checked 2026-10-22 to 2026-10-23 UTC. Thirty-seven records are historical. Publication dates, reporting periods and configuration dates remain separate from retrieval. The preview includes a 2019-05-20 filing and a February 2024 handbook revision; later website and contact checks do not refresh those statements.

133 reviewed operators: 37 have statements naming ERP, 29 have unspecified NetSuite modules, one names WMS, one MRP and one inventory, and 64 have SuiteCommerce storefront configuration only. Commerce configuration does not establish ERP or CRM use.

Oracle NetSuite source composition
Source classCountScope
ERP named in company or issuer statements37The statement names ERP at its recorded reporting-entity, period and module scope.
Other module scopes3229 records leave NetSuite modules unspecified; one names WMS, one MRP and one inventory. These do not establish whole-ERP coverage.
SuiteCommerce configuration only64Referenced static storefront configuration; ERP, CRM, paid status and executed runtime are unverified.

Separate commerce from ERP: Denominator: all 133 accepted operators in this product package, counted once per operator. Workflow scope and historical status are separate classifications and can overlap. WhosBuilt analysis of the saved company research and separately reviewed findings; no source refresh.

Research dated 2026-10-23; original source observations ran 2026-10-22 to 2026-10-23 UTC. Counts describe this selected package, not the product's customer base.

Keep the older disclosures dated: Denominator: all 133 accepted operators in this product package, counted once per operator. Workflow scope and historical status are separate classifications and can overlap. WhosBuilt analysis of the saved company research and separately reviewed findings; no source refresh.

Research dated 2026-10-23; original source observations ran 2026-10-22 to 2026-10-23 UTC. Counts describe this selected package, not the product's customer base.

  • Thirty-seven records retain historical scope. The other records also do not verify a current paid contract or executed runtime.
  • Company, issuer, subsidiary and storefront identities keep their stated limits. No organization-wide module coverage, buyer role or buying intent is inferred.
  • Accessible storefronts were prominent in discovery. Package composition does not estimate market share, churn or technology non-use.

Source access dates do not refresh historical statements. Static signals do not prove execution, payment or buying intent. Published contacts do not establish deliverability or outreach permission.