NetSuite AI Units: Usage, Monitoring and Cost Planning

Availability last checked: August 27, 2026.

AI Units are the consumption metric NetSuite uses for generative AI feature usage. Every published per-action figure Oracle documents is explicitly labeled an estimate, not a fixed cost, and this page treats that qualification as load-bearing rather than a footnote. This is an ERP Peers editorial reference built from Oracle’s own AI Units documentation, not an official Oracle pricing guide.

For what each AI feature actually does, see our NetSuite AI Features overview. For whether your account and roles are ready to pilot one, see our AI Readiness Checklist. This page focuses on one thing: what AI Units measure, what’s included, and how to plan and monitor consumption.

What Are NetSuite AI Units?

Oracle’s own definition: “AI Units are the elements of consumption for NetSuite AI features. AI Units are measured and calculated by Oracle based on Customer’s use of such features which may vary by AI feature, model, or provider.”

In plain terms, an AI Unit is not tied to a fixed action like “one email” or “one document,” it’s a variable measure Oracle calculates behind the scenes, and the same type of request can consume a different number of units depending on complexity.

An AI Unit does not represent a fixed dollar amount, a fixed number of words, or a guaranteed quota per user. It’s an account-level (or, per Oracle’s own term-allowance language, a shared “AI Unit Pool”) measure of consumption across your organization, not a per-user allocation.

Who Receives AI Units and What’s Included

Oracle documents specific included allowances by license type, provisioned upfront for the full term rather than accruing monthly:

