Before you connect NetSuite

Contact Optiply Support to confirm the environment, authentication route, required data permissions and setup owner. Have your NetSuite administrator perform the account-side steps. Keep production and sandbox access separate.

Use the token-based steps below only for a connection that uses that route. Oracle states that NetSuite 2027.1 prevents creating new TBA integrations. Existing integrations continue until TBA support ends in 2028.2. Discuss the route with Support before starting a new integration on those releases. Do not replace TBA credentials with OAuth credentials in an existing form.

Steps to prepare NetSuite token access

  1. In NetSuite, open Setup → Company → Company Information and record the Account ID.
  2. Open Setup → Company → Enable Features, then the SuiteCloud tab.
  3. In Manage Authentication, enable Token-based Authentication and accept the applicable terms.
  4. Save the feature settings.
  5. Open Setup → Users/Roles → User Management → Manage Roles.
  6. Create or customise the integration role with the data and service permissions agreed for your connection.
  7. Add Log in using Access Tokens, or User Access Tokens if that user must create its own tokens.
  8. Save the role.
  9. Open the intended employee through Lists → Employees → Employees and choose Edit.
  10. On Access, select the integration role, choose Add, then Save.
  11. Open Setup → Integration → Manage Integrations → New.
  12. Enter an application name and keep State as Enabled.
  13. On Authentication, select Token-based Authentication for the confirmed route.
  14. Clear User Credentials if the application will authenticate only with tokens.
  15. Save and store the Consumer Key and Consumer Secret securely.
  16. With an authorised token manager, open Setup → Users/Roles → Access Tokens.
  17. Choose New Access Token and select Application Name, User and Role.
  18. Save and store the Token ID and Token Secret securely.

The application credentials and token values appear only on their respective confirmation pages. Oracle's token-based authentication setup links the detailed administrator procedures.

Steps to connect NetSuite in Optiply

  1. In Optiply, open Settings → Integrations.
  2. Wait for the source lists to load, then choose Add a source.
  3. Select NetSuite if it appears, then choose Next to open Connect to system.
  4. If Contact us appears, choose it to request assisted setup.
  5. If credential fields and Connect appear, confirm the requested configuration with Support, enter the agreed values and choose Connect.
  6. If Support needs access details, use only the secure method agreed with Support.
  7. After setup, return to Settings → Integrations and check the source name and Connected label.
  8. Compare the first agreed records with NetSuite using the mapping guide below.

If NetSuite is absent from the menu, contact Support instead of selecting another connector. If the route is unclear, stop before submitting configuration.

Fields in NetSuite connection setup

FieldMeaning
Account IDThe NetSuite environment being connected.
Consumer Key / Consumer SecretThe application's credential pair.
Token ID / Token SecretThe token tied to the selected application, user and role. Some forms call Token ID Token Key.
Application Name, User, RoleThe records that determine which application and permissions the token uses.
Contact usStarts an assisted setup request when offered.
ConnectSubmits the displayed configuration when offered.
ConnectedA linked source, not confirmation that every record has arrived.

What you see when NetSuite connection setup worked

NetSuite holds the intended application, user-role assignment and token. Optiply shows Connected once the source is linked. Check imported records separately, including products, suppliers and orders selected for your connection.

Limits of connecting NetSuite

Permissions depend on the selected data and service route. Access Token Management lets a token manager manage other users' tokens. It does not itself allow token login. User Access Tokens already includes token login, so the same role does not also need Log in using Access Tokens.

If the confirmed connection uses RESTlets, Oracle requires Client SuiteScript and Server SuiteScript features. These are not universal requirements for every token-based connection.

Production tokens are not copied to sandbox or preview accounts. A sandbox refresh requires new sandbox tokens. Agree synchronization timing with the setup owner.

If your account reaches its integration limit, contact Support before adding another source.

If connecting NetSuite did not work

If Add a source remains unavailable after loading, or NetSuite is missing, contact Support. If credentials are rejected, have the administrator check the environment, application state, assigned role and token selection.

If a secret was not saved, coordinate replacement with Support. Resetting application credentials invalidates the previous pair. Never email secrets, tokens or passwords.