NetSuite Setup

NetSuite setup and connection

This version uses SuiteTalk SOAP with token-based authentication (TBA). The authentication selector exposes only Token. Username/password authentication, application-ID CLI arguments, REST, and OAuth 2.0 are not implemented by this package.

Check the integration's service life

Oracle's SOAP removal FAQ announces SOAP removal in NetSuite 2028.2 and the end of creating new SOAP/TBA integrations in 2027.1. It recommends REST with OAuth 2.0 for new work. These are NetSuite release milestones, not dates defined by this connector.

The package still defaults to SOAP endpoint 2024_2 and the 2024.2 SDK series. Changing only the endpoint setting is not a REST migration or proof of compatibility with a newer schema. Check Oracle's current versioning guidance and your account's release before selecting this version for a new integration.

Prepare an integration identity

The Rocket Web credential guide describes the TBA setup sequence. Adapt it to the current NetSuite account:

1. Enable SOAP Web Services and Token-based Authentication in the account's SuiteCloud features.
2. Create an enabled integration record with TBA and retain its consumer key and consumer secret in the project's credential store.
3. Assign a dedicated integration user a role with access to the records, custom fields, lists, locations, saved searches, and files used by the selected flows.
4. Create an access token for that integration, user, and role. Retain the token ID and token secret securely.
5. Get the account ID and the account-specific SuiteTalk URL from NetSuite's account/company information. Use the correct sandbox or production account.

The original guide's Administrator/CEO examples are not a universal permission requirement. Verify permissions against the selected operations with the NetSuite administrator. Oracle documents integration records for TBA and account-specific web-service URLs.

Enter store settings

Under General settings, set:

Setting	Value to supply
NetSuite Host	The account-specific SuiteTalk base URL, such as https://ACCOUNT.suitetalk.api.netsuite.com. Use the value provided by the account.
NetSuite account id	The exact account ID, including the sandbox suffix when applicable.
Consumer key / Consumer secret	Values belonging to the integration record.
Token Id / Token secret	Values belonging to its user and role.
NetSuite Base url	The account's browser application base URL. Used for admin links, not SOAP authentication.
Soap Request timeout	Defaults to 180; the client applies a minimum connection timeout of 60 seconds.

The SOAP endpoint is configured at mageos_netsuite/general/nsendpoint, defaults to 2024_2, and has no editable field in this version's admin form. Keep it aligned with the installed SDK.

Click Test connection, then save the settings. The test calls getServerTime. Continue with an actual sandbox record for each enabled flow.

Separate connection credentials

Import, Export, and Stock connection groups can inherit the General credentials, or use a separate TBA credential set by changing Same as default connection? to No. They share the General account, host, and endpoint.

Explicit import, export, and stock run modes choose their corresponding groups. The all run mode retains the General credential context throughout its processing. importToQueue, processQueue, location mode, and direct utility commands also do not automatically select the import/export groups. Use explicit run modes when credential separation matters.

Credential handling

The current admin form defines credential fields as ordinary text and does not assign Magento's encrypted configuration backend. Do not assume these secrets are encrypted in core_config_data or masked in exports. Restrict configuration access, protect database backups, and use the host platform's supported secret/environment configuration practices. Never put credentials in command examples, support tickets, screenshots, or this wiki.

Prepare dependent NetSuite records

Flow	NetSuite preparation
Products	Item fields and price levels matching the product mappings.
Configurables	Populated custitem_magento_matrix_children and custitem_magento_matrix_attrs; the historical population script is not bundled.
Images	Custom item fields containing NetSuite File references and role access to those files.
Customer export	A custom address field for the connector's address identity; configure its script ID explicitly.
Orders	Payment methods, shipping items, optional order location, and mapped transaction fields.
Tax and discounts	Matching tax/discount item IDs or a validated NetSuite tax-calculation setup.
Refunds	custbody_rw_cf_so_origin linking the originating sales order; optional custbody_rw_cf_refund_in_magento.
Stock	Saved item search with the required result columns.
Locations	Source-code/import/enabled custom fields described in Inventory, subject to the location-import limitation.

Sources: auth choices, service configuration, credential routing, connection test, admin fields.