# NetSuite

> Planned: look up order history, draft sales orders and update customers in NetSuite by text.

Status: Coming soon

Source: https://asktack.com/docs/integrations/netsuite/

**Status: planned — not available to connect in Tack yet.** These steps prepare the integration; creating vendor credentials does not enable it in the app.

## Planned workflows

Planned for NetSuite:

| You text | What would happen in NetSuite |
|---|---|
| "What did Dale's Hardware order last quarter?" | Reads order history |
| "Reorder the same" | Drafts a sales order |
| "New customer: Ridge Plumbing" | Creates the customer |

These are intended workflows, not a guarantee that every operation is exposed by the vendor. Each must pass the API and permission checks below before release.

## Before you start

Involve the customer's NetSuite administrator. Record the account ID, sandbox/production environment, subsidiaries and the records the pilot may change. Use OAuth 2.0 for this proposed REST integration.

## Developer setup — once

1. Implement the OAuth authorization-code flow, encrypted token storage and account-specific API routing.
2. Choose whether the integration record will be distributed or registered separately by each customer. Document the exact callback URL and required REST record operations.
3. Check record metadata and custom fields before building order writes. Draft creation and transaction approval/posting must remain separate actions.

## Customer setup — repeat for each account/environment

1. The admin confirms OAuth 2.0 and REST Web Services are enabled and creates an appropriately restricted role/user. Use Oracle's [OAuth setup guide](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_157771281570.html).
2. Install the supplied integration record, or open **Setup → Integration → Manage Integrations → New** to create the agreed customer-specific record.
3. Set its state to **Enabled**. Under OAuth 2.0, enable **Authorization Code Grant**, enter the exact HTTPS redirect URI and select **REST Web Services**. Enable RESTlets only if the connector actually uses them.
4. Save the record and configure its client credentials through the secure setup process. Select the appropriate public/confidential client configuration with the developer; do not expose a confidential secret in a browser.
5. Authorize as the designated user and role. Record the account and subsidiary restrictions with the connection.

Oracle documents [integration-record creation and OAuth options](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_157771733782.html).

## Verify write access

In a sandbox, read a test customer and item, create an unapproved test sales order and read it back. Check subsidiary, currency, tax, pricing and mandatory custom fields. Confirm it has not been fulfilled, billed or approved. Repeat permission checks for production rather than copying sandbox credentials.

## Disconnect and troubleshoot

Have the admin block/disable the dedicated integration and revoke its authorizations, then remove stored tokens. If reads succeed but writes fail, inspect role record permissions, subsidiary restrictions and required fields before broadening access. Account or environment mismatches require correcting the connection configuration.

## Who completes the work?

An agent/developer can implement the connector, field mappings and automated checks. A customer administrator must authorize account access and permissions; the vendor must approve any restricted partner access. A business operator verifies the test records before production use. Follow the [shared setup and release checklist](https://asktack.com/docs/integration-setup/) for credential handling, approval gates and launch checks.

_Setup guidance reviewed October 23, 2026. Vendor menus and entitlements can change; unresolved details are called out above._