• NetSuite General Access Cloud Service User (Item #6023): 1,000 AI Units per month of term, provisioned upfront into the customer AI Unit Pool.
• NetSuite Social Impact Cloud Service User (Item #3112): 1,000 AI Units per month of term, same provisioning model.
• NetSuite Social Impact Donation for SuiteSuccess 3-User Bundle (Item #6360): 3,000 AI Units per month of term.
• Sandbox environments (Item #6500): a separate pool equal to the AI Units licensed in the connected production account.
• Development environments (Items #6501/#6552): a separate pool of 10,000 AI Units per month of term.

Oracle’s own worked example: “A NetSuite customer who signs a 36-month term and purchases 10 General Access Cloud Service Users receives 360,000 AI Units for use throughout their term,” provisioned entirely upfront rather than released monthly.

Unused AI Units expire when your NetSuite term expires, they don’t roll over into a new term. Sandbox, development, and preview accounts are tracked in separate pools from production and reset at the beginning of each licensing term.

Additional AI Units are available for purchase in two pooled package sizes Oracle names by item number: a 10,000-unit package (Item #7127) and a 25,000-unit package (Item #7143). Oracle’s public AI Units FAQ does not publish pricing for either package, current cost requires vendor confirmation from your account team.

Which Features Consume AI Units

Oracle’s own FAQ gives a clean rule: “If a SuiteApp uses generative AI capabilities in NetSuite then it uses AI Units. This includes features such as the SuiteScript Generative AI APIs, Text Enhance, Prompt Studio, and Ask Oracle.” That’s a broad, deliberately general rule, not a closed list, so don’t assume a generative AI feature is exempt just because this page doesn’t name it explicitly.

A separate, equally direct rule covers what doesn’t consume AI Units: “Add-on NetSuite modules with AI capabilities, such as NetSuite Bill Capture, NetSuite EPM products and NetSuite Analytics Warehouse, do not consume AI Units.” Those follow their own separate module pricing instead, covered in Features That Follow Different Rules below.

Feature-by-Feature Consumption Reference

Every figure below is Oracle’s own published estimate, explicitly labeled as such on Oracle’s documentation, not a fixed cost. Actual consumption depends on request length and complexity.

Ask Oracle

Standard generative features

Developer capabilities

For implementation detail on the N/llm module itself, see our SuiteScript Generative AI guide. If your use case pairs an external AI model with NetSuite data rather than using N/llm directly, that runs through the AI Connector Service instead, worth checking before assuming N/llm’s consumption figures apply.

* Every figure above is Oracle’s own published estimate. Oracle states directly: “the amount of AI Units used in your account for similar transactions may vary from these estimates,” and separately, “the number of AI Units used depends on the amount of AI processing required,” so a longer document, a more complex prompt, or a multi-step workflow will typically consume more than a short, simple one even within the same feature.

Features That Follow Different Rules

Three named categories are explicitly documented as consuming zero AI Units, because they’re priced as their own add-on modules instead:

• NetSuite Bill Capture, its own module purchase, separate consumption model.
• NetSuite EPM products (including Planning and Budgeting), separate product pricing.
• NetSuite Analytics Warehouse (NSAW), separate product pricing.

SuiteCloud Agent Skills and SuiteCloud Developer Assistant aren’t named in Oracle’s AI Units FAQ at all. Whether either consumes AI Units, and if so at what rate, isn’t stated in current public documentation, treat this as requires vendor confirmation rather than assuming either zero or nonzero consumption.

How to Monitor AI Units Usage

Oracle’s documented location is specific: “AI Units usage will be visible on the Billing Information page,” reached via Setup > Company > View Billing Information. This is the same page Oracle’s broader AI Units documentation references for both account-level usage and current balance.

Oracle documents email alerts as customers approach their licensed amount: “as customer nears their licensed amount, they’ll receive email alerts,” intended to notify administrators “when usage reaches key thresholds, such as when the account is approaching or has exceeded its AI Units allowance.” Oracle’s public documentation does not specify the exact threshold percentages that trigger these alerts, or whether alert recipients are configurable, treat those specifics as requires vendor confirmation.

Oracle’s documentation does not state a specific administrator role or permission required to view the Billing Information page, or how long historical AI Units consumption data is retained for reporting. Both are reasonable questions to confirm with your account team before relying on this page for ongoing governance.

How to Estimate Usage for a Pilot

A transparent planning formula, not a prediction: expected actions during the pilot period, multiplied by the published estimated range for that action, gives a planning range, not a bill.

Illustrative example 1. A pilot group runs 20 Ask Oracle analysis questions per week for a four-week pilot: 80 questions x 10-50 AI Units = a planning range of roughly 800-4,000 AI Units for the pilot period. This is a bounded example using Oracle’s published range, not a forecast of what any specific account will actually consume.

Illustrative example 2. A support team generates 15 Case Summary outputs per day for two weeks (10 business days): 150 summaries x 5-75 AI Units = a planning range of roughly 750-11,250 AI Units. The wide spread here reflects Oracle’s own wide published range for this feature, not an error in the math, some case summaries are simple, some are long and complex.

Both examples use neutral, generic labels rather than a named company or claimed outcome, and neither should be read as a quote, a bill prediction, or a savings estimate. Entitlement, included allowance, and additional-package pricing all require direct confirmation from Oracle or your account team before you commit a pilot budget.

Budget Guardrails Without Invented Pricing

Because Oracle doesn’t publish add-on package pricing, a NetSuite AI Units budget can’t be expressed reliably in currency from public information alone. What can be planned without invented numbers:

• Set an internal AI Units consumption threshold for the pilot (a number of units, not a dollar figure) that triggers a review before the pilot expands.
• Track observed consumption against your planning range weekly during the pilot, not just at the end.
• Decide, before the pilot starts, who is notified if consumption is trending well above the planning range, separate from Oracle’s own account-level email alerts.
• Confirm the additional-package purchase process and lead time with your account team before you’re actually close to exhausting your allowance, not after.

These are internal governance practices ERP Peers recommends, not Oracle-published defaults, and they’re presented as such. Ongoing monitoring like this is the same discipline a NetSuite optimization engagement applies to any recurring account cost, not something unique to AI.

What to Confirm Before Expanding Usage

Take this list to Oracle, your account representative, or your contract owner before scaling an AI pilot beyond its initial bounded group:

• Your account’s current included AI Units allowance and remaining balance.
• Exact reset/renewal timing tied to your specific contract term.
• Current pricing for the 10,000-unit and 25,000-unit additional packages.
• Whether your account/edition is eligible for every AI feature you intend to pilot.
• Regional availability for any feature limited to specific data centers.
• Feature-specific consumption behavior not covered in Oracle’s general documentation.
• Whether SuiteCloud Agent Skills or SuiteCloud Developer Assistant usage consumes AI Units in your account.
• Exact alert threshold percentages and whether recipients are configurable.
• What “pause any further usage” looks like in practice when units run out mid-cycle.
• Which roles/permissions are required to view AI Units billing data.
• How long historical consumption data is retained for reporting.
• Any contract-specific exceptions to the standard allowance or package terms.

Common Planning Mistakes

• Treating “included” as “unlimited.” A 1,000-unit monthly allowance per General Access user is real, but it’s shared across a company-wide pool and a handful of research-style Ask Oracle questions can consume 50-200 units each.
• Converting a range into a single number. Oracle’s own estimates span wide ranges (5-200 units for Narrative Insights alone); planning around the midpoint as if it were precise understates the real variance.
• Assuming every feature consumes AI Units. Bill Capture, EPM products, and NSAW explicitly don’t, budgeting AI Units for them is a wasted planning step.
• Waiting until the balance is low to ask about additional packages. Oracle’s documented behavior when units run out is to purchase more or pause usage, neither is instant, plan the confirmation conversation before you need it.

AI Units Operating Checklist